New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML links in RTF output are broken (Origin: bugzilla #668424) #4547

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.7.6.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-01-22 05:55:55 +0000, tarzanliu@yahoo.com wrote:

Somehow all my links that I created with 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.

On 2012-01-22 10:48:43 +0000, Dimitri van Heesch wrote:

Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?

On 2012-01-23 04:14:01 +0000, tarzanliu@yahoo.com wrote:

Created attachment 205847
All files needed to show the problem

This is to be used to reproduce the bug 668424.

On 2012-01-23 04:15:34 +0000, tarzanliu@yahoo.com wrote:

Comment on attachment 205847
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 :)

On 2013-12-01 17:16:54 +0000, albert wrote:

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)

On 2013-12-07 22:24:15 +0000, Dimitri van Heesch wrote:

Thanks, I've merged the pull request.

On 2013-12-24 19:00:07 +0000, Dimitri van Heesch wrote:

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).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment