UKTeX Digest Monday, 22 Jul 1991 Volume 91 : Issue 29
Today's Topics:
{Q&A}:
RE: TeX
Re: TeX for the Atari-ST?
Arabic in TeX
Re: Help with obtaining some font libraries
Graphics and EmTeX
Using DVIPS (under VMS) - PostScript Small Caps
Re: Using DVIPS (under VMS) - PostScript Small Caps
Re: Using DVIPS (under VMS)
DVIPS
emtex
Re: emtex
RE: emTeX
{Announcements}:
Training Day at RHBNC; 24th July, 1991 (this week!)
Administrivia:
Moderators: Peter Abbott (Aston University) and
David Osborne (University of Nottingham)
Contributions: UKTeX@uk.ac.tex
Administration, subscription and unsubscription requests:
UKTeX-request@uk.ac.tex
------------------------------------------------------------
Date: Fri, 12 Jul 91 17:12:22 +0000
From: Brian {Hamilton Kelly} <TeX@uk.ac.cranfield.rmcs>
Subject: RE: TeX
In a message to UKTeX of Thu, 27 Jun 91 10:32 BST,
Neil Weightman <WEIGHTNA@uk.ac.southbank-poly.vax> wrote:
(I don't know what happened here; it wasn't received at uk.ac.tex until
12th July!!)
> Sorry to bother you, but I'm trying to download a PC (MSDOS) version of TeX
> from your archive and I'm not getting very far. Can you tell me what I'm doin
g
> wrong, please?
>
> I'm looking for as complete a version as possible. It seems to me that EMTeX
> (in TEX-ARCHIVE.TEX.MSDOS.EXTEX) is the best bet. Since the only access I hav
e
> is via JANET, I guess I have to use TRANSFER. Here's what I'm trying:
>
> $TRANSFER
> <Local filename> tex.boo <or whatever is a valid name>
> <remote filename> uk.ac.sbank::tex.boo
> <remote username> weightna
> <remote password> <my password>
>
> I get an error message saying that the CBS network manager hasn't started, bu
t
> I can't see what I'm doing wrong.
I think that the TRANSFER software had probably crashed at the time;
it's all right at the time of writing (I've just checked!)
Incidentally, if your home site is a VMS system, you might find it
advantageous to use /CODE=FAST on the TRANSFER command.
> The other thing is that I'd rather transfer
> the whole lot at once rather than one file at a time - is there any way of us
ing
> wildcards?
Well, you _could_ try this; no guarantees, etc. (And it should be typed
exactly as shown, except that I've wrapped lines where necessary -- just
type the command all on one line, and let VMS wrap the command line for
you).
$ @SYS$COM:FOR_ALL "TRANSFER 'file_spec' uk.ac.sbank::'short_spec'
WEIGHTNA <password>"
which will transfer all the files in the current directory of the
archive. User's of non-VMS machines might need to say something like
uk.ac.unix-site::""'"+"'F$EDIT(short_spec,""LOWERCASE"")'""
in place of the uk.ac.sbank::'short_spec' shown above; they might also
need to put `""' before and after both the username and password for
their site's machine.
Users familiar with VMS should note that the string enclosed within the
double quotes deliberately uses only a SINGLE apostrophe before each DCL
symbol: symbol expansion is wanted at the time the command is EXECUTED,
not when the command line is TYPED. That's also the reason for breaking
up the two apostrophes before the call of the F$EDIT lexical function by
putting them into separate strings which are subsequently concatenated.
If you want just some subset of the files, that can be specified by a
wildcard expression, you can put (for example) *.BOO after the TRANSFER
command (enclosed within the quoted-string above), e.g.:
$ @SYS$COM:FOR_ALL "TRANSFER 'file_spec' uk.ac.sbank::'short_spec'
WEIGHTNA <password>" *.boo
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: {mcsun,ukc,uunet}!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) +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------
Date: Sat, 13 Jul 91 13:20:00 -0600
From: Erik-Jan Vens <erikjan@nl.rug.icce>
Subject: Re: TeX for the Atari-ST?
DO9EA00@uk.ac.manchester-poly.computing-services.sysa schrijft:
> copies of TeX and related software through your e-mail servive (by
> Mark@Lancs.pdsoft). Please could you inform me if a copy of TeX
David,
there is a good copy avail. via FTP from various sources. I cannot find the
address for the DANTE server in Germany, but you could also try
<forwiss.uni-passau.de> in the </pub/atari/tex/StrunkTeX> directory .
Yours,
Erik-Jan Vens. erikjan@icce.rug.nl ICCE
------------------------------
Date: Sat, 13 Jul 91 20:22:46 +0000
From: Dominik Wujastyk <ucgadkw@uk.ac.ucl>
Subject: Arabic in TeX
Yes, Yannis Haralambous has created an Arabic metafont for use with
TeX. See the article in TUGboat 11.4 (I think).
Input is in roman transliteration, and you can choose your own
preferred correspondences of roman to arabic letters.
Another way would be to use an Arabic front end, such as
Multilingual Scholar on the PC, and filter the output into
TeX input.
To handle the bidirectionality of Arabic, you can use either
Graeme McKinstry's semitic.sty, or actually set up a
special bi-directional TeX, called TeXXeT. This is
available for the PC, thanks to Knuth, MacKay and
Sullivan. But you need some expertise in TeX to get to
grips with it.
Basically, Arabic in TeX is there today if you really know
TeX inside out, and are prepared to read manuals and fiddle
around quite a bit. The results are really nice, though.
Another area to watch is Yannis's forthcoming ScholarTeX
package, which does Arabic as well as a whole gaggle of
other languages. Very promising.
If you want to keep up to date on Arabic and Hebrew for
TeX, join the IVRITEX listserv group. To do this,
send the message "subscribe ivritex" to the address
"listserv@bitnet.taunivm".
Best wishes,
Dominik
Dr Dominik Wujastyk, | Janet: D.Wujastyk@uk.ac.ucl
Wellcome Institute for | Bitnet/Earn/Ean/Uucp/Internet: D.Wujastyk@ucl.ac.uk
the History of Medicine,| or: dow@harvunxw.bitnet or: dow@wjh12.harvard.edu
183 Euston Road, | last resort: D.Wujastyk%uk.ac.ucl@nsfnet-relay.ac.uk
London NW1 2BN, England. | Phone no.: +44 71 383-4252 ext.24
------------------------------
Date: Sun, 14 Jul 91 16:45:54 +0000
From: Sebastian Rahtz <S.P.Q.Rahtz@uk.ac.southampton.ecs>
Subject: Re: Help with obtaining some font libraries
schoepf%de.zib-berlin.sc@uk.ac.nsfnet-relay writes:
> Robert Tregidgo <treg@essex.ac.uk> wrote:
>
> GETTING EMTEX TO PRINT WITH A 24 PIN LQ-500 COMPATIBLE PRINTER
>
> I recently obtained a copy of emtex, and installed most of it
> successfully on my pc. The only thing I can't get to work is
> the printer driver for my LQ-500 compatible printer (180dpi).
> The copy of emtex I have, came with a set of font library files
> labelled LJ_*.FLI, these I presumed are actually for a laser jet
This is a perennial complaint. As has been noted, the difficulties of
getting these enormous files moved around are noticeable. May I
suggest in the interim that you check out the MFJOB utility which
comes with emTeX? This makes generating new PK files (which can be put
into .fli libraries) very easy. By my short experience, leaving a
reasonable 386 PC running for 10-12 hours will generate all the fonts
you need for a particular device, which is acceptable for most people
who need sleep and food.
MFJOB looks forbidding, but I think all you need do is type
mfjob all m=lql
and then go home; edit \emtex\mfjob\modes.mfj first to check on the
path name for the output files. You will get a set of PK files, and
you will need either to run FONTLIB to put these into .fli files, or
to add some info in your .cnf files to tell the drivers where to find
what they want.
Sebastian
PS Update to emtex in the Aston archive: the files
DVIDRVMA.BOO, CHANGES.{ENG,GER}, and README.{ENG,GER} have been
upgraded to the latest versions from Eberhard Mattes.
------------------------------
Date: Wed, 17 Jul 91 09:37:55 +0000
From: Peter Abbott (Aston University) <p.abbott@uk.ac.aston>
Subject: Graphics and EmTeX
From Codus, Sheffield (query via paper mail)
Using EmTeX on a pc with HP Laserjet
Do facilities exist for the inclusion of imported graphics and PC screen
dumps in TeX output, and more particularly is there any means of sizing
such imported material on the output page?
Kevin Atkins
Codus Limited
------------------------------
Date: Wed, 17 Jul 91 15:57:11 -0500
From: Robin Fairbairns on LSL cluster <robin@uk.co.laser-scan>
Subject: Using DVIPS (under VMS) - PostScript Small Caps
Some time ago, I asked for help with getting the latest version of
DVItoPS going under VMS. The only answer I got was a characteristically
helpful one from Max Calvani saying `use DVIPS'.
More recently, my colleague Tony Ibbs posted a remark about getting VMS
DVIPS working properly, and Max again offered the helpful observation
(and I found this one in my archive ;-) that:
beware that also the files dospecial.c and special.pro do not work
properly under vms.
The "working" version of DVIPS under VMS is in the new DECUS tape.
As a much belated response to Max's `help', I've started playing around
with DVIPS myself. I want to replace the CM fonts, and have the idea of
using the M&S NFSS with the PostScript extensions written by Sebastian
Rahtz and TFMs and VFs generated by the AFM2TFM that comes with DVIPS to
solve _all_ my problems. (Note that this would replace my present set
up of using Mario Wolczko's PSLaTeX with TFMs generated by Mario's
AFTOPL.)
What I have come to a dead stop on is Small Caps fonts. AFM2TFM can
create Small Caps fonts ("-V" switch, albeit a leetle bit tricky to
generate under VMS), but I can't produce an incantation that enables me
to use the TFM and VF thus generated through DVIPS. (Note that I
haven't plunged straight into NFSS - this is all being exercised through
a minuscule Plain TeX file.)
And, while we're at it, does anyone have the `working' DVIPS under VMS
that Max talks of? Some of us have no budget for buying tapes from
DECUS (nor pockets that stretch to buying them personally :-( ). Or
does anyone know of an FTP site where this stuff can be picked up? It's
really a bit daft to have a non-working bit of software in an archive of
the quality of Aston.
Robin
Robin Fairbairns, Senior Consultant, postmaster and general dogsbody
Laser-Scan Ltd., Science Park, Milton Rd., Cambridge CB4 4FY, UK
Email: robin@lsl.co.uk --or-- rf@cl.cam.ac.uk
------------------------------
Date: Wed, 17 Jul 91 16:32:43 +0000
From: Philip Taylor (RHBNC) <P.Taylor@uk.ac.rhbnc.vax>
Subject: Re: Using DVIPS (under VMS) - PostScript Small Caps
Robin ---
>>> And, while we're at it, does anyone have the `working' DVIPS under VMS
>>> that Max talks of? Some of us have no budget for buying tapes from
>>> DECUS (nor pockets that stretch to buying them personally :-( ). Or
>>> does anyone know of an FTP site where this stuff can be picked up? It's
>>> really a bit daft to have a non-working bit of software in an archive of
>>> the quality of Aston.
I have V5.47 `working' under VAX/VMS and MS/DOS; here's a copy of my
initial letter to its author and implementors, followed by their replies:
(and then some earlier comments thereon)
- --------
Gentlemen ---
After an enormously long period of resistance, during which I have faithfully
used ArborText's DVILASER/PS, I have finally followed the received wisdom and
investigated your DVIPS implementation (V5.47) , and I now have a few queries
,
which I would be most obliged if you could find time to answer.
1) DVIPS appears to assume the Knuthian canonical origin of (1", 1") w.r.t.
the top-left corner of the page. At RHBNC (and other institutions), we
assume an origin coincident with the top-left corner. Could you please
tell me how I tell the driver to use the local origin, as there appears
to be no qualifier which affects the placement of the origin.
2) Many documents require to be printed two-up, with the origin cyclically
varying between recto and verso page; how may this be accomodated, please ?
3) Many documents require to be printed in non-monotonic order, to allow for
imposition requirements; how may pages be processed in arbitrary order,
please ?
4) How, in the VMS implementation, may I specify that
MakeTeXPK is not to be attempted under any circumstances ?
5) In the MS/DOS implementation, on attempting to process the following
document, I get a `Memory allocation error' after getting `<tex.pro>. [1]'
displayed; the system then reports `Cannot load COMMAND, system halted'.
This occurs only if I specify -D1270 (for 1270 dpi output); at the default
of 300 dpi, no problem occurs. I have 2880K of expanded memory available,
and no free extended memory. Can DVIPS use expanded and/or extended memory,
if so, how do I so configure it, and is the `Memory allocation error' a
valid diagnostic ? (COMSPEC is set correctly; I cannot understand why the
system cannot reload COMMAND).
\hsize = 297 mm
\vsize = 210 mm
\hoffset = 1 cm
\voffset = 1 cm
\advance \hsize by -2 \hoffset
\advance \vsize by -2 \voffset
\output = {}
\def \crest #1 {{\font \crest = rhbnc scaled #1
\crest
\char 0} }
\crest \magstep0
\end
%%% RHBNC.PL follows:
(DESIGNSIZE R 75.872803)
(COMMENT DESIGNSIZE IS IN POINTS)
(COMMENT OTHER SIZES ARE MULTIPLES OF DESIGNSIZE)
(CHECKSUM O 10072240273)
(CHARACTER O 0
(CHARWD R 0.725)
(CHARHT R 0.8)
(CHARDP R 0.160001)
)
6) The documentation shows various instances of \special being used with no
reserved keyword to indicate the driver intended to process the special;
is this intended, and if so is it wise ? I thought that drivers were
supposed to differentiate between their use of \special by a reserved
word as the first part of the \special text.
Many thanks in advance for any advice you can offer.
Philip Taylor
Royal Holloway and Bedford New College,
``The University of London at Windsor''
rokicki@cs.stanford.edu
xev@bunny.gte.com
rjl@monu1.cc.monash.edu.au
- --------
Date: Tue, 16 Jul 91 11:32:43 -0700
From: Tomas "G." Rokicki <rokicki@edu.Stanford.Neon>
To: P.Taylor@uk.ac.rhbnc.vax
Subject: DVIPS V5.47
Sender: rokicki@edu.stanford.neon
Howdy! Thanks for the note. I'll try to answer your questions . . .
> 1) DVIPS appears to assume the Knuthian canonical origin of (1", 1") w.r.t.
> the top-left corner of the page. At RHBNC (and other institutions), we
> assume an origin coincident with the top-left corner. Could you please
> tell me how I tell the driver to use the local origin, as there appears
> to be no qualifier which affects the placement of the origin.
Why do you do this? Do you also switch push and pop in the dvi file, and
have you changed TeX accordingly? Why fly in the face of the standard?
In any case, this is a trivial modification to the header file procedure
@rigin, which does the placement.
> 2) Many documents require to be printed two-up, with the origin cyclically
> varying between recto and verso page; how may this be accomodated, please
?
This should be done either within TeX or within a program such as dvidvi.
Failing this, it is fairly trivial to hack up some PostScript changes to
`bop-hook' to make this work.
> 3) Many documents require to be printed in non-monotonic order, to allow fo
r
> imposition requirements; how may pages be processed in arbitrary order,
> please?
Imposition should be done by dvidvi or another program, or by a PostScript
post-processing program. Dvips only will print a single monotonic range of
pages.
> 4) How, in the VMS implementation, may I specify that
> MakeTeXPK is not to be attempted under any circumstances ?
Delete MakeTeXPK. Or compile with `dontmakefonts' initialized to 1.
> 5) In the MS/DOS implementation, on attempting to process the following
> document, I get a `Memory allocation error' after getting `<tex.pro>. [1
]'
> displayed; the system then reports `Cannot load COMMAND, system halted'.
> This occurs only if I specify -D1270 (for 1270 dpi output); at the defau
lt
> of 300 dpi, no problem occurs. I have 2880K of expanded memory availabl
e,
> and no free extended memory. Can DVIPS use expanded and/or extended mem
or
y,
> if so, how do I so configure it, and is the `Memory allocation error' a
> valid diagnostic ? (COMSPEC is set correctly; I cannot understand why t
he
> system cannot reload COMMAND).
>
> \hsize = 297 mm
> \vsize = 210 mm
> \hoffset = 1 cm
> \voffset = 1 cm
> \advance \hsize by -2 \hoffset
> \advance \vsize by -2 \voffset
> \output = {}
> \def \crest #1 {{\font \crest = rhbnc scaled #1
> \crest
> \char 0} }
> \crest \magstep0
> \end
>
> %%% RHBNC.PL follows:
>
> (DESIGNSIZE R 75.872803)
> (COMMENT DESIGNSIZE IS IN POINTS)
> (COMMENT OTHER SIZES ARE MULTIPLES OF DESIGNSIZE)
> (CHECKSUM O 10072240273)
> (CHARACTER O 0
> (CHARWD R 0.725)
> (CHARHT R 0.8)
> (CHARDP R 0.160001)
> )
You should always use -Z at 1270 or above. I take no responsibility for the
bogus memory arrangements under DOS; I work on reasonable machines. In any
case, the newer version of dvips will make more of an effort to conserve
memory (although the current one does very well; much better than any other
dvi to PostScript converter I am aware of.)
> 6) The documentation shows various instances of \special being used with no
> reserved keyword to indicate the driver intended to process the special;
> is this intended, and if so is it wise ? I thought that drivers were
> supposed to differentiate between their use of \special by a reserved
> word as the first part of the \special text.
This is intended. There are three types of specials. The first is
`landscape'---and it should work on any driver. The second is
`PSfile' and variants, and it should also work on any driver (and it
does on many systems, such as the Amiga and NeXT). The third are ps:
and similar hacks; they were added strictly for compatibility and thus
could not have the driver keyword.
Please let me know if you have any suggestions for the driver or any way
I can improve things for your site.
- -tom
- --------
From: rjl@au.edu.monash.cc.monu1 ( r lang)
To: Philip Taylor (RHBNC) <P.Taylor@uk.ac.rhbnc.vax>
Subject: Re: DVIPS V5.47
Date: Wed, 17 Jul 91 10:03:42 +1000
Sender: rjl <rjl%au.edu.monash.cc.monu1@au.oz.munnari>
> 5) In the MS/DOS implementation, on attempting to process the following
> document, I get a `Memory allocation error' after getting `<tex.pro>. [1
>]'
> displayed; the system then reports `Cannot load COMMAND, system halted'.
> This occurs only if I specify -D1270 (for 1270 dpi output); at the defau
>lt
> of 300 dpi, no problem occurs.
How large are the bitmaps? Do they exceed 64k bytes? If so, the MS-DOS
version will not be able to handle it.
> Can DVIPS use expanded and/or extended memory,
No.
> and is the `Memory allocation error' a
> valid diagnostic ?
This error message appears to be generated outside dvips - presumably
by MS-DOS. It appears that the MS-DOS memory allocation is dying so
badly that COMMAND.COM cannot be reloaded.
All I can suggest is that you use a debugger to find out which memory
allocation operation is actually causing the crash.
- --
Russell Lang Email: rjl@monu1.cc.monash.edu.au Phone: (03) 565 3460
Department of Electrical and Computer Systems Engineering
Monash University, Australia
- --------
From: VAXA::CHAA006 "Philip Taylor (RHBNC)
<P.Taylor@Uk.Ac.Rhbnc.Vax>" 17-JUL-1991 13:15:48.98
To: CBS%UK.AC.NSFNET-RELAY::EDU.STANFORD.NEON::ROKICKI
CC: CHAA006
Subj: RE: DVIPS V5.47
Tom ---
Many thanks for your reply; I will try to answer your questions, but
am sitting at a very strange terminal, so my normal annotation mechanism
won't work ...
>>> > 1) DVIPS appears to assume the Knuthian canonical origin of (1", 1") w.
r.
t.
>>> > the top-left corner of the page. At RHBNC (and other institutions),
w
e
>>> > assume an origin coincident with the top-left corner. Could you ple
as
e
>>> > tell me how I tell the driver to use the local origin, as there appe
ar
s
>>> > to be no qualifier which affects the placement of the origin.
>>> Why do you do this? Do you also switch push and pop in the dvi file, and
>>> have you changed TeX accordingly? Why fly in the face of the standard?
Well, despite the fact that I hold Knuth in the highest esteem (somewhere
between a demigod and the real thing, in fact), I think that on the day
he decided that the origin should be at (1", 1") he was WRONG ! There is
absolutely no logic to it, and I prefer, when teaching TeX, to tell the
students to base their \hoffset and \voffset values on the physical origin
of the page, which is simple, justifiable and logical. There is absolutely
nothing special about (1", 1") and for those needing smaller margins, negativ
e
values for \hoffset and \voffset seem ridiculous. I assume your question
about push and pop was humorous !
>>> In any case, this is a trivial modification to the header file procedure
>>> @rigin, which does the placement.
Fine, I'll look there.
>>> > 2) Many documents require to be printed two-up, with the origin cyclica
ll
y
>>> > varying between recto and verso page; how may this be accomodated, pl
ea
se?
>>> This should be done either within TeX or within a program such as dvidvi.
>>> Failing this, it is fairly trivial to hack up some PostScript changes to
>>> `bop-hook' to make this work.
Well, it can't be done in TeX because the documents already exist, and
although I have no fear of output routines, I don't write them just to
get two-up printing ! (Incidentally there's a very nice problem involving
indexing when the output routine is used to achieve two-up printing which
I'll send you if you're interested; the solution requires a trick so dirty
it makes Knuth's dirty tricks look like a Sunday school outing ...).
I'll look at bop-hook ...
>>> > 3) Many documents require to be printed in non-monotonic order, to allo
w
for
>>> > imposition requirements; how may pages be processed in arbitrary ord
er
,
>>> > please?
>>> Imposition should be done by dvidvi or another program, or by a PostScrip
t
>>> post-processing program. Dvips only will print a single monotonic range
of
>>> pages.
Hmmm. Don't have DVIDVI; I'll have to look for a VAX/VMS and MS/DOS
implementation of it ...
>>> > 4) How, in the VMS implementation, may I specify that
>>> > MakeTeXPK is not to be attempted under any circumstances ?
>>> Delete MakeTeXPK. Or compile with `dontmakefonts' initialized to 1.
Well, deleting MakeTeXPK didn't stop it trying (and failing !). I'll
implement your recompile suggestion.
>>> You should always use -Z at 1270 or above. I take no responsibility for
th
e
>>> bogus memory arrangements under DOS; I work on reasonable machines. In a
ny
>>> case, the newer version of dvips will make more of an effort to conserve
>>> memory (although the current one does very well; much better than any oth
er
>>> dvi to PostScript converter I am aware of.)
OK, I'll give that a go. What is the latest version of DVIPS, and do you
by any chance know if the VAX/VMS and MS/DOS implementations of it are
available anywhere ? I took V5.47 from Aston.
>>> > 6) The documentation shows various instances of \special being used wit
h
no
>>> > reserved keyword to indicate the driver intended to process the spec
ia
l;
>>> > is this intended, and if so is it wise ? I thought that drivers wer
e
>>> > supposed to differentiate between their use of \special by a reserve
d
>>> > word as the first part of the \special text.
>>> This is intended. There are three types of specials. The first is
>>> `landscape'---and it should work on any driver. The second is
>>> `PSfile' and variants, and it should also work on any driver (and it
>>> does on many systems, such as the Amiga and NeXT). The third are ps:
>>> and similar hacks; they were added strictly for compatibility and thus
>>> could not have the driver keyword.
I wasn't thinking of these, but of the \special {" <some PostScript string>},
\special {! <some PostScript macro>} and the \special {/foo {<proc> def},
all of which are referred to in the documentation, but none of which commence
with a keyword.
>>> Please let me know if you have any suggestions for the driver or any way
>>> I can improve things for your site.
Well, explicit specification of the origin, cyclic origins, and random page
access would be an enormous step forward, but I suspect you didn't have
these in mind !
Many thanks, Tom.
** Phil
P.S. Came up with another one after my last message: I do not seem able
to successfully rotate an A4 page into Landscape mode in the VAX/VMS
implementation, as I suspect it doesn't honour two /mode qualifiers.
I tried hacking the PostScript code, inserting an @a4 just before the
@landscape, but even that didn't work. I'm going to try again when I've
managed to install the (0", 0") origin, as that should make life simpler.
** P.
- --------
From: DOMINIK WUJASTYK <teexdwu@UK.AC.LON.IOE>
Date: Wed, 2 Jan 91 20:57:49 GMT
To: p.taylor@uk.ac.rhbnc.vax
Subject: dvips for VMS
Happy new year to you too, Phil.
This swam past me a few days ago, and I thought you might be interested.
It looks as though Rokicki's DVIPS is trying to take over the world: I
think it probably deserves to as well. Having pushed for ULCC to use
dvitops, I would now probably say that dvips would be the one to support,
if they want something public domain.
- ---------------------
Article 4174 of comp.text.tex:
From: viswanat@rodan.acs.syr.edu (Viswanath)
Newsgroups: comp.text.tex,comp.text,comp.os.vms
Subject: New improved port of dvips for VMS.
Date: 27 Dec 90 03:21:41 GMT
Sender: viswanat@rodan.acs.syr.edu (Viswanath)
Organization: Syracuse University, Syracuse, NY
Hello Friends,
A port of dvips for VMS is currently available from YMIR.CLAREMONT.EDU in the
directories LOCAL:[ANONYMOUS.TEX.DRIVERS.DVIPS_NEW...]
This is a port of the dvips for VMS. The current version fixes many of the
bugs reported. Also, VMS users wanted to have the package to use the VMS
command line interpretter. Hence a CLD has been provided. The routine needed
to
support this has been provided. Thanks to Xev Gittler, for his initial work a
nd
for all the information/suggestions. I have tried to incorporate them into
this distribution.
Although considerable effort has been expended to make this software correct
and reliable, no warranty is implied. Any obligation or liability for damage
s,
including but not limited to special, indirect, or consequential damages
arising out of or in connection with the use or performance of this software
is
disclaimed.
To compile, set the following in
MAKE.COM:
Set TFMPATH to where the TFM files are located. Default is TEX$FONTS:
($ TFMPATH = "TEX$FONTS:")
Set PKPATH to where the PK fonts are located. Default is TEX_PK:
($ PKPATH = "TEX_PK:")
Set VFPATH to where the VF fonts are located. Default is TEX_VF:
($ VFPATH = "TEX_VF:")
Set FIGPATH to where the epsf and psfiles are located. Default is TEX_INPUTS:
($ FIGPATH = "TEX_INPUTS:")
Set HEADERPATH to where the header files are located. Default is
TEX$POSTSCRIPT:,SYS$LOGIN:,"
($ HEADERPATH = "TEX$POSTSCRIPT:,SYS$LOGIN:,")
Set CONFIGPATH to where the config files are located. Default is
TEX$POSTSCRIPT:
($ CONFIGPATH = "TEX$POSTSCRIPT:")
Set TPIC to ",TPIC" if you want TPIC support enabled. Default is enabled.
($ TPIC = ",TPIC")
Set DEBUG to ",DEBUG" if you want DEBUG support enabled. Default is enabled.
($ DEBUG = ",DEBUG")
Then execute MAKE.COM
Expect 1 warning in dospecial.c
To install:
maketexpk := @DIRECTORY:maketexpk
Use install to install the dvips.cld
Make sure that all the logicals defined above (eg, tex_pk, tex_vf) are
actually defined.
DVIPS.HLP is a VMS help file which may be directly included into the system
help. For additional details about the special features of dvips, refer to th
e
manual provided (dvips.tex).
Report any problems or bugs to :
Viswanathan Narayanan
=============================================================================
email: Phone:
internet:viswanat@rodan.acs.syr.edu Res:(315)-423-3011
bitnet :vnaraya2@sunrise Off:(315)-443-4450
snail-mail: Lab:(315)-443-1105
Res: 530, Allen Street,
Syracuse, NY 13210.
Off: 121 Link Hall
Syracuse, NY 13244-1240.
=============================================================================
=
Date: Tue, 23 APR 91 10:54:26 GMT
From: LIST_SERVER@UK.AC.TEX
To: P.TAYLOR@UK.AC.RHBNC.VAX
Subject: DVIPS on VMS
Reply-To: Tony J Ibbs (Tibs) 041-339-8855 x6649"Tony J Ibbs
(Tibs) 041-339-8855 x6649" <GAGA50@UK.AC.GLASGOW.VMS3>,
UKTeX Reviewers <UKTeX-Reviewers@Uk.Ac.TeX>
Originally-sent:Tue, 23 Apr 91 11:38 GMT
Originally-To: UKTEX@UK.AC.TEX
Originally-from:GAGA50@UK.AC.GLASGOW.VMS3
I've been installing DVIPS on our local VAX/VMS system, and thought the
following might be worth pointing out:
1) Although it might look as if the various paths that DVIPS looks
along are being specified in the [.VMS]MAKE.COM file, you should
be aware that they are most (if not all) actually hard-coded into
PATHS.H in the main directory. I made the following specific
changes:
line 54: PKPATH
changed "TEX_PK" to be "TEX$PKS:"
whilst the name change is not particularly important
(it's just to meet existing practice), the insertion
of the missing `:' is essential for the program to work
line 55: VFPATH
changed "TEX_VF:" to be "TEX$VF:"
note that the colon was in place here already. The dollar
instead of underline just follows other logical names here.
line 56: CONFIGPATH
changed "TEX$POSTSCRIPT" to be "TEX$POSTSCRIPT:"
again, the addition of the colon makes it work (otherwise
the program will never find you configuration file)
2) To make the /DEBUG qualifier work, edit [.VMS]VMSCLI.C at line 78
and change
if(sscanf(...) != 0)
to be
if(sscanf(...) == 0)
3) I also added a new qualifier, /[NO]AUTOGENERATE, to control whether
the program tries to generate a new font using MakeTeXPK - ie, the
-M qualifier under Unix. This involved adding a `qual25' in the
aforementioned [.VMS]VMSCLI.C - the following code fragments were
used:
After the definition of `qual24':
static $DESCRIPTOR(qual25,"autogenerate");
At the end of the routine:
status = cli$present(&qual25);
if(status == CLI$_NEGATED) dontmakefont=1;
I also fiddled with the [.VMS]MAKE.COM command file to improve it a little,
but if you know VMS you should be able to work with the existing one anyway
(it requires either altering or the shuffling around of some of the source
files - I preferred to make the command file more intelligent)
Now for a couple of questions:
Firstly, if I want to use the MakeTeXPK facility, I need to customise
[.VMS]MAKETEXPK.COM, but I don't know anything about MetaFont. What base
file should I be using? (answers as for a totally ignorant fool, please)
Secondly, what IS the recommended layout of directories for DVIPS use,
and what goes where? Much of it is specified in the documentation (at least
to some extent) and I expect the rest can be found by trial and error, but
a statement of what directories are needed, what they are conventionally
called (under Unix and VMS (and MS-DOS?)), which files from the distribution
go where, etc, ALL IN ONE PLACE, would be very useful.
General impressions, though, are good - for a piece of software with little
support, it's all going together quite quickly.
- ---------------------------------------------------------------------------
--
Tony J Ibbs (Tibs)
Department of Geography and Topographic Science
University of Glasgow
GLASGOW G12 8QQ Telephone: +41-339-8855 x6649
Scotland Email - Janet (UK): GAGA50@uk.ac.Glasgow.vms
(non-UK): GAGA50@vms.Glasgow.ac.uk
- ---------------------------------------------------------------------------
--
Date: Tue, 23 Apr 91 13:30 GMT
From: "Tony J Ibbs (Tibs)
041-339-8855 x6649" <GAGA50@UK.AC.GLASGOW.VMS3>
To: P.TAYLOR@UK.AC.RHBNC.VAX
Subject: RE: DVIPS on VMS
Thanks for the quick response!
All points taken, and in reply:
TEX_PK vs TEX$PKS - yes, I'd forgotten about DEC reserving dollars for
themselves - although it's not STRICTLY true, since they
allow <company mnemonic>$ as a prefix for `approved'
software suppliers, if I remember correctly. The trouble is
that I've been programming VMS too long (!) and, of course,
that many existing TeX implementations already use a lot
of logical names starting TEX$. But you are right, and they
(we) should be changing to the proper form.
Lib$Match_Conds vs cli$present - unfortunately I was attempting to match
the code that is already present (I wouldn't actually have
programmed the relevant routine the way it is anyway, in
various different manners), so I had little choice about
what to do
Base file - thanks for the help, that answers me exactly.
It occurs to me that I may have forgotten to mention that the CLD file
([.VMS]DVIPS.CLD) also needs a line adding - viz:
add a new qualifier to the end, AUTOGENERATE NEGATABLE,DEFAULT
Best wishes, Tony Ibbs
- ------
Via: UK.AC.TEX; Tue, 23 Apr 91 23:26 BST
X-Date: Tue, 23 APR 91 22:25:28 GMT
X-From: LIST_SERVER@UK.AC.TEX
To: P.TAYLOR@UK.AC.RHBNC.VAX
Subject: DVIPS / PSFig
Reply-To: <D.MATHER@UK.AC.EDINBURGH>,
UKTeX Reviewers <UKTeX-Reviewers@Uk.Ac.TeX>
Originally-sent:23 Apr 91 19:32:28 bst
Originally-To: uktex@uk.ac.tex
Original-Ident: <23 Apr 91 19:32:28 bst 060682@EMAS-A>
Originally-from:D.MATHER@UK.AC.EDINBURGH
X-Serial: 00000360
Can anyone help ? I have a DOS executable copy of DVIPS from the ASTON
archivers. The documentation states v5.4, whilst in use in identifies
itself as v5.395.
I'm trying to use PSFig (which v5.4 says is supported), beginning with
PSFig's own manual PSFIGDOC.TEX from the archive, but whenever DVIPS
encounters a `\psfig', it outputs several (typically 8) lines like;
\begin{verbatim}
C:\EMTEX\DVIPS.EXE Unknown keyword ("836254794) in \special will be ignored
\end{verbatim}
(The numbers may be different; the `"' only appears in the first such
statement, whilst something like `635283946"' appears in the last)
This is then followed by;
\begin{verbatim}
C:\EMTEX\DVIPS.EXE No \special psfile was given; figure will be blank
\end{verbatim}
Apart from this DVIPS, works perfectly. Is the problem in my version,
or is there something more subtle ?
Dunc
- --------
------------------------------
Date: Thu, 18 Jul 91 12:07:00 -0500
From: Robin Fairbairns on LSL cluster <robin@uk.co.laser-scan>
Subject: Re: Using DVIPS (under VMS)
I posted to UKTeX yesterday, saying:
>Some time ago, I asked for help with getting the latest version of
>DVItoPS going under VMS. The only answer I got was a characteristically
>helpful one from Max Calvani saying `use DVIPS'.
>
>More recently, my colleague Tony Ibbs posted a remark about getting VMS
>DVIPS working properly, and Max again offered the helpful observation
>(and I found this one in my archive ;-) that:
>
>[...]
Since then, to my chagrin in view of the sarcastic tone of the remarks
about Max in the above, I have had two very helpful messages from Max.
The first message offered a way out of the wood about the Small Caps
problem (which I shall evaluate and post to the archive maintainers if I
get it going right).
The second message said that in the last half hour before going on his
holidays, he had made a tape for me of the `working' VMS DVIPS from the
Decus TeX tape. This is supposed to have been posted from Italy to me
today; he asks that when I've had my use of it, I forward it to Aston,
which I shall of course do.
What more can I say? This is plainly support way beyond the call of any
conceivable duty - I feel it's encumbent on me to retract any suggestion
of my low opinion of Max!
Robin
Write 100 lines: I must avoid flaming people for their voluntary efforts
(By hand)
------------------------------
Date: Wed, 17 Jul 91 17:44:00 +0100
From: Max Calvani - Italy <FISICA%it.unipd.astrpd@uk.ac.earn-relay>
Subject: DVIPS
Hello, here I am, Max
I am sorry about DVIPS. The fact is that I am on SPAN and have
a lot of difficulties in getting in touch with Aston Archive.
The tex archive I look after is at 39003::$1$dua2:[tex]
and if you can aceess span please copy whatever you need.
I do NOT know of any FTP place where they have a bug free VMS DVIPS.
Everywhere I looked I found the version (that is at Aston) and has bugs in.
In case, I couls mail you ALL files when I maback from holydays.
I am indeed leaving in two hours! I'll be back beginning august.
About small caps, I do noy know if this can help, but is a procedure
I found somewhere to create new ps fonts from old ones and it works.
Let me know! It is not that I am not willing to share my DVIPS,
simply I am on the wrong network!
(to use FTP, I have to login to a different machine where they allowed
me to have a small account).
Max
_____________________ MAKEFONTS.PS ________________________________
%!
% PostScript code to generate derived fonts for PS-LaTeX
%
% Create a transformed font
% params: symbol for name of new font,
% symbol for name of original font,
% font transformation matrix
% proc to execute on font (the transformed font dict is on the
% top of the stack when this proc is called)
/TransformFont {
30 dict begin % for temporary storage
/Proc exch def % the proc to exec
/TransformMatrix exch def % transform matrix
/BaseName exch def % existing font
/NewName exch def % new name
% find old font, apply transfrom
/BaseFontDict BaseName findfont TransformMatrix makefont def
% make a dictionary for the new font
/NewFont BaseFontDict maxlength dict def
% copy entries into the new dictionary (see Cookbook for expln.)
BaseFontDict
{ exch dup /FID ne
{ dup /Encoding eq
{ exch dup length array copy
NewFont 3 1 roll put }
{ exch NewFont 3 1 roll put }
ifelse }
{ pop pop }
ifelse
} forall
NewFont /FontName NewName put
% call procedure
NewFont Proc
% store new font in fontdict
NewName NewFont definefont
pop
end
} def
% Create an Oblique font
% params: new name for font
% old font
% angle of obliqueness
/ObliqueFont {
20 dict begin
/Angle exch def
[1 0 Angle sin Angle cos div 1 0 0] % transform for obliqueness
{pop}
TransformFont
end
} def
% Create a SmallCaps font...in fact just a copy of the font, and the
% name is used to indicate whether it should be treated differently
% params: new-name, old-name. new-name should include the string
% 'SmallCaps'.
/SmallCapsFont {
[1 0 0 1 0 0] % identity transform
{pop} % no-op
TransformFont
} def
% Create a condensed font with different strokewidth
% params: new font name
% old font name
% factor to condense by (e.g., 0.8)
% factor to thicken lines by (e.g., 1.5)
/CondensedFont {
20 dict begin
/LineThickening exch def
/WidthNarrowing exch def
[WidthNarrowing 0 0 1 0 0] % transform matrix
{dup /StrokeWidth get LineThickening mul /StrokeWidth exch put}
TransformFont
end
} def
% Create a Reduced font
% params: new-name old-name scale
/ReducedFont {
20 dict begin
/reduction exch def
[reduction 0 0 reduction 0 0]
{pop} % no-op
TransformFont
end
} def
/Times-Oblique /Times-Roman 15 ObliqueFont
/Times-BoldOblique /Times-Bold 15 ObliqueFont
%/Times-ItalicUnslanted /Times-Italic -15.15 ObliqueFont
/Symbol-Oblique /Symbol 15 ObliqueFont
/Times-SmallCaps /Times-Roman SmallCapsFont
/Courier-Condensed /Courier 0.85 1.5 CondensedFont
/Helvetica-Reduced /Helvetica 0.875 ReducedFont
/NewCenturySchlbk-SmallCaps /NewCenturySchlbk-Roman SmallCapsFont
% Can use these on a LaserWriter Plus
%/makeLWPlusFonts {
% /Bookman-LightOblique /Bookman-Light 10 ObliqueFont
% /Bookman-LightSmallCaps /Bookman-Light SmallCapsFont
% /NewCenturySchlbk-Oblique /NewCenturySchlbk-Roman 10 ObliqueFont
% /NewCenturySchlbk-SmallCaps /NewCenturySchlbk-Roman SmallCapsFont
% /Palatino-SmallCaps /Palatino-Roman SmallCapsFont
% /Palatino-Oblique /Palatino-Roman 10 ObliqueFont
% /Palatino-BoldOblique /Palatino-Bold 10 ObliqueFont
%} def
------------------------------
Date: Thu, 18 Jul 91 17:30:24 +0000
From: PHY6JAN@uk.ac.leeds.ucs.cms1
Subject: emtex
Dear dr Abbott,
I have already copied EM-TEX from Aston. Main problems I have is where
I can find fonts for EPSON LQ.
In EMTEX subdirectory I found only font LJ_? for laser printers.
Yours sincerely,
Janusz Holender
------------------------------
Date: Fri, 19 Jul 91 14:28:48 +0000
From: Adrian F Clark <alien@uk.ac.essex>
Subject: Re: emtex
> I have already copied EM-TEX from Aston. Main problems I have is where
> I can find fonts for EPSON LQ.
> In EMTEX subdirectory I found only font LJ_? for laser printers.
If the fonts that Robert Tregidgo was asking about a week or so are
suitable for the LQ, I have a copy. Will transfer them to Aston asap.
..Adrian
------------------------------
Date: Mon, 22 Jul 91 11:33:02 +0000
From: Philip Taylor (RHBNC) <P.Taylor@uk.ac.rhbnc.vax>
Subject: RE: emTeX
Janusz ---
>>> I have already copied EM-TEX from Aston. Main problems I have is where
>>> I can find fonts for EPSON LQ.
>>> In EMTEX subdirectory I found only font LJ_? for laser printers.
Coming, shortly.
Philip Taylor
Royal Holloway and Bedford New College,
``The University of London at Windsor''
------------------------------
Date: Wed, 17 Jul 91 18:08:06 +0000
From: LIST_SERVER@uk.ac.tex
Subject: Training Day at RHBNC; 24th July, 1991 (this week!)
There are still a few places left for the Training Day at RHBNC on Wednesday
24th July. Two concurrent seminars are offered (see below for details), and
the price (\pounds 30-00 for members, \pounds 40-00 for non-members) includes
all refreshments including morning, lunch and afternoon breaks. The food is
reportedly excellent ! Please respond immediately by e-mail, telephone or
facsimile to reserve one of the few remaining places; there will be no further
training sessions this year !
- -----------------------------------------------------------------------------
--
Tables in LaTeX | Cross-referencing and the 3 `R's
=============== | ================================
LaTeX hax some powerful table making | Cross-referencing is essential in many
facilities. Most straightforward | typesetting tasks, and yet the Plain
tables can be tackled very readily, | TeX format provides no macros to assist
and generate quite pleasing results. | with this. However, despite the lack
This workshop will cover the basics, | of any Knuthian guidance, cross-refer-
but go on to some of the more subtle | -encing is both interesting and quite
aspects associated with tables and | straightforward, although there are
LaTeX. Manipulating the default | many pitfalls into which the unwary can
parameters sometimes leads to un- | stumble. We will cover both internal
expected results --- but not to | and external cross-referencing (i.e.
those who survive the workshop! We | both avoiding and using external files)
will also cover the inclusion of | and this will lead us on to the whole
footnotes in tables, and deal with | area of \csname, reading and writing
floating, table and tabular env- | (and a little arithmetic) in TeX.
ironments.
- -----------------------------------------------------------------------------
--
Directions: Royal Holloway and Bedford New College is on the A30 between Egham
and Sunningdale, and is within five minutes of the M25 (Staines intersection).
The nearest station is Egham, which is served by half-hourly trains from London
Waterloo; a taxi from the station will take you straight to Founder's building
for a couple of pounds.
- -----------------------------------------------------------------------------
--
Booking arrangements: A booking form may be had on application to Philip
Taylor, The Computer Centre, Royal Holloway and Bedford New College, University
of London, Egham Hill, Egham, Surrey (E-mail: P.Taylor@Uk.Ac.Rhbnc.Vax;
Tel: 0784 443172 (11:00--19:00); Fax: 0784 434348). Reservations may be made
by E-mail, telephone or fax, but confirmation (including payment or an official
order) must be made in writing.
- -----------------------------------------------------------------------------
--
------------------------------
UK TeX ARCHIVE at ASTON UNIVERSITY
*** JANET Interactive and NIFTP access ***
Host: uk.ac.tex (JANET DTE 000020120091)
Username: public Password: public
[Sorry, no Internet ftp access is available yet]
*** Mail server ***
Send mail to TeXserver@uk.ac.tex (JANET)
or TeXserver@tex.ac.uk (rest of the world)
with message body containing the word HELP
*** FILES OF INTEREST ***
[tex-archive]00readme.txt
[tex-archive]00directory.list [tex-archive]00directory.size
[tex-archive]00directory_dates.list [tex-archive]00last30days.files
This year's UKTeX back issues are stored in the archive in directory
[tex-archive.digests.uktex.91]
This year's TeXhax back issues are stored in the archive in directory
[tex-archive.digests.texhax.91]
Latest TeXhax: #31
TeXMaG back issues are stored in the archive in directory
[tex-archive.digests.tex-mag]
Latest TeXMaG: V5N3
*** MEDIA DISTRIBUTIONS ***
Washington Unix TeX distribution tape (latest copy from May/June 1991)
Contains:
TeX 2.993(==3.0), LaTeX 2.09, Metafont 1.9 (2.0), plus many utilities
suitable for Unix 4.2/4.3BSD & System V
tar format, 1600bpi, blockfactor 20, 1 file (36Mb)
Copies available on:
One 2400ft tape sent with return labels AND return postage to Aston
OR One Quarter-Inch Cartridge (DC600A or DC6150)
sent with envelope AND return postage to Nottingham (addresses below).
A VMS backup of the archive requires two 2400ft tapes at 6250bpi.
A VMS backup of TeX 2.991 plus PSprint requires one 2400fttape.
Exabyte 8mm tapes: same contents available as 1/2in tapes.
Following tape types available: SONY Video 8 cassette P5 90MP,
MAXELL Video 8 cassette P5-90, TDK Video 8 cassette P5-90MPB
OzTeX (for Macintosh): Send 10 UNFORMATTED 800K disks with return postage.
emTeX (for MS-DOS):
Send 11 UNFORMATTED 1.44Mb or 18 (EIGHTEEN!) 720K 3.5" disks;
or 12 UNFORMATTED 5.25" disks; with return postage. emTeX is now
distributed with a copy of `Baskerville' and documentation. Please
therefore send the disks in packing of A4 size or enclose an A4 envelope.
*** POSTAGE RATES ***
(all prices in Pounds Sterling)
(For Aston orders, make cheques payable to Aston University)
0.5" tapes: UK: 2.50 (one tape), 5.00 (two tapes).
Europe: 5.00 (one tape), 9.00 (two tapes).
Outside Europe please enquire.
8mm tapes:
UK: 1.00, Europe: 2.00.
Quarter-inch cartridges:
UK: 1.00, Europe: 2.00.
Diskettes:
Quantity/Size Europe World UK 1st UK 2nd
18/3.5" 3.10 5.10 1.40 1.10
11/3.5" 1.80 2.90 0.80 0.65
18/5.25" 1.20 2.00 0.60 0.50
11/5.25" 0.80 1.30 0.50 0.35
*** POSTAL ADDRESSES ***
(Please include SELF-ADDRESSED ADHESIVE LABELS for return postage).
Peter Abbott
Computing Service, Aston University,
Aston Triangle, Birmingham B4 7ET
David Osborne
Cripps Computing Centre, University of Nottingham,
Nottingham NG7 2RD, UK
(for Quarter-inch cartridges ONLY)
(Please include stamps for return postage)
*** UK TeX USERS GROUP ***
For details, contact
Malcolm Clark or Geeti Granger
IRS John Wiley & Sons
Polytechnic of Central London Baffins Lane
115 New Cavendish Street Chichester
London W1M 8JS W Sussex PO19 1UD
email: malcolmc@uk.ac.pcl.mole
End of UKTeX Digest [Volume 91 Issue 29]
****************************************