diff options
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html')
-rw-r--r-- | Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html index e499936e390..d6275c61b16 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html @@ -4,7 +4,7 @@ <h3>Controlling widows and orphans</h3> <p>Widows (the last line of a paragraph at the start of a page) and orphans (the first line of paragraph at the end of a page) interrupt -the reader's flow, and are generally considered "bad form"; +the reader’s flow, and are generally considered “bad form”; (La)TeX takes some precautions to avoid them, but completely automatic prevention is often impossible. If you are typesetting your own text, consider whether you can bring yourself to change the @@ -19,7 +19,7 @@ stretchability or shrinkability, so if the page maker has to balance the effect of stretching the unstretchable and being penalised, the penalty will seldom win. Therefore, for typical layouts, there are only two sensible settings for the penalties: finite (150 or 500, it -doesn't matter which) to allow widows and orphans, and infinite (10000 +doesn’t matter which) to allow widows and orphans, and infinite (10000 or greater) to forbid them. <p>The problem can be avoided by allowing the pagemaker to run pages short, by using the <code>\</code><code>raggedbottom</code> @@ -27,21 +27,21 @@ directive; however, many publishers insist on the default <code>\</code><code>flushbottom</code>; it is seldom acceptable to introduce stretchability into the vertical list, except at points (such as section headings) where the document design explicitly permits it. -<p>Once you've exhausted the automatic measures, and have a final draft -you want to "polish", you should proceed to manual measures. To +<p>Once you’ve exhausted the automatic measures, and have a final draft +you want to “polish”, you should proceed to manual measures. To get rid of an orphan is simple: precede the paragraph with -<code>\</code><code>clearpage</code> and the paragraph can't start in the wrong place. +<code>\</code><code>clearpage</code> and the paragraph can’t start in the wrong place. <p>Getting rid of a widow can be more tricky. If the paragraph is a long -one, it may be possible to set it 'tight': say <code>\</code><code>looseness</code><code>=-1</code> -immediately after the last word of the paragraph. If that doesn't +one, it may be possible to set it ‘tight’: say <code>\</code><code>looseness</code><code>=-1</code> +immediately after the last word of the paragraph. If that doesn’t work, try adjusting the page size: <code>\</code><code>enlargethispage{<code>\</code><code>baselineskip</code>}</code> may do the job, and get the whole paragraph on one page. Reducing the size of the page by <code>\</code><code>enlargethispage{-<code>\</code><code>baselineskip</code>}</code> may produce a -(more-or-less) acceptable "two-line widow". (Note: +(more-or-less) acceptable “two-line widow”. (Note: <code>\</code><code>looseness</code><code>=1</code>, -increasing the line length by one, seldom seems to work - the looser -paragraph typically has a one-word final line, which doesn't look much +increasing the line length by one, seldom seems to work — the looser +paragraph typically has a one-word final line, which doesn’t look much better than the straight widow.) <p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows</a> </body> |