fontconfig-config 45-latin.conf and ~/.fonts.conf overriden by new 60-latin.conf

arne, do we want the 45-latin or 60-latin thing to be used (disregard the number for now).

is there anything more I can do to help progress this bug?

in conf.d README, the following is said about the priorities:

Files begining with: Contain:

 00 through 09 Font directories
 10 through 19 system rendering defaults (AA, etc)
 20 through 29 font rendering options
 30 through 39 family substitution
 40 through 49 generic identification, map family->generic
 50 through 59 alternate config file loading
 60 through 69 generic aliases, map generic->family
 70 through 79 select font (adjust which fonts are available)
 80 through 89 match target="scan" (modify scanned patterns)
 90 through 99 font synthesis

Isnt that scheme used properly for *-latin.conf ?

I can confirm this problem with the latest karmic daily build (Aug 23).

On jaunty, I also have 60-latin.conf enabled by default but my own ~/.fonts.conf works without any problem.

And the contents of 60-latin.conf on jaunty and on karmic are completely the same.

Confirming the problem. Can't override latin and non-latin via ~/.font.conf or /etc/fonts/local.conf due to 60-latin.conf and 65-nonlatin.conf

please fix this before 9.10 release!

Workaround:

$ cd /etc/fonts/conf.d/
$ sudo mv 50-local.conf 05-local.conf
$ sudo mv 50-user.conf 05-user.conf

Confirming the problem as well. I miss being able to remove smoothing from a few tiny fonts. :'(

Andrey's workaround solved it (at least until the next update), but I would really like to see this fixed.

any further update on this bug and what might happen for maverick? its been sitting around marked as 'in progress' for a while now :-)

another 3 months have gone by without any activity? should I unassign this and put it back to 'confirmed' if nobody is actively working on it?

I'll unassign this one and instead forward it to Debian, as this affects them as well.