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.tex221
1 files changed, 153 insertions, 68 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 db2bce403f2..a752145682b 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
@@ -1,6 +1,6 @@
% ======================================================================
% typearea.tex
-% Copyright (c) Markus Kohm, 2001-2012
+% Copyright (c) Markus Kohm, 2001-2013
%
% This file is part of the LaTeX2e KOMA-Script bundle.
%
@@ -18,7 +18,7 @@
% This work consists of all files listed in manifest.txt.
% ----------------------------------------------------------------------
% typearea.tex
-% Copyright (c) Markus Kohm, 2001-2012
+% Copyright (c) Markus Kohm, 2001-2013
%
% Dieses Werk darf nach den Bedingungen der LaTeX Project Public Lizenz,
% Version 1.3c, verteilt und/oder veraendert werden.
@@ -45,10 +45,12 @@
%
% ======================================================================
-\ProvidesFile{typearea.tex}[2012/07/22 KOMA-Script guide (chapter: typearea)]
+\KOMAProvidesFile{typearea.tex}%
+ [$Date: 2013-12-13 12:11:01 +0100 (Fr, 13. Dez 2013) $
+ KOMA-Script guide (chapter: typearea)]
\translator{Markus Kohm\and Gernot Hassenpflug\and Krickette Murabayashi}
-% Date of translated german file: 2012/07/22
+% Date of translated german file: 2013/11/21
\chapter{Construction of the Page Layout with \Package{typearea}}
\labelbase{typearea}
@@ -355,7 +357,7 @@ user, but rather at authors of classes and packages.
\cite{JTsch87}.
A disadvantage of this late Middle Age method is that the width of
- the text area is no longer dependent on the font. Thus, one doesn't
+ the text area is no longer dependent on the font. Thus, one does not
choose the text area to match the font, but the author or typesetter
has to choose the font according to the text area. This can be
considered a ``must''.
@@ -465,24 +467,24 @@ construction method is found in
larger the \PName{Factor}, the larger the text block and the smaller
the margins. Any integer value greater than 4 is valid for
\PName{Factor}. Please note that large values can lead to
-unfulfillment of various minor conditions in the type-area, depending
+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 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
+In \autoref{tab:typearea.typearea} are found the type area sizes for
several \Var{DIV} factors for an A4 page without binding correction. Here
the minor conditions dependent on font size are not considered.
\begin{table}
\centering
- \caption{Type-area dimensions dependent on \Var{DIV} for A4}
+ \caption{Type area dimensions dependent on \Var{DIV} for A4}
\begin{tabular}{ccccc}
\toprule
&
- \multicolumn{2}{c}{Type-area} & \multicolumn{2}{c}{Margins}\\
+ \multicolumn{2}{c}{Type area} & \multicolumn{2}{c}{Margins}\\
%\raisebox{1.5ex}[0pt]{
\Var{DIV}
%}
@@ -658,7 +660,7 @@ class is used together with a font package.
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
-renewed type-area calculations after loading a different font; it is
+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
is fulfilled that \Length{textheight} less
@@ -670,7 +672,7 @@ exactly the same setting is used as in the last calculation.
\begin{Example}
Let us take up the previous example again, in which a good line
- length is required for a type-area using the Bookman font. At the
+ length is required for a type area using the Bookman font. At the
same time, a {\KOMAScript} class is to be used. This is easily
possible using the symbolic value \PValue{last} and the command
\Macro{KOMAoptions}:
@@ -697,25 +699,25 @@ can also lead to \LaTeX{} loading a different font.
\begin{desctabular}
\pventry{areaset}{Recalculate page
layout.\IndexOption{DIV~=areaset}}%
- \pventry{calc}{Recalculate type-area including choice of
+ \pventry{calc}{Recalculate type area including choice of
appropriate \Var{DIV} value.\IndexOption{DIV~=calc}}%
- \pventry{classic}{Recalculate type-area using Middle Age book
+ \pventry{classic}{Recalculate type area using Middle Age book
design canon (circle-based
calculation).\IndexOption{DIV~=classic}}%
- \pventry{current}{Recalculate type-area using current \Var{DIV}
+ \pventry{current}{Recalculate type area using current \Var{DIV}
value.\IndexOption{DIV~=current}}%
- \pventry{default}{Recalculate type-area using the standard value
+ \pventry{default}{Recalculate type area using the standard value
for the current page format and current font size. If no
standard value exists, \PValue{calc} is
used.\IndexOption{DIV~=default}}%
- \pventry{last}{Recalculate type-area using the same \PName{DIV}
+ \pventry{last}{Recalculate type area using the same \PName{DIV}
argument as was used in the last call.\IndexOption{DIV~=last}}%
\end{desctabular}
\end{table}
-Often the renewed type-area calculation is required in combination
+Often the renewed type area calculation is required in combination
with a change in the line spacing
-(\emph{leading})\Index{leading}. Since the type-area should be
+(\emph{leading})\Index{leading}. Since the type area should be
calculated such that an integer number of lines fit in the text block,
a change in the leading normally requires a recalculation of the page
layout.
@@ -733,7 +735,7 @@ layout.
\KOMAoptions{DIV=last}
\end{lstcode}\IndexCmd{linespread}
Since \Package{typearea} always executes the command
-\Macro{normalsize} itself upon calculation of a new type-area, it is
+\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}, since this will be used already in the
recalculation.
@@ -755,21 +757,26 @@ page should be reset to the normal value.
A complete example would be:
\fi
\begin{lstcode}
- \documentclass[10pt,twoside,BCOR=12mm,DIV=calc]{scrreprt}
+ \documentclass[10pt,twoside,BCOR=12mm,DIV=calc]
+ {scrreprt}
\usepackage{setspace}
\onehalfspacing
+ \AfterTOCHead{\singlespacing}
\KOMAoptions{DIV=last}
\begin{document}
\title{Title}
\author{Markus Kohm}
\begin{spacing}{1}
\maketitle
- \tableofcontents
\end{spacing}
+ \tableofcontents
\chapter{Ok}
\end{document}
\end{lstcode}
- See further also the notes in \autoref{sec:typearea.tips}.
+ See further also the notes in \autoref{sec:typearea.tips}. The command
+ \Macro{AfterTOCHead}\IndexCmd{AfterTOCHead} will be described in
+ \autoref{cha:tocbasic} of \autoref{part:forExoerts} on
+ \autopageref{desc:tocbasic.cmd.AfterTOCHead}.
\end{Example}
Please note that when using this option with one of the {\KOMAScript}
@@ -813,7 +820,7 @@ margins are automatically recalculated anew.%
\Macro{typearea}\OParameter{BCOR}\Parameter{DIV}}
\label{tab:symbolicBCOR}
\begin{desctabular}
- \pventry{current}{Recalculate type-area with the currently valid
+ \pventry{current}{Recalculate type area with the currently valid
\Var{BCOR} value.\IndexOption{BCOR~=current}}
\end{desctabular}
\end{table}
@@ -828,7 +835,7 @@ change to \PName{BCOR}.
\begin{Explain}
The command \Macro{typearea} is currently defined so as to make it
- possible to change the type-area anywhere within a
+ possible to change the type area anywhere within a
document. Several assumptions about the structure of the {\LaTeX}
kernel are however made and internal definitions and sizes of the
kernel changed. There is a definite possibility, but no guarantee,
@@ -838,7 +845,7 @@ change to \PName{BCOR}.
Since \Macro{typearea}\POParameter{current}\PParameter{last} or
\Macro{KOMAoptions}\PParameter{DIV=last} are often needed for
-recalculation of the type-area, there exists specially the
+recalculation of the type area, there exists specially the
abbreviated command
\Macro{recalctypearea}\ChangedAt{v3.00}{\Package{typearea}}.
@@ -882,38 +889,42 @@ typesetting is carried out. Deactivation of the option leads to
single-sided typesetting.
\begin{table}
- \begin{minipage}{\textwidth}
\centering
\caption{Standard values for simple switches in \KOMAScript}
\begin{tabular}{ll}
\toprule
Value & Description \\
\midrule
- \PValue{true}\footnote{This value will be used also, if you use the option
- without assigning any value.} & activates the option \\
+ \PValue{true} & activates the option \\
\PValue{on} & activates the option \\
- \PValue{yes} & activates the option \\
+ \PValue{yes} & activates the option \\
\PValue{false}& deactivates the option \\
\PValue{off} & deactivates the option \\
- \PValue{no} & deactivates the option \\
+ \PValue{no} & deactivates the option \\
\bottomrule
\end{tabular}
\label{tab:truefalseswitch}
- \end{minipage}
\end{table}
Apart from the values in \autoref{tab:truefalseswitch} the value
-\PValue{semi}\ChangedAt{v3.00}{\Package{typearea}} can also be
-given. The value \PValue{semi} results in a double-sided typesetting
-with single-sided margins and single-sided, i.\ e., not alternating,
-margin notes.
+\PValue{semi}\ChangedAt{v3.00}{\Package{typearea}} can also be given. The
+value \PValue{semi} results in a double-sided typesetting with single-sided
+margins and single-sided, i.\ e., not alternating, margin
+notes. Nevertheless\ChangedAt{v3.12}{\Package{typearea}}, since \KOMAScript{}
+version 3.12 binding corrections (see \Option{BCOR},
+\autopageref{desc:typearea.option.BCOR}) will be part of the left margin on
+odd pages but part of the right margin on even pages. But if you use
+compatibility with prior versions of \KOMAScript (see
+\autoref{sec:typearea.compatibilityOptions},
+\autopageref{sec:typearea.compatibilityOptions}), binding correction will be
+part of the left margin on both pages while using \OptionValue{twoside}{semi}.
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
\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
+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.%
@@ -925,11 +936,11 @@ recalculation a page break is made to the next odd page.%
\begin{Declaration}
\KOption{twocolumn}\PName{simple switch}
\end{Declaration}
-For the calculation of a good type-area with the help of
+For the calculation of a good type area with the help of
\OptionValue{DIV}{calc} it is useful to know in advance if the
document is to be typeset one-column or two-column. Since the
observations about line length in \autoref{sec:typearea.basics} then
-apply to each column, the width of a type-area in a two-column
+apply to each column, the width of a type area in a two-column
document can be up to double that in a one-column document.
To implement this difference, the \Package{typearea} package must be
@@ -945,7 +956,7 @@ The option can also be passed as class option in
even after loading of the \Package{typearea} package with the use of
\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
+recalculation of the type area using \Macro{recalctypearea} (see
\autopageref{desc:typearea.cmd.recalctypearea}).%
%
\EndIndex{Option}{twocolumn~=\PName{simple switch}}
@@ -958,8 +969,8 @@ recalculation of the type-area using \Macro{recalctypearea} (see
\KOption{footinclude}\PName{simple switch}
\end{Declaration}%
\begin{Explain}%
- So far we have discussed how the type-area is
- calculated\Index{type-area} and the relationship of the
+ So far we have discussed how the type area is
+ 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?
@@ -1039,9 +1050,9 @@ Please note that when using these options with one of the
either as a class option, or passed via \Macro{KOMAoptions} or
\Macro{KOMAoption} after loading the class. Changing of these options
after loading the \Package{typearea} package does not result in an
-automatic recalculation of the type-area. Instead, the changes only
-take effect at the next recalculation of the type-area. For
-recalculation of the type-area, refer to the \Option{DIV} option with
+automatic recalculation of the type area. Instead, the changes only
+take effect at the next recalculation of the type area. For
+recalculation of the type area, refer to the \Option{DIV} option with
the values \PValue{last} or \PValue{current} (see
\autopageref{desc:typearea.option.DIV.last}) or the
\Macro{recalctypearea} command (see
@@ -1083,7 +1094,7 @@ double-sided page layout has been chosen. The option
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 set up. 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 length has to be enlarged depends on the special
situation and it requires some flair. This is another reason the
@@ -1098,7 +1109,7 @@ double-sided page layout has been chosen. The option
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 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 cannot be combined with automatic calculation of the
@@ -1113,9 +1124,9 @@ classes as in the example above, 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} package does not result in an automatic
-recalculation of the type-area. Instead, the changes only take effect
-at the next recalculation of the type-area. For recalculation of the
-type-area, refer to the \Option{DIV} option with the values
+recalculation of the type area. Instead, the changes only take effect
+at the next recalculation of the type area. For recalculation of the
+type area, refer to the \Option{DIV} option with the values
\PValue{last} or \PValue{current} (see
\autopageref{desc:typearea.option.DIV.last}) or the
\Macro{recalctypearea} command (see
@@ -1130,7 +1141,7 @@ type-area, refer to the \Option{DIV} option with the values
\KOption{headlines}\PName{number of lines}\\
\KOption{headheight}\PName{height}
\end{Declaration}%
-We have seen how to calculate the type-area using the
+We have seen how to calculate the type area using the
\Package{typearea} package and how to specify whether header and
footer are part of the text or the margins. However, in particular for
the header, we still have to specify the height. This is achieved with
@@ -1149,7 +1160,7 @@ its default value and adapt it only in special cases.
Assume that you want to use a header with two lines. Normally this would
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:
+ calculate an appropriate type area:
\begin{lstcode}
\documentclass[a4paper]{article}
\usepackage[headlines=2.1]{typearea}
@@ -1159,8 +1170,8 @@ directly as a class option:
\begin{lstcode}
\documentclass[a4paper,headlines=2.1]{scrartcl}
\end{lstcode}
-Commands that can be used to define the contents of a header with two
-lines are described in \autoref{cha:scrpage}.
+Commands that can be used to define the contents of a header with two lines
+are described in \autoref{cha:scrpage} and \autoref{cha:scrlayer-scrpage}.
\end{Example}
In some cases it is useful to be able to specify the header height not
@@ -1169,7 +1180,7 @@ with the aid of the alternative option \Option{headheight}. For
\PName{height} any lengths and sizes that \LaTeX{} understands are
valid. It should be noted though that when using a \LaTeX{} length
such as \Length{baselineskip} its value at the time of the calculation
-of the type-area and margins, not at the time of setting of the
+of the type area and margins, not at the time of setting of the
option, is decisive.
Please note that when using these options with one of the
@@ -1177,9 +1188,9 @@ Please note that when using these options with one of the
either as a class option, or passed via \Macro{KOMAoptions} or
\Macro{KOMAoption} after loading the class. Changing of these options
after loading the \Package{typearea} package does not result in an
-automatic recalculation of the type-area. Instead, the changes only
-take effect at the next recalculation of the type-area. For
-recalculation of the type-area, refer to the \Option{DIV} option with
+automatic recalculation of the type area. Instead, the changes only
+take effect at the next recalculation of the type area. For
+recalculation of the type area, refer to the \Option{DIV} option with
the values \PValue{last} or \PValue{current} (see
\autopageref{desc:typearea.option.DIV.last}) or the
\Macro{recalctypearea} command (see
@@ -1188,13 +1199,87 @@ the values \PValue{last} or \PValue{current} (see
\EndIndex{Option}{headheight~=\PName{height}}%
\EndIndex{Option}{headlines~=\PName{number}}
+\begin{Declaration}
+ \KOption{footlines}\PName{number}\\
+ \KOption{footheight}\PName{height}
+\end{Declaration}
+\BeginIndex{Option}{footlines~=\PName{number}}%
+\BeginIndex{Option}{footheight~=\PName{height}}%
+As\ChangedAt{v3.12}{\Package{typearea}} well as we needed a height value for
+the head, we need a height value for the page footer. But in difference to the
+height of the head, \LaTeX itself do not provide a length for the height of
+the page footer. So \Package{typearea} defines the new length
+\Length{footheight}\IndexLength[indexmain]{footheight}, if it does not
+exist. Wether or not this length will be used by classes or packages depends
+on the classes and packages, that will be used. The \KOMAScript{} package
+\Package{scrlayer-scrpage} incorporates \Length{footheight} and actively
+cooperates with \Package{typearea}. The \KOMAScript{} classes do not recognize
+\Length{footheight}, because without any package assistance they provide only
+page styles with single-line page footers.
+
+You can use \Option{footlines} to setup the \PName{number} of lines in the
+page footer, similar to \Option{headlines} for the number of lines in the page
+header. By default \Package{typearea} uses 1.25 footlines. This is a
+compromise, large enough for overlining or underlining footers and small
+enough that the relative weight of the bottom margin is not affected too mich
+when the footer is neither over- nor underlined. Thus in most cases you may
+leave \PName{footlines} at its default value and adapt it only in special
+cases.
+
+\begin{Example}
+ Assume a two-lined copyright note should be placed in the page
+ footer. Indeed, \LaTeX{} itself does not test, whether or not the footer has
+ room enough for that, exceeding of the available height would probably could
+ result in unbalanced margins. Moreover, for example package
+ \Package{scrlayer-scrpage}, that may be used to define such a page footer,
+ would definitely do such a test and would notify a recognised oversize. So
+ it makes sense, to declare the needed footheight already for the calculation
+ of the text area and the margins:
+\begin{lstcode}
+ \documentclass[a4paper]{article}
+ \usepackage[footlines=2.1]{typearea}
+\end{lstcode}
+ Again, if you use a \KOMAScript{} class, it is recommended to pass this
+ option directly a a class option:
+\begin{lstcode}
+ \documentclass[footlines=2.1]{scrartcl}
+\end{lstcode}
+ Commands that can be used to define the contents of a footer with two lines
+ are described in \autoref{cha:scrlayer-scrpage}.
+\end{Example}
+
+In some cases it is useful to be able to specify the footer height not
+in lines but directly as a length measurement. This is accomplished
+with the aid of the alternative option \Option{footheight}. For
+\PName{height} any lengths and sizes that \LaTeX{} understands are
+valid. It should be noted though that when using a \LaTeX{} length
+such as \Length{baselineskip} its value at the time of the calculation
+of the type area and margins, not at the time of setting of the
+option, is decisive.
+
+Please note that when using these options with one of the
+{\KOMAScript} classes as in the example above, they must be used
+either as a class option, or passed via \Macro{KOMAoptions} or
+\Macro{KOMAoption} after loading the class. Changing of these options
+after loading the \Package{typearea} package does not result in an
+automatic recalculation of the type area. Instead, the changes only
+take effect at the next recalculation of the type area. For
+recalculation of the type area, refer to the \Option{DIV} option with
+the values \PValue{last} or \PValue{current} (see
+\autopageref{desc:typearea.option.DIV.last}) or the
+\Macro{recalctypearea} command (see
+\autopageref{desc:typearea.cmd.recalctypearea}).%
+\EndIndex{Option}{footheight~=\PName{height}}%
+\EndIndex{Option}{footlines~=\PName{number}}%
+
+
\BeginIndex{Cmd}{areaset}%
\begin{Declaration}
\Macro{areaset}\OParameter{BCOR}\Parameter{Width}\Parameter{Height}
\end{Declaration}%
So far we have seen how a good or even very good
-type-area\Index{type-area} is calculated and how the
+type area\Index{type area} is calculated and how the
\Package{typearea} package can support these calculations, giving you
at the same time the freedom to adapt the layout to your needs.
However, there are cases where the text body has to fit exactly some
@@ -1230,7 +1315,7 @@ text line is \Macro{topskip} below the top margin of the type area, as
long as the height of the topmost line is less than
\Macro{topskip}. Thus, the uppermost line does not require any
height. The descenders of characters on the lowermost line, on the
-other hand, hang below the dimensions of the type-area.
+other hand, hang below the dimensions of the type area.
\item A poetry book with a square text body with a page length of
15\Unit{cm} and a binding correction of 1\Unit{cm} could be
@@ -1248,7 +1333,7 @@ other hand, hang below the dimensions of the type-area.
\OptionValue{DIV}{areaset}
\end{Declaration}%
In\ChangedAt{v3.00}{\Package{typearea}} rare cases it is useful to be
-able to reconstruct the current type-area anew. This is possible via
+able to reconstruct the current type area anew. This is possible via
the option \OptionValue{DIV}{areaset}, where
\Macro{KOMAoptions}\PParameter{DIV=areaset} corresponds to the
\begin{lstcode}[belowskip=\dp\strutbox]
@@ -1356,8 +1441,8 @@ 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}
package does not result in an automatic recalculation of the
-type-area. Instead, the changes only take effect at the next
-recalculation of the type-area. For recalculation of the type-area,
+type area. Instead, the changes only take effect at the next
+recalculation of the type area. For recalculation of the type area,
refer to the \Option{DIV} option with the values \PValue{last} or
\PValue{current} (see \autopageref{desc:typearea.option.DIV.last}) or
the \Macro{recalctypearea} command (see
@@ -1375,7 +1460,7 @@ the \Macro{recalctypearea} command (see
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 them in the division of the
- page into type-area and margins.
+ 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
@@ -1421,7 +1506,7 @@ at \autoref{tab:typearea.outputdriver}. The default is
\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
+ Does not set any output driver and does not 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
@@ -1516,7 +1601,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. \emph{Usable} frequently means readable and correctable. In
-the author's opinion the type-area of a text set with {\LaTeX} and the
+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
obviously substantially from it, then the author recommends submitting
@@ -1527,7 +1612,7 @@ modification of option \Option{DIV}. The author advises against the
use of \Macro{areaset} for this purpose however. In the worst case
one may make use of the geometry package (see
\cite{package:geometry}), which is not part of \KOMAScript, or change
-the type-area parameters of \LaTeX. One may find the values
+the type area parameters of \LaTeX. One may find the values
determined by \Package{typearea} in the \File{log} file of one's
document. Thus moderate adjustments should be possible. However, one
should make absolutely sure that the proportions of the text area
@@ -1542,7 +1627,7 @@ too frequently, it has been obsolete since the introduction of
\Macro{linespread}. The author recommends the package
\Package{setspace}\IndexPackage{setspace} (see
\cite{package:setspace}), which is not part of \KOMAScript. Also one
-should let \Package{typearea} recalculate a new type-area after the
+should let \Package{typearea} recalculate a new type area after the
conversion of the line spacing. However, one should switch back to
the normal line spacing for the title, preferably also for the table
contents and various listings\,---\,as well as the bibliography and
@@ -1557,7 +1642,7 @@ respective document. Thus one can select a smaller value easily after
the first {\LaTeX} run.
The question is not infrequently put to the author, why he spends an
-entire chapter discussing type-area calculations, when it would be
+entire chapter discussing type area calculations, when it would be
very much simpler to merely give the world a package with which anyone
can adjust the margins like in a word processor. Often it is added
that such a package would in any case be the better solution, since