[Bug 705348] Byte-code interpreter seems not enabled in Qt

bugzilla at redhat.com bugzilla at redhat.com
Sat Jun 4 00:42:19 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=705348

--- Comment #15 from Kevin Kofler <kevin at tigcc.ticalc.org> 2011-06-03 20:42:16 EDT ---
So this is what Qt does:
http://www.qt.gitorious.org/qt/qt/blobs/4.7/src/gui/text/qfontengine_x11.cpp#line1038

I think the difference is that Pango has its own class to represent a set of
fonts, so it will only pass one font at a time to fontconfig (which allows
getting the settings for the exact font containing the glyph), whereas Qt
actually uses freetype's glyph lookup, which unfortunately means fontconfig
gets only the whole list of fonts to work with.

The Pango approach looks pretty much like a hack around the limitations in
fontconfig and freetype to me.

So I still think that it is impractical to change Qt and that the lohit fonts
must be fixed to zap the unwanted hinting bytecode from the fonts themselves as
was done for lohit-devanagari-fonts and drop the fontconfig settings.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the fonts-bugs mailing list