Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 27 Nov 2007 20:50:15 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id lARJo9MI025746 for ; Tue, 27 Nov 2007 20:50:09 +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 lARJhlc2008827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Nov 2007 20:43: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 lAQN1PjO013778; Tue, 27 Nov 2007 20:45:22 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 197559 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 27 Nov 2007 20:45:22 +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 lARJjMqS032666 for ; Tue, 27 Nov 2007 20:45:22 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id lARJjGf8004431 for ; Tue, 27 Nov 2007 20:45:20 +0100 Received: from morse.mittelbach-online.de (p54A9B5F1.dip0.t-ipconnect.de [84.169.181.241]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1Ix6Mu3nnI-0006gG; Tue, 27 Nov 2007 20:45:17 +0100 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id 626935E70E; Tue, 27 Nov 2007 20:45:16 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <18249.57441.391405.468407@morse.mittelbach-online.de> <008a01c83026$f01a3900$14b2a8c0@DOMINUS> <18250.53690.194331.660833@morse.mittelbach-online.de> <005401c8305d$cf23a290$14b2a8c0@DOMINUS> <18251.16134.90835.686471@morse.mittelbach-online.de> <006a01c830c9$d1352560$14b2a8c0@DOMINUS> <18251.53934.527003.575084@morse.mittelbach-online.de> <008401c83127$c6f994b0$14b2a8c0@DOMINUS> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX18DIe4mnrmc3F00u0mJaVLQjH79ELjbf2jJKLv gQVvp6f3SnkdB7UPKo9kXRaD6uoic7lao/Lzp4VfCkcCoHKe7z 6gjmGhj+GPjX++eR3AbTePnB7spJJbs X-Spam-Whitelist-Provider: Message-ID: <18252.29644.250197.671360@morse.mittelbach-online.de> Date: Tue, 27 Nov 2007 20:45:16 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: Extending the output routine to middle floats To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <008401c83127$c6f994b0$14b2a8c0@DOMINUS> 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: 27 Nov 2007 19:50:15.0624 (UTC) FILETIME=[BB08EC80:01C8312E] Status: R X-Status: X-Keywords: X-UID: 5086 Ulrich Dirr writes: > > > this should be covered by my above definition (text above > > > 16\baselineskip, float area 6\baselineskip, text after > > > 42-(16+6)\baselineskip). > > > > as one possibility for specification (not the actual values but the > > concept: which is fixed starting position with a given vertical size and > > one area only). my question is what others should/could be supported? > > not one area but areas which can be in 0 to n columns with and without > spans. yes sure I should have been more explicit here. I meant more than one area vertically in a single column (or as spans). allowing for several middle columns that use or span different columns is something i though was obvious, eg. just like the current algorithm supports several top areas as long as they don't overlap --- the middle part would support several middle columns as long as they don't overlap (with or without spans). in theory one could probably also make overlapping areas possible (in terms of the columns they use) but then rules for deciding how they are placed would become very difficult to describe). > > > I thought this was what I'd proposed. > > > > yes, I think so, you proposed option 2. But what about: > > > > > > * ...other ideas... > > > > is there any kind of reasonable rule set that is not covered > > by my initial variations and should perhaps be supported as well? > > I don't think so. O.k., maybe we can think of an explicity given > vertical offset which is added or subtracted after each column, e.g. not that i think this would be very attractive other than for some weird magazine layout :-) but in any case it would automatically supported already since you could specify different vertical offsets for each column area individually. > a magazine designer might like this idea to have picture material going > like a sinus wave from page to page ... ;-) Or picture material always > going in the outside column and going down somewhat after each chapter > (like an index thumb). same situation, would work well enough if you really want to, since the new design would allow you to change your float setup (ie which areas to use where and when) so that you could implement something like this changing the positioning after each chapter > I will zap through some design books -- maybe I will find some other > interesting variations. ok, thanks, but it is good to know that essentially so far nobody came up with something radically different and missing. so only remains to make it work (right now it accepts the area but doesn't then place the float :-) frank