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

Re: Character encoding information of Http Request

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 13 Sep 2006 14:18:21 +0200
To: "Richard Ishida" <ishida@w3.org>
Cc: <www-international@w3.org>
Message-ID: <chrfg2hni9ako6hq1nbn5np7fg4u7fmi31@hive.bjoern.hoehrmann.de>

* Richard Ishida wrote:
>If you are aware of current or future standard to retrieve the
>character encoding from the browser, please let me know. 

"HTTP request" is rather broad, there are many places in a HTTP requests
where character information is conveyed to web applications, including
the request resource identifier, individual header fields, and the body
of the message. Clients would only need to convey encoding information
if it is possible that different clients use different encodings. This
is typically avoided (through means such as picking the page encoding
properly, or the accept-charset attribute for HTML forms). Where this is
insufficient, http://www.w3.org/TR/web-forms-2/#the-charset can be used
in some browsers. draft-hoehrmann-urlencoded-00 is an upcoming Internet-
Draft that helps removing the need to convey the character encoding to
web applications. I am not sure there are cases where you need _charset_
if you want UTF-8 submissions, though.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 13 September 2006 12:18:30 GMT

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