[Fontconfig] Streamlining fontconfig scanning

[Jerry Casiano]

It's unfortunate that so many font files out there are just a mess
internally.

The speed increase is obviously a good thing. Not sure if it's worth giving
up the accuracy, but I guess the only way to know for sure is try it and
see how many bugs are actually filed over it.

I don't know how difficult it would be or if it's even worth doing but it
seems the best approach would be to trust the font for the initial scan but
flag it as unchecked then go back and do the full check in the background
with a low priority. That way it doesn't affect application startup, which
seems to be the main issue some are having, and you eventually end up with
an accurate cache

BTW, thank you for Fontconfig.

On Aug 9, 2017 10:45 AM, "Keith Packard" <keithp at keithp.com> wrote:

> Jerry Casiano <jerrycasiano at gmail.com> writes:
>
> > Nice!
> >
> > I assume FcCharset is here to stay even if it might not be as accurate as
> > it was before, correct?
> >
> > I'm guessing FcBlanks just wasn't something anybody used anyway.
>
> FcBlanks is used to check to see if a glyph without an outline is
> supposed to not have an outline, so only used with the current code
> which looks at the outline to check whether to include it in the
> charset.
>
> --
> -keith
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig/attachments/20170809/b0fc69db/attachment.html>