Facilities for chemists: AMSTeX; LaTeX example

Received: by nummer-3.proteosys id <01C19442.D62E32AC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:38:52 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19442.D62E32AC" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Facilities for chemists: AMSTeX; LaTeX example Date: Thu, 25 Oct 1990 15:08:11 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 253 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19442.D62E32AC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Firstly, my apologies to anyone who has had difficulties because of my use of AMSTeX. The AMSTeX I'm using says it's version 1.1c, as of 8th July 1987. But I don't want anyone (including myself) to have to = waste their time trying to change my .tex file or their AMSTeX environment so = that they are compatible. I'll do a .tex file for standard LaTeX 2.09: = you'll lose a nicely labelled arrow (of the sort that Rainer said John Simmie wanted), but should at least be able to get a readable document quickly. Secondly, with reference to Barbara's message, there may be no = difference between what she's suggesting and what I'm suggesting. I sent the long AMSTeX file second and the short LaTeX file third, but I think a mailer somewhere changed the order. So what I thought of as an afterthought may have received undue emphasis because it arrived second when I = thought it would arrive third. Anyway, in the "afterthought", I just intended to show what a chemist might actually do on seeing the current LaTeX manual (before the chemist found that it didn't give him/her what s/he wanted), not to show what I think chemists should do in future. I agree with Barbara that, in an ideal world (to which we are working = with LaTeX 3.0), the user should not use the existing notation: you'll see = that I made some suggestions about an alternative notation "to capture the = logic" in the AMSTeX file. My next message will be a LaTeX equivalent (give or take an arrow) of the AMSTeX file that's been causing the trouble. David Rhead ------_=_NextPart_001_01C19442.D62E32AC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Facilities for chemists: AMSTeX; LaTeX example

Firstly, my apologies to anyone who has had = difficulties because of my
use of AMSTeX. The AMSTeX I'm using says it's = version 1.1c, as of
8th July 1987. But I don't want anyone = (including myself) to have to waste
their time trying to change my .tex file or their = AMSTeX environment so that
they are compatible. I'll do a .tex file for = standard LaTeX 2.09: you'll
lose a nicely labelled arrow (of the sort that Rainer = said John Simmie
wanted), but should at least be able to get a = readable document quickly.

Secondly, with reference to Barbara's message, there = may be no difference
between what she's suggesting and what I'm = suggesting. I sent the long
AMSTeX file second and the short LaTeX file third, = but I think a mailer
somewhere changed the order. So what I thought = of as an afterthought
may have received undue emphasis because it arrived = second when I thought
it would arrive third. Anyway, in the = "afterthought", I just intended
to show what a chemist might actually do on seeing = the current LaTeX
manual (before the chemist found that it didn't give = him/her what s/he
wanted), not to show what I think chemists should do = in future.
I agree with Barbara that, in an ideal world (to = which we are working with
LaTeX 3.0), the user should not use the existing = notation: you'll see that
I made some suggestions about an alternative notation = "to capture the logic"
in the AMSTeX file.

My next message will be a LaTeX equivalent (give or = take an arrow)
of the AMSTeX file that's been causing the = trouble.

&nbs= p; = ; = &= nbsp; &n= bsp; David Rhead

------_=_NextPart_001_01C19442.D62E32AC--