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 668424 - HTML links in RTF output are broken
HTML links in RTF output are broken
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.6.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-01-22 05:55 UTC by tarzanliu
Modified: 2013-12-24 19:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
All files needed to show the problem (69.80 KB, application/x-zip)
2012-01-23 04:14 UTC, tarzanliu
Details

Description tarzanliu 2012-01-22 05:55:55 UTC
Somehow all my links that I created with <a> are broken. There is a # in the beginning of the hyperlink address. I saved the RTF into .PDF and the links are still broken. Somehow the HTML output is fine.
Comment 1 Dimitri van Heesch 2012-01-22 10:48:43 UTC
Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Comment 2 tarzanliu 2012-01-23 04:14:01 UTC
Created attachment 205847 [details]
All files needed to show the problem

This is to be used to reproduce the bug 668424.
Comment 3 tarzanliu 2012-01-23 04:15:34 UTC
Comment on attachment 205847 [details]
All files needed to show the problem

Here it is. It's about 1,000 lines.

Please see refman.rtf page 26 for a few hyperlinks that have "#" attached to
the beginning of the addresses and all hyperlinks on page 30.

BTW, on page 28, the short summary of the classes is messed up. Again the HTML
version is perfectly alright. I'm unable to fix it either.

Thank you!

P.S. 
This is an open source library for Arduino :)
Comment 4 albert 2013-12-01 17:16:54 UTC
I've pushed a solution regarding the hyperlinks to git (pull request 63).

I cannot see the problem regarding the class that is mentioned in the BTW, but this might be because I look at the wrong place. If this problem still exists in the current version of doxygen please submit a new bug report (maybe with some images indicating the problem)
Comment 5 Dimitri van Heesch 2013-12-07 22:24:15 UTC
Thanks, I've merged the pull request.
Comment 6 Dimitri van Heesch 2013-12-24 19:00:07 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).