summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html80
1 files changed, 40 insertions, 40 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
index 861205a5f0a..963117f2a30 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-overfull.html
@@ -5,36 +5,36 @@
<p/>When TeX is building a paragraph, it can make several attempts to
get the line-breaking right; on each attempt it runs the same
algorithm, but gives it different parameters. You can affect the way
-TeX&rsquo;s line breaking works by adjusting the parameters: this answer
-deals with the &ldquo;tolerance&rdquo; and stretchability parameters. The other
-vital &lsquo;parameter&rsquo; is the set of hyphenations to be applied: see
-&ldquo;<a href="FAQ-nohyph.html">my words aren&rsquo;t being hyphenated</a>&rdquo;
+TeX&#8217;s line breaking works by adjusting the parameters: this answer
+deals with the &#8220;tolerance&#8221; and stretchability parameters. The other
+vital &#8216;parameter&#8217; is the set of hyphenations to be applied: see
+&#8220;<a href="FAQ-nohyph.html">my words aren&#8217;t being hyphenated</a>&#8221;
(and the questions it references) for advice.
-<p/>If you&rsquo;re getting an undesired &ldquo;overfull box&rdquo;, what has happened is
-that TeX has given up: the parameters you gave it don&rsquo;t allow it to
-produce a result that <em>doesn&rsquo;t</em> overfill. In this circumstance,
+<p/>If you&#8217;re getting an undesired &#8220;overfull box&#8221;, what has happened is
+that TeX has given up: the parameters you gave it don&#8217;t allow it to
+produce a result that <em>doesn&#8217;t</em> overfill. In this circumstance,
Knuth decided the best thing to do was to produce a warning, and to
allow the user to solve the problem. (The alternative, silently to go
-beyond the envelope of &ldquo;good taste&rdquo; defined for this run of TeX,
+beyond the envelope of &#8220;good taste&#8221; defined for this run of TeX,
would be distasteful to any discerning typographer.) The user can
-almost always address the problem by rewriting the text that&rsquo;s
-provoking the problem &mdash; but that&rsquo;s not always possible, and in some
-cases it&rsquo;s impossible to solve the problem without adjusting the
+almost always address the problem by rewriting the text that&#8217;s
+provoking the problem &#8212; but that&#8217;s not always possible, and in some
+cases it&#8217;s impossible to solve the problem without adjusting the
parameters. This answer discusses the approaches one might take to
-resolution of the problem, on the assumption that you&rsquo;ve got the
+resolution of the problem, on the assumption that you&#8217;ve got the
hyphenation correct.
-<p/>The simplest case is where a &lsquo;small&rsquo; word fails to break at the end of
-a line; pushing the entire word to a new line isn&rsquo;t going to make much
-difference, but it might make things just bad enough that TeX won&rsquo;t
+<p/>The simplest case is where a &#8216;small&#8217; word fails to break at the end of
+a line; pushing the entire word to a new line isn&#8217;t going to make much
+difference, but it might make things just bad enough that TeX won&#8217;t
do it by default. In such a case on can <em>try</em> the LaTeX
<code>\</code><code>linebreak</code> command: it may solve the problem, and if it does, it
will save an awful lot of fiddling. Otherwise, one needs to adjust
-parameters: to do that we need to recap the details of TeX&rsquo;s line
+parameters: to do that we need to recap the details of TeX&#8217;s line
breaking mechanisms.
-<p/>TeX&rsquo;s first attempt at breaking lines is performed without even
-trying hyphenation: TeX sets its &ldquo;tolerance&rdquo; of line breaking
+<p/>TeX&#8217;s first attempt at breaking lines is performed without even
+trying hyphenation: TeX sets its &#8220;tolerance&#8221; of line breaking
oddities to the internal value <code>\</code><code>pretolerance</code>, and sees what
-happens. If it can&rsquo;t get an acceptable break, TeX adds the
+happens. If it can&#8217;t get an acceptable break, TeX adds the
hyphenation points allowed by the current patterns, and tries again
using the internal <code>\</code><code>tolerance</code> value. If this pass also fails, and
the internal <code>\</code><code>emergencystretch</code> value is positive, TeX will try
@@ -44,46 +44,46 @@ to the spaces in each line.
hyphenation) that you can change: <code>\</code><code>pretolerance</code>, <code>\</code><code>tolerance</code>
and <code>\</code><code>emergencystretch</code>. Both the <code>tolerance</code> values are
simple numbers, and should be set by TeX primitive count
-assignment &mdash; for example
+assignment &#8212; for example
<blockquote>
<pre>
\pretolerance=150
</pre>
</blockquote><p>
-For both, an &ldquo;infinite&rdquo; tolerance is represented by the value
+For both, an &#8220;infinite&#8221; tolerance is represented by the value
<code>10</code><code>000</code>, but infinite tolerance is rarely
appropriate, since it can lead to very bad line breaks indeed.
-<p/><code>\</code><code>emergencystretch</code> is a TeX-internal &lsquo;dimen&rsquo; register, and can
+<p/><code>\</code><code>emergencystretch</code> is a TeX-internal &#8216;dimen&#8217; register, and can
be set as normal for dimens in Plain TeX; in LaTeX, use
-<code>\</code><code>setlength</code> &mdash; for example:
+<code>\</code><code>setlength</code> &#8212; for example:
<blockquote>
<pre>
\setlength{\emergencystretch}{3em}
</pre>
</blockquote><p>
-<p/>The choice of method has time implications &mdash; each of the
+<p/>The choice of method has time implications &#8212; each of the
passes takes time, so adding a pass (by changing
<code>\</code><code>emergencystretch</code>) is less desirable than suppressing one (by
-changing <code>\</code><code>pretolerance</code>). However, it&rsquo;s unusual nowadays to find a
-computer that&rsquo;s slow enough that the extra passes are really
+changing <code>\</code><code>pretolerance</code>). However, it&#8217;s unusual nowadays to find a
+computer that&#8217;s slow enough that the extra passes are really
troublesome.
<p/>In practice, <code>\</code><code>pretolerance</code> is rarely used other than to manipulate
the use of hyphenation; Plain TeX and LaTeX both set its value
to <code>100</code>. To suppress the first scan of paragraphs, set
<code>\</code><code>pretolerance</code> to <code>-1</code>.
<p/><code>\</code><code>tolerance</code> is often a good method for adjusting spacing;
-Plain TeX and LaTeX both set its value to <code>200</code>. LaTeX&rsquo;s
+Plain TeX and LaTeX both set its value to <code>200</code>. LaTeX&#8217;s
<code>\</code><code>sloppy</code> command sets it to <code>9999</code>, as does the
<code>sloppypar</code> environment. This value is the largest
available, this side of infinity, and can allow pretty poor-looking
-breaks (this author rarely uses <code>\</code><code>sloppy</code> &ldquo;bare&rdquo;, though he does
-occasionally use <code>sloppypar</code> &mdash; that way, the change of
+breaks (this author rarely uses <code>\</code><code>sloppy</code> &#8220;bare&#8221;, though he does
+occasionally use <code>sloppypar</code> &#8212; that way, the change of
<code>\</code><code>tolerance</code> is confined to the environment). More satisfactory is
to make small changes to <code>\</code><code>tolerance</code>, incrementally, and then to look to
see how the change affects the result; very small increases can often
-do what&rsquo;s necessary. Remember that <code>\</code><code>tolerance</code> is a paragraph
-parameter, so you need to ensure it&rsquo;s actually applied &mdash; see
-&ldquo;<a href="FAQ-paraparam.html">ignoring paragraph parameters</a>&rdquo;.
+do what&#8217;s necessary. Remember that <code>\</code><code>tolerance</code> is a paragraph
+parameter, so you need to ensure it&#8217;s actually applied &#8212; see
+&#8220;<a href="FAQ-paraparam.html">ignoring paragraph parameters</a>&#8221;.
LaTeX users could use an environment like:
<blockquote>
<pre>
@@ -97,9 +97,9 @@ LaTeX users could use an environment like:
enclosing entire paragraphs (or set of paragraphs) in it.
<p/>The value of <code>\</code><code>emergencystretch</code> is added to the assumed
stretchability of each line of a paragraph, in a further run of the
-paragraph formatter in case that the paragraph can&rsquo;t be made to look
+paragraph formatter in case that the paragraph can&#8217;t be made to look
right any other way. (The extra scan happens if
-<code>\</code><code>emergencystretch&gt;0pt</code> &mdash; if it&rsquo;s zero or negative, no gain
+<code>\</code><code>emergencystretch&#62;0pt</code> &#8212; if it&#8217;s zero or negative, no gain
could be had from rerunning the paragraph setter.) The example above
set it to <code>3em</code>; the Computer Modern fonts ordinarily fit three
space skips to the <code>em</code>, so the change would allow anything up
@@ -110,21 +110,21 @@ width. It is therefore clear that <code>\</code><code>emergencystretch</code> n
treated with a degree of caution.
<p/>More subtle (but more tricky to manage) are the microtypographic
extensions provided by PDFTeX. Since PDFTeX is the default
-&lsquo;engine&rsquo; for LaTeX and ConTeXt work in all distributions,
+&#8216;engine&#8217; for LaTeX and ConTeXt work in all distributions,
nowadays, the extensions are available to all. There are two
extensions, margin kerning and font expansion; margin kerning only
affects the visual effect of the typeset page, and has little effect
-on the ability of the paragraph setter to &ldquo;get things right&rdquo;.
+on the ability of the paragraph setter to &#8220;get things right&#8221;.
Font expansion works like a subtler version of the trick that
-<code>\</code><code>emergencystretch</code> plays: PDFTeX &lsquo;knows&rsquo; that your current font
+<code>\</code><code>emergencystretch</code> plays: PDFTeX &#8216;knows&#8217; that your current font
may be stretched (or shrunk) to a certain extent, and will do that
-&ldquo;on the fly&rdquo; to optimise the setting of a paragraph. This is a
+&#8220;on the fly&#8221; to optimise the setting of a paragraph. This is a
powerful tool in the armoury of the typesetter.
<p/>As mentioned above, the microtypographic extensions are tricky beasts
to control; however, the <i>microtype</i> package relieves the user
of the tedious work of specifying how to perform margin adjustments
-and how much to scale each font &hellip; for the fonts the package
-knows about; it&rsquo;s a good tool, and users who can take on the
+and how much to scale each font &#8230; for the fonts the package
+knows about; it&#8217;s a good tool, and users who can take on the
specification of adjustments for yet more fonts are always welcome.
<dl>
<dt><tt><i>microtype.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse the directory</a>)