Jerry James writes:
> ;; #### stephen doesn't like this but it's up to him to
do better!
I don't like the direction this is going. The existing rpm includes
an option (unused in Fedora) to build with xft support. The idea is
that once it looks like xft is ready (I'm just waiting for the
"display turds" to go away, actually), I can flip the default from off
to on. The approach we're taking here is going to make that
impossible.
No, it already is impossible as far as I am concerned. I am not
willing to say that Xft is near releasable state. A lot of work
remains to be done, on font.el, font-mgr.el, objects-x.c, menus,
custom, lwlib, etc etc.
The display turds are way low on my list of things to do. If you're
serious that you don't care if the menus and custom fail in many
circumstances, you don't care if font-selection for charset-crossing
texts really sucks, then just flip the switch and let the users fix it
for us. That's the kind of thing that somebody who's willing to face
a couple crashes before they get the code right can improve by just
poking around in redisplay-x.c.
Also, I don't understand how the regexp change helps with the
bug
report. Isn't the problem that font-x-font-regexp matches too
little?
No. The current design is that you use XLFDs for legacy X fonts or
it's not supported. Sorry, but that is what you all voted for when
you voted to have Xft merged. You will recall I opposed it then. I
was right then, and I'm still right.
Now, I intend to change that assumption, but the whole infrastructure
needs to change, and there's nothing in the current design that is
easily adaptable to making it work.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta