On Thu, 16 Jan 2003 13:42:32 -0500, Liam Quin wrote: > Lonnie Borntreger <[EMAIL PROTECTED]> wrote: >> On Thu, 2003-01-16 at 09:34, Serge Pl�ss wrote: >>> After "playing" a little more with it I came to >>> the conclusion that it doesn't matter which fonts I move around > >> Instead of rebooting, run "fc-cache -f" after each font move, before >> trying the program. > >> I was not able to start any of the programs until the bad font was >> removed. > > Like Serge, I found it didnt' matter which fonts I moved around. > Frederic Crozat spent some timelooking at this too. I found that > it depends on the *order* in which fc-cache is run... > > If you run fc-cache in /usr/X11R6/lib/fonts so it descends recursively, > the result is useless, programs don't run. > > If you make a change, e.g. moving a font or directory, things run. > E.g. I did, mv drakfonts .., to move a whole directory away. > > If you then move the directory back, and do > cd drakfont > fc-cache -f -v `pwd` > then everything runs, with all the fonts yuo had before.
Well, I'm not able to "fix" the problem when regenerating cache using this method :(( > Furthermore, the cache file generated in the drakfont directory > is identical! Only the tiemstamp is different. In fact, there is two differents ways to generate cache in fontconfig code (argggg), one is used when using fc-cache, the other when starting a program linked with fontconfig (and when cache is not coherent..) > Ferderic suspects some code in pango, because that's where gedit dies. I don't think it is a bug in pango.. I think it is a bug in the fontconfig matching code, which is only used by pango.. -- Frederic Crozat MandrakeSoft
