Description: The attached .odt file, when converted to pdf, as a strange problem: Certain areas of text can not be copy-and-pasted correctly. The copied text is silently corrupted, causing certain characters to be dropped or duplicated. Very strange. Steps to Reproduce: 1. Open attached "bug.odt" and do File->Export to PDF (or open the attached .pdf) 2. Open the .pdf file. Select the string "critters@example.com" with the mouse, and then Control-C to copy. 3. Put cursor in a terminal (e.g. gnome-terminal) window. Control-Shift-V to paste. Actual Results: Something else is pasted (a corrupted version of the text). Expected Results: What is displayed should be copied. Reproducible: Always User Profile Reset: No Additional Info: NOTE: In real life, the problem arises in files which have been modified by non-LO software (The ODF::lpOD perl library), and seemingly only in tables. I have not been able to reproduce it with text entered manually. The attached demo file is a cut-down copy of a user directory generated from a database using a software tool. User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Created attachment 140456 [details] bug.odt (see steps to reproduce)
Created attachment 140457 [details] bug.pdf (results when I did File->Export to PDF)
Appears to be a REGRESSION. The problem does NOT occur with version 5.1.3.0.0+ Build ID: 72a7b8d08649ecea2b749d72c660d0d9ecf05abd ...but DOES occur with version Version: 5.4.5.1 Build ID: 1:5.4.5-0ubuntu0.17.10.4 and all later versions I tried.
Further narrowed it down: 5.4.0.1 fails, but 5.3.7.2 works.
I guess it's a ligature issue and dupe of Bug 66597 like other duplicates with Calibri and Carlito fonts. *** This bug has been marked as a duplicate of bug 66597 ***
So what changed in 5.4.0.1 to make this problem appear? The exact same .odt does not create wrong PDF in 5.3.x
Bug 66597 is becoming a kind of meta bugs with different issues lumped together, lets separate different issues. *** This bug has been marked as a duplicate of bug 115117 ***
Confirming that this one is fixed in latest master.