This does not apply to the context matchings.

This regresses tests right now.  And we are not sure whether this is
the right thing to do for GPOS.  But we'll figure out.

Enable by setting envvar:

  HB_OT_INDIC_OPTIONS=uniscribe-bug-compatible

Plus, LeftMatra+Halant "feature".

As can be seen in: U+092B,U+093F,U+094D

Uniscribe doesn't move the Halant, we do.  And do a broken job of it now.

Needed for upcoming changes to GSUB/GPOS mask matching.

This is to incorporate it into GSUB/GPOS processing.

Not that the code makes any difference since the presence of ZWJ itself
causes the ligature to fail to match anyway.

Another 1000 down!

Yay!

Done.  I promise.

Makes debug output much more pleasant.

More to come, for APPLY, CLOSURE, etc.

We have varargs in the trace interface now.  To be used soon...

Fixed for Deva cases with two full-form consonants.  Failures **way** down.
Not much left to go :-).

We now check that the 'rphp' table exists before forming Reph, so
we don't need to comment out Ra for those scripts.

Hindi Wikipedia failures down to 6639 (0.938381%)!

The spec says: "[{M}+[N]+[H]]", and that's what Uniscribe implements.
We instead do: "{M+[N]+[H]}", which means we allow Nukta and Halant
after all Matras, not just the last one.  It makes more sense.

Uniscribe doesn't do it, but we want to do as it gives the Reph the
opportunity to interact with the Matras.  Test with mangal for example.
Sequence: <0930,094d,0915,094b,094d>
In test suite already.