> > What I'm saying is that instead of implementing any workaround I'll
> > just try to make sure we implement the standard ( ;charset= ) and
> > make it possible to customize this ( by adding a module ).
>
> Agreed. What I want to say is that there is anothor charset problem in
> JSP. And I thin
Costin
From: Costin Manolache <[EMAIL PROTECTED]>
Subject: Re: TC3.3: Encoding
Date: Tue, 20 Feb 2001 11:23:00 -0800 (PST)
Message-ID: <[EMAIL PROTECTED]>
> What I'm saying is that instead of implementing any workaround I'll
> just try to make sure we implement th
> 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.
What I'm saying is that instead of imple
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
After more thinking, I have to agree with Hans - some of the
"advanced" guesses for detecting the encoding are too "significant" and
not enough specified ( or on the "border" line).
I will fix as many bugs as possible in this area, but I'll not add any new
functionality for 3.3.
What I have to d
