[spec] Ambiguity with regards to quote lines

ew.gemini ew.gemini at nassur.net
Sun Jan 3 19:01:28 GMT 2021
Hello Alex,


alex wennerberg writes:

> Hi all --
>
> I noticed there may be a bit of ambiguity in the spec:
>
>> Lines beginning with ">" are quote lines.  This line type exists so
>> that advanced clients may use distinct styling to convey to readers the
>> important semantic information that certain text is being quoted from
>> an external source.  For example, when wrapping long lines to the the
>> viewport, each resultant line may have a ">" symbol placed at the front.
>
> What isn't clear is whether subsequent quote lines ought to be
> considered as part of the same quote block, ie, say my client surrounds
> quotations with " marks. Should these marks surround each line, or
> surround an entire block of subsequent quote lines?
>
> The clients that I tested did the latter, and this seems intuitively
> correct, but the spec doesn't make this explicit.
>
> Let me know what you all think.

See section 5.4 of the spec.
Section 5.4.1

> In order to take full advantage of this method of text formatting, authors of
> text/gemini content SHOULD avoid hard-wrapping to a specific fixed width, in
> contrast to the convention in Gopherspace where text is typically wrapped at 80
> characters or fewer.  Instead, text which should be displayed as a contiguous
> block should be written as a single long line.

=> gemini://gemini.circumlunar.space/docs/specification.gmi


A line is "one" line. So "one line" starting with ">" and
optional space is a quote and is rendered as one block.
Email type quotes with ">" on every line, happen to be
subsequent blocks in gemini layout.

At least that is what I understand.

Cheers,
~ew

>
> All the best,
>
> Alex


-- 
Keep it simple!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 861 bytes
Desc: not available
URL: <https://mailing-list-archive.gemi.dev/www/attachments/20210103/a48f6af8/attachment.sig>


Archive home | About this archive