kramdown-rfc
kramdown-rfc copied to clipboard
cabo
An XML2RFC (RFC799x) backend for Thomas Leitner's kramdown markdown parser
## I wish To define keywords that reference specification sections. ``` normative: SEMANTICS: I-D.ietf-httpbis-semantics ... ## Notational Conventions {::boilerplate bcp14-tagged} The definitions of "representation", "selected representation", "representation data" are to...
#170 mentions that manpages are good for Debian, but they are probably good for everybody else as well. Some initial PRs would be appreciated -- I haven't written manpages for...
The RPC seems to be adding the following attributes: * On `section` - `numbered="true" toc="default"` * On `xref` - `format="default"` Could these be added in v3 output (once again, to...
Because `kramdown-rfc` command sets `$options.v3 = true`. `kramdown-rfc -2` thinks both `v2` and `v3` are set and defaults to `v3`. ``` $ kramdown-rfc --version kramdown-rfc2629 1.6.4 $ kramdown-rfc -2 draft-ietf-httpbis-proxy-status.md...
using a DL in markdown produces XML like this: ~~~ xml Name dns_timeout Description The intermediary encountered a timeout when trying to find an IP address for the next hop...
The following reference style: ~~~ {{Sections 1.2 and 3.4 of RFC1234}} ~~~ ... works for external references, but not for internal references, e.g.: ~~~ {{Sections foo and bar}} ~~~ which...
https://github.com/mnot/I-D/blob/main/draft-nottingham-http-structure-retrofit.md appears to be a counter-example; `home` points to the repo, `repo` points to the issues (but gets the boilerplate about "source"). `github-issue-label` is a great idea that needs to...
PR #110 was an attempt to address this, but let's keep this as a broader issue.
The current mechanism for artwork-{txt,svg}-options (1.5.14) assumes that any default options can be overridden by giving the option again. This is not true universally, certainly not for tex2svg. We could...