Closed IanMayo closed 6 months ago
We have this source content:
<ul> <li>Phase A</li> <li><a href="#">Phase B</a>.</li> <li><a href="#">Phase C</a>.</li> </ul>
This produces this DITA:
<ul> <li>Phase A</li> <li> <xref href="#">Phase B</xref> . </li> <li> <xref href="#">Phase C</xref> . </li> </ul>
Which is exported to this HTML:
Note how the full-stop / period is on a line of its own. This produces this published content:
Note the space between the link and the period.
However, if we cancel the prettify_xml step the content remains structured the same as the original:
prettify_xml
Hmm, we have choices:
prettify
I'm tempted to go for 1., until it frustrates me.
1.
Done, for now.
We have this source content:
This produces this DITA:
Which is exported to this HTML:![image](https://github.com/DeepBlueCLtd/LegacyMan/assets/1108513/ad132553-c13c-4133-9f2a-7cb5a6044634)
Note how the full-stop / period is on a line of its own. This produces this published content:![image](https://github.com/DeepBlueCLtd/LegacyMan/assets/1108513/44d7d0c8-98dd-4860-8bf3-feb796216c34)
Note the space between the link and the period.
However, if we cancel the![image](https://github.com/DeepBlueCLtd/LegacyMan/assets/1108513/5e70d88f-4398-4dd2-904a-5fb96a941acb)
prettify_xml
step the content remains structured the same as the original:Hmm, we have choices:
prettify
with a find/replace that fixes the above issue (it's quite common across the document set)I'm tempted to go for
1.
, until it frustrates me.