Description: When printing odt document with URL links to a virtual PDF printer and using Calibri font links are not clickable in resulting pdf. Steps to Reproduce: 1. Create a document with a link using http 2. Change font for the whole document (select all) to Calibri (if Liberation Sans is used as default) 3. Print document to a virtual PDF printer (PDFCreator, Nitro PDF, etc.) Actual Results: When you open such pdf document in a pdf viewer (Adobe Acrobat Reader DC, Chrome) links with http are not clickable. Expected Results: Links should work. Reproducible: Always User Profile Reset: No Additional Info: Based on discussion on PDFCreator forums https://forums.pdfforge.org/t/links-do-not-work-when-using-calibri-font it seems that when using Calibri (and maybe other fonts) Libre is sending tt as a special character and not as t twice. And such character then can't be used in the url. This doesn't happen when using Liberation Sans (maybe other fonts). Also doesn't happen when saving to pdf using Libre's built-in option (even if using Calibri font). Sending same document to print via MS Word doesn't produce such issue.
Confirming behavior on Windows 10 Home 64-bit en-US with Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Printing of ligatures (e.g. tt, ti, ffi) to gs based PDF generators can corrupt URLs for some fonts. OTF ligature support was not enabled, but on printing for some strings of URLs ligatures are used and corrupt the URL (noticed "tt" in http or https, and at least a "ti" (from time), "ffi" (from office). No solid reporducer--maybe autocorrect recognition of URL, while writer shell is unaware of ligature use disrupts URL?
Created attachment 159113 [details] Printed to PDF - no URL The difference between *exporting* to PDF in LO and *printing* to PDF is that in the former case a *URL link* is exported, while in the latter case just the *text*. So, essentially, it is then up to the PDF reader, to interpret the "http://..." text as a URL or not. ==> What happens if you copy the printed URL and paste it into a browser - does it get opened correctly? I tried it with a gs-based PDF printer on Linux and it does, even though the URL text does contain ligatures after printing. In this case, one PDF reader (Atril viewer) does not interpret the text as URL, while another (PDF-XChange Editor, via WINE) does. Used font is Carlito, which also supports ligatures. I'm not sure if Word disables font ligatures or not, but in LO they can be disabled by appending “:-liga” to the font name would work around the "issue".
Dear wroot, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Just tested again, this time printed PDF using Microsoft Print to PDF (Windows 10, originally it was reported when using Windows 7 and i used PDFCreator and Nitro virtual PDF printers). The issue is still present. Version: 7.3.1.3 (x64) / LibreOffice Community Build ID: a69ca51ded25f3eefd52d7bf9a5fad8c90b87951 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: lt-LT (lt_LT); UI: en-US Calc: threaded
The PDFs printed to PDF virtual printers don’t contain hyperlinks, and whether a hyperlink is auto detected or not is up to the PDF viewer and we can’t do anything about it. If you want fully functional PDFs, export them directly from LibreOffice. If you want to disable ligatures, you can do so from the Font Features dialog.