Le jeudi 09 février 2006 à 11:23 -0500, Patrick Lam a écrit : > Frederic Crozat wrote: > > Le mardi 07 février 2006 à 16:12 -0500, Patrick Lam a écrit : > > > >>Frederic Crozat wrote: > >> > >>>I can confirm fontconfig erases bad global cache files. > >>> > >>>But I found a way to cause fontconfig to never update cache correctly > >>>with the following test case : > >>>-clean your cache completely : rm -f /var/cache/fontconfig/* > >>>-run fc-cache -v to get a consistent cache > >>>-put the attached old fonts.cache-2 (before cache was moved > >>>to /var/cache/fontconfig) in /usr/share/fonts/ttf/big5 > >>>-run fc-cache -v => cache is updated for this directory > >>>-run fc-cache -v again => cache is updated AGAIN for this directory and > >>>is growing (check in /var/cache/fontconfig..) > >>>-remove fonts.cache-2 from the directory > >>>-run fc-cache -v several time : each time, cache is updated and grow. > >>> > >>>I've attached the file to put in big5 directory as well as the broken > >>>cache which is generated in /var/cache/fontconfig and the good one. > >>> > >>>This problem is not visible when using non-root applications because > >>>missing cache will be stored in ~/.fonts.cache-2 and won't get updated. > > I've reproduced, and I think I've fixed, this problem in CVS. Please > confirm. Cache always growing problem is fixed. But old fonts.cache-2 file in the file system (not in /var/cache/fontconfig) is not removed when running fc-cache and running fc-cache several times still update cache in /var/cache/fontconfig. -- Frederic Crozat <fcrozat@xxxxxxxxxxxx> Mandriva _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
