Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Fri, 11 Jan 2008 11:03:22 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m0BA3Cko016192 for ; Fri, 11 Jan 2008 11:03:13 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m0B9t5oI003365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Jan 2008 10:55:05 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m0AN1SZH008600; Fri, 11 Jan 2008 10:57:51 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 254378 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 11 Jan 2008 10:57:51 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m0B9vpgR027562 for ; Fri, 11 Jan 2008 10:57:51 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m0B9sk37002882 for ; Fri, 11 Jan 2008 10:54:50 +0100 Received: from morse.mittelbach-online.de (p4FD463C8.dip.t-dialin.net [79.212.99.200]) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis) id 0MKwh2-1JDGe126XP-0005pR; Fri, 11 Jan 2008 10:57:45 +0100 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id B196162023; Fri, 11 Jan 2008 10:57:43 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX19UjMDvIA9CCbm/cov4r3IFCtUMTx+3CPK9VKQ ySXwWPxhyPhQtKvCuaDSFZ8nXtZ7Cp8M6iqam5XLtLArO9NLWc rwg+OXSytFhiGT6bqf7aBg3M+/bxvWV X-Spam-Whitelist-Provider: Message-ID: <18311.15767.694736.417577@morse.mittelbach-online.de> Date: Fri, 11 Jan 2008 10:57:43 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: external float position logic for xor To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -102.464 () BAYES_00,FORGED_RCVD_HELO,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 11 Jan 2008 10:03:23.0027 (UTC) FILETIME=[3347C630:01C85439] Status: R X-Status: X-Keywords: X-UID: 5151 over the holiday break I reimplemented part of the xor float handling so that external float control is working again. if somebody wants to try, the documentation in xo-pfloat is correct but in a nutshell it works as follows: - specifying \savefloatplacement will write a file \jobname.fpl listing all float areas for each page and which floats went into them. - specify \readfloatplacment will attempt to read float placments from a file \jobname.fpc so if you copy the .fpl to .fpc you can then change the placements by simply moving the floats listed there from one area to another. if the fpc file is not complete, eg has only specs for a number of pages, then the algorithm reverts back to placing the remaining floats on its own. saying it differently: if you start doing explicit placments this way you have to do the placements starting with the fist page up to a certain page in the document. right now you can't do placements only for a certain page somewhere within the document and to be honest i'm not so sure that this would be really such a good idea anyway since the chances are high that intermediate automatic placements would invalidate the fixed ones very often another restriction is that since the floats are inside the document the placement spec will not work if you move the float to a position earlier than it is actually seen in the document. in that case you would need to put the float earlier in the document as well. a good document to play around with the possibilities might be xo-sample.tex there are certainly quite a number of ways in which such a scheme could be extended and improved. the question is which are most valuable? any suggestions and comments welcome. cheers frank