W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

[Bug 24386] Consider allowing more encodings in TextEncoder

From: <bugzilla@jessica.w3.org>
Date: Mon, 27 Jan 2014 12:02:59 +0000
To: www-international@w3.org
Message-ID: <bug-24386-4285-n3LbJTV9A3@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24386

Henri Sivonen <hsivonen@hsivonen.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@hsivonen.fi

--- Comment #1 from Henri Sivonen <hsivonen@hsivonen.fi> ---
(In reply to Anne from comment #0)
> People writing web-based email applications have found a need for it.

I think this needs more information about what the need is, etc. So far, it
looks like refusing to support non-UTF on the TextEncoder side has been a
success by making Gaia email just use UTF-8 (as opposed to e.g. resulting in
encoders written in JS):
https://github.com/mozilla-b2g/gaia-email-libs-and-more/blob/master/data/lib/js-shims/faux-encoding.js#L37

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 27 January 2014 12:03:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:36 UTC