<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Text copied from a PDF exported using Linux Libertine G Graphite font is missing characters. (comment 24)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124191#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Text copied from a PDF exported using Linux Libertine G Graphite font is missing characters. (comment 24)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=124191">bug 124191</a> from <a class="email" href="mailto:fz1844@gmail.com" title="Frank Zimmerman <fz1844@gmail.com>"> Frank Zimmerman</a> <pre>Fellows, I wanted to revisit this issue and add one more interesting detail. I recently did a bug report for Foxit Phantom, so they could hopefully modify their code to include support for the /ActualText tags mentioned above. During the testing procedure, I realized that using Linux Libertine G in Microsoft Word (2016) with Ligatures turned on, I could export to PDF (using the MS Word Export function), and the resulting PDF worked fine for copying out text, with all PDF readers (Foxit, Acrobat, Chrome, Edge). So, how is it that the Word PDF export can bypass the /ActualText tagging problem? Does it have some internal way of preparing the PDF that avoids this or substitutes a more compatible method? I also realized that the resulting PDF is about 10 times larger (in file size) than a PDF printed using a PDF printer driver. I'm going to attach the Word Doc and Exported PDF. Maybe someone can examine the PDF and see what is going on here? If they (MS Word) can do it, why can't we?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>