Around 1 o'clock on Mar 22, Patrick Lam wrote: > Seems like a good thing to work on after I have an initial version with > the mmapable config. I think someone's recently added some hashing, too. Without a specification for how matching and sorting can work without looking at every font, there's little point in starting to work on an mmap'able data structure. In fact, I suspect that to get reasonable performance, we will have to add a new API that allows for incremental sorting where you don't receive all of the fonts at once but rather need to ask for the 'next' font in line. I'd rather change the cache file format only once; it's an expensive operation to consider as we will have old versions on disk for some time after any switch. So, first we need a specification for font matching which doesn't require examining each font, then some idea of how to extend that into a sorting API. Looking at the CSS2 specification and matching that more closely may actually permit some of these optimizations. -keith -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available Url : http://lists.freedesktop.org/archives/fontconfig/attachments/20050322/2ee4f222/attachment.pgp
