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 490191 - Monospace fonts can't be aliased in gnome-terminal
Monospace fonts can't be aliased in gnome-terminal
Status: RESOLVED DUPLICATE of bug 142640
Product: gnome-terminal
Classification: Core
Component: general
2.18.x
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-25 16:09 UTC by Charles A. Landemaine
Modified: 2007-10-26 00:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Charles A. Landemaine 2007-10-25 16:09:12 UTC
Please describe the problem:
I developed a set of fontconfig rules¹ for the Microsoft fonts to look the same way in Unix as in Windows, but one rule doesn't work properly. I checked everything in the code, many times. For me it's a bug. In my file, I defined "Courier New" when not italic and between 8 and 19px as aliased:

<match target="font" >
        <test name="family" >
                <string>Courier New</string>
        </test>
        <test compare="eq" target="pattern" name="slant" >
                <const>roman</const>
        </test>
        <test compare="more_eq" name="size" qual="any" >
                <double>8</double>
        </test>
        <test compare="less_eq" name="size" qual="any" >
                <double>19</double>
        </test>
        <edit mode="assign" name="antialias" >
                <bool>false</bool>
        </edit>
</match>


<match target="font" >
        <test name="family" >
                <string>Courier New</string>
        </test>
        <test compare="eq" target="pattern" name="slant" >
                <const>roman</const>
        </test>
        <test compare="more_eq" name="pixelsize" qual="any" >
                <double>8</double>
        </test>
        <test compare="less_eq" name="pixelsize" qual="any" >
                <double>19</double>
        </test>
        <edit mode="assign" name="antialias" >
                <bool>false</bool>
        </edit>
</match>

(The second set is necessary for Firefox and Mozilla applications to take the
rule into account as they only understand "pixelsize").

I also set the monospace standard font as "Courier New":

<alias>
        <family>monospace</family>
        <prefer>
                <family>Courier New</family>
                <family>Fixed [Misc]</family>
                <family>DejaVu Sans Mono</family>
                <family>Nimbus</family>
        </prefer>
</alias>

This works fine everywhere in Gnome except in gnome-terminal. I think this is a gnome-terminal bug because the fontconfig developer told me² this is due to gnome-terminal not using Pango. If you have a look at the following
screenshot, you'll see that the "Courier New" font (used for code, mainly) is
sharp and clear inside Firefox and gedit, but it is blurry/washed out in
gnome-terminal: http://img87.imageshack.us/img87/3356/screenshot2zm4.png
I hope we can figure out what is going on.
Thanks,

Charles.



¹ Source: http://ubuntuforums.org/showthread.php?t=208396
² https://bugs.freedesktop.org/show_bug.cgi?id=12866

Steps to reproduce:
1. Install the Microsoft fonts (make sure you have Freetype compiled with the Byte Code Interpreter)
2. Remove font antialiasing below 14px
3. Set "Courier New" as default font for gnome-terminal


Actual results:
The font is still antialiased in gnome-terminal.

Expected results:
The font should be aliased and sharp, like in any other application.

Does this happen every time?
Yes

Other information:
Here's the previous bug report I filed for fontconfig, and the answer from the fontconfig developer: https://bugs.freedesktop.org/show_bug.cgi?id=12866
Comment 1 Behdad Esfahbod 2007-10-26 00:03:22 UTC
Well, I maintain both vte/gnome-terminal and Pango :).

This looks like it should be a dupe of bug 142640 in fact.  I try fixing it tonight.

*** This bug has been marked as a duplicate of 142640 ***
Comment 2 Behdad Esfahbod 2007-10-26 00:03:56 UTC
In the mean time, if you run g-t by setting env var VTE_BACKEND=pango, you get the desired behavior, but it's kinda slower.