1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<head>
<title>UK TeX FAQ -- question label fuzzy-T1</title>
</head><body>
<h3>Fonts go fuzzy when you switch to T1</h3>
<!-- crippled blurry -->
<p/>You’ve been having problems with hyphenation, and someone has
suggested that you should use “<code>\</code><code>usepackage[T1]{fontenc}</code>”
to help sort them out. Suddenly you find that your final PDF
has become fuzzy. The problem may arise whether you are using PostScript
output and then distilling it, or you are using PDFTeX for the
whole job.
<p/>In fact, this is the same problem as most others about the
<a href="FAQ-dvips-pdf.html">quality of PDF</a>: you’ve abandoned
your previous setup using Type 1 versions of the CM fonts, and
<i>dvips</i> has inserted Type 3 versions of the EC fonts
into your document output. (See
“<a href="FAQ-adobetypen.html">Adobe font types</a>
for details of these font types; also, note that the font
<em>encoding</em> T1
has nothing directly to do with the font <em>format</em> Type 1).
<p/>However, as noted in
“<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>”,
Type 1 versions of CM-like fonts in T1 (or equivalent) encoding
are now available, both as “real” fonts, and as virtual font sets.
One solution, therefore, is to use one of these alternatives.
<p/>The alternative is to switch font family altogether, to something like
<i>Times</i> (as a no-thought default) or one of the many more pleasing
Adobe-encoded fonts. The default action of <i>fontinst</i>, when
creating metrics for such a font, is to create settings for both OT1
and T1 encodings, so there’s little change in what goes on (at the
user level) even if you have switched to T1 encoding when using the
fonts.
<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1</a>
</body>
|
