Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Tue, 7 Mar 2000 19:51:54 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id TAA03314 for ; Tue, 7 Mar 2000 19:51:54 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id TAA10946 for ; Tue, 7 Mar 2000 19:51:53 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF8866.3496C100" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.DE1EF664@mail.listserv.gmd.de>; Tue, 7 Mar 2000 19:50:35 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 452488 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 7 Mar 2000 19:49:13 +0100 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 TAA10587 for ; Tue, 7 Mar 2000 19:49:11 +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 TAA19980 for ; Tue, 7 Mar 2000 19:51:49 +0100 Received: from ixgate02.dfnrelay.d400.de (ixgate02.dfnrelay.d400.de [193.174.248.2]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id TAA21008 for ; Tue, 7 Mar 2000 19:49:11 +0100 (MET) In-Reply-To: "200003062306.AAA02162": References: "200003052035.VAA01735":, "200003062306.AAA02162": Return-Path: X-Mailer: VM 6.44 under Emacs 19.34.1 x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1652" "Tue" "7" "March" "2000" "19:51:37" "+0100" "Chris Rowley" "C.A.Rowley@OPEN.AC.UK" nil "46" "On float position rules and forgiveness" "^Date:" nil nil "3" nil nil nil nil nil]nil) x400-received: by /PRMD=uk.ac/ADMD= /C=gb/; Relayed; Tue, 7 Mar 2000 19:51:37 +0100 x400-mts-identifier: [/PRMD=UK.AC/ADMD= /C=GB/;<14533.18280.231752.298772@fell.] content-identifier: On float posi... x400-content-type: P2-1984 (2) alternate-recipient: Allowed x400-originator: C.A.Rowley@open.ac.uk x400-recipients: non-disclosure:; Content-class: urn:content-classes:message Subject: On float position rules and forgiveness Date: Tue, 7 Mar 2000 19:51:37 +0100 Message-ID: <14533.18280.231752.298772*@MHS> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Chris Rowley" 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: 3554 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF8866.3496C100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank slipped these into his advertising splash, I see: > - allows for changing the position algorithm > > - will soon do spanning floats Which prompts me to publicly say: I forgive Sebastian Rahtz!! (Well for one thing, anyway ... there's still hyperref:-) ) for never having supplied us humble coders with what he claims is `the obvious algorithm for float positioning (including spanning floats)'. Having tried quite hard over the last few weeks to look inside his mind and reconstruct it, I now realise that it does require a somewhat weird intellect (something Dr Rahtz refers to in a phrase involving `planets', `brains' and `like you ****ing mathematicians') to find an algorithm that is time- and space-efficient but also gets a reasonably good result most of the time (and maybe even warns you when it is not doing so well). Help Wanted =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The reason why I am going pubic in this particular forum is to ask for your help. Not necessarily help in designing this wonderful algorithm but in formulating, or finding in the literature, the rules and heuristics for judging whether a float placement is acceptable and/or good. Frank has already mentioned that the rules of classic LaTeX can perhaps be relaxed somewhat: > - handle different float strategies, eg float after callout, float = after or > in the same column, float on the same page but these are only suggestions and the need to deal with spreads and with spanning floats will certainly call for further strategies. Thanks in advance, and please pass this request on to anyone who is interested or has useful knowledge. chris ------_=_NextPart_001_01BF8866.3496C100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On float position rules and forgiveness

Frank slipped these into his advertising splash, I = see:

>  - allows for changing the position = algorithm
>
>  - will soon do spanning floats

Which prompts me to publicly say:

  I forgive Sebastian Rahtz!! (Well for one = thing, anyway
          &nbs= p;            = ;        ... there's still = hyperref:-) )

for never having supplied us humble coders with what = he claims is `the
obvious algorithm for float positioning (including = spanning floats)'.

Having tried quite hard over the last few weeks to = look inside his
mind and reconstruct it, I now realise that it does = require a somewhat
weird intellect (something Dr Rahtz refers to in a = phrase involving
`planets', `brains' and `like you ****ing = mathematicians') to find an
algorithm that is time- and space-efficient but also = gets a reasonably
good result most of the time (and maybe even warns = you when it is not
doing so well).

Help Wanted
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The reason why I am going pubic in this particular = forum is to ask for
your help.

Not necessarily help in designing this wonderful = algorithm but in
formulating, or finding in the literature, the rules = and heuristics for
judging whether a float placement is acceptable = and/or good.

Frank has already mentioned that the rules of classic = LaTeX can
perhaps be relaxed somewhat:

>  - handle different float strategies, eg = float after callout, float after or
>    in the same column, float on = the same page

but these are only suggestions and the need to deal = with spreads
and with spanning floats will certainly call for = further strategies.

Thanks in advance, and please pass this request on to = anyone who is
interested or has useful knowledge.


chris

------_=_NextPart_001_01BF8866.3496C100--