summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/placeins/placeins.txt
blob: aee762d13d184bfbe0ab66ea54e2227e7075e129 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

  p l a c e i n s . s t y          ver 2.2  April 18, 2005
  Donald Arseneau                  asnd@triumf.ca


Placeins.sty keeps floats `in their place', preventing them from floating
past a "\FloatBarrier" command into another section.  To use it, declare
"\usepackage{placeins}" and insert "\FloatBarrier" at places that floats 
should not move past, perhaps at every "\section".  

Option:  [section]

A more convenient way to stop floats at section boundaries is to change 
the definition of "\section" to include "\FloatBarrier", either at the
beginning, before "\@startsection", or in the `style' specification (see 
The LaTeX Companion, section 2.2.2; or 2.3 in the 1st ed).  If you specify 
"\usepackage[section]{placeins}", then the "\section" command will be 
redefined with "\FloatBarrier" inserted at the beginning.

Options:  [above]  [below]

Something you may not like is that, by default, "\FloatBarrier" is very 
strict, and will (try to) prevent a float from appearing above the start 
of the current section or below the start of the next section, even 
though the float is still on the same page as its intended section.  
Each restriction can be relaxed separately by using the "[above]" and 
"[below]" package options: "[above]" allows floats to appear above their 
section, if on the same page; "[below]" allows below.

NOTE!  The original version of placeins.sty acted like it was loaded
with the option "[above]" specified.

There is a problem with LaTeX's "\suppressfloats" being out of step with 
the page breaking (see usenet msg <yfi656pbsn0.fsf@triumf.ca> and thread)
which sometimes allows a float to go above a "\FloatBarrier" placed near
the top of a page. Maybe placeins will fix it sometime later.

Option: [verbose]

There is a package option "[verbose]" that causes many messages to be
written in the log file.  It might be used to answer the question:
`How did *that* get *there*?!?'