Hi, > > > Any directories not matching a configured prefix would map to themselves; > > > this makes the existing configuration and cache files compatible. > > How do you resolve any fonts which doesn't located under /usr/share/fonts ? > > The prefix mapping would be configurable; add a map from > /usr/X11R6/lib/X11/fonts to /var/cache/fontconfig/x11-fonts and you'll > get your cache files for fonts in the standard X directories stored > in /var/cache/fontconfig/x11-fonts. > > > 2. Add one additional mapping table under the FontCachePrefix/ > > I can either store the mapping table in a file or directly in the file > system; I don't have a strong preference, but using the file system is > likely to involve fewer but more complicated system calls during > application startup. It might also involve a slight bit of overhead. The > advantage is that there aren't any synchronization issues; each cache file > is accessable without reference to a separate file. It seems like that > should be more robust in many ways.
Sorry, do you mean that, "store the mapping table in the file system", you are talking about the first idea? Anyway, I agree that "additional table in a file" is less robust and involve more overhead. For the "configurable prefix mapping", how do it exists? Also it is permissable that, there are many "<dir>" in the fonts.conf. Is it possible to store the mapping as properties of the "<dir>" elements? > > > But, "/var/cache/fonts" is already specified in the FHS, that, this > > directory is for dynamically generated fonts, I quote it here : > > Sigh. We'll use /var/cache/fontconfig then. I don't really care. > > > Though, I think /var/cache/fonts should be the better, as I like the style > > what fontconfig do. > > To some extent, we can ask if a slight reinterpretation of the FSH can be > permitted in this case. Ok. Best Regards, Zenith Lau _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
