UKTeX Digest Friday, 7 Sep 1990 Volume 90 : Issue 30 Today's Topics: Aston archive 00* listing files Latest versions of TeX and MF available for VMS Long citations Re: UKTeX V90 #29 Spellcheckers Re: Euler fonts in strange sizes / new font selection dvi driver for atari st Building TeX under DOS Extender LaTeX and BibTeX styles for citations and reference-lists ----------------------------------------------------------------------------- Moderator: Peter Abbott Editor: David Osborne (University of Nottingham) Submissions: uktex@uk.ac.aston Administration: uktex-request@uk.ac.aston Back Issues: These are stored in the Aston archive, in the directory DISK$TEX:[TEX-ARCHIVE.DIGESTS.UKTEX.90] Latest TeXhax: #57 Back Issues: These are stored in the Aston archive, in the directory DISK$TEX:[TEX-ARCHIVE.DIGESTS.TEXHAX.90] Latest TeXmag: V4 N3 Back Issues: These are stored in the Aston archive, in the directory DISK$TEX:[TEX-ARCHIVE.DIGESTS.TEX-MAG] E d i t o r ' s N o t e The next issue of UKTeX Digest will be delayed while I am in Ireland for the European TeX meeting in Cork. Issue #31 should appear on Monday, September 24th. ------------------------------------------------------------ Date: Tue, 04 Sep 90 13:39:57 -0000 From: TEX@rmcs.cran.ac.uk Subject: Aston archive 00* listing files In response to customer suggestions (and to make use of a program that I wrote a year ago), I've made some changes to the 00*.* listing files scattered around the archive. ARCHIVE LISTINGS ~~~~~~~~~~~~~~~~ At the top of the archive you will now find the files: disk$tex:[tex-archive]00directory.list disk$tex:[tex-archive]00directory.size disk$tex:[tex-archive]00last7days.files disk$tex:[tex-archive]00last30days.files Their contents are summarised briefly below: 00directory.list - all of the files in the archive grouped by directory. 00directory.size - all of the files in the archive grouped by directory. The size and date of each files is also listed. 00last30days.files - files in the archive which have been changed in the last 30 days listed in descending date order. The date, size, contents and full file specification is listed for each file in '00files.txt' format (see below). 00last7days.files - files in the archive which have been changed in the last 7 days listed in descending date order. The date, size, contents and full file specification is listed for each file in '00files.txt' format (see below). NOTES: With the exception of 00last7days.files (which didn't exist), these names used to begin with THREE zeros. The old files will remain for a while but will not be updated. The new files will be updated every day at about 0130 UK time (BST/GMT). DIRECTORY LISTINGS ~~~~~~~~~~~~~~~~~~ In every (non-empty) directory of the archive, you should find a file called 00files.txt which lists all of the files in that directory in descending date order. The date, size, contents and full file specification is listed for each file. For example, here is the 00files.txt from the directory DISK$TEX:[TEX-ARCHIVE.AMSTEX] >Files matching DISK$TEX:[TEX-ARCHIVE.AMSTEX]*.* >listed in reverse time order (listing updated: 26-Aug-90 15:52). > >Last change Size Type File specification >----------------------------------------------------------------------------- >30-Apr-90 11:13 - DIR disk$tex:[tex-archive.amstex]trip.dir >30-Apr-90 11:13 - DIR disk$tex:[tex-archive.amstex]doc.dir >30-Apr-90 11:13 - DIR disk$tex:[tex-archive.amstex]amstex-style.dir >13-Jul-89 20:06 12110 BIN disk$tex:[tex-archive.amstex]amstex.doc_z >13-Jul-89 20:05 10166 BIN disk$tex:[tex-archive.amstex]amsppt.doc_z >13-Jul-89 20:05 30856 BIN disk$tex:[tex-archive.amstex]amsman.tex_z >13-Jul-89 20:05 1296 BIN disk$tex:[tex-archive.amstex]amsman.hdr_z >13-Jul-89 20:05 1014 BIN disk$tex:[tex-archive.amstex]amsman.errata_z >14-Apr-86 21:32 1018 TXT disk$tex:[tex-archive.amstex]amstex.chg >----------------------------------------------------------------------------- NOTES: The size is in bytes (not VMS blocks). The Type will be one of: BIN - binary file (use /ENCODE with the mail server) DIR - VMS directory (don't try to fetch these) TXT - ordinary text file The directory contents are checked every day, and the 00FILES.TXT files updated only if something has changed in the directory. The contents of 00LAST7DAYS.FILES and 00LAST30DAYS.FILES in the top level directory are in this format, except that the first two lines are slightly different: >Files matching DISK$TEX:[TEX-ARCHIVE...]*.* >modified since 21-Aug-90 00:00 (listing updated: 27-Aug-90 01:49). > >Last change Size Type File specification >----------------------------------------------------------------------------- If you find any problems, errors, or have any comments to make, please direct them to me or . Niel Kempson Aston University TeX archive group +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + JANET: tex@uk.ac.cranfield.rmcs + + BITNET: tex%uk.ac.cranfield.rmcs@ukacrl + + INTERNET: tex%uk.ac.cranfield.rmcs@nsfnet-relay.ac.uk + + UUCP: {mcvax,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) 785687 (UK), +44-793-785687 (International) + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------ Date: Fri, 31 Aug 90 09:51:00 -0700 From: DHOSEK%EDU.CLAREMONT.HMCVAX@UK.AC.NSFNET-RELAY Subject: Latest versions of TeX and MF available for VMS The latest versions of TeX and MF for VMS are now available from ymir.claremont.edu. A few bug fixes and minor enhancements have been made to the TeX change file bringing it to 3.0/3.2 (the latter number is the change file version). The upgrade of this change file is not necessary if you have 3.0/3.1a, but is worthwhile. Files are in [anonymous.tex.sources.tex3_0]. MF 2.0/2.1a is now officially available for VMS. There is an increase in the speed of the system through some assembly routines contributed by John Lavagnino and all on-line displays are accessed through VMS sharable libraries. At present only one library, the GraphOn-140 1.0a library is available, although others are under development (contact Don Hosek, dhosek@ymir.claremont.edu if you intend to create a library to find out if anyone else is working on one and for advice in creating the library). Files are in [anonymous.tex.sources.mf2_0]. The files 00readme.txt in each directory indicate what the files are. Below are vms_tex_notes.txt and vms_mf_notes.txt from those directories. Help files are under development and will be announced shortly. Those without FTP access can obtain the files from mailserv@ymir.claremont.edu. Directory specifications are identical, but without the :anonymous" at the beginning. The command to retrieve a file is "send", e.g., send [sources.tex3_0]00readme.txt Binary files are not currently available via mailserv. Nothing can be done about this deficiency at this time. These versions of TeX and MF will be available on tape from DECUS and Stanford by mid-September (I think). - ------ Some notes on the version of TeX for VMS located in this directory: - The version number on the change file is currently 3.2 - Note that a larger version of TANGLE is necessary to Tangle this code. I used max_names=5000 and max_toks=52000 to get it compiled. - The Pascal code generated by TANGLEing TEX.WEB will not compile properly with Pascal versions prior to 4.0. - TeX is now called through the CLI. You should install the file TEX.CLD in the system DCL tables. The following options are provided: /BATCH Run TeX in batch mode sending no output to the terminal and ending with a fatal error if input is necessary. The default is /NOBATCH. /CONTINUE Indicate that TeX is to continue execution after the editor is invoked with an 'E' response at an error prompt. The default is /NOCONTINUE /DIAGNOSTICS Indicate that an LSE Diagnostics file be written. A file name can be specified using /DIAGNOSTICS=fn. The default is /NODIAGNOSTICS. /DVI_FILE= Indicate the name of the DVI file to write. The default is to use the name of the TeX job for the DVI file name. This qualifier is negatable. /EDITOR= Indicate the name of the editor to be used at the 'E' response. The options are: + Callable_EDT + Callable_LSE + Callable_TECO + Callable_TPU + The name of a command to be run in a subprocess which will take three arguments: 'p1 is the name of the file to edit, 'p2 is the line number with the error and 'p3 is the column number of the error. If the value given with /EDITOR ends in a colon, TeX will assume that it's a logical name and attempt to translate it. The default is /EDITOR=TEX_EDIT:. This qualifier is negatable. /FORMAT= Indicate the name of a format to pre-load when running. The default varies depending on the specific verb used. This qualifier is negatable. /INIT Run IniTeX rather than TeX. The default is /NOINIT. INITEX should be set equivalent to TEX/INIT/NOFORMAT. /JOBNAME_SYMBOL= Indicate the name of a DCL symbol to which the TeX jobname is to be written. The default is /JOBNAME_SYMBOL=TEX_JOBNAME. This qualifier is negatable. Negation causes the symbol to not be written. /LOG_FILE= Indicate the name of the LOG file to write. The default is to use the name of the TeX job for the LOG file name. This qualifier is negatable. /TEXFONTS= These qualifiers are not intended to be used /TEXFORMATS= by the end-user; they specify the names of the /TEXINPUTS= logicals to be used for the locations of TFMs, format and pool files, and input files respectively. They are provided to allow sites to customize these values without recompiling TeX. - INITEX is part of the main TeX module. Thus, there is only one change file and one executable. The price that we pay is trivial: three if statements operating on a boolean variable and an executable 25K larger. The three if statements are all out of the inner loop so other than a slightly increased startup time, TeX will not be slower. - This is 64bit TeX. If memory is really a problem, you can reduce the main memory array and recompile. Personally, I think that it's inconvenient to try and run TeX at two memory sizes so I don't recommend it. - In previous versions of VMS TeX with an editor interface, TeX continued after leaving the editor. This behavior is incorrect and has been changed. - ----- Some notes on the version of MF for VMS located in this directory: - The version number on the change file is currently 2.1a - Note that a larger version of TANGLE is necessary to Tangle this code. I used max_names=5000 and max_toks=54000 to get it compiled. - MF is now called through the CLI. You should install the file MF.CLD in the system DCL tables. The following options are provided: /BASE= Indicates the base file to be "preloaded" by MF. The default varies depending on the version of MF being used. The default CLD uses /BASE=plain for MF and /NOBASE for INIMF. /BATCH Run MF in batch mode sending no output to the terminal and ending with a fatal error if input is necessary. The default is /NOBATCH. /CONTINUE Indicates that MF should continue after editing a file. The default is /NOCONTINUE /DIAGNOSTICS= Indicate that an LSE Diagnostics file be written. A file name can be specified using /DIAGNOSTICS=fn. The default is /NODIAGNOSTICS. /DISPLAY= Indicates the name of the display for on-line graphics. The default is /DISPLAY=MFTERM: /EDITOR= Indicate the name of the editor to be used at the 'E' response. The options are: + Callable_EDT + Callable_LSE + Callable_TECO + Callable_TPU + The name of a command to be run in a subprocess which will take three arguments: 'p1 is the name of the file to edit, 'p2 is the line number with the error and 'p3 is the column number of the error. If the value given with /EDITOR ends in a colon, TeX will assume that it's a logical name and attempt to translate it. The default is /EDITOR=TEX_EDIT:. This qualifier is negatable. /GF_FILE The GF file to which output should be written. The default is to write to a file with file name equivalent to the MF jobname and extension given by the resolution * magnification of the MF run. This qualifier is not negatable. /GLIB_INDEX= Indicates the name of the index file for displays. /INIT Run IniMF rather than MF. The default is /NOINIT. The INIMF verb automatically selects /NOBASE /JOBNAME_SYMBOL= Indicates the name of a symbol in which MF should store the name of the GF file it writes. The default is /JOBNAME_SYMBOL=MF_JOBNAME This qualifier is negatable. If either it or /JOBSIZE_SYMBOL is negated, no symbols are written. /JOBSIZE_SYMBOL= Indicates the name of a symbol in which MF should store the numeric portion of the GF file which it writes. The default is /JOBSIZE_SYMBOL=MF_JOBSIZE. If either it or /JOBNAME_SYMBOL is negated, no symbols are written. /LOG_FILE= Indicate the name of the LOG file to write. The default is to use the name of the TeX job for the LOG file name. This qualifier is negatable. /MFBASES= These qualifiers are not intended to be used /MFINPUTS= by the end-user; they specify the names of the logicals to be used for the locations of base input files respectively. They are provided to allow sites to customize these values without recompiling MF. - INIMF is part of the main MF module. Thus, there is only one change file and one executable. - In previous versions of VMS MF with an editor interface, MF continued after leaving the editor. This feature is now controlled by the switch /CONTINUE. - On-line displays are now stored in separate sharable libraries. Each library intended to be used with MF must contain the following routines. (Note: C protocols are untested and may be wrong for libdrrow.) + LIBINITSC: Handles whatever initializations are necessary to use the display and prints a banner line on the display. This routine is always called, even if no graphics are used, so it may be wise to hold off initializations of the display itself until LIBSTARTS is called and only initialize static variables etc. This routine is passed the addresses of two integer variables whose values should be set to the horizontal and vertical sizes of the display. PROTOCOL: Pascal procedure LIBINITSC(var x_size, y_size : integer); C void LIBINITSC(x_size, y_size) int *x_size, *y_size; + LIBSTARTS: Called before the first write to the screen. should handle any screen initializations and leave the graphics screen blank and ready-to-write. Upon completion, the terminal should be in text mode, if possible. PROTOCOL: Pascal procedure LIBSTARTS; C void LIBSTARTS() + LIBBLRECT: Erases a rectangle whose boundaries are given as arguments to the procedure in integer quantities. Upon completion, the terminal should be in text mode, if possible. PROTOCOL: Pascal procedure LIBBLRECT(left_col,right_col,top_row,bot_row:integer); C void LIBBLRECT(left_col, right_col, top_row, bot_row) int left_col, right_col, top_row, bot_row; + LIBDRWROW: Draws a row of alternatingly black and white pixels which alternate between black and white between columns a[i] on row r for n columns. With initial color b. See the MF source or a sample library for details. Should leave the terminal in TEXT mode if at all possible. PROTOCOL: Pascal type trans_spec= array[0..65536] of integer; procedure LIBDRWROW(r: integer; b:0..1; a:trans_spec; n: integer); C void LIBDRROW(r, b, a, n) int r, b, n; int a[65536]; + LIBUPDTSC: Makes sure that everything on the display is up-to-date. This is particularly valuable for those displays which cannot easily erase portions of the screen. Should leave the terminal in TEXT mode if at all possible. PROTOCOL: Pascal procedure LIBUPDTSC; C void LIBUPDTSC() + LIBCLOSSC: Restores the terminal back to a normal state. It is not necessary to clear the graphics screen unless not doing so would interfere with use of the terminal's text mode. PROTOCOL: Pascal procedure LIBCLOSSC; C void LIBCLOSSC() + LIBLEVEL: A function which returns 0. This is meant for future expansion of the graphics library functionality. PROTOCOL: Pascal function LIBLEVEL: integer; C int LIBLEVEL() ------------------------------ Date: Mon, 03 Sep 90 17:42:34 -0000 From: DVJM@UK.AC.GLASGOW.CS Subject: Long citations I'm in the habit of using long citations, [Kwiatkowska et al.~1990] being one of the worst. How can I persuade latex to insert suitable linebreaks ? The obvious \bibitem[Kwiat\-kow\-ska et al.~1990]{Marta} doesn't work. Many thanks. David Murphy, | JANET: dvjm@uk.ac.glasgow.cs Dept. of Computing Science, | UUCP: ..!mcsun!ukc!uk.ac.glasgow.cs!dvjm University of Glasgow, | ARPA: dvjm%cs.glasgow.ac.uk@nsfnet-relay.ac.uk Glasgow G12 8QQ, SCOTLAND + Necessity is the mother of strange bedfellows ------------------------------ Date: Mon, 03 Sep 90 18:28:00 -0700 From: DHOSEK%EDU.CLAREMONT.HMCVAX@UK.AC.NSFNET-RELAY Subject: Re: UKTeX V90 #29 >I have been informed by Neil Kempson at RMCS (Cranfield) that it is >possible to obtain from Aston University a copy of BigTex for an >IBM pc. I have at present PC-Tex but I have problems with Tex memory >when compiling my thesis. I would appreciate if you could help me with >this matter. One other possibility to consider, since you've already invested in PCTeX, is upgrading to PCTeX 3.0 (this will cost, I believe $50). I haven't tried the upgrade myself, but the catalog claims a speed increase of 10% over the last release (2.93? I don't have the catalog handy, so these stats are from memory) and double the main memory. They also have released versions of TeX for 386-based PCs which are faster and have double the main memory and 4x the main memory. - -dh ------------------------------ Date: Tue, 04 Sep 90 08:13:16 -0000 From: XUUM29@UK.AC.UMIST.CENTRAL-SERVICES.PRIME-A Subject: Spellcheckers SOmeone mentioned that there is a program to strip out the LateX command strings from a file so it can be passed through a spell/grammar checker. Is this true and if so could someone direct me to where I could obtain it from (preferably including source code) Many thanks Steve C. ------------------------------ Date: Tue, 04 Sep 90 08:19:36 -0000 From: XUUM24@UK.AC.UMIST.CENTRAL-SERVICES.PRIME-A A few simple questions regarding LaTeX. i) in maths how do you generate the `therefore' symbol ie. the three dots? ii) does anyone have a copy of the program which strips out LaTeX commands so you can use a spell checker on the text? I believe its called 'unretex'. I can run it on PC, Atari ST or Amiga - sorry none of these flashy Sun workstations here. iii) Style files - I've seen so many of these. Is there any documentation anywhere which tells what they do and how to use them? iv) I've seen some talk about PicTex - what is it and what does it do? Thanks for any help Steve C. ------------------------------ Date: 04 Sep 90 08:21:46 +0000 From: PZF5HZ%EARN.DRUEDS2@UK.AC.EARN-RELAY Subject: Re: Euler fonts in strange sizes / new font selection > > I am in the early stages of working up a LaTeX document style which > will use the concrete fonts with Euler maths (as in `Concrete maths'). > I am using the new font selection scheme for LaTeX, and I've been > looking at the `concrete.sty' file provided with it. in this file, a > whole bunch of small-size Euler fonts (eurm & euex) are used. I would > like to use these too, especially the euex, but we have a much more > limited set of pk files (5,7,10 for euex, 9,10 for eurm). > > I know the metafont source isn't available for these, but obviously > someone, somewhere, has the pks & tfms. So... can anyone tell me > where they are? > The whole set of Euler fonts is now in the public domain. They are available at Heidelberg and other places (Aston probably too). There are a few problems: the files contain formfeed chars which are not allowed on some MF implementations. It is also necessary to compile them with the plain and *not* the cmbase, otherwise one will run into errors. While I have the stage, I would like to remind everybody that the new font selection is a beta-testing release and that we are very eager to get status reports, even if they are only saying that ``I use the new font selection and ran into no problems''. It will definitely help to get information about the number of sites and users that switched to the new mechanism, as well as problem reports or difficulties when setting up the format or running older documents with the new scheme. In case of problems, please note, that it is possible that you use an old version and that we therefore need *all* file version numbers to locate the problem. This includes the information in the format log file. Frank Mittelbach ------------------------------ Date: Tue, 04 Sep 90 11:05:00 +0100 From: VOGEL@EARN.MPIAHD Subject: dvi driver for atari st I'm using TEX on ATARI ST with a 24-dot matrix printer EPSON LQ 500. I've got a DVI driver for the resolution 180*180 dpi but I want to use the 360*180 dpi resolution. Does anybody now where I can get a DVI driver for this resolution? The printer isn't able to print with 360*360 dpi so I can't use these drivers. Thank you and please reply to: VOGEL@DHDMPI5V.BITNET A. Vogel ------------------------------ Date: Wed, 05 Sep 90 17:37:31 +0000 From: Graham Toal Subject: Building TeX under DOS Extender Dear netland, I'm trying to do something which probably hasn't been done before, and I've hit a problem. If anyone has already tried anything similar, I'd appreciate if you could get in touch please: I'm trying to make a version of TeX for MSDOS which will run under a DOS Extender; this means that as far as the C program is concerned, you appear to have a real computer with a large flat address space. You can, for instance, have .exe files which are a megabyte large, and they still load and run correctly, or you can allocate vast areas off the heap - 3 Mb for instance, in one block. (I'm using Microsoft C and OS/286 dos extender) I've had quite a lot of success. I've got everything compiled, and it sort of runs, but I get strange TeX errors while TeX'ing the plain base file. The interesting thing is that I get very similar style of errors whether I'm running a version of CTeX that I've ported, *or* CommonTeX. The fact that these are two very different sources written by different people in different styles suggests that the problem is something pretty basic. My current theory is that it is because MSC's ints are 16 bits wide. I *have* #defined SIXTEENBITS, and typedef'd integer as long where appropriate, but the word size is the only difference I can see between this port and *the same source files* compiled on other (32 bit, non Intel) machines. I'm going to try a 32-bit 386 compiler next, and a 386 DOS extender (as soon as our purchasing folks can buy one :-() but it will be an awful waste if there is another reason causing the problems. The only other significant change I've made is that all TeX's large arrays are now taken off the heap, rather than being static, because very large static arrays weren't handled well by the dos extender. This also gives the advantage that the development cycle is vastly speeded, since I can generate a larger version of TeX by setting an environment variable or command line parameter -- instead of a 40 minute recompilation. The point of this exercise was originally to be that I would first port a straight TeX, with normal memory, and when that worked, I would go over to a huge TeX with double-sized memory (a la Unix). We have some particularly large tables which could have used this immediately -- it seemed the easier option over totally redesigning our table generator. Many thanks indeed if you have worked on anything similar and can offer advice. (Or even better, a working program ;-) ) Graham Toal PS - the sort of thing going wrong is that stuff like \newbox doesn't work, or other perfectly simple TeX commands go totally weird. CommonTeX got further that CTeX; I managed to build a base file, but it went wrong on trivial documents. ------------------------------ Date: Fri, 07 Sep 90 13:00:00 -0000 From: David Rhead Subject: LaTeX and BibTeX styles for citations and reference-lists I have produced a number of LaTeX style-option files and BibTeX style files that are concerned with citation and production of reference-lists. They have now been included in the Aston archive. LaTeX style-option files, at Aston in [TEX-ARCHIVE.LATEX.CONTRIB]. thebib-plus.sty - This is for people who are using thebibliography or \bibliography as defined in the standard LaTeX styles, but who want control over the title and want an \addcontentsline issuing for a table-of-contents entry. apalike-plus.sty - This is for people who want something like apalike.sty (possibly in conjunction with apalike.bst) for an author-date citation scheme, but who want control over the title and want a table-of-contents entry. authordate1-4.sty - This is for people who are using one of the BibTeX author-date style files authordate1.bst, ... , authordate4.bst mentioned below. It redefines \cite and thebibliography, and defines a \shortcite command [such that if \cite gives (Smith, 1970), \shortcite gives (1970)]. This too gives control over the title and issues the \addcontentsline needed for a table-of-contents entry. BibTeX style files, at Aston in [TEX-ARCHIVE.BIBTEX.STYLES.CONTRIB]. The following are all for people who wish to use the author-date system. The styles are loosely based on the recommendations of British Standard 1629 (1976 edition), Butcher's "Copy-editing" (Cambridge University Press, 1981) and the Chicago Manual of Style (1982 edition). authordate1.bst - Author's names are typeset in roman. Uppercase letters in article, journal and book titles are left as given in the .bib file. authordate2.bst - As authordate1, but with downstyle titles, i.e, titles that are lower-case except for the first letter, any letter following a colon, and letters protected by { and }. authordate3.bst - As authordate1, but with author's names in small capitals. authordate4.bst - As authordate3, but with downstyle titles. To use any of these, you must have authordate1-4 as a style-option in your \documentstyle. Please note that the .bst files use the entry types and fields defined in Appendix B of the LaTeX manual (as subsequently modified by Oren Patashnik in his "BibTeXing" document). If I had the time to do the job properly, I would now be inclined to define entry types and fields that correspond more closely to the document categories etc. defined in "the standards" You may find these files useful until someone has the time to do the job properly. David Rhead Nottingham University ----------------------------------------------------------------------------- !! UK TeX ARCHIVE at ASTON UNIVERSITY: !! !! Files of interest !! [tex-archive]000aston.readme [tex-archive]000directory.list !! [tex-archive]000directory_dates.list [tex-archive]000directory.size !! [tex-archive]000last30days.files !! !! FTP access: site uk.ac.aston.tex !! username public !! password public !! !! !! I have a tape labelled TeX 2.993(==3.0) LaTeX 2.09 Metafont 1.9 (2.0) !! Unix 4.2/3BSD & System V. Tar 1600 bpi blocked 20 1 file dated !! 28 March 1990 (from washington.edu) !! !! I have the facility to copy this tape for anyone who sends the following !! 1 2400 tape with return labels AND RETURN postage. (2.50 pounds sterling !! for UK users, payable to `Aston University') Outside UK please ask me. !! UK users send 4.25 for two tapes or 6.60 for three tapes. !! Send to !! !! P Abbott !! Computing Service !! Aston University !! Aston Triangle !! Birmingham B4 7ET !! !! A VMS backup of the archive requires 2 (two ) 2400' tapes at 6250bpi. !! Remaining details as above. !! !! A VMS backup of TeX 2.991 plus PSprint is available; one tape is needed. !! !! Exabyte tape drive with Video 8 cassettes: !! Same formats available as 1/2in tapes. We use the following tapes !! SONY Video 8 cassette P5 90MP, MAXCELL Video 8 cassette P5-90 !! TDK Video 8 cassette P5-90MPB !! Postage 35p UK (stamp please), 1 pound sterling Europe, other areas 2 pounds !! !! OzTeX - Send 10 UNFORMATTED (800k) disks with return postage. !! !! ---Peter Abbott. End of UKTeX Digest *******************