There should be option in generate_featurefile to either export gpos or gsub lookups
This is specifically case for Lohit2 project. As we are working for reusable open type tables.
Here one very important thing to note is, GPOS tables are specifics to fonts. So if we are applying feature file on existing font it is no need to apply gsub tables.
So taking this into consideration, might be good to have option for exporting either gpos or gsub rules.
Doesn't that mean making an issue for fontforge to change fontforge.font.generateFeatureFile() to allow that level of control? :)
It is good to have feature :) But i think there should be other options available in fontforge scripting stuff to only export GSUB tables. In Lohit presently though we are generating both GPOS and GSUB tables feature file, we are only applying GSUB tables while generating fonts, so this is minor issue.
font.generateFeatureFile() already accepts lookup name as parameter, so that we can generate featurefile for that lookup. But if it accepts array of lookups then we can generate two feature files separately.
On Mon, Feb 17, 2014 at 9:39 AM, Pravin Satpute [email protected]:
It is good to have feature :) But i think there should be other options available in fontforge scripting stuff to only export GSUB tables. In Lohit presently though we are generating both GPOS and GSUB tables feature file, we are only applying GSUB tables while generating fonts, so this is minor issue.
— Reply to this email directly or view it on GitHubhttps://github.com/aravindavk/fontforge-python-cookbook/issues/2#issuecomment-35227610 .
Regards Aravinda | ಅರವಿಂದ http://aravindavk.in
Fontforge gui do not anymore offer option to export feature file. it was a very useful feautre to inspect bug introduced in lookups in between versions