Open a new font file, and name it in howsoever many ways so that it exists only as itself?
Well, not wishing to be pedantic, just precise, one does not “open” a “new” font file, as opening a file is done on a file which already exists.
The following is what I do. Suppose that, for example, I wish to produce a font named Ginevra (incidentally, the name comes from a painting by Leonardo da Vinci, I needed to choose a name for the font in this example and that just sprang to mind.).
Use File | New…
Then in the dialogue panel type the name Ginevra then click OK.
Use File | Save As…
Choose a file name. Font Creator 5.0 offers a name with an extension of .ttf.
Now, I have no justification for the following, it is just something I feel happiest with, maybe with or without justification, but I remember the old DOS (disc operating system) days and that Windows sits on DOS, so I always use no more than eight characters for a file name and I use capitals and digits and the extension is .TTF in capitals.
Now, that is the basics.
The name of the font above was Ginevra. The name of a font can be up to about 28 characters including spaces though there may be some restrictions on which characters can be used. The 26 letters of English, both uppercase and lowercase, and digits are all suitable.
If I were trying to produce a font named, say, Buttercup Fields, I would start with a new font with a font name of Buttercup Fields 001 and I would save it in a file named BUTTE001.TTF.
I would add some glyphs and use File | Save as I proceeded. When starting the next session, maybe after lunch or the next day I would use File | Open and open BUTTE001.TTF. I would then use File | Save As… and use BUTTE002.TTF. I would then use Tools | AutoNaming… and use Buttercup Fields 002 as the name of the font.
The saving is all to an ordinary directory, not to the C:\WINDOWS\FONTS directory. Windows uses the term folder for directory. I install a font for testing by copying from the directory where the font has been developed to the C:\WINDOWS\FONTS directory. Actually, this PC has a file partition system on it and Font Creator 5.0 is in the J:\ drive, so copying from the development directory to the C:\WINDOWS\FONTS directory does not try to remove the file from the development directory.
When I had got to a stage where I felt that the font was ready to publish on the web I would do the following. Suppose for this example that that stage was reached with BUTTE005.TTF with a font name of Buttercup Fields 005.
I would then produce Buttercup Fields in a file with a name such as BUTTERFI.TTF using the fact that I have derived this from the 005 version to designate the Buttercup Fields font as version 0.05.
I would then delete the unused glyphs from BUTTERFI.TTF and then use Format | Settings | Ranges to calculate both ranges.
BUTTE005.TTF would still have ready-mapped spaces for adding other characters. So any future development would start by copying BUTTE005.TTF to a new file BUTTE006.TTF and using the font name Buttercup Fields 006 during development. This means that I would not alter existing finished work, just in case later additions need to be rethought or abandoned.
I could install Buttercup Fields 006 for testing without needing to remove Buttercup Fields from the C:\WINDOWS\FONTS directory. Such removal would only be necessary when I wanted to publish an updated version of Buttercup Fields. At that time I would delete BUTTERFI.TTF from the C:\WINDOWS\FONTS directory. I would rename the then present version of BUTTERFI.TTF in the working directory as BUTTERFI005.TTF. It would still have the font name Buttercup Fields within it, yet as it is not installed, that does not matter and indeed is good as it is an archived version of what has been published previously.
That is not the only way to organize file names and font names. It is just a way that I devised as I was starting to get into problems and muddle: since using this method I have found it to be very satisfactory.
William Overington