On Tue, Aug 8, 2017 at 3:44 PM, Jerry Casiano <jerrycasiano@xxxxxxxxx> wrote:
Nice!I assume FcCharset is here to stay even if it might not be as accurate as it was before, correct?
Of course. That's the main machinery for fallback.
I'm guessing FcBlanks just wasn't something anybody used anyway.
Right. It was only useful to the extent that we did not trust fonts to have correct cmap.
On Aug 7, 2017 1:31 PM, "Behdad Esfahbod" <behdad@xxxxxxxxxx> wrote:______________________________Cheers,After that, we should clean up the cache race patches and remove the locking. We should accept that cache updates will always remain racy, simply because we don't have or want to use the kinds of synchronization primitives that guarantee no race. With scanning 10x faster this shouldn't be a problem in practice. I like to get back to each process trying to update the cache and possibly discarding its result if another process already did...After this, I think we should fix the relocatable feature to not touch mmaped cache files. Here's my proposed approach:If no one has comments, I like to merge this and get it out for testing in the wild.Hi everyone,I have a proposed patchset speeding up fontconfig scanning by 10x, simply by not loading glyphs at all, and trusting fonts having correct cmap:
https://bugs.freedesktop.org/show_bug.cgi?id=64766#c56
https://bugs.freedesktop.org/show_bug.cgi?id=101889#c17 _________________
Fontconfig mailing list
Fontconfig@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fontconfig
--
behdad
http://behdad.org/
http://behdad.org/
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
