Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: xiaofei@acsu.buffalo.edu (Xiaofei Wang)
Newsgroups: comp.text.tex
Subject: Re: TeX preprocessor?
Message-ID: <68480@eerie.acsu.Buffalo.EDU>
Date: 2 Apr 91 23:19:58 GMT
References: <1991Mar30.215707.649@basho.uucp> <7285@emory.mathcs.emory.edu>
Sender: news@acsu.Buffalo.EDU
Organization: SUNY Buffalo
Lines: 21
Nntp-Posting-Host: lictor.acsu.buffalo.edu

* In article <1991Mar30.215707.649@basho.uucp> john@basho.uucp (John Lacey) writes:
* 'I've been thinking about all these macro sets for TeX, and the increasing 
* 'problems in sending documents around as sites lack sets that other possess.
* '
* 'Is there any way to write a TeX file that will process another TeX file 
* 'and reduce it to primitives and then write it out?  I'm thinking of 
* 'something extremely analogous to the C preprocessor.
* 
* A better solution is to have a number of sites for storing widely used macros
* and send along obscure macros along with the text. We already have the
* former (claremont, clarkson, etc). Now if people would do the latter,
* sharing tex/latex files would not be a problem.

I think a better solution is to have a large macro package like EPLAIN.
I think that is the direction that TeX should go. I would like to see
Eplain, Fplain, Gplain, Hplain, Iplain, Jplain, Kplain, Lplain, Mplain ...

Why can not we use TeX and LaTeX together? In one paper, some parts written
by TeX [Plain] and some parts by LaTeX?
-- 
xiaofei@acsu.buffalo.edu / rutgers!ub!xiaofei / v118raqa@ubvms.bitnet