summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
index cdaf84cfbbf..66c40d9b7ed 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-cvtlatex.html
@@ -8,7 +8,7 @@ also help users of Plain TeX or other packages; this answer
attempts to provide a rough-and-ready guide to transcribing such macro
definitions for use in other packages.
<p/>The reason LaTeX has commands that replace <code>\</code><code>def</code>, is that
-there&rsquo;s a general philosophy within LaTeX that the user should be
+there&#8217;s a general philosophy within LaTeX that the user should be
protected from himself: the user has different commands according to
whether the command to be defined exists (<code>\</code><code>renewcommand</code>) or not
(<code>\</code><code>newcommand</code>), and if its status proves not as the user expected,
@@ -16,9 +16,9 @@ an error is reported. A third definition command,
<code>\</code><code>providecommand</code>, only defines if the target is not already
defined; LaTeX has no direct equivalent of <code>\</code><code>def</code>, which ignores
the present state of the command. The final command of this sort is
-<code>\</code><code>DeclareRobustCommand</code>, which creates a command which is &ldquo;robust&rdquo;
-(i.e., will not expand if subjected to LaTeX &ldquo;protected
-expansion&rdquo;); from the Plain TeX user&rsquo;s point of view,
+<code>\</code><code>DeclareRobustCommand</code>, which creates a command which is &#8220;robust&#8221;
+(i.e., will not expand if subjected to LaTeX &#8220;protected
+expansion&#8221;); from the Plain TeX user&#8217;s point of view,
<code>\</code><code>DeclareRobustCommand</code> should be treated as a non-checking version
of <code>\</code><code>newcommand</code>.
<p/>LaTeX commands are, by default, defined <code>\</code><code>long</code>; an optional <code>*</code>
@@ -27,7 +27,7 @@ the command is <em>not</em> to be defined <code>\</code><code>long</code>. The
detected by a command <code>\</code><code>@ifstar</code> which uses <code>\</code><code>futurelet</code> to switch
between two branches, and gobbles the <code>*</code>: LaTeX users are
encouraged to think of the <code>*</code> as part of the command name.
-<p/>LaTeX&rsquo;s checks for unknown command are done by <code>\</code><code>ifx</code> comparison
+<p/>LaTeX&#8217;s checks for unknown command are done by <code>\</code><code>ifx</code> comparison
of a <code>\</code><code>csname</code> construction with <code>\</code><code>relax</code>; since the command name
argument is the desired control sequence name, this proves a little
long-winded. Since <code>#1</code> is the requisite argument, we have:
@@ -42,9 +42,9 @@ long-winded. Since <code>#1</code> is the requisite argument, we have:
</blockquote><p>
(<code>\</code><code>@gobble</code> simply throws away its argument).
<p/>The arguments of a LaTeX command are specified by two optional
-arguments to the defining command: a count of arguments (0&ndash;9: if the
+arguments to the defining command: a count of arguments (0&#8211;9: if the
count is 0, the optional count argument may be omitted), and a default
-value for the first argument, if the defined command&rsquo;s first argument
+value for the first argument, if the defined command&#8217;s first argument
is to be optional. So:
<blockquote>
<pre>