Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Wed, 8 Mar 2000 15:29:38 +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 PAA04412 for ; Wed, 8 Mar 2000 15:29:38 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF890A.BB9D7500" 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 PAA28091 for ; Wed, 8 Mar 2000 15:29:37 +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 <14.645B3C2D@mail.listserv.gmd.de>; Wed, 8 Mar 2000 15:28:17 +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 452310 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 8 Mar 2000 15:26:52 +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 PAA28844 for ; Wed, 8 Mar 2000 15:26:51 +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 PAA15578 for ; Wed, 8 Mar 2000 15:29:31 +0100 Received: from nag.co.uk ([62.232.54.10]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id PAA03900 for ; Wed, 8 Mar 2000 15:26:50 +0100 (MET) Received: (from davidc@localhost) by nag.co.uk (AIX4.2/UCB 8.7/8.7) id OAA23470; Wed, 8 Mar 2000 14:25:36 GMT In-Reply-To: (message from Barbara Beeton on Wed, 8 Mar 2000 09:11:38 -0500) References: Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1269" "Wed" "8" "March" "2000" "14:25:36" "GMT" "David Carlisle" "davidc@NAG.CO.UK" nil "54" "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:25:36 +0100 Message-ID: <200003081425.OAA23470@nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" 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: 3568 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF890A.BB9D7500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Barbara since you mentioned floats spanning some or all the columns does AMS have any rules about the relative _order_ of these float areas. latex always keeps floats in order. It's fairly clear that top of page is before bottom of page, but in general it isn't so claer what `order' means. If you have a single column float followed (in the document callout/reference order) by a double column float can you typeset them as --------------float 2 ----------- ----float 1 -- or do you have to have ----float 1 -- and defer --------------float 2 ----------- to next page. If you allow the former would you also have allowed --------------float 1 ----------- ----float 2 -- ie consider just a partial order on float areas with either the single or double column top being first. if so would you allow --------------float 2 ----------- ----float 1 -- ----float 3 -- and similar permutations on a theme. the algorithm is really quite a bit simpler if you can impose a strict ordering on areas (it doesn't matter what the ordering is) but that might be too rigid. But once you open up the possibilities of partial orderings on the areas, there is a danger of combinatorial explosion in the number of possible arrangements that need to be tried. David ------_=_NextPart_001_01BF890A.BB9D7500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: float position rules

Barbara since you mentioned floats spanning some or = all the columns
does AMS have any rules about the relative _order_ of = these float areas.
latex always keeps floats in order. It's fairly clear = that top of page
is before bottom of page, but in general it isn't so = claer what `order'
means. If you have a single column float followed (in = the document
callout/reference order) by a double column float can = you typeset
them as



--------------float 2 -----------

----float 1 --


or do you have to have

----float 1 --

and defer

--------------float 2 -----------

to next page.

If you allow the former would you also have = allowed


--------------float 1 -----------
----float 2 --

ie consider just a partial order on float areas with = either
the single or double column top being first.

if so would you allow



--------------float 2 -----------
----float 1 --
----float 3 --


and similar permutations on a theme.

the algorithm is really quite a bit simpler if you can = impose a strict
ordering on areas (it doesn't matter what the = ordering is) but that
might be too rigid. But once you open up the = possibilities of partial
orderings on the areas, there is a danger of = combinatorial explosion in
the number of possible arrangements that need to be = tried.


David

------_=_NextPart_001_01BF890A.BB9D7500--