>> It would be good if we could make use of some sort of callback or
>> anything in Freetype2 (?) when it knows it is likely to spend a lot
>> of time like this.
>
> I think this should be rather done in fontconfig...
>
>> Or if we can predict the "cache does not exist" situation reliably,
>> we could trigger the cache rebuild explicitly with a suitable pair
>> of messages around it?
>
> I will ask on the fontconfig list how to detect that.
Here's my question to the fontconfig developers.
[...] how can an application find out that the font cache creation
(or update) is very time consuming? Is it at least possible to
catch the situation of a first run?
And here's the answer.
current implementation assumes the users will runs fc-cache to
create caches before running. as such APIs isn't available at this
point, so no, it isn't. though we discussed a bit these days, if it
is wrong assumption, we may need to think about another way IMHO.
Depressing...
Maybe the Windows installer of lilypond can execute fc-cache?
Werner
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
