Open raducoravu opened 8 months ago
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
?
It should probably be something like
<ol outputclass="start-3">
The biggest problem for me is that it would not map to standard DITA.
Agreed, but there is also a problem if semantic meaning is lost in the conversion.
I see @outputclass as an extension, because it's not compatible with other DITA tools anymore.
So do I. Probably one of the most useful attributes though :)
For example, does Oxygen support some magic @outputclass value that effectively works like HTML5 @start?
No, but we were pondering about adding one.
<ol outputclass="start-3">
Looks good.
Your Markdown format is invalid for the ordered list numbering to continue.
To ensure your codeblock (or any content) is considered part of 2. it must be indented using 4 spaces
# Title
1. A
2. B
```plain
hello
Markdown syntax allows for auto-number generation, so you should consider using the one
format (re: MD029)
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.