summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html18
1 files changed, 9 insertions, 9 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html
index 10327ca08fa..bcc7d341a3b 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html
@@ -1,29 +1,29 @@
<head>
<title>UK TeX FAQ -- question label protect</title>
</head><body>
-<h3>What's the reason for 'protection'?</h3>
+<h3>What&rsquo;s the reason for &lsquo;protection&rsquo;?</h3>
<p>Sometimes LaTeX saves data it will reread later. These data are
often the argument of some command; they are the so-called moving
-arguments. ('Moving' because data are moved around.) Places to look for
+arguments. (&lsquo;Moving&rsquo; because data are moved around.) Places to look for
are all arguments that may go into table of contents, list of figures,
<em>etc</em>.; namely, data that are written to an auxiliary file and
read in later. Other places are those data that might appear in head-
or footlines. Section headings and figure captions are the most
-prominent examples; there's a complete list in Lamport's book
+prominent examples; there&rsquo;s a complete list in Lamport&rsquo;s book
(see <a href="FAQ-books.html">TeX-related books</a>).
<p>
-<p>What's going on really, behind the scenes? The commands in the moving
+<p>What&rsquo;s going on really, behind the scenes? The commands in the moving
arguments are already expanded to their internal structure during the
process of saving. Sometimes this expansion results in invalid TeX
-code when processed again. "<code>\</code><code>protect</code><code>\</code><code>cmd</code>" tells LaTeX to save
+code when processed again. &ldquo;<code>\</code><code>protect</code><code>\</code><code>cmd</code>&rdquo; tells LaTeX to save
<code>\</code><code>cmd</code> as <code>\</code><code>cmd</code>, without expansion.
-<p>What is a 'fragile command'? It's a command that expands into illegal
+<p>What is a &lsquo;fragile command&rsquo;? It&rsquo;s a command that expands into illegal
TeX code during the save process.
-<p>What is a 'robust command'? It's a command that expands into legal
+<p>What is a &lsquo;robust command&rsquo;? It&rsquo;s a command that expands into legal
TeX code during the save process.
-<p>Again, commands are marked as 'robust' or 'fragile', as they're
-defined in Lamport's book. Sadly, some commands are robust in
+<p>Again, commands are marked as &lsquo;robust&rsquo; or &lsquo;fragile&rsquo;, as they&rsquo;re
+defined in Lamport&rsquo;s book. Sadly, some commands are robust in
LaTeX itself, but are redefined by some packages to be fragile; the
<code>\</code><code>cite</code> command commonly suffers this treatment.
<p>No-one (of course) likes this situation; the LaTeX3 team have