Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Tue, 25 Jan 2000 17:25:58 +0100 (MET) 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 RAA12714 for ; Tue, 25 Jan 2000 17:25:58 +0100 (MET) MIME-Version: 1.0 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 RAA06803 for ; Tue, 25 Jan 2000 17:25:57 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF6750.DC41AF00" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <5.AB4ACE1A@mail.listserv.gmd.de>; Tue, 25 Jan 2000 17:25:42 +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 449540 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 25 Jan 2000 17:24:30 +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 RAA15398 for ; Tue, 25 Jan 2000 17:24:29 +0100 (MET) Received: from sun06.ams.org (sun06.ams.org [130.44.1.6]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id RAA13149 for ; Tue, 25 Jan 2000 17:24:27 +0100 (MET) Received: from sun06.ams.org by sun06.ams.org (PMDF V5.1-10 #27147) id <0FOW00602GB1IV@sun06.ams.org> for LATEX-L@URZ.UNI-HEIDELBERG.DE; Tue, 25 Jan 2000 11:25:49 -0500 (EST) In-Reply-To: Frank Mittelbach's message of Fri, 14 Jan 2000 16:08:42 +0100 Lines: 39 References: <200001141508.QAA00970@istrati.zdv.uni-mainz.de> Return-Path: X-Mailer: Gnus v5.5/Emacs 20.2 x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1694" "Tue" "25" "January" "2000" "11:25:49" "-0500" "Michael J. Downes" "mjd@AMS.ORG" nil "40" "Re: templates for galley (paragraph) formatting" "^Date:" nil nil "1" nil nil nil nil nil]nil) Comments: Originally-From: Michael John Downes Content-class: urn:content-classes:message Subject: Re: templates for galley (paragraph) formatting Date: Tue, 25 Jan 2000 17:25:49 +0100 Message-ID: <200001251624.RAA13149@relay.uni-heidelberg.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Michael J. Downes" 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: 3508 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF6750.DC41AF00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In xhj.dtx: % An interesting question is whether or not such templates should % set (or inhibit) paragraph indentations via a template key. After % all with cutouts on the top left such indentations are usually % not desired.\footnote{Right now only justification templates set % indentation but perhaps they should not, or both should, or what?} In my opinion it is much better to have the parindent in the parshape template, not in the justification template. % justification centerfirst % % This instance centers the first line of a paragraph and sets all % remaining lines as a solid block (including the last line). This Is the first line really the same as the remaining text (i.e. a continuation of the same sentence, rather than a kind of title)?? Strange. There is a related kind of justification problem that is used in AMS publications: if a figure caption is less than one line in length, center it, otherwise use block justification: |-----------------------------------------------------------| Figure 1. A short caption |-----------------------------------------------------------| Figure 2. On the other hand if there is a long caption the first line should not be centered, the whole caption should be full-justified like this. This is hard to handle by only declarative parameter settings. At some level it is necessary to program a test for the length of the text. And in practice there are some esthetic complications: If the caption width is 1.01 of line width, clearly it is better to either leave it on one line (overfull) or else the justification should use something like .9 of linewidth instead of 1.0. ------_=_NextPart_001_01BF6750.DC41AF00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: templates for galley (paragraph) formatting

In xhj.dtx:

%    An interesting question is whether = or not such templates should
%    set (or inhibit) paragraph = indentations via a template key. After
%    all with cutouts on the top left = such indentations are usually
%    not desired.\footnote{Right now = only justification templates set
%    indentation but perhaps they = should not, or both should, or what?}

In my opinion it is much better to have the parindent = in the parshape
template, not in the justification template.

% justification centerfirst
%
%    This instance centers the first = line of a paragraph and sets all
%    remaining lines as a solid block = (including the last line). This

Is the first line really the same as the remaining = text (i.e. a
continuation of the same sentence, rather than a kind = of title)??
Strange.

There is a related kind of justification problem that = is used in AMS
publications: if a figure caption is less than one = line in length,
center it, otherwise use block justification:

  = |-----------------------------------------------------------|
          &nbs= p;       Figure 1. A short caption


  = |-----------------------------------------------------------|
  Figure 2.  On the other hand  if = there is  a long caption the
  first line  should not be centered,  = the whole caption should
  be full-justified like this.

This is hard to handle by only declarative parameter = settings. At some
level it is necessary to program a test for the = length of the text. And
in practice there are some esthetic complications: If = the caption width
is 1.01 of line width, clearly it is better to either = leave it on one
line (overfull) or else the justification should use = something like .9
of linewidth instead of 1.0.

------_=_NextPart_001_01BF6750.DC41AF00--