You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging issues around ligatures and ligature attachment, it would be very helpful to have the buffer serialization be able to output the ligature component and id for each glyph in the buffer.
I would be happy to code this up, but what fields do we want to call them? Do we simply extend --show-flags to include them? Do we want to output them as part of the text output?
The text was updated successfully, but these errors were encountered:
alerque
changed the title
[Feature Request]
[Feature Request] Provide debug info of ligature component and id for each glyph in buffer
Aug 21, 2023
It's hard to respond to 'various reasons'. But I will just say that my needs are, without trying to force the method of addressing them.
To know when a new value of ligature id or component is set on a glyph
To know the ligature ids and components when doing ligature attachment
The reason is that if I am trying to track down why a particular mark attaches to a different ligature component than the one expect, I need to know which component it thinks it is attaching to and how it got that idea in the first place. Since ligature components and ids are an internal concept to a shaping engine, there is no other way to get this information.
When debugging issues around ligatures and ligature attachment, it would be very helpful to have the buffer serialization be able to output the ligature component and id for each glyph in the buffer.
I would be happy to code this up, but what fields do we want to call them? Do we simply extend --show-flags to include them? Do we want to output them as part of the text output?
The text was updated successfully, but these errors were encountered: