W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2012

Re: [whatwg] Encoding: API

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 10 Oct 2012 16:50:45 -0700
Message-ID: <CA+c2ei8r9g=ODWo=N3mS6GSNAF7OoR_ox_ru8w0yV-uOaYaOuQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: WHATWG <whatwg@whatwg.org>, Joshua Bell <jsbell@chromium.org>
On Wed, Oct 10, 2012 at 6:42 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> Hey, I was wondering whether it would make sense to define
> http://wiki.whatwg.org/wiki/StringEncoding as part of
> http://encoding.spec.whatwg.org/ Tying them together makes sense to me
> anyway and is similar to what we do with URL, HTML, etc.
>
> As for the open issue, I think it would make sense if the encoding's
> name was returned. Label is just some case-insensitive keyword to get
> there.
>
> I also still think it's kinda yucky that this API has this gigantic
> hack around what the rest of the platform does with respect to the
> byte order mark. It seems really weird to not expose the same
> encode/decode that HTML/XML/CSS/etc. use.

Also, Firefox 18 as well as recent nightlies implement this draft. It
should be matching the draft pretty closely, though I know there is
some weirdness in handling invalid input for some encodings when doing
decoding. This is also hooked up to the generic Gecko decoder backend
which means that the decoder doesn't yet support the exact set of
encodings as defined by the http://encoding.spec.whatwg.org/ spec.

/ Jonas
Received on Wednesday, 10 October 2012 23:51:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT