On Fri Mar 20 14:47:36 2026 +0000, Paul Gofman wrote:
More exactly, there can be glyphs without color which can be rendered through normal glyph run, but the color glyphs cannot be rendered this way at all, not just that they would loose the color. Sure, layers won't be accessible through cmap, but glyphs that are accessible will still work. We could reject anything that has COLRv1 data in it, like you did, but that might reject otherwise usable font. With COLRv0 the logic is simple - for IsColorFont() application should be using Translate*, if application is not aware, it can render as before. Since we don't support COLRv1, is it a problem to simply not report as a color font, and let it render as is?
In practice, it was my impression that nothing is using COLRv0 except for Segoe UI on Windows, and COLRv1 is will always be preferred for newer fonts. Best way would be to test this particular font on older Windows builds without COLRv1 support, like Windows 8/10, and match that. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10388#note_133055