Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f0A8X6717299 for ; Wed, 10 Jan 2001 09:33:06 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f0A8XN711557 . for ; Wed, 10 Jan 2001 09:33:23 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f0A8X5M18015 for ; Wed, 10 Jan 2001 09:33:05 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C07ADF.F4384D00" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id JAA09694 for ; Wed, 10 Jan 2001 09:33:04 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f0A8X3027807 for ; Wed, 10 Jan 2001 09:33:03 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.CB2E2EFD@mail.listserv.gmd.de>; Wed, 10 Jan 2001 9:33:03 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 478752 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 10 Jan 2001 09:33:01 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id JAA29249 for ; Wed, 10 Jan 2001 09:33:00 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id JAA40240 for ; Wed, 10 Jan 2001 09:32:59 +0100 Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f0A8WxU18222 for ; Wed, 10 Jan 2001 09:32:59 +0100 (MET) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0A8Wwm28928 for ; Wed, 10 Jan 2001 09:32:58 +0100 (MET) Received: from diabolo.Informatik.RWTH-Aachen.DE (diabolo.Informatik.RWTH-Aachen.DE [137.226.53.122]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id JAA24429 for ; Wed, 10 Jan 2001 09:32:58 +0100 (MET) In-Reply-To: <200101051326.OAA02251@mozart.ujf-grenoble.Fr> Return-Path: X-Sender: blume@diabolo.Informatik.RWTH-Aachen.DE x-mime-autoconverted: from QUOTED-PRINTABLE to 8bit by relay.urz.uni-heidelberg.de id JAA29250 Content-class: urn:content-classes:message Subject: Re: templates for page layout Date: Wed, 10 Jan 2001 09:58:01 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Achim Blumensath" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3651 This is a multi-part message in MIME format. ------_=_NextPart_001_01C07ADF.F4384D00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, On Fri, 5 Jan 2001, Thierry Bouche wrote: > =BB The reason you should determine the text width first is that the = width of a > =BB line is very important for how easy a text is to read: if the line = is too > =BB long then it is hard to find the beginning of the next line. > > but designers don't (necessarily) work that way: you usually have the > constraint of the paper format (or choose one in the first place), > then choose the text width/height and adjust type size/leading to > achieve nice text blocks. You can't say like in current standard > classes `i want that font size/leading on that paper' and get a line > length/textheight computed, because you'd adjust the leading depending > on the line length, and the line length (together with type size) > depending on the margins... What set of parameters to specify the layout would you think is most convenient? Achim -- ________________________________________________________________________ | \_____/ = | Achim Blumensath \O/ \___/\ = | Mathematische Grundlagen der Informatik =3Do=3D \ = /\ \| www-mgi.informatik.rwth-aachen.de/~blume /"\ = o----| ____________________________________________________________________\___|= ------_=_NextPart_001_01C07ADF.F4384D00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: templates for page layout

Hello,

On Fri, 5 Jan 2001, Thierry Bouche wrote:
> =BB The reason you should determine the text = width first is that the width of a
> =BB line is very important for how easy a text = is to read: if the line is too
> =BB long then it is hard to find the beginning = of the next line.
>
> but designers don't (necessarily) work that way: = you usually have the
> constraint of the paper format (or choose one in = the first place),
> then choose the text width/height and adjust = type size/leading to
> achieve nice text blocks. You can't say like in = current standard
> classes `i want that font size/leading on that = paper' and get a line
> length/textheight computed, because you'd adjust = the leading depending
> on the line length, and the line length = (together with type size)
> depending on the margins...

What set of parameters to specify the layout would you = think is most
convenient?

Achim
--
________________________________________________________________= ________
          &nbs= p;            = ;            =             &= nbsp;           &n= bsp;  | \_____/ |
   Achim = Blumensath          &nb= sp;           &nbs= p;            = ;       \O/ \___/\ |
   Mathematische Grundlagen der = Informatik          &nb= sp;        =3Do=3D  \ /\ = \|
   = www-mgi.informatik.rwth-aachen.de/~blume     &nb= sp;            = /"\   o----|
________________________________________________________________= ____\___|

------_=_NextPart_001_01C07ADF.F4384D00--