<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - FreeText annotation ignores font"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81748#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - FreeText annotation ignores font"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81748">bug 81748</a>
from <span class="vcard"><a class="email" href="mailto:aacid@kde.org" title="Albert Astals Cid <aacid@kde.org>"> <span class="fn">Albert Astals Cid</span></a>
</span></b>
<pre>(In reply to oliver.sander from <a href="show_bug.cgi?id=81748#c7">comment #7</a>)
<span class="quote">> If prawnpdf and pdfcomment really create pdf files that don't follow the
> specification then I think that we should inform them about it. </span >
Yes, if we have the time to spare, we should
<span class="quote">> However,
> that won't save us from the fact that there are plenty of malformed pdf
> files out there that won't go away.</span >
Correct, moreover if other viewers render them correctly
<span class="quote">> We should think about how poppler could
> cope with these files. If the RufScript font is not where it is supposed to
> be, can we look for it elsewhere?</span >
We can, but at that stage of dealing with a broken file, i would say let's do
the minimum needed to make it work, if that involves just going to some default
font, we can do that, probably easier, and then we can try to iterate/improve
on it if needed/time is available :)</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>