search

cabo / kramdown-rfc

An XML2RFC (RFC799x) backend for Thomas Leitner's kramdown markdown parser
MIT License
195 stars 83 forks source link

Produce blockquote elements #169

Closed martinthomson closed 2 years ago

martinthomson commented 2 years ago

This empty list thing isn't necessary any more. https://datatracker.ietf.org/doc/html/rfc7991#section-2.10

This respects the override with the 'gi' attribute still.

cabo commented 2 years ago

Markdown blockquotes are currently used for

-- indented blocks (ul/empty in v3), default -- v3 block quotes, via {:quote} -- v3 asides, via {:aside}

(Please see https://github.com/cabo/kramdown-rfc/wiki/Syntax#the-yaml-header and scroll up a slight bit to see the examples.)

This PR essentially removes the capability to do the first and makes the second the default.

I don't agree with that at all.

First of all, there is a certain level (*) of promise that rfc-markdown stays stable, so you can unpack your dusty decks and still get the desired output, even through the caprioles RFCXML may take. Replacing the subtle indented block by v3's heavy blockquotes is a significant flag-day change.

Second, ul/empty may be less important than the equivalent was in v2, but it still is the preferred way to format indented blocks. So I think the capability should stay, and the default mapping to these is entirely justified.

Do you really use the RFCXML blockquote element that much that the default mapping bothers you?

(*) Can't help against incompatible changes like <tt in 3.10.0.

martinthomson commented 2 years ago

Fair enough. I had expected that the goal was preservation of the semantic (for which ul/empty is meaningless), but I can use {:quote}.