<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cache file update fails on Windows (also Cygwin)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99360#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cache file update fails on Windows (also Cygwin)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99360">bug 99360</a> from <a class="email" href="mailto:trueroad@trueroad.jp" title="Masamichi Hosoda <trueroad@trueroad.jp>"> Masamichi Hosoda</a> <pre>Fontconfig 2.12.3 (released today) still fails to rebuild the font cache on Windows (MinGW). LilyPond 2.19.56 for Windows (released Feb. 26, 2017) has applied my patch to the bundled fontconfig. <a href="https://github.com/gperciva/gub/commit/4092624f4fa85ae8c38fcb87646942f13583b26a">https://github.com/gperciva/gub/commit/4092624f4fa85ae8c38fcb87646942f13583b26a</a> Before applying the patch, the bug reports on font caching raised frequently. After releasing LilyPond 2.19.56, it has gone, except the case of using older LilyPond. There are no bug reports on the font cache for the last three months. Furthermore, TeX Live 2017 for Windows will be applied my patch. <a href="https://www.tug.org/svn/texlive?view=revision&revision=44334">https://www.tug.org/svn/texlive?view=revision&revision=44334</a> This patch can solve font caching problems and it does not cause other problems.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>