MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <pc910inkm2.fsf@epsilon.ams.org>
            <199706110929.KAA19914@lochnagarn.elsevier.co.uk>
            <199706110956.TAA01247@flash.anu.edu.au>
            <199706111026.LAA24123@lochnagarn.elsevier.co.uk>
Message-ID:  <199706111103.VAA01304@flash.anu.edu.au>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <199706111026.LAA24123@lochnagarn.elsevier.co.uk>
Date:         Wed, 11 Jun 1997 21:03:06 +1000
From: Richard Walker <Richard.Walker@CS.ANU.EDU.AU>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
Subject:      Re: automatic numbering
Status: R

Sebastian Rahtz writes:
 > no, i was serious for once.

I had a sneaking suspicion this was the case, but I was too scared
to admit it to myself!

 > TeX is ok, in this context, but once we go
 > outside that, its C++ or Java, please. If Phil Taylor is listening and
 > says `WEB!' I shall scream (silently)

I was going to mention the W word but I thought I had better keep
quiet.

At the moment, Java is a moving target.  I would rather ISO standard C
than a flavour of C++.  Anyway, we're getting sidetracked . . . .

 > what do you have in mind? N articles being combined into one journal
 > issue? Robin Fairbairns was working on that for TUGboat, and
 > Matt (where is he now?) Swift discussed in some detail a few years
 > ago.

Yes, that's what I had in mind.  I think that is the `bigger issue'
here.  Getting page numbers etc. right is just a `symptom' of a bigger
`disease'.

 > Elsevier, for what its worth, combines articles at the printing level:-}

I'm surprised.  A pity.  We should be able to do much better.
MS Word (for instance) may not do this sort of thing much better, but
it does it better.  A challenge to us all!