(2012/04/20 17:09), Anne van Kesteren wrote:
On Fri, 20 Apr 2012 09:58:52 +0200, Makoto Kato
<m_k...@ga2.so-net.ne.jp> wrote:
I have a question of Encoding standard of
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html.
Gecko supports IBM864, but it is different of old IBM864. It is
modified to support euro sign due to requested by IBM ([1] and [2]).
Gecko also supports data:text/html;charset=ibm864,%25 0x25 -> U+066A
which is probably worse as it changes the ASCII range.
You submit encoding detail [3] in repository, but this spec seems to
be old spec of IBM864.
I think that we should use new mapping supported euro sign [4] instead
of old mapping. Or we should remove IBM code pages from spec. How do
you think?
Does that mean you want to remove the encoding from Gecko? That would
work for me. It is currently not supported by Opera either.
Alternatively mapping 0xA7 to U+20AC works for me too, but I don't want
it to tinker with the ASCII range.
Except to OS/2 and AIX, I think that this encoding is unnecessary since
most browsers aren't supported. If you only add IBM864 and IBM866 to
this spec as legacy encoding, you should add all encodings that Gecko
supports due to ambiguous.
