summaryrefslogtreecommitdiffstats
path: root/lib/fonts/l047033t.pfa
diff options
context:
space:
mode:
authorEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@nokia.com>2011-03-22 09:57:59 (GMT)
committerEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@nokia.com>2011-04-15 10:56:26 (GMT)
commit1348f4f0853155182d2ea5836902794d1e43980c (patch)
treef51a9882326ff3d89876902a65af0493436d3146 /lib/fonts/l047033t.pfa
parent3bff1637cd49617d334c1be63c20e008fac93be1 (diff)
downloadQt-1348f4f0853155182d2ea5836902794d1e43980c.zip
Qt-1348f4f0853155182d2ea5836902794d1e43980c.tar.gz
Qt-1348f4f0853155182d2ea5836902794d1e43980c.tar.bz2
Long live QRawFont!
The QGlyphs API was initially attempted with a bastardization of QFont which was meant to encapsulate a single, physical font instance (a QFontEngine) where a set of glyph indexes would make sense. This is not how QFont was intended to be used, and it caused several issues. At the same time, the requirement for loading a font from ttf/otf data and be able to access it and use it without polluting the rest of the process with the font arose. To support these two APIs we introduce QRawFont, which is an abstraction on top of a single physical font. Done-with: Jiang Jiang
Diffstat (limited to 'lib/fonts/l047033t.pfa')
0 files changed, 0 insertions, 0 deletions