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 595191 - missing tags in the alphabetical index in config.html
missing tags in the alphabetical index in config.html
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.6.1
Other All
: Normal trivial
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-09-14 16:50 UTC by Carl R. Werth
Modified: 2009-12-30 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
correct alphabetical index for config.html (14.26 KB, text/html)
2009-09-14 16:50 UTC, Carl R. Werth 		Details

Description Carl R. Werth 2009-09-14 16:50:57 UTC 
Created attachment 143170 [details]
correct alphabetical index for config.html

Tags are missing in the alphabetical index of the tags at the beginning of the
page config.html and some tags are not in alphabetical order.

!--> A correct index is uploaded as attachment.

These are the missing items of the alphabetical index:
DOT_CLEANUP
HTML_FILE_EXTENSION
INCLUDED_BY_GRAPH
SHOW_USED_FILES
USE_INLINE_TREES


Some of the other tags are not in alphabetical order:
BRIEF_MEMBER_DESC
BUILTIN_STL_SUPPORT

ENABLED_SECTIONS
ENUM_VALUES_PER_LINE

PERLMOD_MAKEVAR_PREFIX
PERLMOD_PRETTY

QHG_LOCATION
QHP_CUST_FILTER_ATTRS
QHP_CUST_FILTER_NAME
QHP_NAMESPACE
QHP_SECT_FILTER_ATTRS
QHP_VIRTUAL_FOLDER

REFERENCES_LINK_SOURCE
REFERENCES_RELATION

SORT_GROUP_NAMES
SORT_MEMBER_DOCS
SORT_MEMBERS_CTORS_1ST
Comment 1 Dimitri van Heesch 2009-10-04 13:20:10 UTC 
Confirmed. Should be fixed in the next subversion/website update.
Comment 2 Dimitri van Heesch 2009-12-30 13:39:06 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).