PDF::API3::Compat::API2::Basic::TTF::GSUB - Module support for the GSUB table in conjunction with TTOpen
Handles the GSUB subtables in relation to Ttopen tables. Due to the variety of different lookup types, the data structures are not all that straightforward, although I have tried to make life easy for myself when using this!
The structure of a GSUB table is the same as that given in PDF::API3::Compat::API2::Basic::TTF::Ttopen. Here we give some of the semantics specific to GSUB lookups.
This is a string taking one of 4 values indicating the nature of the information in the ACTION array of the rule:
The action contains a string of glyphs to replace the match string by
The action array contains a list of lookups and offsets to run, in order, on the matched string
The action array is an unordered set of optional replacements for the matched glyph. The application should make the selection somehow.
The action array is empty (in fact there is no rule array for this type of rule) and the ADJUST value should be added to the glyph id to find the replacement glyph id value
This indicates which type of information the various MATCH arrays (MATCH, PRE, POST) hold in the rule:
The following table gives the values for ACTION_TYPE and MATCH_TYPE for each of the 11 different lookup types found in the GSUB table definition I have:
1.1 1.2 2 3 4 5.1 5.2 5.3 6.1 6.2 6.3 ACTION_TYPE o g g a g l l l l l l MATCH_TYPE g g c o g c o
Hopefully, the rest of the uses of the variables should make sense from this table.
Asked by the superclass to read in from the given file the indexth subtable from lookup number lookup. The file is positioned ready for the read.
Returns the table type number for the extension table
Passed the filehandle to output to, suitably positioned, the lookup and subtable index, this function outputs the subtable to $fh at that point.
Martin Hosken Martin_Hosken@sil.org. See PDF::API3::Compat::API2::Basic::TTF::Font for copyright and licensing.