374289 - Complex Fontconfig configurations spread across /etc/fonts/conf.d do not work

Status: UNCONFIRMED

(Core :: Graphics: Text, defect)

Description

[Logan Rathbone]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070121 PhoeNUX/1.5.0.9-2pnx Firefox/1.5.0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070121 PhoeNUX/1.5.0.9-2pnx Firefox/1.5.0.9

This isn't exactly the same situation as described in bug 243227, but it's similar --but I felt it was different enough to create a new report.

I'm working on a Linux distro and getting all applications to work will with a relatively complex font setup is important to me.  Basically, here are the rules in plain english for this setup:

(1) start by antialiasing and autohinting everything (10-antialias.conf, 10-autohint.conf)
(2) use bytecode interpreter for all MS Core Fonts, and for those fonts, don't antialias when the size is below 16 points (or 18 pixels, specifically for Mozilla) (20-msttcorefonts.conf)

While all programs on my machine that use the fontconfig library honour these settings when the config files are split up, Mozilla/Firefox/Thunderbird/Seamonkey only honours them when they're all in one file (local.conf).

For both situations, the "size" property for <test> in fontconfig does not work; only "pixelsize" -- that's the topic of bug #243227 and is not directly related to this bug, but I just thought I'd mention it.

Reproducible: Always

Steps to Reproduce:
(remember to replace "Mozilla" with Mozilla/Firefox/Thunderbird/Seamonkey as you will - they're all affected.)

1. make sure your freetype2 is compiled with the bytecode interpreter enabled.
2. make sure MS's "core fonts for the web" (msttcorefonts) are installed.
3. place the attached local.conf file into /etc/fonts/
4. start Mozilla, and go to a site like Google, that prefers these fonts.  Notice how they appear as they should.
5. remove /etc/fonts/local.conf, and put the other attached XX-*.conf files into /etc/fonts/conf.d/ (may need to temporarily move any other files that may be there)
6. Start Mozilla, go to google, and notice how the fonts do not render as they should.  You may need to recreate your .fonts.cache-2 files by running "fc-cache -fv" and you may need to restart your X server before the system notices the config files changes... I didn't, but it's a possibility.
Actual Results:  
Mozilla doesn't honour my settings when files are split up, fonts are not rendered correctly.

Expected Results:  
Mozilla should honour my settings and render fonts correctly.

Comment 1

[Logan Rathbone]

Attachment: Configuation files used to reproduce the bug.

These are the config files used to reproduce the bug.

local.conf goes into /etc/fonts/
The rest go into /etc/fonts/conf.d/

Comment 2

[doa379]

I can confirm that the browser doesn't read the fontconfig config properly even at ESR-68.