Accepting contributions for Rust-based font indexing?

[Behdad Esfahbod]

Hi Keith,

Good to hear from you.

On Sun, Sep 8, 2024 at 8:28 AM Keith Packard <keithp at keithp.com> wrote:

> From: Dominik Röttsches <drott at chromium.org>
> Date: Fri, 06 Sep 2024 18:11:05 +0300
>
> > * Do you see dependencies other than indexing that require FreeType?
> > (FreeType specific API functions [3] would need to be compiled out in
> > the Fontations build).
>
> Many fonts lie about their code point coverage, so fontconfig has to
> examine each glyph outline to see if they generate any ink.


Umm. As part of significantly speeding up fontconfig we removed that logic
in 2017. See:

  https://bugs.freedesktop.org/show_bug.cgi?id=64766#c47

As noted there by Khaled, the check was actually problematic for a style of
font design that would want to include eg. a-acute in the cmap, but
decompose it via GSUB. Such fonts used to have to include a non-empty
outline for a-acute. Not with this change.

So, there's water under that bridge for better or worse. I don't remember
we ever receiving a complaint or bug report about it.

 b
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig/attachments/20240908/43f093c7/attachment.htm>