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 765002 - `@addindex`entries fail to link to the exact location in Compiled HTML Help.
`@addindex`entries fail to link to the exact location in Compiled HTML Help.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.11
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-04-13 16:18 UTC by Christoph Lipka
Modified: 2016-09-05 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christoph Lipka 2016-04-13 16:18:00 UTC
When using Compiled HTML Help output, index entries created using `@addindex` link to the corresponding HTML page, rather than the corresponding anchor on the page.
Comment 1 albert 2016-04-17 16:48:02 UTC
Please provide some information how to jump to a place not at the top of the page / example chm file where this takes place. Been searching the Internet but didn't find a suitable example.
(Example / description in German is OK for me too).
Comment 2 Christoph Lipka 2016-04-26 23:25:44 UTC
One example would be the inbuilt help of POV-Ray for Windows.

There's really no black magic to it: Just have the index.hhk point to the corresponding anchor on the HTML page, like so:

<LI><OBJECT type="text/sitemap"><param name="Local" value="mypage.html#myanchor"><param name="Name" value="Foo"></OBJECT>

But I've thrown together a corresponding patch already; expect a pull request within the next few hours.
Comment 3 Dimitri van Heesch 2016-04-27 07:49:16 UTC
Thanks, I've merged the pull request
Comment 4 Dimitri van Heesch 2016-09-05 13:46:33 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).
Comment 5 Christoph Lipka 2016-09-05 14:09:15 UTC
The fix seems to be working properly in 1.8.12, thanks.