Rick Cameron wrote: > So the original statement was correct. If the file starts with FF FE, it > must be a little-endian encoding; but you can't tell whether it's UTF-16 or > UTF-32.
If you know that it's UTF-16 and you just try to figure out the byte order, then FF FE is unambiguous. If you look for any Unicode signature, then you look for FF FE 00 00 (UTF-32LE) before you check for FF FE (UTF-16LE). markus
