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

@subpage in ordered list is not created correctly (Origin: bugzilla #690831) #5008

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 blocker in component build for ---
Reported in version 1.8.3 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-12-28 19:59:17 +0000, Stefan wrote:

Created attachment 232348
project to reproduce the bug

Dimitri,

attached find a manual where you can find the online version at http://ultradefrag.sourceforge.net/handbook/

Notice the TOC is created with @subpage commands in 00_main.dox, which was resulting in the correct ordered list until doxygen 1.8.2

Starting with doxygen 1.8.3 this is no longer the case.

To generate the documentation run build_docs.cmd

Thanks in advance for a fast fix, so I can take advantage of the fix of bug # 687572.

--
Stefan

On 2012-12-28 21:44:11 +0000, Stefan wrote:

Dimitri,

as a workaround the HTML tags "

" can be used instead of "-#", but that is only a workaround.

--
Stefan

On 2012-12-28 23:41:15 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2013-01-20 13:34:57 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3.1. 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 2013-01-30 00:46:35 +0000, Stefan wrote:

Dimitri,

I can confirm the fix.

Thanks for fixing this issue.

--
Stefan

@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