Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Wed, 8 Mar 2000 15:11:47 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id PAA01189 for ; Wed, 8 Mar 2000 15:11:46 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF8908.3D3FD380" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id PAA26700 for ; Wed, 8 Mar 2000 15:11:45 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <4.E5FD2217@mail.listserv.gmd.de>; Wed, 8 Mar 2000 15:10:26 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 452282 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 8 Mar 2000 15:09:02 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id PAA28431 for ; Wed, 8 Mar 2000 15:09:01 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id PAA18440 for ; Wed, 8 Mar 2000 15:11:41 +0100 Received: from ams.org (sun06.ams.org [130.44.1.6]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id PAA29947 for ; Wed, 8 Mar 2000 15:08:59 +0100 (MET) Received: from localhost (bnb@localhost) by ams.org (8.9.3/8.9.3) with ESMTP id JAA25774 for ; Wed, 8 Mar 2000 09:11:38 -0500 (EST) In-Reply-To: <200003081323.NAA23620@nag.co.uk> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1456" "Wed" "8" "March" "2000" "09:11:38" "-0500" "Barbara Beeton" "bnb@AMS.ORG" nil "35" "Re: float position rules" "^Date:" nil nil "3" nil nil nil nil nil]nil) Content-class: urn:content-classes:message Subject: Re: float position rules Date: Wed, 8 Mar 2000 15:11:38 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Barbara Beeton" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3567 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF8908.3D3FD380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable since you're now looking for heuristics, and nobody has yet mentioned working with multiple columns, let me address that a bit from experience here at ams, mostly with the ams notices. if there is a running footer, that, of course, always goes at the very bottom. if there is a spanning bottom float, that goes next at the bottom; one-column footnotes go above a spanning float. i have no experience with spanning footnotes. however, there are a number of situations where ancillary material is packaged into a spanning bottom float with its own multi-column arrangement; the number of columns in the float may, but need not, be the same as the number of columns on the main part of the page. a spanning bottom float which covers fewer columns than the whole page goes above any full-width spanning floats. one-column footnotes are still above this. a one-column bottom float goes above footnotes. a footnote goes at the bottom of the same column as its callout. unnumbered footnotes (first-page credits, e.g.) always go in the column in which the item begins. if the last column ends "short", any footnotes in that column still go at the very bottom of the page. a one-column, full-page-length float appears to be preferentially placed in an "outside" column. tables are more often placed at the top rather than at the bottom. footnotes to a table appear directly below the table. -- bb ------_=_NextPart_001_01BF8908.3D3FD380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: float position rules

since you're now looking for heuristics, and nobody = has yet
mentioned working with multiple columns, let me = address that a bit
from experience here at ams, mostly with the ams = notices.

if there is a running footer, that, of course, always = goes at the
very bottom.

if there is a spanning bottom float, that goes next at = the bottom;
one-column footnotes go above a spanning float.  = i have no experience
with spanning footnotes.  however, there are a = number of situations
where ancillary material is packaged into a spanning = bottom float
with its own multi-column arrangement; the number of = columns in the
float may, but need not, be the same as the number of = columns on
the main part of the page.

a spanning bottom float which covers fewer columns = than the whole
page goes above any full-width spanning floats.  = one-column footnotes
are still above this.

a one-column bottom float goes above footnotes.

a footnote goes at the bottom of the same column as = its callout.
unnumbered footnotes (first-page credits, e.g.) = always go in the
column in which the item begins.

if the last column ends "short", any = footnotes in that column
still go at the very bottom of the page.

a one-column, full-page-length float appears to be = preferentially
placed in an "outside" column.

tables are more often placed at the top rather than at = the bottom.
footnotes to a table appear directly below the = table.
          &nbs= p;            = ;            =             &= nbsp;        -- bb

------_=_NextPart_001_01BF8908.3D3FD380--