Received: by nummer-3.proteosys id <01C19443.AA193C4C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:48 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.AA193C4C" 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: Short form citation system Date: Tue, 5 May 1992 14:23:42 +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: 700 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.AA193C4C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Footnotes were mentioned a while back, and I suggested that those = footnotes that are making citations have internal structure. I've had a go at isolating that structure, and how a user-interface = might cope (and help the user to cope) with that structure. You'll get = details in the following 3 mail messages. * I seem to remember that, at the meeting in London about a year ago, someone said " ... macros ... " and someone else said " ... put some comments in the macros ... " and then Rainer said "No. First write the documentation!". In this spirit, the first mail message illustrates how a manual might describe the suggested interface. * The second message is a test file. If you can think of a better user-interface, than the one I've suggested, you might like to use this test file to test your ideas. * The 3rd message is a .sty file that implements some of the commands defined by the first mail message. As the comments say, it is only intended to be good enough to illustrate the suggested interface. = (If anyone does a more elegant version, could they let me have a copy, please?) Main questions: "Would something like the suggested interface do what humanities people want? If not, what would?" David Rhead JANET: d.rhead@uk.ac.nottingham.ccc.vme ------_=_NextPart_001_01C19443.AA193C4C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Short form citation system

Footnotes were mentioned a while back, and I suggested = that those footnotes
that are making citations have internal = structure.

I've had a go at isolating that structure, and how a = user-interface might
cope (and help the user to cope) with that = structure.  You'll get details
in the following 3 mail messages.
*    I seem to remember that, at the = meeting in London about a year ago,
     someone said " = ...  macros ...  " and someone else said " ...  = put
     some comments in the macros = ...  " and then Rainer said "No.  First
     write the = documentation!".  In this spirit, the first mail = message
     illustrates how a manual = might describe the suggested interface.
*    The second message is a test = file.  If you can think of a better
     user-interface, than the one = I've suggested, you might like to use
     this test file to test your = ideas.
*    The 3rd message is a .sty file = that implements some of the commands
     defined by the first mail = message.  As the comments say, it is only
     intended to be good enough = to illustrate the suggested interface.  (If
     anyone does a more elegant = version, could they let me have a copy,
     please?)

Main questions: "Would something like the = suggested interface do what
humanities people want?  If not, what = would?"


David Rhead
JANET: d.rhead@uk.ac.nottingham.ccc.vme

------_=_NextPart_001_01C19443.AA193C4C--