💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › 87r18f3r12.fsf@news.geriks… captured on 2022-04-29 at 11:35:04. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

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

Re: Gemini markup extensions [Was: Re: a solution for emphasis]

Message headers

From: Gustaf Erikson <gerikson@gmial.com>

Subject: Re: Gemini markup extensions [Was: Re: a solution for emphasis]

Date: Mon, 07 Feb 2022 11:33:13 +0100

Message-ID: <87r18f3r12.fsf@news.gerikson.com>

Message content

Luca Saiu <luca@ageinghacker.net> writes:

On 2022-02-05 at 00:13 +0100, Gustaf Erikson wrote, mostly in
gemini://gerikson.com/gemlog/gemini-sux/e-m-p-h-a-s-i-s.gmi :

[long interesting discussion snipped]

Thanks for taking the time to read my post and reply!

Please note however, that I am not proposing a *specification* change,

merely that enough clients recognize the "*"/"_" convention to enable a

writer to be relatively confident that they can use this "markup" as

intended.

I think that Gemini as it stands is a worse fit for technical writing
than for free-flow text.

I agree. To be fair, it's not meant to be all-encompassing.

Cheers,

/g.

--

.sig goes here

Related

Parent:

Gemini markup extensions [Was: Re: a solution for emphasis] (by Luca Saiu <luca@ageinghacker.net> on Mon, 07 Feb 2022 01:36:55 +0100)

Start of thread:

a solution for emphasis (by Gustaf Erikson <gerikson@gmial.com> on Sat, 05 Feb 2022 00:13:15 +0100)

Children:

Re: Gemini markup extensions [Was: Re: a solution for emphasis] (by Martin <martin@datapulp.de> on Tue, 8 Feb 2022 08:10:56 +0100)