summaryrefslogtreecommitdiff
path: root/info/digests/texline/no10
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /info/digests/texline/no10
Initial commit
Diffstat (limited to 'info/digests/texline/no10')
-rw-r--r--info/digests/texline/no10/acog.tex386
-rw-r--r--info/digests/texline/no10/amiga.tex106
-rw-r--r--info/digests/texline/no10/arch.tex141
-rw-r--r--info/digests/texline/no10/aston.tex161
-rw-r--r--info/digests/texline/no10/bcs-ep.cals125
-rw-r--r--info/digests/texline/no10/books.tex180
-rw-r--r--info/digests/texline/no10/cahiers.tex354
-rw-r--r--info/digests/texline/no10/chris2.tex174
-rw-r--r--info/digests/texline/no10/dante.tex88
-rw-r--r--info/digests/texline/no10/didot.tex150
-rw-r--r--info/digests/texline/no10/ed.tex109
-rw-r--r--info/digests/texline/no10/ep90.tex44
-rw-r--r--info/digests/texline/no10/good_guys.tex110
-rw-r--r--info/digests/texline/no10/groningen.tex29
-rw-r--r--info/digests/texline/no10/meetings.tex294
-rw-r--r--info/digests/texline/no10/new.tex116
-rw-r--r--info/digests/texline/no10/newtwo.tex166
-rw-r--r--info/digests/texline/no10/nordic.tex417
-rw-r--r--info/digests/texline/no10/orin.tex17
-rw-r--r--info/digests/texline/no10/ou.tex83
-rw-r--r--info/digests/texline/no10/rose.tex56
-rw-r--r--info/digests/texline/no10/rowley.tex44
-rw-r--r--info/digests/texline/no10/sgml.tex74
-rw-r--r--info/digests/texline/no10/talk.tex854
-rw-r--r--info/digests/texline/no10/tex88.tex72
-rw-r--r--info/digests/texline/no10/texline.head40
-rw-r--r--info/digests/texline/no10/texline.tex143
-rw-r--r--info/digests/texline/no10/tl.tex28
-rw-r--r--info/digests/texline/no10/tlx.tex70
-rw-r--r--info/digests/texline/no10/verbar.tex33
-rw-r--r--info/digests/texline/no10/victor.tex124
31 files changed, 4788 insertions, 0 deletions
diff --git a/info/digests/texline/no10/acog.tex b/info/digests/texline/no10/acog.tex
new file mode 100644
index 0000000000..e86008cbd8
--- /dev/null
+++ b/info/digests/texline/no10/acog.tex
@@ -0,0 +1,386 @@
+\centerline{\bf Idle by the Thames}
+\medskip
+\noindent
+On April 5th--7th I had the pleasure of attending
+a workshop on \sgml\ organised by the AGOCG
+(Advisory Group on Computer Graphics). The reason for the
+workshop ran thus: now that \sgml\ has adopted CGM (Common
+Graphics Metafile) as its method of incorporating
+graphics, is there a case for promoting \sgml\ as the
+medium of document interchange among the graphics
+community. Keen readers will notice a flaw here
+straightaway: CGM is in no way a part of \sgml: on the
+other hand, CALS (Computer-aided Acquisition and
+Logistic Support)
+does embrace both CGM and \sgml\ -- and group 4 fax, and
+IGES. True, it is possible to include CGM as a `Notation'.
+A `Notation' is a bit like a |\special|. You can include
+anything you like, but whether anything sensible happens
+to it is another matter altogether.
+
+As I've suggested elsewhere, in the \TeX\ world we've
+been electronically interchanging documents for quite
+some time. And since I'm quite convinced that \TeX\ is a
+whole lot better at graphics than we admit, I thought
+that it might be helpful to contribute something about
+\TeX\ and\slash or graphics. (`Share experiences' as
+someone said at the workshop: something to do with
+changing a light bulb I think.)
+
+The workshop was attended my three main groups: those
+presenting papers, who notionally had some grasp of
+\sgml\ (this included me, so the grasp could be tenuous);
+a clutch of University Computer Centre people who mostly
+didn't know a document type from its declaration
+(probably there for the experience); and the Rutherford
+boys and girls. This last group requires a bit of
+explanation: the workshop was held at the delightful
+Cosener's Hall in Abingdon. Cosener's is owned\slash used
+by Rutherford Labs as a sort of residential\slash
+conference place. It is really delightful with an
+excellent conference area, and electronic gadgetry so
+advanced no-one could work it (but no email access: I was
+quite twitchy after three days -- just like caffeine
+deprivation). Essentially it is an outpost of Rutherford.
+
+The papers were, on the whole, good. Easily the best was
+Tim Niblett's from the Turing Institute in Glasgow
+(`\sgml\ and Programmed Documents'). I also found Angela
+Scheller's paper (`Experience with \sgml\ in the real
+World') very useful, since she was discussing the {\sc Daphne}
+project. {\sc Daphne} (Document Application Processing in a
+Heterogeneous Network Environment) uses \TeX\ as its
+formatter. Hers was the only paper which demonstrated that
+you could do anything with \sgml\ and CGM graphics (on her
+own very particular installation). That's not quite fair,
+since David Duce and Ruth Kidd of Rutherford did something
+similar (`The {\sc Daphne} Document Types and AGOCG'), but
+had to email it to Angela to be processed.
+
+Obviously there was a very heavy diet of \sgml. Paul
+Ellison waded us through the murky depths of what was
+happening with standards, and all the associated
+standards like DSSSL, SPDL, etc, etc (`\sgml\ and related
+Information Standards'). It was a rich diet of acronymns.
+Martin Bryan exposed us to `Using the full power of
+\sgml', an awesome prospect.
+
+Two things surprised me from the beginning. First was the
+general low level of understanding of what was in the
+various standards -- what they were for. Although all the
+papers were available at least a few days in advance,
+they had almost all been written for \sgml\ literate
+audiences. First mistake. The second surprise was the
+readiness with which standards were accepted as `a good
+thing'. There was a conviction that only ISO standards
+could be considered. This left \PS\ in an interesting
+position, although we were assured that the SPDL
+(Standard Page Description Language) would look a lot
+like \PS, though without the programmability or the fonts
+(what's left?). People seemed happy to accept assurances
+that there would one day be suitable software to allow
+\sgml\ to be input painlessly across a wide range of
+platforms; that one day there would be suitable
+formatters linked to the \sgml\ to allow you to see what
+had been input to \sgml; and that one day there would be
+enough DTDs (Document Type Definitions: broadly
+analagous to \LaTeX\ styles) to suit a reasonable range of
+needs.
+
+The workshop convenor, Anne Mumford, made it clear from
+the start that we were supposed to work for our living
+and make some recommendations about electronic document
+interchange. Most of the papers and discussion addressed
+this in a general way (although I would argue that only
+three of the dozen or so invited papers even
+{\it considered\/} graphics at all -- mine, and the two
+{\sc Daphne} papers). I had understood the `community' to
+be the academic\slash research community (hence the
+inclusion, for example, of Lou Burnard and TEI -- the Text
+Encoding Initiative). However, it never did become very
+clear exactly who the `community' were supposed to be.
+
+To focus our minds, Anne had
+distributed a list of `discussion topics':
+\item{\rtr}what requirements does the community have for
+document exchange?
+\item{\rtr}what are the target systems?
+\item{\rtr}what document types meed to be defined for the
+community?
+\item{\rtr}what software can we use today?
+\item{\rtr}what software do we need to have available if
+\sgml\ is to be a successful form of document interchange?
+\item{\rtr}what support is needed in the community if we are
+to move to use \sgml?
+\item{\rtr}writing funding proposals for the community for
+work to get \sgml\ in use.
+
+\noindent
+It was fairly clear from these topics that at best we
+could bring in a verdict of `not proven' for \sgml's
+suitability, but there was no way we could reject it
+entirely. The whole jury was biassed towards one view
+point. To ensure `evenhandedness', an extra speaker
+(Ian Campbell-Smith of ICL) was shipped in at the last
+minute to tell us something about ODA (note that the `O'
+now implies `Open', not `Office' as it once did).
+
+But eventually, when the work came to be done, these
+topics were laid aside and the real reason for the workshop
+appeared. The participants were broken into three groups.
+I should have sensed something was wrong when two of the
+groups were to be chaired by Rutherford people (the other
+by the convenor): I definitely realised that we had been
+railroaded when a revised sheet of topics
+appeared to be considered by each group. True, these
+revised topics could be considered to have arisen during
+the course of the workshop: however they were not logical
+outgrowths of either the explicit purpose of the workshop,
+nor of the main direction of discussion. So replace those discussion
+topics given above with:
+
+\noindent ``AGOCG wishes to distribute:
+\item{\rtr}viewgraphs
+\item{\rtr}teaching material
+\item{\rtr}manuals
+
+\noindent to University sites in a form where they can
+incorporate it into local teaching material and
+documentation.
+\item{\rtr}is \sgml\ the right protocol to use?
+\item{\rtr}if so, are the {\sc Daphne} DTDs a good starting
+point?
+\item{\rtr}if so, what changes are needed?
+\item{\rtr}are there commercial offerings we should consider?
+\item{\rtr}what utilities related to the \sgml\ system are
+needed?
+\item{\rtr}should the UK academic community develop its own
+software?
+\item{\rtr}how should what AGOCG does be influenced by other
+requirements?
+\item{\rtr}if we target for {\tt troff} and \TeX\ is that
+sufficient?''
+
+\noindent If the conclusions had been pre-empted before,
+they were even more constrained now!
+
+As Bob Hopgood of Rutherford explained, the question {\it he}
+wanted answered could be summarised `how can Rutherford best
+distribute the GKS manual electronically'. That was why {\it
+he} had brought us together, and why {\it he} had had the workshop
+organised (the myth of ACOCG as an entity with any existence
+outside Hopgood was eliminated). Plain and simple. Had that been
+an explicit question from the outset we could have given him an
+answer on day one and then got down to something more
+interesting. Given Hopgood's position at Rutherford, the
+weighting of the workshop and its work groups towards
+Rutherford, and the master stroke of a piece of paper with
+specific questions, it was inevitable that it was difficult to
+restore the workshop to its apparent explicit purpose.
+
+An interesting by-product of the workshop was the
+prepared papers. They illustrated neatly the problem
+with systems which emphasise structure and virtually
+ignore formatting: they may have been logically
+structured, but in terms of document design they were
+almost uniformly appalling, and difficult to read: the
+typewriter conventions of underlining, no indentation on
+the first line of a paragraph, but an extra `line' between
+paragraphs, and so on were much in evidence. Even
+`standard' \LaTeX\ documents were starting to look
+well-designed by comparison.
+
+That does not mean the workshop was a waste of time. From
+my own point of view it helped me put straight my view of
+\TeX\ and graphics; it allowed me to raise the perennial
+question of the character corruption which occurs to file
+transfers which pass through the Rutherford Gateway (and
+to be told that it was because I was trying to pass
+`non-mail' characters through -- whatever that
+mumbo-jumbo means); it revealed the immense ignorance
+that persists about \sgml, ODA, \TeX, and practically
+everything else we've been doing for the last five to ten
+years. Yes it depressed me -- especially the ready
+adherence to tomorrow's software in preference to today's
+tested and available software. But the food was
+plentiful, the majority of the participants stimulating,
+and the surroundings extremely pleasant. If only it had
+been a bit more rigorous. Beware Rutherford Appleton Labs
+bearing gifts!
+
+
+\rightline{\sl \mwc}
+
+\bar\centerline{\bf Echoes}
+\smallskip
+\noindent
+The Displays Group of the BCS held a `State of the Art
+Seminar' on Systems Integration and Data Exchange on
+February 28th. This meeting examined some of the current
+range of `documentation' standards like \sgml, ODA, CGM,
+\PS\ and CALS. It was curious that this came so hot on
+the heels of the BCS Electronic Publishing Group's
+similar one day meeting. Much could be gained by a little
+more cooperation here. Nevertheless, outside the subject
+matter there was surprisingly little overlap. The speakers were
+different, and the audience was not the same as the EP one
+(except for me, I think).
+
+One of the things I found interesting was the
+re-usability of presentations. One of the major selling
+points for \sgml\ is that it allows the same information
+to be re-used in a number of forms. In fact, if you are
+not going to re-use the information, it becomes difficult
+to justify the added inconvenience of \sgml. Paul
+Ellison's talk was re-used at the AGOCG Workshop the
+following week; Alan Francis' presentation was a
+reworking of his Electronic Publishing talk at Durham
+last year (and at the AGOCG meeting I heard Lou Burnard
+re-present the paper he had given at the BCS ep meeting).
+It often helps to hear the same material again -- the
+army principle of `tell them what you're going to tell
+them; tell them it; and then tell them what it is they've
+just heard'. Even Heather Brown's talk reminded me of
+something I had once heard at another Displays Group
+meeting at Rutherford Labs. All a case of d\'j\`a \'ecout\'e.
+
+Anne Mumford (Integration and Exchange --
+Restating the Case for Standards) introduced the day by
+making a case for standards. Here standards tend to be
+taken to mean `Standards, as agreed and ratified by
+national or international bodies'.
+
+Paul Ellison (\sgml\ and Related Information Standards)
+led us through the many-threaded path of `\sgml\ and
+Related Information Standards', and even treated us to his
+version of how Adobe was led to the sacrificial altar to place
+\PS\ `in the public domain'. I'd heard a rather different
+version, so it will be interesting to find out just what
+went on. There must be room for a book on Adobe, just like
+the clutch of books which have come out recently on Apple.
+It is difficult to get excited about the many standards and
+what seems like their interminably slow path to acceptance.
+
+One of Paul's claims was that math coding through \sgml\
+would mean that the resultant formulas could be input to
+algebraic manipulation systems. This seemed such a very
+useful attribute that I contacted Barbara Beeton to see
+if she knew of any cases where this was done. She was
+unable to uncover anything. On the other hand, several
+systems, Mathematica included, output \TeX\ form
+formulas. This tendency to attribute to \sgml\
+capabilities which only exist in theory does worry me. I
+would like to see something substantive.
+
+Heather Brown's talk (Structured Multimedia Documents and
+the Office ({\it sic\/}!) Document Architecture) was a very
+good overview of ODA -- easily the best I've heard so far.
+It is quite intriguing how both \sgml\ and ODA appear to be
+embracing `multimedia'. ODA almost offers something which
+I find quite interesting (something that \TeX\slash
+\LaTeX\ offers too, but have failed to
+point out to the world as a positive feature). An
+ODA document can be revisable or not: depending on what
+you ship, the recipient can change it and reformat it, or
+merely print it out (in \TeX\ terms you can send the
+marked up text, which is revisable, or the \dvi, which
+isn't). There are many documents which you do not wish to
+be changed. The ultimate non-revisable document must be
+the fax, but it's usually also unreadable. It seems to me
+that ODA is a little more realistic than \sgml\ in its
+world view. It at least acknowledges that there is a
+layout structure, as well as a logical one.
+
+Alan Francis discussed the many differences between CGM
+and \PS\ (CGM versus \PS\ -- Horses for Courses). It should
+come as no real surprise that they are trying to address
+slightly different issues, and that in different
+circumstances one is more applicable than the other. Since
+CGM isn't a programming language and doesn't address
+itself to font questions, it is a great deal simpler and
+more compact. Converting from CGM to \PS\ seems no great
+feat. CGM is undoubtedly an ideal way of encoding graphics
+for interchange. I note that there are some \dvi\ drivers
+which can accept included CGM, and also that
+Wilcox's Metaplot may also convert CGM to \MF. As usual,
+we're there, but we aren't jumping up and down about it. It
+seemed to me less a case of horses for courses than
+of trying to compare bicycles and fish.
+
+Jon Owen (Standards for Product Data Exchange
+and Conformance Testing) illustrated that exchanging
+CAD-CAM graphics and diagrams was certainly possible, but
+that you had to be very careful to establish just what it
+was you thought you were exchanging. The drawings didn't
+always contain all the information you expected: the old
+adage about what you see not being all there is, far less
+what you want, was brought home very clearly.
+
+In a multi-authored paper from Rutherford Labs, (Integration
+of Graphics and Communications in {\sc Argosi}: J Gollop,
+R Day, R Maybury \& D A Duce) Duce looked at {\sc Argosi}, a
+`European' project to transmit continuously updated
+information to selected points. {\sc Argosi} (Applications
+Related Graphics and OSI Standards Integration) is an
+Esprit project to advance the state of the art of
+communicating graphical information over international
+networks. The specific demonstrator application chosen is
+a prototype road freight scheduling system, calling on
+databases in nations represented in the project. The
+databases contain causes of delay which a freight
+scheduler needs to take into account when planning a
+Europe-wide journey.
+
+Lastly, Norman Harris of Procad described the CALS
+project (CALS -- the US Initiative). With the massive
+backing of the DoD (and now a number of other US Government
+agencies) CALS has lent massive legitimacy to \sgml, having
+`adopted' it as one of its many `standards'. I have a
+sneaky suspicion that CALS has managed to rescue \sgml\
+from the doldrums. Harris described some of the original
+motivation and history of the iniative, covering TIMS and
+ATOS. As I have commented elsewhere, one of the curious
+by-products of CALS may be to save trees, since one
+objective is to reduce the paper flows between and within
+the contractors and the military. CALS will have a very
+wide effect: besides the US Armed Forces, other Armed
+Forces may adopt it; non-US aerospace and `defence'
+contractors will have to comply to tender for US
+contracts; some CALS specifications have been proposed as
+FIPS (Federal Information Processing Standards) for use
+throughout the US federal government. Some state
+governments (especially those like California and
+Washington with a large number of arms contractors) are
+likely to adopt it. CALS is not static, and the next
+stages include examination of other `interchange' formats
+and standards, like ODA/ODIF, SQL (Structured Query
+Language), and PDES (Product Data Exchange Specification).
+
+The absence of the last speaker meant that there was extra
+time for discussion. The printed version of this paper by
+Shiela Lewis (Testing, Testing, One, Two, Three) raised
+several interesting issues about conformance testing,
+chiefly in the context of the CALS Test Network. At a
+time when many vendors claim to adhere to various
+standards, it is valuable to see what mechanisms are
+being invoked to clarify what adherance means. She notes
+that `Conformance testing does not in any way prove the
+usability of the product, simply its ability to process
+code in the manner prescribed by the Standard'.
+
+An interesting programme which would have been a worthy
+BCS ep meeting -- it seems a great pity that there is not
+greater coordination between the groups. Calling it a
+`State of the Art Seminar' was very astute! It seemed a bit
+expensive to me, especially as there were no
+foreign speakers jetted in at enormous cost, and no lunch.
+BCS ep provides speakers of equivalent standard (sometimes
+the same ones!), and lunch. The only advantage that I
+would say this meeting had was the provision of the papers
+to all the participants. I have mixed feelings about this:
+on the one hand it is a real boon to the audience (and to a
+reviewer). On the other hand it puts sufficient extra work
+into the hands of the speakers that it might dissuade some
+of them from speaking at all.
+
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/amiga.tex b/info/digests/texline/no10/amiga.tex
new file mode 100644
index 0000000000..bef70ac00f
--- /dev/null
+++ b/info/digests/texline/no10/amiga.tex
@@ -0,0 +1,106 @@
+% Hi Malcolm,
+% this is the paper about Amiga\TeX{} I promised you in Karlsruhe. If
+% there are any problems with the gateway, these are the used chars.
+% ABCDEFGHIJKLMNOPQRSTUVWXYZ (uppercase letters)
+% abcdefghijklmnopqrstuvwxyz (lowercase letters)
+% \ -- backslash
+% { } curly braces
+% ( ) - . , : parentheses, dash, dot, comma, semicolon
+% My address is
+% Konrad Neuwirth
+% Fernkorngasse 44-2-4
+% A-1100 Wien, Austria
+% !!!PLEASE!!!! do not send any mail to the address given in the
+% participants list handed out at the conference. It will reach me, but I am
+% not in official contact with the Institute.
+%
+% so long,
+% Konrad (a4422dae at awiuni11.bitnet)
+\def\\{\hfil\break}
+\centerline{\bf Amiga and \TeX{}}
+\centerline{\bf a very special relationship}
+\smallskip
+\noindent
+We all know that \TeX{} is special stuff, but why the Amiga--\TeX{}
+relationship? That's an easy one: the Amiga and the Amiga\TeX{}
+implementation make a very good pair. The Amiga itself has some very nice
+resources which make Amiga\TeX{} a very good \TeX{}-workstation for a
+very nice price.
+
+The Amiga was the first computer to introduce a truly multitasking system
+on a PC priced machine. The operating system also is rather user friendly
+but still quite fast. AmigaDOS with the user interface Intuition is
+actually everything OS/2 wants to be. The Amiga also has a coprocessor for
+speedy graphics, good support over Networks (both academic and commercial),
+a big Public Domain software collection (over 2000 disks). What is also
+nice for a \TeX{}-Station is that it can read quite a variety of disk
+formats. You can read disks written by Macintosh, PCompatibles, C64s, Atari
+STs and even Acorn BBC Computers. It is also very easy to upgrade the
+processor from the standard 7.54\,Mhz 68000 up to a 25\,MHz 68030 and 68882
+combination.
+
+The niceties of Amiga\TeX{} are that it uses all the Amiga's resources to
+their full extent, especially the multitasking system. With the addition of
+ARexx, an implementation of the IBM Mainframe batch language REXX, that
+also is a tool to link together tasks, it is very easy to have preview,
+\TeX{} and an editor in the memory simultaneously and each program knows
+about the others. So you just press a key in the editor, it tells \TeX{} to
+process the current editor file, and \TeX{} sends off the pages to the
+previewer as soon as it finishes them. This improves the speed of the
+debugging cycle enormously, as you don't have to wait for \TeX{} to go into
+memory, finish processing etc. If \TeX{} encounters an error, it tells the
+editor the exact location and the editor jumps to the point. You can also
+have the editor window directly below the previewer window and so see the
+real code while looking at the finished document.
+
+Amiga\TeX{} doesn't require a hard disk. I used to run it with 2 or 3
+drives for some time and it really works. It is not as fast as with a
+hard disk, but it still works fully. It does that with quite a trick: it
+has an intelligent font cache. The minimum hardware configurations for
+Amiga\TeX{} are either 1.5\,Mbyte of memory and 1 drive or 1\,Mbyte and 2 drives.
+You can also run \TeX{} in a 512\,kbyte system, but you can run just a
+very small version of plain \TeX{},
+and \LaTeX{} not all.
+
+The printer drivers are something special, too. They all know about
+\MF\ and so can generate all the missing fonts. This can be done with 2
+ways. You can either tell them to start \MF\ as a background task and
+wait for \MF\ to finish, or you can tell the \DVI\ program to generate a
+font queue which can be worked of any time you want. This is also true for
+the preview program.
+
+The printer drivers, with the exceptions of those for the QMS Kiss and the
+SmartWriter, allow the inclusion of graphic files. But this is much easier
+than on other PCs, as the Amiga has a standard graphic format called {\tt ILBM
+IFF}. So you can include any raster graphic file, created by any of the
+great graphic packages available for the Amiga, within your documents. You
+can also see what the graphic will look like with the previewer, although
+the calculation of a picture takes some time (around half a minute). The
+pictures also will be dithered automagically. You can even specify the
+method you want them dithered, which can be done with the Floyd-Steinberg
+algorithm, a standard ordered dither or with the classic method used, for
+instance, by all the newspapers. The graphics features also will be
+improved in the future, colour support and support for structured
+graphics within the \DVI\ programs is planned.
+
+Amiga\TeX{} is a real workhorse. It offers some very unique features and
+still is able to communicate with the world. It is fast even on the slow
+standard processor and it will blow anything away on a fast processor. It
+offers all the features you see on the big \Unix\ workstations, but for a
+fraction of the price. It is simply irresistible.
+
+For more information contact:
+{\parindent30pt\obeylines
+Radical Eye Software
+Tomas Rokicki
+Box 2081
+Stanford, CA 94309
+}
+
+This may look like a commercial. It is not intended to be. It
+is just shows that I like the project. I don't get any money for this. I am
+just a satisfied user.
+
+\rightline{\sl Konrad Neuwirth}
+
+
diff --git a/info/digests/texline/no10/arch.tex b/info/digests/texline/no10/arch.tex
new file mode 100644
index 0000000000..f2acff0762
--- /dev/null
+++ b/info/digests/texline/no10/arch.tex
@@ -0,0 +1,141 @@
+\centerline{\bf Archimedes \TeX}
+\smallskip
+\noindent
+Archi\TeX\ (\TeX\ and \MF\ on
+ Archimedes computers) consists of:
+\item{\rtr} Knuth \TeX\ 2.93 fully verified
+\item{\rtr} {\sc initex}
+\item{\rtr} plain \TeX\ (source and format file)
+\item{\rtr} \TFM\ files
+\item{\rtr} \DVI\ driver for screen previewing and various
+printers;
+ runs under Arthur 1.2 and Risc-OS 2.00
+ using the {\sc wimp} environment and multi-tasks
+under Risc-OS
+\item{\rtr} full font set for the screen (95
+pixel/inch)
+\item{\rtr} fonts for one printer (as
+described under `Printers supported')
+
+
+\noindent Also available are:
+\item{\rtr} \LaTeX\ (format and source files)
+\item{\rtr} \BibTeX
+
+\noindent
+Archi\TeX\ runs on any Archimedes with at least 1\,Mbyte of RAM and
+one double sided disk drive. A second drive and/or a hard disk
+and more memory are recommended.
+
+\smallskip
+\goodbreak
+\leftline{\sl Printers supported}
+\noindent
+The \DVI\ driver currently supports besides the screen in
+any resolution the following printer-types (the numbers in
+brackets are the horizontal/vertical resolution in
+pixel/inch):
+
+\item{\rtr}EPSON FX (240$\times$216, 80$\times$72)
+\item{\rtr}EPSON MX-80 (120$\times$144, 60$\times$72)
+\item{\rtr}EPSON LQ/SQ (360$\times$180, 180$\times$180)
+\item{\rtr}NEC P6 (360$\times$360, 360$\times$180, 180$\times$180)
+\item{\rtr}NEC P2 (120$\times$120)
+\item{\rtr} OKI uLine (288$\times$288, 144$\times$144)
+\item{\rtr}HP-Laserjet+ (pixel-driver) (300$\times$300, 150$\times$150)
+
+\noindent These include the following printers:
+FX-80, FX-100, MX-80, SR-10 (IBM), NR-15, SG-15, KXP 1092, P2, P3, P5, P6, P7,
+P8, P9, LQ-2500, SQ-2500, OKI 293 (IBM), OKI 293 (Microline), DPL24D, DPL24I,
+DL3300, HP-Laserjet+.
+
+The package contains one printer font set, which you can select for one of the
+above.
+
+\smallskip
+\leftline{\sl Features}
+\item{\rtr}search paths for input files, paths for output files
+ (using system variables)
+\item{\rtr}additional characters for other languages can be implemented
+ if requested
+\item{\rtr}`Libraries' (similar to \unix-Archive for \TFM\
+and font files,
+ thus reducing space requirements and speeding up the font
+ access time; also eliminating problems with too many files
+ in too many directories on a hard disk
+\item{\rtr}one driver for the screen and printers
+\item{\rtr}7 different types of printers
+\item{\rtr}`landscape' print option
+\item{\rtr}screen output using one, several or no windows
+\item{\rtr}screen resolution can be selected, thus enabling
+ magnified (for example, using the printer fonts) and smaller
+ output (for example, whole page vertically with appropiate
+fonts) \item{\rtr}`overview' function (reduces output to display
+a full page
+ on the screen) enables you to get an impression of the page layout
+\item{\rtr} printer parameters for adapting half compatible printers
+\item{\rtr}optimizes printer output (using minimal empty graphics)
+\item{\rtr} uses \PK\ files (\PXL\ files can also be used).
+\item{\rtr}the \DVI\ driver multi-tasks under Risc-OS
+\item{\rtr} both the format and print process can be interrupted
+ (even in the middle of a page)
+\item{\rtr}pages can be printed in any sequence (`skip mode'),
+ which can be defined in a file
+\item{\rtr}the unpacked \PK\ fonts are swapped, thus only
+the packed
+ fonts must fit into memory
+\item{\rtr}a log window is used to display memory use, unpacking of
+ fonts etc.
+\item{\rtr} missing scaled fonts can be substituted with unscaled fonts
+\item{\rtr}the page size -- the size of the bitmap buffer -- can be
+ automatically taken from the postamble
+
+
+
+
+\leftline{\sl Extensions available}
+\noindent
+\LaTeX: 3 disks\hfil\break
+\BibTeX: 1 disk\hfil\break
+Additional fonts: fonts for more than one printer and/or
+ other resolutions are available for a
+ shipping and handling fee.
+\smallskip
+\leftline{\MFsl}
+\noindent
+Consists of:
+
+\item{\rtr}Knuth \MF\ 1.7 fully verified (includes a
+version
+ using the {\sc wimp} environment for on-line
+graphics
+ output and multi-tasks under Risc-OS)
+\item{\rtr}plain \MF\ source and base file
+\item{\rtr}{\sc inimf}
+\item{\rtr}utilities GFtoDVI, GFtype, GFtoPK, GFtoPXL, PXtoPK,
+ PKtoPX, PLtoTF, TFtoPL, CHtoPX and PXtoCH
+\item{\rtr}\MF\ source files for the Computer Modern fonts
+of
+ the \TeX\ system and the source files for the
+fonts of
+ the \LaTeX\ system
+
+\smallskip
+\leftline{\sl Technical Data}
+\noindent
+Computer: Archimedes A440, A420, A410, A310, A3000\hfil\break
+Memory: $>=$ 1\, MByte \hfil\break
+Monitor: normal,
+multisync, high-resolution, mono\-chrome or colour \hfil\break
+Operating
+System: Risc-OS (and also Arthur 1.2 for Archi\TeX).
+
+
+Available from:
+{\parindent20pt\obeylines
+ Tools GmbH
+ Kessenicher Str. 108
+ FRG-5300 Bonn 1
+ e-mail: {\tt tex@tools.uucp}
+}
+\rightline{\sl Dieter Gogolin}
diff --git a/info/digests/texline/no10/aston.tex b/info/digests/texline/no10/aston.tex
new file mode 100644
index 0000000000..882c7ba6c6
--- /dev/null
+++ b/info/digests/texline/no10/aston.tex
@@ -0,0 +1,161 @@
+\centerline{\bf uk\TeX ug meets again}
+\smallskip
+\noindent
+The third Meeting of the UK \TeX{} Users' Group was held
+at the University of Aston, on 11 October 1989.
+The programme was presented in two parts, Fonts: how they are
+created and Fonts: how they are used. As one of those attending
+said, this was a nice \TeX{} meeting -- \TeX{} didn't get mentioned by
+the speakers until after tea!
+
+\smallskip
+\leftline{\sl Summary of papers}
+ \noindent
+David Kindersley -- `Making letterforms':
+this talk was built around a set of marvellous 35\,mm slides
+showing the various kinds of lettering that he had designed and carved.
+In particular these illustrated the freedom available to a designer
+making a fairly short inscription which could be seen as a work of
+art as well as conveying a message in words. Among the additional
+freedoms were the ability to superimpose letters within a word,
+to make minor adjustments to the sizes of the letters so that the
+words would fit the space and the chance to create a backward sloping
+italic to fit a design. Against that had to be set the necessity of
+making systematic adjustments to letter sizes so that words could
+still be read on, for example, a horizontal memorial set into
+the floor.
+
+David Kindersley also talked about his search for an
+algorithm to ensure correct letter spacing in typesetting.
+This is built on the basis that letter spacing should be
+applied to groups of three letters -- the middle of the
+three should be in the optical centre -- and that it is
+possible to compute a `centre' for each letter in a fount.
+His method ignores the bounding rectangle which was
+imposed on metal type.
+
+Paul Bacsich (Open University) -- `\PS\ needs MoreMaths':
+a talk illustrated with overhead projector slides, spoke
+about his project to design additional characters to be used with
+\PS\ so that output to be printed in a combination of Times and
+Symbol (for the Greek letters) could also include as many maths symbols
+as Computer Modern. His particular aim was to have available in
+Times\slash Symbol\slash MoreMath a set of pi characters comprising all
+the pi characters in Computer Modern, the relevant ISO standard and the
+\sgml\ list.
+Apart from needing to design the actual characters in some cases, it was
+necessary to find the baseline of the font and, even more
+important, its maths axis so that all the characters
+may be set properly.
+
+Sarah Winthrop (Linotype)
+gave a short introduction to typography -- communicating
+by means of the printed word. She included a brief history of type,
+including the system devised by Frutiger for the Univers font family
+of using a two-digit code to indicate the style of the face, e.g.,
+roman, italic, condensed, (second digit) and the weight: anything from
+ultra light to extra black (first digit). She also explained the reason
+why different sizes of type generally need different designs within the same
+typeface.
+
+Andrew Boag (Reading University)
+used 35\,mm slides from two carousels -- so
+that he could show two slides together when needed to illustrate his talk,
+`Creating Letterforms'. He also circulated
+a handout. His talk was based on seven points describing what type is
+and therefore what type design is, and what those seven points mean
+for the type designer. His illustrations showed screens from various
+type design programs.
+
+James Mosley -- `Type, evolution and examples'
+had been billed as talking about digital type, but
+assured the audience that he would in fact be talking entirely about
+analogue type! He started by talking about the constituents of the
+(English) character set -- the capital and lower case letters and the digits;
+the \& and other oddities. He reminded us that Western languages were
+unique in using two forms for each letter (upper and lower case). The
+upper case letters were based on Roman inscriptions, particularly the
+letters used on Trajan's Column; lower case type was originally designed
+to mimic fifteenth and sixteenth century handwriting; and the digits
+were based on Arabic shapes. All these shapes, together with some oddities,
+had been incorporated into the original typewriter and had moved into the
+standard computer character set from there.
+
+There had been various experiments in typography, such as monoline type
+with no distinction between upper and lower case. Another experiment was
+the use of sans serif fonts. He showed a slide of a book published in 1900
+using a sans serif font -- although the page was very decorated.
+
+James Mosley then showed slides of some of the earliest examples of
+features that are part of modern typefaces: a Greek inscription from
+340 {\sc bc} showed undoubted serifs; an illustration from 1200 {\sc
+bc} showing characters made by a reed pen or brush showed shading --
+the change of thickness in the character shape, and an inscription
+found in Pompeii shows a thick\slash thin contrast in upper case
+letters. We were then shown pictures of the original types and their
+twentieth century versions of the typefaces Bembo, Garamond, Plantin
+and Grandjon\slash Galliard. These were followed by slides showing
+copperplate, and the Baskerville type face, developments of which
+include the advertising fat faces and Bodoni. The final slides showed
+traditional punch cutting, as still carried out at the Imprimerie
+Nationale, and the later technique of drawing the type on paper
+followed by automatic cutting.
+
+Andrew Trevorrow -- `Drivers revealed'
+started the second part of the programme by
+demonstrating his own \OzTeX{} and Victor
+Ostromoukhov's Mac\MF, using an Apple Macintosh SE and a Dataframe
+projector. As usual, the projected image was just a bit too dim for
+comfortable reading. He showed the results of running the previewer
+trip test, which resulted in a few pages on all of which the printing
+was way out of the page area
+
+Rod Mulvey (CUP)
+described the \TeX{}-to-Type system which has been
+developed at the Printing House of Cambridge University Press.
+They typeset their work on a Monotype Lasercomp at 1000\,dpi using
+an extended range of \TeX{} fonts. CUP will supply \TeX{} design
+packs based on well-tested macros which include their preferred
+book design.
+To get \TeX{} to use the Monotype
+typefaces in place of Computer Modern it had been necessary
+to compile \tfm\ files for the Monotype fonts, bearing in mind that
+Monotype only supply the width of the characters, not their height.
+
+Sebastian Rahtz (Southampton University) on `\PS\ is good for you':
+spoke about the problems encountered when trying to use
+Computer Modern fonts with other \TeX{} fonts, such as the sans serif, and
+at sizes other than their design sizes. Although it should be easy to
+give \TeX{} a different set of \tfm\/s in order to set in a
+different typeface, there was quite a lot of CM-linked information
+built into \TeX{}. Most of this was in the maths setting parts of
+\TeX{}. If you want to use fonts other than CM, there are
+three approaches:
+\item{\it1:} If using |lfonts| -- strip out the CM fonts and replace
+them with what you want;
+\item{\it2:} Redefine the fonts and the macros;
+\item{\it3:} Throw away all the Knuth font information and redo it
+(this approach is described in detail in \TUGboat 10(2)).
+
+In `\PS\ meets Computer Modern'
+Les Carr (Southampton University) talked about his attempt to convert
+Computer Modern fonts into \PS\ fonts. It had seemed an
+attractive project as both \MF\ and \PS\ use Bezi\`er
+curves. The idea had been to refine the \MF\ descriptions to get
+the information that \PS\ needs; this worked up to a point, but
+the whole project proved impossible. In fact, short of scanning images
+of the individual characters into \PS\, there was no way of
+moving from \MF\ to \PS.
+
+Phil Taylor (Royal Holloway and Bedford New College) -- `Computer
+Modern meets \PS'. Phil Taylor had been involved in the
+production of a book that used the Times typeface for text, Computer
+Modern for maths and Adobe Symbol for Greek and similar. The real
+problems came with the maths setting, as in the book all the equations
+were in capital letters, not the lower case envisaged by Knuth. To get
+the mathematical symbols in to the right places in relation to capital
+letters, he had written a splendid macro that when presented with a
+relevant symbol raised it by the correct amount to match the capital
+letters.
+
+\rightline{\sl Carol Hewlett}
diff --git a/info/digests/texline/no10/bcs-ep.cals b/info/digests/texline/no10/bcs-ep.cals
new file mode 100644
index 0000000000..296d82735e
--- /dev/null
+++ b/info/digests/texline/no10/bcs-ep.cals
@@ -0,0 +1,125 @@
+\centerline{\bf BCS-ep}
+\smallskip\noindent
+The BCS Electronic Publishing Specialist Group's meeting of
+December 5th was concerned with publishing standards, and in
+particular with Standard Generalized Markup Language (\sgml{}), Open Document
+Architecture (ODA) and Computer-aided Acquisition and Logistic Support
+(CALS), the acronyms for which are frequently quoted, not always with a clear
+understanding of what they are about.
+
+The first speaker of the day was Professor David Barron from the University
+of Southampton on `Why use \sgml{}?', although perhaps `What is \sgml{}?' is
+really what he discussed. He began by reminding the audience that Electronic
+Publishing is not just Desktop Publishing, that is, in spite of all the hype
+there is a place for non-\wysiwyg\/, that is procedural, systems (although,
+of course, the two do not have to be mutually exclusive). Professor Barron
+then gave a brief explanation of the development of GML at IBM and of MarkUp,
+the two precursors of \sgml{}, together with some details of the ISO working
+groups and a summary of what \sgml{} is. Rather he stated what \sgml{} is not,
+once he had explained the principles of generic markup. \sgml{} is not a
+language -- it is a metalanguage -- and \sgml{} is not a formatter, although
+it specifies how coding systems written according to the rules of \sgml{} can
+be parsed and parsers can be written to output files in such a way that
+they can be input directly into formatters.\looseness1
+
+Professor Barron then explained the significance of the Document Type
+Definition (DTD) and went through a simple DTD describing the meaning of
+the coding. Finally he showed how the power of \sgml{} could be used in a
+project like the OED and how it is invaluable when either transferring
+documents between different systems or producing a range of documentation
+in a single format or related range of formats. For
+those who missed this talk and would like a relatively straightforward introduction to
+\sgml{}, Professor Barron has published a paper which is similar in content to his
+talk in {\sl Electronic Publishing: Origination, Dissemination and Design} (1989)
+2(1), 3--24.
+
+The second talk was on `The Text Encoding Initiative' (TEI). Lou Burnard
+of Oxford University Computing Services
+explained what this is. TEI is essentially an aid to
+scholarship and covers aspects outside those considered by \sgml{}, such as
+those concerned with textual analysis. TEI is not really concerned with
+coding for publishing; it is concerned with the representation of
+already-published texts, for example what actually appears on the page,
+both its content and representation. However, it is not always possible to
+know in advance what is to be described, so the standard \sgml{} DTD
+formulation is not flexible enough unless the DTD can be violated. Lou
+Burnard finished by describing some of the practical problems: the lack of
+software; the lack of success of previous standardization efforts in this
+area; and finally the lack of public awareness.
+
+Stephen Downie, Secretary of the \sgml{} Users' Group and previously of
+Unixsys UK Ltd, gave a rather different introduction to \sgml{}, by pointing
+out that when data and text are input the uses to which they may be put are
+not always all known (as TEI illustrated very aptly). If a text is input
+according to \sgml{} conventions and the DTD has been written properly, then
+the text can be used subsequently for uses which were not envisaged when it
+was originally input. Pathways give new meanings to data.
+
+Stephen Downie then went on to describe the use of \sgml{} in producing the
+Official Journal of the European Community (although in fact no actual
+issues have as yet been produced). The principal problem which has had to
+be solved is the production of nine editions in nine languages, but with
+synoptic pagination. Input is now carried out using the SoftQuad \sgml{}
+Author/Editor (on which a DTD has been written at Pindar Infotek using the associated
+Rules Builder). Using a specially written DSSSL (Document Style, Semantics and
+Specification Language), the documents are converted to SoftQuad {\tt
+troff}, using which all text heights are measured on the first run. Then
+using the \Unix\ utility {\tt awk} a master list is produced which is used in
+the final pagination run. There have been problems, as might be expected:
+producing the DSSSL has been very complex; the journal rules had not
+previously been clarified; US software (as usual) does not concern itself
+with accents and non-latin character sets; and finally, although both
+SoftQuad {\tt troff} is up to the task and \sgml{} reduces the complexity of
+the problem, high programming expertise is required.\looseness1
+
+CALS, Judi Morrison of Interleaf explained, is a program to acquire and
+manage weapon systems information more efficiently. At present 96\% of
+manuals are not computerized, one in four contain errors and it takes up to
+20 months to make corrections -- and the cost is phenomenal. In addition
+10\% of the cost of a weapon system is paperwork. CALS was therefore
+developed to try to save money, reduce development times and improve
+quality. CALS therefore affects almost everybody eventually, in that
+contractors and subcontractors to the military purchase materials and
+expertise (including software) from other industries, and by 1990 all
+proposals to the Department of Defense have to be CALS-conforming.
+
+Of course there are many aspects of CALS, but the documentation aspects,
+which include \sgml{} for text and various graphics standards such as CCITT
+Group 4 (as Fax), IGES (International Graphics Exchange Specification) and CGM
+(Computer Graphics Metafile), are probably the most currently important. The final aim
+is to create a single database which can be accessed by both military and
+contractors. Whether this will actually happen remains to be seen and there
+are bound to be problems of security as well as of a technical
+nature.
+
+After lunch (which through an interesting bureaucratic mistake was
+different from usual!), Patrick Hull and John Dixon of Deuce Systems
+discussed more detailed aspects of CALS, in particular all the various
+standards involved, who produces them and what they mean. It is difficult to
+summarize what was said, but the two speakers made it very clear how complex
+the field is and what a challenge is there for those involved.
+
+In neither of the talks on CALS was there any discussion of what quality of
+weapon systems means in real terms, but it was clear that defence (or
+defense) and military applications have ramifications far beyond the
+immediately obvious.
+
+The final talk of the day was from John Stratton of the National Computing
+Centre and was on The Open Document Architecture (ODA). This is another
+ISO standard which is like \sgml{} but not like \sgml{}. It grew not from the
+world of publishing and computer text processing and programming, but more
+from the world of ECMA, the European Computer Manufacturers Association, and
+was initially concerned (as is probably obvious from the name) with Open
+documentation. The aim was to be able to provide open exchange of
+documents, either in a fully formatted way or in a form which can be edited
+and reformatted. ODA therefore considers a document in terms of both its
+structure and its content or, put another way its logic and its layout. The
+logical view is similar to that provided by \sgml{}, while the layout view is
+in terms of blocks, pages, page sets etc. In addition there are document
+management attributes and standard ways of handling graphics.
+
+In summary, a day full of acronyms, but most people probably came away
+feeling that they understood at least a few of them and the concepts
+behind them.
+
+\rightline{\sl David Penfold}
diff --git a/info/digests/texline/no10/books.tex b/info/digests/texline/no10/books.tex
new file mode 100644
index 0000000000..8bdd21632a
--- /dev/null
+++ b/info/digests/texline/no10/books.tex
@@ -0,0 +1,180 @@
+\centerline{\bf Book Reviews}
+\smallskip
+\noindent
+Every so often something good plops through the letter
+box. Both the books which I received recently fall into
+the `good' category. The first of these was a
+particularly delectable item: not only is it by someone I
+know, but it's a book about
+\sgml\ that is readable. Eric van \hbox{Herwijnen's
+}`Practical \sgml' (to be published by Kluwer Academic
+Publishers Group) is a very thoughtful and balanced
+approach to his subject. Briefly, the background is this:
+Eric works at CERN in Switzerland. One of CERN's problems
+(besides physics), is in exchanging documents between an
+array of different machines both at the Swiss site and at
+other similar locations world wide. The approach has been
+to encourage the use of \sgml. The book is therefore an
+outgrowth of that approach, and therefore covers not only
+the {\sl meta\/}-language, but also the software which
+may be employed to write with \sgml, and the problems
+which were encountered. The {\sl Practical} of the title
+is well-earned.
+
+He takes other systems seriously -- giving fair and
+reasonable attention to \TeX\ (so he should, I taught
+him!), although his example of using \TeX\ to construct a
+memo I found a little idiosyncratic. In a similar way, he
+examines how the same formula for the decay of a
+particular particle could be expressed in \TeX, |eqn| and
+two flavours of \sgml\ DTD (AAP Maths and ISO). Since
+one of the criticism's Eric makes of the \sgml\
+applications is that `compound symbols such as $(m_{\eta
+c})$ and $(Q_c)$\dots have a meaning to physicists' I was
+surprised that he had not redefined them to have a name
+which reflected that meaning. Similarly, if you have to
+distinguish between `a right arrow and a decay reaction',
+why not give them different names? The symbols can remain
+the same, but the coding could be different. This is the
+advantage of markup, that you can make the intention clear.
+But the criticism that Eric is making here is really of the
+DTDs, which are currently inadequate.
+
+One of the appendices discusses the problems which were
+encountered in writing a book on \sgml\ using \sgml. This
+is a particularly illuminating section and does much to
+redress the excesses of other promoters of \sgml.
+
+This is a
+valuable and welcome addition to the literature on \sgml.
+\begintt
+@book{EvH,
+title={Practical {SGML}},
+year={1990},
+author={Eric van Herwijnen},
+publisher={Kluwer},
+isbn={0 7923 0635 X},
+price={\pound24.90},
+pages={307}}
+\endtt
+\smallskip
+\subsection{Introduction to \TeX}
+The other book was Norbert Schwarz' `Introduction to
+\TeX'. I bought the German version last year (along with
+two other German \TeX\slash\LaTeX\ books). This is a
+translation prepared by Jost Krieger, a Dutchman. Now
+there's something interesting. The first non-Knuth \TeX\
+book in English is a translation from the German by a
+Dutchman. And the second may be Bechtolsheim's (another
+non-native English speaker). Hint. It does read a bit like
+a translation too. I don't think that does any harm. Once
+or twice you have to reread a sentence or paragraph to
+understand just what is being meant, but on the whole Krieger
+has done a fair job. It is very much a book on \TeX.
+There is very little about documents. It carefully, and
+most often clearly, goes through the bulk of the plain
+\TeX\ commands (one or two of which sent me scurrying
+back to my {\sl\TeX book} just to check that they really
+did exist). Very thorough. But they do tend to present
+things without giving a clue of the generality or
+usefulness. I did like the fact that the name Baskerville
+appears by page 33.
+
+Many of the examples are extremely practical and useful.
+Inevitably there is a tendency to introduce some things
+in a brief way in order to develop something more
+interesting. Although macros don't appear until Chapter
+7 (starting on page 95), they have in fact cropped up
+several times in the preceding chapters, with only
+rudimentary explanation. The first reference to a macro I
+found on page 15, and the first definition is on page 21.
+I suspect that developing \TeX\ in a `linear' manner is
+near impossible (after all, Knuth had to adopt a sort of
+recursive approach), but sometimes I felt the reader had
+to take quite a lot on trust. The alternative would be to
+illustrate points with trivial examples, and I would have
+criticised that too. Perhaps the single strongest feature
+is the list of commands, together with an explanation
+which forms the `end' of the book. It really is useful to
+be able to flick through that, like an glossary of
+commands, and then refer either to \TB, or to this book
+for more details. A little hypertext version of the
+glossary for my Mac would be very useful.
+
+The authors note the use of |\tracingstats|.
+Unfortunately, as Knuth points out (page 303), and they
+fail to, not all production versions of \TeX\ heed the
+value of the tracing commands. This could conceivably
+confuse the inexperienced. In view of Chris Rowley's
+comments elsewhere in \TeXline, it was interesting to
+read their comment (page 96) `A superfluous pair of
+braces rarely has an adverse effect..' (sic). Although the
+authors claim that the book should be `a bit more
+internationally oriented than a book of English (sic) or
+American origin', they don't suggest A4 alternatives to the
+built-in |\hsize| and |\vsize|.
+
+
+If I have a major criticism, it is one which is really a
+criticism of the publisher (the inevitable
+Addison-Wesley). I can see why the problem arises, but I
+don't think it an adequate excuse. The book was
+inadequately proof read. I suspect the authors themselves
+typeset and proof read the book. This is not what we
+employ publishers for! There are too many places where the
+punctuation should have been tightened up (too numerous to
+mention, but note the comma which begins a line on page
+37 and the opening quotes round the wrong way on page 150), or
+where the english should have been corrected (page 184,
+`dipthong' for `diphthong'; page 84, `incontinuity' for
+`discontinuity'). There are several cases where * is used
+instead of $\times$. Surely the asterisk has not yet displaced
+the $\times$ for a multiplication sign? What makes this more
+culpable is the inconsistency of using both operators. The
+table on page 12 seems curiously incomplete, with one
+conversion factor given merely as the decimal point.
+Small things, but they make a great deal of difference.
+
+And surely we don't have to print from laser printed output?
+Bromides don't really cost that much more -- if Addison-Wesley
+is having difficulty finding a printer, I'd be happy to take
+care of the printing from \dvi\ for them. It seem such a
+tragedy that the amount of effort which Knuth went to in
+providing us with \TeX, the effort that Norbert and
+Jost went to in writing this particular book, should be let
+down by the publisher who inadequately controls that part
+of the process they traditionally handled -- copy-editing
+and printing. There might be some criticism too of the
+driver used, since it shows up those irritating {\it
+dis\/}continuities in the horizontal bar of the square
+root sign and the over- and under-braces which
+appear to bedevil so many drivers.
+
+This is a prime example of the orthogonality of form and
+content. The content is excellent, but the form could do
+with some attention. To dedicated \TeX ies, who know
+what's going on, the form will not detract, because the
+content is so strong. For the uninitiated, for whom this
+book is really intended, the capabilities of \TeX\ may be
+obscured.
+
+Leaving the relatively minor criticisms of content aside,
+this is a fine book. Their discussion on tables (chapter
+6), the list of `common' error messages, and the glossary
+make the book value for money. How much? A mere
+\quid19.95 in paperback, for a bountiful 278 action-packed
+pages.
+\begintt
+@book{NS,
+title={Introduction to {\TeX}},
+year={1990},
+author={Norbert Schwarz and Jost Krieger},
+publisher={Addison Wesley Europe},
+isbn={0 201 51141 X},
+price={\pounds19.95},
+pages={278},
+notes={see also Schwarz'
+ original in German}}
+\endtt
+
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/cahiers.tex b/info/digests/texline/no10/cahiers.tex
new file mode 100644
index 0000000000..1feddbdba1
--- /dev/null
+++ b/info/digests/texline/no10/cahiers.tex
@@ -0,0 +1,354 @@
+\def\talk#1#2{\medskip\noindent\ignorespaces{%
+\def\PS{{\it P{\iteight OST\-}S{\iteight CRIPT}}}%
+\def\sgml{{\iteight SGML}}%
+\def\LaTeX{{\it L\kern-.36em\raise.3ex\hbox{\iteight
+A}\kern-.15emT\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}%
+\it #1\/}: #2.\quad}
+\def\Textures{{\sl Textures}}
+
+\centerline{\bf Cahier GUTenberg}
+\smallskip
+\noindent
+The last \TeXline\ carried abstracts or summaries of the papers
+included in the `zeroth' edition of the Cahiers GUTenberg. Most of the
+summaries below are based on translations prepared by Catherine
+Griffin. The latest edition of the Cahiers, number 4, has short english
+abstracts (slightly enlarged here). This innovation is to be welcomed.
+While it is unlikely that \TeXline\ will ever follow suit, perhaps
+\TUGboat\ will. \smallskip
+\leftline{\bf Summaries from Number 1, April
+1989:} \talk{Quelques r\'eflexions sur le traitement de textes
+informatis\'es \`a propos du logiciel \TeX}{Fran\c cois Chahuneau,
+pp.2--15}
+In the beginning of computing, that is, in the '50's, one could scarcely
+imagine using computers for text manipulation: first, computers were
+scarce; second, it was difficult enough to type computer programs on punch
+cards to dissuade any text except program comments; finally, in any case,
+the resulting printout, from impact printers -- all in capitals and without
+accents! -- would have been most disappointing.
+In the '70's, the parallel development of time-share systems and printing
+terminals (`teletypes'), the adoption of 7-bit \ascii\ which made
+possible the use both upper and lower case, and the appearance of
+line-editors caused a rapid development in this area.
+
+As a result of talk at MIT and in the research labs of
+Bell Telephone on the characteristics of a modern shared time system, we
+saw the appearance of much more powerful line-editors
+ The same people were at the origin of the first text formatters such
+as {\tt roff}, of which the direct descendants -- keeping the same
+philosophy -- were Runoff and Compose on Multics or {\tt nroff} and
+{\tt troff} on \unix. To use these text formatters, one combines in a
+source text the text itself (sensu stricto?) with commands -- to a
+greater or lesser degree cryptic -- for the formatting program.
+\talk{\TeX\ et Baudelaire}{Raymond P Poggenbur, pp.16--20}
+ Here is the history of the birth of a history of history, in other
+words, a chronology. If this work exists today in printed form, it is
+thanks to the marriage of \TeX{} and the DEC 1011, the computer of my
+university.
+ The book `Charles Baudelaire: a micro-history', was published in
+April 1987 by Jose Corti in Paris. The book was typeset by the author,
+using \TeX{}.
+ I propose to describe the origin of the project, then to suggest some
+possibilities for the development of this type of tool and I will end with
+some very brief remarks on the advantages of \TeX{} for the examination of
+chronological problems.
+\talk{\LaTeX\ or \sgml\ pouvaient-ils faire \'eviter la
+catstrophe de la gare de Lyon?}{Jacques Andr\'e, pp.21--25}
+ We remember that 27 June 1988 when a train entered the Gare de Lyon
+at Paris, at fairly high speed and without brakes, ran into and
+embedded itself in a train waiting to depart: 56 dead and dozens of
+wounded. An enquiry was immediately organized by the Minister of
+Transport and the Sea. The results were published as a report -- a
+catastrophe of this magnitude is rarely due to a single cause, but is
+the result of a chain of circumstances. The report mentions in
+particular the possibility of a consciopusly harmful act (the closing
+of a tap), an alarm signal mistakenly pulled, the difficulty the
+mechanic had in applying the brakes, liaison problems by radio and
+blocked signals, the absence of an escape track, etc.
+ But, and this is what prompted this article, the commission noted
+that, when presented with a real crisis, the relations that those
+in charge had to establish between the texts of the various regulations,
+which in turn included cross-references and footnotes, the rules for
+their application, and the procedures indicated by specialised
+instructions -- for example, breakdown procedures -- is not always
+straightforward. The enquiry also drew attention to the specific case of
+an error in the typography of the manual which could lead to a mistaken
+interpretation.
+\talk{Pr\'esentation d'une revue mensuelle compos\'ee automatique
+par \LaTeXsl\ \`a partir d'une base de donn\'ees relationelle}{Nicolas
+Brouard, pp.26--34} The `Revue fran\c cais des sondages' or `Sondoscope'
+is a monthly journal of about 40 pages, typeset automatically using
+\LaTeX{}, from the first to the last page. Each section has its own
+typographic design. A large part of the journal, mainly the tables, est
+extracted from a relational database.
+ The aim of this article is to explain how we produce this journal, and
+the choices we have made. After briefly describing the journal, we will
+talk of the relevant material, then of the type of relational database
+used, and the interfaces bwetween the database and a text formatter
+such as \TeX{}. Finally, we will discuss questions which are not
+resolved by \TeX{} and \LaTeX{}.
+\talk {DDI Dessin DVI}{Andr\'e Violante, pp.35--38}
+\TeX{} is known for its imperviousness to any file type except \ascii.
+In fact, every entity is automatically reduced to a box containing
+`glue', characters and horizontal and vertical marks. These characters
+are only seen by \TeX{} as numeric codes.
+ It is only during preview or printing that
+these codes are transformed to already existing graphic entities.
+ For graphic representation, two possibilities are available to the
+user: \item{$\bullet$}use of the |\special| command to incorporate
+graphics into the document for printing. The drawback of this solution
+is that that the document is not independent of the peripheral, so it
+is not possible to preview the document as it will appear, and to
+prevent the the figure's text to be in \TeX{} characters;
+\item{$\bullet$}the use of semi-graphical fonts. We remain
+independent of the peripheral devices, and graphics done this way could
+be previewed on a screen or printed on an ordinary printer.
+\LaTeX{} exploits this possibility with its graphics environment. However,
+this solution is only for elementary graphics.
+
+\noindent DDI is
+a work environment for the creation of scientific,
+technical and artistic graphics. The fundamental of the
+system is the creation and use of graphic fonts. To use
+these, several tools are available: design software
+({\tt Designcad}); a program to convert {\tt Designcad}
+files to \MF; \MF\ itself; GFtoPK; \TeX; and a suitable
+device driver.
+\talk{Evolution en amont de \TeX: le foisonnement des
+Pr\'eprocesseurs pour la Math\'ematique}{Laurent Siebenmann,
+pp.39--44}
+The problem of keying manuscruipts for a high quality printing is
+particularly difficult when the manuscripts are mathematical. Since Don
+Knuth created \TeX{} partly to resolve this well-known problem (which directly
+involved his own books!), it is probably interesting for the participants
+of the GUT day (including non-mathematicians) to note the different
+solutions surrently proposed. In fact, the realisation of these ideas is
+often of general concern.
+ On the other hand, the specific pre-processors which I will mention, in
+particular my Sweet-teX{}, don't have the same usefulness as \TeX{}
+outside of mathematical sciences: they are specialised tools --
+especially where they are in frequent use.
+\talk{Les concepts graphiques de \PS}{Bruno Borghi, pp.45--51}
+This article is devoted to an analysis of the graphics concepts in force in
+the page description language \PS{}. The basic principles of the
+\PS{} Graphics model are thus distinguished entirely independently of
+the proper language aspects (syntax, general operators).
+\talk{Une macro \TeX\ pour signaler les mises \`a jour\/}{Georges Weil,
+pp.52--53} This macro
+allows one to put a correction bar in the margin of one or more
+paragraphs.
+The macro |\maj| puts a bar for the paragraph which follows.
+The macro |\majdeb| puts a bar for all the paragraphs which follow until
+meeting the command |\majfin|.
+
+\talk{Les fiches cuisine d'Onc' \PS: Fiche N$^\circ$1:
+une table Tra\c cante}{Bruno Borghi, pp.64--66} \PS{} is
+wonderful, it allows you to write text in a spiral with one character
+funnier than the next, and all sorts of other delightful gimmicks.
+Honestly.
+ The problem is that the great majority of applications are concerned
+with much more fundamental graphics problems: tracing presentable marks
+with a horizontal text.
+ For this first cookbook file, Onc' \PS{} will consider an
+application which every \PS{} programmer has confronted: connecting a
+\PS{} printer to a vector graphics program. All the
+output conversion programs such as Tektronix, HPGL or Benson belong to
+this family.
+ The problem is less simple than it appears, but the solutions which
+we will look at together could be adapted to more ambitious cases.
+\goodbreak\bigskip\goodbreak
+\leftline{\bf Summaries from Number 2, May 1989:}
+\talk{Xwindows, \LaTeX, \TeX draw et Plot79, ou comment
+calculer, r\'ediger, dessiner et imprimer plus
+ais\'ement}{Nicolas Brouard, pp.11--12} A workstation running under
+X-Windows offers a way of calculating, writing and
+designing which is much simpler than with a `classic'
+terminal. Two graphics tools, \TeX Draw (a public analogue
+of MacDraw) and PLOT79 (a 3D graphics system based on
+CORE), can easily be employed with \LaTeX.
+\talk{\TeX\ and Graphics: the state of the
+problem}{Nelson Beebe, pp.13--53} Inclusion of graphics in documents
+typset by \TeX\ is not yet a satisfactorily solved
+problem, and no final general solution is in sight. This
+paper surveys alternatives for insertion of graphics in
+\TeX\ documents. It summarizes graphics primitives of
+several modern software systems, and shows how \TeX\
+has seriously deficient support for their direct
+incorporation in \TeX\ itself.
+\talk{JPDraw, un \'editeur de dessins pour \LaTeX\ sur SUN}{Jean-Pierre
+Merlet, pp.54--62}
+We will describe the a drawing editor working on the SUN in the
+{\tt suntools} environment. The first aim of this editor is to generate
+\LaTeX{} files in the `picture' environment. But it is also possible to
+save the designs as \PS\ images, or at least in the shape of
+instructions for a Hewlett-Packard type plotter for the creation of
+colour slides.
+ JPdraw allows mouse manipulation of various geometric primitives
+(lines, text, rectangles, polygons, ellipses, ovals, various curves)
+similarly to Macdraw on the Macintosh. But is also has a meta-language
+for describing drawings, thereby allowing a convenient interface
+between a user program (for example dtp, image handling) and
+\LaTeX{}.
+\talk{\TeX\ et les graphiques dans l'environment
+Mac}{Anestis Antoniadis, pp.63--67} Painting and drawing are the two
+sides of the creation of graphics on the Macintosh.
+{\sl Paint\/} images (otherwise known as bitmaps) are known
+to the Mac as a set of points on the screen. {\sl Draw}
+images (also known as vector drawings) are known to the
+Mac as objects (rectangles, lines, circles, polygons) and
+are defined by their mathematical attributes. As a
+consequence of the way in which they are defined, they
+take full advantage of the resolution of \PS\
+peripheral devices. The goal of this article is to give
+an overview of the methods and software for the
+generation of graphics on the Mac, and to discuss the
+insertion of such graphics in documents prepared with
+\Textures, one of the implementations of \TeX\ on the
+Macintosh.
+
+\talk{Traduction en \TeX\ d'un
+fichier \sgml\ avec r\'ecup\'er\-ation des graphiques et
+des tableaux}{Maurice Laugier, pp.68--72} The logic of \sgml\ markup
+is close to that of \LaTeX, and translation from \sgml\
+to \LaTeX\ can be realised quite simply. However, the
+problem is rather different for graphics and tables. This
+paper presents a way in which the PC graphics characters
+were successfully mapped into \LaTeX, easing the
+production of tables and simple diagrams.
+
+\talk{GI\TeX, PAPS: deux logiciels minipulant \PS\ et
+\LaTeX}{Christophe C\'erin, pp.73--80}From pc-based graphics
+programs, PAPS (Programme d'App\-lication \PS) transforms
+an image into a \PS\ format. It will also allow some
+manipulation of the graphics image. GI\TeX\
+(G\'en\'erateur d'Image \TeX) is a program which allows a
+{\tt figure} environment to be constructed for inclusion
+of the \PS\ into a \LaTeX\ file.
+
+
+\talk{L'incorporation de graphiques dans
+INRS\TeX}{\nl Michael Ferguson, pp.81--89} The approach used in
+INRS\TeX\ is to use the power of the printer to create
+graphics, and not to introduce special characters. The
+capability to generate graphics has been achieved for \PS,
+and for QMS graphics on a QUIC laser printer. The paper
+discusses the role of the printer as well as the need for
+support software to permit the incorporation of graphics
+produced by other systems. The paper also discusses some
+of the limitations inherent in the choice of graphics
+systems.
+
+\talk{L'environment de production de documents \TeX\ \`a
+l'IRISA}{Philippe Louarn \& Bertrand Decouty, pp.90--95} The group
+consists of over 200 researchers, teachers and engineers,
+who need to produce reports, articles, theses,
+books\dots\ The objective was to provide a set of
+homogenous tools in a heterogenous environment (Unix,
+VMS, workstations, pcs\dots). Naturally, \TeX\ was chosen
+as the fundamental tool. In graphics, the two main
+avenues are through the incorportion of \PS, and by the
+use of {\tt eepic} in the \LaTeX\ picture environment.
+\bigskip\goodbreak
+\leftline{\bf Summaries from Number 3, October 1989:}
+\talk{\TeX\ et les graphiques pour le PC}{Lance Carnes, Chris Bohn, Ian
+Griffin \& Brian Carnes, pp.4--8}% This talk reviews the various graphics
+systems offerings for the IBM pc and compatibles, and the ways these
+systems can be used in conjunction with \TeX; the use of
+\PS, HP PCL and bitmap files in conjunction with current
+\TeX\ drivers; the use of output from screen oriented
+drawing systems; and the conversion of graphics files
+from one format to another, and scaling of images, for
+inclusion in documents.
+\talk{{\ttit texpic}: design and implementation of a
+picture graphics language in \TeX\ \`a la {\ttit pic}}{Rolf
+Olejniczak, pp.9--20} {\tt texpic} is a \TeX\ implementation of a
+graphics language similar to Kerhighan's {\tt troff}
+preprocessor {\tt pic}. The implmentation consists of two
+parts, a set of elaborate \TeX\ macros and a postprocessor
+for drawing (in the {\tt dvi} file). {\tt texpic} objects
+and \TeX\ or \LaTeX\ commands may be combined at will.
+{\tt texpic} is written in C, and is fully portable, to
+the extent that every \TeX\ implementation, every preview
+and every correctly written printer driver will work with
+{\tt texpic}.
+\talk{Un pilote graphique entre le logiciel statistique S et
+\PiCTeX}{Olivier Nicole, pp.21--31}
+INRA replaced its Multics system with \unix. This gave us access to a
+large amount of public domain software, including \TeX, which would
+run on a wide variety of platforms. We evaluated several statistics
+packages, and eventually adopted S. We therefore had a syetem capable
+of typesetting mathematics and a statistics system which met our needs,
+but no way of connecting the two. This paper describes the development
+of a method of combining the two, through \PiCTeX.
+
+
+
+\talk{M\kern-0.2em\lower0.2ex\hbox{A}\kern-0.2emCRO\TeX: Un g\'en\'erateur
+de code \LaTeX\ impl\'e\-ment\'e en MACSYMA}{J Ph Chancelier \& A Sulem,
+pp.32--39} M\kern-0.2em\lower0.2ex\hbox{A}\kern-0.2emCRO\TeX\ is a code
+generator producing \LaTeX\ code form Macsyma, a system for symbolic
+calculus. M\kern-0.2em\lower0.2ex\hbox{A}\kern-0.2emCRO\TeX\ contains
+both translation functions from Macsyma into \LaTeX\ and paper
+generation facilities. So it adds the power of Macsyma to the quality
+of texts exited through \LaTeX.
+M\kern-0.2em\lower0.2ex\hbox{A}\kern-0.2emCRO\TeX\ is written in Common
+Lisp.
+
+
+\talk{Les fiches cuisine d'Onc' \PS: Fiche N$^\circ$2:
+une \'emulateur de table ra\c cante}{Bruno Borghi, pp.66--68}Continues
+the earlier paper to provide an emulation of a pen plotter for OPGL
+(Onc' \PS\ Graphic Language).
+\bigskip\goodbreak
+\leftline{\bf Summaries from Number 4, December
+1989:}
+\talk{Normes et Fontes}{Daniel Dardailler, pp.2--8}
+This article gives an overview of the different
+standards, official or not, which may be met in the
+digital font world. There is an urgent need to
+standardise the whole range of features in this domain,
+from font names through to the type of mathematical
+curves used in representing letter shape. This would help
+make the process of document creation and interchange
+less difficult than they are at present. Four
+main sub-domains are suggested in which standardisation
+is needed: font names and styles; classification into
+e.g.~Latin, Kanji etc; the way the character is formed --
+bitmap, outline; the vocabulary to be used -- what is a
+typeface, a font, etc? Gives an overview of many of the
+standards currently in production.
+
+\talk{M\'etriques des fontes en typographie
+traditionelle} {Jacques Andr\'e, 9--22}
+This paper is a tutorial on font metrics in hot metal. It
+is the first in a series of paper on digital typography.
+Gives the typographical terms used to describe typefaces
+and fonts (noting {\it en passant\/} that the King of
+France's thumb was bigger than that of the King of
+England -- and ultimately accounting for the difference
+between the sizes of the French and English `points').
+Probably holds the record for number of footnotes per
+page (averaging 3!). Many examples, extensive
+bibliography.
+
+\talk{Punk: De \MFsl\ \'a \PS}{Jacques Andr\'e \& Victor
+Ostromoukhov, pp.23--28}
+The Punk font, initially designed by D. Knuth for \MF,
+has been translated into \PS. Thanks to the \PS\ font
+machinery, this new font is more dynamic than the genuine
+one.
+
+\talk{Une meilleure int\'egration du graphisme Macintosh}
+{Laurent Siebebmann, pp.29--38}
+Describes the integration of graphics
+with \TeX\ on the Macintosh, chiefly with \Textures, but also with other
+Mac implementations. Also notes the impact on Sweet-teX,
+and the latest feature of \Textures, allowing export of
+an {\sc epsf} file to, for example, Illustrator.
+
+\talk{\TeX\ 3.0 ou le \TeX\ nouveau va arriver}{Donald E
+Knuth, pp.39--45}
+A french translation of the article in \TUGboat\ 10(3)
+p.325--328.
+
+\rightline{\sl Catherine Griffin \& Malcolm Clark}
diff --git a/info/digests/texline/no10/chris2.tex b/info/digests/texline/no10/chris2.tex
new file mode 100644
index 0000000000..c58805e267
--- /dev/null
+++ b/info/digests/texline/no10/chris2.tex
@@ -0,0 +1,174 @@
+
+%
+% Here is my contribution Malcolm, for TeXline
+% if you think it suitable. I've plain \TeX'ed
+% it upto a point---I didn't fix overfull boxes
+% (there are only two)---and all the macros
+% are from \TeX book. Everything below the line
+% which screams ``HERE'' is needed except for the
+% endgame lines.
+% Everything above is Knuth's
+% chris
+% PS I'll be away until 18 Sep.
+%
+
+%
+% HERE
+%
+{\let\latex\LaTeX
+\let\bibtex\BibTeX
+\def\Makeindex{{\tt make\-index}}
+\def\pagerefs{{\tt page\-refs}}
+\def\awk{{\tt awk}}
+\centerline{\bf Cross Referencing the Bibliography}
+\smallskip
+\leftline{\sl Why cross reference?}
+\noindent
+When you are looking through an article,
+do you wish that
+the bibliography contained cross references to the point
+in the text where the item was cited? I often do, and in this note
+I explain why I find this useful and include a small set of
+\unix\ based tools to accomplish this task quite painlessly
+using \latex\ and \bibtex\ (Patashnik, 1985).
+
+Academic and other sources now publish vast amounts of written
+material. You can't read it all and you have to make some kind
+of judgement as to what you read carefully, what you skim
+quickly and what you ignore. This is especially true in
+academic circles where we are constantly snowed under with journals,
+new journals and conferences, as well as books and
+departmental reports.
+
+One of the first things I look at when trying to judge the
+relevance of an article is its bibliography. I want and expect
+it to be work I have already seen or know
+about. There are several occasions though, when something
+catches your eye about the list of references, and you want to go
+immediately to some particular point of the article:
+
+\item{$\bullet$}
+ Perhaps the article is a survey or tutorial and you
+ want to see how the authors treat your favourite work
+ (or your own!);
+
+\item{$\bullet$}
+ Perhaps there is an intriguing article cited: a paper
+ you have come across in a totally different context
+ and is quite unexpected here. Why is it cited? Or
+ more likely, a paper unknown to you. What is it about?
+
+\item{$\bullet$}
+ Perhaps you wish to refresh your memory about
+ something -- you have come back to this paper looking for
+ specific comments made by the authors concerning some
+ other work. Where do they talk about it?
+
+\noindent
+A bibliography including this kind of cross reference would be
+extremely useful to its readers. You can probably think of lots
+of other examples yourself. Clearly, cross referencing back into
+the text in a book or a thesis can be a great help, but I would
+also stress the advantages of doing the same thing in
+journals accepting long articles and even short reports and
+conference proceedings. In particular, books which are
+collections of articles by several authors and have collected
+bibliographies at the back (or elsewhere!) can benefit greatly
+from such a scheme.
+
+This cross referencing is quite specific to the citation in question.
+You don't have to go hunting through an index for author's names
+which may not give you exactly the right places anyway. Instead
+you get exactly the information you want: where the reference was
+cited. If you forget the authors' names, bibliographies are
+often short enough to scan through to get the right item; In any case,
+what journals and conference proceedings have indexes? Even some (bad)
+books don't have an index.
+\smallskip
+\leftline{\sl Producing the cross references}
+\noindent
+No journals or books that I know of have produced such a
+bibliography. Nevertheless, it's not hard to do so; I have already
+started and I hope others will follow suit. (I'd like to think that the
+conference proceedings and technical reports I find myself reading in
+the future will do so. Maybe even one day the technical journals\dots)
+
+I am going to spend the remaining few paragraphs talking about a
+small program to produce the bibliography in a \latex\
+document. The program is very heavily \unix{}\ biased, and was simply
+thrown together in a few hours, but I hope that
+the ideas are clear enough. It is not really a very difficult problem.
+
+In addition to using \latex, we make use of two other `standard'
+programs: \bibtex\ and \Makeindex. \bibtex\ will of course
+come as no surprise. \Makeindex\ is a program written
+by Pehong Chen at Berkeley, with help from Leslie Lamport,
+and if you are writing a book with \latex, \Makeindex\ is a program you
+must consider using.
+Unfortunately,
+it is, I believe, only written in C and unavailable outside the \unix{}
+world. You will need \Makeindex\ to use my particular implementation.
+If you don't have it I believe it is on the standard \unix{} tape from
+Washington and several archives, including Aston. If you're not on
+\unix, I'm afraid you can't use my implementation anyway because it
+relies on \awk.
+
+The suite consists of:
+\itemitem{1:} a \latex\ style file;
+\itemitem{2:} a preprocessor made from a couple of \awk\ scripts;
+\itemitem{3:} \Makeindex;
+\itemitem{4:} a postprocessor, in C;
+\itemitem{5:} a shell script, \pagerefs, working on 2--4 above.
+
+\noindent\pagerefs\ runs in a manner analogous to \bibtex.
+\bibtex\ must be run first to produce the {\tt .bbl} file,
+and then \pagerefs\ to add the page numbers.
+
+The style file, {\tt pagebib}, simply redefines
+|\cite| to write out the page number
+(but not the |\nocite| command -- it
+didn't seem appropriate). None of this interferes with the
+normal citation methods of \latex.
+
+The style file also defines a command called |\PageBIB|,
+which is used to format the references. My current command is
+\begintt
+\newcommand{\PageBIB}[1]%
+{\hspace*{\fill}\hbox{[#1]}}
+\endtt
+\noindent You can of course redefine it as you please; I flirted with
+the idea of putting the page numbers in marginal notes.
+
+Step~2 simply puts the citations into a suitable form for
+\Makeindex, which does all the hard work. Step~4 relies
+on the fact that the bibliography styles include the bibliographic
+key from the database, (not the label!) in the {\tt bibitem} entry
+which is how citations are matched up with labels. I don't know if
+this is a step \bibtex\ always does but it certainly works for
+the ones I have used -- |alpha|, |plain|, \hbox{|abbrv|},
+|unsrt| and |acm|.
+
+Finally, of course, you must run \latex\ again, but this is only a
+real cost if the last thing you did to your manuscript was to add or
+delete a reference, in which case you will probably run \bibtex\
+again anyway. In the whole scheme of resource usage when writing
+and producing a book or article, this particular part is really rather
+small.
+\smallskip
+\leftline{\sl The bibliography}
+\noindent
+{\frenchspacing\parindent0pt\hangindent20pt\hangafter1
+Alfread~V. Aho, Brian~W. Kernighan, and Peter~J. Weinberger,
+{\awk}: a pattern scanning and processing language, 1978.
+
+\hangindent20pt\hangafter1
+Leslie Lamport,
+Makeindex: an index processor, 1988.
+
+\hangindent20pt\hangafter1
+Oren Patashnik,
+{\bibtex}ing, 1985.
+}
+
+\rightline{\sl Christopher P. Higgins}
+
diff --git a/info/digests/texline/no10/dante.tex b/info/digests/texline/no10/dante.tex
new file mode 100644
index 0000000000..245b9db529
--- /dev/null
+++ b/info/digests/texline/no10/dante.tex
@@ -0,0 +1,88 @@
+\centerline{\bf DANTE meeting, 12--13th October}
+\smallskip
+\noindent
+Eichst\"att is a small university town in Bavaria, a few
+hours' drive from Munich. The one delight in driving
+there from Munich was passing the huge sign in Stuttgart
+which says `Vorsprung durch Technik' (or something
+similar), after many denials from German and English alike
+that this phrase existed, far less meant anything.
+It may not mean anything, but it's good at identifying the
+product. I'm sure there's a moral there for us all. This
+was {\sc dante}'s 10th annual meeting. More accurately, it
+is the tenth annual meeting of German-speaking \TeX\
+users. {\sc dante} itself has only been in existence for
+about a year or so (perhaps longer by the time \TeXline\
+appears!).
+
+The two day meeting adopted the style familiar to many
+other European groups of a teaching\slash training
+session immediately preceding the more general meeting.
+It also had the familiar sight of Lance Carnes. I can't
+remember a European meeting where Lance hasn't turned up
+(usually with his presentation on what's new with Personal
+\TeX).
+
+I'm not going to give more than impressions,
+because my German is too rudimentary to follow things
+very closely (the original plan was to go with Peter
+Abbott, who is fluent in German, but he had other
+commitments). What impressed me? The number of people,
+for a start; I didn't do a head count and there seemed to
+be no list of attendees, but there were easily over 50
+people there, perhaps as many as a hundred. The range of
+people: besides West Germany, Czechoslovakia and Austria
+were represented. The Austrian representation ensured
+that the next {\sc dante} meeting would be in Vienna
+(20--21 March, 1991).
+
+I was a little worried that two German \TeX\ meetings
+so close together (the Karlsruhe meeting was only a
+month previously) would damage both. In the event, I do
+suspect that some might have gone to one rather than
+the other, but that both were reasonably well attended.
+On the other hand, the logic of combining both, with perhaps
+a {\sc dante} day or day-and-a-half seems inescapable.
+Everyone else would get the opportunity to see this group
+in action, and to benefit by their approach to problems
+which beset us all.
+
+As is becoming usual, but is still
+remarkable, there is a wide range of \TeX\ usage:
+commercial, academic and research. I'm less clear about
+the comparative employment of \TeX\ and \LaTeX; that
+didn't come through clearly, and the impressions I formed
+at Eichst\"att were rather different to the ones I had
+formed at Karlsruhe.
+
+There were many familiar faces from
+Karlsruhe, including the irrepresible Christina Detig and
+Joachim Schrod, Klaus Thull (of very public domain \TeX\
+and \MF\ on pc fame), and Joachim Lammarsch and Luzia
+Dietsche (respectively, {\sc dante}'s Chairman and
+Secretary), and one or two presentations familiar from
+Karlsruhe too. There were also many I recognized by name
+and reputation.
+
+Most of the real business seemed to get done in the
+breaks and the evenings (as usual) -- this was helped by
+a reasonable vendors display and the availability of a
+micro to share software. But the talks and presentations
+were the peg on which the whole event could turn. Wolfgang
+Slaby, the local organiser did an admirable and
+well-natured job in taking care of the meeting and its
+participants.
+
+I was lucky to be driven around by a friend who works at
+one of the many Max-Plank Institutes (it's a sort of
+generic term for physical research). I taught her \TeX\ a
+few years ago, and she now uses it exclusively in her
+Institute, also passing on her expertise to the scientific
+staff. She knows about \TeX\ and TUG, but not
+about {\sc dante}. When I told her about {\sc dante}, which she had not heard of
+before, she was slightly intimidated by the idea of a `German-speaking'
+group: all {\it her} reports are in English; what did
+she need (or want) with such a group\dots? More education
+and information needed?
+
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/didot.tex b/info/digests/texline/no10/didot.tex
new file mode 100644
index 0000000000..8b62303ee5
--- /dev/null
+++ b/info/digests/texline/no10/didot.tex
@@ -0,0 +1,150 @@
+\def\blt{$\bullet$}
+\centerline{\bf DIDOT}
+\centerline{\bf European project for training}
+\centerline{\bf in
+numerical typography}
+\smallskip
+\noindent
+The Laboratory of Peripheral Systems of the Polytechnic of Lausanne is
+preparing a project for continual training in digital typography. This
+project seeks to establish a European system for training for typographers
+and artists with a view to enabling them to use new creative tools and for
+computer experts in order to make them competent to create these new tools.
+This training therefore would be carried out by mixing the two groups in
+shared seminars. In fact, the purposes the project are several:
+
+\item{\blt}To prepare a curriculum which would define the type of training
+which
+ would be carried out;
+\item{\blt}To define tools, especially computer-assisted, for this instruction;
+\item{\blt}To organise short duration courses to validate these methods;
+\item{\blt}To anticipate the training of instructors in professional schools.
+\smallskip
+\leftline{\sl Objectives of the project Didot}
+\noindent
+The object of project {\sc Didot} (`Digitalisation and Design of
+Typefaces') is to conceive, to equip and to evaluate a European programme of
+instruction in digital typography for computer experts and graphical arts
+specialists. This area includes not just the creation and use of fonts (and
+more generally logos, drawings, etc.) in printing or for laser printers, but
+also for all sorts of displays, computers, television, etc.,
+tele-distribution, (of which fax. is just a first sketch) their storage
+(CD-ROM, for example) etc. In other words, this sector is an important one,
+even though this is not always recognised.
+\smallskip
+\leftline{\sl Reasons for the project and its origin}
+\noindent
+While the great typographical inventors
+ (Gutenberg, Baskerville, Mergenthaler, Higgonnet and Moyroud, Karow,
+B\'ezier, etc) are European in origin, the market in typefaces has for a
+number of years been in the hands of some American firms. (ITC, Bitstream,
+Adobe, Allied, etc). By a market we mean the market of the artistic creation
+of the font and its `giving it a number' and finally its distribution. The
+ recent font-war (choice of a standard) proves that very adequately.
+ Europe could be better placed in this market thanks to a better
+ knowledge of the new technologies, hence the need for a formation which
+ is `state-of-the-art' and mixed (computer specialists and
+ graphical specialists).
+ Didot is also the
+name of a whole French dynasty of font-engravers, founders, printers or
+booksellers, whose activity spans more than three centuries. The most famous
+are probably Fran\c coise Ambroise Didot (1704--1804) who gave his name to the
+Didot point, a typographical unit still used in most European countries
+and his son Firmin Didot, (1765--1836) who drew `Le Didot'.
+
+The state-of-the-art technology have reached a certain maturity. On
+ the other hand, training in this area remains very localised and
+ Europe remains thus dependent on countries which do not necessarily
+ share its culture.
+
+The modern display interfaces (NeWS, Display \PS) and programs on
+ page printers are based upon derivatives of the page descripion language
+ \PS. It is essential that European industrialists should be
+ capable of developing their own controllers for displays, printers and
+ phototypesetters based upon such a language.
+
+Very soon, all computer and office systems will incorporate extensive
+ typographic possibilities/facilities; it is therefore essential to bring
+ together European typographers, computer specialists and industrialists.
+ This training will permit the exchange of information between teachers
+ and students from diverse industrial academic and artistic backgrounds.
+ It ought to be possible to obtain a very significant synergistic result.
+
+
+
+\smallskip
+\leftline{\sl Types of activities and training be undertaken}
+\noindent
+The principal activities of project {\sc Didot} therefore concern the
+preparation of a curriculum and associated tools. At the same time, training
+will be carried out with a view to validating this program of instruction.
+The types of training to be carried out concern, for example,
+
+\item{\blt}For typographers who create fonts, how to use the new computer
+ tools
+
+\item{\blt}For computer specialists of PME, the bases of classic typography,
+ the computer-based techniques of rasterisation, etc.,
+
+\item{\blt}For specialists in office equipment, (distance distribution,
+ storing CD-ROM, etc) standards and servers for fonts.
+
+\item{\blt}For researchers in typography, how these new technologies
+ enable new developments in typography.
+
+\smallskip
+\leftline{\sl Proposals}
+\noindent
+Project {\sc Didot} therefore proposes:
+\item{\blt}To prepare in collaboration with the PME who are concerned and
+ with typographers and computer experts and researchers who are
+ computer experts in this domain a curriculum; that is to say,
+ to conceive a programme of courses in digital typography
+\item{\blt}To develop tools for this training both CAI tools for teaching
+ in groups and for individuals
+\item{\blt}To validate these tools in training sessions.
+\item{\blt}To train the instructors on the relevant professional courses,
+ e.g art school, high school of graphic art and printing, so
+ that they can instruct their pupils in the new technologies.
+
+\noindent The organisers have already been involved in attempts at training of
+this kind -- the INRIA school `Typography and Computer at Rennes, 1985', and
+Aussois, 1987 `colloquium on digital typography at Sophia-Antipolis (1987)'
+`Raster Imaging and Digital Typography at Lausanne, 1989'. Conference on
+Electronic Publishing at Nice, 1988; as well as many courses of a more
+academic nature at EPFL Lausanne and at the University of Rennes.
+These have always been successful both with PME and with researchers.
+
+
+\smallskip
+\leftline{\sl Results to be obtained}
+\noindent
+\item{\blt}To introduce font designers and logo designers to the new
+ technology, and notably to the use of computer-based systems
+
+\item{\blt}To initiate computer experts in the problems of traditional
+ or digital typography
+
+\item{\blt}To enable European industrialists to acquire the knowlege
+ necessary to develop an \PS-like interpreter and to
+ follow the work of international groups working on standardisation
+
+\item{\blt}To bring about, through the contact of these groups and
+ through the presence of motivated instructors a symbiosis
+ whose indirect fallout ought to be the creation of new tools
+ adapted to meet the true needs of creators and users.
+\smallskip
+\leftline{\sl Input required}
+\noindent
+This project will be presented at the end of February 1990, under the title
+`{\sc Didot}' within the auspices of the Comet-2 programme to the European
+Community.
+
+In order to give it weight, we wish to demonstrate that this indeed
+coresponds to a need both of typopgraphers and of industrialists and
+researchers. We would therefore like to hear from your institution
+telling us what you think of this project. We are at your disposal for
+further information.
+
+\rightline{\sl Jacques Andr\'e \& Roger Hersch}
+\rightline{\sl (translated by Malcolm Smith)}
diff --git a/info/digests/texline/no10/ed.tex b/info/digests/texline/no10/ed.tex
new file mode 100644
index 0000000000..6449c3e340
--- /dev/null
+++ b/info/digests/texline/no10/ed.tex
@@ -0,0 +1,109 @@
+\def\mwc{Malcolm Clark}
+\centerline{\bf Tripping over our own feet}
+\medskip
+\noindent
+How do you know you are using \TeX? What is it about the
+program you are using that makes it \TeX, and not
+something that only looks like \TeX? The answer lies in
+the trip. Each implementation of \TeX\ has to pass the
+trip test. What is the trip test? This is not quite so
+easily answered. The trip test is Knuth's torture test
+which seeks to flex those muscles which are probably best
+never seen: it attempts to verify that the program is
+doing what it is supposed too, out in those marginal
+situations where you can't really understand what the
+fuss is about (`Why would you want to do that anyway?').
+That seems simple enough. But there are some minor
+problems.
+
+First, the trip test is not a static test. With
+practically every bug fix to \TeX\ the trip test is
+extended -- after all, part of the reason for the
+existence of the bug is the inadequacy of the testing (so
+far). So the trip test is updated to bolt the stable
+door. Unfortunately, Knuth has, up to now, not numbered
+or dated the trip tests (a fact he acknowledged at the
+TUG meeting in 1989). You may very well have a \TeX\ which
+passed trip. That does not necessarily mean it will pass
+tomorrow. And who decides when a pass is a pass? The
+output from trip is not a simple `Pass' or `Fail'. It is
+not possible to pump it through a differencing program:
+true, if no differences are found, then you've probably
+passed (or cheated); but some differences are legal, while
+others are not.
+
+
+The criterion of \TeX hood is passing trip: Knuth
+will be pretty upset if you call something \TeX\ when it
+isn't: and ultimately, the AMS (who hold the copyright on
+\TeX, whatever that means exactly) might set legal wheels
+in motion to protect \TeX's integrity. This places some
+pressure on \TeX\ implementors to pass trip. In general,
+the implementor decides whether trip has been passed.
+There appears to be no `regulatory' procedure, or even a
+`certification' procedure. There is no third party to
+whom an implementor can turn to ask to verify that theirs
+is a valid implementation. The AMS don't really want to
+know.
+
+Surely it is time we did something about this? There seem
+to be at least two main issues: the first is to ensure
+that the `current' version of trip can be identified.
+This is presumably in Knuth's hands. But it should not
+be too difficult to add the date to trip. The second
+issue is who decides on a pass? Is verifying a trip test
+really so difficult (one or two implementors have
+expressed the opinion to me that they felt it really was
+difficult, especially for quiche eaters like me)? Whose
+responsibility should it be anyway?
+
+How can a trip pass be verified? I have been advised that
+making the output from trip available is insufficient.
+Some implementors considered that it would be pretty easy
+to cheat. That seems to indicate that someone, somewhere,
+has to be the umpire. I would nominate TUG as the
+`disinterested' verifier.
+
+Obviously there {\it are}
+problems: few others may have access to an equivalent
+machine on which to test the implementation: I see this
+only a problem for mainframe versions. The most critical
+area is surely that of the commercial implementations:
+commercial versions are expected to sell, so they are done
+for machines which are fairly common. This kills two birds
+with one stone: the vendors could pay TUG a nominal sum,
+and in return receive (say) an annual certificate of
+validity (or not). Doing this annually ensures that the
+trip test is re-applied to the software, accounting for
+changes both to trip and the implementation. The vendor
+then has independent verification, the customer does not
+have to depend on the good faith of the vendor (not that I
+make any imputations of any {\it lack\/} of good faith!),
+and TUG may earn some money.
+
+ Perhaps each
+copy of \TeX\ given or sold should have a copy of the trip
+test, but if the output is so difficult to understand, this
+is only going to require an excessive amount of explanation
+on the already overworked implementor. Conformance
+testing should be a background activity, not one which is
+thrust on the users.
+
+Of course, it is not just \TeX\ which has a rigorous test
+to verify its performance. \MF\ has the trap test, and
+the drivers committee has suggested a similar sort of
+testing of device drivers. We need not stop there. What
+about \LaTeX? What about a trip for \LaTeX? Anyone brave
+enough?
+
+Clearly these ideas flow on from my previous editorial on
+`standards'. Until we can really claim that our {\it de
+facto} standards are adhered to (and probably to a far
+higher degree than any ISO standard), we should be
+cautious in proclaiming our integrity too loudly. But it
+must be in all our interests, both in the long and short
+terms, to have some independent arbiter of conformance.
+We really can't leave everything to Don! Give him a
+break.
+
+\rightline{\sl \mwc}
diff --git a/info/digests/texline/no10/ep90.tex b/info/digests/texline/no10/ep90.tex
new file mode 100644
index 0000000000..41fe58983c
--- /dev/null
+++ b/info/digests/texline/no10/ep90.tex
@@ -0,0 +1,44 @@
+\centerline{\bf Electronic Publishing '90}
+\smallskip
+\noindent
+EP90, an international conference on electronic publishing, document manipulation,
+and typography, will be held in mid-September, 1990, in the Washington, DC area
+in Gaithersburg, Maryland on the campus of the National Institute of Standards and
+Technology (formerly the National Bureau of Standards). An associated exhibition
+will provide an opportunity for participants to see commercial and research systems
+in action.
+EP90, {\sl Electronic Publishing '90}, will be the third in
+a series of international conferences established to bring
+together researchers in all areas of electronic publishing
+systems. EP86, held in Nottingham, England, was sponsored
+by the British Computer Society. EP88, held in Nice,
+France, was sponsored by INRIA. The proceedings of papers
+presented at the earlier sessions were published by
+Cambridge University Press and have received wide
+dissemination. The proceedings of EP90 will also be
+published in book form and will be available at the
+conference.
+
+EP90 will adopt a broad definition of `electronic publishing'. Electronic publishing
+will be taken to encompass all aspects of computer-assisted preparation, presentation,
+transmittal, storage, and retrieval of documents. The scope of the conference also
+includes the design of the related computer systems, the design of their components,
+and the theory that underlies such systems. Both linear and non-linear documents
+are appropriate subjects for discussion. While the conference will be principally
+oriented to new ideas and techniques, careful presentation of important earlier
+results inadequately described in the open literature is also appropriate. Papers
+should present previously unpublished original research results and should be supported
+by experience.
+
+Further information may be obtained from:
+{\parindent20pt\obeylines
+Lawrence A Welsch/EP90
+Building 225, Room B252
+National Institute of Standards \& Technology
+Gaithersburg
+MD 20899, USA
+tel: 0101 301 975-3345 (office hours);
+fax: 0101 301 590-0932
+e-mail: {\tt ep90@asl.ncs.nist.gov}
+}
+
diff --git a/info/digests/texline/no10/good_guys.tex b/info/digests/texline/no10/good_guys.tex
new file mode 100644
index 0000000000..33fae7b0ac
--- /dev/null
+++ b/info/digests/texline/no10/good_guys.tex
@@ -0,0 +1,110 @@
+\centerline{\bf The good guys}
+\def\address#1={\goodbreak\vskip8ptplus2pt\goodbreak\parindent0pt%
+\hbox{\hfuzz40pt\hsize3.1truein\vbox{#1}}}
+{\obeylines
+\address
+Konrad Neuwirth
+Fernkorngasse 44-2-4
+A-1100 Wien, Austria
+email: {\tt a4422dae@awiuni11.bitnet}
+=\address
+{Christopher P. Higgins}
+{Department of Computer Science,}
+{University of York,}
+{York, YO1 5DD, UK}
+{email: {\tt chris@uk.ac.york.minster}}
+=\address
+Carol~Hewlett
+Computer Service
+London School of Economics
+Houghton Street
+London, WC2A~2AE, UK
+email: {\tt hewlett@uk.ac.lse}
+=\address
+David Penfold
+Edgerton Publishing Services
+30 Edgerton Road
+Edgerton
+Huddersfield HD3 3AD, UK
+0484 519462
+=\address
+Victor Eijkhout
+Department of Mathematics
+University of Nijmegen
+Toernooiveld 5
+6525 ED Nijmegen, the Netherlands
+email: {\tt u641000@hnykun11}
+=\address
+John Feltham
+ Open University
+Walton Hall
+Milton Keynes
+ Bucks MK7 6AA, UK
+=\address
+ Dieter Gogolin
+ Tools GmbH
+ Kessenicher Str. 108
+ FRG-5300 Bonn 1
+ e-mail: {\tt tex@tools.uucp}
+=\address
+Jacques Andr\'e
+INRIA, Campus de Beaulieu,
+F-35042 Rennes cedex, France
+=\address
+Roger Hersch
+INF-LSP
+Ecole Polytechnique F\'ed\'erale
+CH-1015 Lausanne, Switzerland
+=\address
+Jan Michael Rynning
+Dept Numerical Analysis \& Computing Science
+Royal Institute of Technology
+S-100~44 Stockholm , Sweden
+email: {\tt jmr@nada.kth.se} or {\tt jmr@sekth}
+=\address
+Chris Rowley
+Parsifal College
+Open University
+527 Finchley Road
+London NW3 7BG, UK
+email: {\tt c\_rowley@ou.acs}
+=
+\address
+Rosemary Bailey
+Statistics Department
+Rothamsted Experimental Station
+Harpenden, Herts
+AL5 2JQ, UK
+email: {\tt rbailey@afrc.resb}
+=
+\address
+Catherine Griffin
+Oxford University Computer Centre
+13 Banbury Road
+Oxford OX2 6NN, UK
+email: {\tt catherine@uk.ac.oxford.vax}
+=
+\address
+David Rhead
+Cripps Computing Centre
+Nottingham University
+Nottingham N57 2RD, UK
+email: {\tt cczdgr@nottingham.ccc.vax}
+=
+\address
+Barbara Beeton
+AMS
+PO Box 6248
+Providence, RI 02940, USA
+email: {\tt bnb@seed.ams.edu}
+=
+\address
+Adrian Clark
+Dept Electronic Systems Engineering
+Essex University
+Wivenhoe Park
+Colchester
+Essex CO4 3SQ, UK
+email: {\tt alien@uk.ac.essex.ese}
+=
+}
diff --git a/info/digests/texline/no10/groningen.tex b/info/digests/texline/no10/groningen.tex
new file mode 100644
index 0000000000..a2c970bda6
--- /dev/null
+++ b/info/digests/texline/no10/groningen.tex
@@ -0,0 +1,29 @@
+\centerline{\bf SGML \& \TeX\ Conference}
+\medskip
+\noindent
+This conference, organized by the {\sl Nedelandstalige \TeX\
+Gebruikersgroep\/} (the Dutch-speaking \TeX\ Users Group) and the \sgml\
+Holland Users Group, will be held at the University of Groningen
+on August 31st, 1990.
+
+The conference will focus on the relationship between \TeX\ and \sgml, now and
+in the future. It is proposed to run two parallel streams of presentations.
+There will be demonstrations by vendors, a book stall, and copying facilities
+for public domain \TeX\ and \sgml\ software. The conference language is Dutch,
+but speakers are urged to have their transparencies in English (non-natives are
+supposed to speak English).
+
+\TeX, \LaTeX, \MF\ and \sgml\ courses will be arranged around the conference.
+Members of any \sgml\ or \TeX\ Uers Group are charged {\sl f\,}75,--- for the
+conference; non-members are charged {\sl f\,}150,---.
+
+For further information contact:
+{\obeylines\parindent20pt
+C G van der Laan
+RekenCentrum RijksUniversteit Groningen
+Landleven 1
+9700 AV
+050-633374 Groningen
+the Netherlands
+email: {\tt cgl@rug.nl}
+}
diff --git a/info/digests/texline/no10/meetings.tex b/info/digests/texline/no10/meetings.tex
new file mode 100644
index 0000000000..9e264d68c3
--- /dev/null
+++ b/info/digests/texline/no10/meetings.tex
@@ -0,0 +1,294 @@
+\centerline{\bf TUG10 \& \TeX89: edited highlights}
+\smallskip
+\noindent
+With big meetings like these it is difficult to provide a
+blow by blow account of all the papers. In any case, the
+proceedings of both meetings are (or will be) available
+shortly. The proceedings of TUG10 are available as
+\TUGboat\ 10(4), and \TeX89 should be out ``{\it real
+soon}''. \TeX89 had one or two unscheduled additions, but
+these too may turn up in the proceedings.
+\smallskip
+\leftline{\sl TUG10}
+\leftline{\sl Stanford University, August
+20--23rd}
+\noindent
+TUG10 was easily the biggest TUG meeting ever held --
+hardly surprising when it was an anniversary meeting, at
+Stanford, and with Don Knuth in attendance. Kodak ought
+to have subsidised the meeting. The clicking of cameras
+was a familiar background noise to Don's every
+public movement. There was a good European turnout, which
+may have contributed to the remarkable change of heart
+experienced by \DeK. After five years of stability, \TeX\
+is to change. It is difficult to know just what went on
+to convince Don of the need for this -- after all, there
+have been repeated suggestions made over the last ten
+years for changes (some of which surfaced in
+\TeX82), but two factors are known. The first was \DeK's
+trip to Norway a year or so ago, where he experienced at
+first hand a few of the problems created by `foreign'
+languages, and visited on \TeX; the second major factor
+must be the duo of Roswitha Graham and Jan Michael
+Rynning, who spend a {\it lot\/} of time with Don very
+early on in the meeting. The essence of their argument is
+presented elsewhere in \TeXline. I have my suspicion
+that personality played a role, as well as argument.
+Fortunately \DeK\ did not agree to wholescale changes
+(`creeping featurism' as he later described it). The
+majority of the changes are designed to enhance \TeX's
+multilingual capability, although some concessions were
+made to make the job of page makeup a hint or two easier
+(or even `a hint or two less difficult'!).
+The details of these changes are in \TUGboat\ 10(3).
+
+In addition to these changes to \TeX, \LaTeX\ seems set
+to change too, although in not particularly radical ways.
+The initiative to embark on this particular evolution seems
+largely due to Frank Mittelbach and Rainer Sch\"opf (who
+seem to write most of \TUGboat\ these days). Frank won
+the Knuth scholarship for his work on \LaTeX.
+
+Since it was an anniversary meeting, everyone was there
+-- well, not quite true, but it was possible to verify
+that the following existed: Mike Spivak, Leslie Lamport,
+Jill Knuth, Max D\'\i az, Arthur Keller, David Fuchs,
+Neenie Billawalla\dots -- many of the names that you see
+hidden somewhere in an essential Stanford report on
+some aspect of \TeX ware. A rogues gallery might have
+saved the rest of us the discomfort of peering at
+badges and saying `Oh, so you're\dots'. Of course they
+all thought I was Malcolm {\it Brown}, so they thought I
+had done a grand job and were pleased to see me too (for
+the email-deficient, Malcolm Brown started the {\tt
+texhax} listings in their present form).
+
+Stanford is a very pleasant campus, although the grass is
+very noisily cut and trimmed. The building in which the
+conference took place is now propped up after the
+earthquake, although still intact. It has a covered area
+around it which made it possible to have registration and
+administrative details dealt with just outside, although
+under cover. The crazy Brits who had never seen sun
+before were all doing their No\"el Coward `heat of the mid
+day sun' impersonations during the breaks.
+
+There was also an exhibition room with various \TeX ware
+distributors and developers. Phil Taylor claims that
+Kinch was giving Turbo\TeX\ away, but this must have only
+been to selected attendees -- I didn't see it. One of the
+highlights might have been a laser printer which
+understands \dvi, but it was held up in customs. By now
+it may be at TUG headquarters in Providence.
+
+If I have a criticism of the meeting, it was with the
+difficulty in fitting in impromptu meetings: practically
+every hour was packed with eating, conferencing,
+partying, socialising\dots\ My lunch times were further
+occupied with TUG Board meetings. Ah, the Board meetings.
+Catapulted into one of these it is difficult to get a
+grasp of what is really going on. Most of the Board are
+appointees (I started out as a European coordinator
+appointee, but now I'm a member by virtue of being
+Chairman of uk\TeX ug -- the UK \TeX\ Users Group). I'm a
+bit wary about this appointee stuff: it's not really the
+weft from which democracy was woven, but as a
+representative of `mad King George' in the land of the
+free, it's not really my place to educate them about
+democracy, is it? On the other hand, if the French
+haven't excellent credentials in this area, who have? Go
+to it Bernard Gaulle! (President of GUTenberg, and now
+also a Board member). Back to my criticism: it really was
+quite difficult to manage other informal meetings
+unless you were prepared to schedule time after
+midnight or before breakfast (same thing I
+suppose). Some `bird's of a feather' meetings did get of
+the ground towards the end of the conference.
+
+During the conference we `elected' a new President
+(Nelson Beebe) and Secretary (Cal Jackson). I hadn't
+realised the extent to which electoral systems differed.
+We English speakers have this illusion that just because
+we can communicate with Americans without too much
+confusion, and because their pol\-itical system grew out of
+the 18th century English system, that we're basically
+similar. Wrong. When we're described
+as `aliens' we should reflect on it and realise that we
+are indeed on another planet. There is no point
+trying to understand US electoral systems from a European
+stance.
+
+Although I won't mention every paper, one or two stand
+out for one reason or another: \DeK's paper on the
+`Errors of \TeX' was scheduled for about three hours.
+That in itself would have been memorable. It was actually
+a very entertaining and stimulating paper which
+catalogued all the errors which \DeK\ had encountered in
+the writing and testing of \TeX. He had categorised them
+and began to draw inferences on the whole subject of
+programming. On this evidence, `zero defect' software
+doesn't seem very likely. Even Knuth repeated some errors.
+What chance do the rest of us have?
+
+There were good papers and not so good papers -- but the
+quality is not the sole yardstick. Presenting papers
+serves to identify people and is an essential part of the
+communication process. Perhaps the format of the TUG
+meeting discourages the little `isn't this interesting'
+paper -- the ones I tend to find most useful -- and
+focusses on `standard-length' papers: this often means
+spinning out material beyond its breaking point.
+
+There was one notable innovation -- the inclusion of an
+extra half day on \MF, at the beginning of the
+conference. Doug Henderson's `Introduction to \MF' was
+amazing as he discovered the supreme difficulty of giving
+a live demo to an audience much larger than anticipated.
+
+As the papers will show, \TeX\ continues to expand into
+new areas and several participants discussed the ways in
+which word processing packages could be employed as the
+first stage in the \TeX\ `publishing' process. I would be
+dishonest if I didn't say that I felt this to be largely
+misdirected. We are still ready to accept the myth that
+\TeX\ is inherently difficult. As someone who finds
+getting out of WordPerfect in one piece really
+mind-bogglingly bizarre and arcane, \TeX\ seems easy as
+cake. Equally, few of the word processing proponents seem
+to have cottoned on to \LaTeX. \LaTeX\ actually makes
+life very easy for the so called naive user. We still
+seem to want to teach people to change font rather than
+to {\it emphasize\/}. I won't claim that \LaTeX\ is
+unequivocally excellent typographically, but it's a great
+deal better than your typist turned typesetter who still
+insists on underlining, double spacing and all the other
+gross indeciencies of typewriting.
+As a sort of antidote, there were also several papers on
+the high quality end of typesetting.
+
+There were no parallel sessions (a great relief) and few
+last minute changes to the programme. As I've obliquely
+mentioned above, one of the key aspects of any conference
+is the social side. After all, the papers will likely all
+be written up one day, but the people you meet are the real
+gems of any conference. Since a large proportion of the
+participants were housed in the same block of residences
+(and my, they do have a spartan time at Stanford!) it was
+very easy to meet and mingle in the quadrangle (despite
+the limited time to do so!). If the conference seemed to
+run itself painlessly and effortlessly it was because the
+irrepressible Charlotte Laurendeau was skilfully joining
+the ends together, papering over the cracks and holding us
+all together.
+
+Will there be another meeting at Stanford? An interesting
+question. TUG meetings have been more mobile over the
+last few years -- Tufts, Montreal, \TeX as. This is a
+trend I would like to see continue (perhaps the 25th
+anniversary should come back to Stanford!), but there may
+be a danger that every meeting has to be bigger (and by
+definition, better), which would tend to encourage
+conservatism. If we look at the distance individual
+participants come for the conference, there are many who
+come from the `local' area. By taking the conference
+around North America it makes it easier for local \TeX
+ies to participate.
+\medskip
+\leftline{\sl Euro\TeX89}
+\leftline{\sl Karlsruhe, September 11--13th}
+\noindent
+\TeX89, or Euro\TeX89 as it seemed to call itself was
+truly European, but the participation from the US was
+encouraging too. Since the meeting was held in Karlsruhe
+there was a major German participation, and perhaps half
+of the papers were from the Germany-speaking world.
+Perhaps the most worrying feature was the relative lack of
+French participation. Perhaps the success of GUTenberg is
+siphoning off French attendees. This would be a great
+pity. But the success of the `national' or `language'
+groups may soon mean that the European meeting will suffer
+as a result.
+
+One or two papers resurfaced from TUG10. I'm afraid I
+agreed to rehash my own `Olde Worlde \TeX' (which I had
+rather hashed at Stanford -- I forgot that most of my
+audience didn't actually know where the Old World --
+Europe -- was); Peter Abbott gave his talk on the Aston
+Archive again, Rolf Olejniczak talked about {\tt texpic}
+(although it does have more features each time I hear
+about it) and Don Hosek talked about designing oriental
+characters with \MF. This was also the first run of Chris
+Rowley's now familiar talk on `What Don said at Stanford'.
+The replay of these papers is useful, since the talk
+evolves, and the audience was very, very, different
+(different planet, see above).
+
+It would be a bit invidious to pick best papers, but
+Mittelbach \& Sch\"opf's `With \LaTeX\ into the Nineties'
+(another refugee from Stanford, but for a different
+reason) clearly has much wider significance. It is a huge
+relief to see the baton of \LaTeX\ taken up by these two
+enormously capable, energetic and earnest enthusiasts. I
+had heard from `usually reliable sources' that Leslie
+Lamport had expected \LaTeX\ to die a natural death
+-- `replacing the dinosaur with a small furry mammal'.
+It looks as if this dinosaur has a good few millenia in
+it yet, and may even evolve into a small furry dinosaur
+of its own volition. (Where do we
+get the idea that dinosaurs weren't fit to survive? They
+lasted a longer than we are likely to.)
+
+Marek Ry\'cko and Bogus\l aw Jackowski's paper on Polish
+\TeX\ (or \LeX, for all sorts of reasons) was another
+taste of the future. The impact of \TeX\ in Eastern
+Europe is growing. The platform (of necessity rather than
+choice) is the pc; hard currency is still difficult to
+obtain, but public domain \TeX\ and drivers make it an
+ideal tool for one of the key components of
+liberalisation -- a printing press in the hands of the
+people. (Another aside: when I was in Warsaw Marek and I
+had an interview with the advisor to the Minister for
+Culture about using \TeX\ more widely\dots). Marek won
+the prize for `best paper'. I was particularly pleased by
+this.
+
+Anne Br\"uggeman-Klein's paper was, as expected
+thoughtful and showed \TeX's great potential, as well as
+many of the problems in `designing' documents. Standards
+cropped up; first through David Rodgers talk, stressing
+CALS, and then through Martin Bryan's `J\LaTeX' which
+showed an application which started life as an \sgml\
+document.
+
+One other harbinger of the future might be Konrad
+Neuwirth: not only was he talking about one of the nicest
+personal \TeX\ implementations -- on the Amiga -- but he
+was easily the youngest participant.
+
+There was a good exhibition area with lots of vendors
+(and even a peripatetic Stanford t-shirt salesperson -- I
+hadn't realised that tie-dye was still around).
+
+One interesting feature of the meeting was the
+publication of the wall-news\-paper, `Backslash'. This
+scurrilous example of the gutter press mysteriously
+appeared each morning. Since we're in the business of
+document preparation, it is surprising that this has not
+happened at \TeX\ conferences before. It certainly lent a
+(spurious) air of immediacy and incredibility to the
+proceedings.
+
+In summary, another useful contribution to the spread of
+\TeX\ knowledge and expertise. Again, apparently
+painlessly run, and with some very fine social events.
+The organisers, Anne Br\"uggeman-Klein and Rainer
+Rupprecht deserve much praise for this worthy successor
+to \TeX88. I keenly believe that the European \TeX\
+conferences are essential for the long term viability of
+\TeX, TUG and \TeX-in-Europe. Without these meetings, and
+without participation from the whole European catchment
+we will all be a great deal poorer. I look forward to more
+meetings like this one, but in Warsaw, in Budapest, in
+Moscow (and, if liberalisation continues, perhaps once
+again in the UK).
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/new.tex b/info/digests/texline/no10/new.tex
new file mode 100644
index 0000000000..b641917393
--- /dev/null
+++ b/info/digests/texline/no10/new.tex
@@ -0,0 +1,116 @@
+\font\eightsy=cmsy8
+\skewchar\eightsy='60\def\LamSTeX{L\kern-.4em\raise.3ex\hbox{$\scriptstyle\cal
+A$}\kern-.25em
+\lower.4ex\hbox{\eightsy M}\kern-.1em{$\cal S$}-\TeX}
+\let\LAmSTeX\LamSTeX
+\def\proggy#1{{\sc#1}}
+\def\|#1|{{\tt#1}}
+\def\cmd#1{{\tt\char`\\#1}}
+\centerline{\bf What's New with \TeX?}
+\smallskip
+\noindent At the 10th Anniversary meeting at Stanford last summer,
+when Knuth hoped to `wrap up' his involvement with \TeX, the
+non-native English-speaking contingent, mostly from Europe, persuaded
+him to embark on one final set of enhancements, to support eight-bit
+character sets and multi-lingual typesetting. This gave rise to \TeX\
+2.993, which mutated into \TeX~3.0 in late March~1990.
+The main changes are:
+
+\noindent\hbox {\bf 1.~Character Set}: Up to 256 distinct characters are
+now allowed in input files.
+
+\noindent\hbox {\bf 2.~Hyphenation Tables}: \TeX\ now supports up to 256
+hyphenation tables. There is a new integer parameter called
+\cmd{language}, whose value specifies the hyphenation to use.
+
+\noindent\hbox {\bf 3.~Hyphenated Fragment Control}: The new version has
+parameters called \cmd{lefthyphenmin} and \cmd{righthyphenmin} which
+specify the smallest number of letters which may be at the beginning
+or end of a word to be hyphenated.
+
+\noindent\hbox {\bf 4.~Better Ligatures}: The major changes concern
+ligatures, although one must modify the \MF\ sources of fonts to take
+advantage of all of them. The new version supports more complex
+ligature constructions then the old, allows two ligatures to share
+common code, and introduces `invisible' boundary characters at the
+beginnings and ends of words which allow the first or last character
+to be changed.
+
+\noindent\hbox {\bf~5. Better-Looking Sloppiness}: In the past, a common
+way to avoid overfull boxes was to set \cmd{tolerance=10000}, which
+resulted in \TeX\ concentrating all the badness in one truly awful
+line. A new parameter, \cmd{emergencystretch} has been introduced to
+combat this. If it is set to a positive value and \TeX\ is unable to
+typeset a paragraph without exceeding the given tolerances, another
+pass is made through the paragraph in which an amount of stretch equal
+to \cmd{emergencystretch} is present in every line.
+
+\noindent\hbox {\bf~6. Miscellany}: There are new parameters called
+\cmd{badness}, which records the badness of the box most recently
+constructed, and \cmd{inputlineno}, defined as `the number of
+the line that \TeX\ would show on an error message if an error
+occurred now.' It is also possible to set the maximum number of lines
+of context information output in an error message -- a useful feature
+for large macro packages like \LaTeX. Finally, there is a new
+parameter called \cmd{holdinginserts} which inhibits \TeX\ from
+inserting insertions when building pages; this feature is primarily of
+interest to designers of output routines who wish to break up and
+re-build the current page.
+
+\smallskip
+ These changes also affect \MF\ (the ligature changes) and
+\proggy{tangle} (\proggy{pool} files). However, Knuth has also made
+a few improvements and bug-fixes to some of the other parts of the
+\TeX\ family. The latest versions of all the important programs are:
+
+\centerline{\vbox{%
+\halign {#\quad\hfil & #\hfil &\qquad #\quad\hfil & #\hfil\cr
+ \TeX & 3.0 &
+ \MF & 2.0 \cr
+ \proggy{tangle} & 4.0 &
+ \proggy{weave} & 4.1 \cr
+ \proggy{VFtoVP} & 1.0 &
+ \proggy{VPtoVF} & 1.0 \cr
+ \proggy{GFtoDVI} & 3.0 &
+ \proggy{GFtoPK} & 2.2 \cr
+ \proggy{GFtype} & 3.0 &
+ \proggy{PKtype} & 2.2 \cr
+ \proggy{DVItype} & 3.2 &
+ \proggy{PLtoTF} & 3.2 \cr
+ \proggy{TFtoPL} & 3.1 \cr
+}}}
+\smallskip
+At the same time as he implemented the above changes to \TeX, Knuth
+also devised {\it virtual fonts.\/} These are composite fonts, built
+up of characters extracted from existing fonts. This makes it
+possible to merge, say, a printer-resident \PS\ font
+for most characters while pulling characters missing from it (e.g.,
+upper-case Greek) from a down-loaded Computer Modern font. (This
+example is for illustration only -- this composite would actually be
+very ugly!) \TeX\ itself sees only one font, but the device driver
+(and perhaps also the printer) would take characters from the two
+fonts as required. One driver, derived from one of the
+\dvi--\PS\ converters, has also been modified by Knuth
+to support virtual fonts. There are new programs, \proggy{VFtoVP} and
+\proggy{VPtoVF}, which are analogous to \proggy{TFtoPL} and
+\proggy{PLtoTF} respectively.
+
+Another significant event at the 10th Anniversary meeting was the
+cessation of Leslie Lamport's development of \LaTeX. Future
+development will be undertaken by a committee led by Frank Mittlebach,
+who has already done significant work on \LaTeX's font-loading
+mechanism and on a more flexible multicolumn style.
+
+Two separate attempts are being made to combine the facilities of
+\LaTeX\ and \AmSTeX. One of these is taking place under the auspices
+of the American Mathematical Society, the AMS. The other, \LAmSTeX, available
+now, is a commercial product by
+Mike Spivak, author of \AmSTeX.
+
+On the font front, the AMS have produced new \MF\ descriptions of
+their extended symbol fonts, which include blackboard bold and many
+useful (and some weird!) mathematical symbols. The \MF\ sources are
+not in the public domain, but I believe the AMS plans to release {\tfm} and
+{\pk} files at some point.
+
+\rightline{\sl Adrian Clark}
diff --git a/info/digests/texline/no10/newtwo.tex b/info/digests/texline/no10/newtwo.tex
new file mode 100644
index 0000000000..f9971c26b0
--- /dev/null
+++ b/info/digests/texline/no10/newtwo.tex
@@ -0,0 +1,166 @@
+
+%\hoffset=-0.1in
+%\voffset=-2pc
+%\raggedbottom
+%\hsize=39pc %\vsize=59pc
+%\maxdepth=2.2pt \parindent=1pc
+%\vsize=720pt
+%\hsize=6.5in
+%\baselineskip12pt
+%\parskip0pt
+%\parindent1em
+%\hfuzz1.5pt
+%\tolerance2000
+
+%\hyphenation{Post-Script}
+% Page layout
+\newdimen\pagewidth \newdimen\pageheight \newdimen\ruleht
+\newdimen\colwidth \newdimen\bigcolheight\newdimen\gutter
+\gutter=0.3in%better as 0.4in
+%\colwidth=3.1in%19pc
+\colwidth=\hsize
+\advance\colwidth by-\gutter
+\divide\colwidth by 2\relax
+%\bigcolheight=1450pt%120pc
+\bigcolheight=\vsize
+\advance\bigcolheight by\bigcolheight
+\advance\bigcolheight by 10pt
+\pagewidth=\hsize \pageheight=\vsize \ruleht=.5pt
+\abovedisplayskip=6pt plus 3pt minus 1pt
+\belowdisplayskip=6pt plus 3pt minus 1pt
+\abovedisplayshortskip=0pt plus 3pt
+\belowdisplayshortskip=4pt plus 3pt
+
+\newinsert\botins
+\def\afoot{\strut\egroup}
+\def\botpic#1{\par
+ \insert\botins\bgroup\hsize=\pagewidth
+ \offinterlineskip
+ \interlinepenalty100 \let\par=\endgraf
+ \leftskip=0pt \rightskip=0pt
+ \splittopskip=10pt plus 1pt minus 1pt \floatingpenalty=20000
+ \medskip{#1}\medskip\egroup}
+\skip\botins=12pt plus 2pt minus 4pt % space added when footnote is present
+\count\botins=2000 % footnote magnification factor (1 to 1)
+\dimen\botins=36pc % maximum footnotes per page
+
+\def\toppic#1{\par
+ \insert\topins\bgroup\hsize=\pagewidth
+ \interlinepenalty100 \let\par=\endgraf
+ \offinterlineskip
+ \leftskip=0pt \rightskip=0pt
+ \splittopskip=10pt plus 1pt minus 1pt \floatingpenalty=20000
+ \medskip{#1}\medskip\egroup}
+\skip\topins=12pt plus 2pt minus 4pt % space added when footnote is present
+\count\topins=2000 % footnote magnification factor (1 to 1)
+\dimen\topins=36pc % maximum footnotes per page
+
+\newinsert\margin
+\dimen\margin=\maxdimen
+%\count\margin=0 \skip\margin=0pt % marginal inserts take up no space
+
+\newif\iftitle
+\def\titlepage{\global\titletrue} % for pages without headlines
+%\def\rhead{{}}
+
+\def\leftheadline{\hbox to \pagewidth{%
+ \vbox to 10pt{}% strut to position the baseline
+ \sl\rhead\hfil\lhead % running head flush left
+ }}
+\def\rightheadline{\hbox to \pagewidth{%
+ \vbox to 10pt{}% strut to position the baseline
+ \sl\rhead\hfil\lhead % running head flush left
+ }}
+
+\def\onepageout#1{\shipout\vbox{ % here we define one page of output
+ \offinterlineskip % butt the boxes together
+ \vbox to 2pc{ % this part goes on top of the 44pc pages
+ \iftitle % the next is used for title pages
+ \global\titlefalse % reset the titlepage switch
+ \setcornerrules % for camera alignment
+ \else\ifodd\pageno \rightheadline\else\leftheadline\fi\fi
+ \vfill} % this completes the \vbox to 3pc
+ \vbox to \pageheight{
+ \ifvoid\margin\else % marginal info is present
+ \rlap{\kern31pc\vbox to 0pt{\kern4pt\box\margin \vss}}\fi
+ \ifvoid\topins\else % top note info is present
+ %\hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \unvbox\topins
+ \vskip\skip\topins \kern-3pt
+ %\hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \vskip\skip\topins \kern-3pt
+ \fi
+ #1 % now insert the main information
+ \vfill
+ \ifvoid\botins\else % bot note info is present
+ \vskip\skip\botins \kern-3pt
+ %\hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \unvbox\botins
+ \vskip\skip\botins \kern-3pt
+ %\hrule height\ruleht width\pagewidth \kern-\ruleht \kern3pt
+ \fi
+ \boxmaxdepth=\maxdepth
+ } % this completes the \vbox to \pageheight
+ }
+ \advancepageno}
+
+\def\setcornerrules{\hbox to \pagewidth{\vrule width 1pc height\ruleht
+ \hfil \vrule width 1pc}
+ \hbox to \pagewidth{\llap{\sevenrm(page \folio)\kern1pc}%
+ \vrule height1pc width\ruleht depth 0pt
+ \hfil \vrule width\ruleht depth 0pt}}
+
+\output{\onepageout{\unvbox255}}
+
+\newbox\partialpage
+\newdimen\savesize
+\def\begindoublecolumns{\begingroup
+ \savesize=\vsize
+ \output={\global\setbox\partialpage=\vbox{\unvbox255\bigskip}}\eject
+ \output={\doublecolumnout} \hsize=\colwidth \vsize=\bigcolheight
+ \advance\vsize by -2\ht\partialpage
+ \advance\vsize by -2\ht\botins
+ \advance\vsize by -2\ht\topins
+ \pagegoal=\vsize}
+\def\enddoublecolumns{\output={\balancecolumns}\eject
+ \global\output={\onepageout{\unvbox255}}
+ \global\vsize=\savesize
+ \endgroup \pagegoal=\vsize}
+
+\def\doublecolumnout{%
+% \splitmaxdepth=\maxdepth
+ \dimen0=\pageheight
+ \advance\dimen0 by-\ht\partialpage
+ \advance\dimen0 by-\ht\botins
+ \advance\dimen0 by-\ht\topins
+ \splittopskip=\topskip
+ \setbox0=\vsplit255 to\dimen0
+ \setbox2=\vsplit255 to\dimen0
+ \onepageout\pagesofar
+ \global\vsize=\bigcolheight
+ \unvbox255 \penalty\outputpenalty}
+\def\pagesofar{\unvbox\partialpage
+ \wd0=\hsize \wd2=\hsize \hbox to\pagewidth{\box0\hfil\box2}}
+\def\balancecolumns{\setbox0=\vbox{\unvbox255} \dimen0=\ht0
+ \advance\dimen0 by\topskip \advance\dimen0 by-\baselineskip
+ \divide\dimen0 by2 \splittopskip=\topskip
+ {\vbadness=10000 \loop \global\setbox3=\copy0
+ \global\setbox1=\vsplit3 to\dimen0
+ \ifdim\ht3>\dimen0 \global\advance\dimen0 by1pt \repeat}
+ \setbox0=\vbox to\dimen0{\unvbox1}
+ \setbox2=\vbox to\dimen0
+% {\unvbox3}
+ {\dimen2=\dp3 \unvbox3 \kern-\dimen2 \vfil}
+ \global\output={\balancingerror}
+ \pagesofar}
+\newhelp\balerrhelp{Please change the page into one that works.}
+\def\balancingerror{\errhelp=\balerrhelp
+ \errmessage{Page can't be balanced}
+ \onepageout{\unvbox255}}
+
+
+
+
+
+
+
diff --git a/info/digests/texline/no10/nordic.tex b/info/digests/texline/no10/nordic.tex
new file mode 100644
index 0000000000..6de5842dc2
--- /dev/null
+++ b/info/digests/texline/no10/nordic.tex
@@ -0,0 +1,417 @@
+\def\proposal{\smallskip\noindent{\sl Proposal:\/\enspace}}
+\def\ssection#1{\par\noindent{\sl#1:}\enspace}
+\def\MLTeX{Multilingual T\kern-.1667em\lower.5ex\hbox{\^E}\kern-.125emX}
+\def\JTeX{\lower.5ex\hbox{J}\kern-.1667em\TeX}
+\def\TeXXeT{\TeX-X\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT}
+\def\command#1{{\tt\char`\\#1}}
+\def\cite#1{}
+\def\caption#1{\centerline{#1}}
+\frame{5pt}{%
+\noindent
+The following contribution has some of the characteristics
+of a historical document. It is essentially the paper which
+Jan Michael took to Stanford and with which contsind
+the details of the arguments with which he and
+Roswitha Graham so ably and persistently bent the ear of Don
+Knuth -- with the outcome that after many years of stability,
+\TeX\ is changing.}
+\medskip
+\centerline{\bf Proposal to the TUG Meeting at Stanford}
+\medskip
+\noindent
+Donald Knuth created \TeX\
+to typeset American text interspersed with mathematical
+formulas. Apart from a few limitations \TeX\ has also
+proved suitable for typesetting other languages. Most
+limitations have been overcome by modifying the \TeX\
+program itself (\MLTeX, \JTeX, \TeXXeT\dots),
+creating new fonts (Devan\=agar\=\i,
+Hebrew\dots), and modifying the
+existing ones (Icelandic Modern\dots).
+While covering the requirements of one or more
+specific languages these modifications have created
+compatibility problems. \TeX\ input files may require
+features which are only available in certain extended
+versions of \TeX, or {\DVI} output
+files may not print correctly unless you make non-standard
+modifications to the device drivers. The only way to solve
+these problems is put the necessary capabilities into the
+standard version of \TeX.
+
+In this paper I describe the
+problems of typesetting the Nordic languages with the
+current version of \TeX, and propose modifications to the
+\TeX\ program itself, the standard fonts, and macro
+packages, which will solve the problems. Most of the ideas
+concerning hyphenation come from Michael Ferguson's
+\MLTeX, which solves some of the problems in that area, but
+not all. I also include a proposal for modifications to
+macro packages (\LaTeX\dots), in
+order to support the use of the language of your own
+choice. It originates from a proposal by Hubert Partl, approved by the German
+\TeX\ users group. In spite of the fact that I have
+restricted myself to the Nordic languages, the proposals
+that I put forward will also be useful for a large number
+of other languages. All the modifications proposed in this
+paper may be carried out in a backward compatible way, that
+will not influence the use of \TeX\ unless you decide to
+use the added capabilities.
+
+This list of proposals was first discussed at the Nordic \TeX\ meeting
+in Stockholm in June 1989, and followed up by discussions through
+electronic mail. Among those people who presented suggestions and
+critique on my original proposal were Staffan Romberger, Peter Busk
+Laursen, Bruce Wolman, Simen Gaure, Heikki Heikkil\"a, Bo Thid\'e,
+and Bernard Gaulle. I apologize if I
+left anyone out of this list. I also want to express my gratitude to
+Roswitha Graham, who arranged the Nordic \TeX\ meeting, and whose
+encouragement has been of invaluable help to me.
+
+\smallskip
+\leftline{\sl Introduction}
+\noindent
+The Nordic problems with \TeX\ may be divided into:
+\item{\rtr} typesetting text in the Nordic languages
+\item{\rtr} using our own words, date formats, etc., instead of the American
+ones hard wired into some macro packages (\LaTeX\dots)
+\item{\rtr} using our national letters in macro names, etc.
+
+The last-mentioned is of minor importance, so I set it aside, and
+concentrate on the typesetting. To avoid the confusion that may arise
+from using different character sets and handling at the various stages
+of \TeX's typesetting process, I have further subdivided this group of
+problems into:
+
+\item{\rtr} input of national letters
+\item{\rtr} internal handling of national letters and words
+\item{\rtr} output of typeset national letters
+
+\smallskip
+\centerline{\vbox{\halign{#&&\quad\hfil#\hfil\cr
+\multispan2{Code}&{\sc ascii}&Sw/Fi&Da/No\cr
+91&&\tt[&\tt\"A&\tt\AE\cr
+92&&\tt\char`\\&\tt\"O&\tt\O\cr
+93&&\tt]&\tt\AA&\tt\AA\cr
+123&&\tt\char`\{&\tt\"a&\tt\ae\cr
+124&&\tt \char'174&\tt\"o&\tt\o\cr
+125&&\tt\char`\}&\tt\aa&\tt\aa\cr
+}}}
+\caption{Nordic 7-bit national characters.}
+
+\smallskip
+\leftline{\sl Input of national letters}
+\ssection{7-bit national characters}
+ISO 646 \cite{iso:646} ({\sc ascii} is the U.S.\ national character set based
+on ISO 646) reserves character codes 64, 91--94, 96, and 123--126 for
+`national or application use'. Unfortunately, three of these codes
+are used both for
+important functions in \TeX, and for important national letters in
+the Swedish, Finnish, Danish, and Norwegian national character sets.
+
+Nordic users expect to be able to use their national letters on their
+national keyboards, just like any other letter. Hence, on computers
+with 7-bit character codes or where \TeX\ will only accept 7-bit input
+we have had to remap \TeX's escape and group delimiter characters, for
+national use.
+\smallskip
+\centerline{\vbox{\halign{#\hfil&&\quad\hfil#\hfil\cr
+Function&{\sc ascii}&Sw/Fi/Da/No\cr
+Escape character&\tt\char`\\&{\tt/}\quad or\quad {\tt!}\cr
+Begin group&\tt\char`\{&\tt<\cr
+End group&\tt\char`\}&\tt>\cr
+}}}\caption{Nordic 7-bit \TeX\ remapping.}
+\smallskip
+The only real problem with this, apart from us being incompatible, is
+that the \command{write} command uses the begin group and end group
+characters in force when a macro was defined, not the ones in force
+when the \command{write} command is executed.
+
+\proposal
+Add a \command{bgroupchar} and an \command{egroupchar} (\TeX\
+already has an \command{escapechar}).
+
+\ssection{8-bit extended {\sc ascii} characters}
+Some implementations of \TeX\ running on computers with 8-bit extended
+{\sc ascii} character sets discard the 8th bit of the character code, silently
+converting characters with codes 128--255 (usually including European
+national letters) to other characters. This is both confusing to the
+users (who have these letters on their keyboards, and expect them to
+work in \TeX, just like in any other program), and not very useful.
+
+\proposal
+Make character codes 128--255 permanently active on computers with 8-bit
+extended {\sc ascii} character sets. This will make it possible to redefine
+them to do something sensible, or lead to an `Undefined control
+sequence' error if they have not been defined. As more and more
+computers get such character sets, this should be part of the \TeX\
+standard. On computers with an {\sc ebcdic} character set, the character
+codes which don't correspond to {\sc ascii} characters should be mapped to
+128--255, and made active.
+\smallskip
+\leftline{\sl Internal handling of national letters and words}
+\ssection{Hyphenating words with accented letters}
+\DeK\ restrained \TeX\ from hyphenating words with accented
+letters, as those words are foreign to American and probably won't
+hyphenate correctly anyway. When using \TeX\ for typesetting languages
+which use accented letters (with the appropriate patterns) this
+restriction has been worked around by creating non-standard versions of
+\TeX\ (like \MLTeX) or non-standard fonts.
+
+\proposal
+Make \TeX\ accept accented letters in \command{patterns} and
+\command{hyphenation}. This will make it possible to use the
+standard version of \TeX, and the standard fonts to typeset text in other
+languages than American, using the built-in hyphenation.
+
+\smallskip
+\ssection{Don't use shifted boxes for national letters}
+\TeX\ (the macros in {\tt plain}, used with the Computer Modern fonts) uses
+shifted boxes for some national letters (\AA, \L, \c c\dots).
+This makes \TeX\ dependent on the metrics of the Computer Modern fonts,
+and it won't work with the above-mentioned hyphenation.
+
+\proposal
+Put national letters into the fonts or use \command{accent} to construct
+them. Use the same method for the uppercase and lowercase version of the
+same letter. Assign the appropriate \command{lccode} to each national
+letter put into the fonts, so that words with these letters may be
+hyphenated.
+
+\smallskip
+\ssection{Multilingual hyphenation}
+\TeX\ only supports one set of hyphenation patterns and exceptions.
+
+\proposal
+Make it possible to have multiple sets, and to switch between them,
+so \TeX\ may easily be used for multilingual typesetting.
+
+\smallskip
+\ssection{Variable suppression of hyphens}
+\TeX\ will never insert a hyphen that has fewer than 2 letters before it
+or fewer than 3 letters after it. These values are not suitable for all
+needs.
+
+\proposal
+Make the number of letters required before and after an inserted hyphen
+settable parameters. Either generate all patterns so that these parameters
+can be set to their minimum values (both 1), or add information to the
+patterns about the values used when they were generated, and restrict \TeX\
+from setting the parameters to smaller values than that.
+
+\smallskip
+\ssection{Allow hyphenation of words with explicit hyphens}
+Some languages have very long words with explicit hyphens. Normally \TeX\
+will refuse to hyphenate these words, though they are perfectly hyphenatable
+and must often be hyphenated.
+
+\proposal
+Make it possible to turn off this `feature', so that words with explicit
+hyphens may be hyphenated.
+
+\smallskip
+\ssection{Discretionary hyphens in patterns and exceptions}
+Some languages (Swedish, German, and probably some more) have
+words that require \command{discretionary} hyphenation.
+\TeX\ does not allow for this in \command{patterns} and \command{hyphenation}.
+
+\proposal
+Make \TeX\ accept \command{discretionary} hyphenation, both in
+\command{patterns} and in \command{hyphenation}, and
+make the corresponding changes to {\tt PATGEN}. It might be tempting to refer
+these words to the exception mechanism, but since it is possible to form
+an almost unlimited number of compound words and inflection forms that
+require \command{discretionary}, I think they are best handled by adding
+`hyphenation rules' to the hyphenation patterns. The
+basic rule, the only one \TeX\ knows of at the moment, is
+\command{discretionary\char`\{-\char`\}\char`\{\char`\}\char`\{\char`\}}.
+The German rule that `ck' is written as `k-k' when
+hyphenated, may be described by
+\command{discretionary\char`\{k-\char`\}\char`\{\char`\}\char`\{c\char`\}},
+and the triple consonant suppression (for example, `tt'
+turns into `tt-t' in some words, because one of the t's was
+suppressed), takes a few more rules like
+\command{discretionary\char`\{t-\char`\}\char`\{\char`\}\char`\{\char`\}},
+for a handful of consonants that may occur at such
+positions. The rules should be read into \TeX\ with the
+patterns, and the number of the rule to be applied at a
+certain position should be stored together with the odd
+interletter value at that position.\looseness1
+
+\smallskip
+\ssection{Log hyphenations for proof-reading}
+No matter how good the hyphenation is, there will always be words which
+are not correctly hyphenated. In languages where compound words are
+frequent, more words tend to be incorrectly hyphenated. It may therefore
+be necessary to proof-read the hyphenations. As even a minimal change
+may cause a lot of hyphenations to change, all hyphenations may have to
+be proof-read after every change, unless there is a way to detect which
+hyphenations have changed.
+
+\proposal
+Make it possible to log hyphenations, e.g.\ by adding a
+\command{tracinghyphenations}. This will facilitate the proof-reading
+of hyphenations, and make it possible to write a program which finds
+the hyphenations that have changed.
+
+
+\smallskip
+\leftline{\sl Output of typeset national characters}
+\ssection{Full Latin character set}
+\TeX\ is capable of typesetting most letters used in Latin
+scripts, using the macros in {\tt plain} and the Computer
+Modern fonts. The following letters and accents in ISO
+6937/2 \cite{iso:6937/2} (which is a superset of the ISO
+8859/1, 2, 3, and 4 character sets) cannot be typeset that
+way: Icelandic {\em Thorn/thorn} and {\em Eth/eth}, Lapp
+{\em Eng/eng} and {\em T/t~with stroke}, Maltese {\em
+H/h~with stroke}, Croat and Lapp {\em D/d~with stroke},
+Catalan {\em L/l~with middle dot}, Greenlandic {\em k~with
+short stem}, and the {\em ogonek accent}, used in Polish
+and Lithuanian. A few more letters and accents used in
+Latin scripts may be found in ISO/DP 10646\cite{iso:10646}.
+
+
+The baseline quotation marks (,,), required for Icelandic and German
+typesetting, and the guillemots (similar to $\ll$ and $\gg$), required
+for French typesetting, and occasionally used for typesetting the Nordic
+languages, are also missing from Computer Modern.
+
+\proposal
+Extend \TeX's Latin fonts so that they contain all of the letters,
+accents, quotation marks, currency symbols and other graphic symbols needed
+to typeset languages written with a Latin script.
+Of the 234 letters in ISO 6937/2 (counting both upper and lower case),
+155 may be formed from a basic letter and a diacritical mark. Therefore,
+only 13 accents and 25 special letter forms need to be in the fonts.
+
+\smallskip
+\ssection{Placement of accents}
+\TeX's accent placement algorithm does not place all
+accents correctly\cite{romberger:texlatin}.
+
+\proposal
+Extend the {\tfm} format, so that \TeX\ may:
+
+\item{\rtr} use the current algorithm
+\item{\rtr} use an explicit accent placement with respect to the base letter,
+instead of the one calculated by the algorithm
+\item{\rtr} use an explicit accent placement for accent-letter pairs not
+handled by the above-mentioned method
+\item{\rtr} use specially designed accented letters as replacements for
+accent-letter pairs
+
+
+\smallskip\goodbreak
+\ssection{Kern accented letters, too}
+\TeX\ performs no implicit kerning between two letters if the second is
+accented. In most cases, the result would look better if the letters
+were kerned.
+
+\proposal
+Make \TeX\ insert implicit kerns between letters without regard to if they
+are accented, or design an algorithm which takes both the basic letter and
+the accent into consideration when inserting implicit kerns.
+
+\smallskip
+\leftline{\sl Macro packages}
+\noindent
+Several macro packages (like the \LaTeX\ style files) contain American words,
+date formats, etc., which should be replaced by the corresponding words and
+date formats from the language used in the text, when using another language.
+Thus, the heading `Contents' should be changed to
+`Inneh\aa ll' in Swedish, `Inhalt' in German, etc.
+
+\proposal
+Define macros for all occurences of American words, date formats, etc.\ in
+macro packages, so that they can easily be replaced, e.g.\ by
+redefining those macros in a style file.
+
+\smallskip
+\leftline{\sl Conclusion}
+\noindent
+The problems of typesetting the Nordic
+languages with the current version of \TeX\ have been decribed, together with proposed
+modifications to the \TeX, the Computer Modern fonts, and macro packages,
+which should solve the problems. This may serve as a basis
+for further discussions aimed at a European proposal. The changes needed may then,
+ be incorporated into a standard version of \TeX.
+
+\smallskip
+\leftline{\sl Bibliography}
+{\frenchspacing\parindent0pt\hangindent20pt\hangafter1
+Michael Ferguson,
+{\sl A \MLTeX},
+\TUGboat, 6(2), 1985, pp57--58.
+
+\hangindent20pt\hangafter1
+Michael Ferguson,
+{\sl\MLTeX\ Update},
+\TUGboat, 7(1), 1986, p16.
+
+\hangindent20pt\hangafter1
+ISO, {\sl ISO 646: ISO 7-bit coded character set for
+information interchange},
+ 1983.
+
+\hangindent20pt\hangafter1
+ISO,
+{\sl ISO 6937/2: Coded character sets for text
+communication -- Part 2: Latin alphabetic and
+non-alphabetic characters}, 1983.
+
+\hangindent20pt\hangafter1
+ISO,
+{\sl ISO\slash DP 10646: Multiple octet coded character set},
+1989.
+
+\hangindent20pt\hangafter1
+Donald~E. Knuth,
+{\sl The \TeX book},
+Addison Wesley, Reading, Massachusetts, 1986.
+
+\hangindent20pt\hangafter1
+Donald~E. Knuth,
+{\sl\TeX: The Program},
+Addison Wesley, Reading, Massachusetts, 1986.
+
+\hangindent20pt\hangafter1
+Donald~E.\ Knuth and Pierre MacKay,
+{\sl Mixing right-to-left texts with left-to-right texts},
+\TUGboat, 8(1), 1987, pp.\ 14--25.
+
+\hangindent20pt\hangafter1
+Leslie Lamport,
+{\sl\LaTeXsl: A Document Preparation System},
+Addison Wesley, Reading, Massachusetts, 1986.
+
+\hangindent20pt\hangafter1
+Hubert Partl,
+{\sl German \TeX},
+\TUGboat, 9(1), 1988, pp70--72.
+
+\hangindent20pt\hangafter1
+Hubert Partl {\it et al},
+{\ttit german.sty}
+
+\hangindent20pt\hangafter1
+Staffan Romberger and Yngve Sundblad,
+{\sl
+Adapting \TeX\ to Languages that use Latin Alphabetic
+Characters}, Proceedings of the First
+European Conference on \TeX\ for Scientific Documentation,
+Addison Wesley, Reading, Massachusetts, 1985.
+
+\hangindent20pt\hangafter1
+Yasuki Saito,
+{\sl Report on \JTeX: A Japanese \TeX},
+\TUGboat, 8(2), 1987, pp.\ 103--116.
+
+\hangindent20pt\hangafter1
+Dominik Wujastyk.
+{\sl The Many Faces of \TeX: A Survey of Digital \MFsl},
+\TUGboat, 9(2), 1988, pp.\ 131--151. {\sl see also}
+\TeXline\ 8.
+
+}
+
+\rightline{\sl Jan Michael Rynning}
diff --git a/info/digests/texline/no10/orin.tex b/info/digests/texline/no10/orin.tex
new file mode 100644
index 0000000000..4c9c3d8649
--- /dev/null
+++ b/info/digests/texline/no10/orin.tex
@@ -0,0 +1,17 @@
+\centerline{\bf Another \BbiBTeX\ feature}
+\medskip
+\noindent
+Oren Patashnik has finally finished his
+dissertation and is now working on \BibTeX\ 1.0. Although he does not
+want to be deluged with requests for new features, he is
+concerned that he may have missed some things that are important to
+European users of \BibTeX. He is also interested in hearing about any
+bugs that may still be present in the code. If anyone has anything to
+say about either concern, I am preparing a summary of the things
+already mentioned in UK\TeX, TEX-NL and GUT (Oren already watches \TeXhax) to
+send to him, and will be happy to include other information. Or you
+could send your comments directly to him:
+\begintt
+opbibtex@Neon.Stanford.EDU
+\endtt
+\rightline{\sl Barbara Beeton}
diff --git a/info/digests/texline/no10/ou.tex b/info/digests/texline/no10/ou.tex
new file mode 100644
index 0000000000..2a78637b26
--- /dev/null
+++ b/info/digests/texline/no10/ou.tex
@@ -0,0 +1,83 @@
+\centerline{\bf Publishing at the OU}
+\smallskip
+\noindent
+This first one-day meeting that the BCS
+Electronic Publishing Specialist Group had held outside
+London, at least within `living memory', was held at The
+Open University on September 28th and organized by Paul
+Bacsich.
+
+Most of the speakers were from the Open University, Peter Hammersley from
+Middlesex Polytechnic being the only `outsider' as the other external
+speaker had to withdraw shortly before the meeting. Nonetheless it was a
+very interesting day, made even more interesting by the related
+demonstrations which ran through the breaks in the day. While
+demonstrations by manufacturers are welcome and helpful, those by people
+using equipment to carry out real tasks are often more revealing.
+
+After the formal welcomes, the first speaker was John Feltham who gave the
+rationale for investing in high-end EP, in particular the
+`CAPS' system used by the OU, which runs under \unix\ on
+SUN workstations. Advantages include the multi-user
+facility, the greater speed of operation and the greater
+power of the software. PC- and Mac-based systems do not
+provide the formatting facilities which CAPS provides and
+although output from Microsoft Word direct to the
+typesetter is a possibility, the macro and style-sheet
+facilities of CAPS provide a way of imposing uniform
+procedures and styles where required with an output quality
+of professional standards.
+
+Chris Rowley and Bob Coates talked about the other approach at the OU,
+that of using \TeX{}, to produce mathematical and technical
+documents. The advantages include the facility for the users to see what
+the final typeset output will look like at every stage, as well as all
+the other advantages of \TeX{}, which are probably familiar to
+readers of \TeXline. The OU have five keyboarders who spend
+at least some of their time on \TeX{} and 6000 pages a
+year are output, almost entirely at 300\,dpi.
+\LaTeX{} is used for input.
+
+Paul Bacsich and Robin Kydd described the use of Microsoft Word Rich Text Format
+(RTF) as a generic coding language. The use of style sheets defined using
+RTF avoids the use of direct formatting by keyboarders (which can produce
+disastrous results when translated to the CAPS system). The disadvantage of
+RTF is that it is essentially linear and has no depth. When translated for
+the CAPS system, the paragraph styles are only taken as name and number
+(that is, the actual MS style sheet is ignored), while at
+the character level the actual coding is translated, for
+example, italic and bold and sorts characters. Robin Kydd
+described the problems involved in the translation process,
+particularly those involving tables, lists and symbols, and
+finished by suggesting that more generality was needed and
+this tended in the direction of \sgml.
+
+Peter Hammersley's talk followed on very appositely as he discussed some of
+the problems involved in translating from MS-Word into Ventura. The project
+was the very practical one of producing a book of conference papers. The
+papers were in the main submitted electronically and then tagged.
+\hbox{Peter} described both 1988 when tags were added using
+the Ventura editor which was very tedious and difficult, and
+1989 when the tags were put in using MS-Word, which was
+easier. However, translation into Ventura produced some
+strange effects, which Peter accepted could be explained
+and even by-passed, but his point was that the naive user
+of such packages would find these effects a
+serious problem.
+
+Finally Paul Lefrere discussed table design. He pointed out that within
+standard packages such as Ventura, MS-Word and even CAPS tables can be very
+hard to produce to the specification required. He analysed what could be
+done with the various packages (and with a specialized package
+`TableTools') and how long these operations can take, that
+is, how cost effective the different packages can be. The
+high-end packages, not surprisingly, come out better than
+the standard DTP packages, but TableTools was definitely
+the winner in terms of value for money, being relatively
+cheap.
+
+The meeting was well attended and discussions indicated that those
+attending found it of interest. That it was actually on site made it that
+much more so.
+
+\rightline{\sl David Penfold}
diff --git a/info/digests/texline/no10/rose.tex b/info/digests/texline/no10/rose.tex
new file mode 100644
index 0000000000..2f706e2f84
--- /dev/null
+++ b/info/digests/texline/no10/rose.tex
@@ -0,0 +1,56 @@
+\let\BiBTeX\BibTeX
+\centerline{\bf \TeX89\ looks at \LaTeXbf\ tools}
+\smallskip\noindent
+Several discussion and `birds of a feather' groups were organised at the
+Karlsruhe \TeX89 meeting. Our discussion group considered indexing and
+bibliographies. We were in fair agreement over indexing. At the moment
+neither |makeindex| nor |makeidx| works on a PC for a document long enough to
+need an index: PC versions are needed. Other desirable enhancements include:
+international language support (such as \"a if |german.sty| has been used);
+options to specify how to alphabetize in languages where there is more than one
+convention (for example, there are three possible positions for \"a in German);
+certain constants to be made bigger; user's choice of delimiter characters, as
+with |\verb|. Other complaints apply more generally to software being passed
+around the \TeX\ community: it should be written in lines of no more than 72
+characters (because of email problems); only a very standard subset of C should
+be used; the authors should be accessible. A wish-list was prepared, which
+will be sent to the authors of |makeindex| and |makeidx| if we can find them.
+
+There was much less consensus over what is currently possible or easy in
+\BiBTeX\ and what are reasonable enhancements to ask for. Clearly, some people
+like programming in reverse Polish while others seem to find it extraordinarily
+difficult. We did agree that it would be useful to have matters as the ordering
+of the items, the type of key used, the ordering of words within the items, and
+the language used for words like `edition', could be easily changed
+independently. International language support is also needed.
+
+Although we agreed that all standard fields should be pre-declared in standard
+\BiBTeX, so that everyone uses them in the same way, we did not agree on what
+we thought was standard. Each of the following was supported by at least one
+person in the group: ISBN number; price of book; title of author, such as `Dr'
+or `S J'; `contribution to discussion of Important Paper X by J Smith' -- but
+are any of these really that standard? This led on to a discussion of whether
+it was really sensible to use \BiBTeX\ as a database, in which case it needs a
+front end to help secretaries input the entries (Anne Br\"uggemann-Klein has
+written one), or whether it is better to use an established database and get it
+to write |.bib| files (my preference).
+
+Our course, getting \BiBTeX\ to be all things to all people also involves making
+|\cite| more flexible. For some journals, |\cite| needs to put the title in a
+footnote on the first occurrence only; for others, it must put the author(s)
+and year in the text, but with punctuation depending on whether one is already
+inside parentheses; for yet others, if a book is cited only once the cited page
+number(s) must go in the bibliography rather than the text. Is it reasonable to
+be able to expect any usable program to be able to do all this? To my mind,
+having an editable |.bbl| file is a huge plus.
+
+Anne Br\"uggemann-Klein agreed to compile a wish-list and send it to Oren
+Patashnik before he finishes his current work on \BiBTeX. I hope we do not give
+the impression that we are not grateful for what has already been done.
+Although many people in the group sounded indignant that \BiBTeX\ would not
+do exactly what they wanted, it seems to me to be such an improvement over
+both `doing it yourself' (Lamport, Section 4.3.1) and using generic commands
+like |\writer| and |\paper|, defined in each style-file (cf. Spivak, Appendix B)
+that I, for one, am simply delighted that I have \BiBTeX.
+
+\rightline{\sl Rosemary Bailey}
diff --git a/info/digests/texline/no10/rowley.tex b/info/digests/texline/no10/rowley.tex
new file mode 100644
index 0000000000..16aeed1b78
--- /dev/null
+++ b/info/digests/texline/no10/rowley.tex
@@ -0,0 +1,44 @@
+\centerline{\bf Too many braces take a belting}
+\smallskip
+\noindent
+For some good reason, which now escapes, I had cause recently to look
+something up in number 7 of this series; thus proving that it is fulfilling its
+destiny as a standard work of reference. As I was browsing through my eye
+lighted on the review of a software package called Formulator. The exact
+nature of this package is of no consequence to my remarks but its pertinent
+property is that it produces `software-written' \TeX\ code for, as the name
+suggests, mathematical formulas. The reviewer points out that it has a
+number of eccentricities in its use of braces: for example, a tendency to
+surround many subformulas with unnecessary braces but to omit them in some
+places where they are essential. The problems caused by the latter are
+explained in some detail, as is one change in the expected typography caused
+by the insertion of an empty pair of braces. The rest are categorized as `No
+bad thing'.
+
+I would argue that all such extra braces are not simply superfluous but are
+possible causes of incorrect typesetting of a nature which is particularly
+disturbing in a system which is presumably aimed at a class of user who is
+less likely than some to notice these errors since they largely affect those
+details of spacing in formulas of which most readers and producers of
+mathematical texts are blissfully unaware.
+
+The cause of the errors occasioned by these braces is the fact that any
+subformula enclosed in braces (even an empty one) is an atom of type
+(flavour) Ord (see p.\ 291 of {\sl The \TeX book}) whatever its contents may
+be. Thus, choosing examples at random from the review: |{\left( ... \right)}|
+appears to the neighbouring atoms to be an Ord instead of its correct
+identity which is Inner; |{\int ...}|, |{\sum ...}| and |{\sin ...}| all change
+from Op to Ord. A glance at the table on p.\ 270 of {\sl The \TeX book\/} will
+reveal the havoc which such changes can wreak to the subtleties of spacing
+revealed therein.
+
+Thus I am led to the conclusion that either the code-writing part of this
+software contains a fundamental design flaw or this software is not intended
+to produce high-quality \TeX-code and is therefore not intended for use in
+high-quality typesetting software.
+
+Of course, it is just possible that it is merely another piece of evidence in
+favour of the thesis that the \wysiwyg\slash Graphical Interface\slash {\sc
+wimp} paradigm is fundamentally at odds with high-quality anything.
+
+\rightline{\sl Chris Rowley}
diff --git a/info/digests/texline/no10/sgml.tex b/info/digests/texline/no10/sgml.tex
new file mode 100644
index 0000000000..3da450a3da
--- /dev/null
+++ b/info/digests/texline/no10/sgml.tex
@@ -0,0 +1,74 @@
+\centerline{\bf SGML Soldiers On}
+\smallskip
+\noindent
+It is reassuring to know that the cold war still lives on
+in these days of glasnost. At Mark-Up '89 held in Gmunden,
+Austria in April we were treated to young, glamorous and
+very earnest women reassuring us that \sgml{} would ensure
+that the free world remained free thanks to the
+combat-readiness of the tanks, cruise missiles and
+destroyers and their accompanying truck loads of
+documentation.
+
+It is apparent that \sgml{} afficionados can be divided
+into two distinct groups, the theorists and the
+pragmatists. I have to say that it was this last group
+that made the conference worth attending. This
+latter group, could be further sub-divided into the
+militarists and the commercial publishers and printers. To
+a great extent, the DoD suppliers have to use \sgml{}
+and its terrible progeny CALS whether they like it or
+not; their main aim is to find an easy way around the
+problem. The now famous Taft memo stating that CALS had to
+be used for all DoD contracts was widely discussed. (The
+ultimate print-buyers revenge?). As a user of a GenCode
+based system (CAPS) I made it my task to search out the
+{\sl voluntary\/} fellow sufferers and I was particularly
+interested to hear their experiences. As usual, the Dutch
+were there in force. I generally regard them as being
+pretty well ahead of the game in Europe and I must say it
+came as a bit of a shock to me to find that many of them
+were still taking {\sc ascii} text and adding their own
+mark-up to it. In the UK there are some encouraging signs
+with at least one other publisher/printer (besides the OU)
+developing an MS Word to \sgml{} program.
+
+Elegant conversion from the authoring word processing program to \sgml{} is still very
+much the missing link. Avalanche Technologies have gone some of the way to solving
+it with FastTag which I believe is the XGML parser that is also used by DocuPro
+and ArborText. To my mind a `visual' system of hierarchy
+recognition misses out a lot of the subtleties of anything
+other than simple text.
+
+There certainly seems to be no shortage of `conventional' \sgml{} parsers available
+at a price, Sobemap's Mark-It and Yuri Rubinsky's SoftQuad being two notable examples.
+These both work as stand-alone word processors and would be great if you could persuade
+all your authors to use one.
+
+Xyvision and Interleaf both gave demonstrations of their \sgml{} front-ends. Interleaf's
+was very neat but again it presupposed that the author was the person on the Interleaf
+keyboard. Doubtless it could take in ready-made \sgml{}. In terms of major installed
+gencode based publishing systems Compugraphic with CAPS was noticeable by their
+absence.
+
+This conference was significant because for the first time people were able to report
+back on the results of actually using \sgml{} in competitive environments. The Oxford
+English Dictionary was offered up as an example of main-stream publishers using
+\sgml{} which makes a lot of sense when you consider updating and multi-media presentations.
+On the military side concern was expressed at how the number of standard DTDs was
+growing on a daily basis (they originally thought they would only need 3 or 4) and
+secondly at the amount of time it took to write a DTD. Noises were made about months
+rather than weeks.
+
+The other worry voiced by the militarists was that of retro-fitting \sgml{}/CALS to
+existing documentation. How was it to be done and who was going to pay for it?
+
+I have to confess that I found the discussions by the theoreticians on standards
+dry to the point of excruciating as well as a slight annoyance that they were apparently
+failing to recognize the amount of hard work being undertaken by users in order
+to breathe life into these standards. But I did come away from the meeting feeling
+that \sgml{} was actually being used by real people. When the conference comes to Europe
+again in two years time I believe that we will see that \sgml{} has progressed significantly
+across all EP applications.
+
+\rightline{\sl John Feltham}
diff --git a/info/digests/texline/no10/talk.tex b/info/digests/texline/no10/talk.tex
new file mode 100644
index 0000000000..5dad0e02ea
--- /dev/null
+++ b/info/digests/texline/no10/talk.tex
@@ -0,0 +1,854 @@
+\overfullrule0pt
+\def\\{\hfil\break}
+\font\ttt=cmtt10
+\def\tt{\ttt\hyphenpenalty10000}
+\def\subsection#1{\leftline{\let\sc\scit\sl #1}\par\noindent\ignorespaces}
+
+\let\subsubsection\subsection
+\def\BibTeXi{B{\iteight IB}\kern-.2em\TeX}
+\font\sb=cmbx8
+\def\BbiBTeX{B{\sb IB}\kern-.2em\TeX}
+\hyphenation{abbrv}
+
+\centerline{\bf Towards \BbiBTeX\ style-files that implement}
+\centerline{\bf principal standards}
+\section{1: Introduction}
+\BibTeX\ can relieve an author of a lot of the work that is
+traditionally involved in compiling a list of references. The
+public domain bibliography style-files certainly produce neat
+bibliographies.
+
+However, documents often have to conform to a house style, to the conventions
+within a subject, or to an externally defined standard. \BibTeX\ users may
+not always be working in the same subject areas as \BibTeX's originators.
+This article considers the extent to which \BibTeX\ and the public domain
+style files are suited to this more exacting task.
+
+\section{2: Standard conventions}
+% Recall what speaker (a) said about the standard conventions [2 mins]
+% (reference-by-number, author-date)
+`Reading between the lines' of the \LaTeX\ manual suggests to me that
+the main influences behind the \LaTeX/\BibTeX\ scheme for
+classifying bibliographic references were van Leunen's book (van Leunen, 1978),
+and the precedent set by {\it Scribe}.
+
+However, I have the impression that the `principal standards' for
+citations and bibliographies are generally those defined by Butcher's book
+(Butcher, 1981), the relevant British Standards
+(BSI, 1989; BSI, 1983; BSI, 1978),
+and the {`Chicago Manual of Style'} (Chicago Manual of Style, 1982), rather
+than van Leunen's and {\it Scribe\/}'s conventions.
+
+
+
+This impression derives partly from the numbers of times that I've seen
+citations of the works concerned. I've only seen van Leunen cited by
+the \LaTeX\ manual, whereas
+Butcher's book is cited by Hart (1983), BSI (1988),
+Chicago Manual of Style (1982) and Williamson (1983);
+the British Standards are cited by BSI (1988), Butcher (1981),
+ McLean (1980) and Williamson (1983);
+the {`Chicago Manual of Style'} is cited by Butcher (1981),
+ Turabian (1987), Williamson (1983) and Lamport (1986), and
+ forms part of the `instructions for authors' for the journal
+ {\it Electronic publishing: origination, dissemination \& design}.
+BS 1629 also seems to correspond to an ISO standard.
+More parochially, the British Standards are mentioned in various Nottingham
+University guidelines about theses and dissertations.
+
+Therefore, it seems more important to help authors
+conform to the recommendations of Butcher's book,
+the British Standards and the {`Chicago Manual of Style'}, than to
+help them conform to van Leunen's recommendations and the {\it Scribe}
+precedent. This may involve supporting the author-date
+(`Chicago Manual of Style', 1982; BSI, 1978; Butcher, 1981),
+reference-by-number (BSI, 1978; Butcher, 1981)
+and short-title schemes (Butcher, 1981).
+There is also an author-number system (Butcher, 1981), but it does not
+seem to be used much.
+
+
+
+\caption{Table 1: BS~1629(1976)/6371 entry types compared with
+\BbiBTeX's}\smallskip
+\def\hline{\noalign{\hrule}}
+\tabskip0pt\halign
+{\offinterlineskip\strut\vrule\enspace\tabskip=0.5em#\hfil&#\hfil&\tabskip0pt#\hfil\tabskip0pt\vrule\cr
+\hline Category & Subcategory & Nearest \BibTeX \cr
+ & & entry-type \cr
+\hline
+Book & Single-vol. work & {\tt book}, {\tt booklet}, \cr
+or other & & {\tt manual} or \cr
+separately & & {\tt proceedings} \cr
+issued & Multi-vol. work & {\tt book} \cr
+publication & British Standard & {\tt techreport} \cr
+ & Technical report & {\tt techreport} \cr
+ & Translation & \cr
+ & Govt. publicn. & \cr
+\hline
+Portion of & & {\tt inbook}, \cr
+above, other & & {\tt incollection}, \cr
+than sep. & & {\tt inproceedings} \cr
+contribution & & \cr
+\hline
+Periodical or & Periodical as & \cr
+other serial & a whole. & \cr
+publication & & \cr
+ & Limited run or & \cr
+ & specific vol. & \cr
+ & or issue & \cr
+\hline
+Article or & in book or\dots & {\tt incollection}, \cr
+contribution & & {\tt inproceedings} \cr
+ &in periodical\dots& {\tt article} \cr
+\hline
+Patent & Patentee and & \cr
+ & inventor & \cr
+ & & \cr
+ & Patentee only & {\tt techreport} \cr
+\hline
+Unpublished & & {\tt booklet}, \cr
+ & & {\tt mastersthesis},\cr
+ & & {\tt phdthesis}, \cr
+ & & {\tt misc} \cr
+\hline
+}
+
+\section{3: Assumptions and abbreviations}
+The remainder of this article will assume that the conventions
+described in Butcher's book,
+the British Standards and the {`Chicago Manual of Style'} are indeed the
+`principal standards', and that the \BibTeX\ user
+wants to be able to produce documents that conform to them.
+(Take care to distinguish this use of `standard' from the \LaTeX\ manual's
+use of `standard' to mean `{\tt plain}, {\tt unsrt}, {\tt alpha} or
+{\tt abbrv}'.)
+
+
+The following abbreviations will be used:
+\item{BS:} a British Standard, or a combination of British Standards;
+\item{Chicago:} the {`Chicago Manual of Style'};
+\item{public domain styles:} {\tt plain}, {\tt unsrt}, {\tt alpha},
+ {\tt abbrv}, {\tt aaai}, {\tt acm}, {\tt ieeetr}, {\tt siam} and
+ {\tt apalike};
+\item{principal standards:} the conventions for citation and bibliography
+ layout specified by Butcher (1981), the British Standards
+ (1989; 1983; 1978) and the {`Chicago Manual of Style'}
+ (1982).
+
+
+\section{4: The problem of divergence}
+% On the assumption that attendees have some handouts [5 mins]
+% of output from Patashnik's and other public domain style files,
+% review the extent to which they meet standards such as the BSI and
+% Chicago.
+\subsection{4.1: Categories of document}
+Table 1
+%\ref{1}
+compares the classification of documents used
+for the British Standards
+with the classification used by the public domain \BibTeX\ styles.
+The table assumes that, where the 1989 edition
+says that `other information may be added in whatever position is most
+appropriate', one would actually put the information where specified by
+the 1976 edition. Table 2
+%\ref{2}
+gives a similar comparison for
+Chicago. You will see that in neither case is there a one-to-one mapping
+between the `\BibTeX\ category' and the `principal standard' category.
+Thus, if the \BibTeX\ user wishes to conform to the `principal standards',
+(s)he starts with the handicap of not being clear about which section
+of the \BibTeX\ documentation corresponds to the required
+section of the specification of a `principal standard'.
+
+\caption{Table 2: Chicago entry types compared with \BbiBTeX's
+}{\smallskip
+\offinterlineskip\tabskip0pt\halign
+{\strut\vrule\enspace\tabskip=1em#\hfil&#\hfil&\tabskip0pt#\hfil\tabskip0pt\vrule\cr
+\hline Category & Subcategory & Nearest \BibTeX \cr
+ & & entry-type \cr
+\hline
+Book & & {\tt book}, {\tt manual}, \cr
+ & & {\tt techreport} \cr
+ & & {\tt booklet}, \cr
+ & & {\tt proceedings} \cr
+\omit\vrule\tabskip1em&\multispan2{\hrulefill\hskip1em}\vrule \cr
+ & [chapters & {\tt inbook}, \cr
+ & \hfil or parts] & {\tt incollection}, \cr
+ & &{\tt inproceedings} \cr
+\hline
+J'n'l article & & {\tt article} \cr
+\hline
+Unpublished & Theses, & {\tt mastersthesis}, \cr
+material & lectures & {\tt phdthesis}, \cr
+ & and other & {\tt manual}, {\tt misc}, \cr
+ & unpublished & {\tt booklet}, \cr
+ & works & {\tt manual}, \cr
+ & & {\tt techreport} \cr
+ & Manuscript & {\tt unpublished}, \cr
+ & collections. & {\tt misc} \cr
+\hline
+Public & United States & {\tt unpublished}, \cr
+ documents & UK, Canada, & {\tt misc} \cr
+ & International & \cr
+ & \hfil Bodies & \cr
+\hline
+Nonbook & \hbox to 0pt{Musical scores} &{\tt misc} \cr
+materials & \hbox to 0pt{Sound recording} & \cr
+ & \hbox to 0pt{Video recordings} & \cr
+ & \hbox to 0pt{Computer programs}& \cr
+\hline
+}}
+\medskip
+\subsection{4.2: Elements of reference}
+Similarly, there is no one-to-one mapping between the elements of a reference as
+defined by the `principal standards' and the fields used by
+the current public domain \BibTeX\ bibliography styles:
+\item{\tt address} is used in three different senses.
+\itemitem{1}For `published works', one would presumably use \BibTeX's
+ {\tt address} for the `place
+ of publication'.
+ \itemitem{2} For `unpublished works', one would use {\tt address} as
+`locator
+ element' (BS 6371) or `location or sponsoring body' (Chicago,
+ Section 16.129).
+ \itemitem{3} For {\tt proceedings} and {\tt inproceedings}, {\tt address}
+ is used in \BibTeX\ 0.99 as `where the conference was held',
+ which the principal standards would probably treat as part
+ of the title.
+ In case 1, one might use \BibTeX's {\tt unpublished}, {\tt misc}, etc.\
+ for the principal standards' `unpublished works', so
+ there is probably an overlap of the function of {\tt address}
+ with that of {\tt howpublished}.
+\item{\tt month} does not seem to appear as such in the `principal standards'.
+ It is sometimes necessary to use `date' as a means of specifying
+ a particular issue (BS 1629 (1976 edn.), Section 4.4(b); Chicago, Section 16.124),
+ but the {\tt month} field is not quite suitable.
+ The non-obvious
+\begintt
+month = jul # "~4,"
+\endtt
+ trick has to be used.
+\item{\tt volume} It is not clear from the documentation
+ whether the public domain styles distinguish between
+ `a volume of a single work'
+ and `a single work that is a volume in a series'.
+ Chicago shows variation of positioning between the two cases.
+\item{\tt portion} Chicago 16.49--16.53 mentions the specification
+ of chapters, parts or page-ranges.
+ BS 1629 (1976 edn.) has the concept of `portion' for these specifications.
+ `Specifying a portion' would be easier than getting involved
+ in tricks like
+\begintt
+chapter = "1.2", type = "Section"
+\endtt
+ with \BibTeX's |chapter| and |type| fields.
+
+\noindent In summary,
+the following groups seem to be merged in the principal standards:
+ {\tt booklet}, {\tt manual}, and {\tt proceedings};
+ {\tt conference}, {\tt incollection} and {\tt inproceedings};
+ {\tt mastersthesis} and {\tt phdthesis}.
+The following \BibTeX\ fields seem to hold information that
+ the principal standards would handle differently:
+ {\tt address} and {\tt howpublished};
+ {\tt institution}, {\tt month}, {\tt organization} and {\tt school}.
+The principal standards don't seem to involve the concepts of
+ `open' and `closed'.
+\medskip
+\subsection{4.3: Order and presentation of elements}
+Given the divergence between the schemes used for classification and
+element-definition, it is difficult to make a general comparison of
+features such as the order of elements, their punctuation and the
+fonts used. However,
+we can make such a comparison in simple cases, for example in the
+cases of references to books and to articles.
+
+If you compare BS (1989) and Chicago (1982, p.439), you
+will see that there is a degree of consensus about the style in which
+references to books are to be laid out for reference-by-number.
+Unfortunately, none of the relevant public domain styles
+({\tt plain}, {\tt unsrt}, {\tt abbrv}, {\tt aaai},
+{\tt acm}, {\tt ieeetr}, {\tt siam})
+format entries in line with this consensus.
+
+For reference-by-number to journal articles, BS and Chicago differ in the order
+suggested for volume and year. Of the public domain styles, {\tt acm} seems
+closest to Chicago. Nothing seems particularly close to the BS.
+
+The public domain author-date styles are {\tt alpha}, {\tt apalike}
+and {\tt aaai}. Of these, {\tt alpha} has unconventional labels,
+and {\tt aaai} gives an unconventional bibliography (with both the
+short form of author-date and the long form). The remaining
+style, {\tt apalike} seems fairly similar to BS and Chicago for
+journal articles, but not for books (because of the order of place
+and publisher).
+\medskip
+
+\frame{5pt}{The {\tt \lowercase{MASTERSTHESIS}} and {\tt \lowercase{PHDTHESIS}}
+entry types now take an optional {\tt type} field\dots
+
+Similarly, the {\tt \lowercase{INBOOK}} and {\tt \lowercase{INCOLLECTION}} entry types
+now take an optional {\tt type} field, allowing `section 1.2' instead of the default
+`chapter 1.2'.
+
+\dots{\tt \lowercase{PROCEEDINGS}}\dots\
+If you want to include the publisher's\dots\ address, put it in the
+{\tt publisher} or {\tt organization} field.
+
+\dots feel free to be creative in how you use these entry types\dots
+
+
+\dots don't take the field names too seriously\dots
+
+\dots don't take the warning messages too seriously\dots
+
+\dots if you want to include information for the day of the month,
+\dots
+{\tt month = jul \char'43\ "\char'176 4,"}
+will probably produce just what you want.
+}
+\nobreak
+\caption{Figure 1: Some hints from `\BbiBTeX ing'}
+\medskip
+\subsection{4.4: Consequences}
+Thus, although \BibTeX\ is very useful for reducing the work involved in
+producing a bibliography, and the public domain styles produce
+neat bibliographies we have to note that
+the entry-types and fields used by the public domain styles diverge
+ from the document-categories and reference-elements
+ those used by the principal standards. This may mean
+ that one has to resort to tricks (such as those shown in Figure
+1,
+%\ref{1}
+taken from Patashnik (1988a)
+ to get the output `looking right'.
+ I imagine that, if the entry-types and fields
+ corresponded more closely to those used by the principal standards,
+ one would have to resort to tricks less often.
+In addition, the punctuation and fonts used by the
+ public domain styles will lead many potential users to
+ quibble that `this is not how we do things in my subject'.
+
+\section{5: Towards `principal standard' styles}
+\subsection{5.1: Extent of consensus about}
+\rightline{\sl categories\slash entry-types}
+\noindent Thus the current public domain styles, and the corresponding
+ entry-types and fields, do not seem to make for straightforward adherance to
+the `principal standards'. How could new entry-types and fields be defined
+that correspond more closely to the assumptions behind the `principal
+standards'?
+
+\topinsert
+\hsize6.5truein\tabskip0pt
+\def\hline{\noalign{\hrule}}{
+\offinterlineskip\halign to\hsize{\tabskip=2em
+minus1em\vrule\strut\enspace#\hfil&&\enspace#\hfil&#\hfil\tabskip0pt\vrule\cr
+\noalign{\hrule} BS & BS & Chicago &Chicago &
+Examples common to\cr category & subcategory & category
+&subcategory & BS and Chicago \cr \noalign{\hrule} Book or other & Single-vol.\
+work & Book & All but `chapters & Book \cr separately & Multi-vol.\ work
+& & or parts' & Technical report$^a$ \cr issued &
+British Standard & & &UK HMSO pub. \cr publication &
+Technical report & & & \cr
+ & Translation & & & \cr
+ & Government pub.& & & \cr
+\multispan2{\vrule\hfill}&\multispan2{\hrulefill}&\omit\hfill\vrule\cr%\cline{3-4}
+ & &Public docs. & UK nonparliamentary$^b$
+& \cr \noalign{\hrule}
+Contribution & In book\dots & Book & Chapters or parts
+ & Collections \cr
+or article & & & & Conf. proceedings\cr
+\omit\vrule\hfill&\multispan4{\hrulefill}\cr%\cline{2-5}
+ &In periodical\dots& Journal article & & Article \cr
+ & & & & \cr
+\noalign{\hrule}
+Unpublished & & Unpublished & Lectures &British Lib. Add. MS.\cr
+ & & & Duplicated material &Theses$^c$ \cr
+ & & & Manuscript colls. & \cr
+\multispan2{\vrule\hfill}&\multispan2{\hrulefill}\cr%\cline{3-4}
+ & & Public docs. & USA unpublished & \cr
+ & & & UK unpublished & \cr
+ & & & Canadian archives & \cr
+\omit\vrule\hfill&\multispan1{\hrulefill}\cr%%\cline{2-2}
+ &Docs. resembling& & & \cr
+ &published works & & & \cr
+\noalign{\hrule}}}
+
+\noindent\strut{$^a$ For technical reports, BS says that `series
+ title and number' are `essential elements'.}
+
+\noindent{$^b$ Chicago says that these are usually treated
+ like `privately published books'.}
+
+\hangindent20pt\noindent{$^c$ BS suggests that theses
+ resemble published works, should have
+ `location element' like other unpublished material,
+ but should be given a `descriptive element'
+ like books.
+ Chicago suggests treating title as for a journal article, and providing
+ `location or sponsoring body or both'.}
+\caption{Table 3: BS 1629(1976)/6371 and Chicago categories that are similar}
+\endinsert
+
+Table 3 displays some BS and Chicago categories that
+seem similar enough to be represented by common \BibTeX\ entry-types.
+Table 4 shows categories that are only described
+by the British Standards, while Table 5 shows
+categories that are only described by Chicago.
+Thus any new scheme should, ideally, be able to cater for all the
+categories shown in Tables 3, 4 and 5.
+One would also have to refer to ISO 690.
+Compatibility with bibliographic databases on CD-ROMs might
+be useful too, but there currently seems little consistency between suppliers,
+let alone consistency between conventions for fields in CD-ROMs and
+fields in printed bibliographies. It might also be useful to consider the
+database structure used for computerised library catalogues.
+
+\caption{\overfullrule0pt Table 4: Categories defined by BS 1629(1976)\slash 6371 but
+not by Chicago} {\overfullrule0pt\offinterlineskip
+\def\hline{\noalign{\hrule}}
+\overfullrule=0pt
+\tabskip0pt
+\halign
+to\hsize{\vrule\strut\tabskip3em
+minus2.5em\enspace#\hfil&#\hfil\strut\tabskip0pt\vrule\cr \hline
+Category & Subcategory \cr
+\hline
+Portion of `book or other & \cr
+separately issued publication' & \cr
+other than a separate & \cr
+contribution & \cr
+\hline
+Periodical or other serial & Periodical as \cr
+publication & a whole \cr
+\omit\vrule\hfill&\omit\hrulefill\quad\tabskip0pt\cr
+ & Limited run or \cr
+ & specific vol. \cr
+ & or issue \cr
+\hline
+Patent & Patentee and \cr
+ & inventor \cr
+\omit\vrule\hfill&\omit\hrulefill\quad\vrule\tabskip0pt \cr
+ & {Patentee only} \cr
+\hline
+}}
+\medskip
+\caption{Table 5: Categories defined by Chicago but not by BS
+1629(1976)/6371}
+{\overfullrule=20pt\offinterlineskip
+\tabskip=0pt
+\halign
+to \hsize{\vrule\strut\enspace\tabskip=3em
+minus2.5em#\hfil&#\hfil\tabskip=0pt\vrule\cr \hline Category & Subcategory
+\cr \hline
+Public documents & US Congress \cr
+ & US Executive departments \cr
+ & US Statutes etc. \cr
+ & US States and local \cr
+ & UK Parliament \cr
+ & US Published records \cr
+ & Canadian government\cr
+ & International Bodies \cr
+\hline
+ Nonbook materials&Musical scores$^a$ \cr
+ & Sound recordings \cr
+ & Video recordings \cr
+ & Computer programs \cr
+\hline}}
+\noindent{\strut$^a$ `Follow rules similar to those for books.'}
+
+\medskip
+\subsection{5.2: A division into categories/entry-types}{\tolerance10000
+From Tables 3, 4, 5,
+it seems that a project to provide style-files to implement the
+`principal standards' might start by defining entry-types such as the following.
+\item{\tt booklike} The categories of document specified in Section 4.2(a)
+ (publication as a whole) of BS 1629 (1976 edn.) (with the exception
+ of `works issued in series by research bodies\dots').
+ This seems the same as the group of documents
+ classified as `Books' by Chicago (excluding
+ Chicago's `chapters or parts of a book').
+ This category might include some of Chicago's
+ `Nonbook materials', e.g. musical scores.
+\item{\tt report} Publications `as a whole' issued in series by research
+ bodies and similar organizations, as specified in
+ Section 4.2(a) of BS 1629 (1976 edn.).
+ Differs only from {\tt booklike} in that
+ `series title and number' are required.
+\item{\tt booklikeportion} A portion (other than a separate contribution) of
+ a document in the category specified in Section 4.2(b)
+ of BS 1629 (1976 edn.) (excluding documents for which `series title
+ and number' are required).
+ (Looks as if it could be implemented by a {\tt
+crossref} to a {\tt booklike} database entry.)
+ Probably equivalent to the optional argument of
+ |\cite|, but worth doing to give the ability to
+ conform to BS 1629 (1976 edn.).
+\item{\tt reportportion} As {\tt booklikeportion} but with
+ `series title and number' required.
+\item{\tt contribution} Contribution to a `book or other separately issued
+ publication' as defined in Section 4.4(a) of BS 1629 (1976 edn.).
+ `Chapter or part of a book' as defined in Sections
+ 16.49--16.53 of Chicago.
+\item{\tt publishedlike} `Documents resembling published works' as specified
+ in Section 10 of BS 6371.
+ This category would include theses. It looks as
+though:
+ \itemitem{\it (i)} the thesis information that BS 6371 would
+use to `compile the descriptive element like a book'
+ is the same as that needed for
+ Chicago to treat the thesis like a journal article
+\itemitem{\it (ii)} the BS 6371 `location element' is much the
+same as the Chicago `location or sponsoring body
+ or both'.
+ This category might also include some of Chicago's
+ `nonbook materials', e.g. sound recordings.
+\item{\tt patent} Patents, as specified in Section 4.5 of BS 1629 (1976
+edn.).
+\item{\tt public} Public documents, as specified in Section 16.141 of
+ Chicago, but excluding those `cited like
+ privately published books' (Chicago, Section 16.162)
+ which would be {\tt booklike} and those
+ to which BS 6371 (except Section 10)
+ and Sections 16.158, 16.171 and 16.172
+ of Chicago apply (which would be {\tt unpublished}).
+\item{\tt unpublished}
+ To which BS 6371 (except Section 10)
+ and Sections 16.128, 16.131--16.133,
+ 16.158, 16.171 and 16.172
+ of Chicago apply.
+\item{\tt periodical} As defined in Section 4.3(a) of BS 1629 (1976 edn.).
+
+\item{\tt periodicalrun} As defined in Section 4.3(b) of BS 1629 (1976 edn.).
+ Might be implemented as a {\tt crossref} to
+ a {\tt periodical}.
+\item{\tt article} This category would include `a contribution
+ or article in a periodical or serial publication'
+ (Section 4.4(b) of BS 1629 (1976 edn.)), and `journal articles'
+ (Chicago, Sections 16.98--16.127).
+\smallskip}
+\noindent
+As it happens, this approach gives 12 categories, compared with
+the 14 for {\tt plain}, {\tt unsrt}, {\tt alpha}, {\tt abbrv}.
+(Studying the unified approach in the 1989 edition of
+BS 1629 might enable one to reduce the number of categories still further.
+On the other hand, the sentences about `Other information may be added
+in whatever position is most appropriate' may lead to retention of the
+categories suggested in the 1976 edition, in order to ensure that
+`other information' is placed appropriately.)
+\medskip
+\subsection{5.3: Elements/fields}
+A project that aimed to implement the `principal standards' would also have to
+define \BibTeX\ fields (within the bibliography entries) that correspond
+to the `elements of a bibliographic reference' defined by the `principal
+standards'.
+
+With the British Standards, it may be possible to use
+the BS `essential' and `supplementary' or `optional' elements
+directly as \BibTeX's required and optional fields.
+It looks as if these elements would provide the information required by
+Chicago, but someone would have to work through all the Chicago examples
+to check this!
+To support the `short title' system (Butcher, 1981; pp. 177--8),
+a field such as {\tt shorttitle} seems desirable.
+
+This approach might give fields such as the following for the entry-types
+postulated above.
+{\tolerance10000
+\item{\tt booklike}
+ Required fields: {\tt author}, {\tt title}, {\tt year}.
+ Optional fields: {\tt shorttitle}, {\tt transtitle},
+ {\tt origtitle}, {\tt edition}, {\tt alleditor},
+ {\tt alltranslator}, {\tt allillustrator}, {\tt thiseditor},
+ {\tt thistranslator}, {\tt thisillustrator}, {\tt placeofpub},
+ {\tt publisher}, {\tt noofvols}, {\tt pagination},
+ {\tt mentionofany}, {\tt size}, {\tt seriesinfo},
+ {\tt isbn}, {\tt price}.
+ Here {\tt author} may be `compiler, personal or corporate'.
+ The meanings of other fields should be obvious by reference to BS 1629 (1976 edn.).
+\item{\tt report}
+ As {\tt booklike}, but with {\tt seriesinfo} required, rather than
+ optional.
+\item{\tt booklikeportion}
+ Same fields as {\tt booklike} except that:
+ `book trade' information, namely
+ {\tt alleditor},
+ {\tt alltranslator}, {\tt allillustrator}, {\tt thiseditor}, {\tt
+thistranslator}, {\tt thisillustrator}, {\tt noofvols}, {\tt pagination},
+ {\tt mentionofany}, {\tt size}, {\tt price}
+ are neither required nor optional.
+ \item {\tt volpart} and {\tt volparttitle} would be optional
+ and {\tt portion} would be required.
+
+\item{\tt reportportion}
+ As {\tt booklikeportion} but with {\tt seriesinfo} required rather than
+ optional.
+\item{\tt contribution} Required fields: {\tt contauthor}, {\tt
+conttitle},
+ {\tt pubauthor} or {\tt pubeditor}, {\tt pubtitle},
+ {\tt year}, {\tt portion}.
+ Optional fields: {\tt shorttitle},
+ {\tt conttranstitle}, {\tt contorigtitle},
+ {\tt contmentionofany}, {\tt pubtranstitle}, {\tt pubedition},
+ {\tt pubvolume}, {\tt placeofpub}, {\tt publisher},
+ {\tt seriesinfo}, {\tt isbn}.
+\item{\tt publishedlike}
+ Fields for `descriptive element' as for {\tt booklike}, with
+ the omission of {\tt placeofpub}, {\tt publisher}, {\tt isbn}.
+ Fields for `location element' as for {\tt unpublished} -- see below.
+\item{\tt patent}
+ Required fields: {\tt patentee}, {\tt title}, {\tt country},
+ {\tt designation}, {\tt serialno}, {\tt pubyear}, {\tt restofpubdate}.
+ Optional fields: {\tt shorttitle},
+ {\tt transtitle}, {\tt inventor},
+ {\tt intclass}, {\tt natclass}, {\tt appdate},
+ {\tt pagination}, {\tt platesetc}.
+\item{\tt public} Following Chicago (Section 16.141), fields for
+ {\tt division}, {\tt body}, {\tt subsid}, {\tt title},
+ {\tt author}, {\tt identification},
+ {\tt publisher}, {\tt date}. In addition, an optional
+ {\tt shorttitle} field, for `short title' citation.
+\item{\tt unpublished}
+ Descriptive element, consisting of optional fields {\tt name},
+ {\tt title}, {\tt date}, {\tt designation}.
+ Location element, consisting of optional fields {\tt place},
+ {\tt repository}, {\tt callno}, {\tt locwithin}.
+ Although the individual fields of the
+ descriptive element and the location element are optional,
+ the descriptive element and the location element are both
+ `required' as a whole.
+ In addition, optional fields {\tt otherinfo} (for Section 9 of BS 6371) and
+ {\tt shorttitle} for `short title' citation.
+\item{\tt periodical} Required field: {\tt title}.
+ Optional fields: {\tt transtitle}, {\tt origtitle}, {\tt firstissue},
+ {\tt lastissue}, {\tt frequency}, {\tt placeofpub}, {\tt publisher},
+ {\tt size}, {\tt summarylangs}, {\tt price}, {\tt earliertitles}.
+\item{\tt periodicalrun}
+ Required fields: {\tt title}, {\tt firstissue}, {\tt lastissue}.
+ Optional fields: {\tt transtitle}, {\tt origtitle},
+ {\tt frequency}, {\tt placeofpub}, {\tt publisher},
+ {\tt size}, {\tt summarylangs}, {\tt price}.
+\item{\tt article}
+ Required fields: {\tt author}, {\tt arttitle}, {\tt serialtitle},
+ {\tt year}, {\tt volume}, {\tt portion}.
+ Optional fields: {\tt transtitle}, {\tt origtitle}, {\tt mentionofany},
+ {\tt placeofpub}, {\tt part}.
+\par}
+
+% Critique bit: "Marie Clare van Leunen had undue influence. [5 mins]
+% The standards should have had more influence."
+
+% Hacking at bst files. Structures in the bst files that I understand.[5 mins]
+% Postfix stack business that I don't.
+% Bit of critique: "Did Patashnik really have to use this Postfix
+% stack business? I don't know."
+
+% Future work for somebody: [5 mins]
+% - start with the concepts in the standards.
+% - define fields.
+% - define bst files that process such bib files.
+% - write it all up.
+\medskip
+\subsection{5.4: Implementation}
+The \BibTeX\ style-file language provides many facilities for
+manipulation of the information that appears in bibliographies.
+Thus, having defined new entry-types and fields, one can
+declare the fields to \BibTeX and also
+define \BibTeX\ {\tt FUNCTION}s to construct the
+ bibliography entries from the fields
+
+I anticipate that if the business of defining entry-types and fields that
+correspond more closely to those defined by the principal standards was
+followed through, there would be less need for the sorts of tricks
+mentioned in Figure {1}, and the output would
+be more likely to be `right first time'.
+
+
+
+
+\section{6: Wish lists}
+\subsection{6.1: \BibTeXi\ itself}
+The current version of \BibTeX\ makes it difficult to produce the style shown in BSI
+(1989) for titles that involve colons. For example, BSI (1989) shows the title:
+
+\centerline{\it Shetland sanctuary: birds on the Isle of Noss}
+
+\noindent Unfortunately, the effect of \BibTeX's |change.case t$| on the likely
+ {\tt bib} file entry would be to give `{\it Birds\/}'.
+
+It would be useful if some future version of \BibTeX\
+allowed a variation on
+\begintt
+change.case$ t
+\endtt
+that refrained from `upper-casing' after a colon.
+\medskip
+\subsection{6.2: \BibTeXi\ style-files}
+It would be nice if someone had time to develop style-files that
+worked in terms of the same concepts as the principal standards, and
+delivered bibliographies formatted in accordance with these standards!
+\medskip
+\subsection{6.3: The combination of \LaTeXsl\ and \BibTeXi}
+\subsubsection{A document having more than one list}
+An author may wish to use `bibliography' to mean `works in the field, with
+some notes about them', and `references' to mean `works I have cited'. Thus,
+a `bibliography' may not be the same as `a long list of references', and
+\LaTeX's assumption that {\tt article}s have `references' while
+{\tt report}s and {\tt book}s have `bibliographies' may be an
+over-simplification.
+
+Some works have more than one list. For example a book might have a
+division called `references', listing works
+ giving further information about the subjects covered in the book,
+ and a division called `further reading', listing works that
+ cover related subjects.
+Similarly, the draft new British Standard for theses (BSI, 1988) suggests a
+`list
+ of references' (for `every work cited') {\em and\/} a `bibliography'
+ (for `all sources consulted but not necessarily relevant to the
+ thesis').
+
+There is no harm in {\tt thebibliography} having a default title,
+but an official mechanism for replacing the default by a more accurate
+description would be very useful.
+Aside: Are the people who are developing non-English
+\LaTeX\ repeating the over-simplification? Instead of providing a mechanism for getting
+equivalents of `references' and `bibliography' in many languages,
+might it be better to just provide one default title in each language
+plus a mechanism for changing the title?
+
+More ambitiously, could some future versions of
+\LaTeX/\BibTeX\ give more general support to documents
+with more than one list? For example,
+could some |\cite|\/s generate a list of references in a brief
+|\bibliographystyle| to be printed under
+a heading of `references', while other |\cite|\/s generate another
+list in a different |\bibliographystyle| to be printed under a heading
+of `further reading'?
+I think that people producing conference proceedings can currently
+get references at the end of each chapter by applying \BibTeX\ separately
+to each chapter: could some development simplify their task?
+\medskip
+\subsubsection{A list with subdivisions}
+Under some circumstances, it may be desirable to divide a list into
+sections. For example, Figure {2} shows the structure of the
+bibliography for a history thesis. Chicago (Chicago Manual of Style,
+1982; chapter 15) shows some further examples of subdivided bibliographies.
+
+\caption{Figure 2: Structure of a history thesis bibliography}
+{\parindent0pt
+\baselineskip10pt
+\font\ttt=cmtt8
+\let\tt\ttt
+\begintt
+\section{Manuscript sources}
+ \subsection{Nottinghamshire County Record Office}
+ \subsection{Nottingham University Library,
+ Manuscripts Department}
+ \subsection{Public Record Office}
+ \subsection{British Library}
+ \subsection{Borthwick Institute}
+ \subsection{Friend's Reference Library}
+ \subsection{Dr. William's Library}
+\section{Printed sources}
+ \subsection{National government series}
+ \subsection{Historical Manuscripts Commission}
+ \subsection{Thomason Tracts (British Library)}
+ \subsection{Other printed sources}
+\section{Secondary works}
+\section{Periodicals}
+\section{Theses}
+\endtt
+}
+
+Could some future versions of \LaTeX/\BibTeX\ support such subdivisions?
+For example,
+perhaps |\section| and |\subsection| could be allowed within
+{\tt thebibliography}, the author could put
+\begintt
+@UNPUBLISHED{...
+ subbib = "Manuscript Sources",
+ ...
+ }
+\endtt
+in a {\tt .bib} file, and \LaTeX/\BibTeX\ between them could arrange that
+the item in question would appear under a sub-heading of `Manuscript Sources'.
+
+\section{7: References}
+\let\newblock\null
+\let\em\rm
+{\frenchspacing\parindent0pt\hangindent20pt\hangafter1
+BSI,
+BS 1629, British Standards Institution, 1989.
+{\it For printed matter, the 1989 edition sometimes gives less detail
+than the 1976 edition. The present article uses information from both editions.}
+
+\hangindent20pt\hangafter1 BSI,
+Citation of unpublished documents,
+BS 6371, British Standards
+Institution, 1983.
+
+\hangindent20pt\hangafter1 BSI,
+Citing publications by bibliographic references,
+\newblock BS 5605, British Standards Institution, 1978.
+
+\hangindent20pt\hangafter1 BSI,
+Recommendations for the presentation of theses, dissertations and similar
+ documents: Draft for public comment,
+\newblock BS 4821, British Standards Institution, 1988.
+\newblock {\it The revised standard is likely to be published in 1990.}
+
+\hangindent20pt\hangafter1 Judith Butcher,
+\newblock {\em Copy-editing},
+\newblock Cambridge University Press, 2nd edition, 1981.
+
+
+\hangindent20pt\hangafter1
+{\em The {C}hicago Manual of Style},
+ University of Chicago Press, 13th
+edition, 1982.
+
+
+\hangindent20pt\hangafter1 Horace Hart,
+\newblock {\em Hart's rules for compositors and readers at the {U}niversity
+ {P}ress, {O}xford},
+\newblock Oxford University Press, 39th edition, 1983.
+\newblock {\it Revised by Hart's successors.}
+
+\hangindent20pt\hangafter1 Leslie Lamport,
+\newblock {\em \LaTeX: A Document Preparation System},
+\newblock Addison-Wesley, 1986.
+
+\hangindent20pt\hangafter1 Mary-Claire van Leunen,
+\newblock {\em A Handbook for Scholars},
+\newblock Knopf, 1978.
+
+\hangindent20pt\hangafter1 Ruari McLean,
+\newblock {\em The {T}hames and {H}udson Manual of Typography},
+\newblock Thames and Hudson, 1980.
+
+\hangindent20pt\hangafter1 Oren Patashnik,
+\newblock {\em \BibTeX ing}, January 1988a.
+
+
+\hangindent20pt\hangafter1 Oren Patashnik,
+\newblock {\em Designing \BibTeX\ styles}, January 1988b.
+
+\hangindent20pt\hangafter1 Kate~L. Turabian,
+\newblock {\em A Manual for Writers},
+\newblock University of Chicago Press, 5th edition, 1987.
+
+
+\hangindent20pt\hangafter1 Hugh Williamson,
+\newblock {\em Methods of Book Design},
+\newblock Yale University Press, 3rd edition, 1983.
+
+
+
+
+
+
+}
+\rightline{\sl David Rhead}
+
diff --git a/info/digests/texline/no10/tex88.tex b/info/digests/texline/no10/tex88.tex
new file mode 100644
index 0000000000..a6d38ca346
--- /dev/null
+++ b/info/digests/texline/no10/tex88.tex
@@ -0,0 +1,72 @@
+\centerline{\bf \TeX88\ -- the proceedings}
+\smallskip
+\noindent
+At last the proceedings! After what seems an etern\-ity,
+the proceedings of the 1988 European \TeX\ Conference at
+Exeter are available. I will not go into the excuses
+here, since I plan to talk about the production of the
+proceedings at \TeX90 at Cork. The proceedings are
+published by Ellis Horwood Publishers. On the one hand
+this makes them a little expensive at \quid39.95 (don't
+blame me, I'm only the editor), but on the other hand, it
+does mean that the production is quite good, with proper
+hard covers (remember hard covers?) and none of this nasty
+wire binding that locks up the book shelf. The paper
+quality is good too (much better than the current paperback
+edition of the \TB). I would also claim that the quality
+of the papers is good, although natural modesty forbids
+me from claiming that it is easily the best produced of
+any of the \TeX\ conferences, either in Europe or in the
+US.
+
+The macros described in some of the papers are available in
+the Aston Archive. In addition, the abstracts have also
+been placed there, in a sort of \BibTeX-style
+bibliography. To obtain information on which macros
+area there, and their exact location you need to read the
+file
+\begintt
+[tex-archive.digests.tex88]proc.info
+\endtt
+The `abstracts' are in the same directory, in a file
+named |abs.bib|. This last file has also been shipped to
+Heidelberg, and may very well be on their server too.
+
+TUG and the publishers are exploring ways of arranging a
+discount for members. It may be possible to extent this
+to other \TeX\ groups, but nothing has been finalised at
+present. If you went to the conference, your copy will
+either be in your hands or on its way. Fret not.
+Nevertheless there are about a dozen attendees whom I have
+been unable to trace. They are:
+Susan C Allcock,
+Josep Sarrate,
+Torbj\"orn Lindh,
+Ger W P M Bakker,
+Mark Liederkerken,
+David Hardy,
+Howard Hansford,
+Hubert Twum-Barima,
+Jim Curry,
+Harald Dahlmanns,
+G{\"u}nter Unbescheid,
+Neil Swindells and
+John Sheppard.
+If they can contact me with a current address, I'll be
+pleased to see that they get their copy.
+
+The |.bib| entry for the proceedings is:
+\begintt
+@proceedings{TeX88,
+title={{\TeX}: Applications, {Uses},
+ {Methods}},
+year={1990},
+editor={Malcolm Clark},
+organization={\TeX88},
+publisher={Ellis Horwood},
+address={Chichester},
+isbn={0139122966},
+price={\pounds39.95}
+\endtt
+
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/texline.head b/info/digests/texline/no10/texline.head
new file mode 100644
index 0000000000..87aeaf5a8e
--- /dev/null
+++ b/info/digests/texline/no10/texline.head
@@ -0,0 +1,40 @@
+\topinsert
+\begingroup
+\font\huge=palatino at65truept%
+\newbox\info
+\newbox\banner
+\newbox\long
+\newdimen\infoht
+\newdimen\bannerht
+\setbox\info=\vbox{%
+\font\small=cmr7 at 7truept%
+\baselineskip=7.5truept%
+\small
+\setbox\long\hbox{printed at Imperial College Computer Centre}%
+\hsize=\wd\long
+\def\monyr{\ifcase\month\or January\or February\or March\or April
+ \or May\or June\or July\or August\or September\or October
+ \or November\or December\fi\ \number\year}%
+\line{\hfill Number 10, \monyr}
+\line{\hfill a Newsletter of the \TeX\ community}
+\line{\hfill edited and assembled by}
+\line{\hfill Malcolm Clark}
+\line{\hfill PO Box 1897}
+\line{\hfill London NW6 1DQ}
+\line{\hfill Tel: 071 269 3555}
+\line{\hfill Tel: 071 435 8983}
+\line{\hfill Fax: 071 831 6265}
+\line{\hfill Janet: malcolm@icrf}
+\line{\hfill Unix: mwc@doc.ic.ac.uk}}
+\setbox\banner\vbox{\hsize=260pt%
+\huge\TeX\kern-0.2ex lineX}
+\infoht=\ht\info
+\advance\infoht by\dp\info
+\bannerht=\ht\banner
+\advance\bannerht by\dp\banner
+\advance\infoht by-\bannerht
+\divide\infoht by2
+\advance\infoht by3ex
+\hbox {\box\info\qquad\raise\infoht\box\banner}
+\endgroup
+\endinsert
diff --git a/info/digests/texline/no10/texline.tex b/info/digests/texline/no10/texline.tex
new file mode 100644
index 0000000000..acd1095576
--- /dev/null
+++ b/info/digests/texline/no10/texline.tex
@@ -0,0 +1,143 @@
+\message{TeXline macros}
+\vsize9.5in
+\hsize6.5in
+\input newtwo-column%%%%%
+\input verbar
+\tolerance3000
+\doublehyphendemerits15000
+%\raggedbottom
+\hfuzz2.5pt
+\baselineskip12pt
+\parskip0pt
+\parindent1em
+\abovedisplayskip1pt
+\belowdisplayskip1pt
+
+\headline{\ifnum\pageno>1\sl \TeXline\ 10 \hss \folio
+\else\hfil\fi}
+\def\rhead{\ifnum\pageno>1{\sl \TeXline\ 10} \hss
+\else\hfil\fi}
+\def\lhead{\ifnum\pageno>1{\sl \hfil \folio}\fi}
+\nopagenumbers
+\def\,{\ifmmode\mskip\thinmuskip\else\thinspace\fi}
+\def\nl{\hfill\break}
+\def\bi{\item{$\bullet$}}
+\def\section#1{%
+\medskip\leftline{\let\sc\scit\sl #1}\par\noindent\ignorespaces}
+\def\article#1{\centerline{\let\ukTuG\ukTUGbf\bf#1}\medskip\noindent\ignorespaces}
+\def\author#1{\smallskip\rightline{\sl#1}}
+
+\def\frac#1/#2{\leavevmode\kern0.1em
+ \raise0.5ex\hbox{\the\scriptfont0 #1}\kern-0.1em
+ /\kern-0.15em\lower0.25ex\hbox{\the\scriptfont0 #2}}
+\def\*#1{\ifmmode\discretionary{\thinspace\the\textfont2\char2#1}{#1}{#1}\else\accent'27#1\fi}
+
+\font\iteight=cmti8
+\font\ttit=cmsltt10
+\font\scb=cmbx8
+\font\sans=cmss10
+\font\sc=cmcsc10
+\font\mf=logo10
+\font\mfb=logobf10
+\font\mfsl=logosl10
+\let\em\it
+\font\symb=symbol at 10pt
+\font\cmu=cmu10
+
+\def\scit#1{\iteight\uppercase{#1}}
+
+\hyphenation{SGML SGML-ers}
+
+\def\MF{{\rm{\mf META}\-{\mf FONT}}}
+\def\MFb{{\bf{\mfb META}\-{\mfb FONT}}}
+\def\MFsl{{\sl{\mfsl META}\-{\mfsl FONT}}}
+\chardef\apple='360
+\def\Mac{{\symb\apple}}
+\def\MarkUp{MarkUp '8\kern-0.2em\lower0.45ex\hbox{7}}
+\def\LaTeX{{\rm L\kern-.36em\raise.3ex\hbox{\sc a}\kern-.15em
+ T\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\LaTeXsl{{\it L\kern-.36em\raise.3ex\hbox{\iteight
+A}\kern-.15emT\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\TeXline{{\sl\TeX\kern-0.1em line}}
+\def\SGML{{\sc sgml}}
+\let\sgml\SGML
+\def\PS{P{\sc{ost}}\-S{\sc{cript}}}
+\def\plain{{\tt plain}\kern-0.1667em\TeX}
+\def\ukTuG{{\sc uk}\kern-0.1emT\kern-0.1667em\lower0.5ex\hbox{U}\kern-0.125emG}
+\def\ukTUGbf{{\scb UK}\kern-0.1emT\kern-0.1667em\lower0.5ex\hbox{U}\kern-0.125emG}
+\def\TeXtures{{\sc\TeX\kern-0.1667em tures}}
+\def\TeXpert{{\sl\TeX\kern-0.1em pert systems\/}}
+\def\TeXhax{\TeX{\sc hax}}
+\let\hax\TeXhax
+\def\TeXbook{{\sl \TeX book}}
+\let\TB\TeXbook
+\def\PCTeX{{\sc pc}\kern-0.1em\TeX}
+\let\ps\PS
+\def\TS{Type \&~Set}
+\def\dvi{{\tt dvi}}
+\let\DVI\dvi
+\def\tfm{{\tt tfm}}
+\let\TFM\tfm
+\def\pxl{{\tt pxl}}
+\let\PXL\pxl
+\def\gf{{\tt gf}}
+\let\GF\gf
+\def\pk{{\tt pk}}
+\let\PK\pk
+\def\CM{{\rm Computer Modern}}
+\def\WEB{{\tt WEB}}
+\def\Weave{{\tt Weave}}
+\def\Tangle{{\tt Tangle}}
+\def\quid{{\cmu\$}}
+\def\unix{{\sc unix}}
+\def\AmSTeX{$\cal A$\kern-.1667em\lower.5ex\hbox{$\cal M$}\kern-.125em
+ $\cal S$-\TeX}
+\def\VorTeX{V\kern-.2em\lower.5ex\hbox{O}\kern-.125em R\TeX}
+\def\BiBTeX{{\sc Bib}\kern-.2em\TeX}
+\let\BibTeX\BiBTeX
+\def\SliTeX{{\sc Sli}\TeX}
+\def\IniTeX{{\sc Ini}\TeX}
+\def\TEX{T\kern-0.1667em\lower0.5ex\hbox{\^E}\kern-0.125em X}
+\def\JANET{{\sc Janet}}
+\let\Janet\JANET
+\def\DVItoVDU{DVIto\kern-.15em VDU}
+\def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC}
+\def\PiCTeX{\PiC\TeX}
+\def\XeT{X\kern-0.1667em\lower.5ex\hbox{E}\kern-.125em T-\TeX}
+\def\FASTeX{F\kern-.1667em \lower.5ex\hbox{A}\kern-.1667em S\TeX}
+\def\TUGboat{{\sc TUGboat}}
+\def\psfig{{\it psfig}}
+\def\OzTeX{O\kern-.03em z\kern-.15em\TeX}
+
+\def\DW{Dominik Wujastyk}
+\def\DEK{D\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125em K}
+
+\def\by{$\times$}
+\def\inch{$''$}
+\def\ascii{{\sc ascii}}
+\let\ASCII\ascii
+\def\eqn{{\tt eqn}}
+\def\b{{\tt\char'134}}
+\def\wysiwyg{{\it wysiwyg\/}}
+%\def\boxit#1{\vbox{\hrule\hbox{\vrule\kern3pt
+% \vbox{\kern3pt#1\kern3pt}\kern3pt\vrule}\hrule}}
+
+
+% Look in the 'Windows' menu for the pictures window
+% It's like the Scrapbook -- cut and paste pictures
+%
+
+\def\picture #1 by #2 (#3){
+ \vbox to #2{
+ \hrule width #1 height 0pt depth 0pt
+ \vfill
+ \special{picture #3} % this is the low-level interface
+ }
+ }
+
+\def\scaledpicture #1 by #2 (#3 scaled #4){{
+ \dimen0=#1 \dimen1=#2
+ \divide\dimen0 by 1000 \multiply\dimen0 by #4
+ \divide\dimen1 by 1000 \multiply\dimen1 by #4
+ \picture \dimen0 by \dimen1 (#3 scaled #4)}
+ }
diff --git a/info/digests/texline/no10/tl.tex b/info/digests/texline/no10/tl.tex
new file mode 100644
index 0000000000..c2a9c3f873
--- /dev/null
+++ b/info/digests/texline/no10/tl.tex
@@ -0,0 +1,28 @@
+\centerline{\bf\TeX line goes belatedly electronic}
+\smallskip
+\noindent
+In deference to many requests, \TeXline\ has finally gone electronic. I have
+lodged `copies' of the articles contained in \TeX line\ somewhere in the Aston
+Archive. These `archived' copies go back to issue 5, and may include the
+necessary support files to produce the newsletter. These support files are still
+developing, so each issue should be regarded as a single entity. In theory, it
+should be possible to reconstitute an issue. Note however that newer issues,
+prepared on my Macintosh, have a tendency to use Macintosh style file names (up
+to 32 characters, including spaces, back- and forward- slashes, etc.). File name
+extensions are not required on the Mac.
+
+How do you get hold of the files? Assuming you can connect to Aston, the files
+are in in the directories
+\begintt
+[tex-archive.digests.texline.no5]
+[tex-archive.digests.texline.no6]
+[tex-archive.digests.texline.no7]
+[tex-archive.digests.texline.no8]
+[tex-archive.digests.texline.no9]
+[tex-archive.digests.texline.no10]
+\endtt
+In each of these directories is |00files.txt|, which contains a list of the
+contents of the directory. There is also a |read.me| file in the
+|texline| directory, which might help.
+
+\rightline{\sl Malcolm Clark}
diff --git a/info/digests/texline/no10/tlx.tex b/info/digests/texline/no10/tlx.tex
new file mode 100644
index 0000000000..465434530d
--- /dev/null
+++ b/info/digests/texline/no10/tlx.tex
@@ -0,0 +1,70 @@
+\input texline
+\def\mwc{Malcolm Clark}
+\def\caption#1{\medskip\setbox0\hbox{\bf#1}\ifdim\wd0>\hsize
+\noindent{\bf#1}\else\centerline{\copy0}\fi}
+\def\item#1{\par\hangindent1em\hangafter1{\noindent\bf#1}}
+\def\itemitem#1{\par\hangindent2em\hangafter1{\noindent\enspace\bf#1\ }}
+\long\def\frame#1#2{\vbox{\dimen0=#1\multiply\dimen0 by2
+\advance\hsize by-\dimen0\hrule\hbox{\vrule\hskip#1\vbox
+{\multiply\tolerance by
+4\overfullrule0pt\parindent0pt\parskip#1
+\vskip#1{}#2\vskip#1}\hskip#1\vrule}\hrule}}
+\def\subsection#1{\medskip\leftline{$\bullet$\sl#1}\smallskip\ignorespaces}
+\def\rtr{\hbox to1em{\hfil$\triangleright$}}
+\def\LaTeXbf{{\bf L\kern-.36em\raise.3ex\hbox{\scb
+A}\kern-.15emT\kern-.1667em\lower.7ex\hbox{E}\kern-.125emX}}
+\def\DeK{D\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125em
+K}
+\def\LeX{L\kern-0.1667em\lower0.5ex\hbox{E}\kern-0.125em
+X}
+\let\Unix\unix
+\font\ttit=cmsltt10
+\def\bar{\vskip12pt plus9pt
+minus3pt\goodbreak{\noindent\hrule depth3pt}\smallskip}
+\abovedisplayskip1pt
+\belowdisplayskip1pt
+\brokenpenalty1000
+\clubpenalty=10000
+\widowpenalty=10000
+{\advance\vsize by0.5in\voffset-0.5in
+\bigcolheight=\vsize
+\advance\bigcolheight by\bigcolheight
+\advance\bigcolheight by 10pt
+\pageheight=\vsize
+\begindoublecolumns
+\input texline.head
+\input ed
+\enddoublecolumns
+\vfill\eject}
+\begindoublecolumns
+\input talk
+\bar\input rose
+\bar\input chris2
+\bar\input orin
+\bar\input nordic
+\bar\input meetings
+\bar\input dante
+\bar\input amiga
+\bar\input arch
+\bar\input aston
+\bar\input victor
+\bar\input ou
+\bar\input didot
+\bar\input ep90
+\bar\input groningen
+\bar\input cahiers
+\bar\input rowley
+\bar\input books
+\bar\input sgml
+\bar\input bsc-ep.cals
+\bar\input acog
+\bar\input tex88
+\bar\input tl
+\bar\input new
+\bar\input good_guys
+\vskip 0pt plus1filll
+\frame{5pt}{\dots combining the ease of
+use of \TeX\ with the power of {\it wysiwyg}\dots
+\hfill\it Leslie Lamport}
+}\enddoublecolumns
+\bye
diff --git a/info/digests/texline/no10/verbar.tex b/info/digests/texline/no10/verbar.tex
new file mode 100644
index 0000000000..4f35eb46ac
--- /dev/null
+++ b/info/digests/texline/no10/verbar.tex
@@ -0,0 +1,33 @@
+% verbatim macros from the TeXbook
+\newskip\ttglue
+\ttglue=0.5em plus 0.25em minus 0.15em
+\outer\def\begindisplay{\obeylines\startdisplay}
+{\obeylines\gdef\startdisplay#1
+ {\catcode`\^^M=5$$#1\halign\bgroup\indent##\hfil&&\qquad##\hfil\cr}}
+\outer\def\enddisplay{\crcr\egroup$$}
+% macros for verbatim scanning
+\chardef\other=12
+\def\ttverbatim{\begingroup
+ \catcode`\\=\other
+ \catcode`\{=\other
+ \catcode`\}=\other
+ \catcode`\$=\other
+ \catcode`\&=\other
+ \catcode`\#=\other
+ \catcode`\%=\other
+ \catcode`\~=\other
+ \catcode`\_=\other
+ \catcode`\^=\other
+ \obeyspaces \obeylines \tt}
+{\obeyspaces\gdef {\ifvmode\indent\fi\space}}% a little extra
+
+\outer\def\begintt{$$\let\par=\endgraf \ttverbatim \parskip=0pt
+ \catcode`\|=0 \rightskip-5pc \ttfinish}
+{\catcode`\|=0 |catcode`|\=\other % | is temporary escape character
+ |obeylines % end of line is active
+ |gdef|ttfinish#1^^M#2\endtt{#1|vbox{#2}|endgroup$$}}
+
+\catcode`\|=\active
+{\obeylines \gdef|{\ttverbatim \spaceskip\ttglue \let^^M=\ \let|=\endgroup}}
+
+
diff --git a/info/digests/texline/no10/victor.tex b/info/digests/texline/no10/victor.tex
new file mode 100644
index 0000000000..bfbe876143
--- /dev/null
+++ b/info/digests/texline/no10/victor.tex
@@ -0,0 +1,124 @@
+\centerline{\bf And now for something completely {\tt\char'134else}}
+\smallskip
+\noindent
+Over the years I have programmed in a number of languages
+(this does not include Basic!), and every once in a while
+I had occasion to ponder their conceptual differences.
+Such reflection need not be a sign of intellectual
+maturity, by the way.
+I still recall with shame coming back to Lisp after a year
+of {\sc Fortran}, and attempting -- futilely! --
+to do call-by-reference parameter passing\dots\
+
+A remnant of my Algol68 years is the desire to write
+code like
+\begintt
+If something Then a Else b Fi :=5;
+\endtt
+which to me is superior to, as well as conceptually more
+correct than,
+\begintt
+If something Then a:=5 Else b:=5 Fi;
+\endtt
+Would such a thing be possible in \TeX?
+
+Let the following macros be given.
+\begintt
+\def\bold#1{{\bf #1}}
+\def\slant#1{{\sl #1}}
+\def\kill#1{}
+\endtt
+Now let's make some examples. The first one.
+\begintt
+\ifnum1>0 \bold \fi {word} \bye
+\endtt
+The `word' appears in roman type, and the log file doesn't give
+any further clue as to what happens.
+If you switch on |\tracingmacros|, however, you see that |\bold|
+did get an argument: it got the |\fi|!
+
+Example number two.
+\begintt
+\ifnum1>0 \bold
+ \else \slant \fi {word} \bye
+\endtt
+Now `word' is bold but the log file says that
+`end occured in group at level~1'.
+This is a tricky one.
+Ask yourself: which closing brace got lost?
+And where did it do so?
+Let's just expand: |\bold| got hold of the |\else|,
+so in the next step the input to \TeX's
+gastro-intestinal tract looks like
+\begintt
+\ifnum1>0 {\bf \else } \slant \fi
+\endtt
+and as the condition is true, everything between |\else| and
+|\fi| will be skipped, including the closing brace.
+Note that we have managed to
+throw something to the other side of the |\else|!
+
+The next example should be understandable by now:
+\begintt
+\ifnum1<0 \bold
+ \else \kill \fi {word} text \bye
+\endtt
+this gives `end occured before |\ifnum| was complete'.
+
+So, is there no \TeX\ equivalent of that Algol construct?
+Well this is a way out:
+\begintt
+\ifnum1>0 \let\next=\bold
+ \else \let\next=\kill \fi
+ \next {word} text \bye
+\endtt
+but, this also works:
+\begintt
+\ifnum1>0 \expandafter \bold
+ \else \expandafter \kill \fi
+ {word} text \bye
+\endtt
+We will have to look at this last one a bit closer.
+From the first two examples we know that the lexical expansion
+of |\else| and |\fi| is empty, so what would happen in the following
+case?
+\begintt
+\ifnum1>0 \expandafter \bold
+ \else {word} \fi {text} \bye
+\endtt
+It is not so that `expanding away' the else gives `word' as
+argument to |\bold|.
+
+The following explanation would be imaginable:
+maybe \TeX\ skips the `false
+text' as soon as it sees the |\else|. This might be possible,
+as no expansion is involved in the skipping.
+In particular, the |\fi| cannot be the result of a macro
+expansion, it really has to be standing there.
+We can test that this is indeed the case
+with a final example:
+\begintt
+\def\hello{\message{hello}}
+\ifnum1>0 \expandafter \hello
+ \else \message{goodbye} \bye
+\endtt
+Now \TeX\ sees the |\else| before the `hello' message, so it
+can start skipping at that very moment.
+You can deduce that it does so,
+because it doesn't greet you before giving
+the error message for the missing |\fi|.
+
+All of this means that conditionals in \TeX\ are rather
+more complicated than in ordinary programming
+languages, but they can be understood once you
+realise that: (1)~|\else| and |\fi| are
+ordinary tokens; and (2)~for true conditions,
+the `false text' is skipped as soon as
+the |\else| has been located.
+
+\rightline{\sl Victor Eijkhout}
+
+
+
+
+