----- Original Message -----
From: Jason Hunter <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 30, 2000 11:56 PM
Subject: Re: Problem with national characters in form input (Attention to
Sun servlet team)
> Vyacheslav Pedak wrote:
>
> > > What's your response to Costin's reasoning for closing the bug?
> >
> > I e-mail him that this problem really exists.
>
> I was hoping for something more compelling. Maybe an answer to his
> question about the e' character?
%E9 is russian character from Cp1251 encoding and it
sounds as "e'" in russian :).
>
> > After this choice web server can know what encoding to use
> > to this client even if web browser does not specify
> > anything in Content-Type header.
>
> Sort of a "here's the decoding method I want" flag. I'm not sure you're
> going to see that added to the servlet spec since the pertinent RFCs
> just don't make enough guarantees that things like that will always
> work. But you can of course build a little infrastructure to do it
> yourself. I showed in the book how to use a hidden charset value.
> That's been a commonly accepted way to deal with this problem.
>
If the problem exist and has "a commonly accepted way to deal
with this problem" why can not it been included in standart API?
In any case thank you for your replys, I understand that I have to
make my own infrastructure. I will try to do this and if it will be
convenient to use, may be other developers will use it too.
Vyacheslav Pedak.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
