💾 Archived View for rawtext.club › ~sloum › geminilist › 006917.gmi captured on 2023-09-28 at 16:36:20. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
skyjake skyjake at dengine.net
Wed Jul 14 06:34:08 BST 2021
- - - - - - - - - - - - - - - - - - -
On 14. Jul 21, at 2.30, Jason McBrayer <jmcbray at carcosa.net> wrote:
The BOM at the start of the file is invalid for UTF-8 documents. I
*think* it's required for UTF-16, but I may be wrong and I'm too tired
to look it up.
BOM is not invalid for UTF-8, although it has limited usefulness:
UTF-8 can contain a BOM. However, it makes no difference as to the endianness of the byte stream. UTF-8 always has the same byte order. An initial BOM is only used as a signature — an indication that an otherwise unmarked text file is in UTF-8.
=
https://www.unicode.org/faq/utf_bom.html#bom1
I recommend this FAQ to anyone wondering about what to do with BOMs, there's plenty of good info.
--jaakko