SFC works by examining all files that are within the selected source folder, regardless of type. By checking various parameters in the file, it determines if the file is a valid TrueType font file. Because it does not depend on file extensions, it can find font files that have incorrect or missing extensions. This is especially useful if you have large numbers of fonts that you are importing from another platform, such as a Macintosh, where file extensions are not used. This program, however, does not convert fonts between platforms; they must be PC type files.
Only valid TrueType fonts are added to font collections. PostScript Type 1 and Type 3 fonts are ignored, including all of the auxiliary files .PFB, .PFM, and AFM. Old style windows bitmapped fonts with a .FON extension are also ignored.
TrueType font collections, with a “.ttc” extension can be added. No matter how many fonts the file contains, only one catalog entry will be generated, based on the first font found in the file. However, you can have a look at all of the fonts in the file by using the View function.
OpenType files may contain TrueType or Postscript fonts. If the file contains a TrueType font it is processed like any other TrueType font. If it contains a PostScript font, it can be renamed, added to a collection, and installed, but it cannot be viewed, either in a catalog or in the View function. This is because Windows lacks native capability for displaying PostScript fonts.Font Names
When fonts are installed in Windows, the system extracts the family name from the font file and uses that name to classify the font. Other information within the font file tells the system what the style (Bold, Italic, etc.) of the font is. If you add more fonts from the same family, the system notes the new style and adds it to the family. The file name is not relevant to this identification process. This is what allows SFC to change the file names and still have the fonts function within Windows. You can now make the file names more meaningful.
Serious Font Collector opens each font file, finds the font name that Windows uses in application menus, and uses that name as the base for the new file name. By setting certain options you can modify this name, by removing the terms “Regular” or “Normal”, for example. If duplicate names are found you have the option of skipping or renaming the file, before it is copied into the collection.
The only change that SFC makes to the font files is the name. No changes are made to the internal structure of the font file. As fonts are added to collections, the font files are copied to the collection location. The original font files are not affected. If a file already has a valid file extension (.ttf, .ttc, etc.), that extension is used for the copied file, as well. If the file did not have an extension, or if the extension was incorrect, the extension “.ttf” is appended to the file name.