💾 Archived View for rawtext.club › ~sloum › geminilist › 005663.gmi captured on 2023-09-08 at 17:16:01. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Fri Feb 26 05:31:20 GMT 2021
- - - - - - - - - - - - - - - - - - -
It was thus said that the Great John Cowan once stated:
On Thu, Feb 25, 2021 at 5:25 PM Sean Conner <sean at conman.org> wrote:
tag = '@art' / '@code' / '@data' / '@poem'
We now know what the benefit of @art is. What are the advantages of the
other three over no tag?
A client could style each type differently, even if just a subtle changein background color. Or even different monospaced fonts depending uponusage.
``` @code
x = 5
```
Shouldn't this be read as if it were "ex equals five"?
I didn't want to get too wild with the examples, but yes, that sounds fineto me.
``` @art Obligatory Cat picture
cat
```
Right.
Didn't want to bother trying to draw an ASCII cat.
``` @data Price list
widget 3.45
gadget 5.99
fob 1.99
```
Shouldn't this be read as "widget one ninety-nine (pause) gadget five
ninety-nine (pause) fob one ninety-nine"?
It could even be "Row one widget one ninety-nine (pause) row two gadgetfive ninety-nine (pause) row three fob one ninety-nine" but I can see therepeated "row x" could get tiresome.
How might a visual browser
render it differently? How about alternating light and dark background for each row? I mean, itdoesn't have to be a jarring contrast like black background/whitebackground, but black background/dark grey background, just to help visuallyseparate the records.
``` @poem
There once was a person from Nantucket ...
```
How might a visual browser render this differently?
No idea on this one, but a screen reader, in theory, could switch voicesfor reading poetry.
I don't expect this to be standardized any time soon in the spec, as thespec for text/gemini is line oriented and less with parsing the data in eachline. But I can certainly see this as something clients slowly converge on,much like gopher clients supporting selector types not specified inRFC-1436.
And the spec does say, "MAY be interpreted ... "
-spc