| |||||||||||||
Acceleration Architectures, state of the art.Acceleration Architectures, state of the art.Posted Feb 20, 2009 5:05 UTC (Fri) by jamesh (guest, #1159)In reply to: Acceleration Architectures, state of the art. by nix Parent article: FOSDEM09: RandR 1.3 and multimedia processing extensions for X
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).
(Log in to post comments)
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.
|
|||||||||||||