Minor hedgedoc / minutes-import disagreement on ```language

[chrysn]

Describe the issue

On a second look at today's CBOR minutes I saw that the hedgedoc import was not 100% correct:

"Source code" in hedgedoc:

```cddl
envelope-content =
    leaf /
    elided /
    node /
    assertion /
    wrapped

leaf = #6.201(any)
```

Rendition in hedgedoc's view mode: pre-formatted, just the content (the cddl wasn't interpreted to really good syntax highlighting, but it was more for the benefit of the readers anyway)

Rendition in the imported notes: There is an extra line after the pre-formatted text: {: .language-cddl}

This is a really small issue, might just as well be fine to just accept it until that markdown part is next updated for other reasons – thanks for already making that import super smooth!

Code of Conduct

• [X] I agree to follow the IETF's Code of Conduct

[cabo]

One problem is that `` is not standard markdown. So the processor might be interpreting this as a code span (foo`), not a code block (which would be

foo

).

[jennifer-richards]

The actual imported file looks like:

## Does a generic "none of the above" tag make sense?   {#does-a-generic-none-of-the-above-tag-make-sense}

dcbor asks for tag, uses it in draft-mcnally-envelope to disambiguate

    envelope-content =
        leaf /
        elided /
        node /
        assertion /
        wrapped

    leaf = #6.201(any)
{: .language-cddl}

CA: Had similar pattern in earlier iterations of CoRAL – generic thing,