On Tue, Aug 26, 2014 at 6:05 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> Richard, Martin, thanks a ton, this looks great.
>
> From your tests it seems Gecko has some discrepancies for windows-*
> encodings, this is now tracked through
> https://bugzilla.mozilla.org/show_bug.cgi?id=1058021 and will be fixed
> in Gecko.
>
> On Sat, Aug 23, 2014 at 10:34 PM, Richard Ishida <ishida@w3.org> wrote:
> > On 23/08/2014 19:06, Jungshik SHIN (신정식) wrote:
> >> JFYI, Blink (chrome 38 - soon to be beta - and newer opera) supports IBM
> >> 866.
> >
> > Thanks Jungshik, you might want to mention that here:
> > https://www.w3.org/Bugs/Public/show_bug.cgi?id=23154
>
> As Chromium now implements ibm866, we'll be keeping that encoding
> around. I closed the relevant bug.
>
I didn't know about that bug. When I picked encodings to support for
Chrome, I removed all the IBM code pages on purpose. (and then, I guess I
also filed a bug against Mozilla for doing the same). I wouldn't fight for
the removal of cp866, but would be happy to remove it again from Chrome 38
branch. Note that Chrome 38 is still in dev channel (and soon will be in
beta channel) and it'll be about 5-6 weeks before it turns stable.
Jungshik
>
> It seems for the remainder only Internet Explorer has differences. I
> suspect they'll want to align at some point to get better
> interoperability with sites.
>
> Given this it seems no changes to the single-byte indexes are required
> at this stage.
>
>
> --
> http://annevankesteren.nl/
>