💾 Archived View for bbs.geminispace.org › u › devalexwhite › 2025 captured on 2024-06-16 at 19:42:32. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-10)
-=-=-=-=-=-=-
Re: "If I could add one thing to the gemtext spec, it would be a..."
@skyjake yeah I can definitely see that. I was thinking of it from the perspective of a screen reader parsing a gemtext file (as I feel this medium goes hand in hand with accessible content). Everything in the current spec would be worth announcing, but I wasn’t sure an HR would be. Although with your comment example, I could see “<Comment text> <Line break> <Comment text>” being useful information.
2023-06-15 · 1 year ago
👻 mediocregopher [OP...] · 2023-06-15 at 18:01:
I think horizontal rules are useful in the context of written documents, you see them in books frequently as a way of lightly splitting up chapters for example. It's kind of like a sub-header, but without having to name the sub-section.
If I was feeling spicy, I would make the argument that we shouldn't forget about the horizontal rule just because markdown has brainwashed us into thinking that heirarchies are the only way to structure digital written content :P
That said, I'm definitely aware the ship has sailed on this so I'm not really making a proposal. It was more of a one-off thought into the void :)
🚂 octal · 2023-06-15 at 21:56:
I like to think of <hr> as an unnamed header, as @mediocregopher suggests, when it's used to introduce a new scene or topic. In a book, this might be rendered as a line of three stars * * * instead of a solid horizontal line.
Conveniently, if that's your use-case, Gemini Text already has unnamed headers! Just make a header line (#,##,###) and don't put any text in it :)
(your rendering may vary)
❄ freezr · 2023-06-16 at 04:09:
horizontal lines can be achieved through a simple...
____________________
or
••••••••••••••••••••••••••
Isn't perfect but it works...
If I could add one thing to the gemtext spec, it would be a horizontal line rule (like <hr/>). You can do it manually, but you can't know how wide the reader's screen is and if you guess badly it looks weird.