summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html28
1 files changed, 28 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html
new file mode 100644
index 00000000000..9d2d936517b
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fllost.html
@@ -0,0 +1,28 @@
+<head>
+<title>UK TeX FAQ -- question label fllost</title>
+</head><body>
+<h3>Float(s) lost</h3>
+<p/>The error
+<blockquote>
+<pre>
+! LaTeX Error: Float(s) lost.
+</pre>
+</blockquote><p>
+seldom occurs, but always seems deeply cryptic when it <em>does</em>
+appear.
+<p/>The message means what it says: one or more figures, tables, etc., or
+marginpars has not been typeset. (Marginpars are treated internally
+as floats, which is how they come to be lumped into this error
+message.)
+<p/>The most likely reason is that you placed a float or a <code>\</code><code>marginpar</code>
+command inside another float or marginpar, or inside a
+<code>minipage</code> environment, a <code>\</code><code>parbox</code> or <code>\</code><code>footnote</code>.
+Note that the error may be detected a long way from the problematic
+command(s), so the techniques of
+<a href="FAQ-erroradvice.html">tracking down elusive errors</a> all need to be
+called into play.
+<p/>This author has also encountered the error when developing macros that
+used the LaTeX internal float mechanisms. Most people doing that
+sort of thing are expected to be able to work out their own problems...
+<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a>
+</body>