Message-Id: <199402161249.AA03541@opal.cs.tu-berlin.de>
Reply-To: Mailing list for the LaTeX3 project <LATEX-L@DHDURZ1.BITNET>
In-Reply-To:  <9402142218.AA02057@ftp.tex.ac.uk>
Date:         Tue, 15 Feb 1994 18:28:37 GMT
From: Sebastian Rahtz <spqr@FTP.TEX.AC.UK>
Sender: Mailing list for the LaTeX3 project <LATEX-L@DHDURZ1.BITNET>
To: Multiple recipients of list LATEX-L <LATEX-L@DHDURZ1.BITNET>
Subject:      Re: collective documents [was exam papers]
Status: R

bbeeton writes:
 > return of the actual file that was published, so that it can be
 > used as the archived documentation).  this file should be capable
 > of being processed all by its lonesome.  and *exactly* the same
 > file should be able to go into the publication stream.  what i
 > really need is a mechanism that will do just that.  i am not sure
sometimes I think we go over the to trying to use TeX for everything;
I think i'd solve your problem in a more amenable programming
language, and do a little pre-processor to carve the top and bottom
off my archival files....

do the LaTeX3 team agree there is an issue here, by the way?

i am getting intrigued now about how to write this enhanced include
which disables the document environment and parses the
\documentclass.. but i'll muse in private

Sebastian