diff options
author | Karl Berry <karl@freefriends.org> | 2009-05-22 23:51:44 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2009-05-22 23:51:44 +0000 |
commit | 566f5207d7e3cafb0633d31277067336ccd9cca7 (patch) | |
tree | 7af53e7ac405185168bc1dc38c4e820f442b78d0 /Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html | |
parent | b0beea26ffffd915bb6d9b82f2d65a0a05b7e23b (diff) |
move generic english documents out of texmf-doc
git-svn-id: svn://tug.org/texlive/trunk@13396 c570f23f-e606-0410-a88d-b1316a301751
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.html | 34 |
1 files changed, 34 insertions, 0 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 new file mode 100644 index 00000000000..3c65b2248d0 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html @@ -0,0 +1,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> |