summaryrefslogtreecommitdiff
path: root/support/pkfix-helper/pkfix-helper.1
diff options
context:
space:
mode:
Diffstat (limited to 'support/pkfix-helper/pkfix-helper.1')
-rw-r--r--support/pkfix-helper/pkfix-helper.124
1 files changed, 22 insertions, 2 deletions
diff --git a/support/pkfix-helper/pkfix-helper.1 b/support/pkfix-helper/pkfix-helper.1
index 648be2b5b3..468c03024a 100644
--- a/support/pkfix-helper/pkfix-helper.1
+++ b/support/pkfix-helper/pkfix-helper.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35)
+.\" Automatically generated by Pod::Man 4.11 (Pod::Simple 3.35)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "PKFIX-HELPER 1"
-.TH PKFIX-HELPER 1 "2020-04-19" "v1.5" " "
+.TH PKFIX-HELPER 1 "2020-07-21" "v1.6" " "
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -339,6 +339,14 @@ None of the fonts considered for a match include all of the characters
in font \fIname\fR. The user should use the \fB\-\-force\fR option to inform
\&\fBpkfix-helper\fR which font to use or the \fB\-\-keep\fR option to retain
the original, bitmapped font.
+.ie n .IP """Processing \fIname\fP ... done (\fIfont\fP with mismatch=\fInumber\fP, tied with \fIfont\fP...)""" 4
+.el .IP "\f(CWProcessing \f(CIname\f(CW ... done (\f(CIfont\f(CW with mismatch=\f(CInumber\f(CW, tied with \f(CIfont\f(CW...)\fR" 4
+.IX Item "Processing name ... done (font with mismatch=number, tied with font...)"
+The best match for \fIname\fR is font \fIfont\fR. A perfect match has a
+\&\fInumber\fR of 0.00000. Worse matches observe larger values. If a tie
+is reported, this means one or more fonts matched \fIname\fR equally well
+(i.e., they see the same \fInumber\fR). In this case, \fBpkfix-helper\fR
+selects the qualitatively most likely font as the winner.
.SH "EXAMPLES"
.IX Header "EXAMPLES"
For the purpose of the following examples, assume that \fIoldfile.ps\fR
@@ -517,6 +525,18 @@ below), who may be able to enhance \fBpkfix-helper\fR to handle them.
Files produced using the \fB\-\-tex\fR option are Plain TeX files and
therefore must be compiled with \fBtex\fR (or a variant such as
\&\fBpdftex\fR, \fBluatex\fR, \fBxetex\fR, etc.), \fInot\fR with \fBlatex\fR.
+.PP
+\&\fBdvips\fR\-produced PostScript files can be structured in sections,
+demarcated by \f(CW%DVIPSBeginSection\fR and \f(CW%DVIPSEndSection\fR. Font
+names are local to a section. Hence, a font named \f(CW\*(C`Fa\*(C'\fR may map to
+\&\f(CW\*(C`cmex10\*(C'\fR in one section and to \f(CW\*(C`cmmi7\*(C'\fR in another. \fBpkfix-helper\fR
+assigns every font in a multi-section document a unique name by
+appending a section-number suffix: \f(CW\*(C`Fa_S01\*(C'\fR, \f(CW\*(C`Fa_S02\*(C'\fR, etc.
+.PP
+Font names are processed in decreasing order of the number of
+characters they have represented in the document. That is, if the
+document includes 10 characters from \f(CW\*(C`Fa\*(C'\fR and 23 characters from
+\&\f(CW\*(C`Fb\*(C'\fR, \fBpkfix-helper\fR will process \f(CW\*(C`Fb\*(C'\fR before \f(CW\*(C`Fa\*(C'\fR.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBpkfix\fR\|(1), \fBdvips\fR\|(1), \fBtex\fR\|(1), \fBgs\fR\|(1)