SFDDIFF(1) General Commands Manual SFDDIFF(1)NAME
sfddiff - compare two font files
SYNOPSIS
sfddiff [--help] [--ignorehints] [--ignorenames] [--ignoregpos] [--ignoregsub] [--ignorebitmaps] [--exact] [--warn] [--merge outfile]
[--usage] [--version] fontfile1 fontfile2
DESCRIPTION
The program sfddiff compares two font files, which may be in any format fontforge(1) can read. It will notice the following differences:
1) Characters are present in one font but not in the other.
2) Characters are present in both fonts but have different sets of outlines or references. 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 an unlink.
This fuzzy comparison is useful when comparing truetype and postscript fonts, or when comparing a font with references to one with-
out.
3) The postscript hints or truetype instructions are different.
4) The font names (the truetype `name' table) differ.
5) The kerning (and other `gpos' information) differs.
6) The ligatures (and other `gsub' information) differ.
7) Any bitmap strikes present in one font but not in the other.
8) Any bitmap characters present in one strike of one font but in the equivalent strike of the other.
9) Any bitmap characters which differ.
OPTIONS --help Provide a description with a list of the available options.
--ignorehints
Suppress the reporting of hint/instruction differences.
--ignoregpos
Suppress the reporting of kerning (and other `gpos') differences.
--ignoregsub
Suppress the reporting of ligature (and other `gsub') differences.
--ignorenames
Suppress the reporting of name string differences.
--ignorebitmaps
Suppress the reporting of bitmap differences.
--exact
Require outlines to match exactly.
--warn 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 sfdfile1, as well as any
characters present in sfdfile2 but not in sfdfile1 will be added, and the outlines of sfdfile2 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
sfdfile2 (references will be unlinked into outlines and those outlines also will be added).
--usage
Display the usage description.
--version
Display the current version.
SEE ALSO fontforge(1)
The HTML version of the fontforge manual at:
http://fontforge.sourceforge.net/
AUTHOR
Copyright (C) 2000-2006 by George Williams (gww@silcom.com). Manual page heavily rewritten and modified to use standard -man(5) macros by
R.P.C. Rodgers (rodgers@nlm.nih.gov), 23 October 2002.
8 April 2006 SFDDIFF(1)
Check Out this Related Man Page
MKEOT(1) EOT UTILITIES MKEOT(1)NAME
mkeot - generate Embedded OpenType
SYNOPSIS
mkeot font-file [ URL [ URL ... ] ] > EOT-file
DESCRIPTION
The mkeot command writes an EOT (Embedded OpenType) file on standard output that contains the given font file (OpenType or TrueType) and
the given URLs.
mkeot handles TrueType files, OpenType files with TrueType outlines, and OpenType files with Postscript outlines. (Technically: all files
with the "sfnt" format.) However, Microsoft's Web browser Internet Explorer (version 8) cannot handle Postscript outlines. To use EOT files
with that browser, OpenType files with Postscript outlines must be converted to TrueType files first. Several prgrams are able to do that,
including the free fontforge.
The URLs that are added to the EOT file list the Web pages on which the EOT font may be used. They act as prefixes, which means that, e.g.,
a URL such as http://example.org/foo enables a font not only for that precise page, but also for http://example.org/foo2 or http://exam-
ple.org/foo/bar or any other pages whose URL starts with the prefix.
The EOT specification allows EOT files without any URLs, but is not clear on the meaning of such a file. In practice, at least in Micro-
soft's Internet Explorer (version 8), an empty list of URLs means the font applies to no Web page at all.
EOT font are typically used for Web pages. To that end, a link (URL) to the EOT file must appear in the Web page's style sheet. A typical
rule in CSS looks like this:
@font-face {
font-family: My Fancy Font;
font-style: normal;
font-weight: normal;
src: url(http://example.org/fonts/fancy-roman.eot);
}
body {
font-family: My Fancy Font, serif;
}
This downloads the EOT file from the given URL and declares it to be a font of normal weight and roman style with the family name "My Fancy
Font." That font can then be used in style rules, such as, in this example, to set the font of body text. See the "CSS Fonts Module level
3" for details on CSS.
TrueType files typically have the extension .ttf, OpenType files typically have the extension .otf and EOT files typically end in .eot.
SEE ALSO eotinfo(1), fontforge(1), WEFT (http://www.microsoft.com/typography/web/embedding/weft3/default.htm), EOT (http://www.w3.org/Submis-
sion/2008/01/) CSS Fonts Module level 3 (see http://www.w3.org/TR/css3-fonts/)
BUGS
mkeot does not apply the optional MicroType Express compression.
mkeot may fail with fonts that have non-ASCII characters in their names.
mkeot cannot handle fonts that use (only) language tags instead of traditional Microsoft/Apple language numbers in their names table.
(Luckily, this feature of OpenType version 1.6 appears to be little used.)
mkeot does not subset the font, unlike Microsoft's graphical WEFT tool. To make a EOT file with a reduced set of glyphs, you must first
create a subsetted TrueType font with a font editor.
1.x 25 Jan 2010 MKEOT(1)