Bug 581612 - please enable xft font rendering in Xemacs
Summary: please enable xft font rendering in Xemacs
Keywords:
Status: CLOSED DUPLICATE of bug 356961
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-12 19:20 UTC by Richard Z.
Modified: 2010-04-12 19:34 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-12 19:34:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard Z. 2010-04-12 19:20:22 UTC
This is disabled, perhaps because in earlier versions a trivial patch would be needed to make it work.

I am running self-built packages with XFT rendering since 15 months without a single problem on Fedora 10 & 12.

If you enable it *nothing* will change for users who do not take special steps to use XFT fonts.

Relying on bitmapped fonts is an evergrowing pain as it is extremely difficult to find any that covers all my character sets, not to mention they look horribly.

If you enable it and want to see a difference you need to put something like this into .Xdefaults:
   XEmacs.default.attributeFont: Mono:size=11.5
   XEmacs.bold.attributeFont: Mono:size=11.5:style=Bold
   XEmacs.italic.attributeFont: Mono:size=11.5:style=Oblique
   XEmacs.bold-italic.attributeFont: Mono:size=11.5:style=Bold Oblique
   XEmacs.modeline.attributeFont: Sans:size=10
   XEmacs.menubar.font: Sans:size=10
   XEmacs*xftFont: Sans:size=10


Thanks
Richard

Comment 1 Jerry James 2010-04-12 19:34:41 UTC
It is disabled because it is unfinished experimental code.  That hasn't changed recently.  This is a duplicate of another bug, so I'll add a few comments there.  The basic problem, though, is that the assertion that "nothing will change for users who don't take special steps" is incorrect.

*** This bug has been marked as a duplicate of bug 356961 ***


Note You need to log in before you can comment on or make changes to this bug.