<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Text sized and positioned incorrectly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95344#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Text sized and positioned incorrectly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95344">bug 95344</a>
from <span class="vcard"><a class="email" href="mailto:oliver.sander@tu-dresden.de" title="oliver.sander@tu-dresden.de">oliver.sander@tu-dresden.de</a>
</span></b>
<pre>Hi Thomas,
I came across your patch when implementing type3 support for the Arthur
backend. The one line added by your patch makes my seemingly correct type3
implementation fail. More details can be found in
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [PATCH] Arthur support for Type3 fonts -- alternative implementation"
href="show_bug.cgi?id=106150">https://bugs.freedesktop.org/show_bug.cgi?id=106150</a>
Looking at your patch got me confused. It calls updateCTM with an all-zero
matrix. In my understanding of what updateCTM does, this will multiply the
current CTM with zero, and all later rendering will be scaled to size zero.
This is indeed what is happening in ArthurOutputDev.
On the other hand, when I revert your patch, I cannot reproduce the original
bug that made you write the patch anymore. I tried with the test file from
<a href="https://bugs.kde.org/show_bug.cgi?id=362765">https://bugs.kde.org/show_bug.cgi?id=362765</a>
I get lots of errors saying
"Error: Save (q) operator before d0/d1 in Type 3 glyph"
but the rendering seems to be okay. So would it be possible to get some
explanation of why you wrote the patch the way you did? Is my understanding of
updateCTM wrong? Or does your fix need improvements?
Many thanks,
Oliver</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>