TEX-NL archief mei 1991

Inhoudsopgave

Wed, 1 May 91 02:17:52 CET: Twee kolommen
Wed, 1 May 91 10:03:00 MET: RE: New files in TEX-NL filelist
Wed, 1 May 91 11:09:00 MET: RE: Twee kolommen
Wed, 1 May 91 11:16:29 +0000: Reply to Twee kolommen
Wed, 1 May 91 11:40:50 met: RE: Twee kolommen
Wed, 1 May 91 11:24:04 CDT: RE: Twee kolommen
Wed, 1 May 91 12:54:09 MET: RE: Twee kolommen
Fri, 3 May 91 14:25:12 +0000: dvips + fontlibraries
Fri, 3 May 91 19:41:00 MET: New files on LISTSERV@HEARN
Mon, 6 May 91 07:33:49 +0000: RE: dvips + fontlibraries
Mon, 6 May 91 11:48:12 CDT: Bomen afbeelden
Mon, 6 May 91 14:37:00 +0100: RE: Bomen afbeelden
Mon, 6 May 91 14:48:00 MET: RE: Bomen afbeelden
Mon, 6 May 91 15:24:54 met: RE: Bomen afbeelden
Mon, 6 May 91 15:53:00 MET: (no subject)
Mon, 6 May 91 14:53:59 -0500: (no subject)
Mon, 6 May 91 16:18:40 METDST: Re : bomen
Tue, 7 May 91 08:51:00 GMT: Braille.xxx disappear from Heidelberg?
Tue, 7 May 91 12:07:20 MET: (no subject)
Tue, 7 May 91 09:26:44 +0000: And now for something completely different ...
Tue, 7 May 91 17:38:39 met: RE: Braille.xxx disappear from Heidelberg?
Mon, 6 May 91 15:30:38 met: Bomen afbeelden
Wed, 8 May 91 10:00:00 MET: dvips547
Wed, 8 May 91 13:44:00 MET: Volunteers asked for contributions NTG's fall meeting,
Wed, 8 May 91 16:42:00 MET: RE: dvips547
Thu, 9 May 91 14:19:51 CDT: MF vraag
Wed, 15 May 91 17:24:00 N: request for international co-operation
Thu, 16 May 91 00:46:00 GMT: Info 6e European TeX Conference 23-26 september Parijs
Thu, 16 May 91 01:10:00 GMT: NTG board; new member
Wed, 22 May 91 07:54:00 MET: Announcing the babel system of style options
Wed, 22 May 91 07:56:00 MET: new on tex-nl filelist
Thu, 23 May 91 11:49:00 MET: Just for those of us who have severe questions
Thu, 23 May 91 16:41:30 CET: Re:Announcing the babel system
Thu, 23 May 91 18:10:00 MET: RE: Re:Announcing the babel system
Mon, 27 May 91 14:50:43 MET: Nederlandse bibliografiestijl
Mon, 27 May 91 17:03:00 MET: babel updates
Tue, 28 May 91 14:27:00 MET: babel
Thu, 30 May 91 16:29:00 MET: I think this is a bug in LaTeX
Thu, 30 May 91 22:20:00 MET: I think this is a feature in LaTeX
Fri, 31 May 91 11:12:00 N: RE: I think this is a bug in LaTeX


Date:Wed, 1 May 91 02:17:52 CET
From:    Maurits Wijzenbeek <A401WIJZ AT HASARA11.BITNET>
Subject:   Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>



Ik wil een periodiek in twee kolommen zetten. Daarbij moet het mogelijk
zijn om op een pagina om te schakelen van een naar twee kolommen en weer
terug.
De \twocolumn - \onecolumn opdrachten in LaTeX beginnen steeds een nieuwe
pagina en zijn dus niet geschikt. In het TeX-Book staat op blz. 386-388
een voorbeeld, maar dat kan ik niet goed aan de praat krijgen: ik krijg
duistere foutmeldingen en de paginanummers zijn zoek of staan op een
ongewenste plaats.

Weet iemand raad?
                               Maurits Wijzenbeek

Vakgroep Experimentele Fysica.
Valckenierstraat 65
1018 XE  Amsterdam
EARN/Bitnet: MWIJZ AT SARA.NL




Date:Wed, 1 May 91 10:03:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   RE: New files in TEX-NL filelist
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


        "Jian AT Hdetud11.Bitnet" <JIAN AT HDETUD11.TUDELFT.NL> vroeg naar het
        adres van de fileserver in Nijmegen: LISTSERV@HEARN

        Piet van Oostrum vroeg naar supertabular.doc, terecht, ik had de
        verkeerde (gestripte) versie van supertabular op de server gezet.
        Ik heb zojuist de gedocumenteerde versie van de file naar Nijmegen
        gestuurd.

        Johannes Braams

PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams AT pttrnl.nl
-------------------------------------------------------------------------------




Date:Wed, 1 May 91 11:09:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   RE: Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Maurits Wijzenbeek <A401WIJZ AT HASARA11.BITNET> schrijft:
>
> Ik wil een periodiek in twee kolommen zetten. Daarbij moet het mogelijk
> zijn om op een pagina om te schakelen van een naar twee kolommen en weer
> terug.
> De \twocolumn - \onecolumn opdrachten in LaTeX beginnen steeds een nieuwe
> pagina en zijn dus niet geschikt. In het TeX-Book staat op blz. 386-388
> een voorbeeld, maar dat kan ik niet goed aan de praat krijgen: ik krijg
> duistere foutmeldingen en de paginanummers zijn zoek of staan op een
> ongewenste plaats.
>
> Weet iemand raad?

        Jazeker, gebruik de multicol style-optie van Frank Mittelbach
        en Rainer Schoepf. Beschreven in TUGboat (vorig jaar, ik weet uit
        mijn hoofd niet welk nummer), verkrijgbaar in Nijmegen (meen ik),
        Utrecht (denk ik, klopt dat Piet?), Heidelberg (LISTSERV@HEARN,
        files MULTICOL README, MULTICOL ZOOUUE01 en MULTICOL ZOOUUE02).
        Verder op nog wel een paar plaatsen.
        De versie in Nijmegen is mogelijk wat verouderd, die in Heidelberg
        is altijd de meest recente.


        Johannes Braams

PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams AT pttrnl.nl
-------------------------------------------------------------------------------




Date:Wed, 1 May 91 11:16:29 +0000
From:    winnink AT ECN.NL
Subject:   Reply to Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>
>RFC-822-HEADERS:
>Return-Path: <guest@enrdt1>
>Received: from HEARN.BITNET by ECN.NL; Wed, 1 May 91 10:45 GMT
>Sender: TEX-NL <TEX-NL AT hearn.bitnet>
>Ik wil een periodiek in twee kolommen zetten. Daarbij moet het mogelijk
>zijn om op een pagina om te schakelen van een naar twee kolommen en weer
>terug.
>De \twocolumn - \onecolumn opdrachten in LaTeX beginnen steeds een nieuwe
>pagina en zijn dus niet geschikt. In het TeX-Book staat op blz. 386-388
>een voorbeeld, maar dat kan ik niet goed aan de praat krijgen: ik krijg
>duistere foutmeldingen en de paginanummers zijn zoek of staan op een
>ongewenste plaats.
>
>Weet iemand raad?
>                               Maurits Wijzenbeek
>
>Vakgroep Experimentele Fysica.
>Valckenierstraat 65
>1018 XE  Amsterdam
>EARN/Bitnet: MWIJZ AT SARA.NL
Maurits,
     Er bestaat een MULTICOL style van Mittelbach, die de gewenste
mogelijkheden biedt.
     Ik denk dat ze beschikbaar is o.a. op de server in Utrecht. Voorzover
ik er wat mee heb gedaan werkt het prima.
        Jos Winnink                Central Planning Bureau
                                   Applied Mathematics & Computer Science Dept.
                                   v Stolkweg 14
                           2586 VL The Hague
                                   The Netherlands


     phone +31 70 3514151
     fax   +31 70 3505847            Internet:    winnink AT ecn.nl


   "If architects built buildings the way programmers build programs,
    then the first woodpecker to appear would destroy civilization"




Date:Wed, 1 May 91 11:40:50 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   RE: Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>>>>> Maurits Wijzenbeek <A401WIJZ AT HASARA11.BITNET> (MW) schrijft:

MW> Ik wil een periodiek in twee kolommen zetten. Daarbij moet het mogelijk
MW> zijn om op een pagina om te schakelen van een naar twee kolommen en weer
MW> terug.
MW> De \twocolumn - \onecolumn opdrachten in LaTeX beginnen steeds een nieuwe
MW> pagina en zijn dus niet geschikt. In het TeX-Book staat op blz. 386-388
MW> een voorbeeld, maar dat kan ik niet goed aan de praat krijgen: ik krijg
MW> duistere foutmeldingen en de paginanummers zijn zoek of staan op een
MW> ongewenste plaats.

De multicolumn optie van Mittelbach en Schoepf geeft deze mogelijkheden.

How to get multicol.zoo from the archive at
        Dept. of Computer Science, Utrecht University:

NOTE: In the following I have assumed your mail address is john AT highbrow.edu.

    Of course you must substitute your own address for this. This should be
    a valid internet or uucp address. For bitnet users name AT host.BITNET
    usually works.

by FTP: (please restrict access to weekends or evening/night (i.e. between
about 20.00 and 0900 UTC).

    ftp archive.cs.ruu.nl [131.211.80.5]
    user name: anonymous or ftp
    password: your own email address (e.g. john AT highbrow.edu)
    cd /pub
    don't forget to set binary mode if the file is a tar/arc/zoo archive,
    compressed or in any other way contains binary data.
    get TEX/latexstyle/multicol.zoo

by mail-server:

send the following message to
mail-server AT cs.ruu.nl (or uunet!mcsun!hp4nl!ruuinf!mail-server):

    begin
    path john AT highbrow.edu (PLEASE SUBSTITUTE *YOUR* ADDRESS)
    send TEX/latexstyle/multicol.zoo
    end

NOTE: *** PLEASE USE VALID INTERNET ADDRESSES IF POSSIBLE. DO NOT USE
ADDRESSES WITH ! and @ MIXED !!!! BITNETTERS USE USER AT HOST.BITNET ***

The path command can be deleted if we receive a valid from address in your
message. If this is the first time you use our mail server, we suggest you
first issue the request:
    send HELP
--
Piet* van Oostrum, Dept of Computer Science, Utrecht University,
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands.
Telephone: +31 30 531806   Uucp:   uunet!mcsun!ruuinf!piet
Telefax:   +31 30 513791   Internet:  piet AT cs.ruu.nl   (*`Pete')




Date:Wed, 1 May 91 11:24:04 CDT
From:    Erik-Jan Vens <erikjan AT ICCE.RUG.NL>
Subject:   RE: Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Maurits Wijzenbeek schrijft:
> De \twocolumn - \onecolumn opdrachten in LaTeX beginnen steeds een nieuwe
> pagina en zijn dus niet geschikt. In het TeX-Book staat op blz. 386-388

Gebruik Frank Mittelbach's <multicol.sty>. Hiermee kun je heen-en-weer
switchen tussen een- en tweekoloms materiaal.

Je kunt deze style-file o.a. vinden in Utrecht.

Erik-Jan.

--

Erik-Jan Vens.    erikjan AT icce.rug.nl
                  erikjan AT guicce.uucp
                  {...!hp4nl!}rug4!guicce!erikjan

ICCE (Interdisciplinary Centre for the development of
      Computercoaches and Expertsystems)
Rijksuniversiteit Groningen
PObox 800
9700 AV  Groningen
the Netherlands.




Date:Wed, 1 May 91 12:54:09 MET
From:    "P. Wackers" <U216002 AT HNYKUN11.BITNET>
Subject:   RE: Twee kolommen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Haal multicol.readme en multicol.arcuue van de server in Nijmegen
(listserv@hearn)
Groeten,
Paul Wackers




Date:Fri, 3 May 91 14:25:12 +0000
From:    winnink AT ECN.NL
Subject:   dvips + fontlibraries
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,
    Ik ben er eindelijk toegekomen om DVIPS (onder MS-DOS) te testen met
FONTLIBRARIES (.fli files). In het verleden heb ik gemeld dat DVIPS alleen
kan werken met het "nieuwe type" fontlibraries, maar ik had dat niet getest.
    Resultaat van de test: HET WERKT UITSTEKEND.
Mensen, die een emTeX implementatie hebben met de oude fontlibraries +
bijbehorenden DVI-drivers en die DVIPS willen gebruiken, kan ik op dit
moment wel aan een UPDATE van hun systeem helpen. Laat het dan even weten.
        Jos Winnink                Central Planning Bureau
                                   Applied Mathematics & Computer Science Dept.
                                   v Stolkweg 14
                           2586 VL The Hague
                                   The Netherlands


     phone +31 70 3514151
     fax   +31 70 3505847            Internet:    winnink AT ecn.nl


   "If architects built buildings the way programmers build programs,
    then the first woodpecker to appear would destroy civilization"




Date:Fri, 3 May 91 19:41:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   New files on LISTSERV@HEARN
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Hallo,

        Ik heb de volgende files op de server vernieuwd, cq toegevoegd:

        HYPHEN1 TEX     Vanwege een wijziging in het telefoonnummer
        HYPHEN2 TEX     van CELEX
        HYPHEN3 TEX     Op veler verzoek de patronen van Vanroose terug

        MULTICOL README Uptodate met Heidelberg gebracht
        MULTICOL.ZOOUUE01
        MULTICOL.ZOOUUE02 Deze twee files vervangen MULTICOL.ARCUUE.

        CHNGBARS STY    Versie 2.2d, nu voor DVIps resolutie onafhankelijk,
                        toegevoegd commando \outerbarstrue om de changebars
                        aan de buitenkant van de tekst te krijgen.


        Johannes Braams




Date:Mon, 6 May 91 07:33:49 +0000
From:    N.POPPELIER AT ELSEVIER.NL
Subject:   RE: dvips + fontlibraries
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Jos,

ik heb vorige week de emTeX-schoenendoos ontvangen en ben dus ook wel
geinteresseerd in welke update er ook maar is bijgekomen in de tijd na het
het land in sturen van de doos.

Nico




Date:Mon, 6 May 91 11:48:12 CDT
From:    Erik-Jan Vens <erikjan AT ICCE.RUG.NL>
Subject:   Bomen afbeelden
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Goeie,

  wie, o wie, frist mijn geheugen op. In mijn achterhoofd zit de gedachte dat
er een set macro's is om makkelijk boom structuren a la:

     S
    / \
   /   \
 NP     VP

te kunnen maken.

Ja?????

Erik-Jan.

--

Erik-Jan Vens.    erikjan AT icce.rug.nl
                  erikjan AT guicce.uucp
                  {...!hp4nl!}rug4!guicce!erikjan

ICCE (Interdisciplinary Centre for the development of
      Computercoaches and Expertsystems)
Rijksuniversiteit Groningen
PObox 800
9700 AV  Groningen
the Netherlands.




Date:Mon, 6 May 91 14:37:00 +0100
From:    KNAPPEN AT VKPMZD.KPH.UNI-MAINZ.DE
Subject:   RE: Bomen afbeelden
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Op de ymir.claremont.edu staat chomsky.sty.
jk




Date:Mon, 6 May 91 14:48:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   RE: Bomen afbeelden
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


        Erik-Jan vroeg naar macros om bomen te kunnen tekenen.
        Anne Brueggemann-Klein heeft een pakket geschreven voor binaire
        bomen. Het is verkrijgbaar op de server in duitsland, of (op speciaal
        verzoek voor niet al te veel mensen) bij mij. Hieronder de readme.doc
        file die meegeleverd wordt met het pakket.

        Johannes
------------------------------------------------------------------------------
TreeTeX is a public domain macro package for drawing
trees with TeX. It may be freely distributed, provided
that the following files are kept together:

  classes.tex, l_pic.tex, readme, tree_doc.aux, tree_doc.bbl
  tree_doc.dvi, tree_doc.tex, treetex.tex

Note (listserv mangement): readme is named readme.doc,
     tree_doc.aux and tree_doc.dvi has been removed
     because of errors.

Copyright is with Anne Brueggemann-Klein and Derick Wood.

All remarks, bug reports etc. should be directed to

  Dr. Anne Brueggemann-Klein
  Institut fuer Informatik
  Rheinstr. 10--12
  7800 Freiburg, West Germany

  email: abk AT sun1.ruf.uni-freiburg.dbp.de






Date:Mon, 6 May 91 15:24:54 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   RE: Bomen afbeelden
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>>>>> Erik-Jan Vens <erikjan AT icce.rug.nl> (EJV) schrijft:

EJV>   wie, o wie, frist mijn geheugen op. In mijn achterhoofd zit de gedachte d
   at
EJV> er een set macro's is om makkelijk boom structuren a la:
EJV>
EJV>      S
EJV>     / \
EJV>    /   \
EJV>  NP     VP
EJV>
EJV> te kunnen maken.

Date: Tue, 4 Apr 89 11:51:35 EDT
From: pfkrause AT ATHENA.MIT.EDU
Reply-To: pfkrause AT wheaties.ai.mit.edu
Subject: Wanted: tree formatter
Keywords: LaTeX, tree formatter

Here's a problem that's both new and hard, at least so far as I know.
What I want to produce is something like this:

                                 S
                                / \
                             NP     VP
                            / \    /  \
                           Det N   V   NP
                           |   |   |   / \
                          The man saw Det N
                                       |  |
                                       a boy

(probably using the slanted lines from LaTeX's \picture font),
with an input something like this:

\tree{S}{\tree{NP}{\tree{Det}{The}%
                   \tree{N}{man}}%
         \tree{VP}{\tree{V}{saw}%
                   \tree{NP}{\tree{Det}{a}}%
                             \tree{N}{boy}}}

(if you can think up a better input format, I'd be happy to take that
too).  Does anybody have an approximation to such a monster, or think
that they could write it?  My thesis thanks you.  I thank you.

                                        -paul
                                        pfkrause AT wheaties.ai.mit.edu

Date: Fri, 12 May 89 11:29 N
From: <GENT%HTIKUB5.BITNET AT UWAVM.ACS.WASHINGTON.EDU>
Subject: Re: tree formatter
Keywords: tree formatting, linguistic theories

(Reply to question of -paul(?) about formatting tree structures that are
used in documents on linguistic theories.)

I have been trying to solve this problem about a year ago.
After shaking my brains doing the job in LaTeX I decided to make an
'external' program that would convert ascii-files into LaTeX source
files (picture environment). This program PICT (in VAX PASCAL) turned out to
work really perfect and very quickly. It can make complex tree structures,
flowcharts and tables in as much time as you need typing it in plain ascii.
If you are interested in this way of formatting your tree structures
please contact me:

          Joop van Gent
          Institute for Language Tecnology and
          Artificial Intelligence, Holland
          GENT@HTIKUB5 (EARN)

Date: Thu, 6 Dec 90 11:07:55 -0800
From: isozaki <isozaki AT penguin.Stanford.EDU>
Subject: Trees and bipartite graphs in LaTeX
Keywords: LaTeX, Trees and bipartite graphs

        I submitted two style files for node&edge graphs
to Clarkson archive. One is for trees, and the other is
for bipartite graphs. And they depend on epic/eepic.
You can find them as nodeedge.shar in pub/tex/latex-style.

Hideki ISOZAKI
Stanford Univ. and NTT Basic Research Labs.

>>> On RUU in TEX/latexstyle/nodeedge.shar


Tugboat March 1985

         David Eppstein, Trees in \TeX

>>> On RUU in TEX/tugboat/tb0tree.tex, TEX/tugboat/treedef.tex

On ASTON:

From: Sebastian Rahtz <spqr AT uk.ac.soton.ecs>
Date: Mon, 19 Jun 89 15:14:10 BST
Message-Id: <15620.8906191414 AT hilliard.ecs.soton.ac.uk>
Subject: TreeTeX
Cc: archivegroup AT uk.ac.aston

A set of new TeX macros for drawing trees has been installed in the
archive; they are in

 [tex-archive.tex-style.treetex]

and the file names are listed in the README, reproduced below.

Sebastian Rahtz

TreeTeX is a public domain macro package for drawing
trees with TeX. It may be freely distributed, provided
that the following files are kept together:

  README
  epodd.bbl
  epodd.tex
  tree_doc.bbl
  tree_doc.tex
  classes.tex
  l_pic.tex
  treetex.tex

Copyright is with Anne Brueggemann-Klein and Derick Wood.

All remarks, bug reports etc. should be directed to

  Dr. Anne Brueggemann-Klein
  Institut fuer Informatik
  Rheinstr. 10--12
  7800 Freiburg, West Germany

  email: abk AT sun1.ruf.uni-freiburg.dbp.de

The following new items may be noted in the archive
(all under [TEX-ARCHIVE])

 [.tex-style]trees.tex  Macros for drawing trees (compatible with LaTeX)
 [.tex-style]tugtree.tex Article relating to former

These are not really very new, they have just been extracted from
other places and installed where they wil be more visible.

Sebastian Rahtz, Southampton

        tree.sty is NOT Bruggeman-Klein, but another, simpler system

        tree.sty should be [tex-archive.latex.contrib]trees.sty, a misspelling
        appeared somewhere. my apologies

        Sebastian Rahtz




Date:Mon, 6 May 91 15:53:00 MET
From:    DRUNEN AT RUG.NL
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo !

Wie o Wie kan mij vertellen waar ik de EXACTE definitie van een DVI file
kan vinden ( formaat, commando-bytes etc....)

Bij voorbaat dank.

Rudi van Drunen

Rudi AT cs.rug.nl
DRUNEN AT HGRRUG5.bitnet




Date:Mon, 6 May 91 14:53:59 -0500
From:    eijkhout AT CSRD.UIUC.EDU
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Het dvi formaat is gedefinieerd in 'TeX: the program' (pg 234 ev),
deel B in de serie 'Computers and Typesetting'
van Donald E. Knuth. Het is ooit ook gepubliceerd
geweest in TUGboat, maar dat was niet meer dan
een overdruk uit bovengenoemde bron.

Het dvi formaat is niet veranderd bij de overgang op
TeX3, dus de broncode mag verouderd zijn in dat boek,
wat je zoekt is er nog steeds te vinden.

Victor Eijkhout
 Center for Supercomputing Research and Development
 University of Illinois at Urbana-Champaign
 305 Talbot Laboratory                 phone: +1 217 244-0047 (office)
 104 South Wright Street                      +1 217 356-0876 (home)
 Urbana, Illinois 61801-2932, USA        fax: +1 217 244-1351

home: 2503 W. Springfield Av, Apt. K-4, Champaign 61821, USA






Date:Mon, 6 May 91 16:18:40 METDST
From:    Ton Biegstraaten <abi AT DUTIBA.TUDELFT.NL>
Subject:   Re : bomen
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>   wie, o wie, frist mijn geheugen op. In mijn achterhoofd zit de gedachte dat
> er een set macro's is om makkelijk boom structuren a la:
>
>      S
>     / \
>    /   \
>  NP     VP
>
> te kunnen maken.

Er is een pakket `tree' dat een of andere slimme inputfile leest en daar
TeX van maakt.
De bomen zien er anders uit dan bovenstaand:
       S
       |
   ----------
   |        |
   |        |
  NP        VP

En dan mooi getekend.
Het draait hier op een sun3 onder SUNOS 4.1.?
het is van :
lee AT uhccux.uhcc.hawaii.edu

Ton

--
Name: Ton Biegstraaten                          Tel : +3115785269
Org.: TU Delft                                  Fax : +3115786522
      Julianalaan 132                           Mail: abi AT dutiba.tudelft.nl
      2628 BL Delft, The Netherlands




Date:Tue, 7 May 91 08:51:00 GMT
From:    "Gerard van Nes, ENR-Petten" <VANNES AT ECN.NL>
Subject:   Braille.xxx disappear from Heidelberg?
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Hallo,

Een jaar geleden stond op textools filelist van Heidelberg het braille
pakket.
Mogelijk gelijk met de reorganisatie is deze module verdwenen?

Waar is het nu te vinden?

Gerard van Nes

Z




Date:Tue, 7 May 91 12:07:20 MET
From:    Piet Tutelaers <rcpt AT URC.TUE.NL>
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

[ DRUNEN AT RUG.NL (May  6, 23:00):
> Hallo !
>
> Wie o Wie kan mij vertellen waar ik de EXACTE definitie van een DVI file
> kan vinden ( formaat, commando-bytes etc....)
>
> Bij voorbaat dank.

Dag Rudi,

Als je de beschikking hebt over dvitype.web en weave dan kun je als volgt
een afdruk maken van dvitype.web:
        weave dvitype.web       (dan krijg je dvitype.tex)
        tex dvitype.tex         (hier heb je manmac.tex voor nodig)

De resulterende dvitype.dvi file kun je afdrukken. Hierin staat
ongetwijfeld wat het formaat is van een dvi-file. Maar je zult er wel wat
tijd voor nodig hebben om erachter te komen. Je kunt natuurlijk ook dvitype
loslaten op een .dvi file. Je krijgt dan te zien wat er zoal in een dvi
file staat.

Geef je een seintje als je de .dvi file formaat kent? Ik heb dan een paar
leuke vragen voor je!

--Piet




Date:Tue, 7 May 91 09:26:44 +0000
From:    N.POPPELIER AT ELSEVIER.NL
Subject:   And now for something completely different ...
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


.. ik misbruik deze lijst even voor het volgende. Onder de TeX-gebruikers
in Nederland zitten vast gebruikers van Sun werkstations. Met die mensen zou
ik graag in contact komen.

Antwoorden niet naar deze lijst, maar rechtstreeks naar het adres in
onderstaande `signature'.

Bedankt,

Nico

----------------------------------------------------------------------
Dr. Nico A.F.M. Poppelier
Elsevier Science Publishers, APD, R&D Department
Sara Burgerhartstraat 25, 1055 KV Amsterdam, The Netherlands
Phone: +(20)5862504. Fax: +(20)5862425. Email: n.poppelier AT elsevier.nl




Date:Tue, 7 May 91 17:38:39 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   RE: Braille.xxx disappear from Heidelberg?
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>>>>> "Gerard van Nes, ENR-Petten" <VANNES AT ecn.nl> (GvN) schrijft:

GvN> Een jaar geleden stond op textools filelist van Heidelberg het braille
GvN> pakket.
GvN> Mogelijk gelijk met de reorganisatie is deze module verdwenen?
GvN>
GvN> Waar is het nu te vinden?

Op de ftp-server van de universiteit van Stuttgart:

info/tex/stylefiles:
-rw-r--r--  1 infoadm      9555 Feb  6  1989 braille.1500pk
-rw-r--r--  1 infoadm     61500 Feb  6  1989 braille.1500pxl
-rw-r--r--  1 infoadm      1741 Feb  6  1989 braille.sty
-rw-r--r--  1 infoadm       573 Feb  6  1989 braille.tfm

Piet van Oostrum <piet AT cs.ruu.nl>




Date:Mon, 6 May 91 15:30:38 met
From:    Harmen van den Berg <hvdberg AT MATH.UTWENTE.NL>
Subject:   Bomen afbeelden
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Dat klopt. Dit is de readme van deze macroset, die vast wel op een aantal server

Harmen van den Berg
Toegepaste Wiskunde
Universiteit Twente
Enschede




                        *                             *
                                  Announcement
                        *        ///////\\\\\\        *
                                /             \
                        *  Tree Drawing      Program  *
                                \             /
                        *        \\\\\\\//////        *
                                   Available
                        *                             *

The above is from the following tree-definition:

                        \tree -b9
(
(*(*\O(*\O(*\O(*\O)))))
        ((Announcement\O(Available\I\O (Tree Drawing()) (\ \ \ \ Program()) ) ))
(*(*\O(*\O(*\O(*\O)))))
)


The `tree' program formats trees for screen display or printing with
TeX.  The program, supporting utilities, and accompanying documents are
free and in the public domain.  If you distribute a modified version of
`tree', please keep your version in the public domain.

The predecessor program to this was written by Chris Barker, the
Linguistics Board at University of California, Santa Cruz, email:
barker AT ling.ucsc.edu.

This version has been tested only on Unix:  SunOS 3.5 and Ultrix 3.1.
It requires the `lex' utility to compile, or else `flex', which is the
free version of Unix `lex' by Vern Pacson.  The Makefile is set up to
use `flex'.  To compile the source, type "make", which will process the
source code with flex then will invoke the C compiler.  This creates 3
programs:  `tree', `tpar', and `unpar'.  The last two are minor
utilities that you may not have any need for; they are described below.

Basic usage for screen display is:  "tree textfile", where the
textfile has some trees.  After you've made the program, try displaying
the example files with:

        % tree sample
        % tree texsample

The texsample file is intended to illustrate printed output using TeX,
which you can get with the following (adapted for your local conventions
for using TeX and printing):

        % tree -t texsample > texsample.tex
        % tex texsample
        % lpr -d texsample.dvi

And you can follow the similar procedure for the file sample.  This
should get you printout of trees done with horizontal and vertical
lines.  If you have a PostScript printer, the following may work to get
trees made with slanty lines:

        % tree -u texsample > texsample.tex
        % tex texsample
        % lpr -d texsample.dvi

That is, everything the same, except use `-u' instead of `-t'.  (`-t' is
for TeX; the only logic to the `-u' is that `u' comes after `t'.) If
this last doesn't work right, the most likely thing to have gone wrong
is that your local PostScript driver program does not treat TeX \special
commands, which I've used to embed PS code, in the same way that mine
does.  If that's a problem, there are two things you can do about it.
(1) Find out what should be in a TeX \special to tell your driver to
just spit out literally into its output whatever it finds in a \special,
then modify the C code in the source tex.c accordingly (see `SKEY' in
the code), or (2) email me and I'll send you my PS driver program (which
is a modification of the free dvi2ps program from MIT).

The Makefile also provides for "make tex" to create TeXable files
use.tex, sample.tex, texsample.tex, and ptsample.tex for a sort of
user manual and some sample output.  If you can't get the `-u'
option to work, you can change the definition of UT in the
Makefile to -t.

Tree has some options for modifying or decorating trees in
various ways.  Some of these can be used either for all the trees in a
source text file by giving the option on the command line after `tree',
or for some individual tree by giving the option after the `\tree' command
within the text file.  For instance, if the text has

        \tree -t (S (Q (did) (V' (you go))))

then TeX code will be generated for this particular tree in the
text, but not necessarily for other trees in that text file.  Here
is another example:

        % tree -L < filename
        \tree -L (S(NP(N(features)))(V'(V(galore))))

The first Unix command will have `tree' omit all connecting lines under
nodes for all trees in the file `filename'.  The second, as a line in a
text file processed by tree, will do that for just the one tree that
follows.  There are other options that apply just to single nodes within
a tree, which are given as backslash plus some capital letter.  As it
happens, in this instance there is an option \L for individual nodes,
also:

        \tree (S(NP(N\L(features)))(V'(\L V(galore))))

which omits lines under just the two nodes `N' and `V'.  The second \L
in this example has to be separated by a space from the following V so
`tree' can tell that this is not a TeX command with the name `LV'.  (If
it happens that you need to use a TeX command with the name `L' in a
node, you could use \\L for this, but it is necessary to use \\ for
TeX commands only in such cases of conflict.)

Here is a reference list of the options or commands for formatting
individual nodes.  (See the man page and use.tree for more info.)

          Command:      Option: Function:

        \D "daughter"           label discontinuous daughter
        \E "even"         -E    select basis for flatten command
        \F "flatten"      -F    move nodes to lowest level
        \H "head"               center mother over this daughter
        \I "invert"       -I    turn tree upside down
        \L "lexical"      -L    don't put lines under nodes
        \M "mother"             label mother of discontinuous daughter
        \O "omit"         -O    omit line above nodes
        \P "phantom"            as "omit" but retain spacing
        \T "triangle"     -T    put triangles under nodes
                          -g<n> use n as the minimal gap between nodes
                          -b<n> do shaded triangles or lines (see below)
                          -v    don't suppress TeX commands on screen

All commands of the form backslash plus capital letter `tree' assumes
are intended for it, and it eats them up without comment, even though
in most cases they don't do anything.

The option `-b<n>' has different effects depending on output is
tty-style or TeX code.  The sample files have examples for the latter.
For tty output, here is a series of trees showing how the connecting
"lines" can be varied.  These are from the tree definition

  \tree (black=<n>(family\T(Martha Henry))(uncle)(aunt)(kin(Fred)(Milly\H)))

with values from 0 through 9 for <n> and with option `-b<n>':

                      black=0
             ____________|____________
             |       |       |       |
           family  uncle    aunt    kin
        _____|______          _______|
        |__________|          |      |
        Martha Henry         Fred  Milly
                      black=1
             +-----------+-----------+
             |       |       |       |
           family  uncle    aunt    kin
        +----+-----+          -------|
        |----------|          |      |
        Martha Henry         Fred  Milly
                      black=2
              ...........:...........
             :       :       :       :
           family  uncle    aunt    kin
         ....:.....           .......:
        ::::::::::::          :      :
        Martha Henry         Fred  Milly
                      black=3
             |||||||||||||||||||||||||
             |       |       |       |
           family  uncle    aunt    kin
        ||||||||||||          ||||||||
        ||||||||||||          |      |
        Martha Henry         Fred  Milly
                      black=4
             :::::::::::::::::::::::::
             :       :       :       :
           family  uncle    aunt    kin
        ::::::::::::          ::::::::
        ::::::::::::          :      :
        Martha Henry         Fred  Milly
                      black=5
              ........../ \..........
             /       :       :       \
           family  uncle    aunt    kin
         ..../\....           .......:
        ::::::::::::          /      *
        Martha Henry         Fred  Milly
                      black=6
              __________/ \__________
             /       |       |       \
           family  uncle    aunt    kin
         ____/\____           _______|
        ||||||||||||          /      *
        Martha Henry         Fred  Milly
                      black=7
              <<<<<<<<<<< >>>>>>>>>>>
             /       |       |       \
           family  uncle    aunt    kin
         <<<<<>>>>>           <<<<<<<|
        |----------|          /      *
        Martha Henry         Fred  Milly
                      black=8
              ////////////\\\\\\\\\\\
             /       |       |       \
           family  uncle    aunt    kin
         /////\\\\\           ///////|
        ||||||||||||          /      *
        Martha Henry         Fred  Milly
                      black=9
              ////////////\\\\\\\\\\\
             /       |       |       \
           family  uncle    aunt    kin
         /////\\\\\           ///////|
        |**********|          /      *
        Martha Henry         Fred  Milly



The utilities `tpar' and `unpar' are for trees using indentation
for indicating structure rather than parenthesization.  For instance,
feed this to `tpar':

        \tree
        S
          NP
            Det\L - the
            N - rain
          VP - V - falls

to get back a parenthesized version that you can give to `tree':

        \tree
        (S
          (NP
            (Det\L(the))
            (N(rain)))
          (VP(V(falls))))

With the option `-v', `tpar' will put some ending parens on new lines,
and with the option `-t' it will turn bracketed digits and i,j,k,x,y,z
into the TeX code for subscripting the digit or letter, and also
translate N',A',V',P' into TeX code for putting bars over the letters.
The `unpar' utility translates the other way, substituting indentation
for parenthesization and, with the `-t' option, going back to the
bracket and prime notation from the TeX code.  The file tpsample has
example trees in indented form.

Bug reports and suggestions for changes are welcome.

                        Greg Lee, lee AT uhccux.uhcc.hawaii.edu, 7/90




Date:Wed, 8 May 91 10:00:00 MET
From:    Jan Hellings Central Computer department <HELLINGS AT AMC.UVA.NL>
Subject:   dvips547
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

beste Mensen
Het installeren van de nieuwe DVIPS547 voor vms geeft wat problemen:
1) Er moet een logical tex_pkdir worden gedefineerd als:
        tex_disk:[tex.pk.]/concealed
2) de fonts files worden nu a.h.v. hun grootte in verschillende directories
gezet. Dus de oude pkfile cmr10.300pk wordt nu [.pk.300]cmr.pk.
3) Helaas wordt de testpage.tex nog steeds niet goed afgedrukt.
Werd bij de oude dvips de linkerkantlijn verkeerd gezet nu wordt de boven
kantlijn verkeerd gezet.
Groeten
***************************Jan Hellings*********************************
* University of Amsterdam         Phone: (+31) 20 5662055              *
* Faculty of medicine/AMC/D01-412 bitnet: hellings@hasamc51            *
* Meibergdreef 9                                                       *
* 1105 AZ Amsterdam               domein  : hellings AT amc.uva.nl        *
* Holland                         decnet  : amccca::hellings           *


Date:Wed, 8 May 91 13:44:00 MET
From:    CGL AT RUG.NL
Subject:   Volunteers asked for contributions NTG's fall meeting,
Subject:   Volunteers asked for contributions NTG's fall meeting,
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,
Na de plezierige en constructieve bijeenkomst bij Elsevier wil ik
hiermede kenbaar maken aan de afwezigen dat Piet Tutelaers onze
gastheer voor de volgende bijeenkomst is, 21 Nov 1991 in Eindhoven.
Het heeft ook een thema: Fun with TeX.
Wij denken daarbij aan de hobby-achtige dingen zoals schaken (Piet T),
bridge (eindelijk dan toch), kruiswoordpuzzles e.d. Ook de dingbats
van Henderson is misschien wat.
Dit ter info, maar nu de vraag/oproep.
Wie-o-wie doet aan kruiswoordpuzzles en zou Brian Hamilton Kelly's macros
willen bekijken, proberen en er zijn bevindingen over willen geven
op de najaarsbijeenkomst?????? (Natuurlijk wordt een bijdrage voor de MAPS
verwacht en een verhaaltje op 21 nov.)
Wie heeft nog suggesties van FUN zaken die naar voren gehaald zouden kunnen
worden? Liefst met naam van degene die dat zouden kunnen verzorgen?

Ook kijken wij wat verder vooruit. Het volgend voorjaar denken wij aan
een bijeenkomst in de trant van Science en TeX, de mathematen, physici e.d.
worden dan eens in het zonnetje gezet. Met CERN en CWI is reeds contt
opgenomen. Suggesties  zijn welkom, en hoe eerder hoe beter.

Het verslag van de bijeenkomst volgt hopelijk spoedig op het net.

Vrijwilligers voor het een en ander kunnen zich of bij mij direct melden
of algemeen bij het bestuur: ntg@hearn.

Kom op mensen, de schouders eronder,

---Kees---




Date:Wed, 8 May 91 16:42:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   RE: dvips547
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


        Jan Hellings had een 'klacht' over dvips 5.47, de bovenmarge zou
        niet goed zijn.
        Klopt, maar als je de documentatie goed leest blijkt dat dit simpel
        te verhelpen is door het programma te vertellen dat je A4 papier
        gebruikt (ipv letter)
        Dat kan eenvoudig door een regel in dvips.cld te wijzigen:
************
File DSKX:[TEX.SOURCES.DVIPS.DVIPS.VMS]DVIPS.CLD;3
   18    qualifier mode, default, value(default="a4")
   19    qualifier magnification,default, value(required)
******
File DSKX:[TEX.SOURCES.DVIPS.DVIPS.VMS]DVIPS.CLD;2
   18    qualifier mode, default, value(default="letter")
   19    qualifier magnification,default, value(required)
************

        Johannes Braams




Date:Thu, 9 May 91 14:19:51 CDT
From:    Erik-Jan Vens <erikjan AT ICCE.RUG.NL>
Subject:   MF vraag
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Yo!

  wie weet waarom deze <.mf> invoer bij sommige pendiktes *wel* en bij sommige
pendiktes *niet* puntjes achterlaat op plaatsen waar ze niet meer zouden
moeten staan? Ik gebruik een CanonCX (=imagen) modesetup. Ik heb de invoer zo
simpel mogelijk weer gegeven:

------------------------------- test.mf ----------------------------
mode_setup;

beginchar("t", 1cm#, 1cm#, 0);
pickup pencircle scaled 2.1mm#;

draw fullcircle scaled 2cm shifted (0, .5cm);
erase cutdraw subpath (directiontime down of fullcircle,
                       directiontime right of fullcircle)
                      of fullcircle scaled 2cm shifted (0, .5cm);

endchar;
end.
------------------------------- test.mf ----------------------------


--

Erik-Jan Vens.    erikjan AT icce.rug.nl
                  erikjan AT guicce.uucp
                  {...!hp4nl!}rug4!guicce!erikjan

ICCE (Interdisciplinary Centre for the development of
      Computercoaches and Expertsystems)
Rijksuniversiteit Groningen
PObox 800
9700 AV  Groningen
the Netherlands.




Date:Wed, 15 May 91 17:24:00 N
From:    VCU11671 AT DS0RUS54.BITNET
Subject:   request for international co-operation
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Request for international co-operation

We are a group of \TeX\ users in the technical scientific field at the
University of Stuttgart.

Our work includes:

--- macro development on the basis of plain \TeX\ (+\PiCTeX)
--- development of special technical symbol fonts with \METAFONT
--- electronic "stripping" (line drawing, pixel graphics and
    colour illustrations)
--- normalisation of numerous different graphic systems on the basis of
    PostScript

for compiling high-quality publications, e.g. reports, lecture manuscripts,
papers, manuals as well as complete books. (Our most recent work: J.Argyris;
Texts on Computational Mechanics, Vol.5, North Holland, 1991)

In order to carry on our work more intensively and perhaps to reach an
international standard or at least industrial marketability, we are looking for
3-4 partners in Europe (in industry or universities) interested in co-operating
and exchanging ideas, thus concerting our research activities.

Contact address:

Steffen Kernstock
c/o Institute for Computer Applications (ICA)
University of Stuttgart
Pfaffenwaldring 27
D-7000 Stuttgart 80
Tel. 49/711/685-3634
Fax  49/711/685-3669
E-Mail: vcu11671@ds0rus54





Date:Thu, 16 May 91 00:46:00 GMT
From:    "Gerard van Nes, ENR-Petten" <VANNES AT ECN.NL>
Subject:   Info 6e European TeX Conference 23-26 september Parijs
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>



Hallo TeXeRs,

Van de week kreeg ik een stapel aankondigingen/registratie
formulieren binnen betreffende de 6e Europese TeX bijeenkomst
op 23-26 september 1991 te Parijs.

Opgenomen is ondermeer het voorlopige lezingenprogramma
(met 3 Nederlandse sprekers), korte informatie over de
tutorials, etc.

Aanmelding voor 30 juni a.s. scheelt 10% in de (totale)
conferentie en/of tutorial kosten.
Het lidmaatschap van de NTG levert daarnaast FF 200
extra op.

Indien men e'e'n of meerdere formulieren wilt ontvangen,
dan gaarne een reply (eventueel met het volledig postadres)
naar ondergetekende.
Niet netwerk-gebruikers zullen de folder in juni ontvangen,
samen met het concept verslag van de afgelopen 2 mei NTG
bijeenkomst.

Gerard van Nes
secretaris NTG





Date:Thu, 16 May 91 01:10:00 GMT
From:    "Gerard van Nes, ENR-Petten" <VANNES AT ECN.NL>
Subject:   NTG board; new member
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Hallo allemaal,

Voor degenen die op de laatste NTG vergadering van 2 mei j.l.
niet aanwezig waren:
De nieuwe NTG bestuurssamenstelling is als volgt:
- Kees van der Laan (voorzitter; herkozen)
- Gerard van Nes (secretaris)
- Johannes Braams (penningmeester)
- Huub Mulders (bestuurslid)
- Jos Winnink (bestuurslid; nieuw lid)

Daar op de laatste vergadering zich maar twee kandidaten hebben
aangemeld, zijn zij ook bij acclamatie gekozen.

Voor het geval u het nog niet wist:
het NTG bestuur heeft als e-mail adres: ntg@hearn

Zoals door de voorzitter reeds op 9 mei j.l. via e-mail is
medegedeeld, wordt de 8e NTG bijeenkomst gehouden op:
    ====>  donderdag 21 november 1991  <====
bij de Technische Universiteit te Eindhoven.


Gerard van Nes
secretaris NTG





Date:Wed, 22 May 91 07:54:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   Announcing the babel system of style options
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Hi,

        Below you find the readme file for the babel system of style
        options. This system supports multi-lingual documents, switching
        of hyphenation patterns, dynamically preloading of various
        hyphenation patterns, language-specific definitions etcetera.
        An article describing this system of style options will appear
        in TUGboat soon.

    Regards,

        Johannes Braams

PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams AT pttrnl.nl
-------------------------------------------------------------------------------

        I am pleased to announce the babel system of style options
        to be used with the standard LaTeX document styles.

        This system consists of any number of language-specific files
        and an underlying common file, babel.sty. The common file
        redefines various parts of the standard document styles,
        replacing english texts with macros. These macros are defined
        in the language-specific files that will be published in TUGboat.
        Currently I have language-specific files for dutch (ofcourse),
        german, english french, italian and spanish. (For the german and
        french parts I used Hubert Partl's german.sty)

        An extra feature of this system is that it offers a possibility
        to switch between languages.

        Anyone who likes to test this, please contact me.

        Please not that this is quite a different approach as the one
        discussed by Joachim Schrod in TUGboat Volume 11 No1. He describes
        a system where the actual LaTeX sources files are modified and a
        new .fmt file has to be built. All of that is not necessary to
        use my approach.

        Files you need:

        BABEL.README            This file
        BABEL.TEX               The driver file to print the documentation,
                                it is based on the use of FMi's doc.sty
        BABEL.DOC               The documented core of the system
        BABEL.STY               The docstripped version of babel.doc
        HYPHEN.DOC              The documented source for the next four files.
                                This file contains code for switchin between
                                languages and preloading pattern files.
        BABEL.HYPHEN            This file was produced from hyphen.doc and
                                can be read by iniTeX 3.x to preload one or
                                more hyphenation patterns, as specified in
                                the file language.dat
        LANGUAGE.DAT            A file listing the languages to be used,
                                this should be modified to reflect local needs.
        BABEL.SWITCH            This file was produced from hyphen.doc and
                                can will be called by babel.sty when
                                babel.switch wasn't processed by iniTeX.
        BABEL22.SWITCH          A version of babel.switch to be used with
                                a TeX version 2.x and plain (lplain) 2.x
        BABEL32.SWITCH          A version of babel.switch to be used with
                                a TeX version 3.x and plain (lplain) 2.x
        LATEXHAX.DOC            Some code, needed for compatibility with
                                plain TeX.
        LATEXHAX.STY            docstripped version of the above file.
        Language specific files come in pairs, documented and stripped.
        These files contain the real user interface, they are all
        the user should see from this system (if he doesn't look in
        TeX's log-file as most don't).
        DUTCH.DOC/DUTCH.STY
        ENGLISH.DOC/ENGLISH.STY
        GERMANB.DOC/GERMANB.STY babel-compatible version of Partl's german.tex
        FRENCH.DOC/FRENCH.STY   derived from german.tex, under development
        ITALIAN.DOC/ITALIAN.STY under development
        SPANISH.DOC/SPANISH.STY under development

    Installation notes

        To install the babel-system the person responsible for the maintenance
        of TeX should place all .sty files in the place where he keeps all
        TeX style files and such. (usually TeXinputs or something similar.)
        When he doesn't want to create new formats he should put the
        appropriate version of babel.switch there as well.
        To build a format, preloading multiple hyphenation patterns, do the
        following:

        1 rename hyphen.tex to something like hyphen.english and include a
          line to reflect this in language.dat;
        2 do the same for other files containing hyphenation patterns;
        3 make sure TeX's parameters are sufficiently sized to preload
          all patterns you want it to (look at trie_size and trie_op_size);
        4 run iniTeX and, when it tells you it can't find hyphen.tex (you
          just renamed it, no wonder) instruct it to read babel.hyphen.

    Notes on filenames

        You may have noted I used some filnames with extensions longer than
        3 characters. This may pose a problem for some operating systems.
        The implementation of TeX I use on my MS-DOS PC (emTeX) is more
        than happy to look for babel.hyp, instead of babel.hyphen. So just
        shorten the names to use 3 characters as extensions for files, no
        need to change any of the code. If you run another TeX implementation
        that behaves differently, well you're out of luck, look for the
        filenames in the code and modify them or get emTeX (this is a plug).

    Regards,

        Johannes Braams

PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,              The Netherlands.
Phone    : +31 70 3325051              E-mail : JL_Braams AT pttrnl.nl
-------------------------------------------------------------------------------




Date:Wed, 22 May 91 07:56:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   new on tex-nl filelist
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Hoi,

        Onlangs is de file rapport3.doc op de fileserver verschenen.
        Tegelijkertijd is rapport3.sty vervangen.
        Verder is de versie van babel, zoals beschreven in de MAPS
        (en binnenkort in TUGboat) nu ook op de server beschikbaar.

        Johannes




Date:Thu, 23 May 91 11:49:00 MET
From:    CGL AT RUG.NL
Subject:   Just for those of us who have severe questions
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Date: Wed, 22 May 91 13:23:43 CDT
From: Yin Kean 6-2473 <U46491@UICVM>
Subject: Everything you wanted to know about TeX
Sender: TeX Education Forum List <TEX-ED@UICVM>

   Everything you wanted to know about TeX and were afraid to ask

First in California, then in Texas, and now it's coming to the East
Coast.  It's time to set your sights on Dedham, Massachusetts. The
inimitable Barbara Beeton will run her famous question and answer
session once again this July 15-18 during the TeX Users Group meeting.
All questions are answered, from the most straightforward to the most
subtle.  Do you have a question to contribute? Is there a TeX problem
that you've never been able to solve, and have never known where to
turn? Is there a quick fix solution that you want to repair -- this
time the right way? Then let's hear from you.

Send in your question in the following way: send email to

TUG-Q AT TAMVM1.BITNET

or to

TUG-Q AT TAMVM1.TAMU.EDU

Your questions will be automatically forwarded to the proper destination.




Date:Thu, 23 May 91 16:41:30 CET
From:    R Veldhuyzen van Zanten <SOND0016 AT HASARA11.BITNET>
Subject:   Re:Announcing the babel system
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Kan FMi's DOC.STY, vereist voor BABEL.TEX, opgenomen worden in TeX-NL?




Date:Thu, 23 May 91 18:10:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   RE: Re:Announcing the babel system
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

 R Veldhuyzen van Zanten schrijft:
> Kan FMi's DOC.STY, vereist voor BABEL.TEX, opgenomen worden in TeX-NL?

        Ja, dat is-ie al. doc.sty maakt deel uit van de multicol distributie.
        Johannes




Date:Mon, 27 May 91 14:50:43 MET
From:    Werenfried Spit <W.Spit AT FYS.RUU.NL>
Subject:   Nederlandse bibliografiestijl
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hierbij een Nederlandse stijl voor BibTeX. Een en
ander toegesneden op de nederlandse grammaticaregels;
qua outputformaat afgestemd op de gebruiken in de
alfa-hoek:

J. van Dale, Woordenboek, 1875.

wordt gealfabetiseerd als          Dale, J. van
gelabeld als                       Van Dale, 1875
genoteerd als hierboven

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 FUNCTION {hello}
{ "BibTeX bibliography style Nederlands " top$
  "version 1.0" top$
  "laatste wijziging 27-05-1991          (WS)    " top$
}
% (C) Werenfried Spit    04-10-90
%
%     R.J. v.d. Graafflaboratorium
%     Postbus 80000
%     3508 TA  Utrecht
%     W.Spit AT fys.ruu.nl
%
%     Met gebruikmaking van veel werk van Piet v Oostrum en Oren Patashnik
%     for BibTeX 0.99a and LaTeX 2.09 %
%
% wijzigingen:
% 27-05-91 karaktertabel toegevoegd
% 14-05-91 behandeling van tussenvoegsels in namen verbeterd
%
%% \CharacterTable
%%  {Upper-case    \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
%%   Lower-case    \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
%%   Digits        \0\1\2\3\4\5\6\7\8\9
%%   Exclamation   \!     Double quote  \"     Hash (number) \#
%%   Dollar        \$     Percent       \%     Ampersand     \&
%%   Acute accent  \'     Left paren    \(     Right paren   \)
%%   Asterisk      \*     Plus          \+     Comma         \,
%%   Minus         \-     Point         \.     Solidus       \/
%%   Colon         \:     Semicolon     \;     Less than     \<
%%   Equals        \=     Greater than  \>     Question mark \?
%%   Commercial at \@     Left bracket  \[     Backslash     \\
%%   Right bracket \]     Circumflex    \^     Underscore    \_
%%   Grave accent  \`     Left brace    \{     Vertical bar  \|
%%   Right brace   \}     Tilde         \~}
%%
%
%   Citation format: [author-last-name, year]
%             [author-last-name \& author-last-name, year]
%             [author-last-name {\em et~al.}, year]
%
%   Reference list ordering: alphabetical by author or whatever passes
%   for author in the absence of one.
%
% This BibTeX style has support for short (year only) citations.  This
% is done by having the citations actually look like
%         \citeauthoryear{author-info}{year}
% The LaTeX style has to have the following (or similar)
%     \let\@internalcite\cite
%     \def\cite{\def\citeauthoryear##1##2{##1, ##2}\@internalcite}
%     \def\shortcite{\def\citeauthoryear##1{##2}\@internalcite}
%     \def\@biblabel#1{\def\citeauthoryear##1##2{##1, ##2}[#1]\hfill}
% which makes \shortcite the macro for short citations.

ENTRY
  { address
    author
    booktitle
    chapter
    edition
    editor
    howpublished
    institution
    journal
    key
    month
    note
    number
    organization
    pages
    publisher
    school
    series
    title
    type
    volume
    year
  }
  {}
  { label extra.label sort.label }

INTEGERS { output.state before.all mid.sentence after.sentence after.block }

FUNCTION {init.state.consts}
{ #0 'before.all :=
  #1 'mid.sentence :=
  #2 'after.sentence :=
  #3 'after.block :=
}

STRINGS { s t }

FUNCTION {output.nonnull}
{ 's :=
  output.state mid.sentence =
    { ", " * write$ }
    { output.state after.block =
    { add.period$ write$
      newline$
      "\newblock " write$
    }
    { output.state before.all =
        'write$
        { add.period$ " " * write$ }
      if$
    }
      if$
      mid.sentence 'output.state :=
    }
  if$
  s
}

FUNCTION {output}
{ duplicate$ empty$
    'pop$
    'output.nonnull
  if$
}

FUNCTION {output.check}
{ 't :=
  duplicate$ empty$
    { pop$ "empty " t * " in " * cite$ * warning$ }
    'output.nonnull
  if$
}

FUNCTION {One.cap}  %(WS) 14-05-91 capitalizes first letter of string
                    %              leaves the rest the same
{ duplicate$
  #1 #1   substring$ "\uppercase{" swap$ * "}" * swap$
  #2 #100 substring$ *
}

FUNCTION {output.bibitem}
{ newline$

  "\bibitem[" write$
  label write$
  "]{" write$

  cite$ write$
  "}" write$
  newline$
  ""
  before.all 'output.state :=
}

FUNCTION {fin.entry}
{ add.period$
  write$
  newline$
}

FUNCTION {new.block}
{ output.state before.all =
    'skip$
    { after.block 'output.state := }
  if$
}

FUNCTION {new.sentence}
{ output.state after.block =
    'skip$
    { output.state before.all =
    'skip$
    { after.sentence 'output.state := }
      if$
    }
  if$
}

FUNCTION {not}
{   { #0 }
    { #1 }
  if$
}

FUNCTION {and}
{   'skip$
    { pop$ #0 }
  if$
}

FUNCTION {or}
{   { pop$ #1 }
    'skip$
  if$
}

FUNCTION {new.block.checka}
{ empty$
    'skip$
    'new.block
  if$
}

FUNCTION {new.block.checkb}
{ empty$
  swap$ empty$
  and
    'skip$
    'new.block
  if$
}

FUNCTION {new.sentence.checka}
{ empty$
    'skip$
    'new.sentence
  if$
}

FUNCTION {new.sentence.checkb}
{ empty$
  swap$ empty$
  and
    'skip$
    'new.sentence
  if$
}

FUNCTION {field.or.null}
{ duplicate$ empty$
    { pop$ "" }
    'skip$
  if$
}

FUNCTION {emphasize}
{ duplicate$ empty$
    { pop$ "" }
    { "{\em " swap$ * "}" * }
  if$
}

INTEGERS { nameptr namesleft numnames }

FUNCTION {format.names}
{ 's :=
  #1 'nameptr :=
  s num.names$ 'numnames :=
  numnames 'namesleft :=
    { namesleft #0 > }

    { s nameptr "{ff~}{vv~}{ll}{, jj}" format.name$ 't :=

      nameptr #1 >                  % in de referentie wordt de volledige naam
    { namesleft #1 >                % afgedrukt: "J.H. van Dale"  (WS)
        { ", " * t * }
        { numnames #2 >
         { "," * }
         'skip$
          if$
          t "others" =
         { " {\em ~et~al.}" * }
         { " en " * t * }           % hier wordt een tussenvoegsel
          if$                       % tussen auteursnamen gemaakt   (WS)
        }
      if$
    }
    't
      if$
      nameptr #1 + 'nameptr :=
      namesleft #1 - 'namesleft :=
    }
  while$
}

FUNCTION {format.authors}
{ author empty$
    { "" }
    { author format.names }
  if$
}

FUNCTION {format.editors}
{ editor empty$
    { "" }
    { editor format.names
      editor num.names$ #1 >
    { ", editors" * }
    { ", editor" * }
      if$
    }
  if$
}

FUNCTION {format.title}
{ title empty$
    { "" }

    { title "t" change.case$ }

  if$
}

FUNCTION {n.dashify}
{ 't :=
  ""
    { t empty$ not }
    { t #1 #1 substring$ "-" =
    { t #1 #2 substring$ "--" = not
        { "--" *
          t #2 global.max$ substring$ 't :=
        }
        {   { t #1 #1 substring$ "-" = }
         { "-" *
           t #2 global.max$ substring$ 't :=
         }
          while$
        }
      if$
    }
    { t #1 #1 substring$ *
      t #2 global.max$ substring$ 't :=
    }
      if$
    }
  while$
}

FUNCTION {format.date}
{ year empty$
    { month empty$
    { "" }
    { "there's a month but no year in " cite$ * warning$
      month
    }
      if$
    }
    { month empty$
    'year
    { month " " * year * }
      if$
    }
  if$
}

FUNCTION {format.btitle}
{ title emphasize
}

FUNCTION {tie.or.space.connect}
{ duplicate$ text.length$ #3 <
    { "~" }
    { " " }
  if$
  swap$ * *
}

FUNCTION {either.or.check}
{ empty$
    'pop$
    { "can't use both " swap$ * " fields in " * cite$ * warning$ }
  if$
}

FUNCTION {format.bvolume}                             % in het Nederlands (WS)
{ volume empty$
    { "" }
    { series empty$
      { ", deel"  }
      { ", "  series emphasize * ", deel" * }
      if$
      volume tie.or.space.connect
    }
  if$
}

FUNCTION {format.number.series}                       % in het Nederlands (WS)
{ volume empty$
    { number empty$
        { series field.or.null }
        { series empty$
            { "there's a number but no series in " cite$ * warning$ }
            { series number tie.or.space.connect }
          if$
        }
      if$
    }
    { "" }
  if$
}

FUNCTION {format.edition}                             % in het Nederlands (WS)
{ edition empty$
    { "" }
    { edition "1" =
        { "Eerste" }
        { edition "2" =
            { "Tweede" }
            { edition "3" =
                { "Derde" }
                { edition "$^{\rm e}$ " * }
                if$
            }
            if$
        }
        if$
        output.state mid.sentence =
            { "l" change.case$ " druk" * }
            { "t" change.case$ " druk" * }
            if$
    }
    if$
}

INTEGERS { multiresult }

FUNCTION {multi.page.check}
{ 't :=
  #0 'multiresult :=
    { multiresult not
      t empty$ not
      and
    }
    { t #1 #1 substring$
      duplicate$ "-" =
      swap$ duplicate$ "," =
      swap$ "+" =
      or or
    { #1 'multiresult := }
    { t #2 global.max$ substring$ 't := }
      if$
    }
  while$
  multiresult
}

FUNCTION {format.pages}
{ pages empty$
    { "" }
    { pages multi.page.check
    { "p." pages n.dashify tie.or.space.connect }
    { "p." pages tie.or.space.connect }
      if$
    }
  if$
}

FUNCTION {format.vol.num.pages}
{ volume field.or.null
  number empty$
    'skip$
    { "(" number * ")" * *
      volume empty$
    { "there's a number but no volume in " cite$ * warning$ }
    'skip$
      if$
    }
  if$
  pages empty$
    'skip$
    { duplicate$ empty$
    { pop$ format.pages }
    { ":" * pages n.dashify * }
      if$
    }
  if$
}

FUNCTION {format.vol.year}
{ volume field.or.null
  year empty$
    { "empty year in " cite$ * warning$ }
    { " (" year * ")" * * }
  if$
}

FUNCTION {format.chapter.pages}                       % in het Nederlands (WS)
{ chapter empty$
    'format.pages
    { type empty$
        { output.state mid.sentence =
          { "hoofdstuk" }
          { "Hoofdstuk" }
          if$
         }
        { type "l" change.case$ }
      if$
      chapter tie.or.space.connect
      pages empty$
        'skip$
        { ", " * format.pages * }
      if$
    }
  if$
}

FUNCTION {format.in.ed.booktitle}                     % in het Nederlands (WS)
{ booktitle empty$                                    %
    { "" }
    { editor empty$
      { output.state mid.sentence =
        { "in " booktitle emphasize * }
        { "In " booktitle emphasize * }
        if$ }
      { output.state mid.sentence =
        { "in " booktitle emphasize * ", " * format.editors * }
        { "In " booktitle emphasize * ", " * format.editors * }
        if$ }
      if$
    }
  if$
}

FUNCTION {empty.misc.check}
{ author empty$ title empty$ howpublished empty$
  month empty$ year empty$ note empty$
  and and and and and

  key empty$ not and

    { "all relevant fields are empty in " cite$ * warning$ }
    'skip$
  if$
}

FUNCTION {format.thesis.type}
{ type empty$
    'skip$
    { pop$
      type "t" change.case$
    }
  if$
}

FUNCTION {format.preprint.number}
{ type empty$
    { "Preprint" }
    'type
  if$
  number empty$
    { "t" change.case$ }
    { number tie.or.space.connect }
  if$
}

FUNCTION {format.tr.number}
{ type empty$
    { "Technical Report" }
    'type
  if$
  number empty$
    { "t" change.case$ }
    { number tie.or.space.connect }
  if$
}

FUNCTION {format.article.crossref}
{ key empty$
    { journal empty$
    { "need key or journal for " cite$ * " to crossref " * crossref *
      warning$
      ""
    }
    { "In {\em " journal * "\/}" * }
      if$
    }
    { "In " key * }
  if$
  " \shortcite{" * crossref * "}" *
}

FUNCTION {format.crossref.editor}
{ editor #1 "{vv~}{ll}" format.name$ One.cap
  editor num.names$ duplicate$
  #2 >
    { pop$ "{\em ~et~al.}" * }
    { #2 <
    'skip$
    { editor #2 "{ff }{vv }{ll}{ jj}" format.name$ "others" =
        { " {\em ~et~al.}" * }
        { " \& " * editor #2 "{vv~}{ll}" format.name$ One.cap * }
      if$
    }
      if$
    }
  if$
}

FUNCTION {format.book.crossref}
{ volume empty$
    { "empty volume in " cite$ * "'s crossref of " * crossref * warning$
      "In "
    }
    { "Volume" volume tie.or.space.connect
      " of " *
    }
  if$
  editor empty$
  editor field.or.null author field.or.null =
  or
    { key empty$
    { series empty$
        { "need editor, key, or series for " cite$ * " to crossref " *
          crossref * warning$
          "" *
        }
        { "{\em " * series * "\/}" * }
      if$
    }
    { key * }
      if$
    }
    { format.crossref.editor * }
  if$
  " \shortcite{" * crossref * "}" *
}

FUNCTION {institution.or.organization.output}
{institution empty$
 {organization empty$
  { "Both organization and institution are missing in " cite$ * warning$ }
  { organization output }
  if$
 }
 {institution output}
if$
}

FUNCTION {format.incoll.inproc.crossref}
{ editor empty$
  editor field.or.null author field.or.null =
  or
    { key empty$
    { booktitle empty$
        { "need editor, key, or booktitle for " cite$ * " to crossref " *
          crossref * warning$
          ""
        }
        { "In {\em " booktitle * "\/}" * }
      if$
    }
    { "In " key * }
      if$
    }
    { "In " format.crossref.editor * }
  if$
  " \shortcite{" * crossref * "}" *
}

FUNCTION {article}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  crossref missing$
    { journal emphasize "journal" output.check
      format.vol.year output
      format.pages output
    }
    { format.article.crossref output.nonnull
      format.pages output
    }
  if$
  new.block
  note output
  fin.entry
}

FUNCTION {book}
{ output.bibitem
  author empty$
    { format.editors "author and editor" output.check }
    { format.authors output.nonnull
      crossref missing$
    { "author and editor" editor either.or.check }
    'skip$
      if$
    }
  if$
  new.block
  format.btitle "title" output.check
  crossref missing$
    { format.bvolume output
      new.block
      format.number.series output
      new.sentence
      publisher "publisher" output.check
      address output
    }
    { new.block
      format.book.crossref output.nonnull
    }
  if$
  format.edition output
  format.date "year" output.check
  new.block
  note output
  fin.entry
}

FUNCTION {booklet}
{ output.bibitem
  format.authors output
  new.block
  format.title "title" output.check
  howpublished address new.block.checkb
  howpublished output
  address output
  format.date output
  new.block
  note output
  fin.entry
}

FUNCTION {inbook}                     % produceert zowel hoofdstuk-
{ output.bibitem                      % als boektitel  (WS)
  author empty$                       % zie ook format.in.ed.booktitle
    { format.editors "author and editor" output.check }
    { format.authors output.nonnull
      crossref missing$
        { "author and editor" editor either.or.check }
        'skip$
      if$
    }
  if$
  new.block
  format.btitle "title" output.check
  crossref missing$
    { format.bvolume output
      format.chapter.pages "chapter and pages" output.check
      format.in.ed.booktitle output
      new.block
      format.number.series output
      new.sentence
      publisher "publisher" output.check
      address output
    }
    { format.chapter.pages "chapter and pages" output.check
      new.block
      format.book.crossref output.nonnull
    }
  if$
  format.edition output
  format.date "year" output.check
  new.block
  note output
  fin.entry
}

FUNCTION {incollection}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  crossref missing$
    { format.in.ed.booktitle "booktitle" output.check
      format.bvolume output
      format.number.series output
      format.chapter.pages output
      new.sentence
      publisher "publisher" output.check
      address output
      format.edition output
      format.date "year" output.check
    }
    { format.incoll.inproc.crossref output.nonnull
      format.chapter.pages output
    }
  if$
  new.block
  note output
  fin.entry
}

FUNCTION {inproceedings}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  crossref missing$
    { format.in.ed.booktitle "booktitle" output.check
      format.bvolume output
      format.number.series output
      format.pages output
      address empty$
    { organization publisher new.sentence.checkb
      organization output
      publisher output
      format.date "year" output.check
    }
    { address output.nonnull
      format.date "year" output.check
      new.sentence
      organization output
      publisher output
    }
      if$
    }
    { format.incoll.inproc.crossref output.nonnull
      format.pages output
    }
  if$
  new.block
  note output
  fin.entry
}

FUNCTION {conference} { inproceedings }

FUNCTION {manual}
{ output.bibitem
  author empty$
    { organization empty$
    'skip$
    { organization output.nonnull
      address output
    }
      if$
    }
    { format.authors output.nonnull }
  if$
  new.block
  format.btitle "title" output.check
  author empty$
    { organization empty$
    { address new.block.checka
      address output
    }
    'skip$
      if$
    }
    { organization address new.block.checkb
      organization output
      address output
    }
  if$
  format.edition output
  format.date output
  new.block
  note output
  fin.entry
}

FUNCTION {mastersthesis}                % doctoraalscriptie (WS)
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.btitle "title" output.check
  new.block
  "Doctoraalscriptie" format.thesis.type output.nonnull
  school "school" output.check
  address output
  format.date "year" output.check
  number empty$
         { skip$ }
         { " (Nr. " number * ")" * output }
         if$
  new.block
  note output
  fin.entry
}

FUNCTION {misc}
{ output.bibitem
  format.authors output
  title howpublished new.block.checkb
  format.title output
  howpublished new.block.checka
  howpublished output
  format.date output
  new.block
  note output
  fin.entry
  empty.misc.check
}

FUNCTION {phdthesis}                                     % proefschrift (WS)
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.btitle "title" output.check
  new.block
  "Dissertatie" format.thesis.type output.nonnull
  school "school" output.check
  address output
  format.date "year" output.check
  new.block
  note output
  fin.entry
}

FUNCTION {preprint}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  format.preprint.number output.nonnull
  institution.or.organization.output
  publisher output
  address output
  format.date "year" output.check
  new.block
  note output
  fin.entry
}

FUNCTION {proceedings}
{ output.bibitem
  editor empty$
    { organization output }
    { format.editors output.nonnull }
  if$
  new.block
  format.btitle "title" output.check
  format.bvolume output
  format.number.series output
  address empty$
    { editor empty$
    { publisher new.sentence.checka }
    { organization publisher new.sentence.checkb
      organization output
    }
      if$
      publisher output
      format.date "year" output.check
    }
    { address output.nonnull
      format.date "year" output.check
      new.sentence
      editor empty$
    'skip$
    { organization output }
      if$
      publisher output
    }
  if$
  new.block
  note output
  fin.entry
}

FUNCTION {techreport}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  format.tr.number output.nonnull
  institution "institution" output.check
  address output
  format.date "year" output.check
  new.block
  note output
  fin.entry
}

FUNCTION {unpublished}
{ output.bibitem
  format.authors "author" output.check
  new.block
  format.title "title" output.check
  new.block
  note "note" output.check
  format.date output
  fin.entry
}

FUNCTION {default.type} { misc }

MACRO {jan} {"januari"}
MACRO {feb} {"februari"}
MACRO {mar} {"maart"}
MACRO {apr} {"april"}
MACRO {may} {"mei"}
MACRO {jun} {"juni"}
MACRO {jul} {"juli"}
MACRO {aug} {"augustus"}
MACRO {sep} {"september"}
MACRO {oct} {"oktober"}
MACRO {nov} {"november"}
MACRO {dec} {"december"}

MACRO {AcP}    {"Acta Physica"}
MACRO {AcPA}   {"Acta Physica Austriaca"}
MACRO {AcPP}   {"Acta Physica Polonica"}
MACRO {AdP}    {"Advances in Physics"}
MACRO {AdNP}   {"Advances in Nuclear Physics"}
MACRO {AmJP}   {"American Journal of Physics"}
MACRO {AnPDu}  {"Annalen der Physik (Leipzig)"}
MACRO {AnPFr}  {"Annales de Physique (Paris)"}
MACRO {AnPNY}  {"Annals of Physics (NY)"}
MACRO {ARevNS} {"Annual Review of Nuclear Science"}
MACRO {ADNDT}  {"Atomic Data and Nuclear Data Tables"}
MACRO {AusJP}  {"Australian Journal of Physics"}
MACRO {CanJP}  {"Canadian Journal Physics"}
MACRO {CPC}    {"Computer Physics Communications"}
MACRO {EJP}    {"European Journal of Physics"}
MACRO {EPL}    {"Europhysics Letters"}
MACRO {FBS}    {"Few Body Systems"}
MACRO {FBSSup} {"Few Body Systems Supplement"}
MACRO {FortP}  {"Fortschritte der Physik"}
MACRO {HePA}   {"Helvetica Physica Acta"}
MACRO {IEEE}   {"IEEE Transactions"}
MACRO {IJMP}   {"International Journal of Modern Physics"}
MACRO {JETP}   {"JETP"}
MACRO {JETPL}  {"JETP Letters"}
MACRO {JaFi}   {"{\cyr {\Ja}derna\ja Fizika}"}
MACRO {JPFr}   {"Journal de Physique (Paris)"}
MACRO {JP}     {"Journal of Physics"}
MACRO {JPSJ}   {"Journal of the Physical Society of Japan"}
MACRO {JPSJSup}{"Journal of the Physical Society of Japan Supplement"}
MACRO {MPL}    {"Modern Physics Letters"}
MACRO {NCim}   {"Il Nuovo Cimento"}
MACRO {NDS}    {"Nuclear Data Sheets"}
MACRO {NP}     {"Nuclear Physics"}
MACRO {PL}     {"Physics Letters"}
MACRO {PRSLon} {"Proceedings of the Royal Society of London"}
MACRO {PR}     {"Physical Review"}
MACRO {PRL}    {"Physical Review Letters"}
MACRO {PRep}   {"Physics Reports"}
MACRO {PScr}   {"Physica Scripta"}
MACRO {PToday} {"Physics Today"}
MACRO {PTP}    {"Progress of Theoretical Physics"}
MACRO {RMP}    {"Reviews of Modern Physics"}
MACRO {ScAm}   {"Scientific American"}
MACRO {SSin}   {"Scienta Sinica"}
MACRO {SovJNP} {"Soviet Journal of Nuclear Physics"}
MACRO {SovJPN} {"Soviet Journal of Particles and Nuclei"}
MACRO {SovPDo} {"Soviet Physics Doklady"}
MACRO {SovPUs} {"Soviet Physics Uspekhi"}
MACRO {STS}    {"Bulletin of Science, Technology and Social Affairs"}
MACRO {ZfN}    {"Zeitschrift f{\H{u}}r Naturforschung"}
MACRO {ZfP}    {"Zeitschrift f{\H{u}}r Physik"}

MACRO {KUN} {"Katholieke Universiteit Nijmegen"}
MACRO {RUU} {"Rijksuniversiteit te Utrecht"}
MACRO {UvA} {"Universiteit van Amsterdam"}
MACRO {RUG} {"Rijksuniversiteit te Groningen"}
MACRO {RUL} {"Rijksuniversiteit te Leiden"}
MACRO {VU}  {"Vrije Universiteit"}
MACRO {TUD} {"Technische Universiteit Delft"}

READ

EXECUTE {hello}

FUNCTION {sortify}
{ purify$
  "l" change.case$
}

INTEGERS { numberlen numberzero}

FUNCTION {numsortify}
{ purify$
  "l" change.case$
  's :=
  #1 'numberlen :=
  { s numberlen #1 substring$ "1" =
    s numberlen #1 substring$ "2" =
    s numberlen #1 substring$ "3" =
    s numberlen #1 substring$ "4" =
    s numberlen #1 substring$ "5" =
    s numberlen #1 substring$ "6" =
    s numberlen #1 substring$ "7" =
    s numberlen #1 substring$ "8" =
    s numberlen #1 substring$ "9" =
    s numberlen #1 substring$ "0" =
    or or or or or or or or or    }
  { numberlen #1 + 'numberlen :=  }
  while$
  #6 numberlen -  'numberzero :=
  "000000" #1 numberzero substring$
  s *
}
INTEGERS { len }

FUNCTION {chop.word}
{ 's :=
  'len :=
  s #1 len substring$ =
    { s len #1 + global.max$ substring$ }
    's
  if$
}

INTEGERS { et.al.char.used }

FUNCTION {initialize.et.al.char.used}
{ #0 'et.al.char.used :=
}

EXECUTE {initialize.et.al.char.used}

FUNCTION {format.lab.names}
{ 's :=
  s num.names$ 'numnames :=

  numnames #1 =                               % maak het citatielabel dat
    { s #1 "{vv~}{ll}" format.name$ One.cap}  % wordt afgedrukt
    { numnames #2 =                           %  b.v.  "van Dale"     (WS)
        {s #1 "{vv~}{ll} " format.name$ One.cap
         s #2 "{ll}" format.name$ "others" =
                { s #2 "\bgroup\em~et~al.\egroup" format.name$ * }
                { " \& " * s #2 "{vv~}{ll}" format.name$ One.cap * }
         if$
        }
        { s #1 "{vv~}{ll} \bgroup\em~et~al.\egroup" format.name$ One.cap }
      if$
    }
  if$

}

FUNCTION {author.key.label}
{ author empty$
    { key empty$
    { cite$ #1 #3 substring$ }
    { key }
      if$
    }
    { author format.lab.names }
  if$
}

FUNCTION {author.editor.key.label}
{ author empty$
    { editor empty$
    { key empty$

        { cite$ #1 #3 substring$ }

        { key }
      if$
    }
    { editor format.lab.names }
      if$
    }
    { author format.lab.names }
  if$
}

FUNCTION {author.key.organization.label}
{ author empty$
    { key empty$
    { organization empty$

        { cite$ #1 #3 substring$ }

        { "The " #4 organization chop.word #3 text.prefix$ }
      if$
    }
    { key }
      if$
    }
    { author format.lab.names }
  if$
}

FUNCTION {editor.key.organization.label}
{ editor empty$
    { key empty$
    { organization empty$

        { cite$ #1 #3 substring$ }

        { "The " #4 organization chop.word #3 text.prefix$ }
      if$
    }
    { key }
      if$
    }
    { editor format.lab.names }
  if$
}

FUNCTION {calc.label}
{ type$ "book" =
  type$ "inbook" =
  or
    'author.editor.key.label
    { type$ "proceedings" =
    'editor.key.organization.label
    { type$ "manual" =
        'author.key.organization.label
        'author.key.label
      if$
    }
      if$
    }
  if$
  "\protect\citeauthoryear{" swap$ * "}{" *
  year field.or.null purify$ *  % CHANGED - pfps - 15 Feb 1989
  'label :=                     % maak het af te drukken citeerlabel
}

FUNCTION {sort.format.names}
{ 's :=
  #1 'nameptr :=
  ""
  s num.names$ 'numnames :=
  numnames 'namesleft :=
    { namesleft #0 > }
    { nameptr #1 >
    { "   " * }
    'skip$
      if$                 % het sorteerlabel begrijpt Nederlandse namen
                          % b.v  "Dale van JH"   (WS)
      s nameptr "{ll{ }}{vv{ }}{  f{ }}{  jj{ }}" format.name$ 't :=
      nameptr numnames = t "others" = and
    { "{\em~et~al}" * }
    { t sortify * }
      if$
      nameptr #1 + 'nameptr :=
      namesleft #1 - 'namesleft :=
    }
  while$
}

FUNCTION {sort.format.title}
{ 't :=
  "De " #2                                % titels worden gesorteerd
   "Een " #3                              % op het lidwoord na  (WS)
    "A " #4
     "An " #5
      "The " #6 t chop.word
              chop.word
          chop.word
      chop.word
  chop.word
  sortify
  #1 global.max$ substring$
}

FUNCTION {author.sort}
{ author empty$
    { key empty$
    { "to sort, need author or key in " cite$ * warning$
      ""
    }
    { key sortify }
      if$
    }
    { author sort.format.names }
  if$
}

FUNCTION {author.editor.sort}
{ author empty$
    { editor empty$
    { key empty$
        { "to sort, need author, editor, or key in " cite$ * warning$
          ""
        }
        { key sortify }
      if$
    }
    { editor sort.format.names }
      if$
    }
    { author sort.format.names }
  if$
}

FUNCTION {author.organization.sort}
{ author empty$
    { organization empty$
    { key empty$
        { "to sort, need author, organization, or key in " cite$ * warning$
          ""
        }
        { key sortify }
      if$
    }
    { "The " #4 organization chop.word sortify }
      if$
    }
    { author sort.format.names }
  if$
}

FUNCTION {editor.organization.sort}
{ editor empty$
    { organization empty$
    { key empty$
        { "to sort, need editor, organization, or key in " cite$ * warning$
          ""
        }
        { key sortify }
      if$
    }
    { "The " #4 organization chop.word sortify }
      if$
    }
    { editor sort.format.names }
  if$
}

FUNCTION {presort}
{ calc.label                                 % maak het label dat wordt afgedruk
   t
  " "                                        %
  type$ "book" =                             % maak nu het sorteerlabel
  type$ "inbook" =                           % (WS)
  or
    'author.editor.sort
    { type$ "proceedings" =
        'editor.organization.sort
        { type$ "manual" =
            'author.organization.sort
            'author.sort
          if$
        }
      if$
    }
  if$
  *
  "                                  "
  *
  year field.or.null sortify
  *
  type$ "article" =
        { " " *
          journal field.or.null sortify *
          volume  field.or.null numsortify *
          pages   field.or.null numsortify * }
        { skip$    }
        if$
  "    "
  *
  title field.or.null
  sort.format.title
  *
  #1 entry.max$ substring$
  'sort.key$ :=
}

ITERATE {presort}

SORT

STRINGS { longest.label last.sort.label next.extra }

INTEGERS { longest.label.width last.extra.num }

FUNCTION {initialize.longest.label}
{ "" 'longest.label :=
  #0 int.to.chr$ 'last.sort.label :=
  "" 'next.extra :=
  #0 'longest.label.width :=
  #0 'last.extra.num :=
}

FUNCTION {forward.pass}
{ last.sort.label label =
    { last.extra.num #1 + 'last.extra.num :=
      last.extra.num int.to.chr$ 'extra.label :=
    }
    { "a" chr.to.int$ 'last.extra.num :=
      "" 'extra.label :=
      label 'last.sort.label :=
    }
  if$
}

FUNCTION {reverse.pass}
{ next.extra "b" =
    { "a" 'extra.label := }
    'skip$
  if$
  label extra.label * "}" * 'label :=   % CHANGED - pfps 15 Feb 1989
  label width$ longest.label.width >
    { label 'longest.label :=
      label width$ 'longest.label.width :=
    }
    'skip$
  if$
  extra.label 'next.extra :=
}

EXECUTE {initialize.longest.label}

ITERATE {forward.pass}

REVERSE {reverse.pass}

FUNCTION {begin.bib}

{ et.al.char.used
    { "\newcommand{\etalchar}[1]{$^{#1}$}" write$ newline$ }
    'skip$
  if$
  preamble$ empty$

    'skip$
    { preamble$ write$ newline$ }
  if$

  "\begin{thebibliography}{}" write$ newline$

}

EXECUTE {begin.bib}

EXECUTE {init.state.consts}

ITERATE {call.type$}

FUNCTION {end.bib}
{ newline$
  "\end{thebibliography}" write$ newline$
}

EXECUTE {end.bib}





%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%




Date:Mon, 27 May 91 17:03:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   babel updates
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Hi,

        Some of the files in the babel system have been refreshed on
        LISTSERV@HEARN. Some mistakes (especially the use of \verb
        within \changes) have been repaired.

        Johannes




Date:Tue, 28 May 91 14:27:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   babel
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Hi,

        Please note the the files, formerly called french.doc and french.sty
        have been renamed to francais.doc and francais.sty. This has had
        its consequences for the macros as well.

        I am unfortunately not allowed to call the language specific file
        for the french language french.sty. GUTenberg (Nicolas Brouard)
        claims the right to that name. I do plan to integrate their french.sty
        with francais.sty in the near future.

        All files concerned on LISTSERV@HEARN have been updated to reflect
        the name-change. In some of the other files some typos have been
        removed.

        Johannes




Date:Thu, 30 May 91 16:29:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   I think this is a bug in LaTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

    Hi,

        Today we stumbled upon a LaTeX 'feature' that I would call a bug.

        A user wanted to have multiple occurences of the same footnotemark
        in a tabular environment. To accomplish this he put the tabular
        environment inside a minipage. So far so good. To his (and mine)
        astonishment the footnotemarks (created with eg \footnotemark[1])
        appeared in the table as arabic numerals, while the marks that
        go with the footnotetext appeared as lowercase letters.
        Digging into:

% LATEX VERSION 2.09 <7 Dec 1989>
% Copyright (C) 1988 by Leslie Lamport

        revealed the following defintion for \footnotemark and its companion
        \@xfootnotemark:

\def\footnotemark{\@ifnextchar[{\@xfootnotemark
    }{\stepcounter{footnote}\xdef\@thefnmark{\thefootnote}\@footnotemark}}

\def\@xfootnotemark[#1]{\begingroup \c@footnote #1\relax
   \xdef\@thefnmark{\thefootnote}\endgroup \@footnotemark}

        which means both macros always use the footnote counter, whereas
        other footnote-macros use the mpfoutnote counter inside a minipage
        environment.

        To cure this behaviour I put

%+
%     This repairs a bug in LaTeX.tex, where the \footnotemark
%     uses \thefootnote instead of \thmpfn
%-
\def\footnotemark{\@ifnextchar[{\@xfootnotemark
    }{\stepcounter{footnote}\xdef\@thefnmark{\thempfn}\@footnotemark}}

\def\@xfootnotemark[#1]{\begingroup \csname c@\@mpfn\endcsname #1\relax
   \xdef\@thefnmark{\thempfn}\endgroup \@footnotemark}

        in a style file.

    Regards,

        Johannes Braams

PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams AT pttrnl.nl
Fax      : +31 70 3326477
-------------------------------------------------------------------------------




Date:Thu, 30 May 91 22:20:00 MET
From:    Rainer Schoepf <Schoepf AT SC.ZIB-BERLIN.DBP.DE>
Subject:   I think this is a feature in LaTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Johannes Braams writes:

    Hi,

        Today we stumbled upon a LaTeX 'feature' that I would call a bug.

        A user wanted to have multiple occurences of the same footnotemark
        in a tabular environment. To accomplish this he put the tabular
        environment inside a minipage. So far so good. To his (and mine)
        astonishment the footnotemarks (created with eg \footnotemark[1])
        appeared in the table as arabic numerals, while the marks that
        go with the footnotetext appeared as lowercase letters.


Let me point out that this behaviour is deliberate and documented
(page 99). It is to allow the use of normal footnotes (e.g. appearing
at the bottom of the page, not the minipage environment) inside the
minipage.

Rainer Sch"opf





Date:Fri, 31 May 91 11:12:00 N
From:    "P.Stoop, KVI, Zernikeln 25, 9747 AA Groningen, NL"
Subject:   RE: I think this is a bug in LaTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Last august I also "stumbled upon" the same problem, trying to do the same
thing. I also think that it is at least a serious omission of LaTeX that
the macros for normal footnotes are not available for footnotes in a minipage.
In addition to the small problem above, I lure your attention to another
problem with footnotes that was discussed and solved by Nico Poppelier in
august 1990. This curious feature, introduced by the style option in article
sty can cause footnote numbers to appear twice if the footnote text is longer
then the current linewidth, which has a significantly higher probability
in a minipage environment. If anybody has this problem again and does not
have the solution given on this list I can sent it to them.

Paul Stoop.