Hi!
Nikola Milutinovic wrote:
>>>>I have had similar problem with Cp1250 encoding(Tomcat and MySQL). You
>>>>have to have in mind this was not done on Tomcat 4.x, but 3.x.
>>>>This is what I have done:
>>>>- <%@page contentType="text/html; charset=windows-1250"%> on top of
>>>>every JSP file
>>>>
>>>>
>>>I don't think that is a correct character encoding as far as Java is concerned. I
>think Java supports only ISO-8859-* and UTF-*. Please correct me if I'm wrong
>>>
>>>
>>
>>I'm sorry, butr you are wrong. You can convert between numerous
>>encodings, but you have to have i18n.jar in your classpath.
>>
>
> Hmm, I thought that Java community loathed anything but ISO, where can I find
>i18n.jar? I'll look for it on Sun's site, but if it is not there, drop me a line.
>
You can get it in jre/lib directory of your JDK install directory.
>
>>>What I'm looking for is a "politically correct" solution. I have so far:
>>>
>>>- PostgreSQL with one Unicode and one ISO-8859-2 databases, both with the same data
>in correct form.
>>>- JDBC driver which is acting OK.
>>>- JSP pages with correctly set pageEncoding
>>>- Java Servlet with correctly set contentType/encoding
>>>
>>>Still, Tomcat goes for default charset encoding and screwes up Latin-2 characters.
>>>
>>>
>>Have you tried putting %@page contentType="text/html;
>>charset=iso8859-2"%> on top of your JSP's ?
>>
>
> Always. And that is what is driving me crazy. I have even tested what is the
>character encoding of the ServletResponse object - it was OK, ISO-8859-2. The trouth
>is I'm running 4.0.1 and I have been looking at sources for 4.0. I'll test 4.0 and if
>it displays characters correctly, there's gonna be a bug report.
>
> Nix.
>
Best regards,
Kovi
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
