TeXhax@cs.washington.edu (TeXhax Digest) (06/16/89)
TeXhax Digest Monday, May 15, 1989 Volume 89 : Issue 50
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:
How should one install AMS fonts in Arbor Tex Preview?
AMS Preprint style
Re: tree formatter
Needed: TIB for VAX/VMS
Re: PostScript file being too large
Re: 1200 dpi PostScript Linotype
Problem using PSPRINT shareware to print .DVI files
Re: \uppercase\ss problem (V89 #39)
Re: \makeatletter, \makeatother
Re: What is \everycr all about?
Sans Serif LaTeX section headings
Smart acronym macro
MacDraw & psfig
Help on including MacDraw files in LaTeX
-------------------------------------------------------------------------------
Date: Fri, 12 May 89 17:47:22 +0300
From: Michael Maschler <MASCHLA%HBUNOS.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: How should one install AMS fonts in Arbor Tex Preview?
Keywords: AMS, Arbor TeX
Recently we received new AMS Screen Fonts, which we wanted to
install in Arbor Tex Preview that we are using. According to the
instructions we used PKtoPX in order to change the format to .PXL.
We then loaded the fonts into the PIXELFILES in the proper subdirectories,
namely subdirectories whose number are five times the dpi number.
Unfortunately, Preview could not open the new font-files when it
was called to do so by the dvi file.
I wonder what was our mistake, and, more importantly, how should one
install new fonts in ArborTex Preview.
Please answer me directly, because this problem is quite urgent for us.
Thanks in advance,
Michael Maschler
---------------------------------------------------------------------------
Date: Wed, 10 May 89 14:09:03 CDT
From: Cliff Bergman <@CCVAX.IASTATE.EDU:S2.CHB@ISUMVS.BITNET>
Subject: AMS Preprint style
Keywords: AMS preprint style
2 remarks on the AMS preprint style
1. The \tenpoint and \eightpoint macros are missing the definitions of the
Euler Fraktur fonts. This can make an abstract look pretty funny if it
uses those symbols.
To the \tenpoint macro add the lines:
\textfont\euffam=\teneuf
\scriptfont\euffam=\seveneuf
\scriptscriptfont\euffam=\fiveeuf
Similarly, to the \eightpoint macro, add:
\textfont\euffam=\eighteuf
\scriptfont\euffam=\sixeuf
\scriptscriptfont\euffam=\fiveeuf
Also, you must define \eighteuf and \sixeuf. Add the lines
\font@\nineeuf=eufm9
\font@\eighteuf=eufm8
\font@\sixeuf=eufm6
starting at line 37 (in my copy). Actually, eufm9 doesn't seem to be used
anywhere, so you might want to leave it out.
Naturally, you should not do this if you do not have the Euler Fraktur fonts
available.
2. I have noticed that LaTeX sets \tolerance to 10000 when setting
bibliographies. The AMS preprint style does not do this. It seems to me
that it should. After all, you can not very well rewrite a bibliographic
entry to eliminate a bad break.
-----------------------------------------------------------------------
Date: Fri, 12 May 89 11:29 N
From: <GENT%HTIKUB5.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: tree formatter
Keywords: tree formatting, linguistic theories
(Reply to question of -paul(?) about formatting tree structures that are
used in documents on linguistic theories.)
I have been trying to solve this problem about a year ago.
After shaking my brains doing the job in LaTeX I decided to make an
'external' program that would convert ascii-files into LaTeX source
files (picture environment). This program PICT (in VAX PASCAL) turned out to
work really perfect and very quickly. It can make complex tree structures,
flowcharts and tables in as much time as you need typing it in plain ascii.
If you are interested in this way of formatting your tree structures
please contact me:
Joop van Gent
Institute for Language Tecnology and
Artificial Intelligence, Holland
GENT@HTIKUB5 (EARN)
----------------------------------------------------------------------------
Date: Wed, 10 May 89 22:40:09 mdt
From: flatau@excell.CS.ColoState.Edu (flatau)
Subject: Needed: TIB for VAX/VMS
Keywords: TIB, VAX/VMS
I would like to try TIB bibliography program on VAX/VMS.
Is there anybody out there who implemented TIB on VMS?
P. Flatau
flatau@handel.colostate.edu
------------------------------------------------------------------------------
Date: Fri, 12 May 89 07:26:46 -0700
From: Tomas G. Rokicki <rokicki@polya.Stanford.EDU>
Subject: Re: PostScript file being too large
Keywords: PostScript,TeX
edwards@dogie.macc.wisc.edu (mark edwards) writes:
> We are thinking about using a Linotronic at a commercial organization. One
> of the packages we want to use with it is TeX.
> I do have a dvi2ps program, however to use all TeX's math fonts it is
> necessary to use CM bitmapped fonts, because postscript does not support all
> TeX's math characters. The problem is that the bitmapped fonts for the
> Lintronic have to be made at 1270 dpi. For cmr10 at 10pt this translates
> into a pxl file of 165k, cmr12 is 225k. In short when using these fonts
> the postscript file created can be quite large. The kicker here is that
> we may be transferring the file over a 2400 baud modem.
And the PostScript file will be at least twice as large, with hex data!
There is a solution. Pick up a copy of dvips 3.0 from
labrea.stanford.edu:pub/drivel.tar.Z. Use it with the -Z option. This
will `compress' the character bitmaps and download the magic PostScript
to decompress the characters as they are needed. Typically these
compressed bitmaps at 1270 dpi are only slightly larger than uncompressed
bitmaps at 300 dpi.
Things run pretty quickly, too, despite what you'd think.
The *real* problem with the Linotronic 100 is how abysmally short of
memory it is---180K free VM is usual. (The Lino 300, in its normal
unexpanded state, is even worse, with only 130K.) You *need* to use
such a compression scheme to be able to use bitmap fonts at all
effectively in that printer.
I have printed extremely complex pages with over a dozen fonts on each
page and tall characters (cminch, for example) on a Linotronic 100
using this version of dvips . . .
This version of dvips also does accurate memory budgeting, automatically
splitting the document up between save/restores as necessary to allow
it to run under a given amount of VM. It also supports PostScript fonts
(use them whenever possible to save even more memory in the printer.)
And graphics. And more.
tom
-------------------------------------------------------------------------------
Date: Wed,10 May 17:52:04 1989
From: Mario Wolczko <mario%research7.computer-science.manchester.ac.uk@NSFnet-Relay.AC.UK>
Subject: Re: 1200 dpi PostScript Linotype
Keywords: PostScript, Linotype
> Our group of TeX/LaTeX users has been using 300 dpi laser printers for a long
> time. Now we want to see important stuff printed on our 1200 dpi Linotype
> typesetter than speaks only PostScript, as far as we know. I can think of
> four ways to do it:
[stuff about three other ways removed]
> Come up with the font metrics for the standard PostScript fonts and use them.
> This would probably require a PostScript plain.tex and lplain.tex that would
> make DVI files that can only be printed on PostScript printers and would not
> look like documents that use the TeX fonts. I've heard rumors that this has
> been done. Would anyone care to substantiate same?
I have indeed done just such a thing. The modified version of LaTeX,
which I call PS-LaTeX, uses Adobe fonts where possible. CMEX, CMSY
and CMMI are required for some of the maths, as the Adobe fonts are
lacking a few symbols.
The modified macro files, and documentation, can be found on the
Clarkson server, or the Aston server. You'll need TFMs for the Adobe
fonts (a set is on Aston, there are others around), and a
DVI->PostScript converter that can deal with Adobe fonts (again, one
is on Aston). If you want any of these, but can't get hold of them,
mail me.
Mario Wolczko
______ Dept. of Computer Science Internet: mario@ux.cs.man.ac.uk
/~ ~\ The University USENET: mcvax!ukc!man.cs.ux!mario
( __ ) Manchester M13 9PL JANET: mario@uk.ac.man.cs.ux
`-': :`-' U.K. Tel: +44-61-275 6146 (FAX: 6280)
%____; ;_____________the mushroom project____________________________________
------------------------------------------------------------------------------
Date: Wed, 10 May 89 10:34 PST
From: <MIKE%UCDHEP.BITNET@UWAVM.ACS.WASHINGTON.EDU> (Mike Hannon; UCD Physics; [916]-752-4966)
Subject: Problem using PSPRINT shareware to print .DVI files
Keywords: PSPRINT, dvi2ps
Executive summary
=================
This is a question about the PSPRINT program, a shareware program used on
VMS systems for converting .DVI files to Postscript files.
Background
==========
We have TeX V2.93 running on a VAX 8600 under VMS 4.7A. We obtained the
distribution from Northlake Software (formerly part of Kellerman & Smith).
Part of the distribution is ``contributed'' software, including a PSPRINT
program, written in Modula-2 by Andrew Trevorrow, which was originally written
to print text, Postscript, and .DVI files on an Apple LaserWriter. PSPRINT
invokes a translator program, PSDVI, to convert .DVI files to Postscript.
We require the translation to Postscript, because we have two DEC LN03R
``Scriptprinters'' (Ricoh engine). The print queue for the first printer
is set up with some auxillary, DEC-supplied Scriptprinter software, including
a print symbiont and various format translators. The PSPRINT command works
exactly as advertised with this setup.
For technical reasons, the second print queue cannot use that auxillary
DEC software. This would seem not to be a terrible problem, because the
original use of PSPRINT did not assume any such software (or even a DEC
printer).
The problem
===========
But we canNOT use PSPRINT to print TeX, i.e., .DVI, files on the second
print queue. We get only a single page which says OPERAND STACK at the
top, followed by a single line which says "-mark-", and NOTHING else.
Plain text files print just fine. I also typed in a simple Postscript program
(the "A Box" example from page 49 of the Tutorial & Cookbook). PSPRINT
printed that without any difficulty also.
This all leads me to think that this can't be a large problem, but it certainly
has been a persistent problem. Any help, hints, words of wisdom, etc.,
will be greatly appreciated.
- Mike Hannon
mike@ucdhep (Bitnet)
ucdhep::mike (HEPnet)
916-752-4966 (Phone)
------------------------------------------------------------------------------
Date: Fri, 12 May 89 10:44:26 -0400
From: bernsten@phoenix.Princeton.EDU (Dan Bernstein)
Subject: Re: \uppercase\ss problem (V89 #39)
Keywords: LaTeX, \uppercase
\def\gimmeans{\ss}
\def\gimmeanS{SS}
\def\S#1{\csname gimmean#1\endcsname}
Now \S{s} will give \ss normally and SS within \uppercase. LaTeX users
might have to worry about command name conflicts and about appropriate
\protects.
Dan Bernstein, bernsten@phoenix.princeton.edu
-----------------------------------------------------------------------
Date: Wed, 10 May 89 22:44:24 -0400
From: Ken Yap <ken@cs.rochester.edu>
Reply-To: ken@cs.rochester.edu
Subject: Re: \makeatletter, \makeatother
Keywords: \makeatletter, \makeatother
Sty file writers, please do not use \makeatother (or \catcode`\@=12) at
the end of your .sty files. It is not just redundant, it upsets LaTeX's
digestion of further sty files in the \documentstyle line. Observe the
effect of running latex on sample.tex with the line:
\documentstyle[eepic,aaai]{article} % Specifies the document style.
This is TeX, C Version 2.98 (no format preloaded)
(sample.tex
LaTeX Version 2.09 <8 Feb 1989>
(/usr/lib/tex/macros/article.sty
Document Style `article' <16 Mar 88>.
(/usr/lib/tex/macros/art10.sty)) (eepic.sty
Extension to Epic and LaTeX. Version 1.1b - Released Febrary 7, 1988
) (/usr/lib/tex/macros/aaai.sty
Conference Style for AAAI-88 -- released 5 April 1988
LaTeX error. See LaTeX manual for explanation.
Type H <return> for immediate help.
! Missing \begin{document}.
\@latexerr ...for immediate help.}\errmessage {#1}
<to be read again>
n
l.67 \let\@in
ternalcite\cite
? No pages of output.
Transcript written on sample.log.
The culprit is eepic.sty. Look at the definition of \documentstyle in
latex.tex and you will see why.
The reason this doesn't happen more often is because either the
offending sty file is at the end of the list, or the styles following
are builtins that are processed first.
Of course, a \makeatletter at the beginning is redundant.
Ken
X-Uucp: ..!rochester!ken Internet: ken@cs.rochester.edu
X-Snail: CS Dept., U of Roch., NY 14627. Voice: Ken!
X-Phone: (716) 275-1448 (office)
------------------------------------------------------------------------------
Date: 09 May 89 1455 PDT
From: Arthur Keller <ARK@SAIL.Stanford.EDU>
Subject: Re: What is \everycr all about?
Keywords: TeX, \everycr
Stephan asks:
>What is \everycr all about? If instead of
> \everycr = {\a\b\c}
>I defined
> \def\CR{\cr\a\b\c}
>and ended table rows with \CR instead of \cr then this
>would work as well, wouldn't it?
No, it would not. TeX is scanning for a \cr, \crcr, or a & when it is
in an \halign or \valign. When the delimeter is reached, the argument
(that is, the text between this delimiter and the previous one) is
substituted for # in the corresponding preamble entry. If the #
expands to \cr, that is too late and will cause an error. Basically,
scanning for \cr, \crcr, and & occur in the mouth, while expansion
occurs in the stomach.
>...
>Along the same lines: why do people end preambles of tables with
>\crcr instead of \cr. Any difference there?
This is so that in LaTeX and similar macros, you can say
\table ...row1...\\...row2...\\ ... \endtable or
\table ...row1...\\...row2...\\ ...\\ \endtable
and get the same result. That is, you don't get an extra line.
The \\ is \let to \cr (not \def'ed to \cr; the difference is important).
The \table...\endtable macro includes a \crcr, which only takes effect
if there was no \cr preceding it.
An exercise left for the reader is why \cr is needed if \crcr exists.
That is, under what conditions does \cr behave differently than \crcr
Arthur
----------------------------------------------------------------------------
Date: Fri, 12 May 89 17:29
From: Wujastyk (on GEC 4190 Rim-D at UCL) <UCGADKW%euclid.ucl.ac.uk@NSFnet-Relay.AC.UK>
Subject: Sans Serif LaTeX section headings
Keywords: LaTeX, section headings
In TeXhax V89 #30, Max Ott asked
> Is there a way in Latex to change the fontsize of the section,
> subsection, ...
I agree that the normal LaTeX chapter and section headings can often be too
loud. I sometimes use the following style file to produce smaller, sans
serif headings. It is meant to go with the default book document style, but
could be used with others if you think the sizes are okay; it is also easy to
modify, or redo from other document style files.
Dominik
%%%%%%%%%%%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% SSHDBK10.STY: Sans Serif headings for BK10 style
% Change the headings to be in Sans Serif typefaces,
% Also, take all sizes down a notch (huge, not Huge etc.).
% The changes are flagged thus.
% ^^^^
%
%----------------------------- part ---------------------------------------
% From book.sty:
%
\def\@part[#1]#2{\ifnum \c@secnumdepth >-2\relax \refstepcounter{part}
\addcontentsline{toc}{part}{\thepart \hspace{1em}#1}\else
\addcontentsline{toc}{part}{#1}\fi \markboth{}{}
{\centering \ifnum \c@secnumdepth >-2\relax \Large\sf Part \thepart \par
% ^^^^^^^^^
\vskip 20pt \fi \huge \sf #1\par}\@endpart}
% ^^^^^^^^^
\def\@endpart{\vfil\newpage \if@twoside \hbox{} \thispagestyle{empty}
\newpage
\fi \if@tempswa \twocolumn \fi}
\def\@spart#1{{\centering \huge \sf #1\par}\@endpart}
% ^^^^^^^^^
%
%----------------------------- chapter -----------------------------------
% From bk10.sty:
%
\def\@makechapterhead#1{ \vspace*{50pt} { \parindent 0pt \raggedright
\ifnum \c@secnumdepth >\m@ne \huge\sf \@chapapp{} \thechapter \par
\vskip 20pt \fi \huge \sf #1\par
% ^^^^^^^^^
\nobreak \vskip 40pt } }
\def\@makeschapterhead#1{ \vspace*{50pt} { \parindent 0pt \raggedright
\huge \sf #1\par
%^^^^^^^^^
\nobreak \vskip 40pt } }
%----------------------------- section -----------------------------------
\def\section{\@startsection {section}{1}{\z@}{-3.5ex plus -1ex minus
-.2ex}{2.3ex plus .2ex}{\Large\sf}}
% ^^^
%-------------------------- subsection -----------------------------------
\def\subsection{\@startsection{subsection}{2}{\z@}{-3.25ex plus -1ex minus
-.2ex}{1.5ex plus .2ex}{\large\sf}}
% ^^^
%-------------------------- subsubsection --------------------------------
\def\subsubsection{\@startsection{subsubsection}{3}{\z@}{-3.25ex plus
-1ex minus -.2ex}{1.5ex plus .2ex}{\normalsize\sf}}
% ^^^
%---------------------------- paragraph ----------------------------------
\def\paragraph{\@startsection
{paragraph}{4}{\z@}{3.25ex plus 1ex minus .2ex}{-1em}{\normalsize\sf}}
% ^^^
%--------------------------- subparagraph --------------------------------
\def\subparagraph{\@startsection
{subparagraph}{4}{\parindent}{3.25ex plus 1ex minus
.2ex}{-1em}{\normalsize\sf}}
% ^^^
%%%%%%%%%%%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Dominik Wujastyk, | Janet: wujastyk@uk.ac.ucl.euclid
Wellcome Institute for | Bitnet/Earn/Ean/Uucp: wujastyk@euclid.ucl.ac.uk
the History of Medicine, | Internet/Arpa/Csnet: dow@wjh12.harvard.edu
183 Euston Road, | or: wujastyk%euclid@nsfnet-relay.ac.uk
London NW1 2BP, England. | Phone: London 387-4477 ext.3013
[Note that as of May 1989 the Janet-Internet gateway address has changed from
"nss.cs.ucl.ac.uk" to "nsfnet-relay.ac.uk"]
-------------------------------------------------------------------------------
Date: Wed, 10 May 89 18:42 CDT
From: <DDGHELP%TAMVENUS.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: Smart acronym macro
Keywords: acronyms
\def\acronym#1#2{\expandafter\def\csname#1\endcsname%
{#2 (#1)\expandafter\def\csname#1\endcsname{#1}}}%
%
\acronym{SAM}{Smart Acronym Macro}
\acronym{NPO}{Non-Profit Organization}
\acronym{IRS}{Internal Revenue Service}
%
Here is a \SAM\ which
Paul E. McKenney $<mckenney@spam.istc.sri.com>$ requested.
\SAM\ is very easy to use. Simply, define all your
\SAM's at the top of your file.
Then use them through your document.
The first occurance will spell out the acronym following it with
the abreviation in parans. All other occurances will be just the
abreviation. The trick, i.e. the hard part, is to define a macro
which defines a macro who's name is one of the arguements.
Did the \IRS\ charge that \NPO\ tax.
I work for a \NPO. Well, I work for the \IRS\ and the \NPO.
\bye
-------------------------------------------------------------------------------
Date: Fri, 12 May 89 16:18:50 BST
From: spqr%electronics-and-computer-science.southampton.ac.uk@NSFnet-Relay.AC.UK
Subject: MacDraw & psfig
Keywords: MacDraw, psfig
Question was:
How does one include a macdraw file in latex, using psfig ? The way I was
advised is
\input{psfig}
\begin{figure}
\centerline{\psfig{figure=fig.ps,prolog=mac.pro}}
\end{figure}
You are safer incuding the MacDraw prolog at the start of your
document so that it is globally available. How you do this
depends which dvi-->PS program you use. But its not much fun, as the
Mac prolog changes so often. Here, we have a mac.pro which works for
the version of MacDraw we have, but I am sure it will stop working if
we upgrade MacDraw
This does not seem to work, as macdraw puts out an encapsulated format of ps
not proper encapsulated PS, it doesn't. To be honest, the best advice
is to drop MacDraw and start using a program which produces decent
PostScript (such as Illustrator). You will always have problems with
MacDraw until Apple do the job properly.
Sebastian Rahtz, Computer Science, Southampton, UK
------------------------------------------------------------------------------
Date: Fri, 12 May 89 10:15:07 EDT
From: guy@phy.duke.edu (Guy Metcalfe)
Subject: Help on including MacDraw files in LaTeX
Keywords: MacDraw, LaTeX
The Mac drawing programs (at least MacDraw and MacDraft) will put out
a postscript file if you type 'apple f' or 'apple k' IMMEDIATELY after
hitting OK in the print dialogue box. This produces a file on disk
called PostScript0. The 'k' version prepends the apple postscript
dictionary to the file while the 'f' version doesn't.
WARNING: This procedure will sometimes clear you Mac* file. The
postscript will be written, but the file you can work with on the mac
will be emptied. So do this on a backup to be safe.
Guy Metcalfe
Duke University Dept. of Physics guy@phy.duke.edu
& Center for Nonlinear Studies guy@physics.phy.duke.edu
Durham, N.C. 27706 guy%phy.duke.edu@cs.duke.edu
-----------------------------------------------------------------------------
%%% 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@xxx
%%% where xxx is the nearest geographical site in the
%%% tree shown below
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%% or UNSUBSCRIBE TEX-L
%%% Here is the BITNET re-distribution tree as shown in a recent
%%% REVIEW (The geography is guessed at from the subscription list)
%%%
%%% CLVM TAMVM1 FINHUTC
%%% | | (Finland, UK, Scand, CERN)
%%% | | |
%%% TeXhax ----> UWAVM ----- MARIST ----- EB0UB011 ----- BNANDP11
%%% | (France,Italy,Spain) (Belgium)
%%% | |
%%% UBVM HEARN --- DEARN
%%% (Netherlands) (Germany)
%%%
%%% Internet: 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
%%%
%%% For further information about TeX Users Group services and publications
%%% contact Karen at KLB@SEED.AMS.COM or write to TUG at
%%% TeX Users Group
%%% P.O. Box 9506
%%% Providence, R.I. 02940-9506
%%% Telephone (401) 751-7760
%%%
%%% Current versions of the software now in general distribution:
%%% TeX 2.95 (2.98 coming) metafont 1.7
%%% plain.tex 2.94 plain.mf 1.7
%%% LaTeX 2.09 ( 8/10/88) cmbase.mf see cm85.bug
%%% SliTeX 2.09 gftodvi 1.7
%%% tangle 2.9 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
%%% AmSTeX 1.1d
%%%\bye
%%%
End of TeXhax Digest
**************************
-------