TeXhax@cs.washington.edu (TeXhax Digest) (07/09/90)
TeXhax Digest Sunday, July 8, 1990 Volume 90 : Issue #51
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:
Changes files for Turbo pascal to Weave 4.1 and Tangle 4.0 WANTED
DVI to LaserJet
FMittelbach's macros
unretex
request for LaTex
numbering lines in LaTeX
Phonetic Symbols
Euler Fonts
Nelson Beebe's reply to DVIALW landscape mode inquiry
Graphics and Memory Problems
Dealing with unwanted \outer-ness
Re: TeX files corruption over networks (TeXhax #48)
SPLAIN for TeX3.0
--------------------------------------------------------------------------
Date: Thu, 14 Jun 90 21:12:14 +0200
From: Hans Vindvad <vindvad@solan.unit.no>
Subject: Changes files for Turbo pascal to Weave 4.1 and Tangle 4.0 WANTED
Keywords: Turbo Pascal, Weave, Tangle, change files
I am using WEAVE and TANGLE together with Turbopascal 5.5 and is Interested
in upgrading to the latest version
Does anyone have Change files for Tangle 4.0 and Weave 4.1 to be ussed
to build Tangle and Weave for Turbopascal?
Hans Vindvad
Internet: vindvad.solan.unit.no
Bitnet: hvindvad AT norunit
----------------------------------------------------------------------------
Date: Fri, 08 Jun 90 16:31:15 BST
From: Ivan Fabian <IGBF%IB.RL.AC.UK@UWAVM.ACS.WASHINGTON.EDU>
Subject: DVI to LaserJet
Keywords: dviware
Does anyone out there know of a DVI to LaserJet driver
that will run on an IBM Mainframe running CMS.
If so please either send it or let me know how to get
hold of it.
Regards
Ivan Fabian
Rutherfor Appleton Lab
---------------------------------------------------------------------------
Date: Fri, 8 Jun 90 11:15:36 PDT
From: ogawa@saturn.arc.nasa.gov
Subject: FMittelbach's macros
Keywords: FMittelbach's macros
Frank has had several articles published over the last year or so in TUGboat.
I would like related .sty files, particularly the DOC tool. In the latest
TUGboat (11/1) he has an article documenting a new approach to fonts. I would
like to obtain the related source files here, too. Any clue on the distribution
of these things? I did notice there was a statement not to ask for individual
distribution. Are they only obtainable from the german archives?
Any help would be appreciated ;-) Art Ogawa
ogawa@sat.ames.nasa.gov
-------------------------------------------------------------------------------
Date: Thu, 07 Jun 90 14:42:57 MEZ
From: Erich Neuwirth <A4422DAB%AWIUNI11@UWAVM.ACS.WASHINGTON.EDU>
Subject: unretex
Keywords: Unretex
Somebody asked for a copy of MSDUS unretex.
This program removed TeX controlsequences to prepare
TeX files for spellchecking and cann add these sequences
afterwards.
Unretex can be retrieved from LISTSEV@dhdurz1.bitnet
ERICH NEUWIRTH
A4422DAB at AWIUNI11 in BITNET
Intitute for Statistics and Computer Science
UNIVERSITY OF VIENNA, UNIVERSITAETSSTR. 5/9, A-1010 VIENNA, AUSTRIA
-------------------------------------------------------------------------------
Date: Wed, 13 Jun 90 16:33:32 mdt
From: esunix!sim.dnet!kpoppleton@cs.utah.edu
Subject: request for LaTex
Keywords: LaTeX
I am looking for the latest release of LaTex and associated support files.
Are the ports avaible for Sun 3 and Sun 4 machines? I am also looking for
the dvi previewers for SUNVIEW and X. And the dvi converters to postscript
and Digital LN03 printers.
Thank you for any information
Ken Poppleton (Evans & Sutherland Computer Corp)
-------------------------------------------------------------------------------
Date: Fri, 8 Jun 90 13:59:13 -0400
From: kesich@acf4.NYU.EDU (John Kesich)
Subject: numbering lines in LaTeX
Keywords: LaTeX, numbering
I have a user who is editing a medieval manuscript.
He needs to have the lines numbered continuously (every 5th or 10th line)
in the left-hand margin.
Although it seems this should be easy to do, I have so far had no luck.
Any suggestions would be appreciated.
Thanks.
-----------------------------------------------------------------------------
Date: Wed, 6 Jun 90 10:11:29 PDT
From: awslawson@ucdavis.ucdavis.edu (Wayne Slawson)
Subject: Phonetic Symbols
Keywords: TeX, LaTeX, Phonetic Symbols
Has anyone heard of fonts for phonetic
symbols in TeX? If so, has anyone
encorporated them into a LaTeX command?
Wayne Slawson, Music Dept. UC Davis
awslawson@ucdavis.edu
------------------------------------------------------------------------------
Date: 6 Jun 90 15:28 -0600
From: Jim Walker <walkerj@wnre.aecl.ca>
Subject: Euler Fonts
Keywords: Euler Fonts
Can I obtain (and if so where from) the .mf files for the Euler fonts?
Jim Walker
---------------------------------------------------------------------------
Date: Mon, 4 Jun 90 08:22:43 EDT
From: WAS@UACSC1.ALBANY.EDU
Subject: Nelson Beebe's reply to DVIALW landscape mode inquiry
Keywords: dvialw.ps, landscape mode
In reference to the question that I posted recently about how to access
landscape mode using the DVIALW driver on a PostScript printer, Nelson Beebe
sent me the following response.
From: IN%"Beebe@science.utah.EDU" "Nelson H. F. Beebe" 2-JUN-1990 10:59:13.76
>> I've noticed that you make reference to landscape mode in the
>> dvialw.ps file. Could you please tell me how to access this
>> mode?
In the 2.10 drivers, this is somewhat inconvenient. First, the
page clipping bounds in dvialw.c, XPSIZE and YPSIZE need to be
enlarged (the current distribution version has done this, but
earlier ones have not). Next, you need to use a private version
of dvialw.ps in which the /BOJ macro is redefined so that
userdict /note known
{NOTE} % default page format for ALW
{userdict /letter known
{LETTER} % default page format for others
becomes
userdict /note known
{LANDSCAPE} % default page format for ALW
{userdict /letter known
{LANDSCAPE} % default page format for others
In the 3.0 DVI development, this has been greatly simplified, but
source release is far off yet.
----------------------------------------------------------------------------
Date: Fri, 8 Jun 90 15:47:13 EDT
From: parzen%jimmy@bess.HARVARD.EDU (Michael Parzen)
Subject: Graphics and Memory Problems
Keywords: TeX, memory
We are using the fig program to produce epic and psfig output.
Unfortunately, some of the pages we want to produce cause TeX to
produce an out of memory error. Since we are usually the only users
on a 16meg Sun386i, is it possible to hack TeX to allow more than
65531 bytes per page (or whatever it is doing right now). All the
log file says to do is se your local wizard.
Thanks,
Mike Parzen
parzen@jimmy.harvard.edu
--------------------------------------------------------------------------
Date: Tue, 05 Jun 90 22:53:32 BST
From: Chris Thompson <CET1@phoenix.cambridge.ac.uk>
Subject: Dealing with unwanted \outer-ness
Keywords: TeX, \outer
In TeXhax digest #48, Michael Barr provides a solution to a problem
of John de Pillis which involves defining a macro whose expansion
includes \newcount, which is defined in plain.tex as \outer. Michael's
circumvention is to copy the definition from plain.tex (without the
\outer), but this involves having to fiddle around with \catcode`\@
and is in any case not robust against the definition being changed
(by a macro package on top of plain.tex, or in plain.tex in some
subsequent release).
This problem with \outer macros arises quite often, and perhaps the
following tricks are not as well known as they ought to be. To simplify
the original problem, suppose one wishes to define
\def\newc#1{\expandafter\newcount\csname CNT#1\endcsname}
As all that TeX is objecting to is that \newcount is \outer at the time
the \def is obeyed, one solution is
{\let\newcount=\relax % locally
\gdef\newc#1{\expandafter\newcount\csname CNT#1\endcsname}
} % \newcount reverts
An alternative, which doesn't assume that we are currently at the
\global nesting level, is
\edef\newc#1{\noexpand\expandafter\noexpand\newcount
\noexpand\csname CNT#1\endcsname}
% all expandable tokens have been prefixed by \noexpand
because \noexpand suppresses the \outer-ness of its argument.
In more complicated cases, \outer tokens may also cause trouble because
they occur in conditionally skipped text, or in inner definitions
(i.e. \def's *obeyed* when the outer macro is *expanded*). The useful
technique here is to be able to define a \inewcount which behaves just
like \newcount when expanded, but is not \outer. Here is one way of
doing that:
\edef\inewcount{\noexpand\newcount}
If you know that \newcount is a macro without arguments (as is, rather
suprisingly, the case---see TeXbook Appendix B) then you can copy its
expansion by
\expandafter\def\expandafter\inewcount\expandafter{\newcount}
and you are then protected against \newcount being redefined later in
this run of TeX, but at the expense of having to have known more about
\newcount than you should. You can even use this last technique to
redefine \newcount itself as `just the same as before, except not
\outer'.
Chris Thompson
JANET: cet1@uk.ac.cam.phx
Internet: cet1%phx.cam.ac.uk@nsfnet-relay.ac.uk
------------------------------------------------------------------------------
Date: Wed, 06 Jun 90 00:34:00 BST
From: Chris Thompson <CET1@phoenix.cambridge.ac.uk>
Subject: Re: TeX files corruption over networks (TeXhax #48)
Keywords: TeX, corruption, networks
In Texhax digest #48, Jacques Goldberg discusses the (very real)
problems with transmitting TeX input over networks, and suggests
(more or less mechanically) replacing dangerous characters by a \char
construct. Unfortunately, this suggestion is not very useful, as `\char
<number>' is only semantically equivalent to the corresponding character
token in a very few TeX contexts: they are never equivalent as tokens
(i.e. from the point of view of macros), nor equivalent at all unless
the category code is 11 or 12, nor will category-code-11 characters
(`letters') that themselves occur in control sequence names work (very
relevant for people using the new 8-bit extensions of TeX to map ISO
Latin 1, for example).
The TeX mechanism that works at the `lexical' (pre-tokenisation) level,
and is not subject to these objections, is that which converts ^^
followed by a character (or now, in TeX 3.0, followed by two hex
digits) into a single character. However, there are problems even with
this: it depends on ^ having category code 7 (in fact, the exact rule
is: a pair of identical characters with category code 7, followed by
etc.---see page 47 of the TeXbook), and it is far from unknown to change
this. For example, manmac.tex makes it an active character (category
code 13). Also, of course, circumflex is itself notoriously one of the
characters liable to be mangled.
Provided there is at least one character which does not occur in the
document AND can be transmitted over the network (a rather optimistic
assumption, unfortunately) then this character can be given category
code 7 and used to escape all the others. (Provided that 0..9 and a..f
can get through...) Of course, after all this you will probably have to
worry about whether the network can handle the enormously long lines you
have generated!
From a pragmatic point of view, I think that currently people should be
advised to use only 95-character ASCII (no *tabs*, please!) in TeX
documents intended for exchange, using the ^^ mechanism (or any other
of their choice) for characters in the ranges "00.."1F and "7F.."FF. On
the other hand, if the transmission medium isn't up to handling even
these 95 characters, then it is probably better to fall back on a
general mechanism (hex pairs, if the worst comes to the worst) rather
than making heroic efforts to perform the transformation within TeX.
My thanks to Jacques for providing yet-another-EBCDIC-to-ASCII-
translation-table! (Well, I admit this one wasn't really new to me:
it is NIFTP-but-with-circumflex-and-tilde-like-XLATE, or NUMAC-before-
the-change. I don't approve of translating bad characters into NULL,
by the way: that's what SUB is for.) I would strongly urge everyone
involved in IBM user groups to support the efforts (so far unsuccessful)
of SHARE and SEAS to get IBM to settle on a single EBCDIC-to-
(ISO-Latin-1) translation table, preferably one based on "Code Page 37".
Chris Thompson
Cambridge University Computing Service
JANET: cet1@uk.ac.cam.phx
Internet: cet1%phx.cam.ac.uk@nsfnet-relay.ac.uk
PS. If Jacques can have one, so can I... When he says
> Fortunately "XYZperts" know a feature to correct that even without
> altering this table ( SET INPUT 4A E0 in this case).
...XYZ has suddenly become "CMS" instead of "IBM". There *are* other
operating systems on IBM machines, you know.
------------------------------------------------------------------------------
Date: Thu, 14 Jun 90 16:49:17 -0700
From: mackay@cs.washington.edu (Pierre MacKay)
Subject: SPLAIN for TeX3.0
Keywords: Splain, TeX
This is a diff file to convert Dominik Wujastyk's lplain.tex
into splain.tex. You should do this if at all possible, since
splain.tex has not kept up with lplain.tex over the years, and
has acquired a lot of cruft. Use patch, if you have it.
Email: mackay@cs.washington.edu Pierre A. MacKay
Smail: Northwest Computing Support Center TUG Site Coordinator for
35F Thompson Hall, Mail Stop DR05 Unix-flavored TeX
University of Washington
Seattle, WA 98195
(206) 543-6259
%--------------------------------------------------------------
*** lplain.tex Thu Jun 14 08:58:02 1990
%--- splain.tex Thu Jun 14 09:00:23 1990
***************
*** 1,3 ****
%--- 1,6 ----
+ % File SPLAIN.TEX - Originally created 11 October 1987
+ % - Modified June 14, 1990 by Pierre MacKay to
+ % track all changes in file LPLAIN up to February 8, 1990
% File LPLAIN - Created 29 October 1985 from plain version 1.5CM
% - Last modified 20 October 1988 to take into account
% changes to PLAIN.TEX reported by Arthur Ogawa
***************
*** 5,13 ****
% match the PLAIN.TEX meant for TeX 3.0 (\fmtname{plain},
% \fmtversion{3.0}).
%
! % This is the LaTeX version of the plain TeX format that's described in
% The TeXbook. All modifications can be found by searching for
! % the word 'LaTeX'.
% N.B.: A version number is defined at the very end of this file;
% please change that number whenever the file is modified!
% And don't modify the file under any circumstances.
%--- 8,16 ----
% match the PLAIN.TEX meant for TeX 3.0 (\fmtname{plain},
% \fmtversion{3.0}).
%
! % This is the SliTeX version of the plain TeX format that's described in
% The TeXbook. All modifications can be found by searching for
! % the word 'LaTeX' or 'SliTeX'.
% N.B.: A version number is defined at the very end of this file;
% please change that number whenever the file is modified!
% And don't modify the file under any circumstances.
***************
*** 406,412 ****
% For example, if another set of macros says "\font\ninerm=cmr9",
% TeX will not have to reload the font metric information for cmr9.
! % LaTeX font definitions are taken from the file LFONTS.TEX,
% so all of PLAIN's font definitions are commented out.
%\message{fonts,}
%--- 409,415 ----
% For example, if another set of macros says "\font\ninerm=cmr9",
% TeX will not have to reload the font metric information for cmr9.
! % SLiTeX font definitions are taken from the file SFONTS.TEX,
% so all of PLAIN's font definitions are commented out.
%\message{fonts,}
***************
*** 1144,1150 ****
\newdimen\p@renwd
% LaTeX: following command is moved after the \tenex font is defined
! % by LFONTS
%\setbox0=\hbox{\tenex B} \p@renwd=\wd0 % width of the big left (
\def\bordermatrix#1{\begingroup \m@th
%--- 1147,1153 ----
\newdimen\p@renwd
% LaTeX: following command is moved after the \tenex font is defined
! % by SFONTS
%\setbox0=\hbox{\tenex B} \p@renwd=\wd0 % width of the big left (
\def\bordermatrix#1{\begingroup \m@th
***************
*** 1304,1327 ****
\def\showhyphens#1{\setbox0\vbox{\parfillskip\z@skip\hsize\maxdimen\tenrm
\pretolerance\m@ne\tolerance\m@ne\hbadness0\showboxdepth0\ #1}}
! % input LaTeX fonts and commands
! \input lfonts
\input latex
% LaTeX change: moved from above.
\setbox0=\hbox{\tenex B} \p@renwd=\wd0 % width of the big left (
! % LaTeX: default values
\normalbaselines
! % LaTeX: select 10pt font size and \rm style
! \xpt
!
\nonfrenchspacing % punctuation affects the spacing
\catcode`@=12 % at signs are no longer letters
! % LaTeX: File called LPLAIN
! % Identify the current format
! \def\fmtname{lplain}\def\fmtversion{2.09-February 8, 1990}
\typeout{Input any local modifications here.}
%--- 1307,1330 ----
\def\showhyphens#1{\setbox0\vbox{\parfillskip\z@skip\hsize\maxdimen\tenrm
\pretolerance\m@ne\tolerance\m@ne\hbadness0\showboxdepth0\ #1}}
! % input SLiTeX fonts and commands
! \input sfonts
\input latex
+ \input slitex
% LaTeX change: moved from above.
\setbox0=\hbox{\tenex B} \p@renwd=\wd0 % width of the big left (
! % SliTeX: default values
\normalbaselines
! \twentypt
\nonfrenchspacing % punctuation affects the spacing
\catcode`@=12 % at signs are no longer letters
!
! % SliTeX: File called SPLAIN
! % identify the current format
! \def\fmtname{splain}\def\fmtversion{2.09-June 14, 1990}
\typeout{Input any local modifications here.}
-----------------------------------------------------------------------
%%% 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
**************************
-------