[Fontconfig] how to detect `fontconfig needs a long time'

Werner LEMBERG wl at gnu.org
Fri Jul 15 12:20:54 UTC 2016

> well, updating caches will be done inside APIs. unfortunately there
> are no interfaces to monitor it so far.

Hmm.  Given that it can take a few minutes if executed the first time,
such an API is highly desirable IMHO.

> the caches will be only updated when 1) there are no corresponding
> caches available in the certain font cache dirs 2) the mtime of font
> dirs was updated 3) font itself was updated, unless the force-update
> is performed through API.

OK.  So 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?


More information about the Fontconfig mailing list