sounds good to me though, not sure if there are any apps relying on this behavior to look up PUA coverage on a font. so if ignoring it on FcFontSort() works enough for Chrome, that may be safer way. On Sat, Dec 16, 2017 at 2:44 AM, Behdad Esfahbod <behdad@xxxxxxxxxx> wrote: > Hey, > > Triggered by a Chrome bug: > > https://chromium-review.googlesource.com/c/chromium/src/+/829378 > > Since PUA has no meaning outside of a specified font, I think we should > exclude that range from either a font's charset, or ignore it during > FcFontSort(). > > Thoughts? > > -- > behdad > http://behdad.org/ > > _______________________________________________ > Fontconfig mailing list > Fontconfig@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/fontconfig > -- Akira TAGOH _______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/fontconfig
