After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 126799 - fontconfig local overrides are not respected for terminal font
fontconfig local overrides are not respected for terminal font
Status: RESOLVED DUPLICATE of bug 142640
Product: gnome-terminal
Classification: Core
Component: general
2.4.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-12 11:13 UTC by leon breedt
Modified: 2007-02-11 19:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Sreenshot of the problem (39.07 KB, image/png)
2003-11-12 11:16 UTC, leon breedt 		Details

Description leon breedt 2003-11-12 11:13:10 UTC 
i've customized fontconfig to turn off aliasing and subpixel rendering for
a specific font below a certain point size, since i have an LCD, and it is
more legible to disable it for small point sizes.

some GNOME applications seem to respect it, and the font shows up without
aliasing (gedit, and the font selection dialog), but GNOME terminal does not.

the relevant fontconfig configuration snippet (from ~/.fonts.conf):

<match target="font">
    <test name="family">
        <string>ProFontWindows</string>
    </test>
    <test name="size" compare="less">
        <double>7.5</double>
    </test>
    <edit name="antialias" mode="assign">
        <bool>false</bool>
    </edit>
    <edit name="hinting" mode="assign">
        <bool>false</bool>
    </edit>
    <edit name="rgba" mode="assign">
        <const>none</const>
    </edit>
</match>
Comment 1 leon breedt 2003-11-12 11:16:27 UTC 
Created attachment 21378 [details]
Sreenshot of the problem
Comment 2 leon breedt 2003-11-12 11:18:55 UTC 
in both applications, the font is manually configured to be
ProFontWindows-7 (Regular)
Comment 3 Luis Villa 2004-01-02 20:25:31 UTC 
Mariano, Havoc, is this a vte problem and not a g-t problem?
Comment 4 leon breedt 2004-01-09 10:03:39 UTC 
btw, i can't reproduce this issue on Debian sid (gnome-terminal 2.4.2)
Comment 5 leon breedt 2004-01-09 10:04:59 UTC 
also: debian vte version being 0.11.10
Comment 6 Noah Levitt 2004-02-26 00:00:33 UTC 
Leon, if you configure your hinting settings in the gnome font
configuration dialog, vte will pick them up.

There was some discussion in irc.gnome.org/#unicode about this
behavior, and it’s unclear whether the actual bug is in vte, gtk+, or
fontconfig.
Comment 7 Wira D. Mulia 2004-04-19 21:08:13 UTC 
This bug still exists on gnome-terminal 2.6.0. Setting the font render method to
Monochrome in gnome-font-properties does help for the terminal, but it will make
all apps not anti-alias everything, which is not the intended behavior.
Comment 8 Wira D. Mulia 2004-04-19 21:32:08 UTC 
I tried downgrading vte to 0.10.29, and the older vte honors fontconfig's
local.conf, but gnome-terminal 2.6.0 won't even start:

$ gnome-terminal
gnome-terminal: relocation error: gnome-terminal: undefined symbol:
vte_terminal_set_scroll_background

vte 0.11.10 does not honor fontconfig's local.conf. So is this vte's problem?
Comment 9 Chris Wilson 2007-02-11 19:18:31 UTC 
It certainly has been reported as vte's problem in the past, but unfortunately has not yet been resolved.

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