diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html index c691672103f..8904a3ee3de 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html @@ -11,7 +11,7 @@ acquire a new font. One important question is the <em>encoding</em> of (Latin character) fonts; while we all more or less agree about the position of about 96 characters in fonts (the basic ASCII set), the rest of the (typically) 256 vary. The most obvious problems are with -floating accents and special characters such as the ‘pounds sterling’ +floating accents and special characters such as the ‘pounds sterling’ sign. There are three ways of dealing with this: either you change the TeX macros which reference the characters (not much fun, and error-prone); or you change the encoding of the font (easier than you @@ -21,20 +21,20 @@ LaTeX2e has facilities for dealing with fonts in different encodings; read the <a href="FAQ-books.html"><em>LaTeX Companion</em></a> for more details. In practice, if you do much non-English (but Latin script) typesetting, you are strongly recommended to use the -<i>fontenc</i> package with option ‘<code>T1</code>’ to select -<a href="FAQ-ECfonts.html">‘Cork’</a> encoding. -A useful alternative is Y&Y’s “private” LY1 encoding, -which is designed to sit well with “Adobe standard” encoded fonts. +<i>fontenc</i> package with option ‘<code>T1</code>’ to select +<a href="FAQ-ECfonts.html">‘Cork’</a> encoding. +A useful alternative is Y&Y’s “private” LY1 encoding, +which is designed to sit well with “Adobe standard” encoded fonts. Basic support of LY1 is available on CTAN: note that the -“relation with Adobe’s encoding” means that there are no +“relation with Adobe’s encoding” means that there are no virtual fonts in the LY1 world. -<p/>Alan Jeffrey’s <i>fontinst</i> package is an AFM to +<p/>Alan Jeffrey’s <i>fontinst</i> package is an AFM to TFM converter written in TeX; it is used to generate the -files used by LaTeX2e’s PSNFSS package to support use of +files used by LaTeX2e’s PSNFSS package to support use of PostScript fonts. It is a sophisticated package, not for the faint-hearted, but is powerful enough to cope with most needs. Much of its power relies on the use of <a href="FAQ-virtualfonts.html">virtual fonts</a>. -<p/>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, +<p/>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, distributed with <i>dvips</i>, is fast and efficient; note that the metrics and styles that come with <i>dvips</i> are <em>not</em> currently LaTeX2e compatible. |