W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2011

I18N-ISSUE-106: When the character cannot be encoded into the target encoding [HTML5-prep]

From: Internationalization Core Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 22 Jul 2011 18:00:23 +0000
To: public-i18n-core@w3.org
Message-Id: <E1QkK1P-0001wS-Iz@barney.w3.org>

I18N-ISSUE-106: When the character cannot be encoded into the target encoding [HTML5-prep]

http://www.w3.org/International/track/issues/106

Raised by: Addison Phillips
On product: HTML5-prep

2.6.3 Resolving URLs
http://www.w3.org/TR/html5/urls.html#resolving-urls

Deals with processing URLs. The steps here result in defining the "character encoding" of the URL, which is applies to the query portion of the URL. I put character encoding in quotes, because what it really is the character encoding of the document or script containing the URL as a string. Step 8.2 contains an implicit encoding conversion (to the document character encoding). A health warning should be supplied about what to do when the character cannot be encoded into the target encoding.
Received on Friday, 22 July 2011 18:00:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 July 2011 18:00:30 GMT