James Hewitt
James Hewitt
> What's the rational behind dita -> dita-html change? The same output was used to check the tests for html and markdown transforms, and with this change they are different....
Do I just use a Java property of my own invention? `org.lwdita.markdown-shortdescs`?
The ditaot params don't seem to be available as Java system properties, and the [docs](https://www.dita-ot.org/dev/topics/plugin-configfile.html) only mention being able to add ``s to `transtype` not `parser`, so any help on...
It occurs to me the other option would be to add a flag to the yaml block at the top - would that fit with the model? I was wondering...
@jelovirt any help here?
In our doc, we try and favour mdita as the format, but where we need l3 headers or anchors, we use markdown instead and have to copy the short description...