💾 Archived View for rawtext.club › ~sloum › geminilist › 006866.gmi captured on 2024-02-05 at 10:55:10. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
mbays mbays at sdf.org
Thu Jul 8 12:12:02 BST 2021
- - - - - - - - - - - - - - - - - - -
[BOM]
Submitted to GitLab:
=
https://gitlab.com/gemini-specification/protocol/-/issues/36
From that issue:
1. The server MUST remove the BOM when serving UTF-8 content that
begins with a BOM.
One thing to consider is that a zero width space could be used at the start of a line as a quoting mechanism. It isn't a nice solution to gemtext's quoting problem, but there doesn't seem to be a nice solution. So then even if U+FEFF is the "wrong" zero width space character to use, it might be used, and then it would be strange for it to work for any but the first line. So this suggests we should follow RFC 3629 when it says 'When a protocol forbids use of U+FEFF as a signature for a certain protocol element, then any initial U+FEFF in that protocol element MUST be interpreted as a "ZERO WIDTH NO-BREAK SPACE".'-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 195 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210708/48f62a67/attachment.sig>