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 765001 - Bad character escaping scheme in HTML anchor generation.
Bad character escaping scheme in HTML anchor generation.
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-04-13 16:06 UTC by Christoph Lipka
Modified: 2016-09-05 14:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Self-contained example demonstrating the problem. (26.95 KB, application/zip)
2016-04-27 00:12 UTC, Christoph Lipka 		Details

Description Christoph Lipka 2016-04-13 16:06:14 UTC 
The current mechanism of escaping special characters to create HTML anchor names (at least when converting from index words) uses the format ":HH", where HH are hexadecimal digits.

This format is unsited when Compiled HTML Help output is enabled, as the help viewer gags on colons in anchor names.
Comment 1 albert 2016-04-17 16:49:24 UTC 
Can you please attach a self-contained example (source+config file in a tar or zip) that allows us to reproduce the problem?
Comment 2 Christoph Lipka 2016-04-27 00:12:59 UTC 
Created attachment 326812 [details]
Self-contained example demonstrating the problem.
Comment 3 Christoph Lipka 2016-04-27 00:22:39 UTC 
I've figured out by now that the problem can be solved without modifying the general HTML output, by substituting colons within anchor names in the index.hhk with "%3A".

I'll submit a corresponding pull request within the next few hours.
Comment 4 Dimitri van Heesch 2016-05-16 10:43:00 UTC 
Thanks, I've merged the pull request
Comment 5 Dimitri van Heesch 2016-09-05 13:45:38 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 6 Christoph Lipka 2016-09-05 14:07:23 UTC 
The fix seems to be working in 1.8.12, thanks.