Received: by nummer-3.proteosys id <01C19443.AB84F25C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:50 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.AB84F25C" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Re: short citation forms Date: Tue, 12 May 1992 12:26:12 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "Mailing list for the LaTeX3 project" To: "Rainer M. Schoepf" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 714 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.AB84F25C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > Let me argue against this one; in maany recent documents, I have > implemented > \Begin {list} ... \End {list}, with the implicit semantics that one > paragraph =3D one item. Much more elegant markup (i.e. tacit markup > rather than explicit), and, when, just occasionally, I needed items > that spanned paragraphs, I implemented \Begin {list} \options =3D > {\spansparagraphs} ... \End {list}, which then required the use of > \Item. you'd be at home in the SGML lists, Phil. i think the overriding thing *is* to use explicit markup, so that items start with \item, and let people who are clever enough redefine \par to start a new item. "\options=3D{spansparagraphs}" indeed!! s ------_=_NextPart_001_01C19443.AB84F25C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: short citation forms

> Let me argue against this one; in maany recent = documents, I have
> implemented
 > \Begin {list} ... \End {list}, with the = implicit semantics that one
 > paragraph =3D one item.  Much more = elegant markup (i.e. tacit markup
 > rather than explicit), and, when, just = occasionally, I needed items
 > that spanned paragraphs, I implemented = \Begin {list} \options =3D
 > {\spansparagraphs} ... \End {list}, which = then required the use of
 > \Item.
you'd be at home in the SGML lists, Phil. i think the = overriding thing
*is* to use explicit markup, so that items start with = \item, and let
people who are clever enough redefine \par to start a = new item.
"\options=3D{spansparagraphs}" = indeed!!

s


------_=_NextPart_001_01C19443.AB84F25C--