Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Thu, 7 Feb 2008 17:27:45 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m17GRi8q007057 for ; Thu, 7 Feb 2008 17:27:44 +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 m17GHPFs009168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Feb 2008 17:17:26 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m16N1fqP017471; Thu, 7 Feb 2008 17:21:06 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 211020 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 7 Feb 2008 17:21:05 +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 m17GL5hJ004811 for ; Thu, 7 Feb 2008 17:21:05 +0100 Received: from freebsd1.webcows.se (217198149020-host.dependit.net [217.198.149.20]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m17GH12U008853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 7 Feb 2008 17:17:05 +0100 Received: from h115n5c1o260.bredband.skanova.com ([81.231.36.115] helo=[192.168.0.179]) by freebsd1.webcows.se with esmtpa (Exim 4.64 (FreeBSD)) (envelope-from ) id 1JN7eh-000ECZ-KK for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 07 Feb 2008 15:23:11 +0100 Mime-Version: 1.0 (Apple Message framework v624) References: <18314.23356.700357.114633@morse.mittelbach-online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Mailer: Apple Mail (2.624) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - freebsd1.webcows.se X-AntiAbuse: Original Domain - listserv.uni-heidelberg.de X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - residenset.net Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id m17GL5hJ004812 Message-ID: <2260810e0ae758b589dd974b228eb2ea@residenset.net> Date: Thu, 7 Feb 2008 15:23:10 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?ISO-8859-1?Q?Lars_Hellstr=F6m?= Subject: Re: Internal and external page setup control To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <18314.23356.700357.114633@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.464 () BAYES_00,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 07 Feb 2008 16:27:45.0780 (UTC) FILETIME=[5EE7DB40:01C869A6] Status: R X-Status: X-Keywords: X-UID: 5157 13 jan 2008 kl. 19.41 skrev Frank Mittelbach: > I'm having a bit of trouble to find a good way to specify internal or > external > page setup control. In LaTeX2e this concept only exists in some > rudimentary > form, i.e., it is possible to influence that page style as far as > running > headings are concerned by placing a \pagestyle or \thispagestyle > command in > the source but that's about all that is available. [snip] > What I'm looking for for the new output routine is to be able to > change, for > example, the area specifications for the current or the following > pages. The > tricky part is: how should this be specified and when should it act? > > If it works like \thispagestyle, i.e., is intended to act on the > "current" > page then this might result in the following problem: > > * Some such directive would be picked up when gathering material > and would > change, say, which float areas are allowed on the current page. > But then > adding floats to these areas the point with the directive might > get > pushed out of the current page (since each float takes away > space from > the galley). As a result all the placements done may no longer be > valid. Maybe a stupid question (however any reply might be better than no reply), but would it help to use \marks for communicating this kind of settings to the output routine? Parts of what you've written seems to indicate there is the kind of sensitivity to position in vertical material that marks would provide, but OTOH grepping in xpackages/xor/ doesn't turn up anything to indicate that marks are being used for anything but running head contents and the like. Lars Hellström