GNOME Bugzilla – Bug 683115
Command ignored when using umlauts in markdown
Last modified: 2014-04-21 12:05:24 UTC
Hello! OS: Debian 6.0.5 Doxygen Version 1.8.2 (backport from Debian experimental) Given following markdown file (remove line numbers): 1 Test {#test_review} 2 ==== 3 4 - Application Management Tool: 5 /*cö*/: 6 7 8 \review Markus: Does this work?? -d Markdown will output: ======== Markdown ========= ---- input ------- - Application Management Tool: /*cö*/: \review Markus: Does this work?? ---- output ----- - Application Management Tool: /*cö*/: \review Markus: Does this work?? --------- And the \review will not be added in the final output. The text "Markus: Does this work??" is however added. Without the /*cö*/ (Removing line 5): -d Markdown will output: ---- input ------- Markus: Does this work?? ---- output ----- Markus: Does this work?? --------- and the command \review works as expected. \review is defined as: ALIASES = "review=\xrefitem review \"Review\" \"List of Reviews\""
With version 1.8.2 we get the warning message: warning: Found unknown command `\review' and the output looks like: . Application Management Tool: /*cö*/: Markus: Does this work?? With version 1.8.6 the warning message is gone and the output looks like: . Application Management Tool: /*cö: Review: Markus: Does this work?? Both in test_review.html. Note: - in 1.8.6 the */ is missing - I've converted the input file to UTF-8 so the ö is handled better (instead of using <alt>0246) Conclusion: - I think the original problem regarding review has been solved in the mean time - I think there is still a possible problem regarding characters following UTF-8 characters in markdown.
Created attachment 264997 [details] Test case
That */ was missing is a bug in itself, not related to processing of UTF-8 characters. I'll use this bug report to fix that as well.
Just wanted to note that I am also having trouble with */ missing from C code inside fenced code blocks in markdown, resulting in the rest of the block being highlighted as a comment.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.7. 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 (preferrably in the form of a self-contained example).
I just installed 1.8.7, and the bug was indeed fixed, thank you.