W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2006

RE: [MWBP 1.0] i18n comment: Support Unicode

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 18 May 2006 17:51:10 +0200
To: Richard Ishida <ishida@w3.org>
Cc: public-bpwg-comments@w3.org, public-i18n-core@w3.org
Message-Id: <1147967470.14951.2.camel@cumulustier>

Le jeudi 04 mai 2006 à 15:22 +0100, Richard Ishida a écrit : 
> The current text, however, doesn't particularly encourage content authors to
> use UTF-8. On the contrary, since it talks about using the value of the
> Accept-Charset header and is noncommittal about which encoding is being
> indicated using the Content-Type header and what determines the choice of
> encoding, it makes no clear recommendation to use utf-8.

As discussed with you in a separate thread, the BPWG has agreed to amend
the text under the Character Encoding section to clarify why using
Unicode is good choice:
"Encoding of the content to a desired character encoding is dependent on
the authoring tools being used, Web server configuration and the server
side scripting technology being used (if any). For a discussion of this
see [CHARSET1] and [CHARSET2].

Unicode is a good choice for representing content when served in
multiple languages. The amount of bandwidth required to transmit content
can vary significantly depending on the character encoding used. Text
consisting principally of characters from the Latin alphabet will encode
more efficiently in UTF-8, whereas text consisting principally of
characters from ideographic scripts will encode more efficiently in
UTF-16. When choosing a character encoding, consider the efficiency of
the available encodings.

Since the Default Delivery Context specifies use only of UTF-8, all
applications should support UTF-8.
"
http://www.w3.org/TR/2006/WD-mobile-bp-20060518/#CHARACTER_ENCODING_USE

As this came as a result of a discussion with you, we assume that you
are now satisfied with this resolution.

Dom
Received on Thursday, 18 May 2006 15:51:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:50 GMT