W3C home > Mailing lists > Public > www-archive@w3.org > April 2012

single-byte encoding encoder research

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 13 Apr 2012 21:52:07 +0200
To: www-archive@w3.org
Message-ID: <op.wcpys5y264w2qv@annevk-macbookpro.local>
These are tests for the encoder algorithm of all the single-byte encodings  
as defined by http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html  
They are generated from generate.py using encodings.json and indexes.json  
as input, both of which can be found in the Encoding Standard repository.

The results seem to be that Firefox always uses the index. That Chrome  
(and Safari) have a few additions (so-called "fallback mappings") as well  
as sometimes mapping fullwidth ASCII to ASCII. That Opera always maps  
fullwidth ASCII to ASCII. (Fullwidth ASCII to ASCII is mapping U+FF01–FF5E  
to 0x21-0x7E.)

Given these results I think I prefer not changing the standard which  
states to use the index.

Anne van Kesteren

Received on Friday, 13 April 2012 19:52:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:44:03 UTC