summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html20
1 files changed, 20 insertions, 0 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html
new file mode 100644
index 00000000000..59e5a8413be
--- /dev/null
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html
@@ -0,0 +1,20 @@
+<head>
+<title>UK TeX FAQ -- question label nocite*</title>
+</head><body>
+<h3>Listing all your BibTeX entries</h3>
+<p>LaTeX and BibTeX co-operate to offer special treatment of this
+requirement. The command <code>\</code><code>nocite{*}</code> is specially treated,
+and causes BibTeX to generate bibliography entries for every entry
+in each <code>.bib</code> file listed in your <code>\</code><code>bibliography</code> statement, so
+that after a LaTeX-BibTeX-LaTeX sequence, you have a
+document with the whole thing listed.
+<p>Note that LaTeX <em>doesn't</em> produce
+
+"<code>Citation ... undefined</code>" or
+"<code>There were undefined references</code>" warnings in respect of
+<code>\</code><code>nocite{*}</code>. This isn't a problem if you're running
+LaTeX "by hand" (you <em>know</em> exactly how many times you have
+to run things), but the lack might confuse automatic processors that
+scan the log file to determine whether another run is necessary.
+<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*</a>
+</body>