X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1493" "Tue" "5" "January" "1999" "10:33:27" "-0500" "Y&Y, Inc." "support@YANDY.COM" nil "40" "Re: Layout parameters in LaTeX" "^Date:" nil nil "1" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id QAA13400; Tue, 5 Jan 1999 16:33:41 +0100 (MET) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <10.9E7CFF66@listserv.gmd.de>; Tue, 5 Jan 1999 16:33:42 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 414321 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 5 Jan 1999 16:33:36 +0100 Received: from mail-out-0.tiac.net (mail-out-0.tiac.net [199.0.65.247]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id QAA18893 for ; Tue, 5 Jan 1999 16:33:34 +0100 (MET) Received: from mail-out-1.tiac.net (mail-out-1.tiac.net [199.0.65.12]) by mail-out-0.tiac.net (8.8.8/8.8.8) with ESMTP id KAA08106 for ; Tue, 5 Jan 1999 10:33:25 -0500 (EST) (envelope-from support@YandY.com) Received: from DENALI (p15.tc10.metro.MA.tiac.com [209.61.77.80]) by mail-out-1.tiac.net (8.8.7/8.8.7) with SMTP id KAA11705 for ; Tue, 5 Jan 1999 10:32:34 -0500 (EST) X-Sender: yandy@pop.tiac.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 References: <199812141041.LAA13591@mozart.ujf-grenoble.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <4.1.19990105102755.033c9900@pop.tiac.net> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199901051451.PAA16364@relay.urz.uni-heidelberg.de> Date: Tue, 5 Jan 1999 10:33:27 -0500 From: "Y&Y, Inc." Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Layout parameters in LaTeX Status: R X-Status: X-Keywords: X-UID: 3239 At 09:50 AM 99/01/05 , Michael J. Downes wrote: >Historically there has not been much leeway to work on such output >routines because two or three complex pages (plus, perhaps, some >pending figures) can use up 256K of main memory and there is no way to >have the output routine check the current memory usage to decide if >there is enough room to consider more material. Lacking such a check, >an output routine that considers two pages or four pages at a time >instead of one is much more likely to create problems by simply >failing in the middle of a job with a fatal TeX out-of-memory error >and leaving an incomplete .dvi file. This particular problem goes away with TeX's that have dynamic memory allocation. >If you want to handle floating objects like footnotes, figures, >tables, the algorithm can easily become infinitely complicated. >I think it would be interesting to try to handle four pages at a time >(two two-page spreads; try to optimize the first one with the ability >to borrow lines from the second one). But I don't think I would want >to go beyond that. Regards, Berthold. By the way Given the rapid increase in computer speed and memory, we will be able to do things for which TeX is even less well suited than what it is being used for now! The dark side of rapid hardware progress is that it makes evolutionary, incremental kludging easier than starting over. Witness MS bloatware. Y&Y, Inc. http://www.YandY.com/news.htm mailto:support@YandY.com