(2012/04/24 15:48), Henri Sivonen wrote:
Does the OS/2 port need it for interfacing with the system APIs? If
the OS/2 port needs it for interfacing with the system APIs, can we
stop exposing the encoding to the Web and can we stop building the
IBM864 encoder/decoder on non-OS/2 platforms? I think
On Tue, 24 Apr 2012 05:31:57 +0200, Makoto Kato
wrote:
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 ambiguo
On Tue, Apr 24, 2012 at 6:31 AM, Makoto Kato wrote:
> (2012/04/20 17:09), Anne van Kesteren wrote:
>> 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
(2012/04/20 17:09), Anne van Kesteren wrote:
On Fri, 20 Apr 2012 09:58:52 +0200, Makoto Kato
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
On Fri, 20 Apr 2012 09:58:52 +0200, Makoto Kato
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]).
Hi Anne.
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]).
Although ICU supports IBM864, this doesn't map
