Re: Xft - problem with XftFontOpenName and XftFontOpen functions.
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Le Lun 20 février 2012 09:18, Eeri Kask a écrit : > On 19.02.12 21:00, "Nicolas Mailhot" <nicolas.mailhot@xxxxxxxxxxx> wrote: >> Le Dim 19 f?vrier 2012 09:13, John Found a ?crit : >>> Hm, nobody knows or nobody cares? >>> Or it is a great secret, for the internal circle only? :D >> >> It's probably because no one sane uses Xft directly nowadays. Xft alone is >> not >> sufficient to display modern text, you need a shaper such as pango (directly >> or via cairo) or harfbuzz to process properly modern fonts, Xft will let you >> read glyphs in truetype fonts but won't know how to position them properly. > > > What is wrong with using XftDrawString8() It's missing all the rules to properly position glyphs in relation to one another according to unicode and truetype extended features. XftDrawString uses freetype directly, but the freetype shaping engine has been deprecated a long time ago (it's been spun out in what became pango, and harfbuzz is a rewrite merging pango with the code QT people had written to do the same thing) -- Nicolas Mailhot _______________________________________________ xorg@xxxxxxxxxxx: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: list-xorg@xxxxxxxxxxx
[X Forum] [Nouveau Driver] [Devices] [XFree86] [XFree86 Newbie] [Site Home] [IETF Annouce] [Security] [Fontconfig] [Bugtraq] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Video for Linux] [Linux RAID] [Linux Resources]