W3C home > Mailing lists > Public > www-international@w3.org > July to September 2003

Re: what should the charset be in the response to the server

From: Shigemichi Yazawa <yazawa@globalsight.com>
Date: Fri, 25 Jul 2003 17:29:18 -0600
Message-ID: <5eznj2dw35.wl@flatiron.globalsight.com>
To: Jungshik Shin <jshin@i18nl10n.com>
Cc: <www-international@w3.org>

At Fri, 25 Jul 2003 16:11:17 -0400 (EDT),
Jungshik Shin wrote:
> 
>   For a while (before 1.0), Mozilla added 'charset' parameter to
> Content-Type header  with application/x-www-form-urlencoded, but
> it broke a lot of CGI programs and was removed later.
> (see http://bugzilla.mozilla.org/show_bug.cgi?id=18643)

This is a very good example that shows that any standard must be
created with i18n in mind. It's very hard to change it after it's out
to the public.

>   If you specify ENCTYPE="multipart/form-data" in FORM, you'll
> get charset parameter specified in each part of 'multipart/form-data'
> if necessary.
> See http://www.w3.org/TR/html401/interact/forms.html#h-17.13.4.2

I tried this, but neither Mozilla 1.0 nor IE 6.0 add content-type
header in any part. I see something like this.

-----------------------------75689853717345751981973594324
Content-Disposition: form-data; name="i18n"

test string
-----------------------------75689853717345751981973594324--

If browsers support charset parameter in multipart/form-data, it would
disambiguate the character encoding, although getting input values
become a little cumbersome (you can't use the convenient
getParameter() method).

-------------------
Shigemichi Yazawa
yazawa@globalsight.com
Received on Friday, 25 July 2003 19:30:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:00 GMT