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

Re: [whatwg] StringEncoding: Allowed encodings for TextEncoder

From: Simon Pieters <simonp@opera.com>
Date: Tue, 14 Aug 2012 16:42:37 +0200
To: whatwg@lists.whatwg.org, "Joshua Bell" <jsbell@chromium.org>
Message-ID: <op.wi1chbxnidj3kv@device-23f190>
On Thu, 09 Aug 2012 19:42:07 +0200, Joshua Bell <jsbell@chromium.org>  

> 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?

Simon Pieters
Opera Software
Received on Tuesday, 14 August 2012 14:43:19 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:44 UTC