Preferred convention for converting inline links?

[Drew DeVault]

On Fri Oct 23, 2020 at 1:32 PM EDT, jan Niko (Nico) wrote:
> Mine is running arch linux, with a GUI built around sway, waybar, and
> sike. The on-screen keyboard is squeekboard with a custom split layout.
> (if people are interested in the UI setup, I'll make a page for it)
>
> => https://source.puri.sm/Librem5/squeekboard Squeekboard
> => gemini://itwont.work/sike.gmi sike

I prefer this approach. Sometimes if I have a lot of references, I'll
make use of unicode superscript numerals to prepare a list of footnotes:

https://en.wikipedia.org/wiki/Unicode_subscripts_and_superscripts#Superscripts_and_subscripts_block

However, in general, I avoid numbered links, because many clients assign
a number to each link for keyboard shortcuts and ease of use, and if my
numbering doesn't line up it could lead to confusion.

But also, as a general rule, I don't do automated conversions of
non-Gemini content to Gemtext. Instead, I manually reformat it as
Gemtext so that I can use editorial descretion to adjust the content to
better express itself in the conventions of the new medium.