A proposed scheme for parsing preformatted alt text

[Nathan Galt]

> On Sep 11, 2020, at 12:44 AM, Sean Conner <sean at conman.org> wrote:
> 
> It was thus said that the Great Nathan Galt once stated:
>> 
>>> On Sep 10, 2020, at 5:30 PM, Sean Conner <sean at conman.org> wrote:
>>> 
>>> I added the following non-standard document:
>>> 
>>> 	gemini://gemini.conman.org/test/preformat.gemini
>>> 
>>> that contains "machine readable text" at the opening preformatted marker,
>>> and a "human readable text" on the ending preformatted marker, just to give
>>> an indication of what it might look like and what might be done with it. 
>>> Enough talk, *someone* has to do an implementation to scare the bejeezus out
>>> of everyone (not that it's particularly scary in what I did).
>>> 
>>> -spc (HTML people.  Seriously, HTML.  You want your format, you have it
>>> 	already ... )
>> 
>> I like sets of concrete examples. Thanks for whipping this up.
>> 
>> What I dislike about this style of “‘machine-readable’ text up top” (for
>> some definition of “machine-readable”) is that the alt-text function has
>> been entirely obliterated, at least in these examples.
>> 
>> For the two code bits at the top of the page, the alt text should be the
>> contents of the captions at the bottom of each.
>> 
>> For the three “images”, the alt-text should be something like:
>> 
>> - a dragon
>> - Merry Christmas
>> - a Christmas tree with a rabbit sitting near its base
> 
>  Okay, check out
> 
> 	gemini://gemini.conman.org/test/preformat-2.gemini
> 
>  -spc (Taking away my fun with the alt-text ... )

Much better.

I don’t know if “image” before the ASCII-art images is, or would be, useful to anything.

It seems a little weird to see “ code Lua” instead of “lua”, and I don’t know how easy it would be to adjust syntax-coloring libraries to account for this, but this nitpick is largely immaterial.

Like with the last one, thanks for making a concrete example.