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

[patch] Title not used when \ref'ing to a \section in a tag (Origin: bugzilla #690403) #4996

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-12-18 11:22:23 +0000, Philipp Moeller wrote:

Created attachment 231795
patch and testcase to fix not used titles

The docanchor tag does not contain the title of the command that generated it.

In the case of \section this leads to anchors that use the title when
\ref'ing to them inside one documentation unit and that use the name
of the anchor when \ref'ing to them through a tag.

To reproduce this with the attached test-case:

$ doxygen Doxyfile1 # creates tag files one.tag
$ doxygen Doxyfile2 # uses one.tag
$ firefox one/html/index.html # see the working \ref using the title
$ firefox two/html/index.html # see the \ref that is using the anchor name

The attached patch fixes this issue by adding a title attribute to the
docanchor element and uses it.

The attached diff can also be seen here: bo0ts/doxygen-fixes@SHA: 9180aa25c0300bed452fc30e729dbe280e2bdce1

On 2012-12-25 21:00:56 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next release.

On 2012-12-26 16:09:18 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.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.

@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