You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MakeOTF.py script's main() function does not return a non-zero value to the calling shell when an exception occurs and the font was not built successfully. Currently all exceptions are handled and passed, so main always exits successfully:
in fontmake there's an optional FDKFeatureCompiler that calls makeotf as subprocess. That code is broken for many reasons, one of which is that it attempts to guess whether the build was successful from the messages printed to stdout, because the exit code is meaningless.
The text was updated successfully, but these errors were encountered:
adobe-type-tools/afdko#417
This way we support both the old and the new behaviour.
I also renamed the method from the deprecated setupFile_featureTables to buildTables
and removed the overridden __init__ as the 'mtiFeatures' argument is no longer used
by ufo2ft (one now needs to use a separate MTIFeatureCompiler class for those).
The MakeOTF.py script's main() function does not return a non-zero value to the calling shell when an exception occurs and the font was not built successfully. Currently all exceptions are handled and passed, so main always exits successfully:
afdko/afdko/Tools/SharedData/FDKScripts/MakeOTF.py
Lines 3063 to 3073 in 56befef
in fontmake there's an optional FDKFeatureCompiler that calls makeotf as subprocess. That code is broken for many reasons, one of which is that it attempts to guess whether the build was successful from the messages printed to stdout, because the exit code is meaningless.
The text was updated successfully, but these errors were encountered: