[whatwg] StringEncoding: Allowed encodings for TextEncoder
glenn at zewt.org
Tue Aug 14 12:23:34 PDT 2012
On Tue, Aug 14, 2012 at 9:42 AM, Simon Pieters <simonp at opera.com> wrote:
> On Thu, 09 Aug 2012 19:42:07 +0200, Joshua Bell <jsbell at chromium.org>
> http://wiki.whatwg.org/wiki/**StringEncoding<http://wiki.whatwg.org/wiki/StringEncoding>has been updated to restrict the
>> supported encodings for encoding to UTF-8, UTF-16 and UTF-16BE.
>> I'm tempted to take it further to just UTF-8 and see if anyone complains.
> I was going to suggest doing so. We've gone UTF-8-only for new features
> (workers, webvtt, appcache manifest, etc). The Encoding spec says "New
> content and formats must exclusively use the utf-8 encoding.". Is there a
> use case for utf-16/utf-16be?
Specs can't (meaningfully) place normative requirements on all "new content
and formats". This should be a note.
More information about the whatwg