Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Fri, 19 May 2000 14:09:25 +0200 (MET DST) 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 OAA20773 for ; Fri, 19 May 2000 14:09:25 +0200 (MET DST) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.10.1/8.10.1) with ESMTP id e4JC9OK10457 for ; Fri, 19 May 2000 14:09:25 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFC18B.12D18880" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <3.4C502A66@mail.listserv.gmd.de>; Fri, 19 May 2000 14:09:23 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 456701 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 19 May 2000 14:08:51 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 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 OAA06753 for ; Fri, 19 May 2000 14:08:50 +0200 (MET DST) 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 OAA13408 for ; Fri, 19 May 2000 14:08:49 +0200 Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id OAA07868 for ; Fri, 19 May 2000 14:08:50 +0200 (MET DST) Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.10.1/8.10.1) with ESMTP id e4JC8nK10366 for ; Fri, 19 May 2000 14:08:49 +0200 (MET DST) Received: from istrati.zdv.uni-mainz.de (dialin340.zdv.Uni-Mainz.DE [134.93.175.40]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id OAA20613 for ; Fri, 19 May 2000 14:08:48 +0200 (MET DST) Received: (from latex3@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id MAA01260; Fri, 19 May 2000 12:55:58 +0200 In-Reply-To: <200003081236.NAA20730@mozart.ujf-grenoble.fr> References: <14534.13514.933795.835811*@MHS> <200003081236.NAA20730@mozart.ujf-grenoble.fr> Return-Path: X-Mailer: VM 6.75 under Emacs 20.4.1 x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["674" "Fri" "19" "May" "2000" "12:55:58" "+0200" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "14" "Re: float position rules" "^Date:" nil nil "5" nil nil nil nil nil]nil) x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id OAA06754 X-Authentication-Warning: istrati.zdv.uni-mainz.de: latex3 set sender to frank.mittelbach@latex-project.org using -f Content-class: urn:content-classes:message Subject: Re: float position rules Date: Fri, 19 May 2000 11:55:58 +0100 Message-ID: <14629.7614.888477.457149@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3582 This is a multi-part message in MIME format. ------_=_NextPart_001_01BFC18B.12D18880 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thierry Bouche writes: > =BB No please no! We want to know what rules and heuristics > =BB forward-looking authors, designers and editors think should be in = this > > The notion of `facing pages' is important (also for spread, i > suppose): I don't care whether a float goes after or before its call, > but i care whether it appears on the same double as the related > text... This is something i currently handle manually (and = painfully). well, as you learned in Toulouse the algorithm as of today doesn't offer = the functionality to force a float onto the same page as its call-out, but = as i wrote in the article i do expect to add "fuzzy-flushing" pretty soon. frank ------_=_NextPart_001_01BFC18B.12D18880 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: float position rules

Thierry Bouche writes:
 > =BB No please no!  We want to know = what rules and heuristics
 > =BB forward-looking authors, designers and = editors think should be in this
 >
 > The notion of `facing pages' is important = (also for spread, i
 > suppose): I don't care whether a float = goes after or before its call,
 > but i care whether it appears on the same = double as the related
 > text... This is something i currently = handle manually (and painfully).

well, as you learned in Toulouse the algorithm as of = today doesn't offer the
functionality to force a float onto the same page as = its call-out, but as i
wrote in the article i do expect to add = "fuzzy-flushing" pretty soon.

frank

------_=_NextPart_001_01BFC18B.12D18880--