<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Fonts subset into PDF are not being used to render PDF to canvas, receive questionable fallback replacement"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=101220#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Fonts subset into PDF are not being used to render PDF to canvas, receive questionable fallback replacement"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=101220">bug 101220</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to RGB from <a href="show_bug.cgi?id=101220#c29">comment #29</a>)
<span class="quote">> The problem seems fixed for 5.4.0.0.beta1!</span >
No, please look more closely...
The ipdf filter to insert is now pdfium based and handles subset fonts
correctly, rendering a high fidelity but low resolution bitmap to document
canvas.
But the pdfimport filter continues to use fall back font substitution rather
than parsing the subset fonts. Poor fidelity to original fonts, but as high
resolution vector font draw objects. Issues when the fall back replacment
lacks coverage of a code point--or the source font uses private use addressing
(PUA).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>