UKTeX Digest Thursday, 22 Aug 1991 Volume 91 : Issue 34 Today's Topics: {Q&A}: Re: Font arrangements in directory trees fnpara.sty inserts spaces shock horror CSP Macro Package Re: VMS record types and ZAPFILE Re: VMS record types and ZAPFILE AMSTeX beginner Re: AMSTeX beginner RE: AMSTeX beginner Hyphenating hyphenated words Re: Hyphenating hyphenated words TeX printing to LaserJet printer on VAX/VMS? TeX implementations for IBM PC and compatibles Can one use a \loop...\repeat to contribute columns to an \halign? CWEB for DOS ?? {Archive News}: When calling TeXserver, make sure you have enough room!! 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 E d i t o r ' s N o t e This issue is appearing a day earlier than usual and There will be no issue of UKTeX Digest next week, due to editorial holidays; issue 35 will appear in the week beginning Sep 3. ------------------------------------------------------------ Date: Thu, 15 Aug 91 03:04:48 +0100 From: Lutz Birkhahn Subject: Re: Font arrangements in directory trees In UKTeX V91 #17, Philip Taylor writes: > One might therefore have a font hierarchy which > resembles the following (shewn for only 300 and 1270 dpi fonts; others may be > added in a directly analogous manner): > > TeX---Fonts---PK----300----1000----Cmb10 > | | |--Cmbsy10 > | | |-- ... > | | |--Cmvtt10 > | | |-- ... > | | --Manual > | |--1095 > | |--1200 > | |--1440 [...] This is very similar to the arrangement we use in Stefan Lindner's Shareware TeX package for the Atari ST for some years now. There the hierarchy is: tex---prtfonts---res300.slm---mag_1.000---cmr10.pk | | |- ... | |-mag_1.095---cmr10.gf | |- ... |-res300.hpl--- ... |-res300.hpd--- ... |-res101.scr--- ... from left to right: - - tex should be clear - - prtfonts stands for "printer fonts", which isn't quite true, since a screen i s no printer. This could be changed to "fonts" (as Philip suggests) - - the keyword "res" introduces the horizontal resolution in dpi, followed by a three character abbreviation of the device name: "slm" = Atari laser printer slm804 "hpl" = HP Laserjet "hpd" = HP Deskjet "scr" = screen and so on... (I could mail all the abbrevs. if you are interested) Remember, the Atari file system is quite similar to the MS-DOS file system, i.e. 8 characters file name + 3 characters file extension. This should be the least common denominator, if one doesn't want to restrict the names to the six characters of some outdated (?!) proprietary mainframe operating systems. The resolution alone is not enough to distinguish the fonts for different printing engines, as can be seen by the (at least) three different 300 dpi printers used on the Atari: the differences between write-white and write- black are well known now, and clearly there are also differences between a laser printer and an ink jet printer. Generic 300 dpi fonts are the sign of a poor font environment. It should always be the goal to have a font set for every printer model (if not even for every single printer, since there may be significant differences in production from month to month). - - "mag" (magnification) can be followed by zero to four underscores ("_"), then comes the magnification with at least one digit for the integer part and up to three digits for the fraction part (you know, the three chars file extension). On VAX/VMS or Cyber NOS/VE you will be forced to change the dot to an underscore or something similar, but on other machines the dot should be used if ever possible, for this could be the first time there is a plausible reason for haven choosen the dot as separator for the file extension. There were some rumours (in an internal discussion list) that you have to use exactly four underscores in the mag part, but that is not true, at least the DVI drivers from Stefan Lindner are capable to read any number of underscores. The **only** reason besides imitation for most users to use four underscores (or three if the magnification is greater or equal to ten) is to get a better visual appearance: if there are many such path specifi- cations in a column, one above the other, it simply looks best if you make each file name part (the first 8 characters before the dot) of equal length, so as to align the dots. The same goes for the fractional part: zero, one two or three digits are allowed, but it looks better if you always use three digits. mag____1.000 mag1 mag____1.095 looks better, mag1.095 mag____1.200 but is exactly mag1.2 mag___10.000 as "correct" as mag10 mag___12.839 mag12.839 - - At last there is the file itself with the file type as extension. I can't see any reason for Philip's suggestion of placing the file type in front of the path. The GF and PK (no one uses PXL any more, I think) instances of a font deserve to rest in the same directory, just as aux and toc files of a LaTeX document are in the same directory. > The advantage, I believe, is that the magnification-dependent component becom es > unambiguously and predictably specified, and the resolution-dependent > component, having been factored out, is equally unambiguous. I think the main advantage over many common font specifications is that you have separate directories for different printers. Specifying the resolution is more historically based than imperative. A similar specification would be the METAFONT mode (cf. mode_def xxx). The important point is that you have a separate directory name for each separate printer (including the different resolutions some printers can use). > The disadvantages > include greater difficulty in re-using fonts for different resolution devices > (greater intelligence needed in the driver), A standard should not be built on misuse. If you absolutely need to take fonts made for another printing machine, every reasonable operating system provides methods for renaming the files in a whole tree (batch file or shell script being common names for such facilities). > and the omission of any facility for specifying magnifications other > than those which yield integral scale factors; Scale factor 1095 is just as much integral as is 1095.5, since both numbers are real numbers (1.095 and 1.0955), the only difference being the precision. I can't imagine an application where one needs to specify the magnification with more accuracy than one thousandth. Note also that the DVI Driver Standard (draft 0.04c as of 25 March 1991) allows any standard driver to silently take a font with a magnification that deviates as much as 0.2% from the specified magnification. Lutz Birkhahn - -- email: lutz@bisun.nbg.sub.org (please, small scraps only! I have to pay for mail.) ------------------------------ Date: Fri, 16 Aug 91 16:49:01 +0000 From: Robin Fairbairns Subject: fnpara.sty inserts spaces shock horror Some little while ago, I retrieved a copy of fnpara.sty from the archive; it does just what I want, except that its (admittedly beautiful) layout inserts spaces into the body of the text being typeset (i.e., not the footnote itself). Now, I admit that the fact that I noticed this probably results from my thoroughly improper style of writing texts. But then, Ms Knuth seems to think that Don shouldn't use footnotes at all, let alone enough that he would need to set them in paragraphs; so we're all beyond the pale... Nevertheless, here are some (VMS-style) diffs between my version of fnpara that doesn't insert spaces (into my documents ;-) and the original. Robin ************ File TEX$ROOT:[INPUTS.NEW]FNPARA.STY;3 19 \edef\@currentlabel{\csname p@footnote\endcsname\@thefnmark}% 20 %CCCC --- need to set each footnote in an hbox and apply 21 % the fudge factor here: 22 \setbox0=\hbox{\@makefntext 23 %CCCC --- this needs a parameter ****** File TEX$ROOT:[INPUTS.NEW]FNPARA.STY;1 19 \edef\@currentlabel{\csname p@footnote\endcsname\@thefnmark} 20 %CCCC --- need to set each footnote in an hbox and apply 21 % the fudge factor here: 22 \setbox0=\hbox{% 23 \@makefntext 24 %CCCC --- this needs a parameter ************ ************ File TEX$ROOT:[INPUTS.NEW]FNPARA.STY;3 32 \penalty -10\relax 33 \hskip\footglue 34 }% end of parameter 35 }% end of \hbox 36 \dp0=0pt \ht0=\fudgefactor\wd0 \box0 37 }% end of \footins 38 }% end of \def 39 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ****** File TEX$ROOT:[INPUTS.NEW]FNPARA.STY;1 33 \penalty -10 34 \hskip\footglue 35 } % end of parameter 36 } % end of \hbox 37 \dp0=0pt \ht0=\fudgefactor\wd0 \box0 38 } % end of \footins 39 } % end of \def 40 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ************ ------------------------------ Date: Fri, 16 Aug 91 16:50:15 +0000 From: Neil Davies Subject: CSP Macro Package I find myself wanting to typeset some CSP, anyone out there got/know about a latex style for this? Many Thanks Neil Davies ------------------------------ Date: Fri, 16 Aug 91 18:52:10 +0000 From: SYSMGR@uk.ac.kcl.ph.ipg Subject: Re: VMS record types and ZAPFILE > I mailed UkTeX recently (91-27) with a problem with the TFM files for > AMSTeX, and Brian HK explained that binary files in the Aston archive > were stored in variable length, max510byte files, but that TeX on VMS > expects fixed length 512 byte files. he also said that there could be > a utility to convert these files somewhere in the archive. ... text deleted > So I looked in the archive and found a utility called ZAPFILE, which > seemed to be what I was looking for. So I did what I thought would do > the conversion: > zapfile *.*pk/type=fixed/record_size=512/maximum_record_size=512 No chance! Some explanation is probably in order for people whose view of the computer workd is derived from UN*X or MS/DOS, where a file is simply a string of bytes. On VMS, a file has two components: a header and a data area. The header includes a description of how the data area is to be interpreted by the system. In many cases, this means that some of the data in the data area is 'private' to the record management system (loosely speaking, filesystem services), and is not normally returned to a program. ZAPFILE, as its name suggests, is a dangerous tool. It allows you to alter the file description in the header, leaving the data area totally untouched. If the help file with it is the one I edited, it includes a warning that in the hands of the uninitiated, ZAPFILE is the quickest way to trash a file that a VAX knows of! (I renamed it and edited the HELP file a little. The original is called FILE, written by Joe Meadows, distributed vis DECUS. FILE sounded far too harmless!) In the case of variable-length records, the VAX internal structure is that each record (returned to a program by a READ statement) is prefixed by a 2-byte length count. Fixed length records have no prefix. If you ZAPFILE variable to fixed, the internal data ceases to be interpreted and instead is doled up in fixed-size chunks - length prefix included. What you need, to convert variable-to-fixed, is a rather hard-to-write copy program that uses a cyclic buffer to read in variable length chunks and write fixed ones. Sorry, I don't have one to hand. COPY and CONVERT will beither work: they will always convert records on a 1:1 basis, probably padding 510-byte variables with 2 null bytes if creating 512-FIXED. What ZAPFILE is valuable for is for converting between STREAM files and FIXED-length record ones. I can't remember when and where this problem arose, but it was something to do with TFMs or GFs. MetaFont output them one way and GFTOPXL wanted them the other, or something like that... If you grew up on VAXes and IBMs, this is all completely natural and you think U**X and MS/DOS are wierd. I guess its true the other way around as well... Hope this helps, Nigel Arnot ------------------------------ Date: Sat, 17 Aug 91 15:02:00 +0100 From: Max Calvani - Italy Subject: Re: VMS record types and ZAPFILE ZAPFILE: I agree that it is VERY dangerous, however there is a way to remeber how to go back to the original file. Look in the help. I find it VERY useful to convert stream_lf files that are produced by various programs in C, to VMS-good files. Max ------------------------------ Date: Mon, 19 Aug 91 16:29:00 +0000 From: Peter Flynn UCC Subject: AMSTeX beginner A user needs AMSTeX to print some docs sent over the net. I see 1633 files in the Aston Archive related to AMSTeX! Which ones do I need to get started? There's no way I am going to ftp all 1633 files...is there a new user's guide written in Plain or LaTeX which would point me in the right direction? ///Peter ------------------------------ Date: Mon, 19 Aug 91 21:10:00 +0100 From: Max Calvani - Italy Subject: Re: AMSTeX beginner There is a book called "The Joy of TeX" by Michael Spivak that is Amstex's guid eMax ------------------------------ Date: Tue, 20 Aug 91 07:47:00 +0000 From: malcolm Subject: RE: AMSTeX beginner i trust you have either edition of AmSTeX, a gourmet guide etc. by Spivak MD? what a lot of amstex files. how did you determine that? malcolm ------------------------------ Date: Tue, 20 Aug 91 08:31:00 +0000 From: malcolm Subject: Hyphenating hyphenated words some time ago someone wanted to hyphenate an already hyphenated word. in other words, given a word like `pin-pricking' it might be necessary to have TeX hyphenate the `pricking' part. TeX will not do this without encouragement. in particular it is not possible to include such a word in the \hyphenation exception dictionary. on the other hand, since this is a problem already encountered within foreign languages (you know, the weird ones with accents and all that silly stuff) where TeX will not hyphenate after a control sequence (and most accents are control sequences), there are solutions: norbert schwarz came up with \nobreak\hskip0pt immediately after the accented character. this fools TeX into thinking that there is a new word starting there. now this is just what we want TeX to think after an explicit hyphen. (well, i don't actually think we do, but for the purposes of this example, there might be a case). so, explicit and inserted hyphens are different. an explicit hyphen should expand to `-\nobreak\hskip0pt'. since the @ is an undersused character, make it active and \def@{-\nobreak\hskip0pt} so that pin-pricking is now written pin@pricking, where it ought to hyphenate to pin-prick-ing. somehow i don't think that making `-' the active character is going to work, but that's only intuition. of course, there is a flaw. its correction is left as an exercise to the reader. ******************************************************************* malcolm clark * normal meaningless and irs, pcl * and pretentious statement etc. * found about here ******************************************************************* ------------------------------ Date: Tue, 20 Aug 91 10:58:49 +0100 From: schoepf%de.zib-berlin.sc@uk.ac.nsfnet-relay Subject: Re: Hyphenating hyphenated words Malcolm writes: should expand to `-\nobreak\hskip0pt'. since the @ is an undersused character, make it active and \def@{-\nobreak\hskip0pt} Very dangerous. In AMS-TeX and AMS-LaTeX @ is already anbactive character, with a very special meaning. Rainer Rainer Schoepf Konrad-Zuse-Zentrum ,,Ich mag es nicht, wenn fuer Informationstechnik Berlin sich die Dinge so frueh Heilbronner Strasse 10 am Morgen schon so D-1000 Berlin 31 dynamisch entwickeln!'' Federal Republic of Germany or ------------------------------ Date: Tue, 20 Aug 91 16:04:02 +0000 From: David Osborne Subject: TeX printing to LaserJet printer on VAX/VMS? David Godfrey of the Home Office (tel: 071-273 2221) has a problem with connecting a Brother HL8E (emulating a Hewlett-Packard LaserJet II) to a VAX/785 running VMS 5.3. The printer is connected to a terminal port (TXA5:) and he is currently COPYing the *.JEP file produced by Nelson Beebe's DVIJEP to this port, but the characters are not printed in the correct positions on the page, implying that the data stream to the printer is being corrupted somehow. He has followed my old `recipe' for setting up the printer port $ SET TERMINAL TXxx:/PERM/NOBROADCAST/NOTYPEAHEAD/NOWRAP/SPEED=9600- /NOMODEM/WIDTH=80/PAGE=0/DEVICE=UNKNOWN/EIGHTBIT/NOSCOPE/PASTHRU but it's 4 years since we ran TeX on VMS, and I'm not sure if this still applies to the current version of VMS. If anyone is using LaserJets or printers which emulate them on VMS, please phone David with the details of how to set them up, or mail me and I'll pass on the information. Thanks - --dave David Osborne, Cripps Computing Centre, University of Nottingham d.osborne@mips.nott.ac.uk ------------------------------ Date: Wed, 21 Aug 91 09:55:20 +0000 From: Chris Dorling Subject: TeX implementations for IBM PC and compatibles Please send me details of implementations of TeX available for use on IBM PC compatibles, including any which may be run under Windows 3.0, indicating those which are commercially available and those which are public domain or shareware. Thankyou. ------------------------------ Date: Wed, 21 Aug 91 21:44:14 +0000 From: Brian {Hamilton Kelly} Subject: Can one use a \loop...\repeat to contribute columns to an \halign? I'm trying to write a (raw) TeX program that will set a number of different characters next to each other (number of characters unknown until other macros, not shown below, determine the [contiguous] sequence of non-empty characters in the font). Furthermore, I want to repeat each such row a number of times. To my consternation (well, not really ;-) I discovered that including a `&' within a \loop...\repeat upsets TeX --- it complains about the \endtemplate contributed [Runaway argument...Forbidden control sequence encountered when scanning use of \loop]. But I can hide that by including a separate macro \endcolumn. But the rather more major problem is that when \endcolumn is expanded, and the & seen by \halign, it *terminates* a group, thus restoring the saved version of \body created by the *enclosing* loop. Funnily enough, the same problem doesn't seem to arise from the \cr contributed to the outer loop at the end of \drawrow. I've tried all the dirty tricks going with brace hacks, to no avail, because the group ended by the & isn't started by any such animal. I've got over the problem by using a sledgehammer: I save the outer loop's \body and make the \body of the inner loop \global --- since the enclosing group is still restored by the &, this entails making all the arithmetic with my counters global too. Needless to say, I'm not happy with these macros (even though they work) so I'd prefer to know how to do it `properly'. (Incidentally, an earlier version had loops *outside* the \halign, and constructed the lines of the alignment by gradually extending a macro. But that's not satisfactory if there are a lot of rows and/or columns because of the time taken in performing the \xdef each time around. I haven't tried constructing a token list: perhaps that's the solution?) Anyone got any ideas? Here's some excerpts from my .tex file (\scale being the macro that's supposed to get the whole kit-and-caboodle going)... > > ... > > \newcount\m \newcount\n \newcount\p \newdimen\dim > \newcount\first \newcount\last \newcount\rows \newdimen\boxwd > \newlinechar=`@ > > ... > > \def\scale{$$\global\n=0 > \halign to\hsize{& \hfil ##\hfil \cr > {}% Something to ensure that \halign doesn't scan the \loop after > % reading the \cr at the end of the preamble > \loop \message{Row \the\n@} > \drawrow > \ifnum \n<\rows \global\advance \n 1 > \repeat \crcr > }$$ > } > > \def\drawrow{\global\m=\first > \global\let\oldbody=\body > \loop > \message{Char \the\m@} > \global\let\body=\body > \hbox to\dim{\leaders\hbox{\char\m}\hfil}% > \ifnum \m<\last \global\advance \m 1 > \endcolumn > \repeat \cr > \let\body=\oldbody > } > > \def\endcolumn{& } > > ... > 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: Thu, 22 Aug 91 11:46:19 +0000 From: CA_ROWLEY@uk.ac.open.acs.vax Subject: CWEB for DOS ?? I have been asked if CWEB is available for the MS-DOS operating system. All information gratefully received. Chris Rowley ------------------------------ Date: Sat, 17 Aug 91 11:22:44 +0000 From: Brian {Hamilton Kelly} Subject: When calling TeXserver, make sure you have enough room!! I've posted a similar message before to UKTeX and TeXhax, but it seems I must reiterate... Noticing that the TeXserver (@uk.ac.tex) had ground to a halt on 13th August, I attempted to restart it and discovered that the account had no disk quota left. Investigation showed that nearly 19MB of traffic had been bounced back since it was last started (on the 9th); I didn't have time nor inclination to read all of the bounced mail, but a very large proportion was there because the addressee (who'd requested the traffic in the first place) didn't have sufficient disk quota to receive all the incoming mail. So please ensure that you _have_ got room for all that you request: if you're not sure how much space will be required, each directory in the Aston Archive contains a 00files.txt file which lists file sizes in bytes, whilst the 00directory.size file lists the entire archive, with sizes given in (512-byte) blocks --- this file itself is nearly 2200 blocks long however. 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) + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------ UK TeX ARCHIVE at ASTON UNIVERSITY >>> UK.AC.TEX <<< 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 \section FILES OF INTEREST [tex-archive]00readme.txt [tex-archive]00directory.list [tex-archive]00directory.size [tex-archive]00directory_dates.list [tex-archive]00last30days.files \section DIGESTS 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: #36 TeXMaG back issues are stored in the archive in directory [tex-archive.digests.tex-mag] Latest TeXMaG: V5N3 \section MEDIA DISTRIBUTIONS \subsection Washington Unix TeX distribution tape Latest copy of May/June 1991 contains: TeX 3.14, LaTeX 2.09, Metafont 2.7, 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 0.5" tape sent with return labels AND return postage to Aston OR One Quarter-Inch Cartridge (DC600A or DC6150) sent with envelope AND stamps for return postage to Nottingham (addresses below). \subsection VMS tapes VMS backup of the archive requires two 2400ft tapes at 6250bpi. VMS backup of TeX 2.991 plus PSprint requires one 2400ft tape. \subsection Exabyte 8mm tapes Same contents available as 0.5" tapes. Following tape types available: SONY Video 8 cassette P5 90MP, MAXELL Video 8 cassette P5-90, TDK Video 8 cassette P5-90MPB \section TeX IMPLEMENTATIONS FOR SMALL COMPUTERS \subsection OzTeX (for Macintosh) Send 10 UNFORMATTED 800K disks to Aston with return postage. \subsection emTeX (for MS-DOS) All enquiries for disks etc. should be directed to: Eigen PD Software, P.O. Box 722, Swindon SN2 6YB (tel: 0793-611270) (JANET e-mail address: kellett@uk.ac.cran.rmcs) \subsection TeX for the Atari ST All enquiries for disks etc. should be directed to: The South West Software Library, P.O. Box 562, Wimborne, Dorset BH21 2YD (JANET e-mail address: mdryden@uk.co.compulink.cix) \section 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 \section 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 -- include stamps for return postage) \section UK TeX USERS GROUP For details, contact: Malcolm Clark IRS, Polytechnic of Central London, 115 New Cavendish Street, London W1M 8JS e-mail: malcolmc@uk.ac.pcl.mol e or Geeti Granger, John Wiley & Sons, Baffins Lane, Chichester, W Sussex PO19 1UD \bye End of UKTeX Digest [Volume 91 Issue 34] ****************************************