UKTeX V88 #39 Friday 25 November 1988 CMR outline fonts? separate bibliographies for chapters comments on some items in issue #38, and other musings [STEPHEN: ps fonts] Comparing two WEB files to yield a CHANGE-file. A new PostScript driver chelgraph typesetter/cmr fonts VMS changes for MF TeX 2.94 for VMS Nottingham meeting: Carol's report Nottingham meeting: Sebastian's report SliTeX fonts Separate Chapter Bibliographies with BibTeX & LaTeX Editor Peter Abbott This issue was prepared for posting late Thursday afternoon so that items received Friday morning will be in next weeks issue. Latest TeXhax in the Archive is #102 Latest TeXmag in the Archive is V2N5 --------------------------------- Date: 18 Nov 88 12:31:10 gmt From: G.Toal @ uk.ac.edinburgh Subject: CMR outline fonts? To: info-tex@uk.ac.aston Message-ID: <18 Nov 88 12:31:10 gmt 050017@EMAS-A> At the Exeter conference, I remember hearing someone describe how they had converted metafont to produce outline fonts. Not having received a copy of the conference proceedings (nudge, nudge, Malcolm...) I'm not sure who it was. Does anyone know? I'm giving serious thought to fitting splines round a highly-magnified cmr pixel font so that I can save space by using scalable outline fonts in the Archimedes previewer I've finally started work on... Graham. --------------------------------- From: Clark Adrian Date: Sat, 19 Nov 88 16:56:14 GMT To: info-tex@uk.ac.aston.mail Subject: separate bibliographies for chapters Following on from Neil Kempson's macros in UKTeX #38, readers may be interested to know that the Springer-Verlag multiple-author style (svma.sty) is intended for collections of papers, so it allows for separate bibliographies in each chapter, too. Adrian F. Clark JANET: alien@uk.ac.essex.ese ARPA: alien%uk.ac.essex.ese@nss.cs.ucl.ac.uk BITNET: alien%uk.ac.essex.ese@ac.uk Smail: Dept. of Electronic Systems Engineering, Essex University, Wivenhoe Park, Colchester, Essex C04 3SQ, U. K. Phone: (+44) 206-872432 (direct) --------------------------------- Received: from seed.ams.com by NSS.Cs.Ucl.AC.UK via Satnet with SMTP id aa05332; 19 Nov 88 21:05 GMT Date: Sat 19 Nov 88 16:29:04-EST From: b beeton Subject: comments on some items in issue #38, and other musings To: info-tex cc: fps Message-ID: <12447880362.16.BNB@SEED.AMS.COM> re the discussion of texperts, malcolm, you're right about some purists insisting that the references you cite also appear in `tex, a system for technical text', ams, 1979, and even in `tau epsilon chi, a system for technical text', stanford artificial intelligence laboratory, memo aim-317, also computer science department report no. stan-cs-78-675, september 1978. i'd like to point out that, though very close, these aren't identical to the tex manual that appeared in `tex and metafont', as knuth made some significant upgrades between editions and these are documented in the later text. for example, on page 110, \firstmark appears in print only in `t&m'; it appears in my copy of the 1979 edition in red ink in knuth's handwriting. (so, i'm showing off.) i merely point this out as a way of saying that, in a question of vocabulary, the latest edition should be taken as current truth. both tex and metafont have undergone a lot of development since their first glimmerings in don knuth's mind, and we should all be grateful for the openness of that mind in adding features that have made tex even more powerful and useful than its first realization. by the way, anyone interested in reading knuth's gibbs lecture (and malcolm is right, it's still well worth reading) can also look in the bulletin (new series) of the american math society, march 1979, vol 1, no 2, pp 337-372; much easier to find, i suspect, than `t&m', which is long out of print and had a rather select (read limited) audience. while i'm on the line, i'd like to mention, in reference to the save-set listing of euler, symbol and cyrillic fonts from gareth hughes, that these fonts, originally from the american math society, will be re-issued shortly by the ams, some of them in new, improved versions. for example, don knuth's recent book, `concrete mathematics', made heavy use of euler, and in the process, he found and fixed some bugs and spacing problems. the symbol fonts are, at this very moment, being re-implemented in mf84; whether the new versions will be ready to include in the next release is not yet known, but when they are ready, it is my understanding that the .mf sources will be made available as well as the .tfm and raster files. no such luck yet with the cyrillic, though we are still seeking serious volunteers to undertake the re-implementation. stay tuned. another comment. in some issues of uktex, i've found that some submissions are `signed' only with a (to me) obscure e-mail address, e.g. `chaa006' (but i've figured out who you are, phil taylor). even though i may never be able to associate a face with a name, it would still be nice to be able to know who's responsible for a particular message. so please sign your name. and it occurs to me that it's worth mentioning that texhax is back on the air, now from the university of washington, under the care of pierre mackay and tiina modisett (yes, that's right -- two i's). i'd like to take this opportunity publicly to thank malcolm brown, who managed it patiently and well since 1986. and, while i'm at it, peter abbott, who manages not only uktex so well, but also a repository of tex goodies that is far superior to any now in existence in the states. (just thought you folks in the u.k. should know how fortunate you are.) finally, tugboat 9#3, which should be out by christmas, will carry an announcement of the 10th anniversary meeting of tug, at stanford, and a call for papers. anyone who can make it to the u.s. next august should consider attending; we'd love to see you there. -- barbara beeton - ------- --------------------------------- Received: Date: Sun, 20 Nov 88 16:03:12 GMT From: Sebastian Rahtz To: info-tex@uk.ac.aston.mail Subject: [STEPHEN: ps fonts] can anyone help with these two questions? my answers were a) buy new Mac versions rather than fiddle about, and b) I've never heard of multcol etc. Don't reply to me, but to address at end sebastian - ----- Forwarded message # 1: a) Is it possible to take Adobe PostScript fonts for use on an I.B.M. pc, and make it so that we can use them on the Mac; for example with WriteNow? b) Also, I am supposed to be looking into finding a decent two column macro so that we can get a typeset version of the pre 1920 Bodleian Library catalogue going. The best ones I have seen are the multcol.out and twocol.out written by Barbara Beeton and distributed on ZAR. However, multcol.out will only print one column per page; and twocol.out keeps generating overfill boxes no matter what I put in! I wondered if you know a way of getting multcol.out to put out more than one column per page; or if you know what I am doing wrong with twocol.out? I - ------ End of forwarded messages Please reply to: Paul Watry c/o stephen@ox.vax --------------------------------- Date: 21-NOV-1988 13:22:34 GMT From: CHAA006@UK.AC.RHBNC.VAXB To: Info-TeX@UK.AC.ASTON Subject: Comparing two WEB files to yield a CHANGE-file. Sender: JANET"CHAA006@UK.AC.RHBNC.VAXB" Message-Id: <21C022C5_001A1F04.0091C31968E238E0$22_3@UK.AC.RHBNC.VAXB> Originally-to: $UK-TEX Originally-from:CHAA006 "Philip Taylor (RHBNC) " Mailer: Janet_Mailshr V3.2 (27-Oct-1988) In the most recent UK-TeX, Sebastian Rahtz writes: >>> [... graphics needs can be met in three ways >>> i. ..., ii. ..., >>> iii. write yourself a set of macros which do what you want >>> (maybe LaTeX picture would do), but implement them as PostScript >>> (or other) \specials, so as to remove the need for either PiCTeX >>> dottery or silly LaTeX picture fonts >>> I have recently come to the conclusion that (iii) is the only way forward, >>> implementing a decent graphics language in TeX (maybe modelled on 'pic'), >>> but relying on PostScript to do the work. One could use 'tpic' and the >>> \specials associated with it, but thats rather clumsy.] May I recommend to Sebastian (and others interested), the DVILASER/PS User Manuals from ArborText Inc., in which the latter write: >>> As an alternative approach, ArborText distributes separately an upward >>> compatible set of extensions to LaTeX where the picture environment >>> implementation has been changed to draw figures using PostScript via >>> DVILASER's \special commands described [in this chapter]. Since PostScript >>> can easily handle arbitrarily shaped figures composed of slanted lines and >>> circles, as well as vastly more complicated figures, there is much more >>> flexibility. Sebastian then goes on to say: >>> b) Phil 'I love VMS' Taylor wants a difference applier. If he were using >>> Unix, he would find that the widely-used `patch' program can read a Unix-style >>> `diff' listing and apply or unapply it to his source, doing what he wants >>> with his Web sources. Doubtless one could rewrite patch under VMS to read >>> VAX `compare' output. But there, either Sebastian (I love Unix) has failed to read what was actually written, or (but far less likely) is demonstrating a sad lack of familiarity with WEB: what was actually requested was not simply a means of generating an arbitrary editor script which would convert from one version of a file to another, given a listing of their differences, but was very specifically a means of generating a CHANGE-file (qua CHANGE-file) which could be used strictly within the constraits of the letter and spirit of WEB programming. But my thanks to Sebastian (and indeed, to the others who responded to my request: regrettably no-one seems to have such a utility, but Mark Damerell is over half-way there, with an EDT script which if applied to a VMS DIFFERENCES listing will yield a CHANGE-file which works if the differences are not too great.) ** Phil (I hate Eunuchs and Wimps) --------------------------------- Date: Fri, 4 Nov 88 12:39:20 GMT From: jclark!jjc@uunet.UU.NET (James Clark) Subject: A new PostScript driver Over the last year or so I've written a new PostScript driver, somewhat unimaginatively called dvitops, which I have placed in the public domain. There are quite a few PostScript drivers already available but most of them have been adapted from drivers for other printers and thus fail to take advantage of the unique features of PostScript. Dvitops has been developed from scratch especially for PostScript. The most important feature of dvitops is that when used with PostScript fonts it produces completely device-independent output. A fairly common misconception about PostScript is that any PostScript program is automatically device-independent. This is no more the case for PostScript than it is for, say, C. One has to work really quite hard if one is completely to avoid device-dependencies: one has to avoid making any assumptions about resolution, fonts, memory or operators that are not part of the language definition. The trickiest area is rounding: most drivers do this themselves; true device-independence requires this to be done in PostScript. Producing rules with the correct dimensions turns out to be quite complicated. Those of you with PostScript printers may have noticed that ruled tables or characters containing rules (such as \overbrace, \underbrace and \sqrt) sometimes don't look quite right. It turns out that when PostScript fills a path, it paints a pixel just in case some part of the pixel lies within the path. Thus a rectangle 1/2 a pixel wide can end up 2 pixels wide on the paper. The solution is to position the corners of rules in the middle of pixels and to subtract one pixel from the height and width of rules. It is possible to do this device-independently in PostScript. Dvitops supports either ordinary PostScript fonts or Metafont generated fonts in pk format; gf and pxl formats are not supported. One problem with PostScript printers is that comparatively little memory is available for downloading fonts. A fundamental design goal of dvitops was to support documents with arbitrarily complex font requirements even on first generation PostScript printers having pathetically little memory. This has been achieved without sacrificing page independence (pages should depend only on the prolog and not on each other), so that it is possible to reorder the document or to print only a subset of it, after it has been composed. Like a number of other drivers dvitops uses a two-pass approach, gathering information about font-usage on the first pass. The output for each page is sorted by font. The output in each font is bracketed by a save/restore pair. Thus dvitops requires only enough memory to hold one font. It can also take advantage of as much memory as you have: it downloads as many fonts as possible in the prolog of the document so that they do not need to be downloaded on each page that they are used. Of course, with pk fonts it only downloads the definitions for those characters that are actually used. Dvitops also allows one to use arbitrarily many downloadable PostScript fonts. It does this by putting an %%IncludeFont comment between at each place that the font is to be included. There is at most one such comment for each font per page (it knows that Optima at 12pt and Optima at 10pt, say, are the same font). For this to work you will need a spooler which understands version 2.0 of the Adobe Document Structuring Conventions, and which can handle font downloading. I have written a filter to do this which can be stuck on the front of a spooler or run separately. If you want to use many downloadable fonts, you will need a lot of patience. A typical Adobe font is over 100k when unpacked. If you have say 100 pages and four fonts that have to be downloaded separately on each page, and you talk to your printer a 9600 baud, it will take you over 9 hours! Dvitops has a few specials including one to import PostScript graphics and an `inline' special to include PostScript code. There is also an interesting set of specials that allows you to apply arbitrary linear transformations to regions of the dvi file in a convenient fashion. Regions of the dvi file are delimited by \special{dvitops: begin region_name} and \special{dvitops: end} commands. You then specify an origin for the transformations to be applied to a region using \special{dvitops: origin region_name}, which sets the origin at the current point. You then apply one or more transformations using \special{dvitops: rotate region_name rotation_amount}, or \special{dvitops: transform region_name a b c d tx ty}, which applies the tranformation represented by the matrix |a b 0| |c d 0| |tx ty 1| to the region. These transformations work correctly with graphics produced by the inline special, as well as with imported graphics. Dvitops works on MS-DOS and Unix machines. It should be easily portable to any machine with a decent C compiler and a reasonable architecture (ASCII and 8-bit bytes are required). It was originally developed on a MS-DOS machine, and some care was to taken to achieve maximum efficiency on a 16-bit architecture, by avoiding the use of 32-bit operations wherever possible. It consequently runs up to 3 times faster than some other PostScript drivers on MS-DOS machines (the relative speed depends on whether you are using floppy, hard or RAM disk; it is relatively much faster on RAM disk). There is much less difference on 32-bit machines. Dvitops is unfortunately too big to fit into one mail message. If anybody in the UK wants to get hold of it they can contact me directly. I will also mail a copy or two per country to anybody who volunteers to make it available for anonymous FTP, or put it on a info-server or archive-server, or otherwise redistribute it. If anybody should volunteer, I'll send details to TeXhax. James Clark +++Editor - The above appeared in TeXhax V88 #100. The software will be made available in the archive as soon as possible. +++ --------------------------------- Date: Tue, 22 Nov 88 17:25:21 BST To: INFO-TEX@UK.AC.ASTON.MAIL From: BOOTH.CM@UK.AC.EXETER Subject: chelgraph typesetter/cmr fonts Message-ID: The only rumour I've heard concerning the Chelgraph typesetter and cmr fonts was one I brought back from Montreal - Lance Carnes/Personal TeX Inc have written a driver for PCTeX to access their Chelgraph IBX 2000, using all TeX fonts etc. They're offering this as a bureau service. I'll also be interested in any other more local rumours... Cathy Booth Exeter University Computer Unit booth.cm@uk.ac.exeter --------------------------------- From: Clark Adrian Date: Wed, 23 Nov 88 09:38:52 GMT To: info-tex@uk.ac.aston.mail Subject: VMS changes for MF Does anyone have a fairly up-to-date change file for Metafont under VMS? I'm looking for something public-domain, not the K-and-S flavour. I'd like to have a starting point from which I could write code to drive a graphics terminal (or has someone done that, too?). Adrian F. Clark JANET: alien@uk.ac.essex.ese ARPA: alien%uk.ac.essex.ese@nss.cs.ucl.ac.uk BITNET: alien%uk.ac.essex.ese@ac.uk Smail: Dept. of Electronic Systems Engineering, Essex University, Wivenhoe Park, Colchester, Essex C04 3SQ, U. K. Phone: (+44) 206-872432 (direct) --------------------------------- From: Clark Adrian Date: Wed, 23 Nov 88 09:35:25 GMT To: info-tex@uk.ac.aston.mail Subject: TeX 2.94 for VMS Ho hum. Every time I upgrade my VMS TeX change file for the latest version of TeX, it immediately becomes out-of-date. So, hot on the heels of the announcement of TeX 2.94, I've updated my VMS change file. Older versions of these changes were guilty of the |last_text_char| problem mentioned by Chris Thompson in a recent TeXhax; this has now been eradicated. Interested parties should contact the author for a copy of the changes and the corresponding PLAIN.TEX (which has also changed; confusing, isn't it?). Adrian F. Clark JANET: alien@uk.ac.essex.ese ARPA: alien%uk.ac.essex.ese@nss.cs.ucl.ac.uk BITNET: alien%uk.ac.essex.ese@ac.uk Smail: Dept. of Electronic Systems Engineering, Essex University, Wivenhoe Park, Colchester, Essex C04 3SQ, U. K. Phone: (+44) 206-872432 (direct) --------------------------------- Date: 23-NOV-1988 15:15:03 GMT From: CCZDAO@UK.AC.NOTT.VAX To: abbottp@UK.AC.ASTON Subject: Nottingham meeting: Carol's report Message-Id: <20600268_000C7B64.0091C4BB742734A0$14_3@UK.AC.NOTT.VAX> Originally-to: JANET"abbottp@aston" Originally-from:CCZDAO "David Osborne" Sender: JANET"CCZDAO@UK.AC.NOTT.VAX" X-Organization: Systems Group, Cripps Computing Centre, University of Nottingham X-Postal: University Park, Nottingham NG7 2RD, England X-Phone: (0602) 484848 ext 2064 %Carol Hewlett's report on UK TUG, held at Nottingham University on % 4 November 1988. % % %Note the wide measure - this was `designed' for A4 paper % \hsize 6.01 true in\vsize 9 true in % \tolerance=500 % \font\headfont=amr10 scaled\magstep1 \font\bigbold=ambx10 scaled\magstep1 % % since I don't have the right fount for `METAFONT', this is the best % I can do... \def\MF{{\tt META}\-{\tt FONT}} % % And here are defs for the other \TeX words, so that these can be easily % replaced with the correct definitions! \def\LaTeX{La\TeX} \def\BibTeX{Bib\TeX} \def\SliTeX{Sli\TeX} \def\WEB{{\tt WEB}} \def\Tangle{Tangle} \def\Weave{Weave} % \parindent .2in % \def\\{\thinspace} \def\q{\kern10pt} % {\headfont \centerline{UK TUG} \medskip \centerline{UK \TeX\ Users' Group} } \medskip \centerline{{\bigbold Inaugural Meeting}} \vskip.5in \noindent The Inaugural Meeting of the UK \TeX\ Users' Group was held at the University of Nottingham, on 4 November 1988. \vskip.5in \centerline{S\\U\\M\\M\\A\\R\\Y\q O\\F\q P\\A\\P\\E\\R\\S} \bigskip \line{\bf \MF---An Overview\hfil Charles Curran, Oxford University} \medskip\noindent Charles Curran started out by asking What is \MF? He then proceeded to give some reasons why it might be used. \smallskip \item{(1)} Users my want to design `odd characters', but not usually a whole fount. \item{(2)} When printing \TeX, there were problems with different device drivers and these could be cured via \MF\ by altering the device parameters for various page-printers, particularly with reference to the write-white versus write-black enigma. \item{(3)} Sometimes defective characters needed redesigning. \smallskip In response to (1), he said that existing characters can often be adapted; he suggested people speak to Dominik Wujastyk if they needed to get founts for alphabets other than european. He then showed diagrammatically the relationship between \MF\ and \TeX\ and the various ouput files, some of which should be tuned to the desired output device. Various implementations of \MF\ exist, running on VMS, SUN and Macintosh. Some have preview capability. In response to (2), Charles said that \MF\ can be used to generate Computer Modern fonts at various resolutions\\/\\magnifications; to generate device-specific fonts by modifying e.g., waits.mf, local.mf; and to generate odd characters. It was possible that there was a need for a UK \MF\ group, although the r\^ole of answering \MF\ problems was currently dealt with by newsletters and bulletin boards. Charles then made a number of general points about the matching of founts to page-printers. It was not generally known which print engine was used in which page-printer (and it could be very difficult to find out). Further, the average user (or implementer) didn't always know how a fount {\it should} look and whether what was being produced was the best possible. This suggested another area for the exchange of information: information on page-printers and their print engines and examples of the best possible printing that could be achieved with any given machine. Another field for discussion/education was that of type design in general. In the discussion that followed Charles' paper, it was suggested that a sample book be put together. The relationship (if that's the right word) between \MF\ and PostScript was mentioned: will PostScript take over all that \MF\ now does? Finally it was pointed out that while \MF\ can be used to design {\it families}, programs like Fontographer were good for single characters but needed a lot of work to retain any consistency when designing more than a few characters. \vskip.5in \line{\bf Installing \TeX---the scenic route\hfil David Osborne, Nottingham University} \bigskip\noindent David Osborne's paper had a subtitle---the long road to implementing \TeX. At Nottingham, several years had been spent in trying to provide a \TeX\ user service. David explained that they had originally obtained a \WEB\ source for their VAX machines. \WEB\ contains both the program source and its documentation. The code is run through a program called \Tangle, which gives Pascal program output and documentation separately; the documentation file then goes through \Weave\ to produce the real documentation and the Pascal compiler is used to produce the \TeX\ executable program. \Tangle\ needs to read a system-specific change file as well as \WEB. There was lots of documentation, but very little help as to where to start reading it. However, most of these problems were solved reasonably quickly. The real difficulty came when trying to fix the printer for \TeX. That particular problem had still not been solved, although they were now considering an AGFA PostScript page-printer, which promised a reasonable printing speed and for which a \TeX-PostScript driver could be used. He summed up by giving three points which new implementers of \TeX\ should follow: \smallskip \item{--} Choose the output device {\it first\/}. \item{--} Allow plenty of time for the implementers to become familiar with the package and documentation. \item{--} Allow plenty of time for the implementation \smallskip David further suggested that better documentation directed at implementers was needed; and that there were implications for training both users and those who would advise them. \vskip.5in \line{\bf An Introduction to \LaTeX\hfil Sue Brooks, Bradford University Software Services Limited} \bigskip\noindent Sue Brooks gave a very persuasive talk about the benefits of using \LaTeX. She set out a number of questions that were asked and told us her answers. First, what was \LaTeX? It was a macro package that was somewhat similar to Scribe (which was itself like Troff). The assumption was made that a document had a structure; additionally, \LaTeX\ was able to handle book-like items like table of contents. Second, why use \LaTeX? Because it uses a document model rather than a page description, as Plain \TeX\ did. It also included certain other sets of macros, namely \BibTeX\ and \SliTeX. Sue compared \LaTeX\ to DTP packages where she felt that \LaTeX won hands down. Third, why did Sue use \LaTeX? Partly this was historical---she had learned \LaTeX\ while at the Open University. She still felt that it was the best way for her to do her current publishing work. It provided a user service, without the need for the user to write macros. Fourth, who would benefit from using it? Authors (especially when collaborating), authors' minions and documentation producers. Fifth, what was wrong with \LaTeX? For a start, it was too structured; the style files were not fully understood (except by Leslie Lamport?) and there was no good {\it reference} manual (although the `User's Manual' was fine). But there was no alternative, either! Next, Sue said that \LaTeX\ was certainly not going to disappear, but there were a number of things that would improve it, especially for the UK. In particular, the distribution needed sorting out; more information should be available on the implementation details and style files. There should be a DOC to STY converter and English hyphenation. Finally, to ease the user's burden, Sue suggested: good editing interfaces, \LaTeX-intelligent spelling checkers, indexing tools, \BibTeX, \SliTeX\ and its fonts, and style files. \vskip.5in \line{\bf TUG, Montr\'eal 1988 Conference\hfil Cathy~Booth, Exeter University} \bigskip\noindent The principal theme of the 1988 conference had been \TeX\ in production. A further subject had been standards for \TeX\ courses. (I did not make notes on Cathy's report as it will no doubt appear in full elsewhere.) \vskip.5in \line{\bf \TeX\ in Germany: report from Freiburg Meeting\hfil Chris~Rowley, Open University} \bigskip\noindent Chris opened his report by saying that there was a lot of \TeX\ going on in W. Germany. \TeX\ does acknowledge that there are countries other than the US, so is welcomed by Germans. It seems to be widely used at the high-end by commercial users. Among other things, there is work on fount design. The meeting had held a `problem session', in which there was a discussion of extensions to \TeX. A program of development for \TeX\ and \LaTeX\ was proposed, for which 24 extensions were suggested. \vskip.5in\noindent Sebastian~Rahtz (Southampton University) was due to present a paper on Picture Languages, but as the proceedings were running late, it was omitted. Peter Abbott (Aston University) asked for \TeX\ contributions for an issue of {\it University Computing}. He also asked for volunteers to help with the task of checking over the Aston Archive to try to keep duplicated material to a minimum and to make sure that what was there was up-to-date. \vskip.5in \line{\bf A UK TUG? \hfil Malcolm Clark, Imperial College} \bigskip\noindent Malcolm started by giving the meeting a pep talk, which he said was his review of the world through \TeX-coloured glass. He outlined the activities of TUG, which included a newsletter, courses, annual conference, hotline support (and email), products and a speakers bureau. He reminded the meeting of the three electronic \TeX\ things---\TeX HAX, UK\TeX\ and the Aston Archive. Malcolm noted the other European countries with \TeX\ groups of various sorts, including \TeX interessen (W. Germany and Austria), Gutenberg (Paris based), Groningen in the Netherlands, a Nordic grouping, a \TeX-produced journal in Spain and also activity in Poland, Israel and Eire. He listed the European \TeX\ meetings, in Italy in 1985, Strasbourg, 1986, Exeter, 1988 and to come Karlruhe/Freiburg or Stockholm in 1989 and Cork in 1990. The last topic of his review was of other groups with an interest in electronic typesetting---the Electronic Publishing Specialist Group of the British Computer Society, the British Computer Society's Displays Group and the SGML users' group. It had been revealed to the meeting that Malcolm had been asked to be the European co-ordinator for TUG. His next points were on the subject of what we wanted from TUG and what we could do. On the second point, be believed that the big thing was to try to solve the ignorance factor. First, we could produce a brief flyer to define \TeX; answer such questions as where can .DVI files be typeset; perhaps document and provide an index to the other \LaTeX\ style files and exchange information on implementing \TeX. Second, someone could make a map showing the interrelation between \WEB, \Weave, \Tangle, \TeX, Pascal, C, GF, PK, PXL, etc. Third, pronounciation could be standardised. Fourth, \TeX\ could be taught English hyphenation. (It was agreed that Charles~Curran and Chris~Martin would investigate this area.) Fifth, perhaps even more use could be made of bulletin boards, electronic mail and the Aston Archive. Sixth, workshops could be arranged on certain subjects, such as \MF\ type design, macros, style files, graphics, etc. The rest of Malcolm's talk, group discussion and so forth was not so structured. Although no conclusion was reached, there was much talk about the relationship between any UK \TeX\ group and TUG. It was suggested that we could be a TUG subgroup, such that a subscription to the UK Group would also form a subscription to TUG itself. Then UK subscribers could get `local' services and TUGboat. Alternately, could the UK group merely collect subscriptions in sterling on behalf of TUG, to save us from buying \$ drafts or using credit cards? How did Europe as a whole fit in? The only conclusion reached was that there should be a group of some sort concerned with \TeX\ that holds regular meetings. It was agreed that there would be another meeeting to be held in London, probably in March, after Malcolm got back from the US where he would have found out more about what being European co-ordinator entailed. Another subject that was raised from time to time was the fact that the Nottingham conference had been arranged at short notice (about 3 weeks) and was successful because those attending had been sent electronic mail over JANET. This gave University staff an advantage over commercial users. It was established that commercial companies could have a legitimate JANET address if they wished to communicate with the academic community. They were not supposed to use JANET to communicate with other commercial users. For the purposes of receiving UK\TeX, etc., provided mail boxes could be established, there was no reason why commercial users should not be able to have a JANET address. It was suggested that universtity recipients of UK\TeX\ send one (printed) copy to a non-email user. \vskip.5in %\centerline{S\\U\\M\\M\\A\\R\\Y} %\bigskip \noindent The meeting ended with a very warm vote of thanks to David Osborne for arranging the meeting. \vskip1in \rightline{\vtop{\hbox{Carol Hewlett}\hbox{22 November 1988}}} \bye --------------------------------- Date: 23-NOV-1988 15:14:15 GMT From: CCZDAO@UK.AC.NOTT.VAX To: abbottp@UK.AC.ASTON Subject: Nottingham meeting: Sebastian's report Message-Id: <20600268_000C7B64.0091C4BB57BBD0A0$14_2@UK.AC.NOTT.VAX> Originally-to: JANET"abbottp@aston" Originally-from:CCZDAO "David Osborne" Sender: JANET"CCZDAO@UK.AC.NOTT.VAX" X-Organization: Systems Group, Cripps Computing Centre, University of Nottingham X-Postal: University Park, Nottingham NG7 2RD, England X-Phone: (0602) 484848 ext 2064 mine is pretty light-hearted, but it follows: use as much or as little as you like.... thanks for the day, it was fun! \documentstyle{csart} \begin{document} \title{A UK \TeX\ Users Group? Report of a meeting held in Nottingham on November 4th 1988} \author{Sebastian Rahtz} \date{November 7th 1988} \maketitle On Friday November 4th I had the pleasure of attending a meeting organised in Nottingham for the purpose of discussing a possible UK \TeX\ Users Group. The impetus for this came from the very successful \TeX eter 88 conference, one of an informal series of get-togethers for European \TeX xies, coupled with the remarkable rise to power of the UK's own \TeX\ Archive at Aston under the benign leadership of Peter Abbott. David Osborne put together a colloquium at short notice in the congenial surroundings (nice lunch, David) of the Cripps Computing Centre of the Cripps Computing Centre, and about 40 people were able to come. The problem with the short notice was that David perforce used electronic mail to advertise the event, leading to a high proportion of committed gurus present, not many dumb users and more or less nobody from outside academia. The day started officially at 11am. For some of us, this meant rising at 5am, tripping over the cat and stumbling onto a train at 6am. Thank god for British Rail egg and cress sandwiches. Anyway, at 11 or thereabouts, Charles Curran from Oxford ambled onto the stage and started talking about Metafont. He claimed to have had his brief changed 2 minutes before, but managed somehow to suggest that since CMR and MF won't go away in the near future, and since the whole situation of different printers and drivers is a mess, it would not do any harm at all to have a UK group advising neophytes on which files to sacrifice black cocks in front of (this apparently being the correct way to get a good value for `blacker' in your local.mf file). Anyone in the audience who still thought \TeX\ was something you bought off the shelf at Safeway were then disillusioned by David Osborne's outline of \TeX\ installation at Nottingham. While his problems revolved mainly around printers, it was clear that the apparent `free' nature of \TeX\ is more than paid for by the arcane nature of the installation from a raw tape. Again, it was clear that new people would benefit from experience from a local group. A breath of fresh air came from Sue Brooks (late of the OU, now in commercial software documentation) with her unashamed plug for writers (as opposed to \TeX xies) to use Lamport's \LaTeX\ macros; she gave a clear outline of the advantages and even some solutions to the answers to problems. She was followed after aforesaid fine lunch by Cathy Booth (Exeter) who told us about the \TeX\ Users Group meeting in Montreal; the interest here was in its concentration on \TeX\ in real world production environments, which confirmed the impression given in Seattle that \TeX\ has gone beyond implementation details (a lesson the UK group could take on board?). Cathy also passed on some gob-smacking gossip from commercial vendors about their new products (nuff said). She was followed by the most valuable talk (to me), a report by Chris Rowley (OU) on the most recent German \TeX\ Users Group meeting, in which he gave an impression of what went on in German \TeX ery. Their work on customizing \TeX\ for German, writing new books and listing the definite things a NEW\TeX\ should do, shows up how lax we have been in England in simply accepting what the Americans give us---as was pointed out, we still lack English hyphenation patterns. The Germans (and other European groups) seemed to be putting more effort than the British into getting \LaTeX\ right, and this seemed to be an area where progress could actually be expected. I was scheduled to give a talk on picture languages in the afternoon, but in the interests of discussion I agreed to be left out; Malcolm Clark, the charismatic Imperial College Leaderene of \TeX\ eter 88, and editor of the prestigious \TeX line newsletter, then took the stage and harangued the populace on the State of the World according to \TeX, outlining what sources of information we had now in Europe and the UK, what the \TeX\ Users Group does, and what we needed in the UK. It turned out that Malcolm had been unilaterally appointed European Coordinator for TUG (one hopes the Germans don't mind), so he was able to promise a firm presentation of our desires to TUG. He outlined issues that needed to be addressed, such as general ignorance in the world at large about what \TeX\ was and how to get it, hyphenation problems, teaching \TeX\ etc. Finally, we got around to the question of whether a formal British group was needed, as opposed to simply sticking with the main TUG or forming a pan-European group. Dissatisfaction over what we got from TUG for the money prompted suggestions of an autonomous group, while others wanted an affiliated chapter---the consensus seemed to me that we would like to join a UK version of TUG which charged us a subscription, but sent most of it off to America and joined TUG on our behalf, saving us bank charges etc, and (hopefully) letting TUG ease administration and postage costs. Three problems prevented a formal constitution being set up on the spot: a) we did not know how TUG would react---Malcolm would find this out in January; b) nobody had tabled any suggestions, and it was getting dark; c) we were not at all representative of UK \TeX\ users (ie we were mostly academic \TeX\ bores). It was therefore decided to hold another meeting in London in February, with wider invitations, when we would formally set up a group (or not, as the meeting went!). \TeX\ is hampered by its free image, to the same extent as it is aided by its free image. Without commercial support, it can only exist if a committed user group continues to keep its distribution and use at a high standard. Ten years after the foundation of TUG, are cracks showing? Will \TeX\ survive in the `real world'? Chaotic and inefficient as it was (I did not see why a full meeting of users could not have taken place later on without this initial peculiar subset), the meeting in Nottingham was another valuable contribution to The Cause of keeping the \TeX\ flame alight. Let us hope a UK group is successfully formed. \end{document} --------------------------------- From: Clark Adrian Date: Thu, 24 Nov 88 11:03:41 GMT To: info-tex@uk.ac.aston.mail Subject: SliTeX fonts I'm sure this has been asked several times before: does anyone have a set of .mf files for the 8-point fonts used by SliTeX? Better still, has anyone built .gf files suitable for an Apple LaserWriter? Adrian F. Clark JANET: alien@uk.ac.essex.ese ARPA: alien%uk.ac.essex.ese@nss.cs.ucl.ac.uk BITNET: alien%uk.ac.essex.ese@ac.uk Smail: Dept. of Electronic Systems Engineering, Essex University, Wivenhoe Park, Colchester, Essex C04 3SQ, U. K. Phone: (+44) 206-872432 (direct) --------------------------------- Date: 24-NOV-1988 11:51:02 GMT From: RM028A@UK.AC.CRANFIELD.CDVA To: info-tex@UK.AC.ASTON Subject: Separate Chapter Bibliographies with BibTeX & LaTeX In UKTeX v88 #37, I offered the LaTeX style file `chapterbib.sty'which would allow the creation of separate bibliographies for each chapter in a LaTeX document. That style file will not produce the correct citation numbers in the document (though the numbers in bibliographies are OK) if any of the BibTeX bibliography database entries which are cited in more than one of the bibliography! In fact, the citation number printed is the one used in the LAST bibliography. My application rather unusually didn't have any common references, so I didn't see the problem. Thanks are due to Harvey Richardson for pointing this out. If you have that style file, please throw it away and accept my apologies. All is not lost, however, because now there's ``new improved'' chapterbib.sty! This will allow multiple bibliographies with the correct citation numbers and no interference between bibliographies. There are of course some restrictions: 1. The \bibliography and \bibliographystyle commands may not be used in the root file, only in files that have been \include'd. If you try to use them, a LaTeX warning is issued and the offending command(s) ignored. This restriction occurs because the root .aux file includes the subsidiary .aux files and when BibTeX processes the root .aux file, it complains about multiple \bibdata commands. 2. If you want to \cite in the root file, you must provide your own bibliography within the root file using the thebibliography environment. I don't suppose that this will appeal to BibTeX users! 3. The subsidiary files must be \include'd (not \input'ed) by the root file, with only one bibliography per \include'd file. 4. The style file works by redefining the \bibcite, so if you've got any other style files that use \bibcite, watch out! The only style files (that I've seen) with \bibcite in them are deproc.sty, ctswan.sty & ipr.sty. Apart from these restrictions (which are easily overcome), I've tested chapterbib.sty on several documents with in-chapter bibliographies and common references and all appears to be OK. No doubt other people will find some (more) errors that I didn't anticipate, but I'd be happy to try to fix them. C. Niel KEMPSON ------------------------------------------------------------------------------ Slow (but reliable) Mail: | Telephone: Swindon (0793) 785687 School of Elec Eng & Science, | International: +44-793-785687 Royal Military College of Science, | Shrivenham, SWINDON, | E-mail: SN6 8LA, | JANET: rmcs-tex@uk.ac.cranfield.cdvc United Kingdom | ------------------------------------------------------------------------------ CHAPTERBIB.STY follows: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> CUT HERE <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< %========================================================================== % chapterbib.sty Version 1.0 (23-NOV-1988) % ~~~~~~~~~~~~~~ % Allow multiple bibliographies in a LaTeX document, including items % \cite'd in more than one bibliography. % % Restrictions % ~~~~~~~~~~~~ % % 1. The \bibliography and \bibliographystyle commands may not be used % in the root file, only in files that have been \include'd. If you % try to use them, a LaTeX warning is issued and the offending % command(s) ignored. This restriction occurs because the root .aux % file includes the subsidiary .aux files and when BibTeX processes % the root .aux file, it complains about multiple \bibdata commands. % % 2. If you want to \cite in the root file, you must provide your own % bibliography within the root file using the thebibliography % environment. I don't suppose that this will appeal to BibTeX users! % % 3. The subsidiary files must be \include'd (not \input'ed) by the root % file, with only one bibliography per \include'd file. % % 4. The style file works by redefining the \bibcite, so if you've got % any other style files that use \bibcite, watch out! The only style % files (that I've seen) with \bibcite in them are deproc.sty, % ctswan.sty & ipr.sty. % % Author % ~~~~~~ % Niel Kempson | Telephone: Swindon (0793) 785687 % School of Elec Eng & Science, | International: +44-793-785687 % Royal Military College of Science, | % Shrivenham, SWINDON, | E-mail: % SN6 8LA, | JANET: rmcs-tex@uk.ac.cranfield.cdvc % United Kingdom | %========================================================================== \let\@debugoutput=\@gobble % %************************************************************************* % DEBUGGING MACROS. To see what global variables are being assigned and % tested, uncomment these lines. % % % \let\@debugoutput=\typeout % \def\@debugnamedef#1#2{\expandafter\def\csname #1\endcsname{#2}% % \@debugoutput{\string\@debugnamedef: defined `#1' \space as `#2'}} % \def\@debugtestdef #1#2#3{% % \@debugoutput{\string\@debugtestdef: testing whether `#1@#2' = `#3'} % \def\@tempa{#3}\expandafter \ifx \csname #1@#2\endcsname% % \@tempa \else \@tempswatrue \fi} % \def\@debugbibtestdef #1#2#3#4{% % \@debugoutput{\string\@debugbibtestdef: testing whether `#1@#2@#4' % % = `#3'} % \def\@tempa{#3}\expandafter \ifx \csname #1@#2@#4\endcsname% % \@tempa \else \@tempswatrue \fi} % \let\@testdef=\@debugtestdef % \let\@bibtestdef=\xbibtestdef % \let\@namedef=\@debugnamedef % %************************************************************************* % %------------------------------------------------------------------------- % Keep track of files currently opened. % 1. The counter @ipfilectr keeps track of the currently open I/P file, % and @includefilectr keeps track of the \include files. % 2. @ipfilectr is set to @includefilectr, except when processing the root % file. An arbitrary large (number greater than the maximum number of % include files) is used to denote the root file. %------------------------------------------------------------------------- \newcounter{@ipfilectr} % current I/P file, \def\the@ipfilectr{\roman{@ipfilectr}} % displayed as roman numerals \newcounter{@includefilectr} % current \include file \def\@rootfilevalue{1988} % arbitrary value for root file \def\savedjobname{\jobname} % save root file name as a macro % %----------------------------------------------------------------------- % The name of the current I/P file is stored in macro \@currentipfile % and the global macro ipfile@the@ipfilectr is set to this name whenever % \@currentipfile changes. %----------------------------------------------------------------------- \def\@currentipfile{\jobname} % initialize to root file \setcounter{@ipfilectr}{\@rootfilevalue} % ditto \global\@namedef{ipfile@\the@ipfilectr}{\@currentipfile} % %----------------------------------------------------------------------- % Redefine the \include macro (taken from LATEX.TEX of 25-JAN-1988) so % that when a file is \include'd % 1. \@currentipfile is updated and \includefilectr incremented % 2. ipfilectr set to includefilectr % 3. global macro ipfile@\the@ipfilectr set to \@currentfile % % When the \include'd file is finished with % 1. reset \@currentipfile to the root file name (\jobname) % 2. reset ipfilectr to \@rootfilevalue % 3. global macro ipfile@\the@ipfilectr set to \@currentfile %----------------------------------------------------------------------- \def\include#1{\clearpage \def\@currentipfile{#1} \@debugoutput{\string\@currentipfile = `\@currentipfile'} \addtocounter{@includefilectr}{1} \setcounter{@ipfilectr}{\value{@includefilectr}} \global\@namedef{ipfile@\the@ipfilectr}{\@currentipfile} % \if@filesw \immediate\write\@mainaux{\string\@input{#1.aux}}\fi \@tempswatrue\if@partsw \@tempswafalse\def\@tempb{#1}\@for \@tempa:=\@partlist\do{\ifx\@tempa\@tempb\@tempswatrue\fi}\fi \if@tempswa \if@filesw \let\@auxout=\@partaux \immediate\openout\@partaux #1.aux \immediate\write\@partaux{\relax}\fi\@input{#1.tex}\clearpage \@writeckpt{#1}\if@filesw\immediate\closeout\@partaux \fi \let\@auxout=\@mainaux\else\@nameuse{cp@#1}\fi % \def\@currentipfile{\jobname} \@debugoutput{\string\@currentipfile = `\@currentipfile'} \setcounter{@ipfilectr}{\@rootfilevalue} \global\@namedef{ipfile@\the@ipfilectr}{\@currentipfile}} % %------------------------------------------------------------------------- % **************************************** % * BIBLIOGRAPHY * % **************************************** % % A bibliography is created by the bibliography environment, which % generates a title such as ``References'', and a list of entries. The % BIBTeX program will create a file containing such an environment, which % will be read in by the \bibliography command. With BIBTeX, the % following commands will be used. % % CONVENTION % % \b@FOO@ipfile@iv : The name or number of the reference created by % \cite{FOO} in \include file iv % e.g. if in the 4th \include file, \cite{FOO} -> [17], % then \b@FOO@ipfile@iv -> 17. %------------------------------------------------------------------------- % %------------------------------------------------------------------------- % \bibcite is now defined as: \bibcite{LABEL}{VALUE}{IPFILECTR}, so make % the \bibitem & \bibiteml commands output the extra parameter. %------------------------------------------------------------------------- \def\@lbibitem[#1]#2{\item[\@biblabel{#1}]\if@filesw { \def\protect##1{\string ##1\space}\immediate \write\@auxout{\string\bibcite{#2}{#1}{\the@ipfilectr}}}\fi\ignorespaces} %% Placement of `}' in def of \@lbibitem corrected 29 Apr 87 %% (Error found by Arthur Ogawa.) \def\@bibitem#1{\item\if@filesw \immediate\write\@auxout {\string\bibcite{#1}{\the\c@enumi}{\the@ipfilectr}}\fi\ignorespaces} \def\bibcite#1#2#3{{\global\@namedef{b@#1@#3}{#2}}} \def\cite{\@ifnextchar [{\@tempswatrue\@citex}{\@tempswafalse\@citex[]}} % % \penalty\@m added to definition of \@citex to allow a line % break after the `,' in citations like [Jones80,Smith77] % (Added 23 Oct 86) % % space added after the `,' (21 Nov 87) % \def\@citex[#1]#2{\if@filesw\immediate\write\@auxout{\string\citation{#2}}\fi \def\@citea{}\@cite{\@for\@citeb:=#2\do {\@citea\def\@citea{,\penalty\@m\ }% \@debugoutput{\string\@citex: testing whether `b@\@citeb @\the@ipfilectr'% is defined.}% \@ifundefined {b@\@citeb @\the@ipfilectr}{{\bf ?}\@warning {Citation `\@citeb' in file `\@nameuse{ipfile@\the@ipfilectr}' % on page \thepage \space undefined}}% \hbox{\csname b@\@citeb @\the@ipfilectr\endcsname}}}{#1}} % %------------------------------------------------------------------------- % We don't allow \bibliography and \bibliographystyle commands in the root % file, so warn and ignore if appropriate. %------------------------------------------------------------------------- \def\bibliographystyle#1{% \ifx\@currentipfile\savedjobname \@warning{\string\bibliographystyle \space commands in the root file % are ignored ^^Jby the `chapterbib' style option.} \else \if@filesw\immediate\write\@auxout{\string\bibstyle{#1}}\fi \fi} \def\bibliography#1{% \ifx\@currentipfile\savedjobname \@warning{\string\bibliography \space commands in the root file % are ignored ^^Jby the `chapterbib' style option.} \else \if@filesw\immediate\write\@auxout{\string\bibdata{#1}}\fi \@input{\@currentipfile.bbl}\fi} % %------------------------------------------------------------------------- % All we need to do now is to redefine \enddocument so that it properly % checks whether the \cite labels have changed. %------------------------------------------------------------------------- \def\enddocument{\@checkend{document}\clearpage\begingroup \if@filesw \immediate\closeout\@mainaux \def\global\@namedef##1##2{}\def\newlabel{\@testdef r}% \def\bibcite{\@bibtestdef b}\@tempswafalse \makeatletter\input \jobname.aux \if@tempswa \@warning{Label(s) may have changed. Rerun to get cross-references right}\fi\fi\endgroup\deadcycles\z@\@@end} \def\@bibtestdef #1#2#3#4{% \def\@tempa{#3}\expandafter \ifx \csname #1@#2@#4\endcsname% \@tempa \else \@tempswatrue \fi} >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> CUT HERE <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< --------------------------------- !! !! Files of interest [public]000aston.readme !! [public]000directory.list !! [public]000directory_dates.list !! [public]000directory.size !! [public]000last30days.files !! !! Editor - I have a tape labelled TeX 2.9 LaTeX 2.09 Metafont 1.3 !! Unix 4.2/3BSD VAX SUN 2/3 Pyramid Sequent SYS V: 3B2 Tar 1600 bpi blocked !! 20 1 file dated 26 may 1988 (from washington.edu). - Later one on its !! way. !! I have the facility to copy this tape for anyone who sends the following !! 1 2400 tape with return labels AND RETURN postage. !! !! 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. !! !! Replies/submissions to info-tex@uk.ac.aston please !! distribution changes to info-tex-request@uk.ac.aston please !! !! end of issue