Closed jvgaultney closed 4 years ago
We are hitting the limits of opentype not having spacing mark attach. But I will see what I can do.
GB, Martin
On Mon, 19 Aug 2019, 21:52 Victor Gaultney, notifications@github.com wrote:
When an asp is followed by a V@W, something is miscalculating the space to the next cluster. It's most evident when the waist tuck is large or the V is thin. It looks like the space to the next glyph is being calculated in reference to the V sidebearing even if the asp is further to the right. However that's not happening in line 3, which looks correct.
I've discovered these when going through the hmd wordlist. I've isolated examples in a new hnd_issues.htxt file. Here's the result:
[image: image] https://user-images.githubusercontent.com/4226750/63274631-0834b400-c298-11e9-8bbc-06c03987d8d2.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/silnrsi/font-shimenkan/issues/81?email_source=notifications&email_token=ABLMO3O7ACIFR3HFKMMIVDLQFKXSFA5CNFSM4INCSBH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HGAHBLQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLMO3NCA7QZT6YIT5Z5CALQFKXSFANCNFSM4INCSBHQ .
Another situation that might be easier if we made cons+asp ligatures? We'd need two more version of each cons (tucked and untucked). (That would be definitely post 1.0 though)
Confirmed fixed in build 285
When an asp is followed by a V@W, something is miscalculating the space to the next cluster. It's most evident when the waist tuck is large or the V is thin. It looks like the space to the next glyph is being calculated in reference to the V sidebearing even if the asp is further to the right. However that's not happening in line 3, which looks correct.
I've discovered these when going through the hmd wordlist. I've isolated examples in a new hnd_issues.htxt file. Here's the result: