ISSUE-371: Choice of encoding details

Choice of encoding details

State:

CLOSED

Product:

encoding

Raised by:

Addison Phillips

Opened on:

2014-07-10

Description:

http://lists.w3.org/Archives/Public/www-international/2014JulSep/0026.html

Comment from Martin Duerst:

This is a Last Call comment on
http://www.w3.org/TR/2014/WD-encoding-20140603/.

Extensive tests conducted by a student of mine have shown that for
single-byte encodings, Opera <=12 (i.e. Presto rendering engine) is the
most conformant, often perfect, while other rendering engines have more
errors.

As an example, for "windows-874", Presto is perfectly conforming, while
Firefox shows 23 errors, and IE, Chrome, Safari, and Opera >=16 show
exactly the same 8 errors.

If the goal of this spec, as I understand, is to help browsers
transition to uniform treatment of encodings, and if this allegedly can
be best achieved by considering browser market share, then some of the
encoding definitions should be carefully revisited.

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.

Related Actions Items:

No related actions

Related emails:

1. Re: Encoding single-byte tests (from duerst@it.aoyama.ac.jp on 2014-08-29)
2. [minutes] Internationalization telecon 2014-08-28 (from ishida@w3.org on 2014-08-29)
3. Re: [Encoding] WG response on: Choice of encoding details [I18N-ISSUE-371] (from duerst@it.aoyama.ac.jp on 2014-08-21)
4. [Encoding] WG response on: Choice of encoding details [I18N-ISSUE-371] (from addison@lab126.com on 2014-08-20)
5. [Bug 26618] New: Fix mappings of legacy single byte encoding test failures for consistency with browsers (from bugzilla@jessica.w3.org on 2014-08-20)
6. [minutes] Internationalization telecon 2014-07-24 (from ishida@w3.org on 2014-07-24)
7. I18N-ISSUE-371: Choice of encoding details [encoding] (from sysbot+tracker@w3.org on 2014-07-10)

Related notes:

Display change log