24386 2014-01-24 22:31:53 +0000 Consider allowing more encodings in TextEncoder 2014-03-27 16:24:50 +0000 1 1 1 Unclassified WHATWG Encoding unspecified PC All RESOLVED WONTFIX P2 normal Unsorted 1 annevk annevk hsivonen jsbell mike VYV03354 www-international sideshowbarker+encodingspec oldest_to_newest 99034 0 annevk 2014-01-24 22:31:53 +0000 People writing web-based email applications have found a need for it. I'm not entirely opposed I suppose once there's more interoperability among browsers on the encodings. 99153 1 hsivonen 2014-01-27 12:02:59 +0000 (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