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 661723 - %'s in Doxygen comments isn't parsed correctly
%'s in Doxygen comments isn't parsed correctly
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.5.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-10-14 00:49 UTC by Geoffrey D Alexander
Modified: 2011-12-06 19:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Geoffrey D Alexander 2011-10-14 00:49:04 UTC
In my Doxygen documentation I use 

   <classname>%'s 

so that Doxygen will generate a link to <classname>.  For example, in Doxygen 1.7.3,

   An Atom%'s string representation is one of the following:

in a Doxygen comment produces

   An Atom's string representation is one of the following:

in the Doxygen HTML output with Atom displayed as a link to the Atom class documentation.  However, in Doxygen 1.7.5.1, the same input to Doxygen produces

   An Atom%'s string representation is one of the following:

in the Doxygen HTML output with Atom displayed as a link to the Atom class documentation.  Note that in Doxygen 1.7.5.1, the % incorrectly appears in the Doxygen HTML output (I haven't tried output formats).
Comment 1 Dimitri van Heesch 2011-10-26 20:09:41 UTC
I'll correct this, such that both Atom%'s and Atom's produce a linked Atom.
Comment 2 Dimitri van Heesch 2011-12-03 18:22:38 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.6. 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.
Comment 3 Geoffrey D Alexander 2011-12-06 19:12:34 UTC
The fix works fine in my environment.  Thanks.