Costin
From: [EMAIL PROTECTED]
Subject: TC3.3: Encoding
Date: Mon, 19 Feb 2001 10:38:57 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
> What I have to do is fixing bugs and making sure the standard mechanism (
> charset in content type ) works. I will also try to make it possible to
> implement special behavior in independent modules ( for example, specify
> the default encoding per context ). ( I know that right now most browsers
> are not respecting the standard, and at least some workarounds are needed
> - but that can be done in a specific module, not part of the standard
> tomcat )
Perhaps there are two i18n improvements in Servlet 2.3 and JSP 1.2:
1, javax.servlet.ServletRequest#setCharacterEncoding()
2, pageEncoding attribute of Page directive
Alternative workarounds in these two points makes non-ASCII users
happy.
P.S.
FYI, a japanese volunteer makes a patch for making it possible to use
pageEncoding attribute on Tomcat 3.2.
http://www.ingrid.org/jajakarta/tomcat/tomcat-3.2/pageEncoding.patch
(I don't attach this patch because this patch don't match the current
specification.)
Kazuhiro Kazama ([EMAIL PROTECTED]) NTT Network Innovation Laboratories
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
