W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

RE: Encoding Standard (was: RE: Encoding API exceptions)

From: Shawn Steele <Shawn.Steele@microsoft.com>
Date: Sun, 9 Nov 2014 20:44:14 +0000
To: Domenic Denicola <d@domenic.me>, Anne van Kesteren <annevk@annevk.nl>, "www-international@w3.org" <www-international@w3.org>
CC: Joshua Bell <jsbell@google.com>, Masatoshi Kimura <VYV03354@nifty.ne.jp>, Boris Zbarsky <bzbarsky@mit.edu>, Allen Wirfs-Brock <allenwb@mozilla.com>
Message-ID: <26d8456ad19f4fa8998815ed736260b9@CY1PR0301MB0731.namprd03.prod.outlook.com>
> My understanding is that for the purpose of the web, these definitions are the standard definitions, and attempting to apply others will be incompatible with web content (and of course the many runtimes that attempt to interoperate with web content, including most server-side systems).

That's my concern.

Generally the content is created with text editors, from data stores, etc, that came from other systems, and not specifically for the web.  I'm unaware of systems that convert from shift-jis to shift-jis for example.

In other words, if the definitions are incompatible with the behavior on the host OS (or wherever the data comes from), then there're likely to be corruptions.

The solution is, of course, to use Unicode.

Received on Sunday, 9 November 2014 20:44:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC