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 735001 - No output for markdown pages with duplicate label title (different anchor)
No output for markdown pages with duplicate label title (different anchor)
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-08-18 14:21 UTC by Haffmans
Modified: 2014-08-20 15:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
minimal example (22.52 KB, application/gzip)
2014-08-18 14:21 UTC, Haffmans
Details

Description Haffmans 2014-08-18 14:21:27 UTC
Created attachment 283758 [details]
minimal example

I have a set of documentation with multiple markdown pages. These pages often have the same structure, e.g. they start with an Overview/Introduction, before going into further details of the topic.

This used to work fine in Doxygen 1.8.6, but as of 1.8.7 (including today's Git build) Doxygen complains about "multiple use of section label" on these pages - even though the section anchors are different.

On pages where such a duplicate label is found all content after that label is simply removed, rendering the page pretty much empty.

I use the "Label {#anchor}" syntax to define the sections.

I have attached a minimal example that exposes this behavior. There are two .md files (under related pages in the HTML output) - see attachment. The first page is generated as expected, but the second page is broken.

Changing the label text of the second page makes thing work as expected again, but means the headings will have to be unique across the whole project - rather than just the anchors.

This may be related to #734727.
Comment 1 Dimitri van Heesch 2014-08-19 10:23:05 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Haffmans 2014-08-20 15:09:35 UTC
I can confirm that it's solved. Thanks!