+2006-02-21 Mike Fabian <mfabian@suse.de>
+ reviewed by: plam
+
+ * fc-cat/fc-cat.c (main):
+
+ Initialize fontconfig library in fc-cat to avoid segfault.
+
+2006-02-18 Patrick Lam <plam@mit.edu>
+ * fc-cache/fc-cache.c (scanDirs):
+ * src/fccache.c (FcCacheReadDirs):
+ * src/fcdir.c (FcDirScanConfig):
+
+ Fix the underlying cause of the below segfault (must usually
+ call FcDirCacheHasCurrentArch after FcDirCacheValid).
+
+2006-02-18 Patrick Lam <plam@mit.edu>
+ * src/fccache.c (FcDirCacheHasCurrentArch):
+
+ Fix triggering of segfault caused by misreading cache files
+ (reported by fcrozat).
+
+2006-02-17 Patrick Lam <plam@mit.edu>
+ * src/fcint.h (FC_CACHE_MAGIC):
+
+ Bump up magic version; we changed the binary format.
+
+2006-02-17 Patrick Lam <plam@mit.edu>
+ * fc-cat/fc-cat.c (main):
+
+ Enable fc-cat to print out old-style cache info when given a
+ directory name.
+
+2006-02-16 Patrick Lam <plam@mit.edu>
+ * src/fccache.c (FcDirCacheHasCurrentArch):
+
+ Deal correctly with changing FC_CACHE_MAGIC.
+
+2006-02-16 Patrick Lam <plam@mit.edu>
+ * fc-cache/fc-cache.c (usage, scanDirs, main):
+
+ Add -r --really-force option which blows away cache files and then
+ regenerates them.
+
+2006-02-16 Patrick Lam <plam@mit.edu>
+ * src/fccache.c (FcDirCacheUnlink, FcCacheCopyOld, FcDirCacheWrite):
+
+ Don't bail if fontconfig can't remove a dir cache file.
+ Skip the ID of a cache file when copying.
+ Eliminate 'source file too small' bug in FcDirCacheWrite.
+
+2006-02-13 Patrick Lam <plam@mit.edu>
+ * src/fcfreetype.c (FcFreeTypeQuery):
+
+ Fix memory leak in error condition code.
+
+2006-02-13 Mike Fabian <mfabian@suse.de>
+ reviewed by: plam
+ * src/fcfreetype.c (FcFreeTypeQuery):
+
+ Skip bitmap fonts which can't even get it together enough to
+ declare a family name; this appears to reproduce previous
+ fontconfig behaviour.
+
+2006-02-10 Takashi Iwai <tiwai@suse.de>
+ reviewed by: plam
+ * src/fccache.c (FcDirCacheOpen):
+
+ Try to open /var/cache/fontconfig/[hashed name] before
+ fonts.cache-2 in a directory, because /var/cache/fontconfig
+ failures ought to be fixable, unlike fonts.cache-2 failures,
+ which may leave you screwed.
+
+2006-02-10 Takashi Iwai <tiwai@suse.de>
+ reviewed by: plam
+ * src/fcmatch.c (FcFontSetMatch):
+
+ Use a tri-state to mark the fonts which didn't get blocked but
+ were just missing an element, to distinguish them from the
+ fonts that do match the element.
+
+2006-02-10 Takashi Iwai <tiwai@suse.de>
+ reviewed by: plam
+ * src/fcmatch.c (FcFontSetMatch):
+
+ Don't kill fonts because they don't declare an element that's
+ being matched on.
+
2006-02-09 Patrick Lam <plam@mit.edu>
* src/fccache.c (FcGlobalCacheLoad, FcGlobalCacheSave,
FcDirCacheUnlink, FcDirCacheOpen, FcDirCacheWrite):
Don't crash on non-existant directories in global cache.
-2006-01-26 Patirck Lam <plam@mit.edu>
+2006-01-26 Patrick Lam <plam@mit.edu>
* src/fccache.c (FcGlobalCacheSave, FcDirCacheWrite):
* src/fccfg.c (FcConfigAddFontDirSubdirs, FcConfigNormalizeFontDir):
* src/fcdir.c (FcDirScanConfig):