Font Filenames

[Finii]

At the moment all the font filenames contain blanks, i.e. Inconsolata Regular Nerd Font Complete Mono Windows Compatible.otf.

Usually font files do not have blanks in them.

Lets see (at root of repo):

$ ls src/unpatched-fonts/**/*.[ot]tf | grep ' ' | wc -l
58
ls src/unpatched-fonts/**/*.[ot]tf | grep -v ' ' | wc -l
690

This means only less then 10% (58) of all source fonts contain blanks, 690 do not.

And what we produce, ignoring the 4 variants for each font:

$ echo "`ls patched-fonts/**/*.[ot]tf | grep ' ' | wc -l` 4 / p" | dc
744
$ echo "`ls patched-fonts/**/*.[ot]tf | grep -v ' ' | wc -l` 4 / p" | dc
0

I would change that so the filename is (like usual) the Postscriptname and not the Human-readable-name (Fullname).
That would also exclude problematic characters from the filename.

The impact might be rather big, as renaming is always an issue, but these blank-embedded-filenames bugger me since ancient times ;)

[Finii]

Appendix with relevant code snippet in font-patcher HEAD:

self.sourceFont.generate(self.args.outputdir + "/" + self.sourceFont.fullname + self.extension, flags=(str('opentype'), str('PfEd-comments')))
print("\nGenerated: {}".format(self.sourceFont.fontname))

(.fontname is the PS name)

We generate with ' ' but report without ;-D, should probably the other way round.

[Finii]

Issue mentioned by @nobuyukinyuu in #632; this change would solve illegal file names.

Which characters are allowed in filenames?
See Answer 1 on SO or this website centric view on the topic here

Postscript names allow

The name string must be restricted to the printable ASCII subset, codes 33 to 126,
except for the 10 characters '[', ']', '(', ')', '{', '}', '<', '>', '/', '%'

There is nothing in fontforge to prevent illegal file names.

Edit: Completely reversed the content of this comment :-D

[Finii]

• Feature request: organize content of release archives differently #919