I noticed that when copy-pasting from LibreOffice-generated PDFs a character corruption occurs. If I copy-paste "respective owners" from the PDF, what I actually get is "respecnve ooners".
Steps to Reproduce:
User Profile Reset: No
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 OPR/50.0.2762.67
Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
No repro. Version: 220.127.116.11.alpha0+
Build ID: 8d4d2bf5405ef9d4b0b126f96f882f01031defd6
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
Created attachment 140243 [details]
Created attachment 140244 [details]
It seems that in former version, when copy-pasting from LibreWriter-generated PDFs a character corruption or replacement occurred, in that “ti” was always replaced with “n”. In version 18.104.22.168, “ti” becomes “t”. Also “ing” becomes “nn” if you copy such words as living, walking, talking.
I confirm this on
Version: 22.214.171.124 (x64)
CPU 线程：4; 操作系统：Windows 10.0; UI 渲染：默认;
区域语言：zh-CN (zh_CN); Calc: group
Also, I find that, if changing the fonts to Arial and then re-export as pdf, the bug is gone. Thus the bug is font-specific. The current document uses Calibri font.
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.10; Render: default;
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Version 126.96.36.199.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Probably it has been already reported in the past to LibreOffice's Bugzilla...
Similar Bug 115117 is explained in https://bugs.documentfoundation.org/show_bug.cgi?id=115117#c2 and marked as a duplicate.
*** This bug has been marked as a duplicate of bug 66597 ***
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 ***