When I create a Chaining Context, the resulting lookup table always appears to be using ChainContextSubstFormat3. Is there a way for users to pick an alternative format like ChainContextSubstFormat1 or ChainContextSubstFormat2 (that is provided it is possible)?
Does Font Creator support data contained in GDEF tables which ChainContextSubstFormat2 uses?
I realize that for most use case, having the ability to select the encoding of these tables might not be needed / relevant. However, in my case I am designing a text layout engine where I use Font Creator Pro to create font files for testing these different formats to make sure my tool reads and processes them correctly.
Get help with FontCreator here. Please do not post feature requests or bug reports here.
1 post • Page 1 of 1