TeXhax@cs.washington.edu (TeXhax Digest) (12/09/88)
TeXhax Digest Monday, December 5, 1988 Volume 88 : Issue 106
Moderators: Tiina Modisett and Pierre MacKay
%%% The TeXhax digest is brought to you as a service of the TeX Users Group %%%
%%% in cooperation with the UnixTeX distribution service at the %%%
%%% University of Washington %%%
Today's Topics:
The mailer chaos
Availability of PiCTeX manuals
Height of the minus sign in cmsy fonts
Combining the functions of METAFONT and Postscript
The power of TeX
A macro that allows you to define your own characters (sprite.sty)
Hard TeX-hacking question concerning fitting figures on a page
WEB to C on HP9000/300
TeX 2.94 for VMS
BibTeX 0.99c (a criticism addressed to its author)
Re: BibTeX 0.99c (a response to the above message)
Sharing a Bibtex database
A public domain DVI to ASCII
Previewer for tektronix 4010/4014 wanted
-------------------------------------------------------------------------------
Date: Wed, 7 Dec 88 22:25:04 PST
To: texhax@cs.washington.edu
Subject: The mailer chaos
About three days ago we received an irate communication from
one of the non-BITNET subscribers who was sure that the minor
problems caused by the little network prank at the beginning
of November were all over, and that there was no reason for
the continued erratic delivery of TeXhax. Some of the chaos
is traceable to our own ignorance, and the problems with BITNET
have nothing to do with the attack on 4.3BSD mailers. It still
remains that a large amount of the problem is the "prank," which
a colleague of mine estimates will cost a cool $30,000,000 in
lost time and resources.
It so happens that I was remarking to another colleague about
four hours ago that the really impossible case was the ARPA
domain, from which I was getting bouncing messages at the rate of
nearly half a megabyte per issue, copied into both TeXhax-requests
and into the TeXhax incoming file. I noted that the Mitre corporation
was the source of about half this error message traffic.
This evening I learn that Mitre has been the target of another
copycat attack, but I do not learn this from the mail system--I learn it
from Time Magazine. Time is only interested in the severance of
the link between Milnet and ARPAnet, but it seems pretty clear that
many other links and services have suffered too.
What the hell are we supposed to do? Do we go in and rip out all
Mitre addresses from the mailing list to try and bring the Error
returns down to manageable level? Do we go on spending fifty percent
and more of our time evaluating error returns? Do we wait until
the Error traffic reaches 2 megabytes per issue before acting?
Or 3 Megabytes? Or what?
These are rhetorical questions, and do not expect an answer. There
is no satisfactory answer. But we do appeal once again for your
indulgence and patience until the damage subsides.
Pierre MacKay
-------------------------------------------------------------------------------
Date: Tue, 29 Nov 88 14:13:11 MST
From: bart@cssun.tamu.edu (Bart Childs)
Subject: Availability of PiCTeX manuals
Keywords: PiCTeX
The PiCTeX manuals are printed and available from the TeX Users
Group. They may be ordered from the address given in TeXhax88.100.
Bart Childs
%%Moderator's note: That address is as follows:
%% The TUG Users Group
%% P.O. Box 9506
%% Providence, RI 02940-9506
%% TUG@Math.AMS.COM
------------------------------------------------------------------------------
Date: Wed 23 Nov 88 18:26:30-EST
From: b beeton <BNB@SEED.AMS.COM>
Subject: Height of the minus sign in cmsy fonts
Keywords: fonts
michael barr notes that the height of the minus sign in cmsy10 is
higher than expected, so that an attempt to define \dotminus
(corresponding to doteq) ends up with the dot way too high. having
had trouble with this myself, i queried knuth, and this is his reply:
*** This is INTENTIONAL; many of the arithmetic operators are defined
to have the same height. The reason, among other things, is that
the square root signs should be positioned the same way in
pairs of formulas like $\sqrt{x+y}+\sqrt{x-y}$. If I gave the
minus its "true" height, that wouldn't happen. (Minus signs
also have nonzero depth, matching plus and various other symbols.)
That doesn't mean \dotminus is a bad idea, only that you should
use \smash or something when you define it.
here is my attempt at \dotminus that i find reasonably acceptable:
\def\dotminus{\buildrel\textstyle.\over
{\hbox{\vrule height.55ex width0pt
\smash{\hbox{\mathsurround=0pt$-$}}}}}
-- bb
-------------------------------------------------------------------------------
Date: Thu, 24 Nov 88 9:50:46 EST
From: "David F. Rogers" <dfr@USNA.MIL>
Subject: Combining the functions of METAFONT and Postscript
Keywords: PostScript
Daniel Smith has suggested that it might be a good idea to combine
the functions of METAFONT and PostScript, i.e. to have METAFONT
produce a single outline font and then to dynamically scale it to
achieve other sizes. I see some problems with this.
PostScript uses linear scaling. Proper fonts DO NOT scale linearly -- they
scale nonlinearly. Linear scaling is one of the reasons PostScript fonts are
ugly at certain sizes. As far as I know no one has discovered the correct (or
any for that matter) nonlinear font scaling equations. It is a really
interesting (and hard) problem. (A similar problem exists for clothing
pattern scaling). It's a good PhD topic!
So until someone discovers the nonlinear scaling equations let's keep
METAFONT the way it is. Disk space is really rather cheap.
When using outline fonts, the print engine must perform a polygon (or
outline) fill to generate the `solid' font character. If the outline is
rather general, this is a nontrivial algorithmic problem. It is also
computationally expensive. This is one of the fundamental reasons that
PostScript laser printers are so slow.
I daily use both a Laserwriter Plus and an HP Laserjet Plus for TeX as
well as other printing. I much prefer the Laserjet Plus. It is faster,
gives just as good TeX output, and is considerably cheaper. It can also
be used directly as a printer without having to encode the data using
something like enscript.
If I want to put graphics into the text, I use a really good graphics
device and cut and paste. I'll keep doing that until I get good device
independent graphics within TeX itself. PicTeX is a step in the right
direction but needs to be reduced in size and capability and made faster.
-------------------------------------------------------------------------
Date: Fri, 25 Nov 88 11:26:19 MET
From: Victor Eijkhout <U641000%HNYKUN11.BITNET@Forsythe.Stanford.EDU>
Subject: The power of TeX
Keywords: macros
A small anecdote.
Sometime ago I scooped from the Usenet a file containing jokes of the
form 'how many ... does it take to screw in a lightbulb'. The way
I formatted that file is quite simple, but it managed to
impress some people who didn't know TeX, but
could appreciate the difficulties of doing that in other systems.
Here's the story. As the file contained some 200 jokes,
and I didn't feel like typing even a simple command 200 times,
I needed a way to format it without interspersing the text with
commands. This is what I did.
\newdimen\ix {\setbox0=\hbox{\sl x} \global\ix=\ht0}
\everypar={\everypar={}\lbj}
\def\lbj#1? #2\par{\bigbreak\leavevmode
\vrule width 2cm height \ix depth 0cm \enspace
\sl #1?\par\nobreak \rm #2\par
\everypar={\everypar={}\lbj}}
And here are two sample jokes (I have chosen fairly inoffensive ones :-)
How many evolutionists does it take to screw in a light bulb?
Only one, but it takes eight million years.
How many fatalists does it take to screw in a light bulb?
What does it matter, we're all gonna die anyway.
Isn't TeX wonderful?
Victor Eijkhout
-------------------------------------------------------------------------------
Date: Mon, 28 Nov 88 21:00:14 -0500 (EST)
From: Martin Costabel <mc3i+@andrew.cmu.edu>
Subject: A macro that allows you to define your own characters (sprite.sty)
Keywords: macros, TeX, LaTeX
The following macro file allows you to define your own characters
by simply inserting a dot pattern into your TeX file. It can be used
in plain TeX as well as in LaTeX. A version of sprite.sty which worked
only with LaTeX was published some months ago in TeXMaG. The present
version has been floating around for some time, and since I was
recently asked for it by several people I thought it might be of
interest for the TeXhax community. Two (stupid) examples of
application of sprite.sty follow: spriteuse.tex (for LaTeX) and
spritetest.tex (for plain TeX).
--Martin Costabel "No one needs wysiwyg word processors any more. Now
we can make fuzzy letters in plain TeX."
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% SPRITE.STY ( Martin Costabel 22-Dec-1987 , last changed 28-Nov-1988)
% Use: \documentstyle[...,sprite,...]{...} in LaTeX
% or
% \input sprite.sty in plain TeX
%
% New command:
%
% \sprite{cmd}(lins,cols)[wdth,hght] pxls \endsprite
%
% Here:
% cmd is a command sequence which is afterwards the name of the new object.
% It is defined as \usebox{cmd@box}, so there is also a new box cmd@box.
% wdth and hght are the width and height of the new object.
% pxls is a sequence of lins lines, each of which starts with a `:'(colon),
% ends with a `|'(vertical bar), and contains cols pixels which are
% either a `.'(period, meaning a white pixel) or a `B'(capital B,
% meaning a black pixel). Blank spaces are ignored.
% If lins and cols do not match the actual numbers of lines and columns of
% your dot pattern, the actual width and height of your new object will
% not match wdth and hght.
%
% If you want to create one symbol in different sizes
% without repeating the dot pattern, you can use
% \definepixels{\nameit}{:..BB..| :BB..BB| etc.} and then
% \sprite{\symbolinonesize}(n,6)[wd1,ht1] \nameit \endsprite
% \sprite{\symbolinanothersize}(n,6)[wd2,ht2] \nameit \endsprite etc.
%
\catcode`@=11 \relax
%%% Some code stolen from LATEX.TEX. Can be omitted if used in LaTeX
\def\newbox{\alloc@4\box\chardef\insc@unt}
\def\usebox#1{\leavevmode\copy #1\relax}
\def\@cdr#1#2\@nil{#2}
\def\@ifnextchar#1#2#3{\let\@tempe #1\def\@tempa{#2}\def\@tempb{#3}\futurelet
\@tempc\@ifnch}
\def\@ifnch{\ifx \@tempc \@sptoken \let\@tempd\@xifnch
\else \ifx \@tempc \@tempe\let\@tempd\@tempa\else\let\@tempd\@tempb\fi
\fi \@tempd}
%%% End of stolen code
\newskip{\@pxlwd} \newskip{\@rulewd} \newskip{\@pxlht}
\def\makedotsactive{\catcode`.=\active \catcode`B=\active
\catcode`:=\active \catcode`|=\active}
\def\makedotsinactive{\catcode`.=12 \catcode`B=11 \catcode`:=12
\catcode`|=12\relax}
\makedotsactive
\def\sprite#1(#2,#3)[#4,#5]{
\edef\@sprbox{\expandafter\@cdr\string#1\@nil @box}
\expandafter\newbox\csname\@sprbox\endcsname
\edef#1{\expandafter\usebox\csname\@sprbox\endcsname}
\expandafter\setbox\csname\@sprbox\endcsname =\hbox\bgroup
\vbox\bgroup
\@pxlwd=#4 \divide\@pxlwd by #3 \@rulewd=\@pxlwd
\@pxlht=#5 \divide\@pxlht by #2
\makedotsactive
\def .{\hskip \@pxlwd \ignorespaces}
\def B{\@ifnextchar B{\advance\@rulewd by \@pxlwd}{\vrule
height \@pxlht width \@rulewd depth 0 pt \@rulewd=\@pxlwd}}
\def :{\hbox\bgroup\vrule height \@pxlht
width 0pt depth 0pt\ignorespaces}
\def |{\vrule height \@pxlht width 0pt depth 0pt\egroup
\prevdepth= -1000 pt}
}
\def\endsprite{\egroup\egroup}
\makedotsinactive
%% Idea of \definepixels (doesn't work):
%% \def\definepixels#1#2{\makedotsactive\def#1{#2}\makedotsinactive}
\def\definepixels#1{\makedotsactive\def\read@pixels##1{\def#1{##1}}
\expandafter\makedotsinactive\read@pixels}
\catcode`@=12 \relax
%%% End of sprite.sty %%%%%%%%%%%%%%%%%
%%%%%%%%%%% SPRITEUSE.TEX %%%%%%%%%%%%
%% Example for the use of SPRITE.STY ( Martin Costabel 28-Nov-1988 )
\documentstyle[12pt,sprite]{article}
\begin{document}
\def\schwa{\FormOfSchwa\kern 1 pt} % Only necessary if \kern... is wanted
\sprite{\FormOfSchwa}(16,24)[0.4 em, 1 ex] % Resolution ca. 200x340 dpi.
:.......BBBBBBBBBB....... |
:....BBBB........BBBB.... |
:..BBB.............BBBB.. |
:.BB.................BBB. |
:.B...................BBB |
:.....................BBB |
:.....................BBB |
:.....................BBB |
:BBBBBBBBBBBBBBBBBBBBBBBB |
:BBB..................BBB |
:BBB..................BBB |
:BBB.................BBB. |
:.BBB...............BBB.. |
:..BBBB...........BBBB... |
:....BBBBB.....BBBBB..... |
:.......BBBBBBBB......... |
\endsprite
%% The following shows how to generate a character in different sizes without
%% retyping the dot pattern each time.
%%%%%%%%% define the dot pattern %%%%%%%%%
\definepixels{\PixelsForScriptH}{
:..........BBBBBBBB.............BBB..................BBBBBB....... |
:........BBBB....BBB..........BBBBB..............BBBBBB...BBBB.... |
:........BB.......BBB.......BBB.BBB............BBBBBB.......BBBB.. |
:........BB.......BBB.....BBB..BBBB..........BBBBBB..........BBB.. |
:........BB.......BBB....BB...BBBB.........BBBBBB............BBBB. |
:........BB.......BBB...BB....BBBB.........BBBBB.............BBBB. |
:..................BBBBBB.....BBB.........BBBBB..............BBBB. |
:............................BBBB........BBBBBB..............BBBB. |
:...........................BBBB.........BBBBB...............BBBB. |
:...........................BBBB.........BBBBB...............BBB.. |
:..........................BBBB.........BBBBB...............BBBB.. |
:..........................BBBB.........BBBB...............BBBB... |
:.........................BBBB.........BBBBB..............BBBB.... |
:.........................BBBB.........BBBB..............BBBB..... |
:........................BBBBB.........BBBB............BBBBB...... |
:........................BBBB.........BBBB..........BBBBBB........ |
:.......................BBBBB.........BBBB.....BBBBBBBB........... |
:..........BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB................ |
:.......BBBB...........BBBBB.........BBBB......................... |
:.....BBBB.............BBBBB........BBBBB......................... |
:....BBB...............BBBB.........BBBB.......................... |
:...BB................BBBB.........BBBBB.......................... |
:..BBB...............BBBBB.........BBBB........................... |
:.BBB................BBBB..........BBBB........................... |
:.BBB...............BBBB..........BBBB............................ |
:BBB...............BBBBB..........BBBB..................B......... |
:BBB..............BBBBB...........BBBB.................BB......... |
:BBB.............BBBBB............BBBB................BBB......... |
:BBB............BBBBB..............BBBB..............BBB.......... |
:BBB...........BBBBB................BBBB...........BBBB........... |
:.BBBB........BBBB...................BBBB........BBBB............. |
:...BBB.....BBBB.......................BBBB....BBBBB.............. |
:.....BBBBBBB.............................BBBBBBB................. |
}
%%%%%%% end of dot pattern %%%%%%%%%%
\newsavebox{\CalH} \sbox{\CalH}{${\cal H}$} % Get the size of \cal H.
\sprite{\normalSH}(33,65)[\wd\CalH, \ht\CalH] % The size will be the same
\PixelsForScriptH % as for \cal H.
\endsprite % Resolution ca. 250x500 dpi
%
\newcommand{\ScriptH}% Some fine-tuning of the
{\raisebox{-0.5 pt}{\normalSH}\kern 1 pt}% positioning might be necessary
% some other sizes:
\sprite{\smallSH}(33,65)[0.8\wd\CalH, 0.8\ht\CalH] \PixelsForScriptH \endsprite
\sprite{\bigSH}(33,65)[1.2\wd\CalH, 1.2\ht\CalH] \PixelsForScriptH \endsprite
\sprite{\hugeSH}(33,65)[2\wd\CalH, 2\ht\CalH] \PixelsForScriptH \endsprite
% Now we can use it
\section{Here is a script \protect\hugeSH :} % It is fragile!
You can use it also in Formulas:
$$ H \neq \ScriptH^{\smallSH} \neq {\cal H}$$
And we defined also some kind of Sch\schwa wa.
\newpage
\section{\TeX\ capacity exceeded?}
If you have too many of these on one page, your \TeX\ might give up:
\\ A \smallSH \normalSH \bigSH \hugeSH
%\\ B \schwa
%\\ C \ScriptH \
%D \schwa
%\\ E \ScriptH
%\\ F \schwa \
%G \ScriptH \ etc.
\end{document}
%% End of SPRITEUSE.TEX %%%%%%%%%%%%%%%
%% spritetest.tex %%%%%%%%%%%%
%% Example for the use of SPRITE.STY in plain TeX ( Martin Costabel 19-Nov-1988 )
\input sprite.sty
\magnification 1200\relax
\sprite{\contradiction}(62,25)[8pt,15pt]
:BBBBBBBBBBBBB............|
:BBBBBBBBBBBBB............|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B..................|
:......B...........B......|
:......B..........BB......|
:......B.........B.B......|
:......B........B..B......|
:......B.......BB..B......|
:......B......BB...B......|
:......B.....BB....B......|
:......B....BB.....B......|
:......B...BB......B......|
:......B..BB.......B......|
:......B.BB........B......|
:......B.B.........B......|
:......BB..........B......|
:......B...........B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:..................B......|
:............BBBBBBBBBBBBB|
:............BBBBBBBBBBBBB|
:.............BBBBBBBBBBB.|
:.............BBBBBBBBBBB.|
:..............BBBBBBBBB..|
:..............BBBBBBBBB..|
:...............BBBBBBB...|
:...............BBBBBBB...|
:................BBBBB....|
:................BBBBB....|
:.................BBB.....|
:.................BBB.....|
:..................B......|
:..................B......|
\endsprite
\def\WI{\kern 2pt \raise -6pt \hbox{\contradiction} \kern 2pt}
% Now we can use it
Now there is a contradiction sign:\contradiction
$$ 1=0 \WI$$
\end
%% End of SPRITETEST.TEX %%%%%%%%%%%%
-------------------------------------------------------------------------------
Date: Sat, 26 Nov 88 13:26:28 PST
From: lamport@src.dec.com (Leslie Lamport)
Subject: Hard TeX-hacking question concerning fitting figures on a page
Keywords: LaTeX
I am contemplating a new version of LaTeX, and I need to find out if
it's possible to do something. LaTeX uses the following method to see
if a figure can fit on the current page: it calls the output routine
with a penalty < -10000 and measures the height of the contents of
box255 to determine the approximate vertical position of the text that
appears thus far on the page. The position is approximate because
stretch and shrink are ignored--indeed, the exact position can't be
known until the whole page is ready to be output--but it's good enough
for LaTeX's current needs. However, a feature that I am thinking of
adding requires the ability to determine the exact position. More
precisely, the output routine needs to squirrel away information that,
when the page is ready to be shipped out, will enable it to determine
the exact position. This seems to require being able to determine the
vertical stretch and shrink in the contents of box 255, not just its
natural height and depth. Is there any way to do this?
By the way, the \pagetotal, \pageshrink, \pagestretch, etc. commands
don't seem to help because they pbetween pcallingcinside a lo
Le
DaSubjecKeywor
Has anyserver a
Piet vaPaduaTelep
--
DateFrom: Clark Adrian <alien@ESE.ESSEX.AC.UK>
Subject: TeX 2.94 for VMS
Keywords: TeX, VMS
(I sent a similar message to this a couple of weeks ago, but I guess
it must have ditched in the pond.)
I've upgraded my TeX changes for VMS to support version 2.94 of the
TeX.WEB, adding a few knobs and whistles along the way. The major
features are (cf TUGboat vol 8 no 2):
o interface to the standard VMS editors, TPU, EDT, TECO, etc.,
selected by a logical name. (TPU and EDT are dynamically linked;
other editors are spawned in a sub-process). Automatic cursor
positioning if the editor allows it.
o greatly extended memory, for PiCTeX figures or halftones.
o sensing batch or interactive usage.
o correct handling of an embedded M in the input file (cf TUGboat
vol 9 no 2).
o correct value for |last_text_char|, so that extended (8-bit)
ASCII codes generate errors instead of illegal input, as
described in a recent TeXhax by Chris Thompson. [As an
aside, there is a utility for converting DEC multinational
codes to normal Tex input.]
The complete kit is really too big to send across the Atlantic for
everyone who'd like a copy; is there anyone on the Internet who is
willing to act as a repository? (It will soon be available on the
Aston archive for sites in the UK, Europe, etc.)
I'm also looking for a GNU Emacs hacker who'd be interested in
improving the TeX-Emacs interface under VMS.
Adrian F. Clark
JANET: alien@uk.ac.essex.ese
ARPA: alien%uk.ac.essex.ese@nss.cs.ucl.ac.uk
BITNET: alien%uk.ac.essex.ese@ac.uk
Smail: Dept. of Electronic Systems Engineering, Essex University,
Wivenhoe Park, Colchester, Essex C04 3SQ, U. K.
Phone: (+44) 206-872432 (direct)
-------------------------------------------------------------------------------
Date : November 29, 1988
From : Nico Poppelier (Poppelier@Hutruu51.Bitnet)
Subject: BibTeX 0.99c (a criticism addressed to its author)
Keywords: BibTeX
Recently I started to implement BibTeX 0.99c on the Atari ST using a
Pascal compiler that strictly follows the ISO standard (level 0).
Now, the Pascal Report (see 'Pascal User Manual and Report', third
edition, Springer Verlag, New York 1985) clearly states in section
'12.3 Write', page 196:
> (d) Each write parameter has one of the following forms:
>
> e e:m e:m:n
>
> e represents the value to be ``written'' on f, and m and n are
> so-called field-width parameters. It is an error if either m or
> n is LESS THAN OR EQUAL TO ZERO. ...
(Capitalization is mine)
The BibTeX file contains 39 examples of a field length of 0, which
need to be corrected for adherence to the standard.
Nico Poppelier
Theoretical Nuclear Physics
University of Utrecht
The Netherlands
-----------------------------------------------------------------------------
Date: Tue 29 Nov 88 07:45:31-PST
From: Oren Patashnik <PATASHNIK@Score.Stanford.EDU>
Subject: Re: BibTeX 0.99c (a response to the above message)
Keywords: BibTeX
Thanks for pointing out the nonstandard-`:0' problem. I was unaware
of it previously, but I'll do something reasonable with it for the
next BibTeX update.
--Oren Patashnik
------------------------------------------------------------------------------
Date: Sat, 26 Nov 88 18:36:34 -0500
From: Amitabh Shah <shah@svax.cs.cornell.edu>
Subject: Sharing a Bibtex database
Keywords: BibTeX
Some of us want to share a copy of a Bibtex database. We would like to
allow independent updates to this database (assuming, of course, that
we have agreed upon a common scheme of referencing the database).
Has anyone designed/seen such a system so that this sharing can be
done consistently (no multiple copies etc.) ?
We would ideally like to have a system that when given an entry type
and a reference string for update, would either prompt for appropriate
fields for the entry and insert this entry in sorted form, or would
respond that the entry exists (and show it).
We'd appreciate any pointers.
-amitabh
Amitabh Shah
Dept. of Computer Science
Cornell University.
-----------------------------------------------------------------------------
Date: Mon, 28 Nov 88 16:25:35 EST
From: "Karl Berry." <karl%umb.edu@RELAY.CS.NET>
Subject: A public domain DVI to ASCII
Keywords: dviware
A public domain program to do this came across Usenet recently.
It is called `dvitty', and is written for Unix.
The author is Svant Lindahl, zap@cs.kth.sunet,
seismo!enea!ttds!zap, or enea!ttds!zap@seismo.css.gov, and
apparently he has a Tops-20 version, also.
As I recall, dvidoc forces you to typeset your whole document
in typewriter. That is not really a previewer to me. dvitty
reads any DVI file, and does a very simple-minded job (not that
you can do much more). Also, I do not understand why anyone
thinks GNU's Texinfo system can preview anything; the Texinfo
package is built on top of TeX, and is their documentation format.
It has nothing to do with the output end of TeX.
Karl. karl@umb.edu
----------------------------------------------------------------------------
Date: Wed, 30 Nov 88 17:28:06 CST
From: "W. Scott McCullough" <u2591aa@UNX.UCC.OKSTATE.EDU>
Subject: Previewer for tektronix 4010/4014 wanted
Keywords: previewer
Does anyone have a previewer for tektronix 4010/4014 terminals (or
terminals that emulate a 4010/4014)?
We are running Ultrix on a Microvax II. We have pascal and C compilers
available on our system, but not a modula-2 compiler.
Thanks in advance,
Scott McCullough u2591aa@unx.ucc.okstate.edu (preferred)
Dept. of Physics u2591aa@uccvms.bitnet
Oklahoma State University
Stillwater, OK 74078-0444
405-744-5801
-------------------------------------------------------------------------------
%%% The TeXhax digest is brought to you as a service of the TeX Users Group
%%% in cooperation with the UnixTeX distribution service at the
%%% University of Washington
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%% BITNET: send a one-line mail message to LISTSERV@UWAVM.BITNET
%%% SUBSCRIBE TEXHAX <your name> % to subscribe
%%% or UNSUBSCRIBE TEXHAX <your name>
%%%
%%% All others: send a similar one line mail message to
%%% TeXhax-request@cs.washington.edu
%%% Please be sure you send a valid internet address!!
%%% in the form name@domain or name%routing@domain
%%% and use the style of the Bitnet one-line message, so that
%%% we can find your subscription request easily.
%%%
%%% All submissions to: TeXhax@cs.washington.edu
%%%
%%% Back issues available for FTPing as:
%%% machine: directory: filename:
%%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nn
%%% yy = last two digits of current year
%%% nn = issue number
%%%
%%% Current versions now in general distribution:
%%% TeX 2.93 metafont 1.5
%%% plain.tex 2.92 plain.mf 1.0
%%% LaTeX 2.09 (10/26/88) cmbase.mf see cm85.bug
%%% SliTeX 2.09 gftodvi 1.7
%%% tangle 2.8 gftopk 1.4
%%% weave 2.9 gftype 2.2
%%% dvitype 2.9 pktype 2.2
%%% pltotf 2.3 pktogf 1.0
%%% tftopl 2.5 mft 0.3
%%% bibtex 0.99c
%%%\bye
%%%
End of TeXhax Digest
**************************
-------