On Wed, Feb 5, 2020 at 4:22 AM solderpunk <solderpunk at sdf.org> wrote: > As far as I see it, the main arguments in favour of a preformatted block > concept now are: > > 1. The ability to include text/gemini syntax without it actually being > rendered by the client, so Gemini can be discussed/taught over > Gemini. > 2. The ability to insist that some content (e.g. source code, ASCII > art), be rendered in a monospace font, even by graphical clients > which might display text in a variable width font by default. I would like to tack on another argument in favor of the ``` blocks that I think is still valid after the recent changes. 3. The ability for GUI clients to display preformatted text blocks in a container with horizontal scrolling. To see exactly what I mean by this, try opening this page on a mobile browser [0]. The page banner is ASCII art which can be scrolled left and right using your thumb. The rest of the text on the page is wrapped to fit the screen. This is the type of interface that I envision gemini GUI clients evolving to support. For gemini clients that choose to implement it, it would give them an escape hatch from this section of the spec: > Authors who insist on hard-wrapping their content MUST be aware that > the content will display neatly on clients whose display device is as > wide as the hard-wrapped length or wider, but will appear with > irregular line widths on narrower clients. [0] https://github.com/michael-lazar/hn-gopher/blob/master/README.md - mozz
---
Previous in thread (1 of 6): 🗣️ solderpunk (solderpunk (a) SDF.ORG)
Next in thread (3 of 6): 🗣️ Sean Conner (sean (a) conman.org)