There is no problem on Windows XP. For windows 2000 I have compiled the source with encoding option through ANT too. It started working on Windows 2000.
<javadoc sourcepath="${sourcedir}" encoding="ISO-8859-2" destdir="./doc/api" classpath="${servlet.jar}:${sapjco.jar}" packagenames="*" author="true" private="true" version="true" windowtitle="${project.title} API Documentation" doctitle="<h1>${project.title} Documentation (Version ${project.version})</h1>" bottom="Copyright "> <classpath refid="libraries"/> </javadoc> File encoding on windows system is - Cp1252. I did not use this option as it is working fine with encoding option in java compilation(javac) Could you please provide me information of making my application to work both on linux and windows. Is there anything need to handle this in tomcat server ? -----Original Message----- From: Christopher Schultz [mailto:[EMAIL PROTECTED] Sent: 13 lutego 2008 20:59 To: Tomcat Users List Subject: Re: i18N jsp application on linux and windows -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Raghuveer, Raghuveer wrote: | This is regarding the damage of polish messages from struts application | deployed on Tomcat on Linux and Windows XP . | | I get polish messages from SAP that to be displayed in JSP page. | | I have set ISO8859_2 in JSP page for charset. | | <%@ page contentType="text/html;charset=ISO8859_2" %> | | I have set encoding attribute in web.xml as below | | <?xml version="1.0" encoding="ISO-8859-2"?> | | This is working on Windows XP. | | But I get Question marks and different characters for polish messages from | application deployed on Linux :( Your charset doesn't look quite right. In the US, we typically use ISO-8859-1 (note the placement of the hyphens), so perhaps what you're looking for is "ISO-8859-2" instead of "ISO8859_2" in your contentType header in the JSP. | Please help if I need to do anything in tomcat on linux system.. Whether that is your problem or not, I wonder if your JVM on the Windows machine has its "file.encoding" set to ISO8859_2 while your Linux box has something else. Honestly, setting the "page" encoding should have done the trick, but for some reason it sometimes does not. Try launching Tomcat with an explicit setting for "file.encoding" like this: $ JAVA_OPTS="-Dfile.encoding=ISO-8859-2" bin/startup.sh (this will work using bash... not sure about other shells) Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkezDMQACgkQ9CaO5/Lv0PA8twCfYN8pBxi2UbOfO+nRqOmtK7rM 4N4AoJ5hscB0UZ0hrvjD4WIvNuE1wjA4 =z+yP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]