Received: by nummer-3.proteosys id <01C19443.AB061B34@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:49 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.AB061B34" 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 09:49:41 +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: 712 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.AB061B34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > I had a similar objection too, but: I'm not sure if such writing > styles always put the \firstcite first. This is something where I > would invite comment from people more experienced with such styles. = If > we can assume that the ``long form'' of the citation always comes > first and all following citations are ``short'' then an automatic > detection of the first citation should be no major problem. its not easy to think of an example, but I would be unhappy if the user could *not* do an apparently ridiculous forward reference, as in "see LSJ (details in footnote on page 44)". i dont think I'd ever do it myself... > > I don't think that an unstructured ``reflist'' environment is a good > idea since it would be seldom result in consistent layout. I prefer = at > least a starting tag. > 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). slightly less philosophical, but how does one economically implement footnote citations? all the implementations that come to mind (I was trying it last night) involve stuffing the full citation into a macro (which is probably picked up from an external file on second passes etc), which is potentially disastrous for TeX memory. if the expansion of \b@knuth:1987 is a three paragraph essay, we soon have problems. does anyone have any suggestions for managing this sort of thing? the possiblity of one external file for each reference raises its ugly head, or opening and searching a whole file for each citation... sebastian ------_=_NextPart_001_01C19443.AB061B34 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: short citation forms

 > I had a similar objection too, but: I'm not = sure if such writing
 > styles always put the \firstcite first. = This is something where I
 > would invite comment from people more = experienced with such styles. If
 > we can assume that the ``long form'' of = the citation always comes
 > first and all following citations are = ``short'' then an automatic
 > detection of the first citation should be = no major problem.
its not easy to think of an example, but I would be = unhappy if the
user could *not* do an apparently ridiculous forward = reference, as in
"see LSJ (details in footnote on page 44)". = i dont think I'd ever do
it myself...

 >
 > I don't think that an unstructured = ``reflist'' environment is a good
 > idea since it would be seldom result in = consistent layout. I prefer at
 > least a starting tag.
 >
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).

slightly less philosophical, but how does one = economically implement
footnote citations? all the implementations that come = to mind (I was
trying it last night) involve stuffing the full = citation into a macro
(which is probably picked up from an external file on = second passes
etc), which is potentially disastrous for TeX memory. = if the expansion
of \b@knuth:1987 is a three paragraph essay, we soon = have problems.
does anyone have any suggestions for managing this = sort of thing?  the
possiblity of one external file for each reference = raises its ugly
head, or opening and searching a whole file for each = citation...

sebastian



------_=_NextPart_001_01C19443.AB061B34--