[Libreoffice-bugs] [Bug 112225] Percent-encoding (URL encoding) shouldn't be used for all hyperlink characters except space

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=112225

Anton F  changed:

   What|Removed |Added

 CC||x4f...@outlook.com

--- Comment #4 from Anton F  ---
Not reproduced.

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: cd2b5168e8ef1cb6e721bc5220421464ed723096
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: ru-RU (ru_RU.UTF-8); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2021-07-21_14:56:23
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 112225] Percent-encoding (URL encoding) shouldn't be used for all hyperlink characters except space

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=112225

--- Comment #5 from Thomas Lendo  ---
Still reproducible with

Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 52443996eff721e612ac4afc1eb1a53bb8a3e06f
CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win
Locale: de-AT (de_AT); UI: de-DE
Calc: threaded



Steps:
- Open the attached zip archive.
- Extract the odt and docx files.
- Open the odt file in Writer, the docx file in MS Word.
- Export from Writer to pdf and save from Word to pdf.
- Open the 2 pdf files and see the tooltip. ü for example is shown as %C3%BC
and ß is sown as %C3%9F in the pdf file exported from Writer.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 112225] Percent-encoding (URL encoding) shouldn't be used for all hyperlink characters except space

[bugzilla-daemon]

https://bugs.documentfoundation.org/show_bug.cgi?id=112225

Stephan Bergmann  changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Stephan Bergmann  ---
(In reply to Thomas Lendo from comment #0)
> Is it necessary to percent-encoding (URL encoding) all hyperlink UTF-8
> characters today? Some Windows programs like PDF-XChange have problems to
> open such encoded hyperlinks (e.g. "f%C3%BCr" is problematic but not "für").

That appears to be a shortcoming of those "Windows programs like PDF-XChange". 
(And I suggest you get in touch with them.)

With your sample PDF files from attachment 138438, "Bug 112225 Straßenbrücken
(exported with LibO 6.1).pdf" contains

> <>

while "Bug 112225 Straßenbrücken (saved with Word 2013).pdf" contains

> <>

when interpreting the file's bytes as UTF-8.  (The difference in absolute vs.
relative URL is apparently as per your comment 3.)

But at least

"PDF 1.7", section 12.6.4.7 "Interactive Features: Actions: Action Types: URI
Actions" in table 206 "Additoinal entries specific to a URI action" on page
424, specifies that key "URI" is of type "ASCII string" with value: "(Required)
The uniform resource identifier to resolve, encoded in 7-bit ASCII."

And your "...(exported with LibO 6.1).pdf" matches that requirement while your
"...(saved with Word 2013).pdf" does not.

(See also

"tdf#70833: IDNA support when exporing hyperlinks to PDF" for how we are
careful to write ASCII-only URI values.)

-- 
You are receiving this mail because:
You are the assignee for the bug.