- From: Phillips, Addison <addison@lab126.com>
- Date: Wed, 20 Aug 2014 18:02:23 +0000
- To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
- CC: "www-international@w3.org" <www-international@w3.org>
Hello Martin, Your comment [1] on 2 July, 2014, was recorded as I18N-ISSUE-373 [2] and was ACCEPTED by the Internationalization WG. Your comment read in part: -- I wonder whether the WG has considered the chances of deployment in particular for the actual encoding conversion definitions. -- The I18N WG has considered this issue. The point of the Encoding specification is that it documents what browsers actually do, or, in cases where this is currently divergent, is based on consensus for the best interoperable choice of implementation. There is support from the major browser vendors to change or "correct" encodings to be consistent with the Encoding specification in these cases. Therefore we have concluded that, while your comment is an important consideration for CR, there is a high (possibly 100%) chance of deployment across the major browsers for all of the character encoding conversions described in Encoding and any discrepancies will be considered as "bugs" in that specific implementation by the implementer, to be fixed as time and release schedules permit. Please reply to this message indicating whether you are satisfied with this resolution. Thanks (for I18N), Addison [1] http://lists.w3.org/Archives/Public/www-international/2014JulSep/0028.html [2] http://www.w3.org/International/track/issues/373 Addison Phillips Globalization Architect (Amazon Lab126) Chair (W3C I18N WG) Internationalization is not a feature. It is an architecture.
Received on Wednesday, 20 August 2014 18:03:40 UTC