Hi, (Replying here to follow up a concern) On Sat, Sep 7, 2024 at 2:36 AM Werner LEMBERG <wl@xxxxxxx> wrote: > > > >> I am curious to hear your thoughts on accepting contributions to > >> FontConfig that provide an alternative indexing code path and build > >> configuration that does not require FreeType, but instead uses the > >> Rust-based Fontations libraries [1] developed by Google Fonts. That sounds good to me. > > I believe this is an important and noble project to consider > > upstream. > > I agree. Using two different font backends could help improve > FontConfig by finding subtle bugs. It might even help FreeType – and > Fontations – fixing bugs, too. > > However, to allow such kind of testing I strongly suggest that > Fontation and FreeType can coexist in FontConfig, similar to HarfBuzz > that also allows multiple backends AFAIK. To do that, it needs to make sure that data in a cache is compatible no matter what backends are used to generate. Otherwise we may want to have some identifier in a cache filename to avoid breakage. > > > Werner -- Akira TAGOH
