We have a concept of platform charset that goes back to pre-NT Windows, Mac OS Classic, OS/2 and pre-UTF-8 *nix platforms. This concept gets in the way of doCOMtaminating old code to use only new facilities in mozilla::dom::EncodingUtils.
These days, on Mac and Android, we say the platform charset is always UTF-8. On Windows, it seems that we access various system resources through post-NT Unicode APIs, but we still try to use a locale-affiliated legacy encoding for Save As *content*, for the old times' sake. On *nix platforms, it's not clear to me what exactly the platform charset is used for these days. An MXR search turns up surprisingly little. On OS/2, it seems the platform charset is always one of several non-UTF-8 encodings. Questions: * On Windows, do we really need to pay homage to the pre-NT legacy when doing Save As? How about we just use UTF-8 for "HTML Page, complete" reserialization like on Mac? * Is the OS/2 port still alive and supported as an in-tree port? The latest releases I've seen are 10.x ESR. * Do we (or gtk) really still support non-UTF-8 platform charset values on *nix? (MXR turns up so little that it makes me wonder non-UTF-8 support might have already gone away for practical purposes.) * If we do, we want to / need to support *nix variants with an encoding other than UTF-8 as the system encoding? * If the previous question needs telemetry to answer, do we even get telemetry from distro Linux builds, from Solaris builds or from *BSD builds? (Are there other *nix ports alive?) * If we do need to support non-UTF-8 system encodings, do we need to support EUC-TW? For Solaris maybe? Out of the encodings that have appeared as past *nix system encodings, it's the one that we wouldn't need to keep code for Web-motivated reasons. -- Henri Sivonen hsivo...@hsivonen.fi http://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
