DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9654>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9654 Tomcat converts to ASCII when it should convert to ISO-8859-1 ------- Additional Comments From [EMAIL PROTECTED] 2002-06-06 06:51 ------- >From what I can see in the sourcecode, all the translation between Locales and >Charset is done by o.a.c.util.CharsetMapper. Now, if your locale (Locale.toString()) returns en_US, that locale will not be recognized by the default properties, but it will in "second match" because we attempt to match on the full locale first, and on the Locale.getLanguage() then (so, if en_US is not in the CharsetMapper.properties file -and it's not- it will be retried only with "en" and that resolves back to ISO-88590-1, so it should work allright. So, either you're setting some weird locale default in your VM, or your OS configuration is _really_ foobared... I just verified, and it works on Solaris 8 with JDK 1.3.1_03 on a SparcV9 system. For sure we make some wild assumptions in setLocale (we set the "encoding" field which is not used when creating the writer, for example, and if someone sets the locale, then sets a content type which includes a ";" character, and then sets the locale again, we might as well send everything down the drain), but with fairly well constructed servlets, this shouldn't be an issue. It's hard to say what's wrong without seeing your code. It _should_ work (on paper). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
