Re: xemacs-gtk now displaying unicode
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> Jeff writes:
> > However, if pango is available, then Gtk almost certainly too. Is there
> > any reason to prefer Xt or Gtk? Your Xresources would be one. Font
> > compatibilty would be another.
We should work to make Xresources just a compatibility feature. It
should not be possible to do anything with Xresources that can't be
done in init.el.
I don't understand what you mean by font compatibility. In the end,
the configuration and rendering engines are the same, no?
I mean font name compatibility. Xft can use XLFD font names, gtk/pango
can not. Xft and pango can use fontconfig font names. Gtk/Gdk, which I'm
no longer using to draw text, only uses a simplfied version of
fontconfig naming, whereas pango uses Gtk font names plus font names
dependent on the backend being used. Right now, that's Xft so
fontconfig names can be used. For pango on Win32 or OSX, the font names
could be different. At least I can tell the three main ones apart.
XLFD - "-*-luximono-bold-r-*-*-*-120-*-*-m-*-*-*"
fontconfig - "Monospace-12:weight=bold:slant=italic
Gtk - "Monospace Bold Italic 12"
I'm trying to pango to consistently work with both Gtk and fontconfig
font names. Using fontconfig brings in the fc-* functions.
As you know, there's a lot of code that assumes XLFD naming.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta