Behdad Esfahbod
Behdad Esfahbod
> This is how that same sequence renders in Terminal.app: >  Looks obviously a different font.
I'm far removed from bidi algorithm right now to know what the expected output is.
`.ico`? :)))
Obviously I think what we are doing in HarfBuzz is the best way to interpret Unicode with OpenType. I've made all those decisions with @jfkthame.
Here. A purely demonstrative example: Imagine you have a rule that ligates C,D but only if preceded by A,B glyphs. That is, A,B,[C,D] is the sequence with A,B part being...
> I had originally thought (and blogged) that I could use the HarfBuzz UNSAFE_TO_BREAK flag, but a careful read of that issue reveals that it is overly optimistic. I will...
Michael: Your `safe_to_split` is what HarfBuzz calls `!UNSAFE_TO_BREAK`. The proposed `!UNSAFE_TO_CONCAT` is closer to your `safe_split_mutate_after/before` combined.
> Michael and Behdad both have the understanding of my original concern right, the ~safe_split_mutate~ [ETA: see below] predicate is a universal quantification, which is what we want. Actually for...
> But on the other hand, potential reshaping after adding a hyphen is very similar to the guarantee needed for general mutation, so I don't immediately see any useful way...
I've given this a try in https://github.com/harfbuzz/harfbuzz/pull/3297 now.