=> Re: "More questions on gemtext parsing" | In: s/Gemini
@mediocregopher I like your interpretation: if any subtype of text (text/gemini being one) can be transmitted with line breaks represented by LF alone, then it means they should be parsed as line breaks as well and not be just merely "transmitted".
The excerpts of the network protocol provided by @sy also support this interpretation.
As for "=>\n" lines, defaulting to text may be the most sensible choice.
Jan 08 · 3 weeks ago
I am willing to publically shame those not using Linux or maybe BSD! Or ignore their backwards propriatary ways.
=> 🌒 s/Gemini
More questions on gemtext parsing — I'm rewriting my gemtext parser and I've landed on questions that I decided to ignore the first time around, but now I really want to solve: 1. All lines beginning with the two characters "=>" are link lines, says the spec, but also is mandatory, so how do we handle a line that is simply "=>\r\n"? 2. What if is not a valid URL or it doesn't have reserved characters encoded? 3. Should single '\n' and '\r' characters be ignored, replaced by a...
=> 💬 lufte · 12 comments · Jan 08 · 3 weeks ago This content has been proxied by September (3851b).Proxy Information
text/gemini; charset=utf-8