TeXhax@Score.Stanford.EDU (TeXhax Digest) (07/08/88)
TeXhax Digest Thursday, July 7, 1988 Volume 88 : Issue 61
Moderator: Malcolm Brown
Today's Topics:
Immoderate Notes
Equation labelling in LaTeX
MakeIndex on IBM PC
LaTeX figure captions vs line buffer size
Directory pointers
Need reference to metafont fix for \Leftarrow, \Rightarrow
TUG IX
Re: Directory pointers? [VMS logical name search lists]
TeX in C
How to become a technical writer
\bf{bold}
Beebe's DVIEPS.C on the PC/AT
DVIEW
Changing TeX$input under VMS
unending \bf; texhax 88#59
no hyphenation after a hyphen
Driver for EPSON LQ500, NECP6
----------------------------------------------------------------------
Date: 07 July 1988
From: Malcolm
Subject: Immoderate Notes
%%% There have been a number of problems at Score that have put a crimp
%%% into TeXhax. First, the mail queues for issues 57 and 58 were
%%% rejected by the mailer, meaning that a large number of you probably
%%% didn't receive them. Sorry, but this erratic behavior on the part of
%%% mailer at Score defies the precautions I take. In any case, PLEASE
%%% attempt to FTP them from Score (Internet) or from the LISTSERV@TAMVM1
%%% on BITNET. Due to the amount of time that moderator duties consume,
%%% mailing back issues is a low-priority task for me. You'll get them
%%% much sooner if you take matters into your own hands.
%%% Second: Score suffered yet another disk failure. I have determined
%%% that items mailed between 1 July and 4 July (inclusive) were lost.
%%% These problems have contributed to the delay of digests. My apologies,
%%% although all these difficulties are beyond my control. I will do my
%%% best to get us up and rolling once again. In the meantime, a very large
%%% backlog has developed, so there will continue to be some delay on
%%% publication of submissions until I can get caught up. Thanks for
%%% your patience.
%%% Malcolm
------------------------------
Date: Fri, 24 Jun 88 14:09 PST
From: <MIKE%UCDHEP.BITNET@Forsythe.Stanford.EDU> (Mike Hannon; UCD Physics)
Subject: Equation labelling in LaTeX
The TeX command:
$$ \eqalign{
x &= y, \cr
u &= v.} \eqno(4) $$
produces a pair of equations with the equation number, in this case, 4,
appearing on a line midway between the two equations, something like:
x = y,
(4)
u = v.
except, of course, that there is not so much space between the equations.
Is there some way to do this in LaTeX? The eqnarray environment seems to
put the equation number directly opposite one of the equations. This is
logically equivalent, I suppose, but seems somehow not as pleasing to the
eye.
Thanks.
- Mike Hannon
MIKE@UCDEP (Bitnet)
UCDHEP::MIKE (HEPnet)
(916)-752-4966 (Telephone)
------------------------------
Date: Sat, 25 Jun 88 21:29:00 EDT
From: jonradel%icecream.Princeton.EDU@Princeton.EDU (Jon Radel)
Subject: MakeIndex on IBM PC
I've made an executable of MakeIndex v2.4 (found on ucbarpa.berkeley.edu
in April 1988) with Microsoft C v5.1. It is unable to process one of the
sample files that came with the source (the book index), and according to
another user, seems to be limited to about 900 entries. Does anyone have
a feel for whether this is a code problem, compiler problem, or a limitation
inherent to 640K of RAM?
--Jon Radel
jonradel@icecream.princeton.edu
------------------------------
Subject: LaTeX figure captions vs line buffer size
Date: Sun, 26 Jun 88 18:33:43 EDT
From: Jean-Francois Lamy <lamy%ai.toronto.edu@RELAY.CS.NET>
When constructing the .aux file, LaTeX writes out captions as a single line.
A large caption will easily exceed the default maximal line length of 500
characters (Unix TeX, web2c C version), especially if it is the least bit
mathematical. As a workaround, we have increased the default value of the
line buffer size up from 500 to a few thousands (to allow for 1/3 of a mammoth
page :-). Maybe someone can figure out how to get LaTeX to break long
captions...
Jean-Francois Lamy lamy@ai.utoronto.ca, uunet!ai.utoronto.ca!lamy
AI Group, Department of Computer Science, University of Toronto, Canada M5S 1A4
%%%%%%%% file bug.tex
\documentstyle[11pt]{article}
\begin{document}
\begin{figure}
\caption{
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu
uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu uuuuuuuuu}
\label{uuuu}
\end{figure}
\end{document}
%%%%%%%%%%%%%%%% the very latest LaTeX fails to process the document as follows
This is TeX, C Version 2.9 (preloaded format=lplain 88.6.25)
(/tmp/lamy/bug.tex
LaTeX Version 2.09 <26 Apr 1988>
(/usr/local/lib/tex/macros/article.sty
Document Style 'article'. Released 23 September 1985
(/usr/local/lib/tex/macros/art11.sty)) (eem.aux
Unable to read an entire line---bufsize=500
------------------------------
Date: 26 Jun 1988 23:00:43 EST
From: dragon@NSCVAX.PRINCETON.EDU (Richard B. Gilbert)
Subject: Directory pointers
>Is there any way (preferably EASY) to change the directory pointers within a
>LaTeX document under Vax/VMS or is the logic of LaTeX inappropriate for such a
>change?
>For example, if a \documentstyle[option] resides in your current directory
>(say, [BED.GDG]) as OPTION.STY, then [BED.GDG]OPTION.STY is used for the LaTeX
>run; if it does not reside in the current directory, then the system default
>TEX$INPUTS:OPTION.STY is used. Is there any way to customize a run such that a
>user can establish their own specified subdirectory (say, [BED.GDG.STYLES])
>such that the logic of LaTeX is changed to check, in sequence, the current
>directory, a user-specified default directory, then the system default
>directory?
The simplest thing to do is to redefine the logical name (that's a
path-name or an environment variable for you non VMS types) TEX$INPUTS.
Version 4.0 and up of VMS allow the equivalence name to be a list of
directories, called a search list. You could use something like the
following to get a search of the directories you want in the order
specified:
$ DEFINE /USER TEX$INPUTS DUA0:[BED.GDG.STYLES], -
DUA0:[FOO.BAR], -
DUA1:[TEX.INPUTS]
The /USER qualifier makes your definition go away after being used once;
the next time you refer to TEX$INPUTS, you get the original definition.
Omit the /USER if you want your definition to be effective for the entire
session.
------------------------------
Subject: Need reference to metafont fix for \Leftarrow, \Rightarrow
Date: Wed, 22 Jun 88 08:54:56 -0700
From: kelem@aerospace.aero.org
I heard that there is a fix to the metafont description of \Leftarrow
and \Rightarrow (the horizontal lines have "stair steps" in them).
Can you point me to the fix?
Thanks,
Steve Kelem
The Aerospace Corporation
------------------------------
Date: Mon, 27 Jun 88 16:26:32 PLT
From: Dean Guenther <GUENTHER%WSUVM1.BITNET@Forsythe.Stanford.EDU>
Subject: TUG IX
The ninth annual TeX Users Group meeting is in Montr/'eal this summer.
This year's meeting is the biggest yet, with speakers from Canada,
the United States, Japan, Israel, Australia and Finnland.
Following is the program
for this year's meeting. Hope to see you there.
-- Dean Guenther
Program Coordinator
-----------------------------------------------------------------
TeX USERS GROUP
McGill University, Montr\'eal
August 21--24, 1988
Updated Program as of June 17, 1988
Sunday -- August 21
7:30--10:15pm Dinner/Cocktails -- Le Festin du Gouverneur
Monday -- August 22
7:45--9:00 Registration
8:00--9:00 Introduction to TeX and TUG -- Bart Childs
9:00--9:15 Introductions: officers, site coordinators, etc.
TeX in Production: In-House Systems
9:15-9:45 Producing NASA Technical Reports with a TeX-based
typesetting system -- Mary McCaskil
9:45-10:15 TeX in an integrated system development
environment -- Tom Renfrow
10:15-10:30 break
10:30-11:00 Using TeX to control departmental documentation
--David Ness and James Slagle
11:00-11:30 Producing families of manuals from the
same sources -- LaurieMann
11:30-1:00 lunch
1:00-1:30 Using TeX to produce government standard
documentation -- Jean Pollari
TeX in Production: Case Studies
1:30-2:00 Implementing TeX in a production environment -- Eric Jul
2:00-2:30 An experience in textbook production -- James Mooney
2:30-3:00 Using TeX to produce kennel club year books -- Robert Harris
3:00-3:15 break
TeX in Production: TeXnical Solutions
3:15-3:45 A page layout design to facilitate production
-- Elizabeth Barnhart and David Ness
3:45-4:15 How and why a trade typesetter chose TeX -- Alex Warman
Orientation
4:15-4:45 Things to do in and around Montr\'eal
4:45-5:30 TUG's educational activities: courses, outlines, syllabi,
milestones, and future -- Bart Childs
5:30-??? Wine & Cheese -- hosted by Personal TeX
5:30-??? Birds-of-a-Feather sessions for sites (DG, CMS, MVS, CDC,
UNIX, VMS, etc.; during and after the Wine & Cheese)
Tuesday -- August 23
8:30-10:30 Output device manufacturer/exhibitor presentations
(Tentative listing based on 1987 participation)
Varityper Corp.; H. St\"urtz AG; TeXT1; TeXnology, Inc.;
Talaris Systems Inc.; Personal TeX; K-Talk Communications;
Kellerman & Smith; Imagen Corp.; ftl systems Inc.;
Docusoft Publishing Technologies; Arbor Text, Inc.;
Digital Composition Corp.; Computer Composition Corp.;
Autologic, Inc.
10:30-10:45 break
10:45-11:30 Site coordinators' status reports
VAX (VMX) -- Barry Smith; UNIX -- Pierre Mackay;
Small Systems -- Lance Carnes; Prime -- John Crawford;
IBM VM/CMS -- Dean Guenther; IBM MVS -- Craig Platt;
Data General -- Bart Childs; CDC Cyber -- Jim Fox
11:30-1:00 lunch
TeX Training
1:00-1:30 TeX tips for getting started -- Berkeley Parks
1:30-2:00 The art of teaching TeX for production -- Alan Wittbecker
2:00-2:30 Comercial use of TeX: experiences of a consultant
-- Arthur Ogawa
2:30-3:00 Choosing between TeX and LaTeX -- Shawn Farrell
3:00-3:15 break
3:ea
Non-English TeX
3:15-3:45 Mathematics textbook publishing with Japanese TeX
-- Nobuo Saito and Kazuhiro Kitagawa
3:45-4:15 SemiTeX: limited support for semitic languages
-- Jacques Goldberg
4:15-4:45 TeX is multilingual -- Michael Ferguson
4:45-5:15 Experiences with TeX in Finland -- Kauko Saarinen
5:15-5:45 DVI driver standards update -- Robert McGaffey
5:45-??? Topical Birds-of-a-Feather sessions
(LaTeX, graphics, fonts, etc.)
Wednesday -- August24
TeX and SGML
8:30-9:00 Using the Emacs editor to safely edit TeX sources and
translate SGML into TeX -- Stephan von Bechtolsheim
9:00-9:30 Using SGML and TeX to produce useredocumentation
-- Lynne Price
TeXnical Support
9:30-10:00 Previewers -- Ken Yap
10:00-11:30 TUG business meeting
11:30-1:00 lunch
TeXnical Support
1:00-1:30 Software for technical book production -- Robert Kruse
1:30-2:00 CapTeX: industrial strength TeX -- Mike Schmidt
2:00-2:30 FaSTeX -- Paul Muller
2:30-2:45 break
2:45-3:45 TeX problems help session -- Barbara Beeton et al.
3:45-4:15 Report from the training standards committee
4:15-4:30 General wrap-up and closing -- Bart Childs et al.
Program coordinator: Dean Guenther -- Washington State University
Committee: Christina Thiele -- Carleton University;
Shawn Farrell -- McGill University
------------------------------
Subject: Re: Directory pointers? [VMS logical name search lists]
From: adk%FSU.BITNET@CUNYVM.CUNY.EDU
Date: Tue, 28-JUN-1988 14:07
In TeXhax Volume 88, Issue 57 (Friday, June 17, 1988) George Greenwade
asked if one could use a search path to find TeX or BiBTeX input files
under the VAX/VMS operating system.
Date: Fri, 10 Jun 1988 11:22:52.33 CST
From: <bed_gdg@shsu.bitnet> (George D. Greenwade)
Subject: Directory pointers?
Is there any way (preferably EASY) to change the directory
pointers within a LaTeX document under Vax/VMS or is the
logic of LaTeX inappropriate for such a change?
The answer is yes, and it is very easy. The TeX and BiBTeX input files
are pointed to by the VMS logical name TEX_INPUTS, so all you need do
is to make this logical name into a search list. For example, on our
system TEX_INPUTS is defined as
$ DEFINE TEX_INPUTS TEX_ROOT:[LOCAL.TEX], TEX_ROOT:[INPUTS]
so (after looking in the default directory) TeX looks for \input files
in TEX_ROOT:[LOCAL.TEX], and if it doesn't find anything it likes
there then it proceeds to look in TEX_ROOT:[INPUTS].
[[Technical note: The way that TeX searches for files is of course
part of TeX's "system dependencies," and therefore depends upon which
port of TeX to VAX/VMS you are using. On our system we use the
Kellerman and Smith port of TeX (VAX/VMS Version 2.0.0).
The handling of search lists is done by VMS, so nothing special has to
be done by TeX itself other than to invoke the system service routine
$SEARCH.
Our local version of BibTeX (SCRI VAX/VMS Version 0.98i.0.2) is a
modification of the Kellerman & Smith Version 0.98i.0 to include the
necessary $SEARCH call so that search lists are understood by BiBTeX
too.
By the way, does anyone have a reason why VMS versions of TeX
shouldn't use LIB$FIND_FILE instead of $SEARCH and $PARSE?]
------------------------------
Date: Tue, 28 Jun 88 15:33:04 GMT
From: Sebastian Rahtz <spqr%CM.SOTON.AC.UK@Forsythe.Stanford.EDU>
Subject: TeX in C
Has anyone else encountered these two problems with TeX in C?
a) The TEXINPUTS environment variable is fossilized after an 'undump'
(though it works normally with a 'virtex');
b) The 'web2c' program fails with a 'Syntax error' when converting Metafont.
I'm running a version of webtoc fetched from Washington in May on a Sun 3
(OS version 3).
sebastian rahtz
computer science
university
southampton
UK
------------------------------
Date: Tue, 28 Jun 88 16:46:03 EST
From: i5f@l.cc.purdue.edu (S Bechtolsheim)
Subject: How to become a technical writer
Do universities or colleges offer courses in "technical writing".
Somebody from Germany asked me whether there is a way in the US
to "study" technical writing. Do English departments offer special
training in that? At least at Purdue I never heard of the possibility
to study technical writing.
Any feedback would be welcome. Thank you very much.
Stephan
------------------------------
Date: 28 Jun 1988 22:36:02 EST
From: dragon@NSCVAX.PRINCETON.EDU (Richard B. Gilbert)
Subject: \bf{bold}
>\item{1)} Even though this should be in \bf{bold} this should not!
>All the text after \bf{bold} is also in bold.
That is exactly the way I would expect it to work. If you want only the
word "bold" to be in boldface, try {\bf bold} which limits the scope of the
boldface command.
------------------------------
Date: Wed, 29 Jun 88 00:13:17 EDT
From: dow@wjh12.harvard.edu (Dominik Wujastyk)
Subject: Beebe's DVIEPS.C on the PC/AT
Has anyone done the work necessary on Nelson Beebe's DVIEPS.C to make it
run satisfactorily on an IBM PC or AT? If so, *please* mail me the code
or diffs. I'm trying to get an Epson driver going so that I can release it
to local BBS people who are eager for it. I heard that someone who
released a PD TeX distribution (announced here in TeXhax some months back)
had done this, but I can't follow that up.
The same goes for Beebe's DVITOS.C.
Alternatively, does anyone know of other Epson and/or Toshiba drivers in the
pd, or being freely distributed.
All and any help very much appreciated.
Dominik Wujastyk
bitnet: user DOW on the bitnet node HARVUNXW
arpanet: dow@wjh12.harvard.edu
csnet: dow@wjh12.harvard.edu
uucp: ...!ihnp4!wjh12!dow
------------------------------
Date: Wed, 29 Jun 88 00:37:08 EDT
From: dow@wjh12.harvard.edu (Dominik Wujastyk)
Subject: DVIEW
I too discovered DVIEW on Simtel20. It really is a very good previewer
indeed, one of the best. It supports several IBM/clone screen types
(including 640x400), allows a screen dump to a printer, scrolls very
smoothly, shows a zoomed out/greeked version of the page, etc., etc.
But it only reads .PXL fonts in its present release (ver. 2.5).
A few months ago I contacted the creator of DVIEW, Professor
Steve Ward of MIT, and talked to him about this. Strangely, he seemed to be
unaware of teh .PK format. So I sent him full documentation (from the WEB
files) on PK and other file formats, and the full DVI family by Beebe. This
contains modular C code for reading all the font formats, and since DVIEW is
in C, Ward said this would greatly help.
Steve Ward is a *very* busy man. His latest word is that he hopes to produce
the next release of DVIEW in mid July, and it will read PK. At that point
we (on PCs) should all jump up and down, cheer, and get ourselves free copies
of DVIEW. My feeling is that he will progress fastest if we leave him
alone.
Oh yes, there was one other drawback to DVIEW: it needed its own set of fonts
at the screen resolution, like the Arbortext previewer used to. DVIEW 2.5
can't just read and convert the fonts that are already there for your printer.
So it means extra storage space, and decisions about which fonts one uses most
often, etc. And Metafont. Hey! Don't grimace. Using MF to churn out a set
of CM fonts at a different resolution or size is *easy*!
Dominik Wujastyk
------------------------------
Date: Tue, 28 Jun 88 10:21 EST
From: <RICH%SUHEP.BITNET@Forsythe.Stanford.EDU>
Subject: Changing TeX$input under VMS
George D. Greenwade asks:
>> Is there any way (preferably EASY) to change the directory pointers within a
>> LaTeX document under Vax/VMS or is the logic of LaTeX inappropriate for such
>> a change?
Easy? It's positively trivial. At least, it is for plain TeX and I assume
it's the same for LaTeX. All you have to do is use a VMS command to redefine
TeX$inputs; make it a search string that starts with the subdirectory you use
for TeX macros, then goes on to the system's TeX directories. You can then run
TeX from anywhere in your directory tree, and it will find your \input files.
Well, maybe it isn't that trivial. You certainly don't want to type in such a
long command every time; probably you'd put it in your login.com file. And, of
course, if the system manager changes the organization of the TeX directories,
and you don't change your definition of TeX$inputs, then everything will cease
functioning for you.
Here's a better way: I put the following into a file called TeXin.com:
================================= CUT HERE ===================================
! TeXin.com -- adds a directory at the head of the TeX$inputs search list
! Usage:
! $ @TEXIN directory
! Rich Holmes (rich@suhep.bitnet) August 1987
!
$ n = f$trnlnm ("TEX$INPUTS",,,,,"MAX_INDEX")
$ x :==
$ loop:
$ x == "," + f$trnlnm ("TEX$INPUTS",,N) + x
$ n = n - 1
$ IF n .GE. 0 THEN GOTO loop
$ define/nolog tex$inputs 'p1''x'
================================= CUT HERE ===================================
Then in my login.com file I put:
$ TeXin [Rich.TeX]
which builds a new search list for TeX$inputs, beginning with [Rich.TeX] and
continuing with whatever the current system standard is.
Rich Holmes
Richard S. Holmes Phone: (315)423-3891 or
Physics Department -2701
Syracuse University BITNET: Rich@SUHEP
Syracuse, NY 13244
------------------------------
Date: Wed 29 Jun 88 01:10:07-EDT
From: b beeton <BNB@SEED.AMS.COM>
Subject: unending \bf; texhax 88#59
in b holmes' query, the fact that \bf{bold} does not ``turn off'' is
cited as a bug. mr. holmes, please read page 13 of the texbook. near
the bottom of that page, the proper syntax {\bf bold} is clearly shown,
along with an introduction to the idea of ``grouping''. i apologize for
being brusque, but the use of the word ``bug'' in the subject of your
message is uncalled for. tex is remarkably free of bugs, and though
several new ones have been found recently, the finders had to work very
hard indeed to demonstrate them! any problem at the level you cite
would have been filtered out long, long ago.
-- barbara beeton
------------------------------
Date: Wed 29 Jun 88 01:18:00-EDT
From: b beeton <BNB@SEED.AMS.COM>
Subject: no hyphenation after a hyphen
knuth's decision to ignore the possibilities for hyphenation after an
explicit hyphen (or after any embedded control sequence, for that matter)
was intentional, if inconvenient at times. he explained his reasoning
at a tug meeting q&a session several years ago, and though i've forgotten
why, here's the recommended workaround.
instead of typing the explicit - use \hyph and define it thus:
\def\hyph{-\penalty0\hskip0pt\relax}
the penalty plus skip allows a break, but 0pt leaves no space. the \relax
protects against the possibility that the following word begins with
`plus' or `minus', which would get gobbled. depending on your sense of
style and the exigencies of your prose, you may find it useful to define
\slash in a similar way, replacing the - by / .
-- bb
------------------------------
Date: Wed, 29 Jun 88 13:37:47 MEZ
From: UNM406%DBNRHRZ1.BITNET@CUNYVM.CUNY.EDU
Subject: Driver for EPSON LQ500, NECP6
Does there exist a (free or commercial) DVI driver for an IBM-PC or
compatible, which supports 180x360 dpi on an EPSON LQ500
(resp. 360x360 dpi on the NEC P6) ?
I haven't seen better than 180x180 for both.
If you know how to get such a thing I would be glad to get the address;
if no such driver exists I am curious to know why not, and would be happy
to find somebody to explain the problems.
Thanks Thomas
unm406.dbnrhrz1 in EARN/BITNET.
------------------------------
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%% BITNET: send a one-line mail message to LISTSERV@TAMVM1.BITNET:
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%%
%%% All others: send mail to
%%% texhax-request@score.stanford.edu
%%% please send a valid arpanet address!!
%%%
%%%
%%% All submissions to: texhax@score.stanford.edu
%%%
%%% Back issues available for FTPing as:
%%% machine: directory: filename:
%%% [SCORE.STANFORD.EDU]<TEX.TEXHAX>TEXHAXnn.yy
%%% nn = issue number
%%% yy = last two digits of current year
%%%\bye
%%%
------------------------------
End of TeXhax Digest
**************************
-------