Re: Multi-byte character support.
Kazuhiro, thank you for your reply, I will investigate the possibility of using tomcat 3.2.b2 - however it is likely I will need to await 3.2.2 milestone before considering it as a release candidate. -Thom Thom, From: "T. Park" [EMAIL PROTECTED] Subject: Multi-byte character support. Date: Mon, 26 Mar 2001 10:32:31 -0800 Message-ID: [EMAIL PROTECTED] Tomcat 3.2[.1] doesn't seem to like static html pages (or servlets for that matter) that offer multi-byte (non-latin) characters. Tomcat 3.2.2b2 has many i18n improvements. Would you use and check 3.2.2b3 if possible? Of cource, a few i18n problem (for example, ServletRequest#getProperty method don't return value in Unicode) isn't resolved in 3.2.2. But they will resolve them in 3.3 4.0. Kazuhiro Kazama ([EMAIL PROTECTED])NTT Network Innovation Laboratories
Re: Multi-byte character support.
From: "Java Poop" [EMAIL PROTECTED] Subject: Re: Multi-byte character support. Date: Mon, 26 Mar 2001 22:33:36 -0800 Message-ID: [EMAIL PROTECTED] What are the il8n limitations in 3.2.1? For example, there are the following limitations: 1, The getParameter method in ServletRequest class returns non-Unicode strings. If a HTTP GET or POST request is done by a HTML form, servlet can't know its charset because the request don't have its charset information. The HTML 4.0 specification recommends to encode UTF-8 strings but most of systems don't do it. Tomcat 3.2 treats parameters like their charset is ISO-8859-1. Other servlet container may return Unicode strings by its own encoding detection method but it is tricky and don't work under some situation. For avoiding this problem, Servlet 2.3 API has setCharacterEncoding method and Tomcat 4.0 based on it. Because Tomcat 3.2 based on Servlet 2.2 API, we can't use this method. But Costin will provide an extension module for Tomcat 3.3 (for example, specify the default encoding per context). 2, A JSP content's encoding may not be recognized correctly. This cause is a lack of a function to specify JSP content's encoding (JSP output encoding is specified by contentType attribute of Page directive). JSP 1.2 has new pageEncoding attribute of Page directive. And a file localization method, it is proposed by Arieh, may provide another solution. Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
Re: Multi-Byte character support.
I have helped work on a fix for this on 4.0 (which supports the javax.servlet.ServletRequest.setCharacterEncoding() method). Tomcat 3.x does not support the new servlet 2.3 methods, so I did not look at fixing it in Tomcat. However, I have an easy to use object (included) which is able to process the mangled string and convert it to the encoding that you specify. This method will work for all Strings parsed into Tomcat (or other web servers). Tim Tye T. Park writes: Greetings, Tomcat 3.2[.1] doesn't seem to like static html pages (or servlets for that matter) that offer multi-byte (non-latin) characters. Has anyone coded a patch to fix this and/or have a workaround for the issue. I'd rather avoid having to re-invent the wheel. Does anyone have any insights as to how big a problem this is to fix? Cheers, Thom -- http://www.borland.com/newsgroups http://www.borland.com/devsupport/disclaim.html ChangeStringEncoding.java
Re: Multi-byte character support.
Thom, From: "T. Park" [EMAIL PROTECTED] Subject: Multi-byte character support. Date: Mon, 26 Mar 2001 10:32:31 -0800 Message-ID: [EMAIL PROTECTED] Tomcat 3.2[.1] doesn't seem to like static html pages (or servlets for that matter) that offer multi-byte (non-latin) characters. Tomcat 3.2.2b2 has many i18n improvements. Would you use and check 3.2.2b3 if possible? Of cource, a few i18n problem (for example, ServletRequest#getProperty method don't return value in Unicode) isn't resolved in 3.2.2. But they will resolve them in 3.3 4.0. Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
