[MPEG-OTSPEC] lookup processing and 'chws', 'vchw'

[Koji Ishii]

>
> > On Aug 19, 2020, at 08:55, Peter Constable <pgcon6 at msn.com> wrote:
> >  :
> > So, the “not consume” clause in the description of ‘chws’ and ‘vchw’
> would seem to be consistent with the rest of the spec _provided that the
> GPOS type 2 lookups do not act on the second glyph_. However, the
> descriptions for these features don’t give any indication that that
> constraint should be followed.
> >
> > Thus, I’d like to know if such a constraint on type 2 lookups used for
> ‘chws’/’vchw’ was intended but somehow left out of the descriptions (hence
> should be added)? Or was it really intended (as it appears on the surface)
> that type 2 lookups for ‘chws’/’vchw’ should be allowed to act on the
> second glyph but that clients should _exceptionally_ not consume the second
> glyph in this case?


Ken knows the text best but I think the answer is the former; there's no
intention to add an exceptional behavior. The intention is to use existing
code without modifications. Ken and I were testing this feature using
existing browsers:
https://kojiishi.github.io/cspc/test.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200820/f1f6e741/attachment-0001.html>