summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/man
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/man')
-rw-r--r--Master/texmf-dist/doc/man/man1/afm2afm.14
-rw-r--r--Master/texmf-dist/doc/man/man1/afm2afm.man1.pdfbin26888 -> 26826 bytes
-rw-r--r--Master/texmf-dist/doc/man/man1/autoinst.1449
-rw-r--r--Master/texmf-dist/doc/man/man1/autoinst.man1.pdfbin73564 -> 68684 bytes
-rw-r--r--Master/texmf-dist/doc/man/man1/ot2kpx.14
-rw-r--r--Master/texmf-dist/doc/man/man1/ot2kpx.man1.pdfbin27175 -> 27116 bytes
6 files changed, 167 insertions, 290 deletions
diff --git a/Master/texmf-dist/doc/man/man1/afm2afm.1 b/Master/texmf-dist/doc/man/man1/afm2afm.1
index 1f89c78a4b8..0ade3382f99 100644
--- a/Master/texmf-dist/doc/man/man1/afm2afm.1
+++ b/Master/texmf-dist/doc/man/man1/afm2afm.1
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "AFM2AFM 1"
-.TH AFM2AFM 1 "2020-06-19" "fontools" "Marc Penninga"
+.TH AFM2AFM 1 "2020-07-29" "fontools" "Marc Penninga"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -223,7 +223,7 @@ but \s-1WITHOUT ANY WARRANTY\s0; without even the implied warranty of
See the \s-1GNU\s0 General Public License for more details.
.SH "VERSION"
.IX Header "VERSION"
-This document describes \fBafm2afm\fR version 20200619.
+This document describes \fBafm2afm\fR version 20200729.
.SH "RECENT CHANGES"
.IX Header "RECENT CHANGES"
(See the source code for the rest of the story.)
diff --git a/Master/texmf-dist/doc/man/man1/afm2afm.man1.pdf b/Master/texmf-dist/doc/man/man1/afm2afm.man1.pdf
index 23138d7996e..c8821828b75 100644
--- a/Master/texmf-dist/doc/man/man1/afm2afm.man1.pdf
+++ b/Master/texmf-dist/doc/man/man1/afm2afm.man1.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/man/man1/autoinst.1 b/Master/texmf-dist/doc/man/man1/autoinst.1
index c3f0c227990..c5ed6de60a8 100644
--- a/Master/texmf-dist/doc/man/man1/autoinst.1
+++ b/Master/texmf-dist/doc/man/man1/autoinst.1
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "AUTOINST 1"
-.TH AUTOINST 1 "2020-06-19" "fontools" "Marc Penninga"
+.TH AUTOINST 1 "2020-07-29" "fontools" "Marc Penninga"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -242,12 +242,9 @@ Titling characters; see above
.IP "\fIOrn\fR" 8
.IX Item "Orn"
ornaments
-.IP "\fINumr\fR" 8
-.IX Item "Numr"
-numerators
-.IP "\fIDnom\fR" 8
-.IX Item "Dnom"
-denominators
+.IP "\fINumr\fR, \fIDnom\fR" 8
+.IX Item "Numr, Dnom"
+numerators and denominators
.PP
The individual fonts are named \fI<FontName>\-<suffix>\-<shape>\-<enc>\fR,
where \fI<suffix>\fR is the same as above (but in lowercase),
@@ -288,19 +285,19 @@ so that its x\-height matches that of the previously active font
(which is usually Computer Modern, unless you have loaded another
font package before this one).
The name \f(CW\*(C`scaled\*(C'\fR may be used as a synonym for \f(CW\*(C`scale\*(C'\fR.
-.ie n .IP """medium"", ""book"", ""text"", ""regular""" 4
-.el .IP "\f(CWmedium\fR, \f(CWbook\fR, \f(CWtext\fR, \f(CWregular\fR" 4
-.IX Item "medium, book, text, regular"
-Select the weight that LaTeX will use as the `regular' weight;
-the default is \f(CW\*(C`regular\*(C'\fR.
+.ie n .IP """medium"", ""book"", ""text"", ""normal"", ""regular""" 4
+.el .IP "\f(CWmedium\fR, \f(CWbook\fR, \f(CWtext\fR, \f(CWnormal\fR, \f(CWregular\fR" 4
+.IX Item "medium, book, text, normal, regular"
+Select the weight that LaTeX will use as the `regular' weight.
.ie n .IP """heavy"", ""black"", ""extrabold"", ""demibold"", ""semibold"", ""bold""" 4
.el .IP "\f(CWheavy\fR, \f(CWblack\fR, \f(CWextrabold\fR, \f(CWdemibold\fR, \f(CWsemibold\fR, \f(CWbold\fR" 4
.IX Item "heavy, black, extrabold, demibold, semibold, bold"
-Select the weight that LaTeX will use as the `bold' weight;
-the default is \f(CW\*(C`bold\*(C'\fR.
+Select the weight that LaTeX will use as the `bold' weight.
.PP
The last two groups of options will only work if
you have the \fImweights\fR package installed.
+The default here is not to change LaTeX's default,
+i.e. use the `m' and `b' weights.
.PP
The style file will also try to load the \fIfontaxes\fR package
(on \s-1CTAN\s0), which gives easy access to various font shapes and styles.
@@ -395,7 +392,7 @@ these offending characters.
Once again: test the results before using them!
If the characters themselves are fine but spaced too tightly,
you may try increasing the side bearings in math fonts with
-the \fI\-mathspacing\fR option (see below), e.g. \f(CW\*(C`\-mathspacing=100\*(C'\fR.
+the \fI\-mathspacing\fR option (see below), e.g. \f(CW\*(C`\-mathspacing=50\*(C'\fR.
.SS "\s-1NFSS\s0 codes"
.IX Subsection "NFSS codes"
LaTeX's New Font Selection System (\s-1NFSS\s0)
@@ -428,17 +425,10 @@ The mapping of shapes to \s-1NFSS\s0 codes is done using the following table:
we map the first of these to `n', for the second one we (ab)use the `it' code
as this family doesn't contain an Italic shape.)
.PP
-The mapping of weights and widths to \s-1NFSS\s0 codes is a more complex,
-two-step proces.
-In the first step, all fonts are assigned a `series' name that is simply
-the concatenation of its weight and width
-(after expanding any abbreviations and converting to lowercase).
-A font with `Cond' width and `Ultra' weight will then be known
-as `ultrablackcondensed'.
-.PP
-In the second step, \fBautoinst\fR tries to map all combinations of \s-1NFSS\s0 codes
+For weights and widths, \fBautoinst\fR tries to the standard \s-1NFSS\s0 codes
(ul, el, l, sl, m, sb, b, eb and ub for weights;
-uc, ec, c, sc, m, sx, x, ex and ux for widths) to actual fonts.
+uc, ec, c, sc, m, sx, x, ex and ux for widths)
+as much as possible.
Of course, not all 81 combinations of these \s-1NFSS\s0 weights and widths will map
to existing fonts;
and conversely it may not be possible to assign every existing font
@@ -446,12 +436,14 @@ a unique code in a sane way (especially for the weights, some font families
offer more choices or finer granularity than \s-1NFSS\s0's codes can handle;
e.g., Fira Sans contains fifteen(!) different weights,
including an additional `Medium' weight between Regular and Semibold).
+Therefore every font is also assigned a `series' name that is simply
+the concatenation of its weight and width
+(after expanding any abbreviations and converting to lowercase).
+A font with `Cond' width and `Ultra' weight will then be known
+as `ultrablackcondensed'.
.PP
-\&\fBautoinst\fR tries hard to ensure that the most common \s-1NFSS\s0 codes
-(and high-level commands such as \f(CW\*(C`\ebfseries\*(C'\fR,
-which are built on top of those codes) will `just work'.
-.PP
-To see exactly which \s-1NFSS\s0 codes map to which fonts, see the log file
+The exact mapping between fonts and \s-1NFSS\s0 codes can be found
+in the generated \fIfd\fR files and in the log file
(pro tip: run \fBautoinst\fR with the \fI\-dryrun\fR option
to check the chosen mapping beforehand).
The \fI\-nfssweight\fR and \fI\-nfsswidth\fR command-line options can be used
@@ -480,6 +472,48 @@ this will create a table of all glyphs in that font.
Note that versions of \fBautoinst\fR up to 20200428 handled ornaments
differently, and fonts and style files generated by those versions
are not compatible with files generated by newer versions.
+.SH "WARNINGS AND CAVEATS"
+.IX Header "WARNINGS AND CAVEATS"
+.SS "OpenType fonts and licensing issues"
+.IX Subsection "OpenType fonts and licensing issues"
+Since \fIpdfTeX\fR cannot subset otf-flavoured OpenType fonts,
+\&\fIotftotfm\fR will convert such fonts to Type1 (pfb) format.
+However, many fonts (at least those licensed under the \s-1SIL\s0 Open Font License)
+do not allow distributing such converted versions under their original name.
+.PP
+To meet these licensing requirements, \fBautoinst\fR provides
+a \f(CW\*(C`\-t1suffix\*(C'\fR command-line option that appends
+a (user-defined) suffix to the names (both filename and internal font name)
+of all generated Type1 fonts; see \*(L"COMMAND-LINE \s-1OPTIONS\*(R"\s0 below.
+.SS "A note for MiKTeX users"
+.IX Subsection "A note for MiKTeX users"
+Automatically installing the fonts into a suitable \s-1TEXMF\s0 tree
+(as \fBautoinst\fR tries to do by default) only works for TeX-installations
+that use the \fIkpathsea\fR library; with TeX distributions that implement
+their own directory searching (such as MiKTeX), \fBautoinst\fR will complain
+that it cannot find the \fIkpsewhich\fR program and move all generated files
+into a subdirectory \f(CW\*(C`./autoinst_output/\*(C'\fR of the current directory.
+If you use such a TeX distribution, you should either move these files
+to their correct destinations by hand, or use the \fI\-target\fR option
+(see \*(L"COMMAND-LINE \s-1OPTIONS\*(R"\s0 below) to manually specify a \s-1TEXMF\s0 tree.
+.PP
+Also, some OpenType fonts contain so many kerning pairs that the resulting
+\&\fIpl\fR and \fIvpl\fR files are too big for MiKTeX's \fIpltotf\fR and \fIvptovf\fR;
+the versions that come with W32TeX (\fIhttp://www.w32tex.org\fR)
+and TeXLive (\fIhttp://tug.org/texlive\fR) don't seem to have this problem.
+.SS "A note for MacTeX users"
+.IX Subsection "A note for MacTeX users"
+By default, \fBautoinst\fR will try to install all generated files into
+the \f(CW$TEXMFLOCAL\fR tree; when this directory isn't user-writable,
+it will use the \f(CW$TEXMFHOME\fR tree instead. Unfortunately, MacTeX's version
+of \f(CW\*(C`updmap\-sys\*(C'\fR doesn't search in \f(CW$TEXMFHOME\fR,
+and hence MacTeX will not find the new fonts.
+.PP
+To remedy this, either run \fBautoinst\fR as root (so that it can install
+everything into \f(CW$TEXMFLOCAL\fR) or manually run \f(CW\*(C`updmap \-user\*(C'\fR to tell
+TeX about the files in \f(CW$TEXMFHOME\fR.
+The latter option does, however, have some caveats;
+see \fIhttps://tug.org/texlive/scripts\-sys\-user.html\fR.
.SH "COMMAND-LINE OPTIONS"
.IX Header "COMMAND-LINE OPTIONS"
\&\fBautoinst\fR tries hard to do The Right Thing (\s-1TM\s0) by default,
@@ -490,9 +524,8 @@ You may use either one or two dashes before options,
and option names may be shortened to a unique prefix
(e.g., \fB\-encoding\fR may be abbreviated to \fB\-enc\fR or even \fB\-en\fR,
but \fB\-e\fR is ambiguous (it may mean either \fB\-encoding\fR or \fB\-extra\fR)).
-.IP "\fB\-version\fR" 4
-.IX Item "-version"
-Print \fBautoinst\fR's version number and exit.
+.SS "General options"
+.IX Subsection "General options"
.IP "\fB\-help\fR" 4
.IX Item "-help"
Print a (relatively) short help text and exit.
@@ -500,14 +533,14 @@ Print a (relatively) short help text and exit.
.IX Item "-dryrun"
Don't generate output; just parse input fonts and write
a log file saying what \fBautoinst\fR would have done.
-.IP "\fB\-logfile\fR=\fIfilename\fR" 4
-.IX Item "-logfile=filename"
-Write log data to \fIfilename\fR instead of the default \fI<fontfamily>.log\fR.
-If the file already exists, \fBautoinst\fR appends to it;
-it doesn't overwrite an existing file.
.IP "\fB\-verbose\fR" 4
.IX Item "-verbose"
Add more details to the log file.
+.IP "\fB\-version\fR" 4
+.IX Item "-version"
+Print \fBautoinst\fR's version number and exit.
+.SS "Font creation options"
+.IX Subsection "Font creation options"
.IP "\fB\-encoding\fR=\fIencoding[,encoding]\fR" 4
.IX Item "-encoding=encoding[,encoding]"
Generate the specified encoding(s) for the text fonts.
@@ -526,26 +559,6 @@ with other packages; the `fontools_' prefix may be omitted.)
Control the creation of TS1\-encoded fonts. The default is \fB\-ts1\fR
if the text encodings (see \fI\-encoding\fR above) include T1,
\&\fB\-nots1\fR otherwise.
-.IP "\fB\-serif\fR/\fB\-sanserif\fR/\fB\-typewriter\fR" 4
-.IX Item "-serif/-sanserif/-typewriter"
-Install the font as a serif, sanserif or typewriter font, respectively.
-This changes how you access the font in LaTeX:
-with \f(CW\*(C`\ermfamily\*(C'\fR/\f(CW\*(C`\etextrm\*(C'\fR, \f(CW\*(C`\esffamily\*(C'\fR/\f(CW\*(C`\etextsf\*(C'\fR
-or \f(CW\*(C`\ettfamily\*(C'\fR/\f(CW\*(C`\etexttt\*(C'\fR.
-.Sp
-Installing the font as a typewriter font will cause two further changes:
-it will \- by default \- turn off the use of f\-ligatures
-(though this can be overridden with the \fI\-ligatures\fR option),
-and it will disable hyphenation for this font.
-This latter effect cannot be re-enabled in \fBautoinst\fR;
-if you want typewriter text to be hyphenated, use the \fIhyphenat\fR package.
-.Sp
-If none of these options is specified, \fBautoinst\fR tries to guess:
-if the font's filename contains the string `mono'
-or if the field \f(CW\*(C`isFixedPitch\*(C'\fR in the font's \fIpost\fR table is True,
-it will select \fB\-typewriter\fR;
-else if the filename contains `sans' it will select \fB\-sanserif\fR;
-otherwise it will opt for \fB\-serif\fR.
.IP "\fB\-lining\fR/\fB\-nolining\fR" 4
.IX Item "-lining/-nolining"
Control the creation of fonts with lining figures. The default is
@@ -579,8 +592,8 @@ The default is \fB\-superiors\fR.
.IP "\fB\-noinferiors\fR" 4
.IX Item "-noinferiors"
.PD 0
-.IP "\fB\-inferiors\fR [= \fBnone\fR | \fBauto\fR | \fBsubs\fR | \fBsinf\fR | \fBdnom\fR ]" 4
-.IX Item "-inferiors [= none | auto | subs | sinf | dnom ]"
+.IP "\fB\-inferiors\fR [ = \fBnone\fR | \fBauto\fR | \fBsubs\fR | \fBsinf\fR | \fBdnom\fR ]" 4
+.IX Item "-inferiors [ = none | auto | subs | sinf | dnom ]"
.PD
The OpenType standard defines several kinds of digits that might be used
as inferiors or subscripts: `Subscripts' (OpenType feature `subs'),
@@ -599,20 +612,39 @@ with inferiors at all; it won't try to substitute one of the other styles.\fR
.IX Item "-fractions/-nofractions"
Control the creation of fonts with numerators and denominators.
The default is \fB\-nofractions\fR.
-.IP "\fB\-ornaments\fR/\fB\-noornaments\fR" 4
-.IX Item "-ornaments/-noornaments"
-Control the creation of ornament fonts. The default is \fB\-ornaments\fR.
.IP "\fB\-ligatures\fR/\fB\-noligatures\fR" 4
.IX Item "-ligatures/-noligatures"
Some fonts create glyphs for the standard f\-ligatures (ff, fi, fl, ffi, ffl),
but don't provide a `liga' feature to access these.
This option tells \fBautoinst\fR to add extra \f(CW\*(C`LIGKERN\*(C'\fR rules to
the generated fonts to enable the use of these ligatures.
-The default is \fB\-ligatures\fR,
-unless the user specified the \fI\-typewriter\fR option.
+The default is \fB\-ligatures\fR, except for typewriter fonts.
.Sp
-Specify \fB\-noligatures\fR to disable the generation of ligatures even for fonts
+Specify \fB\-noligatures\fR to disable generation of ligatures even for fonts
that do contain a `liga' feature.
+.IP "\fB\-ornaments\fR/\fB\-noornaments\fR" 4
+.IX Item "-ornaments/-noornaments"
+Control the creation of ornament fonts. The default is \fB\-ornaments\fR.
+.IP "\fB\-serif\fR/\fB\-sanserif\fR/\fB\-typewriter\fR" 4
+.IX Item "-serif/-sanserif/-typewriter"
+Install the font as a serif, sanserif or typewriter font, respectively.
+This changes how you access the font in LaTeX:
+with \f(CW\*(C`\ermfamily\*(C'\fR/\f(CW\*(C`\etextrm\*(C'\fR, \f(CW\*(C`\esffamily\*(C'\fR/\f(CW\*(C`\etextsf\*(C'\fR
+or \f(CW\*(C`\ettfamily\*(C'\fR/\f(CW\*(C`\etexttt\*(C'\fR.
+.Sp
+Installing the font as a typewriter font will cause two further changes:
+it will \- by default \- turn off the use of f\-ligatures
+(though this can be overridden with the \fI\-ligatures\fR option),
+and it will disable hyphenation for this font.
+This latter effect cannot be re-enabled in \fBautoinst\fR;
+if you want typewriter text to be hyphenated, use the \fIhyphenat\fR package.
+.Sp
+If none of these options is specified, \fBautoinst\fR tries to guess:
+if the font's filename contains the string `mono'
+or if the field \f(CW\*(C`isFixedPitch\*(C'\fR in the font's \fIpost\fR table is True,
+it will select \fB\-typewriter\fR;
+else if the filename contains `sans' it will select \fB\-sanserif\fR;
+otherwise it will opt for \fB\-serif\fR.
.IP "\fB\-math\fR" 4
.IX Item "-math"
Tells \fBautoinst\fR to create basic math fonts (see above).
@@ -622,6 +654,50 @@ Letterspace each character in the math fonts by \fIamount\fR units,
where 1000 units equal one em.
In my opinion, many text fonts benefit from letterspacing by 50 to 100 units
when used in maths; some fonts need even more. Use your own judgement!
+.SS "Output options"
+.IX Subsection "Output options"
+.IP "\fB\-t1suffix\fR [ = \fI\s-1SUFFIX\s0\fR ]" 4
+.IX Item "-t1suffix [ = SUFFIX ]"
+Tell \fBautoinst\fR to modify the font names of all generated Type1\-fonts,
+by adding \fI\s-1SUFFIX\s0\fR to the family name.
+If you use this option without specifying a \fI\s-1SUFFIX\s0\fR value,
+\&\fBautoinst\fR will use the value ``\s-1PS\s0''.
+The default behaviour when this option is not given
+is to not modify font names at all.
+.Sp
+See also \*(L"OpenType fonts and licensing issues\*(R" above.
+.IP "\fB\-target\fR=\fI\s-1DIRECTORY\s0\fR" 4
+.IX Item "-target=DIRECTORY"
+Install all generated files into the \s-1TEXMF\s0 tree at \fI\s-1DIRECTORY\s0\fR.
+.Sp
+By default, \fBautoinst\fR searches the \f(CW$TEXMFLOCAL\fR and \f(CW$TEXMFHOME\fR trees
+and installs all files into the first user-writable \s-1TEXMF\s0 tree it finds.
+If \fBautoinst\fR cannot find such a user-writable directory
+(which shouldn't happen, since \f(CW$TEXMFHOME\fR is supposed to be user-writable)
+it will print a warning message and put all files into the subdirectory
+\&\f(CW\*(C`./autoinst_output/\*(C'\fR of the current directory.
+It's then up to the user to move the generated files to a better location
+and update all relevant databases
+(usually by calling \fItexhash\fR and \fIupdmap\fR).
+.IP "\fB\-vendor\fR=\fI\s-1VENDOR\s0\fR" 4
+.IX Item "-vendor=VENDOR"
+.PD 0
+.IP "\fB\-typeface\fR=\fI\s-1TYPEFACE\s0\fR" 4
+.IX Item "-typeface=TYPEFACE"
+.PD
+These options are equivalent to \fIotftotfm\fR's \fI \-\-vendor\fR and \fI \-\-typeface\fR
+options: they change the `vendor' and `typeface' parts of the names of the
+subdirectories in the \s-1TEXMF\s0 tree where generated files will be stored.
+The default values are `lcdftools' and the font's FontFamily name.
+These options change \fIonly\fR directory names,
+not the names of any generated files.
+.IP "\fB\-logfile\fR=\fIfilename\fR" 4
+.IX Item "-logfile=filename"
+Write log data to \fIfilename\fR instead of the default \fI<fontfamily>.log\fR.
+If the file already exists, \fBautoinst\fR appends to it;
+it doesn't overwrite an existing file.
+.SS "Specialist options"
+.IX Subsection "Specialist options"
.IP "\fB\-defaultlining\fR/\fB\-defaultoldstyle\fR" 4
.IX Item "-defaultlining/-defaultoldstyle"
.PD 0
@@ -636,15 +712,6 @@ They are only needed for fonts that don't provide OpenType features
for their default figure style; and even in that case,
\&\fBautoinst\fR's default values (\fB\-defaultlining\fR and \fB\-defaulttabular\fR)
are usually correct.
-.IP "\fB\-nofigurekern\fR" 4
-.IX Item "-nofigurekern"
-Some fonts provide kerning pairs for tabular figures.
-This is very probably not what you want
-(e.g., numbers in tables won't line up exactly).
-This option adds extra \fI \-\-ligkern\fR options
-to the commands for \fIotftotfm\fR to suppress such kerns.
-Note that this option leads to very long commands (it adds
-one hundred \fI \-\-ligkern\fR options), which may cause problems on some systems.
.IP "\fB\-nfssweight\fR=\fIcode\fR=\fIweight\fR" 4
.IX Item "-nfssweight=code=weight"
.PD 0
@@ -664,112 +731,26 @@ use \f(CW\*(C`\-nfssweight=ul=\*(C'\fR.
Append \fIextra\fR as extra options to the command lines for \fIotftotfm\fR.
To prevent \fIextra\fR from accidentily being interpreted as options
to \fBautoinst\fR, it should be properly quoted.
-.IP "\fB\-manual\fR" 4
-.IX Item "-manual"
-Manual mode; for users who want to post-process the generated files
-and commands. By default, \fBautoinst\fR immediately executes all
-\&\fIotftotfm\fR commands it generates;
-in manual mode, these are instead written to a file \fIautoinst.bat\fR.
-Furthermore it tells \fIotftotfm\fR to generate human readable (and editable)
-\&\fIpl/vpl\fR files instead of the default \fItfm/vf\fR ones,
-and to place all generated files in a subdirectory \f(CW\*(C`./autoinst_output/\*(C'\fR
-of the current directory, rather than install them into your TeX installation.
-.Sp
-When using this option, you need to execute the following manual steps after
-\&\fBautoinst\fR has finished:
-.RS 4
-.IP "\- run \fIpltotf\fR and \fIvptovf\fR on the generated \fIpl\fR and \fIvf\fR files, to convert them to \fItfm/vf\fR format;" 2
-.IX Item "- run pltotf and vptovf on the generated pl and vf files, to convert them to tfm/vf format;"
-.PD 0
-.IP "\- move all generated files to a proper \s-1TEXMF\s0 tree, and, if necessary, update the filename database;" 2
-.IX Item "- move all generated files to a proper TEXMF tree, and, if necessary, update the filename database;"
-.ie n .IP "\- tell TeX about the new \fImap\fR file (usually by running ""updmap"" or similar)." 2
-.el .IP "\- tell TeX about the new \fImap\fR file (usually by running \f(CWupdmap\fR or similar)." 2
-.IX Item "- tell TeX about the new map file (usually by running updmap or similar)."
-.RE
-.RS 4
-.PD
-.Sp
-Note that some options (\fI\-target\fR, \fI\-vendor\fR and \fI\-typeface\fR,
-\&\fI\-[no]updmap\fR) are meaningless, and hence ignored, in manual mode.
-.RE
-.IP "\fB\-target\fR=\fI\s-1DIRECTORY\s0\fR" 4
-.IX Item "-target=DIRECTORY"
-Install all generated files into the \s-1TEXMF\s0 tree at \fI\s-1DIRECTORY\s0\fR.
-.Sp
-By default, \fBautoinst\fR searches the \f(CW$TEXMFLOCAL\fR and \f(CW$TEXMFHOME\fR trees
-and installs all files into the first user-writable \s-1TEXMF\s0 tree it finds.
-If \fBautoinst\fR cannot find such a user-writable directory
-(which shouldn't happen, since \f(CW$TEXMFHOME\fR is supposed to be user-writable)
-it will print a warning message and put all files into the subdirectory
-\&\f(CW\*(C`./autoinst_output/\*(C'\fR of the current directory.
-It's then up to the user to move the generated files to a better location
-and update all relevant databases
-(usually by calling \fItexhash\fR and \fIupdmap\fR).
-.Sp
-\&\fI\s-1WARNING:\s0\fR using this option may interfere with \fIkpathsea\fR and \fIupdmap\fR
-(especially when the chosen directory is outside the standard \s-1TEXMF\s0 trees),
-so using \fI\-target\fR will disable the automatic call to \fIupdmap\fR
-(as if \fI\-noupdmap\fR had been given).
-It is up to the user to manually update all databases (i.e., by calling
-\&\fItexhash\fR and \fIupdmap\fR or similar).
-.IP "\fB\-vendor\fR=\fI\s-1VENDOR\s0\fR" 4
-.IX Item "-vendor=VENDOR"
-.PD 0
-.IP "\fB\-typeface\fR=\fI\s-1TYPEFACE\s0\fR" 4
-.IX Item "-typeface=TYPEFACE"
-.PD
-These options are equivalent to \fIotftotfm\fR's \fI \-\-vendor\fR and \fI \-\-typeface\fR
-options: they change the `vendor' and `typeface' parts of the names of the
-subdirectories in the \s-1TEXMF\s0 tree where generated files will be stored.
-The default values are `lcdftools' and the font's FontFamily name.
-.Sp
-Note that these options change \fIonly\fR directory names,
-not the names of any generated files.
-.IP "\fB\-updmap\fR/\fB\-noupdmap\fR" 4
-.IX Item "-updmap/-noupdmap"
-Control whether or not \fIupdmap\fR is called after the last call to \fIotftotfm\fR.
-The default is \fB\-updmap\fR.
-.SS "A note for MiKTeX users"
-.IX Subsection "A note for MiKTeX users"
-Automatically installing the fonts into a suitable \s-1TEXMF\s0 tree
-(as \fBautoinst\fR tries to do by default) only works for TeX-installations
-that use the \fIkpathsea\fR library; with TeX distributions that implement
-their own directory searching (such as MiKTeX), \fBautoinst\fR will complain
-that it cannot find the \fIkpsewhich\fR program and move all generated files
-into a subdirectory \f(CW\*(C`./autoinst_output/\*(C'\fR of the current directory.
-If you use such a TeX distribution, you should either move these files
-to their correct destinations by hand, or use the \fI\-target\fR option
-(see \*(L"COMMAND-LINE \s-1OPTIONS\*(R"\s0 below) to manually specify a \s-1TEXMF\s0 tree.
-.PP
-Also, some OpenType fonts contain so many kerning pairs that the resulting
-\&\fIpl\fR and \fIvpl\fR files are too big for MiKTeX's \fIpltotf\fR and \fIvptovf\fR;
-the versions that come with W32TeX (\fIhttp://www.w32tex.org\fR)
-and TeXLive (\fIhttp://tug.org/texlive\fR) don't seem to have this problem.
-.SS "A note for MacTeX users"
-.IX Subsection "A note for MacTeX users"
-By default, \fBautoinst\fR will try to install all generated files into
-the \f(CW$TEXMFLOCAL\fR tree; when this directory isn't user-writable,
-it will use the \f(CW$TEXMFHOME\fR tree instead. Unfortunately, MacTeX's version
-of \f(CW\*(C`updmap\-sys\*(C'\fR (which is called behind the scenes) doesn't search
-in \f(CW$TEXMFHOME\fR, and hence MacTeX will not find the new fonts.
-.PP
-To remedy this, either run \fBautoinst\fR as root (so that it can install
-everything into \f(CW$TEXMFLOCAL\fR) or manually run \f(CW\*(C`updmap \-user\*(C'\fR to tell
-TeX about the files in \f(CW$TEXMFHOME\fR.
-The latter option does, however, have some caveats;
-see \fIhttps://tug.org/texlive/scripts\-sys\-user.html\fR.
+.IP "\fB\-nofigurekern\fR" 4
+.IX Item "-nofigurekern"
+Some fonts provide kerning pairs for tabular figures.
+This is very probably not what you want
+(e.g., numbers in tables won't line up exactly).
+This option adds extra \fI \-\-ligkern\fR options
+to the commands for \fIotftotfm\fR to suppress such kerns.
+Note that this option leads to very long commands (it adds
+one hundred \fI \-\-ligkern\fR options), which may cause problems on some systems.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
-Eddie Kohler's \fBTypeTools\fR (\fIhttp://www.lcdf.org/type\fR).
+Eddie Kohler's \fBTypeTools\fR and \fBT1Utils\fR (\fIhttp://www.lcdf.org/type\fR).
.PP
\&\fBPerl\fR can be obtained from \fIhttp://www.perl.org\fR;
it is included in most Linux distributions.
For Windows, try ActivePerl (\fIhttp://www.activestate.com\fR)
or Strawberry Perl (\fIhttp://strawberryperl.com\fR).
.PP
-\&\fBXeTeX\fR (\fIhttp://www.tug.org/xetex\fR) and
-\&\fBLuaTeX\fR (\fIhttp://www.luatex.org\fR)
+\&\fBLuaTeX\fR (\fIhttp://www.luatex.org\fR) and
+\&\fBXeTeX\fR (\fIhttp://www.tug.org/xetex\fR)
are Unicode-aware TeX engines that can use OpenType fonts directly,
without any (La)TeX\-specific support files.
.PP
@@ -804,10 +785,18 @@ but \s-1WITHOUT ANY WARRANTY\s0; without even the implied warranty of
\&\s-1GNU\s0 General Public License for more details.
.SH "VERSION"
.IX Header "VERSION"
-This document describes \fBautoinst\fR version 20200619.
+This document describes \fBautoinst\fR version 20200729.
.SH "RECENT CHANGES"
.IX Header "RECENT CHANGES"
(See the source for the full story, all the way back to 2005.)
+.IP "\fI2020\-07\-29\fR" 12
+.IX Item "2020-07-29"
+Some changes in the generated \fIsty\fR and \fIfd\fR files,
+to improve compatibility with the \fImicrotype\fR package.
+Made sure that \fIpfb\fR fonts are always generated whenever
+the input fonts are in \fIotf\fR format.
+Added the \f(CW\*(C`\-t1suffix\*(C'\fR command-line option,
+to modify the font and file names of those generated Type1 fonts.
.IP "\fI2020\-06\-19\fR" 12
.IX Item "2020-06-19"
Added the \f(CW\*(C`nomathgreek\*(C'\fR option to generated style files.
@@ -837,115 +826,3 @@ an argument to \fI\-inferiors\fR.
.IP "\fI2020\-01\-29\fR" 12
.IX Item "2020-01-29"
Don't create empty subdirectories in the target \s-1TEXMF\s0 tree.
-.IP "\fI2019\-11\-18\fR" 12
-.IX Item "2019-11-18"
-Fine-tuned calling of \fIkpsewhich\fR on Windows (patch by Akira Kakuto).
-The font info parsing now also recognises numerical weights, e.g. in Museo.
-.IP "\fI2019\-10\-29\fR" 12
-.IX Item "2019-10-29"
-The generated style files now use T1 as the default text encoding.
-.IP "\fI2019\-10\-27\fR" 12
-.IX Item "2019-10-27"
-The mapping in \fIfd\fR files between font series and standard \s-1NFSS\s0 attributes
-now uses the new \fIalias\fR function instead of \fIssub\fR (based on code by
-Frank Mittelbach).
-The way \fIotftotfm\fR is called was changed to work around a Perl/Windows bug;
-the old way might cause the process to hang.
-Using the \fI\-target\fR option now implies \fI\-noupdmap\fR, since choosing
-a non-standard target directory interferes with kpathsea/texhash and updmap.
-.IP "\fI2019\-10\-01\fR" 12
-.IX Item "2019-10-01"
-Handle \fI\-target\fR directories with spaces in their path names.
-Tweaked messages and logs to make them more useful to the user.
-.IP "\fI2019\-07\-12\fR" 12
-.IX Item "2019-07-12"
-Replaced single quotes in calls to \fIotfinfo\fR with double quotes,
-as they caused problems on Windows 10.
-.IP "\fI2019\-06\-25\fR" 12
-.IX Item "2019-06-25"
-.RS 12
-.PD 0
-.IP "\-" 3
-.PD
-Added the \fI\-mergeweights\fR and \fI\-mergeshapes\fR options,
-and improved \fI\-mergewidths\fR.
-.IP "\-" 3
-Improved the parsing of fonts' widths and weights.
-.IP "\-" 3
-Improved the mapping of widths and weights to \s-1NFSS\s0 codes.
-.IP "\-" 3
-Changed logging code so that that results of font info parsing
-are always logged, even (especially!) when parsing fails.
-.IP "\-" 3
-Added a warning when installing fonts from multiple families.
-.IP "\-" 3
-Added simple recognition for sanserif and typewriter fonts.
-.IP "\-" 3
-Fixed error checking after calls to \fIotfinfo\fR
-(\fBautoinst\fR previously only checked whether \f(CW\*(C`fork()\*(C'\fR was successful,
-not whether the actual call to \fIotfinfo\fR worked).
-.IP "\-" 3
-Fixed a bug in the \fI\-inferiors\fR option;
-when used without a (supposedly optional) value,
-it would silently gobble the next option instead.
-.RE
-.RS 12
-.RE
-.IP "\fI2019\-05\-22\fR" 12
-.IX Item "2019-05-22"
-Added the \fImainfont\fR option to the generated \fIsty\fR files.
-Prevented hyphenation for typewriter fonts
-(added \f(CW\*(C`\ehyphenchar\efont=\-1\*(C'\fR to the \f(CW\*(C`\eDeclareFontFamily\*(C'\fR declarations).
-Added the \fI\-version\fR option.
-.IP "\fI2019\-05\-17\fR" 12
-.IX Item "2019-05-17"
-Changed the way the \fI\-ligatures\fR option works:
-\&\fI\-ligatures\fR enables f\-ligatures (even without a `liga' feature),
-\&\fI\-noligatures\fR now disables f\-ligatures (overriding a `liga' feature).
-.IP "\fI2019\-05\-11\fR" 12
-.IX Item "2019-05-11"
-Separate small caps families are now also recognised when the family name
-ends with `\s-1SC\s0' (previously \fBautoinst\fR only looked for `SmallCaps').
-.IP "\fI2019\-04\-22\fR" 12
-.IX Item "2019-04-22"
-Fixed a bug in the generation of swash shapes.
-.IP "\fI2019\-04\-19\fR" 12
-.IX Item "2019-04-19"
-Fixed a bug that affected \-mergesmallcaps with multiple encodings.
-.IP "\fI2019\-04\-16\fR" 12
-.IX Item "2019-04-16"
-Added the <\-mergesmallcaps> option, to handle cases where
-the small caps fonts are in separate font families.
-Titling shape is now treated as a separate family instead of a distinct shape;
-it is generated only for fonts with the `titl' feature.
-Only add f\-ligatures to fonts when explicitly asked to (\fI\-ligatures\fR).
-.IP "\fI2019\-04\-11\fR" 12
-.IX Item "2019-04-11"
-Tried to make the log file more relevant.
-Added the \fI\-nfssweight\fR and \fI\-nfsswidth\fR options,
-and finetuned the automatic mapping between fonts and \s-1NFSS\s0 codes.
-Changed the name of the generated log file to \fI<fontfamily>.log\fR,
-and revived the \fI\-logfile\fR option to allow overriding this choice.
-Made \fI\-mergewidths\fR the default (instead of \fI\-nomergewidths\fR).
-.IP "\fI2019\-04\-01\fR" 12
-.IX Item "2019-04-01"
-Fine-tuned the decision where to put generated files;
-in particular, create \f(CW$TEXMFHOME\fR if it doesn't already exist
-and \f(CW$TEXMFLOCAL\fR isn't user-writable.
-.Sp
-In manual mode, or when we can't find a user-writable \s-1TEXMF\s0 tree,
-put all generated files into a subdirectory \f(CW\*(C`./autoinst_output/\*(C'\fR
-instead of all over the current working directory.
-.Sp
-Added `auto' value to the \fIinferiors\fR option,
-to tell \fBautoinst\fR to use whatever inferior characters are available.
-.IP "\fI2019\-03\-14\fR" 12
-.IX Item "2019-03-14"
-Overhauled the mapping of fonts (more specifically of weights and widths;
-the mapping of shapes didn't change) to \s-1NFSS\s0 codes.
-Instead of inventing our own codes to deal with every possible weight
-and width out there, we now create `long' codes based on the names
-in the font metadata.
-Then we add `ssub' rules to the \fIfd\fR files to map the standard \s-1NFSS\s0 codes
-to our fancy names (see the section \fB\s-1NFSS\s0 codes\fR;
-based on discussions with Frank Mittelbach and Bob Tennent).
diff --git a/Master/texmf-dist/doc/man/man1/autoinst.man1.pdf b/Master/texmf-dist/doc/man/man1/autoinst.man1.pdf
index a8ae98ec4ad..c2809d9dfee 100644
--- a/Master/texmf-dist/doc/man/man1/autoinst.man1.pdf
+++ b/Master/texmf-dist/doc/man/man1/autoinst.man1.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/man/man1/ot2kpx.1 b/Master/texmf-dist/doc/man/man1/ot2kpx.1
index 772d0fa0719..88e2ecbdd59 100644
--- a/Master/texmf-dist/doc/man/man1/ot2kpx.1
+++ b/Master/texmf-dist/doc/man/man1/ot2kpx.1
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "OT2KPX 1"
-.TH OT2KPX 1 "2020-06-19" "fontools" "Marc Penninga"
+.TH OT2KPX 1 "2020-07-29" "fontools" "Marc Penninga"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -228,7 +228,7 @@ but \s-1WITHOUT ANY WARRANTY\s0; without even the implied warranty of
See the \s-1GNU\s0 General Public License for more details.
.SH "VERSION"
.IX Header "VERSION"
-This document describes \fBot2kpx\fR version 20200619.
+This document describes \fBot2kpx\fR version 20200729.
.SH "RECENT CHANGES"
.IX Header "RECENT CHANGES"
(See the source code for the rest of the story.)
diff --git a/Master/texmf-dist/doc/man/man1/ot2kpx.man1.pdf b/Master/texmf-dist/doc/man/man1/ot2kpx.man1.pdf
index 0b66b53c6ab..eec2f134f15 100644
--- a/Master/texmf-dist/doc/man/man1/ot2kpx.man1.pdf
+++ b/Master/texmf-dist/doc/man/man1/ot2kpx.man1.pdf
Binary files differ