[Libreoffice-bugs] [Bug 113543] When exporting to tagged PDF, characters in certain fonts are lost or misrepresented in the underlying text.

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #3 from Quentin Christensen <quentin at nvaccess.org> ---
Hi Timur,

I tested on the build I was running this morning:

LibreOffice 6.0.0.3 (x64)
Build ID: 64a0f66915f38c6217de274f0aa8e15618924765
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: en-AU (en_AU); Calc: group

While I updated that build, I reproduced on my other computer on Windows 7 with
LibreOffice 5.4.2.2 (x64)

Now, I've updated and rebooted and my main PC is running:
Version: 6.0.3.2 (x64)
Build ID: 8f48d515416608e3a835360314dac7e47fd0b821
CPU threads: 8; OS: Windows 10.0; UI render: default; 
Locale: en-AU (en_AU); Calc: group

My Windows 10 is the latest Fast Insider build, though since it also reproduces
on Windows 7, I don't think the Windows version is so important here.

For just one word, tagging isn't necessary, true - I needed it for the file I
was originally creating.

Zoom does seem to have an effect though.

When I have zoom set to 20%, my exported PDF has the word "certifccte" instead
of "certificate".  When I zoom up to 200%, the word becomes "certifccate"

I can definitely still reproduce this.  I did originally download my Raleway
font from Google rather than GitHub.  If it is an issue with the font itself,
perhaps the GitHub version is newer - although I expect more people would find
it through Google.  Surely though the font just controls how the text is
rendered, it shouldn't change what the underlying text is?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20180419/807747ed/attachment.html>