3 ms·
> This is because U+FEFF had become a special beacon called the byte order mark, that was placed on the beginning of some UTF-8 files. Shouldn't this be "UTF-1
by flohofwoe 6y ago
> This is because U+FEFF had become a special beacon called the byte order mark, that was placed on the beginning of some UTF-8 files.
Shouldn't this be "UTF-16"? "Byte order" doesn't make sense with UTF-8 encoding, and I've only ever seen BOMs in files created in Windows tools (where UTF-16 is fairly common).
- pjc50 6y agoYeah, UTF-16 or more technically the thing you get if you build a Windows C++ program with "_UNICODE" defined: https://docs.microsoft.com/en-us/windows/win32/learnwin32/working-with-strings https://docs.microsoft.com/en-us/windows/win32/learnwin32/wo...
- mkl 6y agoBoth. It's sometimes used in UTF-8 to indicate that the file is encoded in UTF-8 (and not byte order). Personally, I think that software hiding extra unnecessary invisible stuff in my files is really annoying. Some more info here: https://en.wikipedia.org/wiki/Byte_order_mark https://en.wikipedia.org/wiki/Byte_order_mark