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

%'s in Doxygen comments isn't parsed correctly (Origin: bugzilla #661723) #4429

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

On 2011-10-14 00:49:04 +0000, Geoffrey D Alexander wrote:

In my Doxygen documentation I use

%'s

so that Doxygen will generate a link to . 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).

On 2011-10-26 20:09:41 +0000, Dimitri van Heesch wrote:

I'll correct this, such that both Atom%'s and Atom's produce a linked Atom.

On 2011-12-03 18:22:38 +0000, Dimitri van Heesch wrote:

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.

On 2011-12-06 19:12:34 +0000, Geoffrey D Alexander wrote:

The fix works fine in my environment. Thanks.

@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