Re: [USER] Weird Title Rendering on Various Clients



> I checked how Lagrange handles the Byte Order Mark (BOM), and sure 
enough it breaks the first line's type detection.

If we follow section 6 of RFC 3629, it looks like the right thing to do is 
to interpret this character as a nonbreaking space, even if it is the 
first character of the utf8-encoded gemtext. So then the first line should 
be interpreted as a text line.

Another thing to clarify in the next version of the spec.

"""
A protocol SHOULD forbid use of U+FEFF as a signature for those textual 
protocol elements that the protocol mandates to be always UTF-8, the 
signature function being totally useless in those cases.

A protocol SHOULD also forbid use of U+FEFF as a signature for those 
textual protocol elements for which the protocol provides character 
encoding identification mechanisms, when it is expected that 
implementations of the protocol will be in a position to always use the 
mechanisms properly.  This will be the case when the protocol elements are 
maintained tightly under the control of the implementation from the time 
of their creation to the time of their (properly labeled) transmission.

[...]

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".
"""

---

Previous in thread (7 of 13): 🗣️ Jonathan McHugh (indieterminacy (a) libre.brussels)

Next in thread (9 of 13): 🗣️ Andrew Singleton (singletona082 (a) gmail.com)

View entire thread.