This came up in the context of omitting DSIG tables, while discussing with @typemytype .
The makeotf help reads:
Note that options are applied in the order in which they are
specified: "-r -nS" will not subroutinize a font, but "-nS -r" will
subroutinize a font. See the makeotf user guide at
https://adobe-type-tools.github.io/afdko/MakeOTFUserGuide.html for
format and contents of the fontinfo and project files.
This is what currently happens:
afdko makeotf -omitDSIG -r – generates DSIG table
afdko makeotf -r -omitDSIG – does not generate DSIG table
Skipping over a supplied option does not seem to be very logical (and is also not in line with other command line tools).
IMO this just smells like a bad parser. Would it be reasonable to overthink the reliance on argument order?
This came up in the context of omitting DSIG tables, while discussing with @typemytype .
The
makeotfhelp reads:This is what currently happens:
afdko makeotf -omitDSIG -r– generates DSIG tableafdko makeotf -r -omitDSIG– does not generate DSIG tableSkipping over a supplied option does not seem to be very logical (and is also not in line with other command line tools).
IMO this just smells like a bad parser. Would it be reasonable to overthink the reliance on argument order?