steven Mitchell writes:
So does adopting Pango affect more than just fonts?
No. Pango is a front-end for font management systems like fontconfig
and rendering engines like freetype. Its job is to manage
internationalization of Unicode text.
Pango would replace much of the "fontcolor*" set of files.
Does it affect icons used, or borders, or menu text, or gutters,
scrollbars, or any other part of what you see on the XEmacs screen?
Text in the menus and gutters of course will be affected. Otherwise,
no. It does require the Xrender extension for efficient use, but
that's no more than Xft does.
Pango seems to be often implemented in conjunction with a drawing
library, Cairo. Would Cairo need to be implemented too, to cover
all the things XEmacs might use pango for?
No. Pango is a low-level library that Cairo uses to draw text.
If so, what would Cairo replace that is in XEmacs currently?
It wouldn't replace anything. It could be added as another lowlevel
display engine, at the level of TTY, Xt, GTK+, and the as yet
unreleased Carbon and GTK+ redisplays. To get an idea of what is
involved, "ls src/*-gtk.[ch] src/*xlike*" (the *xlike* files contain
the low-level implementation of routines that are common between GTK+
and Xt).
It could also be wrapped in LISP and used to implement a canvas and
other drawing features, which is something I'd like to see.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta