Apache OpenOffice (AOO) Bugzilla – Issue 55736
Hyperlinks with UTF8 encoded characters destroyed during PDF export
Last modified: 2008-10-12 18:05:25 UTC
I checked with 2.0 (1.9.m125) German version WIN XP: [680m125(Build8947)] Steps to reproduce: 1. create new writer document 2. insert Text "Hyperlink here" 3. Mark word "here" 4. open hyperlink dialogue 6. click "Weblink" 7. Insert Link from a.m. URL 8. Confirm and close hyperlink dialogue 9. save document 10. test hyperlink: it will wor fine 11. export to pdf (quality 75%, max resolution 300px, does not matter) 12. Open .PDF 13. test hyperlink expected: works, will open <http://de.wikipedia.org/wiki/Gierseilf%C3%A4hre> actual: does not work, tries to open <http://de.wikipedia.org/wiki/Gierseilf%C3%A4hre> 14. Try again hyperlink in .odt, of course it will still work Some further test 15. Mark "here" with hyperlink, open Hyperlink-dialogue expected: <http://de.wikipedia.org/wiki/Gierseilf%C3%A4hre> actual: <http://de.wikipedia.org/wiki/Gierseilfähre> (UTF8 destroyed) (what ever that might mean) 16. Confirm and close Hyperlink dialogue 17. Try hyperlink expected: should not work (?) actual: this hyperlink still works You will see just the same problems in CALC
I forgot to say for step 7: I copye the URL from the URL pane of my MOZILLA ftom open WIKIPEDIA page
Same problem with 2.0 (1.9.m118) English version WIN XP: [680m118(Build8936)]
ssa->pl: duplicate ?
pl->fme: this basically is another aspect of issue 54985
.
*** Issue 64606 has been marked as a duplicate of this issue. ***
I think "OOo Later" is not appropriatefor this bug. Hyperlinks to Internet-URLs is an often used feature, and it is really annoying if those links become destroyed during PDF-export, especially because generally nobody will check that in the created PDF. so TM -> 2.X (pls. also see Issue 54985).
*** Issue 73513 has been marked as a duplicate of this issue. ***
*** Issue 54985 has been marked as a duplicate of this issue. ***
6 attachments to follow, 4 demo documents and two alternative patches
Created attachment 42261 [details] exportlink.odt
Created attachment 42262 [details] exportlink.odp
Created attachment 42263 [details] exportlink.odg
Created attachment 42264 [details] exportlink.ods
Created attachment 42265 [details] patch against all the apps that use SetLinkURL
Created attachment 42266 [details] alternative patch against just vcl's setLinkURL
do either of those two patches appeal as a fix for the export link to PDF problems ?
FME->PL: At a first glance, the vcl patch looks more attractive to me. Could you please have a look?
OK. will apply in CWS vcl73
committed in CWS vcl73
please verify in CWS vcl73
Verified with cws vcl73 = ok
Still ok in 680m211_9151
I think that this problem occurred with 2.4 again. Please reopen this issue. I checked with 2.4 and 3.0 (BEA300_m2) Japanese version WIN XP. Please look at two files which I attached.
作æˆã•ã‚ŒãŸæ·»ä»˜ (id=53380) The PDF that I made with 2.4
作æˆã•ã‚ŒãŸæ·»ä»˜ (id=53381) An explanation image
I checked example from original export with "2.4.0 Multilingual version German UI WIN XP: [680m12(Build9286)]" and also with "3.0.0 Beta Multilingual version English UI WIN XP: [300m1 (Build9298)]". Confirm, bug is back again.
reassign, target
*** Issue 89439 has been marked as a duplicate of this issue. ***
fixed in CWS vcl89
*** Issue 89940 has been marked as a duplicate of this issue. ***
please verify in CWS vcl89
Verified with cws vcl89 = ok
Hello rainerbielefeld, *, I have tested your steps with DEV300m28 under Debian SID AMD64, where this problem does not occur. Could you try it again with an actual Win version or a dev snapshot, if it still occurs on Win? If not: Could you close this issue, please? @kamataki: Could you try it again as well with a newer Japanese version of OOo, please? TIA Thomas.
I checked with "Ooo-dev 3.0.0 Beta Multilingual version English UI WIN XP: [300m29 (Build9339)]" proceeding as per original report. Result: Works for me.
I checked with Ooo-dev m29 Japanese version WIN XP. Good! Thanks, Kamataki.
Hello rainerbielefeld, *, as you and kamataki has confirmed my observation, I will close this issue :) Feel free to reopen this issue, if reappears again. Thomas.