https://bugs.documentfoundation.org/show_bug.cgi?id=171301
--- Comment #5 from Mike Kaganski <[email protected]> --- (In reply to [email protected] from comment #4) > - **Windows File Explorer** → Result: "File not found" error message True. Windows File Explorer uses the legacy "use current system codepage" idea inherited from IE. > - **Firefox** → Result: does not open Wrong. Firefox opens it fine. > All programs that rely on the Windows API to open files (Wondershare > PDFelement, Adobe Acrobat, Firefox, File Explorer) fail because Windows > cannot resolve the path. Wrong. Your PDF works fine in Adobe Acrobat (I created the path locally, to see if it works). And - most important: Windows' own current API (UrlCreateFromPath, System.Uri) use it. Respective RFCs (RFC 3986, RFC 8089) and other standards (like WHATWG URL Standard) recommend UTF-8 encoding; all of them list "current codepage" as insecure and to-be-avoided. Your test only proves that there are some applications that do not follow the correct current recommendations of URL encodings. -- You are receiving this mail because: You are the assignee for the bug.
