On Mon, Sep 16, 2024 at 9:54 PM Dominik Röttsches <drott@xxxxxxxxxxxx> wrote: > I will work on the Fontations functions in parallel to my work on > shipping Fontations in Chromium and completing the proposed change > will take a bit of time, but if you're ready to have the existing bits > as experimental code in the main branch, I can polish the existing > code (as shown in the demo section of my original mail) and break it > into reviewable PRs, behind the default-off buildflag. The changes > contain an extra CI configuration to build them as well, so that > breakage is avoided. Sure. I look forward to your contribution. > Yes, I agree with Behdad: I will try to produce patterns that match > FreeType for font formats supported by Fontations, which are > SFNT-based formats, OpenType/TrueType. Bitmaps fonts such as SBIX, > CBDT/CBLC are supported. There's limited EBDT/EBLC support in > Fontations - I can't say yet if there are metadata mismatches between > FreeType and Fontations for those. > > I assume that any cache mismatch would mainly (only?) be a problem if > in testing we would dynamically switch between backends. If they provide the same thing, that's good then. However, Cache files could be shared and be used on containers. they could use different backends. So if there is any difference causing incompatible behavior no matter what they switch dynamically or not, we may need to fix it. > > Dominik -- Akira TAGOH
