[hmd, hmz, ywqa, yna] Kern specific combinations

[cheuk879]

For 16F16..16F19, kerning at S position is too lax in build 222:

Users want tighter kerning as in build 194 (ignore vertical positioning):

For 16F1A..16F1B & 16F3D..16F3E combined with asp or with 16F57..16F58, they want it even a little bit tighter than build 194.

[jvgaultney]

OK - well then I'll revert my change from 16 July. [lpo] will be less happy with this. We'll have to see if we can address their desire for 'half-kerning' in a later release.

Kerning for specific combinations (such as 16F1A+16F57) will require a separate set of OT kerning lookups, as we can't just adjust APs to do it because it's specific to that context. IOW if we move the AP on the cons then all vowels will move and some will get too close and touch. If we move the AP on the vowel then it will be too close and touch other cons. Specific contextual kerning will need to wait until a later release after 1.0.

[jvgaultney]

16 July change reverted. Will leave this open and rename it to reflect need to kern specific contextual combinations.

[cheuk879]

Per build 245, for [hmd] no kerning is seen for asp when V is at S/F (red syllables): It is certain that asp should tuck in when V is at S pos, & this should be fixed for v1.0. For V at F pos, we're awaiting user confirmation & will post update asap.

[mhosken]

For which languages does the aspiration mark not tuck (or tuck, I'll take explanation either way).

[cheuk879]

[hmd] has just confirmed that asp should tuck regardless of V position.

Only [hmd, hmdd, hmz] use asp with C's open on the top-right. Of these, [hmd, hmz] want tucking; [hmdd] does not.

[jvgaultney]

[hmz, hmdd] good now. [hmd] still a problem in 258:

[jvgaultney]

Confirmed that asp is now tucking for [hmd] in build 261:

Since that was the only v1.0 problem here I'll remove this issue from release 1.0 but leave ti open for the future.