cabo

> ``` > nested-ordered-types: 1 a i A I > ``` Those types can contain spaces, so a space-separated list won't work too well. Probably needs to be > nested-ordered-types:...

OK, implementation-wise your number 1 (see what I did here :-) seems easiest. It is also probably easiest to roll through the array, i.e., putting the shifted off current value...

On 19. Apr 2024, at 19:33, Paul Hoffman ***@***.***> wrote: > > Is there a reason why we're not trying to follow what would happen from CommonMark? Yes. Kramdown-rfc is...

I have written the code, but https://github.com/ietf-tools/xml2rfc/issues/1122 Will push this anyway after some more testing.

Now in 1.7.9: 1.7.9 Add option nested_ol_types Set globally in `{::options nested_ol_types="1, i, a" /}` (markdown, not YAML header) or for a single

1.7.10 now also takes nested_ol_types from YAML kramdown_options As in ``` kramdown_options: nested_ol_types: 1, i, a ``` (overridden by ::options and by pseudo-attribute on

1.7.11 now also takes an option ol_start_at_first_marker As in ``` kramdown_options: ol_start_at_first_marker: true ``` Default: false (for kramdown-rfc backward compatibility) If `true`, an ordered list (`

I think the recent changes should address both the original observation and the discussion, so please close this if this works for you. https://github.com/ietf-tools/xml2rfc/issues/1122 remains though, for now.

Nice -- a solution is on its way in https://github.com/ietf-tools/xml2rfc/pull/1123 (If you don't need uppercase roman numerals, everything else appears to work.)

Right, `certified` is abandonware; it would be trivial to fork it and make a Ruby 3.0 compatible version. Whether you need `certified` or not depends on how Ruby was installed...