summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html18
1 files changed, 9 insertions, 9 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
index e3a0dfd830e..f9c6f06b308 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-bibstrtl.html
@@ -1,15 +1,15 @@
<head>
<title>UK TeX FAQ -- question label bibstrtl</title>
</head><body>
-<h3>&lsquo;String too long&rsquo; in BibTeX</h3>
-<p/>The BibTeX diagnostic &ldquo;Warning&ndash;you&rsquo;ve exceeded 1000, the
-<code>global-string-size</code>, for entry <code>foo</code>&rdquo; usually arises
+<h3>&#8216;String too long&#8217; in BibTeX</h3>
+<p/>The BibTeX diagnostic &#8220;Warning&#8211;you&#8217;ve exceeded 1000, the
+<code>global-string-size</code>, for entry <code>foo</code>&#8221; usually arises
from a very large abstract or annotation included in the database.
The diagnostic usually arises because of an infelicity in the coding of
-<i>abstract.bst</i>, or styles derived from it. (One doesn&rsquo;t
+<i>abstract.bst</i>, or styles derived from it. (One doesn&#8217;t
ordinarily output annotations in other styles.)
<p/>The solution is to make a copy of the style file (or get a clean copy
-from CTAN &mdash; <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a
+from CTAN &#8212; <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a
long file-name system, to <i>abstract-long.bst</i>). Now edit it: find
function <code>output.nonnull</code> and
<ul>
@@ -27,16 +27,16 @@ to
</pre>
</blockquote><p>
Finally,
-<li> delete the function&rsquo;s last line, which just says &ldquo;<code>s</code>
+<li> delete the function&#8217;s last line, which just says &#8220;<code>s</code>
(line 84 in the version on CTAN).
</ul>
Finally, change your <code>\</code><code>bibliographystyle</code> command to refer to the
name of the new file.
<p/>This technique applies equally to any bibliography style: the same
change can be made to any similar <code>output.nonnull</code> function.
-<p/>If you&rsquo;re reluctant to make this sort of change, the only way forward
-is to take the entry out of the database, so that you don&rsquo;t encounter
-BibTeX&rsquo;s limit, but you may need to retain the entry because it
+<p/>If you&#8217;re reluctant to make this sort of change, the only way forward
+is to take the entry out of the database, so that you don&#8217;t encounter
+BibTeX&#8217;s limit, but you may need to retain the entry because it
will be included in the typeset document. In such cases, put the body
of the entry in a separate file:
<blockquote>