The upstream source comments are not quite strict at using `*`s,
`<`s or `>`s. These characters, when not enclosed in backtiqs, are
interpreted as Markdown emphasize markers or HTML tags.
Hacking the generator code is not the right solution. We should
attempt to fix them in the source code instead.
Before that, let's keep fixing the generated outputs manually.
There are limitations in the generator when parsing ambiguous strings
such as `*`, `<` etc. `*` is used in Markdown for emphasis, but some
comments are using the literal '*' without properly escaping it.
`<` and `>` are not allowed in Markdown parser. The generated content
for this is at best some warning strings.
This PR fixes this issue manually.
An ideal fix would be proposed to the upstream source code wherever
these happen.