Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Nov 2007 13:36:10 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id lAQCa4EO020952 for ; Mon, 26 Nov 2007 13:36:04 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id lAQCUl51030305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Nov 2007 13:30:47 +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 lAPN198h013444; Mon, 26 Nov 2007 13:30:43 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 199765 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 26 Nov 2007 13:30:43 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id lAQCKhkx009696 for ; Mon, 26 Nov 2007 13:20:43 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id lAQCKbjK013437 for ; Mon, 26 Nov 2007 13:20:41 +0100 Received: from DOMINUS (p5B0CE55D.dip.t-dialin.net [91.12.229.93]) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis) id 0ML29c-1Iwcx33V5I-0005BG; Mon, 26 Nov 2007 13:20:38 +0100 References: <18249.57441.391405.468407@morse.mittelbach-online.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Thread-Index: AcgvpWH6TI8A4V19TSSHMPgFUD+99wAfS+kg X-Provags-ID: V01U2FsdGVkX1/UHI7YmKUkRyl/Rngxz5MggYXJXj9QMMMhG0Y WvXRgFAaLZpOUvsXWcxaMBpvx61RWfKsDms8xCKeNYfUB5TsdU X8RpgOOsk3tk0f/CSx/h9vYeQWUl/q5 X-Spam-Whitelist-Provider: Message-ID: <008a01c83026$f01a3900$14b2a8c0@DOMINUS> Date: Mon, 26 Nov 2007 13:21:56 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Ulrich Dirr Organization: Art & Satz Subject: Re: Extending the output routine to middle floats To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <18249.57441.391405.468407@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 26 Nov 2007 12:36:12.0952 (UTC) FILETIME=[EDFAC980:01C83028] Status: R X-Status: X-Keywords: X-UID: 5077 Hi, in my opinion middle floats always float ;-) "Middle" floats could float from the column top to the column bottom; if there's room left before or after one should apply the standard orphan/widow rules (but if a designer wants a fixed middle placement one should have an option like the absolute placement for top and bottom position). They can be of different size and therefore I don't think there is a algorithm that will satisfy all possible combinations automatically. As said there should be a possibility for a fixed position on the page, e.g., on top or bottom or both (wether in single column mode or more) and maybe even in combination with column number, e.g., left column, middle, right (or one, two, three, ...) -- In this case I would like to have an option to place some text at the original position when the float has been moved. > To state the problem differently, what should be the amount of freedom > available to the designer (through the algorithm), and what would be a good > way to express it? No restrictions! > Questions: > > * What kind of other specs can you think of? for fixed positions: [col=1, pos=, col=2, pos=, col=3, pos=, ...] or even [col=1, pos=absolute(10cm), ...], [col=1, pos=absolute(10\baselineskip), ...], or [col=1, pos=(10\baselineskip), ...] otherwise real floats with optional preferences where to float: [pos=, text=] Plus an option for maximum numbers of floats per column, plus an option for vsize of floats. The biggest problem is how to manually adjust bad page makeup ... Ulrich