Re: xemacs-gtk now displaying unicode

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? Richard writes: I would characterize it as a fast-thrashing target that doesn't actually move much. :-) And ugly, to boot. :-) (Not that Emacsen are pretty by current standards. :-( ) Nevertheless, I think we should take a careful look at the GTK/pango combination before moving to replace/provide an alternative to Xft in the Xt port. The current Xft implementation has a lot of problems but it works well enough for ordinary editing. Pango will *not* solve those problems (except maybe the font turds), and may create new ones, because most of the problems have to do with fontconfig integration into customize and things like that. So, rather than complicating the Xt/XLIKE code with #ifdefs and so on, I think it would be a better idea to leave it alone for now and tell people who want a pretty or pango-fied or GNOME-integrated XEmacs to use the GTK port. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta