TeXhax@cs.washington.edu (TeXhax Digest) (03/18/89)
TeXhax Digest Friday, February 24, 1989 Volume 89 : Issue 16
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:
Needed: information about digital and analog symbols
Needed: information concerning script fonts?
The availability of AMS sponsored fonts (Blackboard etc.)
TeX page as an EPSF
Unix man pages for TeX etc. available by ftp
Texx2 available by anonymous ftp
LaTeX line drawing bug
DVITTY--a problem with page selection option -p and -P
Merging DVI files
Graphics and TeX--a response
Re: misprint in the texbook
Re: the LaTeX copyright notice
Misinterpretation of copyright notices.
The \begin{verbatim}text \end{verbatim} anomaly
BibTeX style which prints abstracts
-------------------------------------------------------------------------------
Date: Tue, 21 Feb 89 08:07:20 PST
From: aho@cory.Berkeley.EDU (alex ho)
Subject: Needed: information about digital and analog symbols
Keywords: symbols
does anyone know where macros can be found for digital logic
symbols (i.e. and, or, not) or analog electronics (i.e. resistors,
op amps, transistors, mosfets, etc)? thank you very much.
alex
aho@cory.berkeley.edu
...!ucbvax!cory!aho
------------------------------------------------------------------------------
Date: Sun, 19 Feb 89 13:59:06 EST
From: sland%padeds@harvard.harvard.edu (Steve Strickland)
To: TeXhax@cs.washington.edu
Subject: Needed: information concerning script fonts?
Keywords: fonts
Does a script font exist for use with TeX/LaTeX ? In the public domain? This
is conventionally used for, among other things, denoting sigma fields on
probability spaces. And while I'm at it, how about other characters in the
style of the LaTeX \Re and \Im ?
-----------------------------------------------------------------------------
Date: Mon, 20 Feb 89 22:35:08 PST
From: mackay@cs.washington.edu (Pierre MacKay)
Subject: The availability of AMS sponsored fonts (Blackboard etc.)
Keywords: fonts, script, blackboard, Fraktur
Script, blackboard and Fraktur are available in compiled versions
from several sources. The UnixTeX distribution tape, for example,
includes compilations for 118dpi, 200--240dpi, and
300(both write-white and write-black)dpi. These are supplied through
the courtesy of the American Mathematical Society.
These fonts were recently reviewed and corrected by Donald Knuth,
and old versions of them are most definitely obsolete.
The American Mathematical Society sponsored the development of
these fonts over several years, and has therefore retained title to
them. If you find that you need access to the metafont code to
make up your own compilations, get in touch with the AMS, and
arrange to receive the source code under license.
---------------------------------------------------------------------------
Date: Sun, 19 Feb 89 03:10:51 -0800
From: Tomas G. Rokicki <rokicki@polya.Stanford.EDU>
Subject: TeX page as an EPSF
Keywords: TeX, dviware
The only PostScript driver I know of that generates its output in a
form that can be used as a graphic in other documents is my version
of dvips on the Amiga. I would consider this a minimum requirement
for dvi to PostScript translators, that they be able to include their
own output as a graphic, perhaps rotated 90 degrees. Recursively.
(Of course, you can't expect bitmapped fonts to look good when
scaled down in this manner.) This requires elimination of the
`initmatrix' and some other operators in the prologue file. -tom
----------------------------------------------------------------------
Date: Mon, 20 Feb 89 21:43:03 PST
From: mackay@cs.washington.edu (Pierre MacKay)
Subject: Unix man pages for TeX etc. available by ftp
Keywords: TeX, UNIX, man pages
I am putting the ./tex82/Man-pages directory on ~ftp/tex at
june.cs.washington.edu, as manpages.tar.Z That's what there is for now.
I am still improving the MF.1 pages, so try for a new lot in about
three weeks.
2 gftodvi.1 8 mf.1 2 pktype.1 7 tex.1
2 gftopk.1 2 patgen.1 1 pltotf.1 1 tftopl.1
2 dvitype.1 2 gftype.1 2 pktogf.1 4 tangle.1
Email: mackay@cs.washington.edu Pierre A. MacKay
Smail: Northwest Computing Support Center TUG Site Coordinator for
Lewis Hall, Mail Stop DW10 Unix-flavored TeX
University of Washington
Seattle, WA 98195
(206) 543-6259
------------------------------------------------------------------------------
Date: Sun, 19 Feb 89 14:18:54 cst
From: grunwald@m.cs.uiuc.edu (Dirk Grunwald)
Subject: Texx2 available by anonymous ftp
Keywords: TeX, previewer, X11
texx2.4 is available for anonymous FTP from
a.cs.uiuc.edu: pub/TeX/texx2.4.tar.Z
or
expo.lcs.mit.edu: contrib/texx2.4.tar.Z
texx2, currently at revision 4, is a second generation TeX previewer for
X11 windowing systems. Unlike texx or xdvi, texx2 uses X11 fonts to display
TeX output. A companion program, `mftobdf', is used to convert TeX fonts
(i.e., PXL/GF/PK) fonts to the the formats required for X11.
Consequentially, texx2 is significantly faster than the first release of
texx or the venerable xdvi. Page display occurs at roughly the same speed
of displays in `xman'. It's really even faster than texsun.
Features include:
+ Multiple pages displays at once, each in their own toplevel window.
+ Pages can be `tied' together, such that hitting `foreward'
in one page causes the second page to go forward
+ Ability to goto any page (using page numbers stored in \count0)
+ Different mag levels can be set for different page displays
+ Can use any existing fonts (for example, I use 300 dpi fonts,
and view the document at mags of 500 and 333 -- this gives
good detail & overall views)
+ horiztoial and vertical scroll bars if needed
+ can mark individual pages for printing
+ can print entire document and/or marked pages
+ the main window is designed to be leftup between viewing
sessions -- no need to restart the tool each time.
+ handles tpic specials, out-lines bounding box of psfig
pictures.
+ Known to work on X servers for Sun 3/60, IBM PC/RT, Vaxstation 3100.
Known to run as client on Sun 3/60, IBM PC/RT, Encore Multimax
(our vaxstation version of X11 doesn't have all patches applied,
so something causes it to die there)
+ It's free.
Downsides:
+ You need to generate the X11 fonts. While this is simple, it's
takes me about 600K to store the fonts we use on a daily basis.
However, you *can* compress them, although that slows down
page display startup.
+ Can easily expand your server memory size by 450K, because of all
the fonts.
+ There is no warrenty, precious little documentation,
and I'm not going to be able to answer mail about it
because I'm interviewing and trying to finish my thesis.
However, if you've ever installed texsun or texx, texx2
should be a snap.
Office: 72 DCL (217) 333-1925
-----------------------------------------------------------------------------
Date: Mon, 20 Feb 89 15:43:21 PST
From: Marty Cohen <mcohen@nrtc.northrop.com>
Subject: LaTeX line drawing bug
Keywords: LaTeX, bug
A coworker found the following LaTeX bug. I verified it with
Textures on a Mac II (though with slightly different failures).
The bug description is in the initial comments.
\documentstyle[12pt]{article}
\begin{document}
% Subject: LaTeX Flub
% Date: Mon, 20 Feb 89 10:08:26 -0800
% From: jbarnett@gremlin.nrtc.northrop.com
%
% The following file is for LaTeX. It was generated by a SYMBOLICS program
% and produces a picture of a Tinker Toy part. The program takes a few
% parameters to control relative and absolute sizes. The included file works
% just fine--run it and see. Next, find `\setlength{\unitlength}{48pt}' phrase
% in the 4th file line; change `48pt' to `47pt' or any other length that is
% smaller and rerun the file. You will note that four lines disappear. These
% lines are approximately 1/6in long and at a 45 deg angles. If the `48pt' is
% reduced further -- somewhere in the 30's -- other short lines disappear also.
% Since LaTeX, to the best of my knowledge, does the lines from a funny font, I
% am curious if we have the wrong files up, etc.
%
% Jeff
% --------------------------------------------------------------------------
\newsavebox{\connectorbox}\sbox{\connectorbox}{
\setlength{\unitlength}{48pt}\begin{picture}(2,2)(-1,-1)\thicklines
\put(0,0){\circle{0.315}}
\put(-0.41421354,1){\line(1,0){0.8284271}}
\put(-0.15,1){\line(0,-1){0.4}}
\put(-0.15,0.6){\line(1,0){0.3}}
\put(0.15,0.6){\line(0,1){0.4}}
\put(0.41421354,1){\line(1,-1){0.58578646}}
\put(0.6010408,0.81317276){\line(-1,-1){0.28284273}}
\put(0.31819806,0.53033006){\line(1,-1){0.21213204}}
\put(0.53033006,0.31819806){\line(1,1){0.28284273}}
\put(1,0.41421354){\line(0,-1){0.8284271}}
\put(1,0.15){\line(-1,0){0.4}}
\put(0.6,0.15){\line(0,-1){0.3}}
\put(0.6,-0.15){\line(1,0){0.4}}
\put(1,-0.41421354){\line(-1,-1){0.58578646}}
\put(0.81317276,-0.6010408){\line(-1,1){0.28284273}}
\put(0.53033006,-0.31819806){\line(-1,-1){0.21213204}}
\put(0.31819806,-0.53033006){\line(1,-1){0.28284273}}
\put(0.41421354,-1){\line(-1,0){0.8284271}}
\put(0.15,-1){\line(0,1){0.4}}
\put(0.15,-0.6){\line(-1,0){0.3}}
\put(-0.15,-0.6){\line(0,-1){0.4}}
\put(-0.41421354,-1){\line(-1,1){0.58578646}}
\put(-0.6010408,-0.81317276){\line(+1,+1){0.28284273}}
\put(-0.31819806,-0.53033006){\line(-1,1){0.21213204}}
\put(-0.53033006,-0.31819806){\line(-1,-1){0.28284273}}
\put(-1,-0.41421354){\line(0,1){0.8284271}}
\put(-1,-0.15){\line(+1,0){0.4}}
\put(-0.6,-0.15){\line(0,1){0.3}}
\put(-0.6,0.15){\line(-1,0){0.4}}
\put(1,0.41421354){\line(0,-1){0.8284271}}
\put(1,0.15){\line(-1,0){0.4}}
\put(0.6,0.15){\line(0,-1){0.3}}
\put(0.6,-0.15){\line(1,0){0.4}}
\put(-1,0.41421354){\line(1,1){0.58578646}}
\put(-0.81317276,0.6010408){\line(1,-1){0.28284273}}
\put(-0.53033006,0.31819806){\line(1,1){0.21213204}}
\put(-0.31819806,0.53033006){\line(-1,1){0.28284273}}
\end{picture}}
\begin{center}\usebox{\connectorbox}\end{center}
\end{document}
----------------------------------------------------------------------------
Date: Fri,17 Feb 89 11:41:39 GMT
From: Dawn_Petherick%VME.CCC.NOTTINGHAM.AC.UK@UWAVM.ACS.WASHINGTON.EDU
Subject: DVITTY--a problem with page selection option -p and -P
Keywords: DVITTY, bug
When using DVITTY (for converting TeX DVI-files to a format suitable
for terminals and line-printers) we came across a problem with
page selection options -p and -P, they didn't work properly!
Trying to select pages 3:6 from a TeX-DVI file containing pages numbered 1 thru
8 produced no output at all, unless the first page in the range was page 1.
Selecting multiple ranges e.g. 1:3,6:8 only produced the first range (but
again, only if page 1 was the first page.)
After looking at the source of the main pascal program (dvitty.p) I found the
problem and include the solution here for anyone interested!
(I've also mailed DVITTY's author, Svante Lindahl and Pierre MacKay so that the
UnixTeX distribution tapes can be updated.)
The problem turned out to be in the function inlist, the correct version is:
function inlist(pagenr : integer) : boolean; {ret true if in list of pages}
begin
inlist:=false;
while (currentpage.pag<0) and (currentpage.pag<>pagenr)
and not currentpage.all and (currentpage.nxt<>nil) do
currentpage:=currentpage.nxt;
if (currentpage.all and (pagenr<currentpage.pag))
or (currentpage.pag=pagenr) then inlist:=true
else if pagenr>0 then begin
while (currentpage.pag<>pagenr) and (currentpage.nxt<>nil) do
currentpage:=currentpage.nxt;
if currentpage.pag=pagenr then inlist:=true
end;
currentpage:=firstpage; {bug correction by DP}
end; {inlist}
Dawn Petherick
Cripps Computing Centre
University of Nottingham
England
-------------------------------------------------------------------------
Date: Fri, 17 Feb 1989 10:29:15 JST
From: Hideki Isozaki <isozaki@expert-sun.ntt.jp>
Reply-To: isozaki%expert-sun.ntt.jp@relay.cs.net
Subject: Merging DVI files
Keywords: dvi files, METAFONT
Does anyone have a program to merge DVI files?
I'd like to merge TeX output with METAFONT/gftodvi output.
Hideki Isozaki
NTT Software Research Labs.
Nippon Telegraph and Telephone Corp.
Organization: NTT Software Research Laboratory
Address: 9-11, Midori-Cho 3-chome, Musashino-shi, Tokyo 180, Japan
Telephone: +81 422 59 2548 (voice) +81 422 59 4369 (fax)
P.S.
Current versions of NTT JTeX :
NTT JTeX : ver.1.0.
NTT JLaTeX : ver.1.1.
Several drivers were updated.
---------------------------------------------------------------------------
Date: Fri, 17 Feb 89 09:14 PST
From: SHECTMAN@seti.llnl.gov
Subject: Graphics and TeX--a response
Keywords: graphics
My greatest problem with David Rogers idea is the inclusion of the
graphics directly in the TeX and therefore the DVI file. Any document
with a signicant number of pictures is rapidly going to generate
files that are a bit on the large size. An alternative is to
extend the definition of a dvi file to encompass a graphics file
and type. The graphics file interpreter instead of translating
from a particular graphics file format into TeX, would translate
into DVI commands, which are then automatically translated into the
device format. Optionally, translation could go directly to output
device format.
This would relieve tex of having to 'layout' the fine detail of a
picture. Most pictures would place a severe strain on the internal
TeX buffers, as the number of primitives on a page with graphics would
be hugh. Only the area the picture would occupy (sounds like a box
to me) would have to be dealt with by TeX in terms of page layout.
We currently use a system that does a little bit of this. We pass
into TeX, the file name and size of a picture (as a floating insert).
TeX lays out the page, and writes to the DVI file a move to start of
the box that is the size of the picture, and then the \special that
has the file name. We then read in the graphics file and pass it
to the printer. What is of course missing from this is the ability
to translate a variety of formats into either DVI or actual printer
commands. At this point all we do is read in printer commands
(QMS laser printer). We generate these from a variety of sources,
mainly graphics programs associated with the display of various
types of data.
For us, it works, but of course only in our rather restricted
environment. Its a whole new can of worms to generalize the
capability.
-------------------------------------------------------------------------
Date: Sun 19 Feb 89 11:00:20-EST
From: b beeton <BNB@SEED.AMS.COM>
Subject: Re: misprint in the texbook
Keywords: errors, TeX
in texhax 89#9, j. m. hicks reports a misprint in the texbook on page 379,
in the line \def\deleterightmost ...
this is indeed an error; it was corrected on 10/12/87, as reported in
knuth's errata file, errata.tex, which can be obtained by anonymous ftp
from score.stanford.edu in directory <tex.doc> and from other repositories,
such as those at clarkson (in the u.s.) and aston (in the u.k.).
an errata list or update is published by the tex users group with almost
every issue of tugboat; a cumulative list from june 1987 will appear with
tugboat 10#1, which is now being readied for the printer. in addition to
errata for volumes a-e of computers and typesetting (of which the texbook
is volume a), this errata list includes changes to the tex and metafont
programs and to the cm fonts, as listed in knuth's files tex82.bug,
mf84.bug and cm85.bug.
the .bug files and earlier errata files -- errata.one, errata.two and
errata.thr -- are available electronically from the same sources as
errata.tex.
printed errata/bug lists are available from tug; see the trailer on any
texhax issue for the address.
bb
----------------------------------------------------------------------------
Date: 19 Feb 1989 1927-PST (Sunday)
From: lamport@src.dec.com (Leslie Lamport)
Subject: Re: the LaTeX copyright notice
Keywords: LaTeX, copyright
Keven Jameson (?) inquires about the copyright notice on the LaTeX
source files. Years ago, Don Knuth advised me to put this notice on
all my files. I don't remember why. Anyone is free to use and copy
those files. The only thing someone may not do is to make basic
changes to LaTeX and call the resulting system "LaTeX". ("Basic"
changes do not include changes to font files and such made to adapt
LaTeX to locally available fonts and output devices.)
------------------------------------------------------------------------------
Date: Mon, 20 Feb 89 22:21:04 PST
From: mackay@cs.washington.edu (Pierre MacKay)
Subject: Misinterpretation of copyright notices.
Keywords: LaTeX, copyright
This is bizarre. I don't know what source you got your TeX from, but
most distributions make it clear, or at least understandable, that
except for physical reproductions of the TeXbook, the purpose of the
copyright notices is more to ensure general accessibility and free
copying privileges than to restrict anything. The COPYING.POLICY
notice in the UnixTeX distribution was written before the Free
Software Foundation worked out its copyright notice, which makes
things even clearer, but it has been the intention of the UnixTeX
distribution, and of all contributors to it that copyright as noted in
all files is intended to ensure the free redistribution of those
files. Perhaps it is time to "grep" all copyrights in the
distribution and associate them explicitly with a version of the Free
Software Copyright notice.
In any case, you are free to take a copy of latex.tex and do anything
with it you like. You can even change it, if you are very bold, but
you must keep the changes to yourself, or let Leslie Lamport decide
whether they are a good idea (by now, rather unlikely). It isn't just
that we don't mind, we positively encourage this action. What Lamport
and all the rest of us want to be protected against is the
proliferation of bogus forms of the software. We also want to be
sure that there is no restriction placed on the redistribution of
genuine copies, just as the Free Software Foundation does.
Email: mackay@cs.washington.edu Pierre A. MacKay
Smail: Northwest Computing Support Center TUG Site Coordinator for
Lewis Hall, Mail Stop DW10 Unix-flavored TeX
University of Washington
Seattle, WA 98195
(206) 543-6259
----------------------------------------------------------------------------
Date: 19 Feb 1989 1927-PST (Sunday)
From: lamport@src.dec.com (Leslie Lamport)
Subject: The \begin{verbatim}text \end{verbatim} anomaly
Keywords: LaTeX, verbatim
David Rhead observes that
\begin{verbatim}
text
\end{verbatim}
and
\begin{verbatim}text \end{verbatim}
behave differently. This is an intentional anomaly. The verbatim
environment is a paragraph-making environment; it starts a new
paragraph at the prevailing left margin. Each newline character is
supposed to start a new line. But, if taken literally, this would
cause problems. Consider the following example.
\begin{verbatim}line one
line two
\end{verbatim}
It should simply form a two-line verbatim environment. Now,
consider
\begin{verbatim}
line two
\end{verbatim}
It should be the same as the previous example, except with "line one"
replaced by blank space. But, this is obviously not what one would
expect. Therefore, the verbatim environment is designed to work
properly when the "\begin{verbatim}" is followed by space and a
newline. As a result, following the "\begin{verbatim}" with
anything else may yield anomalous results.
I suppose it might be possible to make both cases work properly. (In
fact, I think it they will when not inside an indented environment.)
But, now I don't even understand why the verbatim environment works at
all, and I don't feel like figuring it out.
Leslie Lamport
-------------------------------------------------------------------------------
Date: Tue, 21 Feb 89 15:07:02 GMT
From: Sebastian Rahtz <spqr%electronics-and-computer-science.southampton.ac.uk@NSS.Cs.Ucl.AC.UK>
Subject: BibTeX style which prints abstracts
Keywords: BibTeX, abstracts
Someone asked for a BibTeX style which prints abstracts; my colleague
Stephen Adams mentioned to me that he had hacked 'alpha' to print the
'annote' field, which is obviously the same. Here is the relevant function:
FUNCTION {fin.entry}
{ add.period$
annote empty$
'write$
{ "\par\bgroup\parindent=0em " * annote * "\par\egroup " * write$
}
if$
newline$
}
I'm not suggesting this is ideal, but it does more or less work, and it
gives a rough model for how to achieve what is wanted. I think all
.bst files have such a 'fin.entry' function which can be similarly
edited.
Sebastian Rahtz, Computer Science, Southampton
---------------------------------------------------------------------------
%%% 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.ACS.WASHINGTON.EDU
%%% 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
%%%
%%% 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 metafont 1.7
%%% plain.tex 2.94 plain.mf 1.0
%%% 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 dvipage 3.0
%%% AmSTeX 1.1d
%%%\bye
%%%
End of TeXhax Digest
**************************
-------