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
Maybe we could add some kind of outputclass value on the second ol to state that it should start from a certain index, in this way the publishing could be customized to reflect this. Otherwise the information about the initial counter state for the second list is lost in the DITA XML content.
The text was updated successfully, but these errors were encountered:
The biggest problem for me is that it would not map to standard DITA. So it would not be just configuring how Markdown structures are mapped to DITA structures, it would be extending DITA. I see @outputclass as an extension, because it's not compatible with other DITA tools anymore. For example, does Oxygen support some magic @outputclass value that effectively works like HTML5 @start?
I have this Markdown content:
If I were to convert it to HTML, the result HTML would look like this:
so two lists with a pre in between, the second list starts from 3.
The conversion to DITA looks like this:
Maybe we could add some kind of outputclass value on the second ol to state that it should start from a certain index, in this way the publishing could be customized to reflect this. Otherwise the information about the initial counter state for the second list is lost in the DITA XML content.
The text was updated successfully, but these errors were encountered: