client-side font rendering very very slow in X.org xserver 1.5.3 w/r200: massive fetches from VRAM, why?

[Nicolas Mailhot]

Le dimanche 01 février 2009 à 12:54 +0000, Nix a écrit :
> On 31 Jan 2009, Michel Dänzer outgrape:

> > I think a big part of the motivation for client side fonts was indeed
> > anti-aliasing, so if you don't want AA and core fonts are faster for
> > you, just use core fonts?
> 
> That's Not really practical, because they involve different APIs,
> different font matching mechanisms, and so forth: they aren't really
> interchangeable. I don't think an attempt to convince the KDE hackers to
> allow konsole to use core fonts would go very far, not least because
> core fonts are generally seen as obsolescent 

From a distribution point of view, apps which use fontconfig almost
never present problems (because fontconfig will do all kinds of smart
stuff like substituting missing fonts transparently), while apps that
use core fonts have a long continuing history of crashing at the
slightest opportunity (with users complaining at the distribution
instead of upstream).

For Fedora 11 we've trying to move all our fonts in fontconfig space,
with symlinks to other parts of the filesystem for apps that do not use
fontconfig

http://fedoraproject.org/wiki/Features/Repackaging_of_Fedora_fonts

I think the Fedora 12 cycle will probably start by mass bug-filling
against apps that need those symlinks.

-- 
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Ceci est une partie de message num?riquement sign?e
URL: <http://lists.x.org/archives/xorg/attachments/20090201/3ce70029/attachment.pgp>