- From: Glenn Maynard <glenn@zewt.org>
- Date: Tue, 14 Aug 2012 14:23:34 -0500
- To: Simon Pieters <simonp@opera.com>
- Cc: whatwg@lists.whatwg.org, Joshua Bell <jsbell@chromium.org>
On Tue, Aug 14, 2012 at 9:42 AM, Simon Pieters <simonp@opera.com> wrote: > On Thu, 09 Aug 2012 19:42:07 +0200, Joshua Bell <jsbell@chromium.org> > wrote: > > 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. -- Glenn Maynard
Received on Tuesday, 14 August 2012 19:24:03 UTC