💾 Archived View for idiomdrottning.org › re-parsing-preformatted-alt-text captured on 2024-08-31 at 14:27:41. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-02-05)

-=-=-=-=-=-=-

RE: A proposed scheme for parsing preformatted alt text

Uh I get so overwhelmed with all the gem text language extentions, lukee :/

(Re your post your marmaladefoo gemspace.)

Ah, now I’m reading bouncepaw’s post for context

I’ve been using md2gemini’s unicode table output, I think it looks good. Not sure how it sounds for audio browsers; the intent is that you’ll hear each row read off ltr before moving down to the next row, just as text but with weird punctuation.

Org-mode has the feature you’re proposing for its code blocks.

Which was one of the reasons I switched to markdown because I got overwhelmed with the complexity.

My gmi files do throw away a lot of semantic markup but that’s because gmi is a simpler format by design.

Gem text should not be the ultimate source format for your semantic, multi-platform data, like stuff you’re gonna publish in books for example. Feel free to write in gemtext directly for simple things like blog posts♥︎ but for more complicated stuff, like hypertext info manuals for example, or novels, it’s better used as a generated output format than as the source format. Just like how you might export to PDF; those PDFs don’t have all the semantic information left in them.

As an example, /line-moving-semantics compared to gemini://idiomdrottning.org/line-moving-semantics.gmi The former has bold sections, italic sections, mono space sections. Neither are essential to comprehend the text.

People go on gemspace because they want simple.

ASCII art is not text, and inline in gem files isn’t necessarily the best place for these type of art works.

I am not trying to discourage people from making content that is accessible to those with impaired vision.

ASCII art is images and belong in separate files just like images do, with a description in the link text.

TL;DR: Keep gemtext simple. Please put non-text in separate files, like data stuff in TSV files and ASCII art in separate text files.

Luke’s post Bouncepaw’s post

Luke’s post

Bouncepaw’s post

Update

Talking to peeps on the IRC about this, I have some crow to eat because I didn’t even know about the alt texts in the first place! I thought even adding alt texts was an extension.

Now I’ve updated my old posts adding non-codified alt texts as per Tomasino’s recommendation.