summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html34
1 files changed, 0 insertions, 34 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html
deleted file mode 100644
index 9428194465b..00000000000
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<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&#8217;ve been having problems with hyphenation, and someone has
-suggested that you should use &#8220;<code>\</code><code>usepackage[T1]{fontenc}</code>&#8221;
-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&#8217;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
-&#8220;<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
-&#8220;<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>&#8221;,
-Type 1 versions of CM-like fonts in T1 (or equivalent) encoding
-are now available, both as &#8220;real&#8221; 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&#8217;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>