[Encoding] WG response on: Choice of encoding details [I18N-ISSUE-371]

Hello Martin,

Your comment [1] on 9 June, 2014, was recorded as I18N-ISSUE-371 [2] and was ACCEPTED by the Internationalization WG.

The operative part of your comment was:

When it comes to passing CR, does the WG intend to count the old Opera
browser? I don't think this would be appropriate, because this browser
is no longer being developed or distributed.

The I18N WG has examined the tests that you supplied as adapted for compatibility with the TTWF framework by Richard [3], and discussed the differences with Anne. The variations in the single byte encodings appear to stem mainly from differences in whether browsers pass unmapped bytes through, generate the U+FFFD replacement character, or generate a PUA code point. Anne has agreed to examine what the majority of browsers are currently doing and adapt the mapping tables appropriately. Opera 12 had a specific (and different) behavior from most other browsers in this regard. To answer your question, the WG does not intend to consider the older Opera browser as an example. Bug 26618 [4] was created to track this issue.

Please reply to this message indicating whether you are satisfied with this resolution.

Thanks (for I18N),


[1] http://lists.w3.org/Archives/Public/www-international/2014JulSep/0026.html 
[2] http://www.w3.org/International/track/issues/371

[3] http://www.w3.org/International/tests/repository/encoding/indexes/results-indexes.en.php

[4] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26618 

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 17:51:28 UTC