Thanks for the comment, even though it doesn't count as an additional +1, any input would be appreciated. I've read those reports and indeed changing the default cachedir for Win32 to LOCAL_APPDATA_FONTCONFIG_CACHE would helps but the issue they were originally complaining won't be completely gone because the cache is still being generated at first. it needs to be taken care by those package maintainer then. Aside from that, they could share their applications installed with users on the box though, I think generating caches per user instance is redundant. it's what this change really means. it could be one of options for packages but if there are any better places for system-wide caches, that would be better for default path IMHO. Given that we settled down the default system-wide cache dir and it can be shared among applications, I'm not sure if it's worth trying, but if having official package for Win32 helps for this issue, let me think about it. or any volunteers are welcome of course :) On Thu, Nov 21, 2013 at 11:06 AM, Jehan Pagès <jehan.marmottard@xxxxxxxxx> wrote: > Hi, > > On Mon, Nov 18, 2013 at 4:07 PM, Akira TAGOH <akira@xxxxxxxxx> wrote: >> Anyone who uses fontconfig on Win32 has any comments on this? >> I'm not even familiar with Win32 so much. so I have no idea if we have >> any concerns once this change is applied. any kinda +1/-1 as a comment >> would be appreciated. > > Well I'm the reporter, so I guess that don't count as an additional > +1, but just searching "fontconfig cache directory" on the web, I can > find several bug reports and discussion about it. On launchpad for > Ubuntu for instance, I found 2 bug reports: > https://bugs.launchpad.net/inkscape/+bug/1021815 > https://bugs.launchpad.net/inkscape/+bug/1196373 > > They are both for inkscape and are about the same path issue. I've > seen other reports for VLC or mplayer, related to fontconfig cache > taking time to generate, regularly, but they did not say what was the > actual issue in the reports when closing it. So I can't say for sure > that was the same path issue. > > In any case, the main problem is that Windows builds of various > software will likely bundle fontconfig in their installer. So that > makes as many fontconfig built by people who did hope that the default > would be ok and won't try to change the configure settings. There is > hardly one fontconfig installation and a knowledgeable maintainer for > this specific package. So flawless default config prevents bad > surprises in the various projects (like GIMP, Inkscape, etc.) who make > win32 builds. > > And in any case, it is always better to have reasonable defaults for a > given platform, isn't it? :-) > > Thanks. > > Jehan > >> >> ---------- Forwarded message ---------- >> From: <bugzilla-daemon@xxxxxxxxxxxxxxx> >> Date: Sun, Nov 17, 2013 at 6:42 PM >> Subject: [Fontconfig-bugs] [Bug 71691] New: Defaulting <cachedir> to >> LOCAL_APPDATA_FONTCONFIG_CACHE for Win32 build >> To: fontconfig-bugs@xxxxxxxxxxxxxxxxxxxxx >> >> >> Priority medium >> Bug ID 71691 >> Assignee fontconfig-bugs@xxxxxxxxxxxxxxxxxxxxx >> Summary Defaulting <cachedir> to LOCAL_APPDATA_FONTCONFIG_CACHE for Win32 build >> QA Contact freedesktop@xxxxxxxxxx >> Severity minor >> Classification Unclassified >> OS Windows (All) >> Reporter jehan@xxxxxxxxxxxx >> Hardware All >> Status NEW >> Version unspecified >> Component conf >> Product fontconfig >> >> Created attachment 89343 [details] >> Defaulting to LOCAL_APPDATA_FONTCONFIG_CACHE >> >> Hi, >> >> I'm a GIMP dev. We had some user telling us that the default value for >> fontconfig cache may not be the most appropriate on Windows (cf. >> https://bugzilla.gnome.org/show_bug.cgi?id=703331). >> >> Well I'm not expert on Windows, so I can't say if >> LOCAL_APPDATA_FONTCONFIG_CACHE is the best fit (but saving in the non-roaming >> data repository sounds acceptable). On the other hand, saving in the %TEMP% >> directory though may indeed not be the best idea, if the TEMP directory concept >> is anything like on UNIX (where you should not expect the TEMP directories to >> have the same contents at your next reboot. It may, but on many installation, >> temp dirs are emptied). And apparently, according to our user, it is indeed >> often emptied on Windows too. >> >> So since you already have the implementation for >> LOCAL_APPDATA_FONTCONFIG_CACHE, I'm proposing to simply use it as the default >> for Windows. >> Patch attached. >> >> ________________________________ >> You are receiving this mail because: >> >> You are the assignee for the bug. >> >> >> _______________________________________________ >> Fontconfig-bugs mailing list >> Fontconfig-bugs@xxxxxxxxxxxxxxxxxxxxx >> http://lists.freedesktop.org/mailman/listinfo/fontconfig-bugs >> >> >> >> >> -- >> Akira TAGOH >> _______________________________________________ >> Fontconfig mailing list >> Fontconfig@xxxxxxxxxxxxxxxxxxxxx >> http://lists.freedesktop.org/mailman/listinfo/fontconfig -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
