On Tue, Oct 30, 2018 at 3:02 PM Keith Packard <keithp@xxxxxxxxxx> wrote: > Agreed. I'd like to suggest that the flatpak environment should be > taught how to map font directory names that it sees to cache file names > generated externally; then the existing md5(pathname) approach to cache > file generation will 'just work' > > Presumably each flatpak has to get a custom font configuration to point > it back at the external fonts; having that include a mapping to the > external names seems like a pretty simple change to me. just reminds me that there should be some options to do this but wasn't too much if we keep compatibility in API and conditions not to modify application-side. given that we revert this change and are going to keep API compatibility and no changes in applications, what we can do is probably to let fontconfig know the directory mapping tables through a file and read it. though they need to re-generate it every time if the mappings is changed every time. > > -- > -keith > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/fontconfig -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
