diff options
| author | Morten Sorvig <msorvig@trolltech.com> | 2009-09-16 05:53:15 (GMT) |
|---|---|---|
| committer | Morten Sorvig <msorvig@trolltech.com> | 2009-09-16 05:53:15 (GMT) |
| commit | db8f89cdb4fcb0d8436db80d50221308900dca01 (patch) | |
| tree | 5c9333d24f328224084ef30e6e9da2d2e7b706cd /src/corelib/global/qglobal.h | |
| parent | 10e1d939d6bf08249304cb2c555be2f74c3a0f02 (diff) | |
| download | Qt-db8f89cdb4fcb0d8436db80d50221308900dca01.zip Qt-db8f89cdb4fcb0d8436db80d50221308900dca01.tar.gz Qt-db8f89cdb4fcb0d8436db80d50221308900dca01.tar.bz2 | |
Improve font handling on Mac/Cocoa.
The Mac/Cocoa font database currently relies on two APIs, ATSUI (old)
and CoreText (new). These are interchangable and work on the same font
database.
Some differences do exist, in particular ATSFontFamilyGetName seems
to return the same as ATSFontGetName for some fonts - the font name,
not the family name. In any case, the old ATS code path is initializing
QFontDatabase::familes() with the font name.
This causes a naming mismatch with code that uses CoreText and gets
the proper family name, in this case in initializeDb(). The fix is
to make sure the correct family name is used by using the CoreText
API to access it.
RevBy: TrustMe
Diffstat (limited to 'src/corelib/global/qglobal.h')
0 files changed, 0 insertions, 0 deletions