X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=FORMATS%2FFLT.txt;h=bf7ea152a8a187129047eaa4d4e6aac1a04ac328;hb=374579adf0e0e307ee42b6a29a6788aeafd3ad8e;hp=475b9a9afc6218f2922e30cfc7a95379206b1c59;hpb=f3cd9bd33ed4148ef3f79025fa957adba434cbab;p=m17n%2Fm17n-db.git diff --git a/FORMATS/FLT.txt b/FORMATS/FLT.txt index 475b9a9..bf7ea15 100644 --- a/FORMATS/FLT.txt +++ b/FORMATS/FLT.txt @@ -102,7 +102,7 @@ STAGE ::= CATEGORY-TABLE ? GENERATOR CATEGORY-TABLE ::= '(' 'category' CATEGORY-SPEC + ')' CATEGORY-SPEC ::= '(' CODE CATEGORY ')' - | '(' CODE CODE CATEGORY ')' + | '(' CODE CODE CATEGORY ')' CODE ::= INTEGER @@ -121,8 +121,8 @@ whose code falls between the two @c CODEs. GENERATOR ::= '(' 'generator' RULE MACRO-DEF * ')' RULE ::= REGEXP-BLOCK | MATCH-BLOCK | SUBST-BLOCK | COND-BLOCK - | DIRECT-CODE | COMBINING-SPEC | OTF-SPEC - | PREDEFINED-RULE | MACRO-NAME + | DIRECT-CODE | COMBINING-SPEC | OTF-SPEC + | PREDEFINED-RULE | MACRO-NAME MACOR-DEF ::= '(' MACRO-NAME RULE + ')' @endverbatim @@ -215,8 +215,8 @@ MATCH-BLOCK ::= '(' MATCH-INDEX RULE * ')' MATCH-INDEX ::= INTEGER @endverbatim -MATCH-INDEX is an integer specifying a parenthesized subexpression -recoded by the previous @c REGEXP-BLOCK. If such a subexpression was +@c MATCH-INDEX is an integer specifying a parenthesized subexpression +recorded by the previous @c REGEXP-BLOCK. If such a subexpression was found by the previous regular expression matching, this rule executes @c RULEs temporarily limiting the current run to the matched part of the subexpression. The matched part is consumed by this rule. @@ -227,10 +227,10 @@ If this is the first rule of the stage, @c MATCH-INDEX must be 0, and it matches the whole current run. @verbatim -SUBST-BLOCK ::= '(' SOURCE-PATTERN RULE * ')' +SUBST-BLOCK ::= '(' SOURCE-PATTERN RULE * ')' SOURCE-PATTERN ::= '(' CODE + ')' - | (' 'range' CODE CODE ')' + | (' 'range' CODE CODE ')' @endverbatim If the sequence of codes of the current run matches @c SOURCE-PATTERN, @@ -243,8 +243,9 @@ zero. The second form specifies a range of codes that should match the first glyph code of the code sequence. In this case, this rule sets the -default code-offset to the first glyph code minus the first @c CODE in @c -SOURCE-RANGE. +default code-offset to the first glyph code minus the first @c CODE +specifying the range. + If no match is found, this rule fails. @@ -287,7 +288,7 @@ For @c LANGSYS, @c SYMBOL specifies a Language System tag name. If @c LANGSYS is omitted, the Default Language System table is used. -For @c GSUB-FEATURES, each @c SYMBOL specifies a GSUB Feature tag name +For @c GSUB-FEATURES, each @c SYMBOL in @c FEATURE LIST specifies a GSUB Feature tag name to apply. '*' is allowed as the last item to specify all remaining features. If @c SYMBOL is preceded by '~' and the last item is '*', @c SYMBOL is excluded from the features to apply. If no @c SYMBOL is @@ -361,13 +362,13 @@ The next glyph is drawn so that these two reference points align. @c OFFSET specifies the way of alignment in detail. If it is '.', the reference points are on the same position. -@c XOFF specifies how much the X position of the next reference point -should be shifted to the right ('<') or left ('>') from the previous -reference point. +@c XOFF specifies how much the X position of the reference point of +the next glyph should be shifted to the right ('<') or left ('>') from +the previous reference point. -@c YOFF specifies how much the Y position of the next reference point -should be shifted upward ('+') or downward ('-') from the previous reference -point. +@c YOFF specifies how much the Y position of the reference point the +next glyphshould be shifted upward ('+') or downward ('-') from the +previous reference point. In both cases, @c INTEGER is the amount of shift expressed as a percentage of the font size, i.e., if @c INTEGER is 10, it means @@ -393,9 +394,9 @@ is drawn with font F1 while the preceding sequence S0 unconditionally requires font F0. @verbatim - sequence S0 S1 - currently used font F0 F1 - usable font(s) F0 F1 + sequence S0 S1 + currently used font F0 F1 + usable font(s) F0 F1 @endverbatim Sometimes, however, a clear separation of sequences is not possible. @@ -403,9 +404,9 @@ Suppose that the preceding sequence S0 can be drawn not only with F0 but also with F1. @verbatim - sequence S0 S1 - currently used font F0 F1 - usable font(s) F0,F1 F1 + sequence S0 S1 + currently used font F0 F1 + usable font(s) F0,F1 F1 @endverbatim In this case, glyphs used to draw the preceding S0 may affect glyph