7a0c5e1ca2
* First round of adding fea output No format tests but all test files give reasonable output so far. * Get existing tests working * Initial tests that work for fea2fea * Get more tests working Bug fixes and re-layout some tests to compare with fea2fea output. Ranges and name parameters are not optimised yet. * Handle vertical default values in fea2fea * Hide fea2fea differences in lookupflags * No reduce() in py3 so use a for loop
26 lines
699 B
Plaintext
26 lines
699 B
Plaintext
# OpenType Feature File specification, section 5.d, example 2.
|
|
# http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html
|
|
|
|
# A contiguous set of ligature rules does not need to be ordered in
|
|
# any particular way by the font editor; the implementation software
|
|
# must do the appropriate sorting.
|
|
|
|
# So:
|
|
feature F1 {
|
|
sub f f by f_f;
|
|
sub f i by f_i;
|
|
sub f f i by f_f_i;
|
|
sub o f f i by o_f_f_i;
|
|
} F1;
|
|
|
|
# will produce an identical representation in the font as:
|
|
feature F2 {
|
|
sub o f f i by o_f_f_i;
|
|
sub f f i by f_f_i;
|
|
sub f f by f_f;
|
|
sub f i by f_i;
|
|
} F2;
|
|
|
|
# In the resulting OpenType GSUB table (spec5d2.ttx),
|
|
# we expect to see only one single lookup.
|