Hi, ok I think I got misleaded. The official Windows package maintainer is actually Jernej, isn't it? Anyway see below about the unpatched Windows package. Jehan On Wed, Nov 6, 2013 at 11:31 AM, Jehan Pagès <jehan.marmottard@xxxxxxxxx> wrote: > Hi, > > On Sun, Sep 29, 2013 at 11:19 PM, Jehan Pagès > <jehan.marmottard@xxxxxxxxx> wrote: >> Hi, >> >> On Thu, Sep 26, 2013 at 2:50 PM, Jehan Pagès <jehan.marmottard@xxxxxxxxx> wrote: >>> Hi, >>> >>> On Mon, Sep 23, 2013 at 1:51 AM, Michael Henning >>> <drawoc@xxxxxxxxxxxxxxxxxx> wrote: >>>> At the time I fixed this, Jernej's builds did not exhibit the problem >>>> because they used an older version of fontconfig. I did not report >>>> this upstream because it's a configuration issue, but now that I think >>>> about it, the defaults should perhaps be changed on windows (or maybe >>>> when cross compiling). >>> >>> Yes I am not sure if upstream or else, but definitely somethings >>> should be done *somewhere*, otherwise we might have various new >>> developers to the team (or the same ones, forgetting it happened >>> already) scratching their head with this problem every 6 months. The >>> simple fact that the last Windows build is broken even though you had >>> this fixed from before this release is a sign there should be >>> something in place for this to not happen again. :-) >> >> Just for information, I have now opened a report upstream: >> https://bugs.freedesktop.org/show_bug.cgi?id=69836 > > The font bugs on Windows are still present in GIMP 2.8.8! > If we use an older version of fontconfig, Drawoc has a patch all ready > for this: build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch > Other than that, we can just use fontconfig 2.11.0 (current stable), > or over when there will be. Fontconfig has the fix since 2.11.0. > > Could we make sure the same process is applied for the Windows > nightbuilds (which use the patches in build/windows/) and the releases > (which apparently do not)? That makes it less useful to have > nightbuilds if we don't even provide the same in a release! > > And can something be done for GIMP 2.8.8? Since it has just been out, > and that's not a change in GIMP itself, can we update the Windows > packages? Or once it is out, we say it is too late? > Thanks! > > Jehan > >> Jehan _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
