Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
The attached patch to emacs-cvs-23.0.0.ebuild adds support for the --enable-font-backend option to configure. This is the new mechanism for supporting fontconfig/xft as well as server-side fonts. I'm running it now as my primary editor, and it works at least as well as w/o --enable-font-backend. Enable-font-backend requires libotf-0.9.4, which is not yet in portage (cf bug 136921). The last hunk of the patch adds ChangeLog.unicode and README.unicode to the dodoc. That chunck should be applied even if there is resistance to the --enable-font-backend stuff.
Created an attachment (id=89262) [edit] patch to emacs-cvs-23.0.0.ebuild to --enable-font-backend
Hi James. I'm a bit out of the loop as far as emacs-23 goes. How does this differ to the (commented out) XFT support in the emacs-cvs-22 ebuild?
Created an attachment (id=89267) [edit] patch to emacs-cvs-23.0.0.ebuild to --enable-font-backend Oops. Attached old version. This is the patch I meant to attach.
(In reply to comment #2) > Hi James. I'm a bit out of the loop as far as emacs-23 goes. How > does this differ to the (commented out) XFT support in the > emacs-cvs-22 ebuild? > It is written by one of the primary contributors to the emacs-unicode-2 branch (Kenichi Handa) and is likely to be *the* solution for XFT/fontconfig/et al suport going forward, unless I miss my guess. It also works better. I don't expect it for emacs-22, however. Just for the emacs-unicode-2 branch, which seems likely to become emacs-23.
Oh, and it is already part of the emacs-unicode-2 branch, so the change to the ebuild is just a matter of a new --enable and two new --with's.
This seems to work spectacularly well for me.
Added to portage. Thanks for the contribution.