TeXhax@cs.washington.edu (TeXhax Digest) (07/27/89)
TeXhax Digest Friday, July 21, 1989 Volume 89 : Issue 69
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:
Graphs in TeX
Unix man page for bibtex 0.99c wanted
Re: TeXhax Digest V89 #66 (clarkson address)
Re: TeXhax Digest V89 #66 (notes in tables)
RE: TeXhax Digest V89 #66 (LaTeX, \footnoterule, \renewcommand)
Eliminating "extra" rule with footnotes in a minipage
Re: Footnotes in tables
Re: Problem with TeX( _ and $)
\catcode Woes
TeX distribution for the SGI
TeX source output from analysis packages
Re: WEAVE CMS-CHAN problem in the VM/CMS TeX distribution
----------------------------------------------------------------------------
Date: Fri, 21 Jul 89 23:40 GMT
From: Peter Flynn UCC <CBTS8001%IRUCCVAX.UCC.IE@UWAVM.ACS.WASHINGTON.EDU>
Subject: Graphs in TeX
Keywords: graphs, TeX
At the Exeter meeting last year, a presentation was made of some nicely
labelled graphs done without LaTeX (I think). A promise of availability
was made---does anyone know what happened to the macros? I managed to get
the chemical structure stuff also presented there at last (from DHDURZ1)
was it ever announced that it was being put into the archives---maybe I
missed an issue?
Peter
----------------------------------------------------------------------------
Date: Thu, 20 Jul 89 18:45:46 EDT
From: nr@Princeton.EDU (Norman Ramsey)
Subject: Unix man page for bibtex 0.99c wanted
Keywords: UNIX, man pages, BibTeX 0.99C
Does anyone have a Unix man page for bibtex version 0.99c?
The most recent man page we have is dated October 1986, so
I think it may be a wee bit out of date :-(
I can ftp from clarkson or washington if a man page finds its
way to the Unix TeX or LaTeX archives.
Norman Ramsey
nr@princeton.edu
Princeton University Computer Science
----------------------------------------------------------------------------
Date: Thu, 20 Jul 89 13:31:07 -0400 (EDT)
From: Mark Fichman <mf4f+@andrew.cmu.edu>
Subject: Re: TeXhax Digest V89 #66 (clarkson address)
Keywords: information, clarkson address
In regard to the clarkson.edu problem, the difficulty is the wrong
name and address were given.
The TeX archives at clarkson are at sun.soe.clarkson.edu (128.153.12.3).
I ran into this problem as well.
Mark Fichman
Carnegie-Mellon University
----------------------------------------------------------------------------
Date: Thu, 20 Jul 89 09:01:40 PDT
From: lamport@src.dec.com (Leslie Lamport)
Subject: Re: TeXhax Digest V89 #66 (notes in tables)
Keywords: notes, tables
Elizabeth Cashdan writes:
What is the best way to put notes in tables? Currently, I'm using the
footnote command like this:
\begin{minipage}{\textwidth}
\begin{tabular}{cccccccc}
...
1.\footnote{Lizot 1978:89--90}
& 38& 40& 45& 38& 54& 136& 357 \\
...
\end{tabular}
\end{minipage}
The problem is that the footnote command generates an unwanted horizontal
rule at the bottom of the minipage...
Looking in the index under "footnote", we find the entry
"line above, 156".
On page 156, we find
\footnoterule: A command that draws the line separating the footnotes
from the main text... It can be redefined anywhere with \renewcommand;
the definition used is the one in effect when TeX produces the page of
output.
The last sentence would lead one to wonder if the \footnoterule command
applies to footnotes in a minipage. However, it should certainly lead
one to give it a try, which reveals that
\renewcommand{\footnoterule}{}
inside the minipage environment (but, of course, outside the tabular
enironment) has the desired effect.
Proper use of LaTeX (separating content from format) dictates that
one should encapsulate all this in a single environment--e.g.,
\newenvironment{foo}[1]%
{\begin{minipage}{\textwidth}
\renewcommand{\footnoterule}{}
\begin{tabular}{#1}}%
{\end{tabular}\end{minipage}}
Leslie Lamport
--------------------------------------------------------------------
Date: Thu, 20 Jul 89 11:27 BST
From: RMCS TeX Account <TEX%rmcs.cranfield.ac.uk@NSFnet-Relay.AC.UK>
Subject: RE: TeXhax Digest V89 #66 (LaTeX, \footnoterule, \renewcommand)
Keywords: LaTeX, \footnoterule, \renewcommand
In TeXhax V89 #65, Elizabeth Cashdan (cashdan@ARSUN.UTAH.EDU) asks how to
suppress the line separating her minipage footnotes from the table above.
Now she HAS recognized that this is a rule, and it's obviously connected with
FOOTNOTEs, so perusing the index of the LaTeX book reveals ``\footnoterule''
or ``footnote, line above''. Both these entries refer to p.156, on which the
intelligence is given that the \footnoterule command generates the line
separating the footnotes from the main text (read contents of a minipage, in
this context). The top of p.157 further informs us that it can be redefined
anywhere with \renewcommand, so a quick check with:
\begin{minipage}{\textwidth}
\renewcommand{\footnoterule}{}
\begin{tabular}{cccccccc}
at the top of her table suppresses the unwanted line!! (Moreover, because the
redefinition is limited to the scope of her minipage, other footnote rules
will appear as normal.)
This query is yet another instance of something that could readily be answered
by a few seconds perusal of the manual --- as one of the TeX support staff at
this site I always tell people to read the manual before bothering me with
problems, and moreover, I recommend that EVERYONE should read the whole of the
LaTeX book at least twice BEFORE setting finger to keyboard!! That way, when
such queries arise, one has it in the back of the mind that ``there's
something about footnotes in the reference section'', etc.
TeXhax (and UKTeX) is becoming more and more cluttered with such simplistic
queries, which, even if not answerable by the inquirer him/herself, should be
filtered off by the local site TeXnician. I keep all TeXhaxes on-line
(because there are many queries/responses that ARE useful) and I resent the
waste of disk quota occasioned by such queries as this.
Brian {Hamilton Kelly}
| JANET: tex@uk.ac.cranfield.rmcs |
| BITNET: tex%uk.ac.cranfield.rmcs@ac.uk |
| INTERNET: tex%uk.ac.cranfield.rmcs@nsfnet-relay.ac.uk |
| Smail: School of Electrical Engineering & Science, Royal Military |
| College of Science, Shrivenham, SWINDON SN6 8LA, U.K. |
| Phone: Swindon (0793) 785252 (UK), +44-793-785252 (International) |
--------------------------------------------------------------------------
Date: Thu, 20 Jul 89 13:15 EDT
From: "Jerry Leichter - LEICHTER-JERRY@CS.YALE.EDU"
<LEICHTER@Venus.YCC.Yale.Edu>
Subject: Eliminating "extra" rule with footnotes in a minipage
Keywords: LaTeX, \footnoterule, \renewcommand
Elizabeth Cashdan is setting a table inside a minipage and using \footnote to
insert reference notes within the table. The actual notes appear at the
bottom of the minipage, but there is an "extra" rule above them.
This rule is simply the footnote separator which is also placed above "normal"
footnotes on a page. Whether it is appropriate depends on where it is being
used. If the minipage contained a bunch of text, it would probably be
desireable; if all it contains is a boxed table, it may look bad. It's
easy to eliminate: It is inserted by the \footnoterule macro, which is a
style parameter. Simply insert the command:
\renewcommand{\footnoterule}{\relax}
just AFTER the \begin{minipage}. CAUTION: This MIGHT have a side effect if
it occurs near the bottom of a page which has footnotes. If TeX decides to
produce a page of output while you are within the minipage environment, the
current \footnoterule - the empty one - will be used for the page. I haven't
looked close enough to determine whether this can really happen; actually, I
suspect it can't. But if it does, it may not be easy to get around, though
you could try forcing a page break to get stuff cleared out before the
minipage begins.
Jerry
----------------------------------------------------------------------------
Date: Thu, 20 Jul 89 11:53:35 CDT
From: Don Hosek <U12921%UICVM.UIC.EDU@UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: Footnotes in tables
Keywords: LaTeX, \footnoterule, \renewcommand
The rule above the footnote is generated by \footnoterule; you can
redefine it inside the minipage using \renewcommand{\footnoterule}{}
so that it doesn't do anything and you shouldn't have a problem with
it.
dh
Don Hosek | Internet: U12921@UICVM.UIC.EDU
3916 Elmwood | Bitnet: DHOSEK@HMCVAX.BITNET
Stickney, IL 60402 | DHOSEK@YMIR.BITNET
Work: 312-996-2981 | UUNet: dhosek@ymir.claremont.edu
ERASE * SCRIPT * | JANET: DHOSEK%HMCVAX.BITNET@UK.AC.EARN-RELAY
30 days until my return to California
--------------------------------------------------------------------------
Date: Sun, 23 Jul 89 03:20:07 CDT
From: dlau@cs.utexas.edu (David Lau)
Subject: Re: Problem with TeX( _ and $)
Keywords: TeX, underscore, $
In issue #65, Ian Murphy inquired about changing the catcodes of `$'
and `_' within a control sequence. He tried the following piece of
code but failed:
\def\program{
\begingroup
\catcode`$=\active
\catcode`_=\active
\def${\dollar}
\def_{\uscore} }
\program %%%% call the macro and wait for the errors
It doesn't work simply because TeX stamps a input character with a
catcode the first time the character is read; and this association will
stay in effect even if another catcode is assigned to the
character in question later on. When \program is being defined,
the characters `$' and `_' are assigned catcodes 3 and 8. Hence, when
TeX tries to expand `\def${...}', a complaint results.
The solution is to define \program only when `$' and `_' are both
"active":
{\catcode`$=\active \catcode`_=\active
\gdef\program{
\begingroup
\catcode`$=\active
\catcode`_=\active
\def${\dollar}
\def_{\uscore} }
}
David
----------------------------------------------------------------------
Date: Fri, 21 Jul 89 01:50 +1000
From: Douglas Miller <munnari!csv.viccol.edu.au!DOUGCC@uunet.UU.NET>
Subject: \catcode Woes
Keywords: TeX, \catcode
> I'm writing a program to typeset programs and I want TeX to handle the _
> and $ symbol rather than my converting all occurences of _ to \_.
> this is what I tried
>
>\def\program{
> \begingroup
> \catcode`$=\active
> \catcode`_=\active
> \def${\dollar}
> \def_{\uscore} }
>\program %%%% call the macro and wait for the errors
>
> TeX complained about the \def$, so I guessed that it was reading the dollar
> before it was executing the \catcode`$,
Yes, catcodes are assigned to characters when the are first read. The
\catcode assignments in your macro ONLY change the catcodes of $ and _ in
text following an invocation of the \program macro. You need a separate
set of catcode assignments to set the catcodes of $ and _ when you are defining
them as macros. e.g.
\begingroup
\catcode`$=\active
\catcode`_=\active
\def${\dollar}
\def_{\uscore}
\endgroup
\def\program{
\begingroup
\catcode`$=\active
\catcode`_=\active}
> ...so I did the following
[attempt with \noexpand deleted]
> ... ( I thought the \noexpand would prevent it from doing anything
> with the tokens in the macro, i was wrong)??????
\noexpand doesn't help, because the problem is not with token expansion,
but with the assignment of catcodes to tokens!
-----------------------------------------------------------------------
Date: Tue, 25 Jul 89 7:52:29 EDT
From: "David F. Rogers" <dfr@cad.usna.mil>
Subject: TeX distribution for the SGI
Keywords: TeX, SGI Iris 4D
G'day,
The first release of TeX for the SGI Iris 4D series is ready for
distribution.
This has been used at RMIT (Royal Melbourne Institute of Technology)
for some months and has worked reasonably well. There should be another
release later this year with an improved previewer and any
improvements/fixes that we make in reponse to comments of other TeX users
on the 4D series. There are a number of improvements in the pipeline,
including better support for pictures in a postscript output file, HP
laserjet (and plus) output as well as a much better previewer.
There isn't a good local guide as there should be. This will be fixed in
the next release.
---
Here is a brief description of the programs useful to most TeX users:
In /usr/local/bin:
tex - Native TeX v2.93
latex - LaTeX v2.09
bigtex - Increased size complex documents/macros -- Common TeX v2.9
biglatex - Increased size complex documents/macros -- Common TeX v2.9
tgrind - convert a source file into TeX and optionally (pretty)
print it
In /usr/local/tex/bin:
initex - normal initex -- As described in the TeXbook
virtex - normal virtex) -- As described in the TeXbook
biginitex - initex enlarged for those extra big jobs (say picTeX)
bigvirtex - initex enlarged for those extra big jobs (say picTeX)
bibtex - BibTeX as documented in the LaTeX book.
texsgi - version 0.5 of the Iris previewer
dvi2ps - a dvi -> postscript converter (port of
tex82/TeXdevices/mitdrivers/dvi2ps)
dvi2tty - a (very) poor man's previewer
dvitype - information about a dvi file
tr2tex - convert a troff document to LaTeX
---
You can send comments etc to
Mike Gigante
Applied Computer Graphics Lab
Royal Melbourne Institute of Technology
124 Latrobe Street,
Melbourne, Australia 3001
+61 3 660 2935
Email: mg@cidam.oz.au
or to
Prof. David F. Rogers
Aerospace Engineering Dept.
U.S. Naval Academy
Annapolis, MD 21402, USA
(301) 267 3283/4/5
Email: dfr@usna.navy.mil
who has offered to act as the US distribution point.
email comments should be sent to both Mike Gigante and Dave Rogers.
Distribution:
Binaries are located on vgr.brl.mil (192.5.23.6) at BRL in directory
/usr/spool/ftp/info-iris
in file
texbin.tar.Z
and may be obtained by anonymous ftp. The compressed tar file is
approximately 5.8 megabytes!
Dave Rogers will provide a distribution (US & Canada only) on SGI
hi-density cartridge tapes if you ABSOLUTELY cannot ftp them. To get
these tapes send three (3) 3M DC600A 600 ft, 12,500 ftpi hi-density
cartridge tapes to him at the above address.
Mike Gigante will provide a similar service for the rest of the world.
To install the distribution
ftp file: zcat texbin.tar.Z | tar xvf -
cartridge tape: tar xv
Place the following in your path:
/usr/local/bin and /usr/local/tex/bin
and you are ready to go. A README file is in /usr/local/tex/README.
!!!!!!!!!!!!! NOTE !!!!!!!!!!!!!
Absolute path names were used to simplify our distribution task.
The compressed tar file will expand into an estimated 15-18 megabytes
in /usr. MAKE SURE YOU HAVE ENOUGH DISC SPACE.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
You will need to set the following environment variables to use dvi2tty,
it is suggested that you put this in /etc/cshrc (/etc/profile) so
that everyone gets it by default..
setenv DVI2TTY ""
(or for Bourne shell users
DVI2TTY=""; export DVI2TTY)
It is recommended that you use the -q option for the present
implementation of the texsgi previewer.
Dave Rogers
Mike Gigante
7/24/89
-------------------------------------------------------------------------
Date: Thu, 20 Jul 89 14:36 GMT
From: Peter Flynn UCC <CBTS8001%IRUCCVAX.UCC.IE@UWAVM.ACS.WASHINGTON.EDU>
Subject: TeX source output from analysis packages
Keywords: TeX, source, output, stats, pstat
At the 9th European P-STAT User Group in London a coupla weeks ago, the
authors showed their tabulation routines producing PostScript. Very nice,
but one step too far on for usability, because and mod to what you want
would mean reentering the package and reprocessing the table. They were
however, very interested in the idea of making P-Stat output TeX source
as well, which would mean (if all is nicely macroised) a relatively
soft-coded method of getting really good quality output from an analysis
and stats package. I will keep the list posted on developments. PostScript
output from this kind of package is not new at all, but TeX source would be.
P-STAT has always had good quality output design, but has fallen behind in
recent years on the typographic side. This might change things.
Peter Flynn
[Declaration of interest: I am Chairman of the European User Group, which is
why I am reporting on this development.]
---------------------------------------------------------------------------
Date: Thu, 20 Jul 89 11:40:31 CDT
From: Don Hosek <U12921%UICVM.UIC.EDU@UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: WEAVE CMS-CHAN problem in the VM/CMS TeX distribution
Keywords: WEAVE CMS-CHAN, VM/CMS TeX distribution
You have stumbled on one (of many) pitfalls in the VM/CMS TeX distribution
where there are unTeXable sections of code (another one occurs in
DVItype). Before summer's end, I should have versions of all of the CMS
change files which are WEAVE- and TeXable. The problem you described
where the code was commented out using {...} could be fixed by
replacing the {...} with @{ and @} (which is the proper way to
out-comment code in WEB). As for the file type being either CMS-CHAN or
CMS-CHANGES, it properly is CMS-CHANGES since the practice in archival
of change files is to make the extension be the OS name + "-CHANGES" as
in CMS-CHANGES, VMS-CHANGES, TOPS20-CHANGES, WEB2C-CHANGES, etc. On
CMS, the name gets truncated to eight characters. C'est l'IBM.
dh
Don Hosek | Internet: U12921@UICVM.UIC.EDU
3916 Elmwood | Bitnet: DHOSEK@HMCVAX.BITNET
Stickney, IL 60402 | DHOSEK@YMIR.BITNET
Work: 312-996-2981 | UUNet: dhosek@ymir.claremont.edu
ERASE * SCRIPT * | JANET: DHOSEK%HMCVAX.BITNET@UK.AC.EARN-RELAY
30 days until my return to California
-----------------------------------------------------------------------
%%% Further information about the TeXhax Digest, the TeX
%%% Users Group, and the latest software versions is available
%%% in every tenth issue of the TeXhax Digest.
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%%
%%% BITNET: send a one-line mail message to LISTSERV@xxx
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%% or UNSUBSCRIBE TEX-L
%%%
%%% Internet: send a similar one line mail message to
%%% TeXhax-request@cs.washington.edu
%%% JANET users may choose to use
%%% texhax-request@uk.ac.nsf
%%% 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
%%%
%%%\bye
%%%
End of TeXhax Digest
**************************
-------