cabo
cabo
Hi Wiktor, on 2023-10-10, at 10:21, Wiktor Kwapisiewicz ***@***.***> wrote: > > > Hi, > > I'd like to generate v3 rfc xml and I found that there's --v3 option...
This ticket is proposing a solution but not very specific about the problem. Is the reason for using {::include here that a common value needs to be used in different...
Here is something you can do today: ``` This secret key was generated using provable prime generation found in FIPS186-4 using the seed [^seed-]. [^seed-]: 47110815 ``` A footnote reference...
I'm not sure I understand the process here. kramdown-rfc produces a v2/v3 mongrel RFCXML. Either the author or the RFC editor runs this through xml2rfc --v2v3 to obtain the processable...
With --v3 (which is now default), kramdown-rfc generates mongrel XML that is converted to proper v3 by xml2rfc. Martin Thomson's pipeline does that for you, so you may not have...
Hmm, I see them. We must be doing something different. Do you have a sample I could try?
No problem. Indeed, the redundant attributes are gone. Need to examine more closely.
Seems to have happened between xml2rfc 3.11.1 and xml2rfc 3.12.1. The commit messages aren't very useful, looking at the code now.
"it happened"?
The fix might actually be in lxml or some such.