Currently, if you install new fonts or remove some fonts, the FontConfig cache does not get updated to match, so weird font-matching could result. The workaround is to delete the PM_Fonts_FontConfig_Cache_v1.1 key, so that it gets regenerated. It would be nice if the cache could be dynamically updated: 1) remove entries for fonts which are no longer found 2) add entries for newly discovered fonts I don't expect that the first part is very hard, but the "newly discovered" part is probably tricky...
At the very least deleting this key should be documented somewhere as the first step to trouble shooting font problems.
If you can write a paragraph for README.txt I will include it as documentation in the Firefox 3.0 GA. But we are too late to change the README in CVS, so not sure what we can otherwise do. Would be better to fix the problem in the FontConfig port, though, in which case this would be invalid again.
Hmmm... maybe "clear" the key isn't as clear as "delete" the key. Feel free to change that word (or any others) for clarity.
OK, thanks. So the documentation part gets done in bug 439193, the rest is invalid as this again is a FC problem. -> dupe
If I understand this correctly: https://bugzilla.mozilla.org/show_bug.cgi?id=439193#c6 this is fixed in mzfntcfgft_20080617.