TeXhax@CS.WASHINGTON.EDU (TeXhax Digest) (11/20/90)
TeXhax Digest Monday, November 19, 1990 Volume 90 : Issue 071
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:
Bembo vs.Bodoni (TeXhax Digest V90 #68)
Interaction between code pages and TeX V3
DVI for Unix VGA, right hand figures
Re: latex and ps
Re: Trouble with Levy's TeX Greek
verbatim mode in LaTeX (problem)
PiCTeX and SLITeX
LaTeX Form letters
7-bit encodings
Need for a PKTOPK program
OzTeX 1.3
re LaTeX as the cross-references may have changed
-----------------------------------------------------------------------------
Date: Fri, 2 Nov 90 12:52:32 -0800
From: mackay@cs.washington.edu (Pierre MacKay)
Subject: Bembo vs.Bodoni (TeXhax Digest V90 #68)
Keywords: Bembo vs.Bodoni
A man who asks for Bembo is obviously a man of taste. A bit
harsh, perhaps, on Computer Modern which, although it derives
from the general principles of Bodoni types, is expressly
modeled on Monotype Modern 8A, a font that avoids most of the
stark extremes of true Bodoni.
The reason we don't have a Computer Bembo is that we have not
yet located a Computer Griffi. Nennie Billawalla is still
the only known designer to have taken on a fully-developed new
face based on something other than the general Bodoni-ish
outlines of Modern. With the appropriate sponsorship and
sufficient time I had rather work on Bembo than even Baskerville,
and I would agree that the place to start is a careful emulation
of the Griffi designs, which would probably look a bit dated if
it were well done, but which could then be delicately adjusted.
I doubt that my qualifications to do such work would appear even
adequate, and anyway, I am busy with Arabic. But here is a warning
to the people who ought to be doing the job. I am getting near
retirement, and if I find that there is still no Computer Bembo
by that time, there is a real risk that I will try to inflict it
on the world.
Email concerned with UnixTeX distribution software should be sent primarily
to: elisabet@max.u.washington.edu Elizabeth Tachikawa
otherwise to: mackay@cs.washington.edu Pierre A. MacKay
Smail: Northwest Computing Support Center TUG Site Coordinator for
Thomson Hall, Mail Stop DR-10 Unix-flavored TeX
University of Washington
Seattle, WA 98195
(206) 543-6259
-------------------------------------------------------------------------
Date: Thu, 1 NOV 90 10:57:34 BST
From: CHAA006@vax.rhbnc.ac.uk
Subject: Interaction between code pages and TeX V3
Keywords: TeX 3.0
John ---
Regarding your query concerning user preferences w.r.t. code pages and TeX V3:
I believe that the ISO Latin 1 solution is inadequate, and imposes artificial
restrictions on the manner of working for TeX users whose native code page is
other than ISO Latin 1. The alternative, that there should be code page
specific xchr/xord tables for each code page, seems philosophically much
cleaner. One implementer, Eberhard Mattes, has already commenced on this
route, and provides a look-up table for code page 850, plus utilities to
generate and manipulate any other code pages that the user wishes to use.
The documentation for this facility is too long to incorporate in a TeX-hax
mailing; I will send you a personal copy under separate cover.
Philip Taylor,
Royal Holloway and Bedford New College,
``The University of London at Windsor''.
----------------------------------------------------------------------------
Date: Wed, 31 Oct 90 08:15:01 PST
From: pauld@scenic.wa.com (Paul Barton-Davis)
Subject: DVI for Unix VGA, right hand figures
Keywords: dviware, Unix VGA, right hand figures
a) Does anyone have or know of a DVI previewer for VGA displays
running under Unix (Sys V/386 3.2) ? I don't mind hacking
it ....
b) There was some nice code in TuGBoat some time ago that could
do right-hand placement of figures for plain. I tried porting
this to LaTeX, without much success (or much understanding of
LaTeX's output routines :-). Has anyone else done this ? This
is an example:
word word word word word word word word word word
word word word word word word word word word word
word word word word word word word word word word
word word word word word word word word word word
word word word word word
word word word word word
word word word word word
word word word word word
word word word word word
word word word word word
word word word word word Figure 1: rhfig
word word word word word
word word word word word word word word word word
word word word word word word word word word word
word word word word word word word word word word
word word word word word word word word word word
word word word word word word word word word word
Paul Barton-Davis <pauld@scenic.wa.com>
ScenicSoft, Inc.
(206) 776-7760 Industry without art is brutality
----------------------------------------------------------------------------
Date: Wed, 31 Oct 90 10:49:53 EST
From: jsg@arbortext.com
Subject: Re: latex and ps
Keywords: LaTeX, PostScript
Regarding your search for a way to include Encapsulated PostScript
figures in your LaTeX documents, many dvi-to-PostScript drivers use
TeX \special commands to provide the capability of embedding external
PostScript files into the PostScript that they write. Sometimes,
however, you will need to write additional PostScript to get the
figure in the size and place you want.
ArborText's DVILASER/PS has a \special command specifically for
Encapsulated PostScript that handles the sizing and positioning
automatically. If you are conversant with Adobe's PostScript
structuring conventions, DVILASER/PS reads the %%BoundingBox comment
of the EPS file and adjusts printer's transformation matrix
accordingly.
John Gourlay
ArborText, Inc.
jsg@arbortext.com
---------------------------------------------------------------------------
Date: Wed, 31 Oct 90 09:50:46 -0500
From: Silvio Levy <levy@math.Princeton.EDU>
Subject: Re: Trouble with Levy's TeX Greek
Keywords: Greek TeX, Levy
Com esse nome, voce so pode ser brasileiro ou portugues...
Eu gostaria de poder te ajudar, mas nunca usei Metafont no
Macintosh. Mas eu tenho uma pergunta: voce ja instalou outras
fontes geradas com Metafont? O Mac tem uns formatos especiais
e 'e possivel que o problema resida nao nas fontes propriamente ditas
mas no processo de instalacao.
Boa sorte,
Silvio Levy
------------------------------------------------------------------------
Date: Sat, 27 Oct 90 17:26:32 PDT
From: pauld@scenic.wa.com (Paul Barton-Davis)
Subject: verbatim mode in LaTeX (problem)
Keywords: LaTeX, verbatim
I'm using an old version of LaTeX (2.09 - RELEASE OF 19 April 1986),
and have some problems with verbatim mode. Specifically, spaces are
not properly preserved. I use only PostScript fonts, and this enables
me to use verbatim* -- Courier's character 040 is actually a real
space, not Knuth's "show-space" bucket character. However, I would
much rather use verbatim, which currently seems to have the "blank"
affected by the space factor. I'd also like to understand what is not
working (having beaten on the code for verbatim mode's @vobeyspaces
command for some time to try and fix it). Is this fixed in a later
version ?
Paul Barton-Davis <pauld@scenic.wa.com>
ScenicSoft, Inc.
(206) 776-7760
"Industry without art is brutality"
------------------------------------------------------------------------
Date: Sat, 27 Oct 90 18:06:24 MEZ
From: Erich Neuwirth <A4422DAB%AWIUNI11@UWAVM.U.WASHINGTON.EDU>
Subject: PiCTeX and SLITeX
Keywords: PiCTeX, SLITeX
I need some help from the LaTeX (or PiCTeX) grandmasters.
I want to use SLITeX and PiCTeX together.
Essentially I manage.
But I would need {\invisible label}.
This does not work.
Neither does $\phantom{label}$.
Is there a workaround?
P.S.: You have to define the font \fiverm before loading
PiCTeX into SLITeX.
ERICH NEUWIRTH
BITNET (EARN): A4422DAB@AWIUNI11
INTERNET: a4422dab@Helios.EDVZ.UniVie.AC.AT
Intitute for Statistics and Computer Science
UNIVERSITY OF VIENNA, UNIVERSITAETSSTR. 5/9, A-1010 VIENNA, AUSTRIA
---------------------------------------------------------------------------
Date: Thu, 18 Oct 90 14:45:01 -0700
From: harrison@mahogany.Berkeley.EDU
Subject: LaTeX Form letters
Keywords: LaTeX, form letters
I seem to remember a submission about how to do form letters
in LaTeX for a large number of recipients.
Can someone supply the reference or point me to some macros?
Thanks in advance.
Mike Harrison
e-mail Physical Address
harrison@berkeley.edu Professor Michael A. Harrison
ucbvax!harrison Computer Science Division
571 Evans Hall
University of California
Berkeley, CA 94720
(415) 642-1469
---------------------------------------------------------------------------
Date: Fri, 26 Oct 90 18:00:53 +0100
From: Dominik Wujastyk <ucgadkw@ucl.ac.uk>
Subject: 7-bit encodings
Keywords: archives, 7-bit encodings
I keep hearing that various TeX archive sites will be introducing
services that include the ability to encode binary files in a
7-bit code, for easy mailing (Beebe's archive and Aston).
These announcements are accompanied by the mention of new 7-bit
coding programs that have been written for this purpose.
May I put in a plea for existing 7-bit encoding schemes to be used?
*Please* don't introduce yet another "useful utility". There is
nothing wrong with XXencode for the purposes envisaged. It is widely
supported, and easily available. For DOS it is available by ftp from
wuarchive.wustl.edu as file /mirrors/msdos/starter/xxinstal.bat, and
the C sources can easily be recompiled on any machine. It is
gateway-proof. It is even supported (with auto-recognition) by REM's
excellent uuencode/decode.exe pair.
If another encoder is necessary for some reason, then why not adopt
Wayne Sullivan's equally excellent suencode/sudecode pair, also
available easily, Bitnet-proof, and very handy for splitting big files
up for distribution and reassembly.
Don't reinvent the wheel.
If I have missed some vital point that makes a new encoder necessary,
I'd be glad to stand corrected.
Dominik
-----------------------------------------------------------------------------
Date: Wed, 31 Oct 90 16:02 GMT
From: "Peter Flynn, UCC Computer Centre"
<CBTS8001%IRUCCVAX.UCC.IE@UWAVM.U.WASHINGTON.EDU>
Subject: Need for a PKTOPK program
Keywords: PKtoPK, TFM, graphics
At the Cork meeting there was a short discussion on the need for a new
utility for managing graphics which have been created as PK and TFM files.
POSITION
There are several pieces of software (eg Wynn-Manley's CAPTURE) which can
take a scanned graphic and put it into a PK file as a character and produce
the relevant TFM file to go with it. This can then be used in TeX as a sort
[printers' jargon for an individual character from a font].
PROBLEM STATEMENT
Using such a font is trivial, but if many graphics are required in a document,
each one has to go in its own separate font. Eventually, TeX will refuse to
load any more fonts. Although the new virtual font concept will help, it
would be significantly more convenient to group together related graphics
in a single font file.
REQUIREMENT
A PKTOPK program which would take as its input a list of one or more font
(PK) files [generated from such graphics programs] containing one or more
characters each, and create a single PK file and the regenerated TFM file
containing the desired selection of characters.
Example:
The user has 5 PK files, each with a graphic in the position of the character
"a". She wants one single file, with the characters is positions "a" thru "e".
She could type
pktopk -sa @pklist mypix
where <pklist> is a disk file containing one line for each of the five PK
files, identifying by number or character the position of the graphic, eg:
banner "a"
photo "a"
diagram "a"
chart "a"
graph "a"
and <mypix> is the name for the resultant PK and TFM files which will contain
five graphics, starting in position "a" (that's the <-sa> parameter). If later
she wanted to extract the photo and graph (now in positions "b" and "e" in
mypix) into another file already containing 17 graphics, and add two more
photos, and arrange it so they start in the place of character "C", she
could type:
pktopk -sC @pixlist bookpix
where <pixlist> would look like this:
oldpix "a" "q"
mypix "b"
mypix "e"
Or something like. Anyway, who is going to volunteer to do this? if anyone!
It seems a reasonably tolerable task for a good WEBhacker, as all the code
for reading and writing PK characters already exists. Any offers? No money,
but I'll happily buy a drink for the author! Maybe TUG should fund this kind
of development?
///Peter Flynn
----------------------------------------------------------------------------
Date: Fri, 26 Oct 90 14:34:30 CDT
From: "OzTeX Distributor" <oztex@midway.uchicago.edu>
Subject: OzTeX 1.3
Keywords: OzTeX, new release
The new release of OzTeX (Version 1.3) is now available for anonymous ftp
from midway.uchicago.edu (in the pub/OzTeX heierarchy). OzTeX is a free
version of D. Knuth's typsetting language TeX for the Macintosh. Version
1.3 has significant improvements over version 1.2; in particular it
incorporates TeX 3.0 changes and can be configured in "large" versions
that can handle huge macro packages. (In particular, I have tested it
successfully with LamsTeX).
OzTeX was written by Andrew Trevorrow, who certainly deserves praise and
thanks for his hard work on this project and for making the fruits of his
labour freely available!
OzTeX should work on any Macintosh Plus, SE, II or newer model. It will
not work on a 128K or 512K Mac. OzTeX was developed on a Mac Plus with 1
Meg of RAM and a 20 Meg hard disk. This is just about the minimum hardware
configuration, given the large amount of memory required to run OzTeX and
the large amount of disk space needed to store all the font information.
OzTeX uses standard pk fonts and tfm files (easily ported from mainframe
versions) and creates standard dvi files (which are easily ported to other
platforms).
The application includes a DVI previewer, a PostScript
driver, and of course TeX (including IniTeX so it is possible to dump
preloaded formats).
For more information get the README file from midway!
For rudimentary support and additional information, send mail to
oztex@midway.uchicago.edu.
--Walter
Walter C3arlip carlip@ace.cs.ohiou.edu
"the 3 is silent" c3ar@zaphod.uchicago.edu
**** oztex@midway.uchicago.edu ****
**** c3ar@finite.chi.il.us ****
----------------------------------------------------------------------------
Date: Wed, 31 OCT 90 11:41:02 BST
From: KAPN1%CLUSTER.SUSSEX.AC.UK@UWAVM.U.WASHINGTON.EDU
Subject: re LaTeX as the cross-references may have changed
Keywords: LaTeX
I have a problem. Using LaTeX assuming I start from the basic .TeX
files, make no changes to them and just process them as normal I find
that no matter how many times I process the ROOT.TEX file I get the
message telling me to re LaTeX as the cross-references may have
changed. I mean that I've processed the thing at least SIX times and
it still tells me to rerun it. Doing a difference command on
adjacent versions of the same files I find no differences after having
LaTeXed three times (as one would expect), the only difference being
the time I LaTeXed it as recorded in the .DVI file.
Any suggestions ?
John E. Upham
Cluster Spectroscopy Group,
School of Chemistry and Molecular Sciences,
University of Sussex,
Falmer,
East Sussex,
England.
BN1 9QJ
Tel: (0273) 678332
(0273) 606755 x8332
Fax: (0273) 677196
Elec. Mail:KAPN1@UK.AC.SUSX.CLUSTER (New)
KAPN1@UK.AC.SUSX.VAX2 (Old) KAPN1@UK.AC.SUSSEX.SYMA (Unix)
KAPN1@UK.AC.SUSSEX.CLUSTER
(Europe)
KAPN1@CLUSTER.SUSSEX.AC.UK (USA)
1st November 1990
-----------------------------------------------------------------------
%%% 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.nnn
%%% yy = last two digits of current year
%%% nnn = issue number
%%%
%%%\bye
%%%
End of TeXhax Digest
**************************
-------