> > 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 think your proposal to add non-standard module is a kind of
> walkaround.
>
> (I am not a native english speaker and give rise to misunderstanding.)
I am not a native english speaker either - so don't worry, I'll understand:-)
There are many problems related with charsets and encodings - including in
JSP. And there is a good reason for that - most people are using 8859-1,
and are not exposed to the problem.
I tried to install my (native) charset ( 8859-2 ) and I'll start using it
- but it's not easy. I don't even know how to type ( on linux ) - I've
allways used 8859-1. ( and of course, there are at least 2
alternate charsets besides 8859-2, and few fonts, etc )
> Japanese developers has much experience about such I18n troubles. We
> would like to supply information that you may need.
As I said, the reason we have many bugs in this area is that most people
have little experience with this.
But we can do very little without help - paches, informations, testing,
etc.
It would be great if someone ( japanese, rusian, etc - i.e. someone who is
using foreign charsets ) could take over the "encoding" work in
tomcat3.3 - or at least provide info/patches/etc.
--
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
