[comp.text.tex] TeXhax Digest V90 #58

TeXhax@cs.washington.edu (TeXhax Digest) (09/05/90)

TeXhax Digest    Tuesday,  September 4, 1990  Volume 90 : Issue 58

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:         

                                   MTeX
                                   \pmod
                       DVI to LaserJet Plus printers
           Request for Information on TeX/LaTeX Utility Programs
                  MF mode def for IBM Personal Pageprinter
                     Wanted: Pascal-WEB-to-CWEB program
            FWEB 1.13: New for IBM-PC, updated for other machines
                   TeXserver gains reverse-address sanity

-----------------------------------------------------------------------------

Date: 	Thu, 26 Jul 90 12:42:00 EDT
From: SCHROEDER%UTORPHYS.bitnet@gpu.utcs.utoronto.ca
Subject: MTeX
Keywords: TeX, music, MTeX, MuTeX

     I have been exploring the MTex macros (distributed on this continent as
MuTeX).  The package produces elegant music score, but only single-staff.
This hamstrings it (I need to do a piano sonata, for instance).  The version
available from WUARCHIVE.WUSTL.EDU's simtel20 mirror is copyright 1987.  I
am very curious to know whether later versions exist, or whether anyone has
been able to tease the system into setting more ambitious score.
     I am Karl Schroeder at Schroeder@utorphys.

---------------------------------------------------------------------------

Date: Fri, 27 Jul 90 10:24:40
From: Mike Piff <PM1MJP@primea.sheffield.ac.uk>
Subject: \pmod
Keywords: TeX, \pmod


On p164 of The TeXBook it states that ``\pmod is to be used when `mod' occurs
parenthetically at the end of a formula.''

Just how literally this is to be taken is shown when it is not  placed  at  the
end  of  a  formula but at the beginning.  To see why this should be necessary,
suppose I wish to say that some values are taken (mod n), and wish the  spacing
to  agree  exactly with what is obtained in \pmod.  Then it would seem perverse
to have to type $({\rm mod}\,\,n)$ to achieve this, and more  natural  to  type
$\pmod n$.

OK, but now see what happens if TeX decides to break the line just before  math
on.  The previous line is not right justified.

Did DEK mean the above quotation  to  be  a  description  of  the  mathematical
circumstances in which \pmod is generally used, or as a warning that it  should
not  be  used  at  the  beginning  of  a  formula?   \pmod  is, of course, safe
mid-formula.

Do any other maths control words in Plain TeX start with \allowbreak?

Is this a bug or an annoying feature?

Mike Piff

-------------------------------------------------------------------------------

Date: Wed, 25 Jul 90 10:06 EDT
From: "Dr. Jim Walker @crnl" <WALKERJ%CRNL.AECL.CA@UWAVM.ACS.WASHINGTON.EDU>
Subject: DVI to LaserJet Plus printers
Keywords: dviware, LJ Plus

Does anybody know where I can get (for a VAX/VMS environment) a DVI to
Hewlett-Packard LaserJet II that can do either/both of

1) Raster Graphics integration.

2) Landscape Printing.

I have been using Nelson Beebe's excellent DVIJEP, but I now need to do
both of the above and DVIJEP can't do these.

Jim Walker.

---------------------------------------------------------------------------

Date: Thu, 26 Jul 90 08:59:53 -0400
From: HOOVER <anita@vax1.udel.edu>
Subject: Request for Information on TeX/LaTeX Utility Programs
Keywords: utility programs

	
     ***************************************************************** 
                          Request for Information
     ***************************************************************** 

     As a result of the presentation given by David Ness at the
     recent TUG meeting on utility programs for aiding TeX Users,
     there has been an interest to try to put together an article
     for TUGboat that lists existing utility programs and where
     you can get them.  We are asking for people to please provide
     as much information about particular utility programs you
     use.  Please use the following format for responding:

     Example 1:

     Program Name : s2latex
     Author : Van Jacobson of Lawrence Berkeley Laboratory
     Language : C and Lex
     Operating System : UNIX
     Description : convert Scribe input files to TeX/LaTeX input files
     Where did you get it? : science.utah.edu

     Example 2:

     Program Name : detex 
     Author : Kamal Al-Yahya, Stanford University
     Language : C
     Operating System : UNIX
     Description : a filter to strip TeX and LaTeX's commands from a
                   file
     Where did you get it? : I don't know originally, but you can
                             get a copy from me by mailing to
                             anita@vax1.udel.edu
    
     ***************************************************************** 

     Please send responses to anita@vax1.udel.edu.


     thanks in advance, 

     Anita Hoover
     University of Delaware

-----------------------------------------------------------------------------

Date:       Mon, 23 Jul 90 09:50:12 BST
From: Martin Ward <martin%easby.durham.ac.uk@UWAVM.ACS.WASHINGTON.EDU>
Subject: MF mode def for IBM Personal Pageprinter
Keywords: MF, mode def, IBM Personal Pageprinter

Does anyone have a Metafont "mode def" for an IBM 4216 020 Personal
Pageprinter (write-white engine)? The only write-white mode def I have is for
a Rioch and it doesn't look right!

                Martin.

My ARPANET address is:  martin%EASBY.DUR.AC.UK@CUNYVM.CUNY.EDU
OR: martin%uk.ac.dur.easby@nfsnet-relay.ac.uk  UUCP:...!mcvax!ukc!easby!martin
JANET: martin@uk.ac.dur.easby    BITNET: IN%"MARTIN@EASBY.DURHAM.AC.UK"

---------------------------------------------------------------------------

Date: Thu, 26 Jul 90 14:58:20 MEZ
From: RZTEX%DKNKURZ1.BITNET@CUNYVM.CUNY.EDU
Subject: Wanted: Pascal-WEB-to-CWEB program
Keywords: Pascal-WEB-to-CWEB program

For my diploma-thesis I have written a (Pascal-)WEB program to simulate
some kind of neural network. Now there is a possibility for me to
change from our host (VM/CMS) to a Unix-Workstation,
but that would require a C-Source, not a Pascal one.
I have heard about WEB2C and P2C, but that
seams to me not to be the right thing for my problem.
What I would like most is a Pascal-WEB to C-WEB translator, firstly
to understand further what my program does and secondly because
this program is still under development.

Does there exist such a utility, where, how to receive?
All help will be greatly appreciated!

   Johannes Mueller, University of Constance, West-Germany
                     email: <rztex@dknkurz1.bitnet>

------------------------------------------------------------------------------

Date: Mon, 23 Jul 90 17:17:32 EDT
From: krommes@ss01.pppl.gov (John Krommes)
Subject: FWEB 1.13: New for IBM-PC, updated for other machines
Keywords: FWEB, IBM-PC

     --- FWEB v. 1.1x: New for the IBM-PC; updated for other machines ---

			John A. Krommes
		     Princeton University

			 July 22, 1990

   FWEB, A WEB SYSTEM for FORTRAN, RATFOR, and C, is a powerful, flexible
software tool for developing and documenting source code. It contains a
powerful macro processor, handles multiple languages, and does Ratfor
statement translation directly into Fortran.  FWEB is provided free of
charge over the networks. It was initially announced in summer 1989 on the
mfe (now nersc) networks, and has been available on the international
networks since November, 1989.

   FWEB version 1.1 will be (finally) available beginning July 26. The
raison d'etre for this release is to get a version out to users of the
IBM-PC. It involves relatively major structural modifications to FWEB v. 1.0 
in order to accomodate the small pc memory. The present version for the 
pc can be compiled with both Borland's Turbo C compiler and Microsoft's C
compiler.  It has been tested slightly more thoroughly with Borland's.

   Although this is the first release for the IBM-PC, the bootstrap code
has been upgraded for the other supported machines/compilers as well.
Presently, these machines are

	ANSI (If your C compiler is FULLY ANSI, use this for unsupported
machines.)  
	APOLLO (**)
	DECstation
	IBM-PC
	MACINTOSH (*)
	MISC (Vanilla-flavored, for unsupported machines that aren't ANSI.)
	SILICON GRAPHICS IRIS
	SUN (SUN cc and GNU gcc)
	VAX

(*) means v. 1.1 has not yet been tested for this machine. You may save
yourself some trouble if you check with me before you download code for
starred machines. Of course, check with me in any event if you encounter
difficulties. 

(**) means that it's been tested, but there's difficulty because of a
compiler bug. Please check with me.

   Users have made FWEB work with a variety of other machines that are not
discussed here. If you're thinking of working with something not listed
above, check with me for the latest information. In all cases, your best
bet is probably to work with the gnu gcc compiler if you have it.

   NOTE: All users of FWEB should upgrade to this present version 1.13.
Various bugs have been fixed, features have been added, and the quality of
the error messages has been improved. The user's manual now contains both a
table of contents and a complete index, as well as more examples, and is
now approaching 100 pages in length. A make file is provided so it should
be easy to install this new version.  One significant new feature is the
ability to read a style file, analogous to the MAKEINDEX utility, that
enables one to customize various features of FWEB such as the appearance of
FWEAVE's index.

   The next major release of FWEB is ``scheduled'' for about January 1,
1991 (or whenever I catch up with my research, whichever comes last), at
which point I hope to complete the support for C++ and Fortran-90. (Most of
those features are already included in v. 1.1; however, they are as yet
undocumented.) In the meantime, as an ongoing exercise I will continue to
interact with users in order to make incremental improvements designed to
enhance portability, fix bugs, etc. If you decide to bring FWEB up on an
unsupported machine, PLEASE keep a detailed record of any modifications you
need to make so I can macro the source code up to support that machine in
the future.

   The files are available via anonymous guest ftp from Internet host

	ss01.pppl.gov,

a Sun Sparcstation running unix. (Formerly, they were available from
ccc.nmfecc.gov; that source has been turned off.)  In the following, let
$FWEB stand for the top-level public directory /pub/fweb/v1.13:

	$FWEB == /pub/fweb/v1.13

(This is, of course, symbolic notation, not standard unix.)  Then the files
are located in the areas $FWEB and, e.g., $FWEB/pc; for any particular
machine this is something over 2 Mbytes of text files. The top-level
directory $FWEB contains the web sources, user's manual, demos, make file,
etc. The underlying subdirectories contain bootstrap code for specific
machines/compilers. For example, the subdirectory $FWEB/pc contains
bootstrap C code for the IBM-PC. To get started, obtain and read the files

	$FWEB/READ_ME.FWEB
	$FWEB/pc/READ_ME.PC

For the user's manual, you need the files

	$FWEB/fwebman.tex
	$FWEB/index.tex
	$FWEB/indexmac.tex
	$FWEB/mx.sty

(The provided make file fweb.mk will build the manual for you if you say
``make fwebman''.)

   If you cannot use Internet anonymous guest ftp, you can alternatively
use the intermediary of BITFTP@PUCC.BITNET. Send to that address a mail
message with a valid ftp session; you will get your results back in the
mail (possibly uuencoded if the file is sufficiently large). An example of
such a session is

	ftp ss01.pppl.gov
	cd $FWEB
	get READ_ME.FWEB
	quit

The main fweb directory and each bootstrap subdirectory also exist as tar
files (compressed with 'compress'). Thus, there are files of the form
TAR.*.Z, for example

	$FWEB/TAR.v1.13.Z
	$FWEB/pc/TAR.pc.Z
	$FWEB/unix/sun/gcc/TAR.gcc.Z

etc. Thus, you can obtain a whole subdirectory with one get operation. If
you're a unix user, a simple make file /pub/fweb/FWEB_FROM_TAR.mk is provided
to recover the files from the TAR.*.Z files. To get all the files for the
IBM-PC, a sample ftp session is

	ftp ss01.pppl.gov
	cd /pub/fweb
	get FWEB_FROM_TAR.mk
	cd v1.13
	get TAR.v1.13.Z
	cd pc
	get TAR.pc.Z
	quit

Put these files in an otherwise empty directory you will use for your
experiments with FWEB. Then say ('V' for ``version'', 'M' for ``machine'')

	make -f FWEB_FROM_TAR.mk V=1.13 M=pc

Now rename the make file fweb.mk to Makefile. In principle, a unix user can
then say

	make bootstrap

to compile the *.c and *.h files,

	make fwebman

to get the manual, etc. It's best to try out these make operations first
with ``make -n ...''. For problems, see the READ_ME files and the
discussion at the beginning of the make file.

   Please let me know about any difficulties. Creating the pc version has
been a somewhat tedious exercise because of the segmented pointer
arithmetic on the pc; although I've tried to be careful, there may still be
some surprises. The SUN and VAX versions are in production locally, but if
you're a user of the IBM-PC, consider yourself a beta tester/pioneer. Be
sure to read $FWEB/pc/READ_ME.PC.

   Many thanks to Arnold Kritz for donating his time and pc for the
development of this version for the IBM-PC, and to Thorsten Ohl for expert
trans-oceanic help with debugging.

   Finally, I have been frequently unable to communicate with users whose mail
reaches me through UUNET. Your mail reaches me, but outgoing mail is
usually bounced back, and postmasters have been unable to help except to
tell me they're not surprised. Please try to provide me with an address
that does not involve UUNET.

   Due to vacation, I will be unable to answer mail about FWEB until about
August 12. But don't hesitate to ask questions, make suggestions, etc. I
maintain an email mailing list for FWEB-related announcements. If you'd
like to be on that, send me a message.

 --- John Krommes

	Internet: krommes@ss01.pppl.gov
			or
		  krommes%ss01.pppl.gov@ccc.nersc.gov
	MFEnet:   krommes@ss01.pppl.gov
	Bitnet:   krommes%ss01.pppl.gov@lbl.bitnet

ss01.pppl.gov == 192.55.106.129 (CHANGED RECENTLY);
ccc.nersc.gov (formerly ccc.nmfecc.gov) == 128.55.128.130.

---------------------------------------------------------------------------

Date: Tue, 24 JUL 90 15:41:04 BST
From: TEX@rmcs.cranfield.ac.uk
Subject: TeXserver gains reverse-address sanity
Keywords: TeXserver, Aston

     New facilities available at the UK TeX Archive mail server
     ==========================================================
     
One of the  commonest errors made by users of the  Aston University  TeX
archive mail server, <TeXserver@Uk.Ac.Aston.TeX> is to fail to provide a
correct return address in requests.  Very often, users forget to mention
the appropriate gateway  through which  the traffic  should be routed to
depart  from  the  UK.   As seen by  the user,  they aren't  getting the
service required:  from  TeXserver's viewpoint,  the message is sloshing
around somewhere under the computer room floorboards.

To avoid this problem,  and generally make TeXserver more friendly, I've
now   provided   preprocessing,   in   the  code   which  despatches  an
acknowledgement of the request back to the requestor.  This also removes
the requirement  to delimit  the  actual request  by means of  a line of
three hyphens.

Therefore,  you may now mail <TeXserver@Uk.Ac.Aston.TeX>  with a message
which starts  with a valid  TeXserver command (HELP,  DIRECTORY,  FILES,
WHEREIS  or SEARCH);  however,  this MUST be the first non-blank line of
the body  of your message  (TeXserver removes valid RFC-822 headers, but
see PS below).

If you prefer,  you may continue  to use  the old format  for  TeXserver
requests,  wherein  everything  is ignored  before the first line  which
commences with three hyphens: in this format, the following line must be
your return address as seen from  Aston,  and the TeXserver command then
appears on the line after that.

With the new format for requests,  if you wish to use a different return
address for  the information to be mailed back to you  (perhaps avoiding
certain gateways which mangle ASCII during a conversion to/from EBCDIC),
then  you  may  specify  the  return  address  (including  the necessary
gateway)  on the line  preceding the TeXserver command;  prefix any such
alternate address with the directive PATH, followed by a space.

If you  fail to get  any response  from  TeXserver  (neither receipt nor
requested  information)   it   may   be   that  your  address  is  being
misinterpreted by the incoming mailer, CBS_MAILSHR.   DEC are aware of a
bug in this,  in that it  always  upcases  usernames,  so if you're on a
system in which the case of letters in usernames is significant, you may
always  wish to provide a PATH directive,  and thereby get the mail sent
to your true username.

Just to clarify things, assume that A.User@machine.univ.edu wants to get
help from the server:  under the  old scheme  he/she would have sent the
following message (using ============== to delimit this from the rest of
this announcement):

===============================
any number of lines
of rubbish that he/she cared
to put in (although why they bothered,
when there's no human to see, I
wouldn't understand!)

--- Here's the three hyphens, followed by return address
A.User%edu.univ.machine@uk.ac.nsfnet-relay
help
===============================
Note  that the  little-endian address on the Internet has been reordered
to  Janet  big-endian format, which is what  UK gateways expect for mail
from within the UK: they reverse it before remailing  to the appropriate
network.

With the new format, this could reduce to just the command directive:
===============================
help
===============================

But  if  A.User's  machine  doesn't  recognize  A.USER  as  the  correct
individual, then he/she would have to specify:
===============================
path A.User%edu.univ.machine@uk.ac.nsfnet-relay
help
===============================

Any difficulties should be reported to me at the address below: it would
be  useful  if you could  specify what operation you were  attempting to
perform (if possible, send me a copy of your request);  also send copies
of any response received from the TeXserver.

                               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                  +
+ UUCP:      ...!mcvax!rmcs.cranfield.ac.uk!tex                           +
+         OR ...!ukc!rmcs.cranfield.ac.uk!tex                             +
+ 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)   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

P.S.  Some users have rogue mailers, which erroneously introduce a blank
line  between  the  various  fields  which   one  assumes  are  meant to
constitute  a single  RFC-822  header.  This is ILLEGAL;  RFC-822 states
that  the  first blank line  terminates  the headers and  introduces the
message  body:  if you fail  to get  ANY  response from  TeXserver,  try
sending yourself a message via some roundabout route and verify that the
headers are contiguous.  If they appear OK to you, please mail me at the 
above address.

-----------------------------------------------------------------------

%%% 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
**************************
-------