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 634857 - Colons "::" don't show up (likely after greater than > sign)
Colons "::" don't show up (likely after greater than > sign)
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.2
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-11-14 21:33 UTC by Cleo Saulnier
Modified: 2011-01-03 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cleo Saulnier 2010-11-14 21:33:23 UTC 
This has shown up in the discussion mailing list as well.  The :: is removed.  Issue exist after both > and >  But may happen without greater than sign.

Example:

<tt><A href="http://www.sgi.com/tech/stl/Vector.html">vector</A>&lt;T&gt;::iterator</tt>

A workaround is to use four of them.

<tt><A href="http://www.sgi.com/tech/stl/Vector.html">vector</A>&lt;T&gt;::::iterator</tt>

Since there is a workaround, perhaps it should be included in the docs and leave it as is... or to implement a fix.
Comment 1 Dimitri van Heesch 2010-11-15 22:16:24 UTC 
I agree, the real fix would be to escape the ::, i.e. use \:: (this is consistent with the other characters that have a special meaning, such as #,<,and >)

Another fix, related to bug #632879, is to give a warning about the use of :: as an link indicator to a non existing global 'iterator' and then show the result as-is.

Should be corrected in the next subversion update.

Then the correct solution is to use:

<tt><a 
href="http://www.sgi.com/tech/stl/Vector.html">vector</a>\<\>\::iterator</tt>
Comment 2 Dimitri van Heesch 2011-01-03 19:01:29 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.3. 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.