💾 Archived View for rawtext.club › ~sloum › geminilist › 007294.gmi captured on 2024-02-05 at 10:47:15. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Robert "khuxkm" Miles khuxkm at tilde.team
Tue Oct 12 21:27:00 BST 2021
- - - - - - - - - - - - - - - - - - -
October 11, 2021 10:44 AM, "Alan Bunbury" <gemini at bunburya.eu> wrote:
In truth I'm not sure in what circumstances a "---" text line would be intended as something other
than a separator, but I'm sure other authors are more imaginative than I am. To take another
example, I have regularly encountered situations where a single * in a markdown document is
incorrectly interpreted as marking the beginning of italicised text, so the rest of the document is
italicised inappropriately. I'd like for that not to become commonplace in Geminispace.
I fail to see how replacing a line that has only `---` on it with a graphical separator is anything like the runaway italics thing you mentioned. Still, I can kind of see where you're going with that.
Separately, on the whitespace issue, I do think it would be helpful to clarify in the spec whether
whitespace is mandatory, particularly for headers. For example, should the line "#### Hello" be
interpreted as (i) a level 3 header whose text is "# Hello", or (ii) a text line whose text is
"#### Hello"? AFAIK that is ambiguous unless there is a clear stance on mandatory whitespace in the
spec.
That is not ambiguous, with or without mandatory whitespace. As Plain Text pointed out, the max amount of characters used to determine the linetype is the first 3, per 5.3 in the gemtext spec (awkwardly numbered because it was originally part of the protocol spec):
It is possible to unambiguously determine a line's type purely by inspecting its first three characters.
Therefore, any (good) client will see that the first 3 characters of the line are "###" and correctly call it what it is: a level 3 header with the text "# Hello". I fail to see how that would be ambiguous (I guess the spec doesn't do *that* good of a job explaining it, but I would think you could catch on by the fact that the section on header lines only gives examples of #, ##, and ###).
Just my two cents,Robert "khuxkm" Miles