Bug 114362 - GDK_USE_XFT=0 does not work anymore
GDK_USE_XFT=0 does not work anymore
Product: Red Hat Raw Hide
Classification: Retired
Component: gtk2 (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Owen Taylor
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-01-27 05:39 EST by Enrico Scholz
Modified: 2007-04-18 13:02 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-27 10:13:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2004-01-27 05:39:44 EST
Description of problem:

$GDK_USE_XFT seems to be ignored in recent gtk2 snapshot so that every
gtk-based application uses AA fonts now. This makes nearly all text
based applications unusable on TFT monitors; tweaking with
gnome-fonr-properties does not help.

Some applications can be cured by assigning a bitmap font as system
font, but important applications like browsers are using the fonts
suggested by the page. Therefore, this does not help really.

KDE/QT knows such a setting (qtconfig - >Fonts -> Enable
Anti-Aliased...) and gtk-2.2. supports it too, so it seems to be
doable to add this functionality.

Version-Release number of selected component (if applicable):

Comment 1 Owen Taylor 2004-01-27 10:13:28 EST
Not a bug, the code has been removed for GTK+-2.3.x. (And hadn't
been maintained for several years, never worked well. It's
an *entirely* different code path.)

I'm not sure what's different about TFT monitors. Many
of us use antialiased fonts on laptops, etc, and like it.
(Since you mention GNOME, I don't think it's bug 88259)

If you want precanned bitmap fonts, just put them in ~/.fonts or
/usr/share/fonts (see the release notes for details).

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