💾 Archived View for bbs.geminispace.org › s › Lagrange › 22294 captured on 2024-12-17 at 15:09:08. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
@skyjake Why does Lagrange normalize spacing in gemtext?
The spec mentions this is up to the client. I'm curious what went into your decision here to remove tabs, etc
Nov 28 · 3 weeks ago
🕹️ skyjake [mod...] · Nov 28 at 10:36:
It ensures a uniform presentation of paragraphs. Sometimes people like to use two spaces after a sentence, for example. Keeping things uniform makes it easier to adapt the presentation to different displays, fonts, themes, etc. It also removes the possibilty to apply preformatting outside preformatted blocks, like indentations that one might want to use in lists to make them multi-level. This kind of creative expansions of Gemtext should be discouraged.
Tabs are a bit of a special case. Lagrange does try to maintain some tab stops and jump to those when it encounters a tab character (outside preformatted blocks, that is) but I can't recall if that code is currently working correctly or not.
In theory at least, tabs could be used to create tabular arrangements outside preformatted blocks, but these should be avoided because they break down when the line width gets too narrow.
A secret pro tip: Lagrange does not normalize all Unicode spaces. If you really want to, you can experiment with nonbreaking spaces and other specialized Unicode spaces, but it's probably not a great idea if you want your content to be correctly displayed everywhere.
Two spaces after a full stop is the gift that typewriters will never stop giving.
I do 2 spaces after a fullstop, but that's because my typewriting teacher made a big yelling point to always do 2 spaces after a fullstop.
Yep. That stupid rule which never existed in professional typesetting is one of the eternal gifts left to us by monospace typewriters, much like QWERTY layout, designed specifically to handicap typing speed so keys would not jam.