summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex75
1 files changed, 54 insertions, 21 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
index 8eb21040059..6bc78ba7267 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
@@ -1,4 +1,4 @@
-% $Id: faq-t-g-wr.tex,v 1.5 2010/03/26 22:48:51 rf10 Exp rf10 $
+% $Id: faq-t-g-wr.tex,v 1.7 2010/08/16 22:04:13 rf10 Exp rf10 $
\section{Things are Going Wrong\dots{}}
@@ -244,7 +244,7 @@ automatic prevention is often impossible. If you are typesetting your
own text, consider whether you can bring yourself to change the
wording slightly so that the page break will fall differently.
-The page maker, when forming a page, takes account of
+The \AllTeX{} page maker, when forming a page, takes account of variables
\csx{widowpenalty} and \csx{clubpenalty} (which relates to orphans!).
These penalties are usually set to the moderate value of \texttt{150}; this
offers mild discouragement of bad breaks. You can increase the values
@@ -257,30 +257,36 @@ only two sensible settings for the penalties: finite (150 or 500, it
doesn't matter which) to allow widows and orphans, and infinite (10000
or greater) to forbid them.
-The problem can be avoided by allowing
-the pagemaker to run pages short, by using the \csx{raggedbottom}
-directive; however, many publishers insist on the default
-\csx{flushbottom}; 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.
+The problem can be avoided by allowing the pagemaker to run pages
+short, by using the \csx{raggedbottom} directive; however, many
+publishers insist on the default \csx{flushbottom}; 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.
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
\csx{clearpage} and the paragraph can't start in the wrong place.
-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 \csx{looseness}\texttt{=-1}
-immediately after the last word of the paragraph. If that doesn't
-work, try adjusting the page size:
-\cmdinvoke{enlargethispage}{\csx{baselineskip}} may do the job, and
-get the whole paragraph on one page. Reducing the size of the page by
-\cmdinvoke{enlargethispage}{-\csx{baselineskip}} may produce a
-(more-or-less) acceptable ``two-line widow''. (Note:
-\csx{looseness}\texttt{=1},
-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.)
+Getting rid of a widow can be more tricky. Options are
+\begin{itemize}
+\item If the previous page contains a long paragraph with a short last
+ line, it may be possible to set it `tight': write
+ \csx{looseness}\texttt{=-1} immediately after the last word of the
+ paragraph.
+\item If that doesn't work, adjusting the page size, using
+ \cmdinvoke{enlargethispage}{\csx{baselineskip}} to `add a line' to
+ the page, which may have the effect of getting the whole paragraph
+ on one page.
+\item Reducing the size of the page by
+ \cmdinvoke{enlargethispage}{-\csx{baselineskip}} may produce a
+ (more-or-less) acceptable ``two-line widow''.
+\end{itemize}
+Note that \csx{looseness}\texttt{=1} (which should increase the line
+length by one) seldom has the right effect~--- the looser paragraph
+typically has a one-word final line, which doesn't look much better
+than the original widow.
\subsection{Things have ``gone away''}
@@ -402,4 +408,31 @@ necessary very often...).
\begin{ctanrefs}
\item[dviasm.py]\CTANref{dviasm}
\item[dtl]\CTANref{dtl}
-\end{ctanrefs} \ No newline at end of file
+\end{ctanrefs}
+
+\Question[Q-initex]{What's happened to \ProgName{initex}?}
+
+In the beginning, \AllTeX{} was stretching the capacity of every
+system it was ported to, so there was a premium on reducing the size
+of executables. One way of doing this was to have a separate
+executable, \ProgName{initex}, that had things in it that aren't
+needed in ordinary document runs~--- notably \csx{patterns} (which
+builds hyphenation tables), and \csx{dump} (which writes out a format).
+
+On modern systems, the size of this code is insignificant in
+comparison to the memory available, and maintaining separate programs
+has been found sufficiently error-prone that free Unix-style system
+distributions have abolished \ProgName{initex} and its friends and
+relations such as \ProgName{inipdftex} in favour of a single
+executable (that is, just \ProgName{tex} or \ProgName{pdftex}) that
+will ``do what \ProgName{initex} (or whatever) used to do'' if it
+detects the command option ``\texttt{-ini}''.
+
+The change happened with the advent of te\TeX{} version
+3.0, which appeared at the beginning of 2005. At that time,
+\texlive{} was following te\TeX{}, so that year's \texlive{}
+distribution would also have dropped \ProgName{initex}.
+
+It would appear that the equation is somewhat different for the
+\miktex{} developers, since that system continues to offer an
+\ProgName{initex} executable.