Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Sat, 29 Jan 2000 13:19:52 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA18350 for ; Sat, 29 Jan 2000 13:19:52 +0100 (MET) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA28311 for ; Sat, 29 Jan 2000 13:19:51 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF6A53.24AFE400" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.F418776E@mail.listserv.gmd.de>; Sat, 29 Jan 2000 13:19:36 +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 448575 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sat, 29 Jan 2000 13:18:22 +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 NAA17511 for ; Sat, 29 Jan 2000 13:16:32 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id NAA18929 for ; Sat, 29 Jan 2000 13:16:34 +0100 (MET) Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA28251 for ; Sat, 29 Jan 2000 13:17:59 +0100 (MET) Received: from istrati.zdv.uni-mainz.de (root@dialin334.zdv.Uni-Mainz.DE [134.93.175.34]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id NAA18168 for ; Sat, 29 Jan 2000 13:17:57 +0100 (MET) Received: (from design@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3) id NAA00579; Sat, 29 Jan 2000 13:05:02 +0100 In-Reply-To: References: Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1331" "Sat" "29" "January" "2000" "13:05:02" "+0100" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "41" "Re: headed paragraphs" "^Date:" nil nil "1" nil nil nil nil nil]nil) X-Authentication-Warning: istrati.zdv.uni-mainz.de: design set sender to design@istrati.zdv.uni-mainz.de using -f Content-class: urn:content-classes:message Subject: Re: headed paragraphs Date: Sat, 29 Jan 2000 13:05:02 +0100 Message-ID: <200001291205.NAA00579@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3523 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF6A53.24AFE400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Achim Blumensath writes: > > reading about paragraph formatting I had the idea for a template for > "headed paragraphs". they are on my lists of things to provide for as well (and no, not = implemented either yet :-) > The template takes an argument containing the text of the head, > typesets it, and prepares the paragraph formatting. In my opinion the template type for this should take not one but three arguments: arg1: A number (or comparable) or \NoValue denoting that this headed = para is unnumbered arg2: The title (required) ie the main title text of the headed para arg3: A subtitle or \NoValue. those three arguments very often go together so it seems sensible to me = to provide for them in the template type. arg3 in case of theorem could be = the optional note, in case of headings it could be a subtitle text or a = motto (that is not supported by current LaTeX but nevertheless ...) the reason to keep arg1 and arg2 separate (they could of course be = passed as a single argument) is that often the two get different treatment (eg = special space between them, order swapped, new line and vertical space between = them, etc etc) does this make sense to you? > Any comments? go ahead and implement some :-) frank ps needs a good name for the template type as well: headedpara looks = horrible to me ------_=_NextPart_001_01BF6A53.24AFE400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: headed paragraphs

Achim Blumensath writes:
 >
 > reading about paragraph formatting I had = the idea for a template for
 > "headed paragraphs".

they are on my lists of things to provide for as well = (and no, not implemented
either yet :-)

 > The template takes an argument containing = the text of the head,
 > typesets it, and prepares the paragraph = formatting.

In my opinion the template type for this should take = not one but three
arguments:

  arg1: A number (or comparable) or \NoValue = denoting that this headed para is
        = unnumbered

  arg2: The title (required) ie the main title = text of the headed para

  arg3: A subtitle or \NoValue.

those three arguments very often go together so it = seems sensible to me to
provide for them in the template type. arg3 in case = of theorem could be the
optional note, in case of headings it could be a = subtitle text or a motto
(that is not supported by current LaTeX but = nevertheless ...)

the reason to keep arg1 and arg2 separate (they could = of course be passed as a
single argument) is that often the two get different = treatment (eg special
space between them, order swapped, new line and = vertical space between them,
etc etc)

does this make sense to you?

 > Any comments?

go ahead and implement some :-)

frank

ps needs a good name for the template type as well: = headedpara looks horrible
to me

------_=_NextPart_001_01BF6A53.24AFE400--