pyftsubset incorrect documentation for --layout-features

It seems that the documentation for --layout-features='*' should be --layout-features=* (no single quotes). I’m guessing that other similar documentation in the lines above also needs updating.

The result of --layout-features=‘*’ was to silently drop all GSUB entries, which caused me some head-scratching.

[ClintGoss]

Here is testing using these command (I have to write “asterisk” since that is a metacharacter … sigh)

echo --layout-features=‘asterisk’ and echo --layout-features=“asterisk”

(I cannot easily test the pyftsubset command directly, since it is exec’ed by a perl script driven by an Excel spreadsheet, fired from a make script … that takes 9+ hours to fully run - this is a big font project).

Windows Console aka Command Prompt (cmd.exe) returns --layout-features=‘asterisk’ and --layout-features=“asterisk”. These will fail with pyftsubset.

Windows PowerShell returns --layout-features=asterisk for both single and double quote version, so I would expect it to succeed with pyftsubset.

The shiny new Windows Terminal, as expected, emulates Console and Powershell correctly: in Command Prompt mode behaves like Windows Console (i.e would fail with pyftsubest) and in PowerShell Prompt mode behaves like Windows Powershell (i.e. would be OK with pysftsubet).

In Azure Cloud Shell … first time trying this … go to a web site? Enter an authentication code?? Sign in??? Establish my cloud based development environment??? sorry … too much of a rabbit hole to test this mode.

So … its only Windows Console / Command Prompt that fails, and I expect by the echo test that it would fail for both single and double quotes.

[madig]

What a pipeline.

What I mean is that argument quoting is fraught with peril on Windows due to a fundamental mistake in API design. You need to check every layer if it passes the quotes on correctly. See e.g. https://docs.python.org/3/library/subprocess.html#converting-an-argument-sequence-to-a-string-on-windows