peppidesu

> If I understand correctly, it's because the same font can provide different glyphs depending on what font-features are enabled. This is indeed the case. If for example the UI...

> does it resolve also #17784 ? Yes. Enabling and disabling ligatures works, but the ligatures are not always properly rendered.

@probably-neb all good!

> Looks like the problem is that `font_id_for_cosmic_id` is another path that updates `loaded_fonts_store` but does not push to `features_store`. i see, mb. I'll probably combine these lists into one...

I might have found the culprit, anyone correct me if I'm wrong: If you run the modified example as described in the issue description with `RUST_LOG=trace`, the following output appears:...

So here are my findings about this issue: - We need to know what characters sequences have associated ligatures. - We need to disregard unicode breakpoints that would break such...

In response to @jackpot51's comment in #392: This is a code snippet from the `build()` function for `ShapeSpan`: https://github.com/pop-os/cosmic-text/blob/eebdd01a8e0c4298d316c893e8ada683d396bec9/src/shape.rs#L805-L849 Here, the span is broken up into words based on the...