BBS:      TELESC.NET.BR
Assunto:  Re: MARKUP message quoting - draft 5
De:       Matthew Asham
Data:     Fri, 13 Mar 2026 11:51:36 -0700
-----------------------------------------------------------
I sent the draft to the FTSC coordinator this morning.

And then realized quoting needed to be addressed.  I've now added section 4.5 to the draft to document how reply quoting can work (otherwise it looks funky).

Now on Draft 5.  Updated https://github.com/awehttam/binkterm-php/issues/161


4.5 Reply Quoting

When replying to a message declared with the MARKUP kludge, software
SHOULD preserve the original source structure as much as practical.

Software SHOULD NOT mechanically convert the entire original body into
legacy inline quote prefixes if doing so would damage the structure or
readability of the declared markup syntax.

For line-oriented or block-oriented formats such as Markdown and
Gemtext, software SHOULD prefer quoting mechanisms native to that
format.

For Markdown specifically, implementations SHOULD prefer enclosing the
original body in a Markdown blockquote while keeping any reply
attribution line outside the quoted block.

Example:

    On 13 Mar 2026, Jane Doe wrote:

    > # Heading
    >
    > - item one
    > - item two
    >
    > ```text
    > code block
    > ```

This approach improves round-trip fidelity for marked-up replies while
remaining readable in plain-text environments.

... The boxes are talking to each other again

--- BinktermPHP v1.8.6
 * Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)

-----------------------------------------------------------
[Voltar]