Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Wed, 19 Jan 2000 04:56:18 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mailserver1.zdv.Uni-Mainz.DE (8.9.3+Sun/8.9.1) with ESMTP id EAA14647 for ; Wed, 19 Jan 2000 04:56:17 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF6231.239BDD00" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id EAA04195 for ; Wed, 19 Jan 2000 04:56:13 +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 <3.F1090406@mail.listserv.gmd.de>; Wed, 19 Jan 2000 4:55:59 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 447890 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 19 Jan 2000 04:54:52 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id EAA07843 for ; Wed, 19 Jan 2000 04:54:51 +0100 (MET) Received: from downtown.oche.de (downtown.oche.de [194.94.253.3]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.1) with ESMTP id EAA20653 for ; Wed, 19 Jan 2000 04:54:47 +0100 (MET) Received: from corona.oche.de (uucp@localhost) by downtown.oche.de (8.9.3/8.9.3/Debian/GNU) with UUCP id EAA16939 for URZ.UNI-HEIDELBERG.DE!LATEX-L; Wed, 19 Jan 2000 04:50:00 +0100 Received: by corona.oche.de (wUUCP 1.10) id <1kmc@corona.oche.de>; Tue, 18 Jan 00 21:13:22 CET Return-Path: X-Mailer: AmiGate 1.6 (13.11.95) x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["2432" "Tue" "18" "January" "2000" "21:03:47" "CET" "Achim Blumensath" "blume@CORONA.OCHE.DE" nil "47" "Re: templates for galley (paragraph) formatting" "^Date:" nil nil "1" nil nil nil nil nil]nil) Content-class: urn:content-classes:message Subject: Re: templates for galley (paragraph) formatting Date: Tue, 18 Jan 2000 22:03:47 +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: 3501 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF6231.239BDD00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach wrote: > As promised this is the first installment of templates and code for > galley formatting, the rest will hopefully follow in couple of days. > > I think that this document already serves as a good introduction to = the > high-level aspects of the new galley mechanism and though one can't = make > use of the code without the low-level interfaces I hope that the > documentation will spawn a lively discussion. A lot of issues and > requests for comments are already added into the documentation. Here are my first impressions: o Name of parameters. At the moment the old LaTeX2e names like \hsize, \@totalleftmargin, etc. are used so that old code does still work. IMHO one should introduce new names right from the start while keeping the old versions in addition. Otherwise, you get in trouble when the interface is finally cleaned up since all LaTeX2e* code using the galley package has to be rewritten as well. o pshape template. Perhaps it would be a good idea to add two arguments to the pshape template for the horizontal and vertical dimension (where the exact meaning depends on the template). Say, a template for a rectangular cutout could interpret the horizontal dimension as width of the cotout and the vertical dimension as number of lines to be indented. o hyphenation template. This template should IMHO be dropped. The only important parameters it sets are (ex)hyphenpenalty which can be moved to the linebreak template. o justification template. I'm not quiet sure how the galley templates are intented to be used -- the package only defines the templates themselve no commands to use them. But I think that the justification templates shouldn't be able to choose whether they affect all paragraphs or only the next one. Instead the user should be able to tell the system which case is desired everywhere such a template is used. o As mentioned in the item above, the user-level interface is missing. Achim ________________________________________________________________________ _ | \_____/ = | // Achim Blumensath | \ _ \O/ \___/\ = | // blume@corona.oche.de |-< /_\ =3Do=3D \ = /\ \| \X/ (p^2 - m^2)\psi =3D 0 |_/ \_ /"\ = o----| ____________________________________________________________________\___|= ------_=_NextPart_001_01BF6231.239BDD00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: templates for galley (paragraph) formatting

Frank Mittelbach wrote:
> As promised this is the first installment of = templates and code for
> galley formatting, the rest will hopefully = follow in couple of days.
>
> I think that this document already serves as a = good introduction to the
> high-level aspects of the new galley mechanism = and though one can't make
> use of the code without the low-level interfaces = I hope that the
> documentation will spawn a lively discussion. A = lot of issues and
> requests for comments are already added into the = documentation.

Here are my first impressions:

o Name of parameters. At the moment the old LaTeX2e = names like \hsize,
  \@totalleftmargin, etc. are used so that old = code does still work.
  IMHO one should introduce new names right from = the start while keeping
  the old versions in addition. Otherwise, you = get in trouble when
  the interface is finally cleaned up since all = LaTeX2e* code using the
  galley package has to be rewritten as = well.

o pshape template. Perhaps it would be a good idea to = add two arguments
  to the pshape template for the horizontal and = vertical dimension
  (where the exact meaning depends on the = template). Say, a template
  for a rectangular cutout could interpret the = horizontal dimension
  as width of the cotout and the vertical = dimension as number of lines
  to be indented.

o hyphenation template. This template should IMHO be = dropped. The only
  important parameters it sets are = (ex)hyphenpenalty which can be moved
  to the linebreak template.

o justification template. I'm not quiet sure how the = galley templates
  are intented to be used -- the package only = defines the templates
  themselve no commands to use them. But I think = that the justification
  templates shouldn't be able to choose whether = they affect all
  paragraphs or only the next one. Instead the = user should be able to
  tell the system which case is desired = everywhere such a template is
  used.

o As mentioned in the item above, the user-level = interface is missing.

Achim
________________________________________________________________= ________
          &nbs= p;            = ;         = _            =             &= nbsp;    | \_____/ |
    //  Achim = Blumensath       | \  = _            =             \O/ = \___/\ |
   //   = blume@corona.oche.de   |-< = /_\           &nbs= p;           = =3Do=3D  \ /\ \|
 \X/    (p^2 - m^2)\psi =3D = 0    |_/ = \_            = ;            = /"\   o----|
________________________________________________________________= ____\___|

------_=_NextPart_001_01BF6231.239BDD00--