summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex')
-rw-r--r--Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex402
1 files changed, 218 insertions, 184 deletions
diff --git a/Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex b/Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex
index 41b96364831..9be22e35c69 100644
--- a/Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex
+++ b/Master/texmf-dist/source/latex/koma-script/doc/english/typearea.tex
@@ -40,47 +40,27 @@
%
% ----------------------------------------------------------------------
%
-% Kapitel über typearea in der KOMA-Script-Anleitung
+% Kapitel ueber typearea in der KOMA-Script-Anleitung
% Verwaltet von Markus Kohm
%
% ======================================================================
-\ProvidesFile{typearea.tex}[2009/01/26 KOMA-Script guide (chapter: typearea)]
-\translator{Markus Kohm\and Gernot Hassenpflug}
+\ProvidesFile{typearea.tex}[2012/04/02 KOMA-Script guide (chapter: typearea)]
+\translator{Markus Kohm\and Gernot Hassenpflug\and Krickette Murabayashi}
-% Date of translated german file: 2006-11-29
-% Updated: 2008-01-02
+% Date of translated german file: 2012/02/01
\chapter{Construction of the Page Layout with \Package{typearea}}
\labelbase{typearea}
-%\textsc{Note:} Following commands are still missing in this chapter:
-%\Macro{KOMAoptions}, \Macro{KOMAoption}, \Macro{recalctypearea}.
-%
-%\textsc{Note:} Following options are still missing in this chapter:
-%\OptionValue{BCOR}{current}, \OptionValue{twoside}{semi},
-%\KOption{headheight}\PName{height}, \OptionValue{pagesize}{automedia}.
-%
-%% Done 2 Jan: sections 2.1, 2.2, 2.3
-%% section 2.4 skipped
-%% Done 3 Jan: parts of section 2.5
-%% \OptionValue{BCOR}{current}
-%% \OptionValue{twoside}{semi}
-%% \OptionValue{headheight}{height}
-%% Done 4 Jan: completed section 2.5
-%% \OptionValue{areaset}
-%% section 2.4 (common.tex)
-%% section 2.6
-%% \OptionValue{pagesize}{automedia}
-%% section 2.7
-
Many {\LaTeX} classes, including the standard classes, present the user
with the largely fixed configuration of margins and typearea. With the
standard classes, the configuration determined is very much dependent
-on the chosen font size. There do exist separate packages, such as
+on the chosen font size. There are
+separate packages, such as
\Package{geometry}\IndexPackage{geometry} (see
\cite{package:geometry}), which give the user complete control, but
-also full responsibility, for the settings of typearea and margins.
+also full responsibility, of the settings of typearea and margins.
\KOMAScript{} takes a somewhat different approach with its
\Package{typearea} package. Here the user is given several
@@ -93,15 +73,16 @@ the \Package{scrbase} package. The latter is explained in the expert
section \iffree{of this document}{of this book} in
\autoref{cha:scrbase} from \autopageref{cha:scrbase} onwards. The
majority of the rules documented there are however not directed at the
-user, but rather at class- and package authors.
+user, but rather at authors of classes and packages.
+
\section{Fundamentals of Page Layout}
\label{sec:typearea.basics}
\begin{Explain}
If you look at a single page of a book or other printed materials,
- you will see that it consists of top, bottom, left and right
- margins, a (running) head area, the text block and a (running) foot
+ you will see that it consists of top, bottom, left, and right
+ margins, a (running) head area, the text block, and a (running) foot
area. There is also a space between the head area and the text
block, and between the text block and the foot area. The relations
between these areas are called the \emph{page
@@ -112,21 +93,22 @@ user, but rather at class- and package authors.
%% \ifx\BUCH\undefined\cite{DANTE:TK0402:MJK}\else(siehe
%% \autoref{cha:typeareaconstruction})\fi
The literature contains much discussion of different algorithms and
- heuristic approaches for constructing a good page layout. Often
- mentioned is an approach which involves diagonals and their
- intersections. The result is a page where the text block proportions
- are related to the proportions of the \emph{page}. In a
- single-sided document, the left and the right margin should have
- equal widths. The relation of the upper margin to the lower margin
- should be 1\(:\)2. In a double-sided document\Index{double-sided}
- (e.\,g. a book) however, the complete inner margin (the margin at
- the spine) should be the same as each of the two outer margins; in
- other words, a single page contributes only half of the inner
+ heuristic approaches for constructing a good page layout%
+ \iffree{ \cite{DANTE:TK0402:MJK}}{. A short introduction to the basics may
+ be found at \autoref{cha:typeareaconstruction}}%
+ . Often mentioned is an approach which involves diagonals and their
+ intersections. The result is a page where the text block proportions are
+ related to the proportions of the \emph{page}. In a single-sided document,
+ the left and the right margin should have equal widths. The relation of the
+ upper margin to the lower margin should be 1\(:\)2. In a double-sided
+ document\Index{double-sided} (e.\,g. a book) however, the complete inner
+ margin (the margin at the spine) should be the same as each of the two outer
+ margins; in other words, a single page contributes only half of the inner
margin.
In the previous paragraph, we mentioned and emphasized \emph{the
page}. Erroneously, it is often thought that with the page format
- the page is also meant the paper format.\Index[indexmain]{paper
+ the page is the same as the paper format.\Index[indexmain]{paper
format} However, if you look at a bound document, it is obvious
that part of the paper vanishes in the
binding\Index[indexmain]{binding} and is no longer part of the
@@ -137,7 +119,8 @@ user, but rather at class- and package authors.
this amount to the width of the inner margin. This is called the
\emph{binding correction}.\Index[indexmain]{binding correction} The
binding correction is therefore calculated as part of the
- \emph{gutter}\Index[indexmain]{gutter}, not however of the visible
+ \emph{gutter}\Index[indexmain]{gutter}, not % however of
+ the visible
inner margin.
The binding correction depends on the process of actually
@@ -228,9 +211,9 @@ user, but rather at class- and package authors.
usable compromise. This requires well-chosen leading, but {\LaTeX}'s
default is usually good enough. Longer line lengths should only be
considered for highly-developed readers who spend several hours
- daily reading. However, even for such, line lengths greater than 80
+ daily reading. However, even for such readers, line lengths greater than 80
characters are unsuitable. In any case, the leading must be
- appropriately chosen. An extra 5\% to 10\% are recommended as a good
+ appropriately chosen. An extra 5\% to 10\% is recommended as a good
rule of thumb. With fonts such as Palatino, which require some 5\%
more leading even at normal line lengths, even more can be
required.
@@ -267,24 +250,28 @@ user, but rather at class- and package authors.
\begin{Explain}
The easiest way to make sure that the text area has the same ratios
- as the page is as follows: first, one subtracts the part \Var{BCOR},
- required for the binding correction\Index{binding correction}, from
- the inner edge of the paper, and divides the rest of the page
- vertically into \Var{DIV} rows of equal height; next, one divides
- the page horizontally into the same number (\Var{DIV}) of columns;
- then, one takes the uppermost row as the upper margin and the two
- lowermost rows as the lower margin (if one is printing double-sided,
- one must similarly take the innermost column as the inner margin and
- the two outermost columns as the outer margin); then, one adds the
- binding correction \Var{BCOR} to the inner margin. What now remains
- of the page is the text area.\Index{text area} The width and the
- height of the text area and margins result automatically from the
- number of rows and columns \Var{DIV}. Since the margins always need
- three stripes, \Var{DIV} must be necessarily greater than three. In
- order that the text area occupy at least twice as much space as the
- margins, \Var{DIV} should really be equal to or greater than 9. With
- this value, the construction is also known as the \emph{classical
- division factor of 9} (see \autoref{fig:typearea.nineparts}).
+ as the page is as follows:
+ \begin{itemize}
+ \item First, subtract the part \Var{BCOR}, required for the binding
+ correction\Index{binding correction}, from the inner edge of the paper,
+ and divide the rest of the page vertically into \Var{DIV} rows of equal
+ height.
+ \item Next, divide the page horizontally into the same number (\Var{DIV}) of
+ columns.
+ \item Then, take the uppermost row as the upper margin and the two lowermost
+ rows as the lower margin. If you are printing double-sided, you similarly
+ take the innermost column as the inner margin and the two outermost
+ columns as the outer margin.
+ \item Then add the binding correction \Var{BCOR} to the inner margin.
+ \end{itemize}
+ What now remains of the page is the text area.\Index{text area} The width
+ and the height of the text area and margins result automatically from the
+ number of rows and columns \Var{DIV}. Since the margins always need three
+ stripes, \Var{DIV} must be necessarily greater than three. In order that the
+ text area occupy at least twice as much space as the margins, \Var{DIV}
+ should really be equal to or greater than 9. With this value, the
+ construction is also known as the \emph{classical division factor of 9} (see
+ \autoref{fig:typearea.nineparts}).
\begin{figure}
\centering
@@ -383,6 +370,8 @@ user, but rather at class- and package authors.
\LoadCommon{0}
+\LoadCommon{1}% TODO: Translate!
+
\section{Options and Macros to Influence the Page Layout}
\label{sec:typearea.typearea}
@@ -433,18 +422,18 @@ unit understood by \TeX{} is valid.
When using a {\KOMAScript} class, the explicit loading of the
\Package{typearea} package can be omitted:
- \begin{lstcode}
+\begin{lstcode}
\documentclass[BCOR=8.25mm]{scrreprt}
- \end{lstcode}
- The option \Option{a4paper} could be omittied with \Class{scrreprt},
+\end{lstcode}
+ The option \Option{a4paper} could be omitted with \Class{scrreprt},
since this is a predefined setting for all {\KOMAScript} classes.
If the option is only later set to a new value, one may then use,
for example, the following:
- \begin{lstcode}
+\begin{lstcode}
\documentclass{scrreprt}
\KOMAoptions{BCOR=8.25mm}
- \end{lstcode}
+\end{lstcode}
Thus, at the loading of the \Class{scrreprt} class standard settings
will be used. When changing the setting with the use of the command
\Macro{KOMAoptions} or \Macro{KOMAoption} a new page layout with new
@@ -479,12 +468,12 @@ the margins. Any integer value greater than 4 is valid for
unfulfillment of various minor conditions in the type-area, depending
on further options chosen. Thus, in an extreme case, the header may
fall outside of the page. Users applying the option
-\KOption{DIV}\PName{Factor} are themselves responsible for fulfillmen
+\KOption{DIV}\PName{Factor} are themselves responsible for fulfillment
of the marginal conditions and setting of a typographically aesthetic
line length.
In \autoref{tab:typearea.typearea} are found the type-area sizes for
-several \Var{DIV} factors for A4 page without binding correction. Here
+several \Var{DIV} factors for an A4 page without binding correction. Here
the minor conditions dependent on font size are not considered.
\begin{table}
@@ -529,11 +518,11 @@ the minor conditions dependent on font size are not considered.
that a value of 15 should be most suitable. The protocol will not
be bound but punched and kept in a folder. Thus, no binding
correction is necessary. One may then write:
- \begin{lstcode}
+\begin{lstcode}
\documentclass[a4paper,twoside]{protocol}
\usepackage{bookman}
\usepackage[DIV=15]{typearea}
- \end{lstcode}
+\end{lstcode}
On completion, it is decided that the protocols will from now on be
collected and bound quarterly into book format. The binding is to be
a simple glue binding, because it is only done to conform with
@@ -542,7 +531,7 @@ the minor conditions dependent on font size are not considered.
is required. Thus, one may change the options of the
\Package{typearea} package accordingly, and use the class for
protocols conforming to ISO\,9000 regulations:
- \begin{lstcode}
+\begin{lstcode}
\documentclass[a4paper,twoside]{iso9000p}
\usepackage{bookman}
\usepackage[DIV=15,BCOR=12mm]{typearea}
@@ -552,9 +541,9 @@ the minor conditions dependent on font size are not considered.
\documentclass[twoside,DIV=15,BCOR=12mm]{scrartcl}
\usepackage{bookman}
\end{lstcode}
-The \Option{a4paper} option can be left out when using the
-\Class{scrartcl} class, as it is predefined in all {\KOMAScript}
-classes.
+ The \Option{a4paper} option can be left out when using the
+ \Class{scrartcl} class, as it is predefined in all {\KOMAScript}
+ classes.
\end{Example}
Please note that when using the \Option{DIV} option with one of the
@@ -657,18 +646,18 @@ class is used together with a font package.
and margins anew after loading the font, with the aid of
\Macro{KOMAoptions}\PParameter{DIV=calc} or
\Macro{KOMAoption}\PParameter{DIV}\PParameter{calc}. Via
- \PValue{calc} an appropriate \Var{DIV} value for an good line length
+ \PValue{calc} an appropriate \Var{DIV} value for a good line length
is then chosen.
As it is often more practical to set the \Option{DIV} option not
after loading the font, but at a more visible point, such as when
loading the class, the \Package{typearea} package offers two further
- symbolic valies for this option.
+ symbolic values for this option.
\end{Explain}
With \KOption{DIV}\PName{current}\ChangedAt{v3.00}{\Package{typearea}}
a renewed calculation of text block and margin is requested, in which
-the currently-set \Var{DIV} will be used. This is less of interest for
+the currently set \Var{DIV} will be used. This is less of interest for
renewed type-area calculations after loading a different font; it is
rather more useful for determining, for example, after changing the
leading, while keeping \Var{DIV} the same, that the marginal condition
@@ -696,7 +685,7 @@ required, then only the setting of the optional argument to
\end{Example}
A summary of all possible symbolic values for the \Option{DIV} option
-can be founf in \autoref{tab:symbolicDIV}. At this point it is noted
+can be found in \autoref{tab:symbolicDIV}. At this point it is noted
that the use of the \Package{fontenc}\IndexPackage{fontenc} package
can also lead to \LaTeX{} loading a different font.
@@ -746,7 +735,7 @@ layout.
Since \Package{typearea} always executes the command
\Macro{normalsize} itself upon calculation of a new type-area, it is
not necessary to activate the chosen leading with \Macro{selectfont}
-after \Macro{linespread}, sicne this will be used already in the
+after \Macro{linespread}, since this will be used already in the
recalculation.
When using the \Package{setspace} package (see
@@ -855,27 +844,27 @@ abbreviated command
\begin{Example}
If one finds the notation
- \begin{lstcode}
+\begin{lstcode}
\KOMAoptions{DIV=last}
- \end{lstcode}
+\end{lstcode}
or
- \begin{lstcode}
+\begin{lstcode}
\typearea[current]{last}
- \end{lstcode}
+\end{lstcode}
for the recalculation of text block and margins too complicated for
reasons of the many special characters, then one may use more simply
the following.
- \begin{lstcode}
+\begin{lstcode}
\recalctypearea
- \end{lstcode}
+\end{lstcode}
\end{Example}%
\EndIndex{Cmd}{recalctypearea}%
\EndIndex{Cmd}{typearea}
-\BeginIndex{Option}{twoside~=\PName{switch}}%
+\BeginIndex{Option}{twoside~=\PName{simple switch}}%
\BeginIndex{Option}{twoside~=semi}%
\begin{Declaration}
- \KOption{twoside}\PName{switch}\\
+ \KOption{twoside}\PName{simple switch}\\
\OptionValue{twoside}{semi}
\end{Declaration}%
As already explained in \autoref{sec:typearea.basics}, the margin
@@ -885,7 +874,7 @@ right margins are equally wide, whereas for double-sided printing the
inner margin of one page is only half as wide as the corresponding
outer margin. In order to implement this distinction, the
\Package{typearea} package must be given the \Option{twoside} option,
-if the document is to be typeset double-sided. Being a \PName{switch},
+if the document is to be typeset double-sided. Being a \PName{simple switch},
any of the standard values for simple switches in
\autoref{tab:truefalseswitch} are valid. If the option is passed
without a value, the value \PValue{true} is assumed, so double-sided
@@ -922,19 +911,19 @@ margin notes.
The option can also be passed as class option in
\Macro{documentclass}, as package option to \Macro{usepackage}, or
even after loading of the \Package{typearea} package with the use of
-per \Macro{KOMAoptions} or \Macro{KOMAoption}. Use of the option after
-loading the \Package{typearea} package results automatically to a
+ \Macro{KOMAoptions} or \Macro{KOMAoption}. Use of the option after
+loading the \Package{typearea} package results automatically in
recalculation of the type-area using \Macro{recalctypearea} (see
\autopageref{desc:typearea.cmd.recalctypearea}). If double-sided
typesetting was active before the option was set, then before the
recalculation a page break is made to the next odd page.%
%
\EndIndex{Option}{twoside~=semi}%
-\EndIndex{Option}{twoside~=\PName{switch}}
+\EndIndex{Option}{twoside~=\PName{simple switch}}
-\BeginIndex{Option}{twocolumn~=\PName{switch}}%
+\BeginIndex{Option}{twocolumn~=\PName{simple switch}}%
\begin{Declaration}
- \KOption{twocolumn}\PName{switch}
+ \KOption{twocolumn}\PName{simple switch}
\end{Declaration}
For the calculation of a good type-area with the help of
\OptionValue{DIV}{calc} it is useful to know in advance if the
@@ -945,7 +934,7 @@ document can be up to double that in a one-column document.
To implement this difference, the \Package{typearea} package must be
told via the \Option{twocolumn} option whether the document is to be
-two-column. Since this is a \PName{switch}, any of the standard values
+two-column. Since this is a \PName{simple switch}, any of the standard values
for simple switches from \autoref{tab:truefalseswitch} is valid. If
the option is passed without a value, the value \PValue{true} is
assumed, i.\,e., two-column typesetting. Deactivation of the option
@@ -954,23 +943,23 @@ results in one-column typesetting.
The option can also be passed as class option in
\Macro{documentclass}, as package option to \Macro{usepackage}, or
even after loading of the \Package{typearea} package with the use of
-per \Macro{KOMAoptions} or \Macro{KOMAoption}. Use of the option after
-loading the \Package{typearea} package results automatically to a
+ \Macro{KOMAoptions} or \Macro{KOMAoption}. Use of the option after
+loading the \Package{typearea} package results automatically in
recalculation of the type-area using \Macro{recalctypearea} (see
\autopageref{desc:typearea.cmd.recalctypearea}).%
%
-\EndIndex{Option}{twocolumn~=\PName{switch}}
+\EndIndex{Option}{twocolumn~=\PName{simple switch}}
-\BeginIndex{Option}{headinclude~=\PName{switch}}%
-\BeginIndex{Option}{footinclude~=\PName{switch}}%
+\BeginIndex{Option}{headinclude~=\PName{simple switch}}%
+\BeginIndex{Option}{footinclude~=\PName{simple switch}}%
\begin{Declaration}
- \KOption{headinclude}\PName{switch}\\
- \KOption{footinclude}\PName{switch}
+ \KOption{headinclude}\PName{simple switch}\\
+ \KOption{footinclude}\PName{simple switch}
\end{Declaration}%
\begin{Explain}%
So far we have discussed how the type-area is
- calculated\Index{type-area} and what the relationship of the
+ calculated\Index{type-area} and the relationship of the
margins\Index{margins} to one another and between margins and text
block. However, one important question has not been answered: What
constitutes the margins?
@@ -981,19 +970,19 @@ recalculation of the type-area using \Macro{recalctypearea} (see
be margin notes, for example (see \Macro{marginpar} command in
\cite{lshort} or \autoref{sec:maincls.marginNotes}).
- One could also ask, whether headers\Index{page header} and
+ One could also ask whether headers\Index{page header} and
footers\Index{page footer} belong to the upper and lower margins or
to the text. This can not be answered unambiguously. Of course an
- empty footer or header belong to the margins, since they can not be
- distinguished from the rest of the margin. A header or footer, that
+ empty footer or header belongs to the margins, since they can not be
+ distinguished from the rest of the margin. A header or footer that
contains only a page
number\Index[indexmain]{pagination}\footnote{Pagination refers to
- the indication of the page number.}, will optically appear more
+ the indication of the page number.} will optically appear more
like a margin. For the optical appearance it is not important
whether headers or footers are easily recognized as such during
- reading. Important is only, how a well filled page appears when
+ reading. Of importance is only how a well-filled page appears when
viewed \emph{out of focus}. One could use the glasses of one's
- far-sighted grand parents, or, lacking those, adjust one's vision to
+ far-sighted grandparents, or, lacking those, adjust one's vision to
infinity and look at the page with one eye only. Those wearing
spectacles will find this much easier, of course. If the footer
contains not only the page number, but other material like a
@@ -1002,17 +991,17 @@ recalculation of the type-area using \Macro{recalctypearea} (see
text layout.
For the header this is even more complicated. The header frequently
- contains running headings \Index[indexmain]{running
- headings}\footnote{Running headings refer to the repetition of a
+ contains running headings\Index[indexmain]{running
+ headings}.\footnote{Running headings refer to the repetition of a
title in titling font, which is more often typeset in the page
- header, less often in the page footer.}. In case of running
- headings with long chapter and section titles the header lines will
+ header, less often in the page footer.} In the case of running
+ headings with long chapter and section titles, the header lines will
be very long and appear to be part of the text body. This effect
becomes even more significant when the header contains not only the
chapter or section title but also the page number. With material on
the right and left side, the header will no longer appear as an
empty margin. It is more difficult if the pagination is in the
- footer, and the length of the titles varies, so that the header may
+ footer, and the length of the titles varies so that the header may
appear as a margin on one page and as text on another. However,
these pages should not be treated differently under any
circumstances, as this would lead to vertically jumping headers. In
@@ -1023,19 +1012,19 @@ recalculation of the type-area using \Macro{recalctypearea} (see
from the text body by a line. This will give a ``closed'' appearance
and header or footer become part of the text body. Remember: It is
irrelevant that the line improves the optical separation of text and
- header or footer, important is only the appearance when viewed out
- of focus.
+ header or footer; only the appearance when viewed out
+ of focus is important.
\end{Explain}
-The \Package{typearea} package can not make the decision whether or
+The \Package{typearea} package cannot make the decision whether or
not to count headers and footers as part of the text body or the
margin. Options \Option{headinclude} and \Option{footinclude} cause
the header or footer to be counted as part of the text. These
-options, being a \PName{switch}\ChangedAt{v3.00}{\Package{typearea}},
+options, being a \PName{simple switch}\ChangedAt{v3.00}{\Package{typearea}},
understand the standard values for simple switches in
\autoref{tab:truefalseswitch}. One may use the options without
specifying a value, in which case the value \PValue{true} is used for
-the \PName{switch}, i.\,e., the header or footer is counted as part of
+the \PName{simple switch}, i.\,e., the header or footer is counted as part of
the text.
Readers who are unsure about the the correct setting should re-read
@@ -1058,61 +1047,61 @@ the values \PValue{last} or \PValue{current} (see
\Macro{recalctypearea} command (see
\autopageref{desc:typearea.cmd.recalctypearea}).%
%
-\EndIndex{Option}{headinclude~=\PName{switch}}%
-\EndIndex{Option}{footinclude~=\PName{switch}}%
+\EndIndex{Option}{headinclude~=\PName{simple switch}}%
+\EndIndex{Option}{footinclude~=\PName{simple switch}}%
-\BeginIndex{Option}{mpinclude~=\PName{switch}}%
+\BeginIndex{Option}{mpinclude~=\PName{simple switch}}%
\begin{Declaration}
- \KOption{mpinclude}\PName{switch}
+ \KOption{mpinclude}\PName{simple switch}
\end{Declaration}
Besides\ChangedAt{v2.8q}{\Class{scrbook}\and \Class{scrreprt}\and
- \Class{scrartcl}} documents where the head and foot is part of the
+ \Class{scrartcl}} documents where the head and foot are part of the
text area, there are also documents where the margin-note area must be
-counted to the text body as well. The option \Option{mpinclude} does
+counted as part of the text body as well. The option \Option{mpinclude} does
exactly this. The option, as a
-\PName{switch}\ChangedAt{v3.00}{\Package{typearea}}, understands the
+\PName{simple switch}\ChangedAt{v3.00}{\Package{typearea}}, understands the
standard values for simple switches in
\autoref{tab:truefalseswitch}. One may also pass this option without
specifying a value, in which case the value \PValue{true} for
-\PName{switch} is assumed.
+\PName{simple switch} is assumed.
The effect of \OptionValue{mpinclude}{true} is that one width-unit of
the text body is taken for the margin-note area. Using option
-\OptionValue{mpinclude}{false}, the default setting, then the normal
+\OptionValue{mpinclude}{false}, the default setting, the normal
margin is used for the margin-note area. The width of that area is
one or one and a half width-unit, depending on whether one-sided or
double-sided page layout has been chosen. The option
-\Option{mpinclude}{true} is mainly for experts and so not recommended.
+\OptionValue{mpinclude}{true} is mainly for experts and so is not recommended.
\begin{Explain}
- In the cases where the option \Option{mpinclude} is used often a
+ In the cases where the option \Option{mpinclude} is used, often a
wider margin-note area is required. In many cases not the whole
margin-note width should be part of the text area, for example if
the margin is used for quotations. Such quotations are typeset as
ragged text with the flushed side where the text body is. Since
- ragged text gives no homogeneous optical impression the long lines
+ ragged text gives no homogeneous optical impression, the long lines
can reach right into the normal margin. This can be done using
option \Option{mpinclude} and by an enlargement of length
- \Length{marginparwidth} after the type-area has been setup. The
+ \Length{marginparwidth} after the type-area has been set up. The
length can be easily enlarged with the command \Macro{addtolength}.
- How much the the length has to be enlarged depends on the special
+ How much the length has to be enlarged depends on the special
situation and it requires some flair. This is another reason the
\Option{mpinclude} option is primarily left for experts. Of course
- one can setup the margin-width to reach a third right into the
- normal margin, for example using
- \begin{lstcode}[belowskip=\dp\strutbox]
+ one can set up the margin-width to reach a third right into the
+ normal margin; for example, using
+\begin{lstcode}[belowskip=\dp\strutbox]
\setlength{\marginparwidth}{1.5\marginparwidth}
- \end{lstcode}
+\end{lstcode}
gives the desired result.
Currently there is no option to enlarge the margin by a given
amount. The only solution is to either not use the option
\Option{mpinclude} or to set \Option{mpinclude} to \PValue{false},
- and instead after the type-area has been calculated one reduces the
+ and after the type-area has been calculated, one reduces the
width of the text body \Length{textwidth} and enlarges the margin
width \Length{marginparwidth} by the same amount. Unfortunately,
- this can not be combined with automatic calculation of the
+ this cannot be combined with automatic calculation of the
\PName{DIV} value. In contrast
\Option{DIV=calc}\IndexOption{DIV~=calc} (see
\autopageref{desc:typearea.option.DIV.calc}) heeds
@@ -1132,7 +1121,7 @@ type-area, refer to the \Option{DIV} option with the values
\Macro{recalctypearea} command (see
\autopageref{desc:typearea.cmd.recalctypearea}).%
%
-\EndIndex{Option}{mpinclude~=\PName{switch}}%
+\EndIndex{Option}{mpinclude~=\PName{simple switch}}%
\BeginIndex{Option}{headlines~=\PName{number}}%
@@ -1158,14 +1147,14 @@ its default value and adapt it only in special cases.
\begin{Example}
Assume that you want to use a header with two lines. Normally this would
- result in a ``\texttt{overfull} \Macro{vbox}'' warning for each page. To
+ result in an ``\texttt{overfull} \Macro{vbox}'' warning for each page. To
prevent this from happening, the \Package{typearea} package is told to
calculate an appropriate type-area:
\begin{lstcode}
\documentclass[a4paper]{article}
\usepackage[headlines=2.1]{typearea}
\end{lstcode}
-If you use a {\KOMAScript} class it is recommended to pass this option
+If you use a {\KOMAScript} class, it is recommended to pass this option
directly as a class option:
\begin{lstcode}
\documentclass[a4paper,headlines=2.1]{scrartcl}
@@ -1174,7 +1163,7 @@ Commands that can be used to define the contents of a header with two
lines are described in \autoref{cha:scrpage}.
\end{Example}
-In some cases it is useful to be able to specift the header height not
+In some cases it is useful to be able to specify the header height not
in lines but directly as a length measurement. This is accomplished
with the aid of the alternative option \Option{headheight}. For
\PName{height} any lengths and sizes that \LaTeX{} understands are
@@ -1217,7 +1206,7 @@ the width and height of the text body. Width and position of the
margins will then be calculated automatically, taking account of the
options \Option{headinclude}, \OptionValue{headinclude}{false},
\Option{footinclude} and \OptionValue{footinclude}{false} where
-needed. On the ther hand, the options
+needed. On the other hand, the options
\Option{headlines}\IndexOption{headlines} and
\Option{headheight}\IndexOption{headheight} are ignored!
@@ -1299,14 +1288,31 @@ exotic paper sizes.
\end{Declaration}%
The option \Option{paper}\ChangedAt{v3.00}{\Package{typearea}} is the
central element for format selection in \KOMAScript. \PName{Format}
-supports first of all the american formats \Option{letter},
-\Option{legal} and \Option{executive}. In addition, it supports the
-ISO formats of the series A, B, C and D, for example \PValue{A4}
-or\,---\,written in lowercase\,---\,\PValue{a4}. Landscape formats are
-supported by specifying the option again, this time with the value
-\PValue{landscape}\Index{paper>orientation}. Additionally, the
-\PName{format} can also be specified in the form
-\PName{height}\texttt{:}\PName{width}.
+supports first of all the American formats \Option{letter},
+\Option{legal}, and \Option{executive}. In addition, it supports the
+ISO formats of the series A, B, C, and D, for example \PValue{A4}
+or\,---\,written in lowercase\,---\,\PValue{a4}.
+
+Landscape formats are supported by specifying the option again, this time with
+value \PValue{landscape}\Index{paper>orientation} or
+\PValue{seascape}\ChangedAt{v3.02c}{\Package{typearea}}. The difference is
+that application \File{dvips} rotates at \PValue{landscape} by
+-90\Unit{\textdegree}, while it rotates by +90\Unit{\textdegree} at
+\PValue{seascape}. So you may use \PValue{seascape} whenever a PostScript
+viewer application shows landscape pages upside-down. But you may see the
+difference only if you also use option \Option{pagesize}, which will be
+described next.
+
+Additionally, the \PName{format} can also be specified in the form
+\PName{height}\texttt{:}\PName{width}. Note that until
+version~3.01a\ChangedAt{v3.01b}{\Package{typearea}} \PName{height} and
+\PName{width} has been interchanged.
+% You should at least pay attention to this,
+This is important
+if you use compatibility settings (see option
+\Option{version}\IndexOption{version}\important{\Option{version}},
+\autoref{sec:typearea.compatibilityOptions},
+\autopageref{desc:typearea.option.version}).
\begin{Example}
Assume one wishes to print on ISO A8 file cards in landscape
@@ -1345,7 +1351,7 @@ As part of the predefined defaults, {\KOMAScript} uses A4 paper in
portrait orientation. This is in contrast to the standard classes,
which by default use the American letter paper format.
-Please note that when using this options with one of the {\KOMAScript}
+Please note that when using these options with one of the {\KOMAScript}
classes, it must be used either as a class option, or passed via
\Macro{KOMAoptions} or \Macro{KOMAoption} after loading the
class. Changing of this option after loading the \Package{typearea}
@@ -1368,9 +1374,10 @@ the \Macro{recalctypearea} command (see
\begin{Explain}%
The above-mentioned mechanisms for choice of paper format only
affect the output insofar as internal {\LaTeX} lengths are set. The
- \Package{typearea} package then uses there in the division of the
- page into type-area and margins. The specification of the DVI
- formats\Index{DVI} however does not include any indications of paper
+ \Package{typearea} package then uses them in the division of the
+ page into type-area and margins.
+ The specification of the DVI
+ formats\Index{DVI}, however, does not include any indications of paper
format. If printing is done directly from DVI format to a low-level
printer language such as PCL%
\iffalse% Umbruchkorrektur
@@ -1381,7 +1388,7 @@ the \Macro{recalctypearea} command (see
\footnote{ESC/P2 is the printer language used by EPSON for its
dot-matrix, inkjet and laser printers.}%
\fi , this is usually not an issue since with this output also the
- zero-position is at the top left, identical to DVI. If however
+ zero-position is at the top left, identical to DVI. If, however,
translation is made into a language such as
PostScript\Index{PostScript} or PDF\Index{PDF}, in which the
zero-position is at a different point, and in which also the paper
@@ -1393,24 +1400,51 @@ the \Macro{recalctypearea} command (see
given in the form of a \Macro{special} command. With {pdf\TeX} or
{V\TeX} one sets instead two lengths.
\end{Explain}
-The option \OptionValue{pagesize}{dvips}\IndexOption{pagesize~=dvips}
-writes the paper size as a \Macro{special} into die DVI data
-file. This \Macro{special} is then evaluated by, for example,
-\File{dvips}. On the other hand, the option
-\OptionValue{pagesize}{pdftex} writes the paper size at the start of
-the document into the {pdf\TeX} page registers
-\Length{pdfpagewidth}\IndexLength{pdfpagewidth} and
-\Length{pdfpageheight}\IndexLength{pdfpageheight}, so that later when
-viewing the PDF file the correct format is chosen. The option
-\OptionValue{pagesize}{auto} is more flexible and, depending on
-whether a PDF or DVI data file is output, uses the mechanism of the
-option \OptionValue{pagesize}{dvips} or
-\OptionValue{pagesize}{pdftex}. With the option
-\OptionValue{pagesize}{automedia} it may be that \Length{mediawidth}
-and \Length{mediaheight} are also set appropriately. In this way even
-the demands of {V\TeX} are supported. If the option \Option{pagesize}
-is used with specifying an \PName{output driver} then \PValue{auto} is
-used.
+With option \Option{pagesize} you may select an output driver for writing the
+paper size into the destination document. Supported output drivers are listed
+at \autoref{tab:typearea.outputdriver}. The default is
+\OptionValue{pagesize}{false}. Usage of option
+\Option{pagesize}\IndexOption{pagesize} without value is same like
+\OptionValue{pagesize}{auto}.
+%
+\begin{table}
+ \caption{Output driver for option \KOption{pagesize}\PName{output driver}}
+ \begin{desctabular}
+ \pventry{auto}{Uses output driver \PValue{pdftex} if pdf\TeX-specific
+ registers \Macro{pdfpagewidth}\IndexLength{pdfpagewidth} and
+ \Macro{pdfpageheight}\IndexLength{pdfpageheight} are defined. In
+ addition, output driver \PValue{dvips} will be
+ used.\IndexOption{pagesize~=\PValue{auto}}}%
+ \pventry{automedia}{Almost the same as \PValue{auto} but if the
+ \mbox{V\TeX}-specific registers
+ \Macro{mediawidth}\IndexLength{mediawidth} and
+ \Macro{mediaheight}\IndexLength{mediaheight} are defined, they will be
+ set additionally.\IndexOption{pagesize~=\PValue{automedia}}}%
+ \entry{\PValue{false}, \PValue{no}, \PValue{off}}{%
+ Doesn't set any output driver and doesn't send page size information to
+ the output driver.\IndexOption{pagesize~=\PValue{false}}}%
+ \pventry{dvipdfmx}{\ChangedAt{v3.05a}{\Package{typearea}}Writes paper size
+ into DVI files using
+ \Macro{special}\PParameter{pagesize=\PName{width},\PName{height}}. The
+ name of the output driver is \PValue{dvipdfmx} because application
+ \File{dvipdfmx} handles such specials not only at document preamble but
+ at the document body too.\IndexOption{pagesize~=\PValue{dvipdfmx}}}%
+ \pventry{dvips}{Using this option at the document preamble sets paper size
+ using
+ \Macro{special}\PParameter{pagesize=\PName{width},\PName{height}}. While
+ application \File{dvips} cannot handle changes of paper size at the
+ inner document pages a hack is needed to achieve such changes. Use
+ changes of paper size after \Macro{begin}\PParameter{document} on your
+ own risk, if you are using
+ \PValue{dvips}!\IndexOption{pagesize~=\PValue{dvips}}}%
+ \pventry{pdftex}{Sets paper size using the pdf\TeX-specific registers
+ \Macro{pdfpagewidth}\IndexLength{pdfpagewidth} and
+ \Macro{pdfpageheight}\IndexLength{pdfpageheight}. You may do this at any
+ time in your document.\IndexOption{pagesize~=\PValue{pdftex}}}%
+ \end{desctabular}
+ \label{tab:typearea.outputdriver}
+\end{table}
+
\begin{Example}
Assume that a document should be available both as a DVI data file
and in PDF format for online viewing. Then the preamble might begin
@@ -1421,14 +1455,14 @@ used.
\end{lstcode}
If the {pdf\TeX} engine is used \emph{and} PDF output is
activated, then the two lengths \Macro{pdfpagewidth} and
-\Macro{pdfpageheight} are set appropriately. If however a DVI data
+\Macro{pdfpageheight} are set appropriately. If, however, a DVI data
file is created\,---\,regardless of whether by {\LaTeX} or by
{pdf\LaTeX}\,---\,then a \Macro{special} is written at the start of
this data file.
\end{Example}%
It is recommended always to specify this option. Generally the method
without \PName{output driver}, or with \PValue{auto} or
-\PValue{automedia} is useful.%
+\PValue{automedia}, is useful.%
\EndIndex{Option}{pagesize}%
\EndIndex{Option}{pagesize~=\PName{output driver}}%
%
@@ -1438,12 +1472,12 @@ without \PName{output driver}, or with \PValue{auto} or
\section{Tips}
\label{sec:typearea.tips}
-In particular for theses many rules exist that violate even the most
+For theses many rules exist that violate even the most
elementary rules of typography. The reasons for such rules include
typographical incompetence of those making them, but also the fact
that they were originally meant for mechanical typewriters. With a
typewriter or a primitive text processor dating back to the early
-´80s it was not possible to produce typographically correct output
+1980s, it was not possible to produce typographically correct output
without extreme effort. Thus rules were created that appeared to be
achievable and still allowed easy correction. To avoid short lines
made worse by ragged margins, the margins were kept narrow and the
@@ -1467,13 +1501,13 @@ margin sizes prescribed.
wide enough for corrections. Thus a page will look generous, even when
quite full of text.
-To some extend the questionable rules are difficult to implement in
+To some extent, the questionable rules are difficult to implement in
{\LaTeX}. A fixed number of characters per line can be kept only when
a non-proportional font is used. There are very few good
non-proportional fonts available. Hardly a text typeset in this way
looks really good. In many cases font designers try to increase the
serifs on the `i' or `l' to compensate for the different character
-width. This can not work and results in a fragmented and
+width. This cannot work and results in a fragmented and
agitated-looking text. If one uses {\LaTeX} for one's paper, some of
these rules have to be either ignored or at least interpreted
generously. For example one may interpret ``60 characters per line''
@@ -1481,7 +1515,7 @@ not as a fixed, but as an average or maximal value.%
As executed, record regulations are usually intended to obtain a
usable result even if the author does not know what needs to be
-considered. Usable means frequently: readable and correctable. In
+considered. \emph{Usable} frequently means readable and correctable. In
the author's opinion the type-area of a text set with {\LaTeX} and the
\Package{typearea} package meets these criteria well right from the
start. Thus if one is confronted with regulations which deviate
@@ -1515,7 +1549,7 @@ contents and various listings\,---\,as well as the bibliography and
the index. The \Package{setspace} package offers for this a special
environment and its own instructions.
-The \Package{typearea} package even with option \Option{DIV=calc}
+The \Package{typearea} package, even with option \OptionValue{DIV}{calc},
calculates a very generous text area. Many conservative typographers
will state that the resulting line length is still excessive. The
calculated \Var{DIV} value may be found in the \File{log} file for the
@@ -1548,6 +1582,6 @@ German words in the German scrguide.
%%% Local Variables:
%%% mode: latex
-%%% coding: iso-latin-1
+%%% coding: us-ascii
%%% TeX-master: "../guide"
%%% End: