Handle XML-escapes in MD sections of nuspec

[glooms]

Hi there, this is a question/feature request.

We encountered a problem when trying to do a release of our tool qlik-cli. The problem was that our release-notes contained something that looked like an XML-tag, in this case <webhookId>. No worries thought I and XML-escaped the trouble-making characters to < and > respectively.

But, now when I look at the release-notes I see that the XML-escaped characters aren't converted back to their proper values. Instead there I see:

qlik webhook edit <webhookId>

How are we supposed to handle these characters so they look nice in descriptions and release-notes? Could they be "unescaped" by the Chocolatey machinery perhaps or is there another way to do this that I've missed?

┆Issue is synchronized with this Gitlab issue by Unito

[AdmiringWorm]

Apologies for not responding to this issue sooner.

Unfortunately at the moment, it is not possible to make the characters < and > look nicely in the description. In the meantime, until we can handle this scenario, I would suggest using double arrows instead as an alternative: « and ».

[pauby]

@st3phhays Can you shed any light on what the options are of fixing this?

[st3phhays]

Without digging into the code, I can think of two solutions:

1. The conversion of markdown to HTML here is handled by Markdig. There may be something in Markdig that we can adjust to accommodate this and other special cases.
2. I could use JavaScript after the fact and replace these characters with the correct ones.

[pauby]

I'd rather option 1 than 2.