[whatwg] Encoding: API
jonas at sicking.cc
Wed Oct 10 16:50:45 PDT 2012
On Wed, Oct 10, 2012 at 6:42 AM, Anne van Kesteren <annevk at 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
> 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.
More information about the whatwg