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

%foo shows % in qhelp index (Origin: bugzilla #604503) #3607

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.6.1 on platform Other
Assigned to: Dimitri van Heesch

On 2009-12-14 04:27:08 +0000, Craig Scott wrote:

When a page or section title contains a % prepended to a word (to prevent auto-link generation), the % is correctly stripped for the title but is not stripped for the title shown in the qhelp contents/index. For example:

/*! \page somekey %MyClass details

....
*/

In the above example, the qhelp index will show an entry like this:

%MyClass details

when it should just be

MyClass details

On 2009-12-28 11:04:51 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next release.

On 2009-12-30 13:38:57 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

On 2012-06-11 08:57:36 +0000, aarsathe@gmail.com wrote:

This bug is still present in html output in version 1.8.1. (win32 version)

I define a page with \page classapge %MyClass

Result: a page name in the navigation pane which is "%MyClass" while the page header is named "MyClass" with no link generation

Expected: a page name in the navigation pane which is "MyClass" and a page header is named "MyClass" with no link generation

@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