You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not clear to me how to get a markdown-sourced document to emit this attribute in a way that xml2rfc will respect it.
This came up in the OpenPGP WG's attempt to refresh the cryptographic standards for OpenPGP. See Derek Atkins message which says:
The ToC doesn't include anything beyond x.y.z
This isn't urgent, but insofar as we're looking at revisions to RFC 4880 it'd be nice to be able to compare the document structure by seeing the same level of ToC depth (RFC 4880 has a ToC 4 levels deep).
The text was updated successfully, but these errors were encountered:
The tocDepth attribute changes the default depth of the generated table of contents.
It's not clear to me how to get a markdown-sourced document to emit this attribute in a way that
xml2rfc
will respect it.This came up in the OpenPGP WG's attempt to refresh the cryptographic standards for OpenPGP. See Derek Atkins message which says:
This isn't urgent, but insofar as we're looking at revisions to RFC 4880 it'd be nice to be able to compare the document structure by seeing the same level of ToC depth (RFC 4880 has a ToC 4 levels deep).
The text was updated successfully, but these errors were encountered: