After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 731509 - Markdown backticks not processed within Markdown links.
Markdown backticks not processed within Markdown links.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7-GIT
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-06-11 09:18 UTC by piwi
Modified: 2015-12-30 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description piwi 2014-06-11 09:18:51 UTC 
Using backticks within Markdown links are not considered as code spans. For example:

//!
//! @see [`std::string`][1]
//!
//! [1]: http://en.cppreference.com/w/cpp/string/basic_string
//!

The generated documentation shows the backticks surrounding std::string, and the text is not in monospace; ie. the backticks are not considered as code spans.
Comment 1 piwi 2014-06-11 09:20:35 UTC 
Also, I tried the same syntax with the Daring Fireball editor (http://daringfireball.net/projects/markdown/dingus), its generated HTML is:

<p><a href="http://en.cppreference.com/w/cpp/string/basic_string"><code>std::string</code></a></p>
Comment 2 Dimitri van Heesch 2015-12-28 14:59:32 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2015-12-30 10:19:45 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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).