LWN.net Logo

Acceleration Architectures, state of the art.

Acceleration Architectures, state of the art.

Posted Feb 19, 2009 12:48 UTC (Thu) by nix (subscriber, #2304)
In reply to: Acceleration Architectures, state of the art. by ctg
Parent article: FOSDEM09: RandR 1.3 and multimedia processing extensions for X

As far as I can tell the intention is for EXA to replace XAA entirely. As of (very) recently it even does core fonts nice and fast, so unless you rely on things like stipple acceleration (!) I'd say it's getting there quite well.

(downside: it looks like Speedo and Type1 core fonts are about to stop working, as the code to handle them has been torn out of libXfont 1.4.0. I doubt anyone misses Speedo, but Type1 may very well be missed, because they *do* still work client-side.)


(Log in to post comments)

Acceleration Architectures, state of the art.

Posted Feb 20, 2009 5:05 UTC (Fri) by jamesh (guest, #1159) [Link]

While the Type1 code is gone from libXfont, it still has the FreeType backend. Given that FreeType can read Type1 fonts, is it possible that they were just removing a superfluous backend and switching to the code base that everyone else uses? (including the apps that use Xft).

Acceleration Architectures, state of the art.

Posted Feb 20, 2009 10:44 UTC (Fri) by nix (subscriber, #2304) [Link]

It's possible. I'm not entirely sure *where* libXfont is used, to be
honest (something or other to do with core fonts). I used to know; I need
a prosthetic memory.

Acceleration Architectures, state of the art.

Posted Feb 20, 2009 14:47 UTC (Fri) by jamesh (guest, #1159) [Link]

LibXfont is pretty much just the core font support library. Any application that has been ported to fontconfig (using Xft or cairo) won't be using it, and should retain Type1 support through the use of freetype.

Looking at the libXfont 1.4.0 release notes, it looks like you were correct about Type1 fonts not working with the new version. That said, I totally understand the desire to reduce the size/complexity of the core font code: the feature is deprecated, but can't easily be removed as it is not an extension to the X protocol.

If they can support Type1 fonts through FreeType with minimal effort, then great. If they can't, it isn't a huge loss.

Acceleration Architectures, state of the art.

Posted Feb 23, 2009 16:54 UTC (Mon) by jcristau (subscriber, #41237) [Link]

Only the old type1 libXfont backend has been removed, support for type1 fonts from the freetype backend is still there.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds