summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
index a65b44f6bcc..81833835bdc 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-semanticnest.html
@@ -1,7 +1,7 @@
<head>
<title>UK TeX FAQ -- question label semanticnest</title>
</head><body>
-<h3>Capacity exceeded [semantic nest &hellip;]</h3>
+<h3>Capacity exceeded [semantic nest &#8230;]</h3>
<p/>
<pre>
! TeX capacity exceeded, sorry [semantic nest size=100].
@@ -12,7 +12,7 @@ you can ask a wizard to enlarge me.
Even though TeX suggests (as always) that enlargement by a wizard
may help, this message usually results from a broken macro or bad
parameters to an otherwise working macro.
-<p/>The &ldquo;semantic nest&rdquo; TeX talks about is the nesting
+<p/>The &#8220;semantic nest&#8221; TeX talks about is the nesting
of boxes within boxes. A stupid macro can provoke the error pretty
easily:
<blockquote>
@@ -28,16 +28,16 @@ The extended traceback
<em>does</em> help, though it does rather run on. In the case above,
the traceback consists of
<pre>
-\silly -&gt;\hbox {
+\silly -&#62;\hbox {
here's \silly being executed}
</pre>
followed by 100 instances of
<pre>
-\silly -&gt;\hbox {here's \silly
+\silly -&#62;\hbox {here's \silly
being executed}
</pre>
The repeated lines are broken at exactly the offending macro; of
-course the loop need not be as simple as this &mdash; if <code>\</code><code>silly</code> calls
+course the loop need not be as simple as this &#8212; if <code>\</code><code>silly</code> calls
<code>\</code><code>dopy</code> which boxes <code>\</code><code>silly</code>, the effect is just the same and
alternate lines in the traceback are broken at alternate positions.
<p/>There are in fact two items being consumed when you nest boxes: the