Re: [whatwg/encoding] Additional UTF-8 and UTF-16 labels (#168)

Were these labels from WebKit itself or just things that ICU happened to support? That is, is there some chain of evidence connecting these to the Web?

> csunicode
> iso-10646-ucs-2

These two were UTF-16BE in pre-Encoding Standard Gecko and was restored for Thunderbird 60.4 without evidence of necessity (as a side effect of restoring some email-necessary stuff).

The comments in the [Thunderbird amendments](https://searchfox.org/comm-central/source/mailnews/intl/charsetalias.properties) to encoding labels might be of interest. That list is a mixed bag of ancient Gecko-supported labels that didn't make it to the Encoding Standard plus more recently-added labels motivated by JavaMail and legacy Apple Mail compat. Some of the labels that have been on the list for a long time were motivated by compat with Sun CDE dtmail circa 2002 and Solaris ns_langinfo (at a time when when Gecko put aliases needed for interfacing with OS APIs on the same list as aliases for making sense of data received from the network).

For items other than csunicode and iso-10646-ucs-2, I'd like to see some research into which ones IE supported. Off the top of my head, I think unicode and unicodeFFFE are IE-supported.

I'm not particularly convinced that labels for UTF-16BE and UTF-16LE actually matter, given the BOM. Also, I'm skeptical of the utility of these particular UTF-8 labels. Absent any evidence of usage on the Web, it seems rather ad hoc to add these without adding csutf8 from the IANA.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/168#issuecomment-447299560