summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-runheadtoobig.html
diff options
context:
space:
mode:
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.html16
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&rsquo;s common for titles too
+operate in a rather constrained area, and it&#8217;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 &ldquo;ordinary&rdquo; reading? It&rsquo;s not possible to do so with unmodified
+for &#8220;ordinary&#8221; reading? It&#8217;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&rsquo;s uppercasing tendencies. Classes in the <i>KOMA-script</i>
-bundle don&rsquo;t uppercase in the first place.
-<p/>In fact, the sectioning commands use &lsquo;mark&rsquo; commands to pass
+LaTeX&#8217;s uppercasing tendencies. Classes in the <i>KOMA-script</i>
+bundle don&#8217;t uppercase in the first place.
+<p/>In fact, the sectioning commands use &#8216;mark&#8217; 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 &ldquo;<em>middling version</em>&rdquo; is in fact the same text as
-&ldquo;<em>long version&rdquo;</em>.)
+even if &#8220;<em>middling version</em>&#8221; is in fact the same text as
+&#8220;<em>long version&#8221;</em>.)
<p/>A similar arrangement is necessary even for chapters if the class
-you&rsquo;re using is odd enough that it puts a page header on a chapter&rsquo;s
+you&#8217;re using is odd enough that it puts a page header on a chapter&#8217;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