Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 18:28:27 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id n0MHSOot019336 for ; Thu, 22 Jan 2009 18:28:25 +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 n0MHO5Iu005850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Jan 2009 18:24:05 +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 n0MBVUv3006126; Thu, 22 Jan 2009 18:23:52 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 229991 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 22 Jan 2009 18:23:52 +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 n0MHNqfr015710 for ; Thu, 22 Jan 2009 18:23:52 +0100 Received: from web82001.mail.mud.yahoo.com (web82001.mail.mud.yahoo.com [66.163.178.245]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with SMTP id n0MHNfE9005606 for ; Thu, 22 Jan 2009 18:23:42 +0100 Received: (qmail 91638 invoked by uid 60001); 22 Jan 2009 17:23:38 -0000 X-YMail-OSG: n890lXkVM1m9yxMzLOJrf0VPhZ7ro0YZbM9jUkN2faDh1dUG6mZhRMbT4s8LBjGl3Dnl5_ESb2.0GHkRiEfHRUzyEsprbDKPIwdLCbGpLmTBw9nx4rsXoGP5BjZnah4x58vYbnZYqG90tNgWjEWah_xDhDm02ni3IGV25d74J1zkRKy1NaMCvp7VVA-- Received: from [128.252.117.249] by web82001.mail.mud.yahoo.com via HTTP; Thu, 22 Jan 2009 09:23:37 PST X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1 References: <49758499.5080004@morningstar2.co.uk> <150532.45020.qm@web82002.mail.mud.yahoo.com> <49782F88.9090501@morningstar2.co.uk> <18808.14594.895857.730057@morse.mittelbach-online.de> <859ec5630901220603q48bbe1e4kb6043967e3581051@mail.gmail.com> <597382.5271.qm@web82008.mail.mud.yahoo.com> <859ec5630901220712k114d02c9t93c28fc8cd74b662@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id n0MHNqfr015711 Message-ID: <151057.88720.qm@web82001.mail.mud.yahoo.com> Date: Thu, 22 Jan 2009 09:23:37 -0800 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Paul Thompson Subject: Re: changing page dimensions in mid-document (was Re: Key points of LaTex3) To: LATEX-L@LISTSERV.UNI-HEIDELBERG.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.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 22 Jan 2009 17:28:27.0583 (UTC) FILETIME=[D62B64F0:01C97CB6] Status: R X-Status: X-Keywords: X-UID: 5625 ----- Original Message ---- From: Morten Høgholm To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Sent: Thursday, January 22, 2009 9:12:32 AM Subject: Re: changing page dimensions in mid-document (was Re: Key points of LaTex3) On Thu, Jan 22, 2009 at 3:55 PM, Paul Thompson wrote: > Thanks for taking the time to look at newlfm. > > What I do there is 1) set dimensions for Page 1 based on letterhead stuff; 2) at the same time, compute requirements for Page 2-K; 3) store Page 2-K in variables; 4) after shipping out Page Z, reset dimensions to the stored values if stored values are there, and then reset the "change dimension variable" after finishing the change. That's all I need, really. This is fine but not solving the problems Frank is talking about. What happens when a paragraph is broken across two pages with different text widths? ------------------------------------ It would look very cruddy, on Pass 1. If the system were designed to allow this, on Pass 2, the processor would read the information in the .aux file, and adjust things correctly on that page. Since LaTeX is a multi-pass system, many things do not work correctly on the first page, and work more correctly on the second and in some cases on the third pass. If you have ever used longtable, you may have looked at the result of the longtable specification on the first pass, and thought "gee that looks terrible." But then on Pass 2, the dimensions for the table are read in from .aux, and the system corrects the table, and all is well. That sort of thing could be done here. But I am not entirely sure how some of the details would be worked out. In my cases, I have adjusted only text height, not text width. Would you agree that this probably would work OK for height? A final point: In TeX/LaTeX, the philosophy always was to give the user more options, and not fewer. Admittedly, the counter-point is that the philosophy is to make good looking MS, not crappy looking kludges. These are at some level antithetical I agree. My thought is to give the option of doing this, and let the user solve their own problems, that's my thought here. Perhaps they will choose to break the paragraph carefully, or to use a \newpage to force the page. Whatever works, and users would find approaches to solve their own problems, I would guess. This would only be used by people who were beyond simple usage anyway. ------------------------------------ > > Your comment about the calc package is very interesting. I don't understand why it will not work. Can you direct me to something to clarify the problem? With calc loaded \setlength\mylen{1pt+2pt} expands to (after a few steps) \calc@assign@generic\calc@Askip\calc@Bskip \mylen {1pt+2pt} with \calc@assign@generic defined as \def\calc@assign@generic#1#2#3#4{\let\calc@A#1\let\calc@B#2% \calc@open(#4!% \global\calc@A\calc@B\endgroup#3\calc@B} Therefore, \global\setlength results in \calc@A being \let globally to \calc@Askip and \mylen being set locally. -- Morten