Received: by nummer-3.proteosys id <01C19443.AB5719CC@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.AB5719CC" 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 13:31:08 +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: 715 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.AB5719CC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >>> this was the most obvious thing that struck me in Rhead's example. I >>> hated the \begin{reflist} and then a set of blank-line separated >>> entries. please, lets keep the traditional \item! an entry could >>> *easily* have a second paragraph (abstract, for instance). 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. ** Phil. ------_=_NextPart_001_01C19443.AB5719CC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: short citation forms

>>> this was the most obvious thing that = struck me in Rhead's example. I
>>> hated the \begin{reflist} and then a set = of blank-line separated
>>> entries. please, lets keep the = traditional \item! an entry could
>>> *easily* have a second paragraph = (abstract, for instance).

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.

        =         =         =         =         ** = Phil.

------_=_NextPart_001_01C19443.AB5719CC--