cabo
cabo
Fixed in 1.0.42. Waiting with an IEEE change for resolution on the bibxml2/bibxml6 issue, though: https://mailarchive.ietf.org/arch/msg/tools-discuss/alTkjTZaPVdPgcpQsqgq4Jm2QfU The IANA mechanism doesn't quite work for me, see https://mailarchive.ietf.org/arch/msg/tools-discuss/M59AKBoaS-9jft3TyP9RLwv_uug
kramdown-rfc 1.1.0 has a fix for the bug in the DOI references generator. That should make bibxml7 more stable once the update has percolated to the relevant servers. It also...
The date issue in the IANA references has been fixed on the xml2rfc.ietf.org server in the runup to IETF98. Only the bibxml2 vs. bibxml6 issue for IEEE remains to be...
There are two somewhat conflicting potential directions of improvement: * Persistent connections (reuse connection for sequential retrievals) * Parallel connections (don't wait for a single retrieval to complete until the...
I hacked something together as aa0ef89, with only rough testing so far. Anecdotically reduces fetch time in one of my drafts from 6.5 to 4 s, so it's not a...
I think the remaining step is to make this the default.
A little bit of sleuthing around in different platform versions needed.
I don't know what "this version" is above. The message is a warning, kramdown-rfc will continue, just slower. To even get this message you must have set `KRAMDOWN_PERSISTENT` in your...
It is not the default -- you have to set the environment variable. It cannot be the default as long as we still support the Ruby 2.3 version installed on...
At least, I have to fix the warning message.