I’ve noticed this with several different files now. I initially dismissed this was an issue with the file or specific setup, but the repeat occurrence suggests this is a reproducible bug, even though I have not figured out what exactly causes it (v3401).
As per intention, the fileName set without file extension:
The error:
Version:
Now, the really peculiar thing is that using “Foobar-Regular.otf” as fileName, including the file extension, will successfully export “Foobar-Regular.otf.otf” — so while the appending of the export-chosen file extension works, the export fails altogether when the fileName does not include a file extension (as it correctly should not include).
This essentially leaves the fileName custom parameter unusable atm.
What is even more odd is that I’ve had at least three files where this happens. Yet, the attached minimal test case, does not fail but works as intended without exhibiting the issue. So there is something else circumstantial about the files that causes this error.
Any ideas what is causing this or how to debug this further?
New Font.glyphs (11.1 KB)
