EUC-TW is a rare Traditional Chinese encoding. (Big5 is the more common legacy encoding.)
The Web is not affected: We already are not exposing EUC-TW to the Web. Mac, Android and B2G are not affected (except in terms of libxul becoming smaller): nsIPlatformCharset is always UTF-8 there. Windows is not affected (except in terms of libxul becoming smaller): nsIPlatformCharset for Traditional Chinese is either Big5 or Big5-HKSCS there. Gtk *nix systems whose locale is not Traditional Chinese are not affected (except in terms of libxul becoming smaller). Gtk *nix systems whose locale is Traditional Chinese but whose locale encoding is UTF-8 or Big5 are not affected. File system access is not affected. For historical reasons unclear to me, Unix file system code doesn't actually use nsIPlatformCharset. However, I think file: URL directory listings will be affected. On Gtk *nix systems with an EUC-TW locale, localized date (month name, weekday name) formatting will be affected. It seems to me that X clipboard handling for non-UTF-8 text is already broken, so we don't *really* support non-UTF-8 *nix locales anyway. Indications in our code base suggest that EUC-TW support has mainly been a Solaris and AIX thing. Also, it appears that Red Hat 7 had it as an option. Red Hat 8, released in 2002, defaulted to UTF-8. On the Debian side, UTF-8 has been the default since 2007. As far as I was able to find instructions for using Traditional Chinese on Debian before that, it appears that Debian used Big5 before moving to UTF-8. It's imaginable that some organization might have a Solaris/AIX-influenced NFS system that's been up and running using EUC-TW for more than 15 years and, therefore, still have Linux or Solaris systems configured with an EUC-TW locale. Other than that, it seems very improbable that anyone would use an EUC-TW system locale these days. Unfortunately, I missed EUC-TW when I added telemetry for encodings that we'd want to remove. EUC-TW is the only (non-OS/2) nsIPlatformCharset that's not in the Encoding Standard and not exposed to the Web. Removing all support for EUC-TW allows us to use the Web-oriented encoding label handling internally for all things and allows us to get rid of the lookup tables that and to the size of libxul. This does not affect Thunderbird's ability to continue to support EUC-TW if the Thunderbird developers so choose. (But EUC-TW email seems improbable, since no one has bothered to register an IANA label for it.) P.S. If your module uses nsIPlatformCharset, please stop using it! All our platform have UTF-16 (Windows) or UTF-8 (other) APIs these days. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
