|
Re-unite PostScript-families In the next step we will reunion postscript-families. Danger: This option requires you to have a valid database, that means: You have created a MySQL-Database of your ~/fontbase-folder and not touched any file therein
later!"Reuniting" means, if you have a file 'font.pfm' and another file 'font.pfb', but they are not in the same folder, each file will be copied to the other one. This normally should not happen, but it does so i.e. when you get fonts from not-so-well treated sources. If you are sure your fonts are already well organized, skip this step, also if you just have one-file-fonts like TrueType and OpenType, but no PostScript at all. The idea is: If an orphan is here and another one is there, they belong together. This may be wrong, but hey, they were already broken before. ;-) |
Note that there will be done nothing harmful, if you have duplicate-named fontfiles in different folders, but their content doesn't match. This means, spoken clearly: We try to rescue broken families. We don't break already united ones, maybe we add wrong files, but we don't overwrite correct ones. Already broken fonts might be repaired, they might be broken again. The worst thing may happen to not-broken families is that additional files may appear in their folder. Start fontlinge_reunion.
The found orphan-files will be copied where they might fit.Note: When having more than two orphans of one familiy, the familiy might "grow" at runtime. In that case it might be necessary to "reunion" multiple times. Recreate the database before doing so. |
|
Quicktip: Danger! Read text above!fontlinge_reunion |