Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Tue, 7 Mar 2000 21:08:26 +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 VAA13709 for ; Tue, 7 Mar 2000 21:08:26 +0100 (MET) MIME-Version: 1.0 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 VAA15267 for ; Tue, 7 Mar 2000 21:08:26 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF8870.E5A25900" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <11.8D4099A0@mail.listserv.gmd.de>; Tue, 7 Mar 2000 21:07:04 +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 452533 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 7 Mar 2000 21:05:41 +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 VAA12599 for ; Tue, 7 Mar 2000 21:05:40 +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 VAA15620 for ; Tue, 7 Mar 2000 21:08:17 +0100 Received: from oxmail.ox.ac.uk (oxmail3.ox.ac.uk [129.67.1.180]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id VAA00079 for ; Tue, 7 Mar 2000 21:05:40 +0100 (MET) Received: from ermine.ox.ac.uk ([163.1.2.13]) by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 12SQHC-0007kz-00 for LATEX-L@urz.uni-heidelberg.de; Tue, 7 Mar 2000 20:08:18 +0000 Received: from max11.public.ox.ac.uk ([192.76.27.11] helo=localhost.localdomain ident=rahtz) by ermine.ox.ac.uk with smtp (Exim 3.13 #1) id 12SQHB-0005GI-00 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Tue, 07 Mar 2000 20:08:17 +0000 In-Reply-To: <14533.18280.231752.298772*@MHS> References: <14533.18280.231752.298772*@MHS> Return-Path: X-Mailer: 20.4 "Emerald" XEmacs Lucid (via feedmail 8 Q); VM 6.71 under 20.4 "Emerald" XEmacs Lucid x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1161" "Tue" "7" "March" "2000" "19:49:00" "+0000" "Sebastian Rahtz" "sebastian.rahtz@COMPUTING-SERVICES.OXFORD.AC.UK" nil "34" "Re: On float position rules and forgiveness" "^Date:" nil nil "3" nil nil nil nil nil]nil) Content-class: urn:content-classes:message Subject: Re: On float position rules and forgiveness Date: Tue, 7 Mar 2000 20:49:00 +0100 Message-ID: <14533.23852.749326.77360@localhost.localdomain> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Sebastian Rahtz" 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: 3555 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF8870.E5A25900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Chris Rowley writes: > I forgive Sebastian Rahtz!! (Well for one thing, anyway > ... there's still hyperref:-) ) you obviously haven't looked at passivetex yet > for never having supplied us humble coders with what he claims is = `the > obvious algorithm for float positioning (including spanning floats)'. its from the same family as the Carlisle algorithm for word counting. it goes WHILE it_doesnt_look_nice() continue END implementation of "it_doesnt_look_nice" is in local libraries > 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. one data point you have to consider is "what the picture looks like". it makes a difference whether it is a line diagram or a photograph, for instance, and how dark it looks. I suspect this "floating silver bullet" doesn't exist. Shock, Horror! Was Knuth wrong in his entire initial premise that computers could solve typography? You have to wonder about a man who rates Georges Perec over Patrick O'Brian. Sebastian ------_=_NextPart_001_01BF8870.E5A25900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: On float position rules and forgiveness

Chris Rowley writes:
 >   I forgive Sebastian Rahtz!! = (Well for one thing, anyway
 >         =             &= nbsp;          ... there's = still hyperref:-) )

you obviously haven't looked at passivetex yet

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

its from the same family as the Carlisle algorithm for = word
counting. it goes

WHILE it_doesnt_look_nice()
 continue
END

implementation of "it_doesnt_look_nice" is = in local libraries


 > 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.

one data point you have to consider is "what the = picture looks
like". it makes a difference whether it is a = line diagram or a
photograph, for instance, and how dark it = looks.

I suspect this "floating silver bullet" = doesn't exist.  Shock, Horror!
Was Knuth wrong in his entire initial premise that = computers could
solve typography? You have to wonder about a man who = rates Georges
Perec over Patrick O'Brian.


Sebastian

------_=_NextPart_001_01BF8870.E5A25900--