Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

The Content-type charset issue

schmidtJan 16 2008 — edited Jan 16 2008
Hi

I've been reading the thread about the origins of the #HEAD# substitition: 606680

Because I want to change the charset parameter in the content-type meta tag in my application. I'm a bit worried since it appears that the value of this attribute is controlled by the PlsqlNLSLanguage setting in the dad. OK and Jan has had various settings here. But there are references to documentation that state that from Apex 3.0 you really can't change the setting with regards to charset (http://download-uk.oracle.com/docs/cd/B32472_01/doc/relnotes.300/b32465/toc.htm#BGBCJIEA) - it must be AL32UTF8.

Now, I'm on 2.2, but I'm definately planning on upgrading at some point, so I guess that limitation will apply to my config too.

AL32UTF8 yields a content type meta tag with charset=utf-8. If I can't change that, how do I get charset=iso-8859-1 like I need?

Scott proposed to put in a second content-type meta tag to (maybe) override the one that Apex makes. I'm going to try that to see if it saves me. But can it be true that Apex doesn't give me any options here - other than relying on browsers probably guessing what I want when I give them HTML-hacks? In my view, that would clearly constitute a bug.

Jakob
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 13 2008
Added on Jan 16 2008
11 comments
1,105 views