💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › stunar$lvl$1@gioia.aioe.or… captured on 2024-08-31 at 12:37:15. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-04-28)
-=-=-=-=-=-=-
From: David <david@arch.invalid>
Subject: Re: Problem with ``` in Gemini
Date: Tue, 8 Feb 2022 22:28:59 +0100
Message-ID: <stunar$lvl$1@gioia.aioe.org>
On 08/02/2022 21:14, news@zzo38computer.org.invalid wrote:
Something that I think is a flaw in the Gemini specification is that it
cannot make a preformatting block containing a line with ``` at first.
One way to fix this is to allow preformatting starting with more than
three back ticks and if so then the end also has the same number of back
ticks
Nice catch. This issue also isn't yet covered in the discussion of the
BNF. I like your proposition of using more ticks when needed (similar to
CommonMark). It would mean to loosen the spec, though:
| It is possible to unambiguously determine a line's type purely by
inspecting its first three characters.
Thus, from a practical point of view, my personal approach would be to
work around in editing and indent the whole preformatted text by a fixed
set of spaces (and mention this in the alt-text).
Alternatively offer the preformatted content as an extra text/plain file
or the whole content in a different format, altogether.
As an aside: Should gemtext support its line types within > quote lines?
Again, personally, I'd prefer sticking to the "first three char" rule.
Cheers
Refs
(NB: XML CDATA sections work around ]]> by closing and reopening.)
Parent:
Problem with ``` in Gemini (by news@zzo38computer.org.invalid on Tue, 08 Feb 2022 12:14:50 -0800)