For what it's worth (if it helps in the future :) ), I went the route of just grepping the ERExtensions source for "encoding," then I just had to spend a little bit to figure out how ERXMessageEncoding worked.msOn Jun 17, 2006, at 6:29 PM, Thomas wrote:Mike,thanks for the help. That was spot on.But
Mike,thanks for the help. That was spot on.But... RRRGGGHHH! I spent many hours Googling and trawling through what little documentation I could find (without coming across this gem) and then more hours debugging and writing debug code and throwing more and more code at it until I found somethin
Wonder abstracts a lot of the encoding management through ERXMessageEncoding. It looks at the language that is being passed back from the browser and it maps it a default encoding. For English and German, that is ISO8859_1 and it does that on every request. You can try calling ERXMessageEncoding
It turns out that despite all my code, the form value encoding was
always ISO8859_1 and so was some of the page encoding.
This is even after I called WOMessage.setDefaultEncoding("UTF8") in
the application constructor, and despite the fact that I had code
that set the content encoding and f
I am having trouble with character encoding in a WO application that
encodes all pages in UTF-8.
As instructed by "Practical WebObjects" I have added an Application
appendToResponse that sets the header to UTF-8. I've also added a
meta-tag for content-type.
Just to be paranoid, I added th
