On Friday 01 March 2002 21:37, Tod Harter wrote:
> > From http://www.w3.org/TR/html4/interact/forms.html#form-content-type :
> >
> > ----
> > application/x-www-form-urlencoded
> >
> > This is the default content type. Forms submitted with this content type
> > must be encoded as follows:
>
> The point is that to conform to proper MIME typing an encoding should be
> specified by the HTTP user agent. So It should send back
>
> Content-Type: application/x-www-form-urlencoded; charset=EUC-JP
>
> for instance. Though actually I believe that if you look up the reference
> on URL encoding that it ALREADY specifies US-ASCII. Anything else
> technically should be escaped. So, basically you have it there in a
> nutshell. There should be no problems with unknown encodings, at least in
> theory...

Right.... apart from that tiny little nagging problem being that the charset 
parameter on application/* is ILLEGAL.

> > Except that this is not possible, at least not if you intend to do
> > anything meaningful with the data.
>
> That might be overstating it a bit. As long as you don't have to convert it
> to any other charset you can still use the information. Honestly I wonder
> how big a problem this is for most applications. I cannot recall having
> serious problems with accepting fairly simple form input wrt encodings.

And how do you use textual data without knowing which charset it is in? You 
can't, you don't. In fact, without knowing the charset you're really dealing 
with raw binary data, and all the power of Perl can't help much. I've had 
those problems, they exist.

-- 
_______________________________________________________________________
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
Critic, n.: A person who boasts himself hard to please because nobody
tries to please him.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to