When using ``` syntax, it's common to ensure syntax highlighting by explicitly declaring the language for blocks with code snippets. This is caught by variouslinters.
However, when specifying a language, this triggers Pandoc's syntax highlighting support, which the LaTeX template used currently doesn't support, due to not porting over some the LaTeX modules used for this support.
As a result, the following example works fine:
caSigningNonce ATTRIBUTE ::= {
WITH SYNTAX OCTET STRING
EQUALITY MATCHING RULE octetStringMatch
SINGLE VALUE TRUE
ID { cabf-caSigningNonce }
}
But the following causes a failure to generate a PDF (when instead, it should succeed)
```asn1
caSigningNonce ATTRIBUTE ::= {
WITH SYNTAX OCTET STRING
EQUALITY MATCHING RULE octetStringMatch
SINGLE VALUE TRUE
ID { cabf-caSigningNonce }
}
When using ``` syntax, it's common to ensure syntax highlighting by explicitly declaring the language for blocks with code snippets. This is caught by various linters.
However, when specifying a language, this triggers Pandoc's syntax highlighting support, which the LaTeX template used currently doesn't support, due to not porting over some the LaTeX modules used for this support.
As a result, the following example works fine:
caSigningNonce ATTRIBUTE ::= { WITH SYNTAX OCTET STRING EQUALITY MATCHING RULE octetStringMatch SINGLE VALUE TRUE ID { cabf-caSigningNonce } }
But the following causes a failure to generate a PDF (when instead, it should succeed)