Revert "[Indic/GSUB] Ignore context when matching would_apply()"
This reverts commit 24dd4e5674
.
Oops. My bad. The change _regressed_ Malayalam test suite, not
improved it. I'll redo it, differentiating between old-spec and
new-spec cases.
This commit is contained in:
parent
24dd4e5674
commit
1f2bb172fe
|
@ -1066,11 +1066,9 @@ static inline bool chain_context_would_apply_lookup (hb_would_apply_context_t *c
|
||||||
const LookupRecord lookupRecord[],
|
const LookupRecord lookupRecord[],
|
||||||
ChainContextApplyLookupContext &lookup_context)
|
ChainContextApplyLookupContext &lookup_context)
|
||||||
{
|
{
|
||||||
/* The MS Indic specs say "...all classifications are determined ... using context-free substitutions."
|
return !backtrackCount
|
||||||
* However, testing shows that MS's Malayalam shapers (both old and new), "match" even if there is no
|
&& !lookaheadCount
|
||||||
* zero-context rule. We follow. Hence the commented out line. */
|
&& would_match_input (c,
|
||||||
return /* !backtrackCount && !lookaheadCount && */
|
|
||||||
would_match_input (c,
|
|
||||||
inputCount, input,
|
inputCount, input,
|
||||||
lookup_context.funcs.match, lookup_context.match_data[1]);
|
lookup_context.funcs.match, lookup_context.match_data[1]);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue