summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex61
1 files changed, 31 insertions, 30 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
index bcac3f260d8..a10e82d6899 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
@@ -1,4 +1,4 @@
-% $Id: faq-how-do-i.tex,v 1.34 2011/09/03 18:56:20 rf10 Exp rf10 $
+% $Id: faq-how-do-i.tex,v 1.37 2012/02/07 21:46:08 rf10 Exp $
\section{How do I do\dots{}?}
@@ -1610,8 +1610,9 @@ in the neighbourhood of list environments (unless you change your
\end{narrowversion}
The syntax of the \environment{wraptable} environment is similar.
- Height can be omitted, in which case it will be calculated by the
- package; the package will use the greater of the specified and the
+ The \emph{\texttt{height}} may be omitted, in which case it will
+ be calculated from the size of the figure; the package will use
+ the greater of the specified and the
actual width. The \texttt{\{l,r,\emph{etc}.\}} parameter may
also be specified as \texttt{i}\emph{(nside)} or
\texttt{o}\emph{(utside)} for two-sided documents, and uppercase
@@ -1706,32 +1707,21 @@ x y
However, this doesn't satisfy everyone: many want the labelling in a
single cell at the top left of the table. It sounds a simple enough
requirement, yet it calls for some slightly tricky \LaTeX{} coding.
-The \Package{slashbox} package does the job for you: it defines
-commands \csx{slashbox} and \csx{backslashbox}, each taking the two
-labels as arguments. It draws a picture with the two labels on either
-side of a slanting line; the command (and hence the picture) may be
-placed in the corner cell, where the labelled row and column meet.
-
-The package isn't the world's neatest: it uses \LaTeX{}
-\environment{picture} mode to draw its line, and picture mode has many
-tedious restrictions (and doesn't, in all honesty, produce
-particularly good pictures). Load slashbox with the \Package{pict2e}
-package, and at least the picture quality will be improved.
-
-Documentation of \Package{slashbox} is less than satisfactory: a
-\LaTeX{} source file of rather startling starkness accompanies the
-package file in the distribution, and the distribution includes that
-file processed to a \acro{PDF} file for reading over the net, if
-necessary. (The third example in the file shows the effect of
-\environment{picture} mode's restrictions: the dividing line doesn't
-go from corner to corner in the box: to correct this requires revision
-of \Package{slashbox}~--- \Package{pict2e} alone doesn't help in this
-regard.)
+The \Package{diagbox} package does this job for you: it defines a
+command \csx{diagbox} whose two arguments provide the texts to be
+used; an optional argument may be used for fine tuning of the result.
+It draws a picture with the two labels on either side of a slanting
+line; the command (and hence the picture) may be placed in the corner
+cell, where the labelled row and column meet.
+
+The \Package{diagbox} package supersedes \Package{slashbox}; the older
+package's commands \csx{slashbox} and \csx{backslashbox} are provided
+in a compatible way in the newer package, to ease transition.
\begin{ctanrefs}
-\item[pict2e.sty]\CTANref{pict2e}
+\item[diagbox.sty]\CTANref{diagbox}
\item[slashbox.sty]\CTANref{slashbox}
\end{ctanrefs}
-\LastEdit{2010-11-02}
+\LastEdit{2010-11-22}
\Question[Q-wholerow]{How to change a whole row of a table}
@@ -2335,6 +2325,8 @@ advice, you can:
tools distribution; they're noticeably less efficient than the
standard \environment{tabular} environment, but they do allow
footnotes.
+\item Use \Package{tablefootnote}; it provides a \csx{tablefootnote},
+ which does the job without fuss.
\item Use \Package{footnote}, which provides an
\environment{savenotes} which collects all footnotes and emits them
at the end of the environment; thus if you put your
@@ -2357,10 +2349,12 @@ recommend any of them, believing that table notes are the way to go\dots{}
\item[footnote.sty]Distributed as part of \CTANref{mdwtools}[footnote]
\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}[mdwtab]
+\item[tablefootnote.sty]\CTANref{tablefootnote}
\item[threeparttable.sty]\CTANref{threeparttable}
\item[threeparttablex.sty]\CTANref{threeparttablex}
\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx]
\end{ctanrefs}
+\LastEdit{2012-02-07}
\Question[Q-ftnsect]{Footnotes in \LaTeX{} section headings}
@@ -2821,8 +2815,15 @@ archive (e.g., \extension{tar.gz} or \extension{zip}) of the files needed by you
document; it comes with configuration files for use with
\ProgName{teTeX} and \ProgName{\miktex{}}. It's plainly useful when
you're sending the first copy of a document.
+
+The \ProgName{mkjobtexmf} finds which files are used in a `job',
+either via the \texttt{-recorder} option of \tex{}, or by using the
+(Unix) command \ProgName{strace} to keep an eye on what \tex{} is
+doing. The files thus found are copied (or linked) to a directory
+which may then be saved for transmission or archiving.
\begin{ctanrefs}
\item[bundledoc]\CTANref{bundledoc}
+\item[mkjobtexmf]\CTANref{mkjobtexmf}
\item[snapshot.sty]\CTANref{snapshot}
\end{ctanrefs}
@@ -3188,8 +3189,8 @@ following minimal solution:
\begin{wideversion}
\begin{verbatim}
\def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}}
-\RCS$Revision: 1.34 $ % or any RCS keyword
-\RCS$Date: 2011/09/03 18:56:20 $
+\RCS$Revision: 1.37 $ % or any RCS keyword
+\RCS$Date: 2012/02/07 21:46:08 $
...
\date{Revision \RCSRevision, \RCSDate}
\end{verbatim}
@@ -3199,8 +3200,8 @@ following minimal solution:
\def\RCS$#1: #2 ${\expandafter
\def\csname RCS#1\endcsname{#2}%
}
-\RCS$Revision: 1.34 $ % or any RCS keyword
-\RCS$Date: 2011/09/03 18:56:20 $
+\RCS$Revision: 1.37 $ % or any RCS keyword
+\RCS$Date: 2012/02/07 21:46:08 $
...
\date{Revision \RCSRevision, \RCSDate}
\end{verbatim}