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

I18N-ISSUE-380 (BUG23971): define an encoding for formerly latin1 [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 10 Jul 2014 04:17:35 +0000
Message-Id: <E1X55nb-0001Be-6e@stuart.w3.org>
To: public-i18n-core@w3.org
I18N-ISSUE-380 (BUG23971): define an encoding for formerly latin1 [encoding]

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

Raised by: Addison Phillips
On product: encoding

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23971

This issue tracks the bug listed above and was created as part of the WG LC process. The bug was created prior to the WG LC.

---

The web does not have latin1, but we do need it for HTTP and stuff. We should probably also expose it to the API.

"identity" makes some sense, but only in one direction. "bikeshed" also makes sense.

We should not expose this encoding to HTTP charset= or <meta> overrides. This is only for internal matters (such as XMLHttpRequest) and developers using the API.
Received on Thursday, 10 July 2014 04:17:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:09 UTC