It’s something that users in my FDK workshops sometimes run into:
macOS seems to append a .txt to any file, even if no extension is explicitly given.
To reproduce this behavior, create a new file in BBEdit, and save it without assigning an extension (I’ve been in touch with BBEdit about this, who confirmed this is happening on the OS side).
This leads to unexpected errors with file names as GlyphOrderAndAliasDB.txt, FontMenuNameDB.txt, fontinfo.txt, etc.
I wonder if we should allow a .txt suffix?
It’s something that users in my FDK workshops sometimes run into:
macOS seems to append a
.txtto any file, even if no extension is explicitly given.To reproduce this behavior, create a new file in BBEdit, and save it without assigning an extension (I’ve been in touch with BBEdit about this, who confirmed this is happening on the OS side).
This leads to unexpected errors with file names as GlyphOrderAndAliasDB.txt, FontMenuNameDB.txt, fontinfo.txt, etc.
I wonder if we should allow a .txt suffix?