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

Wrong page number and header in pdf output (Origin: bugzilla #707483) #5285

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component documentation for ---
Reported in version 1.8.5 on platform Other
Assigned to: Dimitri van Heesch

On 2013-09-04 16:28:29 +0000, albert wrote:

When looking at the index at the end of the doxygen manual and especially at the item "flex", it refers to page 7. When using the hyperlink to page 7 it lands on the wrong page 7, it lands in the contents and not in the "normal" documentation part, chapter installation.

A probably related problem is that the header line for the not numbered "Introduction" chapter is "Contents".

Another problem is the header line on the second page of each chapter. This is nicely illustrated in chapter 3. The second page reads here "Documenting the code" whilst this should be "Special comment blocks" like on the third page of this chapter. An alternative would be that all pages of the chapter would have the header line "Documenting the code" i.e. the chapter title.

On 2013-09-09 11:40:37 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 18:59:36 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.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 (preferrably in the form of a self-contained example).

On 2013-12-29 17:34:50 +0000, albert wrote:

Reference is now correct

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment