On 30/12/20 01:04, Grant Edwards wrote: > You must be talking about some sort of weird "wide" encoding (is there > such a thing as UTF-16?). I've never seen a file like that. Everybody > and everything uses UTF-8 these days and has for years. UTF-8 is a > superset of ASCII, and doesn't increase size of the file unless > non-ascii characters are used. Converting an ASCII file to UTF-8 > encoding is a noop. An ASCII file _is_ UTF-8.
There is utf-16 - MS's default version. They wrote their unicode support *before* utf-8 really was a thing. So we have the nix's settling on an 8-bit char, and MS settling on a 16-bit char BEFORE that. Unbaking that mess would be fun ... So that file is probably something to do with MS and ASCII-16 :-) Cheers, Wol
