[Fontconfig] Don't do font fallback for PUA chars?
behdad at behdad.org
Mon Dec 18 19:28:38 UTC 2017
On Sun, Dec 17, 2017 at 10:19 PM, Akira TAGOH <akira at tagoh.org> wrote:
> sounds good to me though, not sure if there are any apps relying on
> this behavior to look up PUA coverage on a font.
Hummm. You're right. The only way would be to NOT include them in charset.
But I guess that would mean not rendering any PUA chars in Pango then.
> so if ignoring it on
> FcFontSort() works enough for Chrome, that may be safer way.
Thinking about it, ignoring in FcFontSort() might help but is not
sufficient. Clients still should know now to go look for fallback for PUA
chars, which Chrome does now, and doesn't need any fontconfig changes.
Yeah, maybe this is a nonissue for fontconfig.
> On Sat, Dec 16, 2017 at 2:44 AM, Behdad Esfahbod <behdad at behdad.org>
> > 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 at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/fontconfig
> Akira TAGOH
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Fontconfig