Re: Lilypond taking forever to typeset

[David Kastrup]

Mojca Miklavec <address@hidden> writes:

> On 13 July 2016 at 16:12, Masamichi Hosoda wrote:
>>
>> If you use LilyPond 2.19.45 binary which is downloaded from LilyPond website,
>> fontconfig version is 2.11.95.
>>
>> Maybe, you can see the version by the following command.
>>
>> $ ./LilyPond.app/Contents/Resources/bin/fc-list --version
>
> Thank you.
>
> It's 2.11.95 for the devel version and 2.8.0 for the stable one. (Not
> that it makes any difference to the "problem" we are facing.)
>
>> I've tried on Windows.
>> I deleted the cache files.
>> Then, I invoked LilyPond for Windows (from LilyPond website).
>>
>> It took about 8 minutes.
>> The environment does not have TeX Live fonts.
>> But it has many Japanese fonts (about 50 Japanese fonts).
>
> OK, so my assumption was correct. (I wonder why there aren't any more
> complaints.)

Because it's on first encounter?  People may give up right away and not
bother about a report ("program is broken so nobody is using it").  Or
they try to make a record of the problem for reporting and it
disappears.

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.

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?

-- 
David Kastrup