diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html index 9a7a49598ad..02c61b595c5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html @@ -4,7 +4,7 @@ <h3>My section title is too wide for the page header</h3> <p/>By default, LaTeX sectioning commands make the chapter or section title available for use by page headers and the like. Page headers -operate in a rather constrained area, and it’s common for titles too +operate in a rather constrained area, and it’s common for titles too be too big to fit: the LaTeX sectioning commands therefore take an optional argument: <blockquote> @@ -23,12 +23,12 @@ scheme is to have a shortened table of contents entry, and a really terse entry in the running head. <p/>One of the problems is the tendency of page headings to be set in capitals (which take up more space); so why not set headings as written -for “ordinary” reading? It’s not possible to do so with unmodified +for “ordinary” reading? It’s not possible to do so with unmodified LaTeX, but the <i>fancyhdr</i> package provides a command <code>\</code><code>nouppercase</code> for use in its header (and footer) lines to suppress -LaTeX’s uppercasing tendencies. Classes in the <i>KOMA-script</i> -bundle don’t uppercase in the first place. -<p/>In fact, the sectioning commands use ‘mark’ commands to pass +LaTeX’s uppercasing tendencies. Classes in the <i>KOMA-script</i> +bundle don’t uppercase in the first place. +<p/>In fact, the sectioning commands use ‘mark’ commands to pass information to the page headers. For example, <code>\</code><code>chapter</code> uses <code>\</code><code>chaptermark</code>, <code>\</code><code>section</code> uses <code>\</code><code>sectionmark</code>, and so on. With this knowledge, one can achieve a three-layer structure for chapters: @@ -55,10 +55,10 @@ the recipe for sections is more tiresome: (the first <code>\</code><code>sectionmark</code> deals with the header of the page the <code>\</code><code>section</code> command falls on, and the second deal with subsequent pages; note that here, you need the optional argument to <code>\</code><code>section</code>, -even if “<em>middling version</em>” is in fact the same text as -“<em>long version”</em>.) +even if “<em>middling version</em>” is in fact the same text as +“<em>long version”</em>.) <p/>A similar arrangement is necessary even for chapters if the class -you’re using is odd enough that it puts a page header on a chapter’s +you’re using is odd enough that it puts a page header on a chapter’s opening page. <p/>Note that the <i>titlesec</i> package manages the running heads in a completely different fashion; users of that package should refer to |