diff options
author | Karl Berry <karl@freefriends.org> | 2008-07-26 18:10:58 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2008-07-26 18:10:58 +0000 |
commit | 792834f087e5d6fa723eb7b0101693636a22d533 (patch) | |
tree | 94ec1000d52586974175b16f8f1ab06969a153fd /Master/texmf/doc/man/man1/otftotfm.1 | |
parent | fe136e3276dbd8a40f1a1ac60a756cfdfe68ee50 (diff) |
update man pages from la(te)st build
git-svn-id: svn://tug.org/texlive/trunk@9788 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf/doc/man/man1/otftotfm.1')
-rw-r--r-- | Master/texmf/doc/man/man1/otftotfm.1 | 51 |
1 files changed, 48 insertions, 3 deletions
diff --git a/Master/texmf/doc/man/man1/otftotfm.1 b/Master/texmf/doc/man/man1/otftotfm.1 index feae43f9740..e1d87b48cf6 100644 --- a/Master/texmf/doc/man/man1/otftotfm.1 +++ b/Master/texmf/doc/man/man1/otftotfm.1 @@ -1,5 +1,5 @@ '\"t -.ds V 2.48 +.ds V 2.69 .de M .BR "\\$1" "(\\$2)\\$3" .. @@ -205,10 +205,20 @@ LaTeX. We begin with six fonts: "MinionPro-Regular.otf", .PP Our first task is to decide how to encode the fonts. The "encoding scheme" is used by TeX to decide how to typeset accents and symbols like "$". The -"LY1" encoding scheme is a good choice for many OpenType fonts; it -corresponds to the "texnansx.enc" encoding file, so we will supply +"LY1" encoding scheme has reasonable accent support and is a good choice +for many OpenType fonts. LY1 corresponds to the "texnansx.enc" encoding +file, so we will supply .B otftotfm with the "\fB\-e\fR texnansx" option. +.RS +.LP +Expert note: Strictly speaking, LY1 corresponds to the "texnansi.enc" +encoding file. Since the "texnansx.enc" version omits duplicate +characters, it has more room for font-specific glyphs and is generally a +better choice; but if you plan to type characters like "ae" directly into +your editor, rather than using TeX commands like \eae, you should use +"texnansi.enc". +.RE .PP Next, we decide on a naming scheme for the font metric files. Let's use the OpenType font names as a base. (There's generally no need to follow @@ -637,6 +647,41 @@ the output encoding will equal the input encoding (and .B otftotfm will not generate an output encoding). ' +.Sp +.TP 5 +.BI \-\-base\-encodings= file +.B Experts only. +Allow the output font to refer to existing "base" fonts. This can greatly +reduce the number of base fonts generated by +.BR otftotfm ". " +Each line in the +.I file +argument contains a TeX font name (as for +.BR \-\-name ) +and a corresponding literal encoding file (as for +.BR \-\-literal\-encoding ); +for example: +.nf + WarnoProReg\-\-eka eka + WarnoProReg\-\-exp1 exp1 +.fi +The named fonts must have been created by prior runs of +.B otftotfm +on the same input OpenType font, with the same +.BR \-\-extend +and +.BR \-\-slant +options as the current run. The current output font will refer to glyphs +from the named base fonts when possible. If the base fonts cover all +glyphs required by the output font, +.B otftotfm +won't generate any new base fonts at all. The +.I file +can also refer to dotless-J fonts using the following syntax: +.nf + WarnoProReg\-\-lcdfj \- dotlessj +.fi +' .PD ' ' |