summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
index a2524a0427f..76ebcd82405 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-casechange.html
@@ -3,11 +3,11 @@
</head><body>
<h3>Case-changing oddities</h3>
<p/>TeX provides two primitive commands <code>\</code><code>uppercase</code> and
-<code>\</code><code>lowercase</code> to change the case of text; they&rsquo;re not much used, but
+<code>\</code><code>lowercase</code> to change the case of text; they&#8217;re not much used, but
are capable creating confusion.
-<p/>The two commands do not expand the text that is their parameter &mdash;
-the result of <code>\</code><code>uppercase{abc}</code> is &lsquo;<code>ABC</code>&rsquo;, but
-<code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always &lsquo;<code>\</code><code>abc</code>&rsquo;, whatever the
+<p/>The two commands do not expand the text that is their parameter &#8212;
+the result of <code>\</code><code>uppercase{abc}</code> is &#8216;<code>ABC</code>&#8217;, but
+<code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always &#8216;<code>\</code><code>abc</code>&#8217;, whatever the
meaning of <code>\</code><code>abc</code>. The commands are simply interpreting a table of
equivalences between upper- and lowercase characters.
They have (for example) no mathematical sense, and
@@ -32,7 +32,7 @@ standard classes to produce upper case running heads for chapters
and sections.
<p/>Unfortunately <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> do not solve
the other problems with <code>\</code><code>uppercase</code>, so for example a section
-title containing <code>\</code><code>begin{tabular}</code> &hellip;
+title containing <code>\</code><code>begin{tabular}</code> &#8230;
<code>\</code><code>end{tabular}</code> will produce a running head containing
<code>\</code><code>begin{TABULAR}</code>. The simplest solution to this problem is
using a user-defined command, for example:
@@ -47,8 +47,8 @@ using a user-defined command, for example:
Note that <code>\</code><code>mytable</code> has to be protected, otherwise it will be
expanded and made upper case; you can achieve the same result by
declaring it with <code>\</code><code>DeclareRobustCommand</code>, in which case the
-<code>\</code><code>protect</code> won&rsquo;t be necessary.
-<p/>David Carlisle&rsquo;s <i>textcase</i> package
+<code>\</code><code>protect</code> won&#8217;t be necessary.
+<p/>David Carlisle&#8217;s <i>textcase</i> package
addresses many of these problems in a transparent way. It defines
commands <code>\</code><code>MakeTextUppercase</code> and <code>\</code><code>MakeTextLowercase</code> which do
upper- or lowercase, with the fancier features of the LaTeX
@@ -56,7 +56,7 @@ standard <code>\</code><code>Make*</code>-commands but without the problems
mentioned above. Load the package with
<code>\</code><code>usepackage[overload]{textcase}</code>, and it will redefine the LaTeX
commands (<em>not</em> the TeX primitive commands <code>\</code><code>uppercase</code> and
-<code>\</code><code>lowercase</code>), so that section headings and the like don&rsquo;t produce
+<code>\</code><code>lowercase</code>), so that section headings and the like don&#8217;t produce
broken page headings.
<dl>
<dt><tt><i>textcase.sty</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase.zip">macros/latex/contrib/textcase</a> (or <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase/">browse the directory</a>)