<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [PATCH] Replace Splash font rendering by Qt font rendering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102290#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [PATCH] Replace Splash font rendering by Qt font rendering"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102290">bug 102290</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>Here is a new version of the patch. It now renders all glyphs in Albert's test
files correctly. The patch didn't really get any prettier, though.
In fact, I completely ripped out the Qt-based code-to-glyph-index conversion
code, and replaced it with what Splash does. That works, but I am a bit
surprised that Qt does not offer more help here. QRawFont has the
glyphIndexesForChars method, but that only takes QChar (aka unicode) as input,
and we don't generally have reliable unicode.
Unfortunately, to use the Splash font engine to do the code-to-gid decoding, I
had to add a new method getCodeToGID to the SplashFTFontFile class. Is that
okay? I tried to do without that, but I couldn't.
During my last tests I noticed that there is still a problem with font colors.
I'll look into that, but I'd like to get an opinion on the new SplashFTFontFile
method while I look. Thanks!</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>