Xref: utzoo comp.sys.mac:55383 comp.text:6946
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!aero!aerospace.aero.org!doner
From: doner@aerospace.aero.org (John Doner)
Newsgroups: comp.sys.mac,comp.text
Subject: Re: (La)TeX on a Mac II
Message-ID: <75637@aerospace.AERO.ORG>
Date: 14 Jun 90 22:16:17 GMT
References: <1990Jun14.161822.27583@cec1.wustl.edu>
Sender: news@aerospace.aero.org
Reply-To: doner@antares.UUCP (John Doner)
Followup-To: comp.sys.mac
Organization: The Aerospace Corporation, El Segundo, CA
Lines: 34

In article <1990Jun14.161822.27583@cec1.wustl.edu> mjt@hyperion.wustl.edu (Mike Turmon) writes:
>What versions of LaTeX are available, either commercial software
>or public domain, for a Mac II?

There's OzTeX (public domain) and TeXtures ($400-$500, unless you can buy
at some University bookstores for $129 or so). Both are complete TeX
implementations.  TeXtures is better from the user's point of view, having
an especially good preview features and convenient facilities for including
pictures.  LaTex is available for either one.  For the most part, you can
run the usual Latex macros; the only thing that may require special action
is the special fonts that come with Latex.  It's possible to convert .pk
files to Macintosh format, and you can also get them from the vendors of
TeXtures.  Quite possibly, you won't care about those fonts, in which case
you can run Latex without modification.

>Do they offer an editor that is
>tailored to the LaTeX environment?

Well....With OzTex, you have to use some other text editor of your choice.
TeXtures has an integrated editor, tailored to the TeX environment.  It is
not as good as the Emacs TeX mode, but it's close.

>Do they offer a previewer?

Yes.

>Can the pool size of that brand of TeX be enlarged to allow very 
>complicated pages to be composed?

I have composed very complex pages with TeXtures, and have never needed to
enlarge anything.  However, I *have* had the experience of exhausting the
hash table size, due to too many control sequence names.  This occurred
after loading AmSTeX, LamSTeX in full, the LamSTeX paper style, and then my
own file of several hundred macros.