compare two font files
compares two font files, which may be in any format
It will notice the following differences:
Characters are present in one font but not in the other.
Characters are present in both fonts but have different sets of outlines
The outlines may be compared so that only exact matches are accepted, or
so that a fuzzier match is used.
Similarly references may need to match exactly, or may be matched after
This fuzzy comparison is useful when comparing truetype and postscript
fonts, or when comparing a font with references to one without.
The postscript hints or truetype instructions are different.
The font names (the truetype `name' table) differ.
The kerning (and other `gpos' information) differs.
The ligatures (and other `gsub' information) differ.
Any bitmap strikes present in one font but not in the other.
Any bitmap characters present in one strike of one font but in the
equivalent strike of the other.
Any bitmap characters which differ.
Provide a description with a list of the available options.
Suppress the reporting of hint/instruction differences.
Suppress the reporting of kerning (and other `gpos') differences.
Suppress the reporting of ligature (and other `gsub') differences.
Suppress the reporting of name string differences.
Suppress the reporting of bitmap differences.
Require outlines to match exactly.
Warn if the outlines/references are slightly different.
- --merge outfile
Store a merged version of the two fonts into the specified output file.
The merged data will be based on
as well as any characters present in
but not in
will be added, and the outlines of
will be placed in the background.
Finally, for any characters with different outlines or references the
background of the character will contain the outlines from
(references will be unlinked into outlines and those outlines also will be
Display the usage description.
Display the current version.
Copyright (C) 2000-2006 by George Williams ([email protected]
Manual page heavily rewritten and modified to use standard
macros by R.P.C. Rodgers ([email protected]
), 23 October 2002.