Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

__xxx__ not interpreted as markdown when xxx begins with a non-word character (e.g. __-1__) (Origin: bugzilla #772574) #6084

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.12 on platform Other
Assigned to: Dimitri van Heesch

On 2016-10-07 15:31:32 +0000, Hayo Baan wrote:

When you use xxx markdown to emphasise xxx this works fine. Except when xxx starts with a non-word character. For instance -1 doesn't get translated into -1 in the html output, but stays -1 (the same goes for e.g. -1).

A workaround is to use -1 in the source code, but it would be nice if the markdown versions would work too.

On 2016-10-17 19:50:32 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2016-12-29 18:45:39 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.13. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.