summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/man/man1/autoinst.1
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/man/man1/autoinst.1')
-rw-r--r--Master/texmf-dist/doc/man/man1/autoinst.1300
1 files changed, 183 insertions, 117 deletions
diff --git a/Master/texmf-dist/doc/man/man1/autoinst.1 b/Master/texmf-dist/doc/man/man1/autoinst.1
index 86c989f1406..4ffb6c4fa52 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-05-11" "fontools" "Marc Penninga"
+.TH AUTOINST 1 "2020-05-27" "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
@@ -180,7 +180,7 @@ Italic and slanted small caps
Swash
.IP "\fInw\fR" 8
.IX Item "nw"
-\&\*(L"Upright swash\*(R"
+`Upright swash'
.RE
.RS 2
.RE
@@ -194,11 +194,11 @@ a family of TS1\-encoded symbol fonts, in roman, italic and slanted shapes.
Families with superiors, inferiors, numerators and denominators,
in roman, italic and slanted shapes.
.IP "\-" 3
-Families with \*(L"Titling\*(R" characters;
-these \*(L"... replace the default glyphs
+Families with `Titling' characters;
+these `... replace the default glyphs
with corresponding forms designed specifically for titling.
These may be all-capital and/or larger on the body,
-and adjusted for viewing at larger sizes\*(R"
+and adjusted for viewing at larger sizes'
(according to the OpenType Specification).
.IP "\-" 3
An ornament family, also in roman, italic and slanted shapes.
@@ -236,7 +236,7 @@ inferior characters; usually only digits and some punctuation,
normal forms for other characters
.IP "\fITitl\fR" 8
.IX Item "Titl"
-Titling characters; see above.
+Titling characters; see above
.IP "\fIOrn\fR" 8
.IX Item "Orn"
ornaments
@@ -249,47 +249,9 @@ 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),
-\&\fI<shape>\fR is either empty, \*(L"sc\*(R" or \*(L"swash\*(R",
+\&\fI<shape>\fR is either empty, `sc' or `swash',
and \fI<enc>\fR is the encoding (also in lowercase).
-A typical name in this scheme would be \*(L"FiraSans\-Light\-osf\-sc\-ly1\*(R".
-.SS "About the log file"
-.IX Subsection "About the log file"
-\&\fBautoinst\fR writes some info about what it thinks it's doing to a log file.
-By default this is called \fI<fontfamily>.log\fR,
-but this choice can be overridden by the user;
-see the \fI\-logfile\fR command-line option in \*(L"COMMAND-LINE \s-1OPTIONS\*(R"\s0 below.
-If this log file already exists, \fBautoinst\fR will append its data to the end
-rather than overwrite it.
-Use the \fI\-verbose\fR command-line option to ask for more detailed info.
-.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.
+A typical name in this scheme would be `FiraSans\-Light\-osf\-sc\-ly1'.
.SS "Using the fonts in your LaTeX documents"
.IX Subsection "Using the fonts in your LaTeX documents"
\&\fBautoinst\fR generates a style file for using the fonts in LaTeX documents,
@@ -312,28 +274,30 @@ yourself.
.el .IP "\f(CWlining\fR, \f(CWoldstyle\fR, \f(CWtabular\fR, \f(CWproportional\fR" 4
.IX Item "lining, oldstyle, tabular, proportional"
Choose which figure style to use.
-The defaults are \*(L"oldstyle\*(R" and \*(L"proportional\*(R" (if available).
-.ie n .IP """scale=\fI<number>\fP""" 4
-.el .IP "\f(CWscale=\f(CI<number>\f(CW\fR" 4
-.IX Item "scale=<number>"
+The defaults are `oldstyle' and `proportional' (if available).
+.ie n .IP """scale=\fI<number>\fP"", ""scale=MatchLowercase""" 4
+.el .IP "\f(CWscale=\f(CI<number>\f(CW\fR, \f(CWscale=MatchLowercase\fR" 4
+.IX Item "scale=<number>, scale=MatchLowercase"
Scale the font by a factor of \fI<number>\fR.
E.g., to increase the size of the font by 5%, use
\&\f(CW\*(C`\eusepackage[scale=1.05]{\f(CI<FontFamily>\f(CW}\*(C'\fR.
-May also be spelled \f(CW\*(C`scaled\*(C'\fR.
-.Sp
-This option is only available when you have the \fIxkeyval\fR package installed.
+The special value \f(CW\*(C`MatchLowercase\*(C'\fR may be used to scale the font
+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 \*(L"regular\*(R" weight;
+Select the weight that LaTeX will use as the `regular' weight;
the default is \f(CW\*(C`regular\*(C'\fR.
.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 \*(L"bold\*(R" weight;
+Select the weight that LaTeX will use as the `bold' weight;
the default is \f(CW\*(C`bold\*(C'\fR.
.PP
-The previous two groups of options will only work if
+The last two groups of options will only work if
you have the \fImweights\fR package installed.
.PP
The style file will also try to load the \fIfontaxes\fR package
@@ -348,8 +312,8 @@ characters:
\& DECLARATION COMMAND SHORT FORM OF COMMAND
\&
\& \etlshape \etexttitling \etexttl
-\& \esufigures \etextsuperior \etextsu
-\& \einfigures \etextinferior \etextin
+\& \esupfigures \etextsuperior \etextsup, \etextsu
+\& \einffigures \etextinferior \etextinf, \etextin
.Ve
.PP
In addition, the \f(CW\*(C`\eswshape\*(C'\fR and \f(CW\*(C`\etextsw\*(C'\fR commands are redefined to place
@@ -372,37 +336,66 @@ By default, \fBautoinst\fR generates text fonts with \s-1OT1, LY1\s0 and T1
encodings, and the generated style files use T1 as the default text encoding.
Other encodings can be chosen using the \fI\-encoding\fR option
(see \*(L"COMMAND-LINE \s-1OPTIONS\*(R"\s0 below).
+.SS "Maths"
+.IX Subsection "Maths"
+This is an experimental feature; \fB\s-1USE AT YOUR OWN RISK\s0!\fR
+Test the results thoroughly before using them in real documents,
+and be warned that future versions of \fBautoinst\fR may introduce
+incompatible changes.
.PP
-\fIOrnaments\fR
-.IX Subsection "Ornaments"
+The \fI\-math\fR option tells \fBautoinst\fR to generate basic math fonts.
+When enabled, the generated style file defines a few extra options
+to access these math fonts:
+.ie n .IP """math""" 4
+.el .IP "\f(CWmath\fR" 4
+.IX Item "math"
+Use these fonts for the maths in your document.
+.ie n .IP """mathlining"", ""matholdstyle""" 4
+.el .IP "\f(CWmathlining\fR, \f(CWmatholdstyle\fR" 4
+.IX Item "mathlining, matholdstyle"
+Choose which figure style to use in maths.
+The default is `mathlining'.
+.ie n .IP """mathcal""" 4
+.el .IP "\f(CWmathcal\fR" 4
+.IX Item "mathcal"
+Use the swash characters from your fonts as the \f(CW\*(C`\emathcal\*(C'\fR alphabet.
+(This option only exists if your fonts actually contain swash characters
+and a \f(CW\*(C`swsh\*(C'\fR feature to access them).
+.ie n .IP """math\-style=\fI<style>\fP""" 4
+.el .IP "\f(CWmath\-style=\f(CI<style>\f(CW\fR" 4
+.IX Item "math-style=<style>"
+Choose the `math style' to use.
+With \f(CW\*(C`math\-style=ISO\*(C'\fR, all latin and greek letters in math are italic;
+with \f(CW\*(C`math\-style=TeX\*(C'\fR (the default), uppercase greek is upright;
+with \f(CW\*(C`math\-style=french\*(C'\fR, all greek as well as uppercase latin is upright;
+and with \f(CW\*(C`math\-style=upright\*(C'\fR all letters are upright.
.PP
-Ornament fonts are regular LY1\-encoded fonts, with a number of
-\&'regular' characters replaced by ornament glyphs.
-The OpenType specification says that fonts should only put their
-ornaments in place of the lowercase \s-1ASCII\s0 letters or the 'bullet'
-character, but some fonts put them in other positions (such as those
-of the digits) as well.
+Note that this `math' option only changes digits, latin and greek letters,
+plus a few basic punctuation characters; all other mathematical symbols,
+operators, delimiters etc. are left as they were before.
+If you don't want to use TeX's default versions of those symbols,
+load another math package (such as \fImathdesign\fR or \fInewtxmath\fR)
+before loading the \fBautoinst\fR\-generated style file.
.PP
-Ornament glyphs can be accessed like \f(CW\*(C`{\eornaments abc}\*(C'\fR and
-\&\f(CW\*(C`{\eornaments\echar"61}\*(C'\fR, or equivalently
-\&\f(CW\*(C`\etextornaments{abc}\*(C'\fR and \f(CW\*(C`\etextornaments{\echar"61}\*(C'\fR.
-To see which ornaments a font contains (and at which positions),
-run LaTeX on the file \fInfssfont.tex\fR (which is included in any
-standard LaTeX installation), supply the name of the ornament font
-(i.e., \f(CW\*(C`GaramondLibre\-Regular\-orn\-u\*(C'\fR) and say \f(CW\*(C`\etable\ebye\*(C'\fR;
-this will create a table of all glyphs in that font.
-.PP
-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.
+Finally, note that \fBautoinst\fR doesn't check if your fonts actually contains
+all of the required characters;
+it just assumes that they do and sets up the style file accordingly.
+Even if your fonts contain greek, characters such as \f(CW\*(C`\evarepsilon\*(C'\fR
+may be missing.
+You may also find that some glyphs \fIare\fR present in your fonts,
+but don't work well in equations or don't match with other symbols;
+edit the generated style file to remove the declarations of
+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.
.SS "\s-1NFSS\s0 codes"
.IX Subsection "NFSS codes"
LaTeX's New Font Selection System (\s-1NFSS\s0)
identifies fonts by a combination of family,
series (the concatenation of weight and width), shape and size.
-\&\fBautoinst\fR parses the font's metadata
-(more precisely: the output of \f(CW\*(C`otfinfo \-\-info\*(C'\fR)
-to determine these parameters.
+\&\fBautoinst\fR parses the font's metadata to determine these parameters.
When this fails (usually because the font family contains uncommon weights,
widths or shapes),
\&\fBautoinst\fR ends up with different fonts having the \fIsame\fR values
@@ -426,16 +419,16 @@ The mapping of shapes to \s-1NFSS\s0 codes is done using the following table:
.Ve
.PP
(\fIException:\fR Adobe Silentium Pro contains two Roman shapes;
-we map the first of these to \*(L"n\*(R", for the second one we (ab)use the \*(L"it\*(R" code
+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 \*(L"series\*(R" name that is simply
+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 \*(L"Cond\*(R" width and \*(L"Ultra\*(R" weight will then be known
-as \*(L"ultrablackcondensed\*(R".
+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
(ul, el, l, sl, m, sb, b, eb and ub for weights;
@@ -446,11 +439,11 @@ and conversely it may not be possible to assign every existing font
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 \*(L"Medium\*(R" weight between Regular and Semibold).
+including an additional `Medium' weight between Regular and Semibold).
.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 \*(L"just work\*(R".
+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
(pro tip: run \fBautoinst\fR with the \fI\-dryrun\fR option
@@ -461,6 +454,26 @@ to finetune the mapping between \s-1NFSS\s0 codes and fonts.
To access specific weights or widths,
one can always use the \f(CW\*(C`\efontseries\*(C'\fR command with the full series name
(i.e., \f(CW\*(C`\efontseries{demibold}\eselectfont\*(C'\fR).
+.SS "Ornaments"
+.IX Subsection "Ornaments"
+Ornament fonts are regular LY1\-encoded fonts, with a number of
+`regular' characters replaced by ornament glyphs.
+The OpenType specification says that fonts should only put their
+ornaments in place of the lowercase \s-1ASCII\s0 letters, but some fonts
+put them in other positions (such as those of the digits) as well.
+.PP
+Ornaments can be accessed like \f(CW\*(C`{\eornaments a}\*(C'\fR and
+\&\f(CW\*(C`{\eornaments\echar"61}\*(C'\fR, or equivalently
+\&\f(CW\*(C`\etextornaments{a}\*(C'\fR and \f(CW\*(C`\etextornaments{\echar"61}\*(C'\fR.
+To see which ornaments a font contains (and at which positions),
+run LaTeX on the file \fInfssfont.tex\fR (which is included in any
+standard LaTeX installation), supply the name of the ornament font
+(i.e., \f(CW\*(C`GaramondLibre\-Regular\-orn\-u\*(C'\fR) and give the command \f(CW\*(C`\etable\ebye\*(C'\fR;
+this will create a table of all glyphs in that font.
+.PP
+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 "COMMAND-LINE OPTIONS"
.IX Header "COMMAND-LINE OPTIONS"
\&\fBautoinst\fR tries hard to do The Right Thing (\s-1TM\s0) by default,
@@ -493,7 +506,7 @@ Add more details to the log file.
.IX Item "-encoding=encoding[,encoding]"
Generate the specified encoding(s) for the text fonts.
Multiple encodings may be specified as a comma-separated list
-(without spaces!); the default choice of encodings is \*(L"\s-1OT1,LY1,T1\*(R".\s0
+(without spaces!); the default choice of encodings is `\s-1OT1,LY1,T1\s0'.
.Sp
For each specified encoding \s-1XYZ,\s0 \fBautoinst\fR will first see if there is
an encoding file \fI\s-1XYZ\s0.enc\fR in the current directory, and if found it will
@@ -501,7 +514,7 @@ use that; otherwise it will use one of its built-in encoding files.
Currently \fBautoinst\fR comes with support for the \s-1OT1, T1/TS1, LY1, LGR,
T2A/B/C\s0 and T3/TS3 encodings.
(These files are called \fIfontools_ot1.enc\fR etc. to avoid name clashes
-with other packages; the \*(L"fontools_\*(R" prefix may be omitted.)
+with other packages; the `fontools_' prefix may be omitted.)
.IP "\fB\-ts1\fR/\fB\-nots1\fR" 4
.IX Item "-ts1/-nots1"
Control the creation of TS1\-encoded fonts. The default is \fB\-ts1\fR
@@ -518,15 +531,15 @@ 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 disabled in \fBautoinst\fR;
+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 \*(L"mono\*(R"
+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 \*(L"sans\*(R" it selects \fB\-sanserif\fR;
-and otherwise it will opt for \fB\-serif\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
@@ -564,12 +577,12 @@ The default is \fB\-superiors\fR.
.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: \*(L"Subscripts\*(R" (OpenType feature \*(L"subs\*(R"),
-\&\*(L"Scientific Inferiors\*(R" (\*(L"sinf\*(R"), and \*(L"Denominators\*(R" (\*(L"dnom\*(R").
+as inferiors or subscripts: `Subscripts' (OpenType feature `subs'),
+`Scientific Inferiors' ('sinf'), and `Denominators' ('dnom').
This option allows the user to determine which of these styles \fBautoinst\fR
should use for the inferior characters.
-Alternatively, the value \*(L"auto\*(R" tells \fBautoinst\fR to use the first value
-in \*(L"sinf\*(R", \*(L"subs\*(R" or \*(L"dnom\*(R" that is supported by the font.
+Alternatively, the value `auto' tells \fBautoinst\fR to use the first value
+in `sinf', `subs' or `dnom' that is supported by the font.
Saying just \fB\-inferiors\fR is equivalent to \fB\-inferiors=auto\fR;
otherwise the default is \fB\-noinferiors\fR.
.Sp
@@ -586,14 +599,23 @@ 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 \*(L"liga\*(R" feature to access these.
+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.
.Sp
Specify \fB\-noligatures\fR to disable the generation of ligatures even for fonts
-that do contain a \*(L"liga\*(R" feature.
+that do contain a `liga' feature.
+.IP "\fB\-math\fR" 4
+.IX Item "-math"
+Tells \fBautoinst\fR to create basic math fonts (see above).
+.IP "\fB\-mathspacing\fR=\fIamount\fR" 4
+.IX Item "-mathspacing=amount"
+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!
.IP "\fB\-defaultlining\fR/\fB\-defaultoldstyle\fR" 4
.IX Item "-defaultlining/-defaultoldstyle"
.PD 0
@@ -617,20 +639,24 @@ 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, \fB\-nfsswidth\fR=\fIcode\fR=\fIwidth\fR" 4
-.IX Item "-nfssweight=code=weight, -nfsswidth=code=width"
+.IP "\fB\-nfssweight\fR=\fIcode\fR=\fIweight\fR" 4
+.IX Item "-nfssweight=code=weight"
+.PD 0
+.IP "\fB\-nfsswidth\fR=\fIcode\fR=\fIwidth\fR" 4
+.IX Item "-nfsswidth=code=width"
+.PD
Map the \s-1NFSS\s0 code \fIcode\fR to the given weight or width,
overriding the built-in tables.
Each of these options may be given multiple times,
to override more than one \s-1NFSS\s0 code.
-Example: to map the \*(L"ul\*(R" code to the \*(L"Thin\*(R" weight,
+Example: to map the `ul' code to the `Thin' weight,
use \f(CW\*(C`\-nfssweight=ul=thin\*(C'\fR.
-To inhibit the use of the \*(L"ul\*(R" code completely,
+To inhibit the use of the `ul' code completely,
use \f(CW\*(C`\-nfssweight=ul=\*(C'\fR.
-.IP "\fB\-extra\fR=\fItext\fR" 4
-.IX Item "-extra=text"
-Append \fItext\fR as extra options to the command lines for \fIotftotfm\fR.
-To prevent \fItext\fR from accidentily being interpreted as options
+.IP "\fB\-extra\fR=\fIextra\fR" 4
+.IX Item "-extra=extra"
+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"
@@ -688,9 +714,9 @@ It is up to the user to manually update all databases (i.e., by calling
.IX Item "-typeface=TYPEFACE"
.PD
These options are equivalent to \fIotftotfm\fR's \fI \-\-vendor\fR and \fI \-\-typeface\fR
-options: they change the \*(L"vendor\*(R" and \*(L"typeface\*(R" parts of the names of the
+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 \*(L"lcdftools\*(R" and the font's FontFamily name.
+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.
@@ -698,6 +724,35 @@ not the names of any generated files.
.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.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
Eddie Kohler's \fBTypeTools\fR (\fIhttp://www.lcdf.org/type\fR).
@@ -743,10 +798,21 @@ 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 20200511.
+This document describes \fBautoinst\fR version 20200527.
.SH "RECENT CHANGES"
.IX Header "RECENT CHANGES"
(See the source for the full story, all the way back to 2005.)
+.IP "\fI2020\-05\-27\fR" 12
+.IX Item "2020-05-27"
+Added basic (and still somewhat experimental) math support.
+Implemented the \f(CW\*(C`scale=MatchLowercase\*(C'\fR option value
+in the generated style files.
+`Wide' fonts are mapped to the `sx' \s-1NFSS\s0 code instead of `x',
+to cater for League Mono Variable's Wide and Extended widths.
+The generated style files now use \f(CW\*(C`\etextsup\*(C'\fR and \f(CW\*(C`\etextinf\*(C'\fR
+instead of the more cryptic \f(CW\*(C`\etextsu\*(C'\fR and \f(CW\*(C`\etextin\*(C'\fR to access
+superior and inferior characters
+(though the old forms are retained for backwards compatibility).
.IP "\fI2020\-05\-11\fR" 12
.IX Item "2020-05-11"
When present, use encoding files in the current working directory
@@ -823,12 +889,12 @@ 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 \*(L"liga\*(R" feature),
-\&\fI\-noligatures\fR now disables f\-ligatures (overriding a \*(L"liga\*(R" feature).
+\&\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 \*(L"\s-1SC\*(R"\s0 (previously \fBautoinst\fR only looked for \*(L"SmallCaps\*(R").
+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.
@@ -840,7 +906,7 @@ Fixed a bug that affected \-mergesmallcaps with multiple encodings.
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.
+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"
@@ -860,15 +926,15 @@ 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 \*(L"auto\*(R" value to the \fIinferiors\fR option,
+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 \*(L"long\*(R" codes based on the names
+and width out there, we now create `long' codes based on the names
in the font metadata.
-Then we add \*(L"ssub\*(R" rules to the \fIfd\fR files to map the standard \s-1NFSS\s0 codes
+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).