After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690831 - @subpage in ordered list is not created correctly
@subpage in ordered list is not created correctly
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.3
Other Windows
: Normal blocker
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-12-28 19:59 UTC by Stefan
Modified: 2013-01-30 00:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
project to reproduce the bug (76.24 KB, application/octet-stream)
2012-12-28 19:59 UTC, Stefan 		Details

Description Stefan 2012-12-28 19:59:17 UTC 
Created attachment 232348 [details]
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
Comment 1 Stefan 2012-12-28 21:44:11 UTC 
Dimitri,

as a workaround the HTML tags "<ol><li></li></ol>" can be used instead of "-#", but that is only a workaround.

--
Stefan
Comment 2 Dimitri van Heesch 2012-12-28 23:41:15 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2013-01-20 13:34:57 UTC 
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.
Comment 4 Stefan 2013-01-30 00:46:35 UTC 
Dimitri,

I can confirm the fix.

Thanks for fixing this issue.

--
Stefan