TEX-NL archief juni 1990

Inhoudsopgave

Mon, 4 Jun 90 16:16:00 MET: Vakantie
Tue, 5 Jun 90 11:07:04 met: [dbj AT titan.rice.edu: Re: LaTeX change bars]
Thu, 7 Jun 90 11:37:00 MET: cyrillisch font
Fri, 8 Jun 90 09:37:00 GMT: PiCTeX manual
Fri, 8 Jun 90 13:24:36 met: PiCTeX manual
Fri, 8 Jun 90 13:59:00 MET: RE: PiCTeX manual
Fri, 8 Jun 90 14:40:38 met: RE: PiCTeX manual
Fri, 8 Jun 90 15:08:00 MET: emmf
Mon, 11 Jun 90 15:41:00 GMT: ReRe: LaTeX change bars
Wed, 13 Jun 90 10:29:00 CET: Kolommen met alignment
Wed, 13 Jun 90 10:38:00 MET: Re: TeXline X. And now for something completely \else
Wed, 13 Jun 90 13:00:35 met: Kolommen met alignment
Wed, 13 Jun 90 10:12:00 MET: Overgeschreven uit de NRC. Over spelling.
Wed, 13 Jun 90 13:34:36 MET: Re: TeXline X. And now for something completely \else
Wed, 13 Jun 90 16:58:00 N: uuencoded, compressed, tar file.... help!
Wed, 13 Jun 90 17:19:47 met: uuencoded, compressed, tar file.... help!
Thu, 14 Jun 90 15:57:11 met: uuencoded, compressed, tar file.... help!
Thu, 14 Jun 90 16:16:00 MET: RE: uuencoded, compressed, tar file.... help!
Fri, 15 Jun 90 09:06:00 N: BibTeX 0.99c
Fri, 15 Jun 90 11:23:00 MET: Re: TeXline X. And now for something completely \else
Fri, 15 Jun 90 11:54:00 MET: Re: TeXline X. And now for something completely \else
Fri, 15 Jun 90 13:59:00 MET: Re: TeXline X. And now for something completely \else
Fri, 15 Jun 90 14:32:42 MET: morphemenlijst
Fri, 15 Jun 90 15:13:56 MET: drivers gezocht
Fri, 15 Jun 90 15:31:00 MET: Re: TeXline X. And now for something completely \else
Fri, 15 Jun 90 15:34:00 MET: RE: drivers gezocht
Fri, 15 Jun 90 15:47:00 GMT: RE: BibTeX 0.99c
Sat, 16 Jun 90 14:45:00 MET: Eric Gill biografie
Mon, 18 Jun 90 00:06:00 MET: SGML-TeX bijeenkomst aug 90; Opgave cursussen en conferentie.
Mon, 18 Jun 90 12:53:00 GMT: NTG > information just posted to NTG members
Mon, 18 Jun 90 12:47:00 MET: deskjet driver
Mon, 18 Jun 90 15:21:51 MET: Pre-publication (read: shameless plug)
Tue, 19 Jun 90 11:08:00 MET: VoetBal.TeX door Opland
Tue, 19 Jun 90 15:00:54 -0100: LaTeX figuurnummering vraag
Tue, 19 Jun 90 16:41:00 -0100: help
Tue, 19 Jun 90 16:54:47 +0200: latex subequations
Tue, 19 Jun 90 19:36:14 met: LaTeX figuurnummering vraag
Tue, 19 Jun 90 20:25:13 met: fig 4a, 4b
Wed, 20 Jun 90 10:54:00 MET: RE: VoetBal.TeX door Opland
Wed, 20 Jun 90 12:54:00 MET: A useful document about LaTeX questions asked over and over. Kees
Thu, 21 Jun 90 11:51:00 MET: Mijn kopie van Frequently Asked Questions was gemold. Verbeterd.
Thu, 21 Jun 90 12:21:00 MET: Sorry, nog wat fouten. Hier is een diff
Sat, 23 Jun 90 14:15:00 MET: Sorry. Compress 16bits.
Mon, 25 Jun 90 11:48:00 N: VMS ZOO
Tue, 26 Jun 90 16:58:00 N: Whitespace before section heading
Wed, 27 Jun 90 11:22:50 MET: BibTeX
Wed, 27 Jun 90 12:24:50 met: BibTeX
Wed, 27 Jun 90 13:35:16 MET: BibTeX
Thu, 28 Jun 90 01:00:00 MET: Character encoding proposal; anybody with experience on the matter
Thu, 28 Jun 90 10:12:41 MET: BibTeX, named.bst
Thu, 28 Jun 90 12:06:00 MET: Q: \expandafter etc. Poor stupid me.
Thu, 28 Jun 90 12:33:00 MET: Some more. Some more. (Frank Zappa. Tinseltown Rebellion).
Thu, 28 Jun 90 14:44:03 MET: Re: Q: \expandafter etc. Poor stupid me.
Thu, 28 Jun 90 13:42:32 met: BibTeX, named.bst
Thu, 28 Jun 90 15:43:50 MET: Re: BibTeX, named.bst
Thu, 28 Jun 90 13:42:28 CET: Re: BibTeX, named.bst
Thu, 28 Jun 90 16:05:15 met: Re: Q: \expandafter etc. Poor stupid me.
Fri, 29 Jun 90 10:17:00 MET:  een shell-archive met de macros voor dragon curves.
Fri, 29 Jun 90 13:53:00 MET: Makeindex status. Seems very interesting to me, so ... Kees
Fri, 29 Jun 90 13:54:00 MET: Once again an interesting state of affairs, so ... Kees
Fri, 29 Jun 90 15:15:27 MET: Re: Q: \expandafter etc. Poor stupid me.
Fri, 29 Jun 90 15:50:40 MET: Geen \the dus. Sorry.
Fri, 29 Jun 90 21:44:00 MET: RE: Geen \the dus. Sorry.
Fri, 29 Jun 90 22:34:00 MET: Interesting survey Uk-archive. Kees


Date:Mon, 4 Jun 90 16:16:00 MET
From:    "Johannes L. Braams" <JL_Braams AT PTTRNL.NL>
Subject:   Vakantie
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


    Beste TeXers,

        Als iemand mij de volgende weken nodig mocht hebben, dan heeft-ie
        pech gehad, ik ben tot eind juni op vakantie...
        Na 1 juli ben ik weer bereikbaar.

    Met vriendelijke groeten,

        Johannes Braams




Date:Tue, 5 Jun 90 11:07:04 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   [dbj AT titan.rice.edu: Re: LaTeX change bars]
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

  From: dbj AT titan.rice.edu (Dave Johnson)
  Subject: Re: LaTeX change bars
  Newsgroups: comp.text.tex
  Message-ID: <8281 AT brazos.Rice.edu>

  In article <136281 AT sun.Eng.Sun.COM> cmcmanis AT stpeter.Eng.Sun.COM (Chuck McMani
  >Here is a good TeXHaX question: How can I generate change bars in
  >a LaTeX document...


  Here's a LaTeX document-style option for doing change bars that
  I wrote a while ago.  It's not perfect, but I does most things right...

                                          Dave Johnson
                                          Dept. of Computer Science
                                          Rice University


----------------------------------------
% Change bar document-style option for LaTeX.
%
% Copyright (C) 1990 by David B. Johnson.

% These macros draw a solid bar down the right margin of the output,
% covering a range of the input file that has been declared to be changed.
%
% The beginning and end of a change bar in the text are marked with
% \chgbarbegin and \chgbarend, respectively.  For example,
%
%     Here is some sample text \chgbarbegin that was
%     changed\chgbarend┼╠ and some that wasn't changed.
%
% The change bar is drawn continuously between the line of output
% containing the \chgbarbegin and the line of output containing the
% \chgbarend.  These lines can end up on separate pages, and the
% division at page boundaries is handled automatically.

% Two dimensions control the size and placement of the change bars:
%     \chgbarwidth      The width of a change bar
%     \chgbarsep        The distance between the text and the change bar

% Warning: it does not appear to be possible to do this completely
% correctly, due to the time at which the verticle glue on a page is
% finally set, and the way that page breaks are decided.  With
% \raggedbottom, this normally works fine.  It hasn't been tested with
% \flushbottom, but will probably behave worse.  In strange rare
% situations, a change bar might be drawn from the first line of a page
% up off the top of a page; this can usually be fixed by slightly moving
% the \chngbarend around, or by breaking a single change bar range
% into two ranges.

\newdimen\chgbarwidth \newdimen\chgbarsep
\chgbarwidth 4pt
\chgbarsep .25in

\def\chgbarbegin┼\ifhmode\@chgbar┼-2╠\else\@chgbar┼-3╠\fi╠
\def\chgbarend┼\@chgbar┼-4╠╠

\marginparpush 0pt

% The remainder of this is hacked up based on the LaTeX 2.09 latex.tex.

% copied from \marginpar
\def\@chgbar#1┼\ifhmode \@bsphack\@floatpenalty -\@Mii\else
   \@floatpenalty-\@Miii\fi\ifinner
      \@parmoderr\@floatpenalty\z@
    \else\@next\@currbox\@freelist┼\global
      \count\@currbox#1╠┼\@floatpenalty\z@ \@fltovf
      \def\@currbox┼\@tempboxa╠╠\fi
     \setbox\@tempboxa\vbox
     \bgroup\end@float\@esphack╠

\newdimen\@chgbarbegin
\newif\if@inchgbar \@inchgbarfalse

\def\@addmarginpar┼%
\ifnum\count\@currbox = -2      % change bar begin from hmode
    \global\@chgbarbegin\@pageht \global\advance\@chgbarbegin -\baselineskip
    \global\@inchgbartrue
    \@cons\@freelist\@currbox
\else
\ifnum\count\@currbox = -3      % change bar begin not from hmode
    \global\@chgbarbegin\@pageht
    \global\@inchgbartrue
    \@cons\@freelist\@currbox
\else
\ifnum\count\@currbox = -4      % change bar end
    \if@inchgbar\else\@latexbug\fi
    \@tempdima\@pageht \advance\@tempdima -\@chgbarbegin
    \nointerlineskip
    \@tempcnta\@ne
    \if@twocolumn
        \if@firstcolumn \@tempcnta\m@ne \fi
    \else
      \if@mparswitch
         \ifodd\c@page \else\@tempcnta\m@ne \fi
      \fi
      \if@reversemargin \@tempcnta -\@tempcnta \fi
    \fi
    \hbox to\columnwidth
      ┼\ifnum \@tempcnta >\z@
          \hskip\columnwidth \hskip\chgbarsep
        \else \hskip -\chgbarsep \fi
\hbox┼\vbox to 0pt┼\vss
       \hrule \@height\@tempdima \@width\chgbarwidth \@depth\z@
╠╠
\hss╠
    \nointerlineskip
    \global\@inchgbarfalse
    \@cons\@freelist\@currbox
\else
    \@next\@marbox\@currlist┼\@cons\@freelist\@marbox
    \@cons\@freelist\@currbox╠\@latexbug\@tempcnta\@ne
    \if@twocolumn
        \if@firstcolumn \@tempcnta\m@ne \fi
    \else
      \if@mparswitch
         \ifodd\c@page \else\@tempcnta\m@ne \fi
      \fi
      \if@reversemargin \@tempcnta -\@tempcnta \fi
    \fi
    \ifnum\@tempcnta <\z@  \global\setbox\@marbox\box\@currbox \fi
    \@tempdima\@mparbottom \advance\@tempdima -\@pageht
       \advance\@tempdima\ht\@marbox \ifdim\@tempdima >\z@
       \@warning┼Marginpar on page \thepage\space moved╠\else\@tempdima\z@ \fi
    \global\@mparbottom\@pageht \global\advance\@mparbottom\@tempdima
       \global\advance\@mparbottom\dp\@marbox
       \global\advance\@mparbottom\marginparpush
    \advance\@tempdima -\ht\@marbox
    \global\ht\@marbox\z@ \global\dp\@marbox\z@
    \vskip -\@pagedp \vskip\@tempdima\nointerlineskip
    \hbox to\columnwidth
      ┼\ifnum \@tempcnta >\z@
          \hskip\columnwidth \hskip\marginparsep
        \else \hskip -\marginparsep \hskip -\marginparwidth \fi
       \box\@marbox \hss╠
    \vskip -\@tempdima
    \nointerlineskip
    \hbox┼\vrule \@height\z@ \@width\z@ \@depth\@pagedp╠
\fi\fi\fi╠

\def\@makecol┼\setbox\@outputbox\box\@cclv
   \if@inchgbar
    \@tempcnta\@ne
    \if@twocolumn
        \if@firstcolumn \@tempcnta\m@ne \fi
    \else
      \if@mparswitch
         \ifodd\c@page \else\@tempcnta\m@ne \fi
      \fi
      \if@reversemargin \@tempcnta -\@tempcnta \fi
    \fi
    \@tempdima\ht\@outputbox \advance\@tempdima -\@chgbarbegin
    \advance\@tempdima -\baselineskip
    \setbox\@outputbox
     \vbox┼\boxmaxdepth \maxdepth
     \unvbox\@outputbox \nointerlineskip \hbox to\columnwidth
      ┼\ifnum \@tempcnta >\z@
          \hskip\columnwidth \hskip\chgbarsep
        \else \hskip -\chgbarsep \fi
       \hbox┼\vbox to 0pt┼\vss
         \hrule \@height\@tempdima \@width\chgbarwidth \@depth\z@╠╠\hss╠╠
    \global\@chgbarbegin 0pt
\fi
   \ifvoid\footins\else\setbox\@outputbox
     \vbox┼\boxmaxdepth \maxdepth
     \unvbox\@outputbox\vskip\skip\footins\footnoterule\unvbox\footins╠\fi
     \xdef\@freelist┼\@freelist\@midlist╠\gdef\@midlist┼╠\@combinefloats
     \setbox\@outputbox\vbox to\@colht┼\boxmaxdepth\maxdepth
        \@texttop\dimen128=\dp\@outputbox\unvbox\@outputbox
        \vskip-\dimen128\@textbottom╠
     \global\maxdepth\@maxdepth╠
----------------------------------------
--
                                        Dave Johnson
                                        Dept. of Computer Science
                                        Rice University
--
Piet van Oostrum, Vakgroep Informatica, Rijksuniversiteit Utrecht,
Padualaan 14, Postbus 80.089, 3508 TB Utrecht.
Telefoon: 030-531806   Uucp:   uunet!mcsun!hp4nl!ruuinf!piet
Telefax:  030-513791   Internet:  piet AT cs.ruu.nl




Date:Thu, 7 Jun 90 11:37:00 MET
From:    "A. van der Bilt, Padualaan 14 Utrecht, T.533096"
Subject:   cyrillisch font
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Beste TeXers,

Bedankt voor alle reacties op mijn verzoek om inlichtingen over
cyrillische fonts. Het is me inmiddels gelukt een cyrillisch
font te installeren.

Met vriendelijke groet,

Andries van der Bilt



_______________________________________________________________________
   Andries van der Bilt             Telefoon  030 - 533096/533540
   Bijzondere Tandheelkunde         FAX       030 - 521105
   Rijksuniversiteit Utrecht        DECnet    RUUMTC::BILT
   Padualaan 14                     INTERnet  BILT AT ruumtc.tcu.ruu.nl
   3584 CH  Utrecht                 EARN      BILT AT HUTRUU53.BITNET
_______________________________________________________________________




Date:Fri, 8 Jun 90 09:37:00 GMT
From:    WINNINK AT ECN.NL
Subject:   PiCTeX manual
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo TeXers,
     Kan iemand mij vertellen waar ik het PiCTeX manual kan vinden. In een
voorbeeld file, die bij het 'macro' pakket PiCTeX zit wordt hiernaar verwezen.
Alvast bedankt,
                            Jos Winnink

internet: winnink AT ecn.nl




Date:Fri, 8 Jun 90 13:24:36 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   PiCTeX manual
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

 > Hallo TeXers,
 >      Kan iemand mij vertellen waar ik het PiCTeX manual kan vinden. In een
 > voorbeeld file, die bij het 'macro' pakket PiCTeX zit wordt hiernaar verwezen

The PiCTeX documentation is available from the TeX Users Group for $30
the address is:
  P.O. Box 9506
  Providence, RI 02940
  Phone: 401-751-7760
  E-mail: TUG AT math.ams.com

Ik geloof dat de prijs intussen $35 is.

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




Date:Fri, 8 Jun 90 13:59:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   RE: PiCTeX manual
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Het PicTeX manuaal moet je *kopen*. In de file HOWTOGET.MAN o.i.d.
staat hoe dat moet.
De file heeft echter een tijd lang (per ongeluk?) op een Atari server
gestaan. Ik hebt 'm opgehaald & van mij mag je 'm hebben.

Schrijf maar,
Erik-Jan.




Date:Fri, 8 Jun 90 14:40:38 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   RE: PiCTeX manual
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Een andere bron zegt:

Das PiCTeX-Handbuch ist nur direkt vom Autor erhaeltlich; es kostet
$15 plus post&package.

Der Autor ist zu erreichen "uber Email:
        wichura AT galton.UChicago.Edu
oder "uber Snailmail:
        Michael Wichura
        Department of Statistics
        University of Chicago
        5734 University Avenue
        Chicago, IL 60637
        USA




Date:Fri, 8 Jun 90 15:08:00 MET
From:    David van Leeuwen <DAVID AT HLERUL59.BITNET>
Subject:   emmf
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hoi MFfers,

Sinds een tijdje werk ik met het emTeX pakket. Het is lekker volledig, dat
bevalt zeer goed. Minder goed bevalt de snelheid. emTeX is zelf zo'n 20%
(dacht ik) langzamer dan PCTeX, maar het is ook een nieuwere versie (2.997
tegen 2.1) dus misschien ligt het daar aan. Maar de metafont van em is
gewoon heel erg traag. Ik heb geen referentiemetafont anders dan eentje op
een vax, en dat vergelijkt zo slecht, maar deze MF voor de PC doet over
het lezen van de `sharped' parameters van cmr10 (dus de file cmr10.mf)
al ruim een halve minuut. Terwijl het inlezen van parameterwaarden geen
grafisch gereken vereist; alleen wat geheugen toewijzingen. Ik vermoed dus
dat geheugen vinden voor metafont niet helemaal meevalt.

Iets anders dat wel jammer is dat deze metafont op mijn scherm geen uitvoer
kan geven, het is voor cga/ega geschreven, meen ik, maar als ik mijn kaart een
cga laat emuleren gebeurt er niets (grafische mode gaat wel aan).
Wellicht geen goede emulatie.

Weet iemand wat de typische proces tijden zijn van het inlezen van `cmr10.mf'
op een atari, mac, AT, wat dan ook? (dus de tijd tussen `(cmr10.mf...' en
`(roman.mf...' op beeldscherm)

Groet, David van Leeuwen





Date:Mon, 11 Jun 90 15:41:00 GMT
From:    "Gerard van Nes, ENR-Petten" <VANNES AT ECN.NL>
Subject:   ReRe: LaTeX change bars
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Hier een reactie betreffende de change.bar mailing van laatste week.

Van de changebars die ik ontving, gebruik ik nu met succes die van
Dave Johnsen (TeX-NL reply van Piet van Oostrum op 5 juni j.l.).

De enige beperking die ik daarbij heb is dat binnen een tabular
omgeving de bars niet gebruikt kunnen worden.
Ook psfig geeft geen conflict met deze changebar, ECHTER
changebar MOET voor psfig in de parameterlijst van \documentstyle
worden opgenomen.
Verdere output via DVIPS is geen probleem.

Joachim Scrod deelde mij mede dat zijn changebar (gepresenteerd op
EuroTeX 89 in Karlsruhe) in principe alleen binnen TeX werkt.
Hij stelt ze wel beschikbaar voor degenen die de aanpassingen
voor LaTeX omgeving wil maken (vooral in de \output routine).
Laten geinteresseerden contact met mij opnemen.

Gerard van Nes





Date:Wed, 13 Jun 90 10:29:00 CET
From:    LETTVA AT HLERUL2.BITNET
Subject:   Kolommen met alignment
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

  Heeft iemand een idee hoe ik het volgende aan zou kunnen pakken?
Ik heb een lijst van ongeveer 40000 woorden, die met TeX in kolommen
afgedrukt moet worden, en wel zo dat ze aligned zijn op het teken =,
dat net als - en . een morfeemgrens aangeeft. Als het een klein lijstje
is, zou ik het met \halign doen. Een klein stukje
6                                       a=
0                                      a*=
2                                      ba=-bax-em
                                       ba=-c` ETC.
                                       ba=-\v\j- ETC
                                       ba=-m ETC
                                       ba=-n ETC.
0                                      ba=-nal-i
                                       ba=\D r ETC.
0                                    abba=
2                                 o\l b-a=-kc`em
                                       ba=-m.ba-s ETC.
1                              ka\l amb-a=-va\v ca\D r
0                                \D rmb-a=-k`ar
                                       ba=-r.ba-\v\j\ ETC.
                                       ba=-r.ba-D r ETC.
1                                 jer-b-a=-kal
1                                   nrb-a=-jayn
1                                   srb-a=-p`ayl
De getallen zijn codes voor woordsoort. Het probleem is dat ik a
priori niet weet hoe lang voor- en achterstukken kunnen worden.
Bovendien is het zo dat als het voorstuk lang is, het achterstuk
kort is. Vermoedelijk valt er dus ruimte te besparen door niet overal
de = op dezelfde plaats in de kolom te zetten.
Hoe pak ik dit aan?

Andrea de Leeuw van Weenen
Dept of Comparative Linguistics
Universiteit Leiden PO Box 9515, 2300 RA Leiden
The Netherlands, LETTVA AT HLERUL2.BITNET




Date:Wed, 13 Jun 90 10:38:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Victor,

(en plein public) waarom vind je een constructie als
  If something Then a Else b Fi := 5;
nou inzichtelijk?

Voor mijn gevoel geeft het een beter inzicht om Lvalues en RHS bij
elkaar te houden. Dus a:=5 los van b:=5. Leest dat niet veel prettiger?
Als je het opschrijft zoals jij dat doet, dan moet je als ("menselijke")
lezer eerst het hele statement parsen, voordat de betekenis tot je door
dringt. Dus je moet nog onthouden dat je een a had, dan dat er ook nog
een b was, en daarna ken je pas een betekenis toe.

Ik schrijf altijd in C, maar ga er vanuit dat een goede compiler
  ( something ? a : b ) = 5;
zelf wel omzet in
  ( something ? a = 5 : ( c = 5 ) );
oftewel
  if ( something )
    a = 5;
  else

 b = 5;

Ook in Metafont gebruik ik het nooit. Leve de 'hide(gobble gobble
gobble)', maar weg met de oninzichtelijke statements.

Erik-Jan.




Date:Wed, 13 Jun 90 13:00:35 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   Kolommen met alignment
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Het simpelste lijkt het mij om de lijst in stukjes van N regels te knippen
en die in een halign te zetten. N kies je zo dat het net op een pagina
past. Het knippen kan met een goede editor of een simpel programmaatje. In
principe kan het natuurlijk ook met TeX, bijv door de newline (^^M) active
te maken en die te laten tellen en de nodige haligns en accolades etc te
laten invoegen. Waarschijnlijk is dat meer geknutsel dan de eerste
suggestie.

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




Date:Wed, 13 Jun 90 10:12:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   Overgeschreven uit de NRC. Over spelling.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Voor wie ---net als ik--- dit interessant vindt, hier een stukje uit de
NRC van gisteren, 12 juni 1990.

Stoethaspelen met spellen. Door H. Heestermans.

Ik moet eerlijk bekennen dat ik lang heb gedacht dat het Nederlands de
enige taal is waarin merkwaardige spellingsverschijnselen voorkomen. Het
blijkt een onjuiste gedachte te zijn geweest.
    In het meinummer van het maandblad `Onze Taal' schrijft Harry Cohen
over de inconsequenties en domheden in de Duitse en Franse
spellingsvoorschriften. Annelies van Hees besteedt in hetzelfde nummer
aandacht aan de `majonaese'-oorlog die in Denemarken is uitgebroken naar
aanleiding van toegestane dubbelvormen als `majonaese' naast
`mayonnaise' en `spagetti' naast `spaghetti'.
    Allereerst Duitsland. De offici"ele spellingsregeling dateerst van
1901, maar bijna niemand is van die regeling op de hoogte: na 1945 is ze
nooit meer herdrukt. Het Duden-woordenboek `Die Rechtschreibung' heeft
haar functie overgenomen en dit boek wordt dan ook algemeen als norm
aanvaard. Maar: het staat vol inconsequenties.
    Een van de problemen waarmee we ook in de Nederlandse spelling te
maken hebben is: wanneer schrijven we twee woorden aan elkaar en wanneer
niet. Spel ik "zo nodig" of "zonodig", "niet rokers", "niet-rokers" of
"nietrokers"? In `de Duden' staan voor dit aaneenschrijven regels
geformuleerd, maar in het werk zelf blijft de regeling een wildernis.
Naast elkaar treffen we aan: "Auto fahren"\footnote{EJV: of "Tractor
fahren voor wie Otto Waalkes {\oe}uvre kent} (los van elkaar),
"eislaufen" en "radfahren" (aan elkaar). Nog wilder wordt het als we op
het hoofdlettergebruik letten: "ich fahre Rad" naast "ich laufe eis".
    Een volgende kwestie vormen samenstellingen als "Schiff" + "fahrt".
Als je die twee woorden achter elkaar zet, krijg je drie opeenvolgende
`f'-en. Ik zou dat geen enkel bezwaar vinden, maar Duden wel. De
voorgeschreven schrijfwijze is dan ook "Schiffahrt" met twee keer een
`f'. Evenzo spelt Duden "Zollager" en "Sperriegel". Blijkbaar is het
voor alle spellingregelaars moeilijk consequent te zijn, want
"Sauerstoffflasche" en "Fusssohle" behouden hun drie medeklinkers.
    Nu heeft een spellingscommissie van het `Institut f"ur Deutsche
Sprache' de opdracht gekregen een nieuwe regeling te ontwerpen. Ik weet
zeker dat bij het verschijnen daarvan de kranten bol zullen staan van de
negatieve reacties. Spelling werkt nu eenmaal op onze zenuwen.
    Zo'n gestoethaspel kan in Frankrijk niet voorkomen, natuurlijk. Daar
maakt de `Acad'emie fran{\c c}aise' uit hoe elk woord geschreven moet
worden. Ik citeer Harry Cohen: ,,Misschien heeft zo'n gelukzalige
toestand ooit bestaan, maar de Acad'emie heeft al lang geleden laten
weten dat zij niets wil voorschrijven en alleen nog als `registrator van
het gebruik' optreedt. Voor haar befaamde `Dictionnaire' schijnt het
publiek zich tegenwoordig niet meer zo te interesseren. Vroegere edities
moesten nog wel eens herdrukt worden, maar sinds het verschijnen van de
laatste (1932--1935) is daar geen behoefte meer aan geweest.''
    Wie of wat is dan wel de richtsnoer voor de juiste spelling? Het
woordenboek. Voor sommigen is dat de `Petit Larousse', voor anderen de
`Petit Robert' of de `Grand Robert', weer anderen houden het op
`Littr'e'. Een officieel `Groen Boekje', waarin de regels van de
spelling zijn opgenomen, is er volgens Cohen niet.
    Gelukkig wijken de genoemde woordenboeken weinig van elkaar af, maar
toch staan er in Frankrijk voortdurend spellingshervormers op die
proberen het spellingsbeeld beter bij de uitspraak te laten aansluiten.
Ze stellen dus voor om bijvoorbeeld "-oignon" door "-ognon" te
vervangen. Een andere suggestie is om de leden van de woordfamilies aan
elkaar aan te passen. Dat levert dan een wijziging op van "chariot" naar
"charriot" omdat er ook "charette" wordt geschreven.
    De Franse overheid bemoeit zich maar ternauwernood met de
spellingsregels. Er bestaat 'e'en document uit 1976, het zogenaamde
`arr^et'e Habry'. Daarin is een lijst opgenomen (ik citeer Cohen) ,,met
afwijkingen van de gebruikelijke spelling en grammatica die bij de
schoolexamens niet fout mogen worden gerekend''. ,,Zo mogen de
examinandi de schrijfwijze van een woord beter in overeenstemming
brengen door accents aigus toe te voegen ("r'ef'erendum", "ass'ener") en
bestaande accents aigus te vervangen door accents grave ("'ev`enement",
"c`ederai").'' Sommige van de toegelaten varianten zijn intussen door de
woordenboeken tot standaard verheven.
    U ziet, ook Frankrijk morrelt aan de spelling.
    Ten slotte Denemarken. Bij de spellingsregeling van 1986 werden
eigenlijk maar driehonderd woorden echt veranderd. Dat wilde veelal
zeggen dat naast een bestaande vorm (zoals "haefte", schrift) een vorm
"hefte" werd geijkt omdat die voorkwam in het taalgebruik van goede
taalgebruikers.
    En dat zorgde natuurlijk voor de nodige consternatie. Hadden de
Denen niet van ons (1954) kunnen leren dat het onzinnig is om twee
schrijfwijzen naast elkaar toe te staan.
    Misschien is het goed dat al die spellingscommissies uit al die
verschillende landen eens met elkaar zouden confereren. Dat zou hun veel
onzinnige voorstellen besparen. En veel geld.

-------------------------------------------------------------------------------

Tot zover,
Erik-Jan.




Date:Wed, 13 Jun 90 13:34:36 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Erik Jan,

>Victor,
>
>(en plein public) waarom vind je een constructie als
>  If something Then a Else b Fi := 5;
>nou inzichtelijk?

Een verbazende vraag.
1/ Kennelijk bestaat TeXline nog (voor de niet ingewijden: het
hobbyblad van Malcolm Clark; kennelijk heeft het zijn wisseling
van baan overleefd), en
2/ Kennelijk heeft hij een stukje dat ik hem een jaar terug
stuurde geplaatst. Aardig. Heeft ie me nooit wat van verteld.

Nu dan de echte vraag.

De Pascal constructie
 If ... Then a:=5 Else b:=5
is een bijzonder geval van
 If ... Then a:=x Else b:=y
dwz, doe een toewijzing, of een andere.

Soms echter bedoel je iets anders:
 If ... Then a Else b Fi := 5 (pseudo-Pascal; meer Algol-68)
betekent: ik heb een waarde, en die wil ik aan de ene of de
andere variabele toewijzen. Dit uitschrijven als boven is een
geval van overspecificatie; je zegt niet meer wat je bedoelt,
maar je doet alvast een vertaalslag om het de computer makkelijk
te maken.

Anders gezegd: in
 If ... Then a:=5 Else b:=5
ben je de informatie kwijt dat die twee 5-en hetzelfde zijn.
Als het statement ingewikkelder wordt
 If ... Then a Else b Fi   :=  If ... Then 5 Else 6 Fi
dan wordt het zelfs een kwestie van overzichtelijkheid, en
overbodig tiepwerk:
 If ... Then If ... Then a:=5 Else a:=6
        Else If ... Then b:=5 Else b:=6
Grovelijkse overspecificatie. Hier staan vier toewijzingen.
Wat ik bedoel is dat ik twee waardes en twee doelvariabelen heb.

>Ik schrijf altijd in C, maar ga er vanuit dat een goede compiler
>  ( something ? a : b ) = 5;
>zelf wel omzet in
>  ( something ? a = 5 : ( c = 5 ) );
Ha, dat verklaart het. U bent een C-programmeur. Die mensen zijn zich
r de hele tijd van bewust dat er zoiets als een compiler en een
computer bestaat. Verkeerde premisse, mijn waarde.
Een programmeertaal heeft een rigoreuze syntax en semantiek, en
(om de prof van wie ik informatica geleerd heb aan te halen -- maar
niet letterlijk, ik heb het boek niet bij de hand)
  ''of het programma dan wordt uitgevoerd door electronica,
    waterkracht, of voedoe, maakt ons verder niets uit''

Bovendien wil ik betwijfelen of een goede compiler het zo vertaald.
Ik heb ooit een cursus compilerbouw gedaan en daar heb ik een
compiler gemaakt voor een Algol-achtige taal waarin
 If ... Then a Else b Fi :=5
legaal is, en volgens mij werd dat vertaald zodat de
conditional het adres berekende waarheen toegewezen moest
en daarna gaat alles hunky-dory.

Zo voldoende geantwoord?

Waarschijnlijk denkt de rest van het net nu:
 ``waar hebben die idioten het over, wat heeft dit
   met TeX te maken''
Welnu, huiswerk: wat gebeurt er in het volgende stuk TeX:

   \def\bold#1┼┼\bf #1╠╠ \def\slant#1┼┼\sl #1╠╠
   \ifnum1>0 \bold \else \slant \fi ┼een╠ woord

uitleg volgt begin september in de cursus Advanced TeX,
gegeven door Uw aller,

Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  61 3169 (switchboard: 61 1111)
   western spiral arm           fax: +31 80 55 3450
   of the galaxy"
                                u641001 AT HNYKUN11.BITNET
                                      ^
                                      note: changed




Date:Wed, 13 Jun 90 16:58:00 N
From:    "Chris Evelo: MFAGKCHR@HMARL5 (BITNET)" <MFAGKCHR AT HMARL5.BITNET>
Subject:   uuencoded, compressed, tar file.... help!
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Hallo,

Een poosje geleden kreeg ik van Nico de sources voor makeindex.
Compileren met Turbo C ging echter niet al te geweldig. Navraag
bij Nelson Beebe leerde dat er inmiddels al weer een nieuwere versie
is, die mogelijk de betreffende fouten al niet meer bevat.

De sources kreeg ik als uuencoded, compressed, tar file. Uudecode
is natuurlijk geen probleem. Compress echter wel. Ik heb uit Utrecht
de compress utility voor de ST gehaald. Maar die kan alleen 12 en
13 bits compression aan. De betreffende files zijn met 16 bits
gecompressed. Ik heb ook het compress zoo file van hp4nl laten komen.
Dat stond echter in btoa format. Atob heb ik inmiddels geport naar de
ST. En getest met wat readme files. Lijkt in orde. Echter het resulterende
zoo file kan ik niet lezen. Het is, volgens de header, gemaakt met zoo 1.5, en
kennelijk kan zoo 2.01 hier niet mee overweg (of mijn atob is toch niet
goed...). Fizz verteld dat de zoo directory headers zijn verschoven. Dat zou
je dan moeten kunnen lezen via @n,x in zoo. Jammer maar helaas, dit wezenlijke
zoo commando werkt voor zover ik kan nagaan niet op de ST en ook niet op de
VAX (De VAX staat er op de @ als indirect file te interpreteren).

Blijft als voornaamste vraag:
Heeft iemand een werkende (de)compress voor 16 bits compression
voor de ST of voor de VAX?

                                Chris Evelo





Date:Wed, 13 Jun 90 17:19:47 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   uuencoded, compressed, tar file.... help!
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Stuur ze maar even naar mij, dan maak ik er wel een zoo archief van en zet
ze tegelijkertijd in onze ftp/mail-server.

                                Hartelijke groeten,
                                Piet van Oostrum.




Date:Thu, 14 Jun 90 15:57:11 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   uuencoded, compressed, tar file.... help!
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Op 13 Jun 90 schreef Chris Evelo:
 >
 > Blijft als voornaamste vraag:
 > Heeft iemand een werkende (de)compress voor 16 bits compression
 > voor de ST of voor de VAX?
 >
De sources van compress hebben wij op onze mail-server (UNIX/compress.shar).
Waarschijnlijk is deze ook wel op VMS te installeren. Wat betreft de Atari,
de versie daarvoor staat op ATARI-ST/utils/compress.arc. Met 1 MB geheugen
moet een 16bits versie te maken zijn. Door USERMEM voldoende groot te
definieren en de zaak dan te compileren. Vrijwilligers?

Piet




Date:Thu, 14 Jun 90 16:16:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   RE: uuencoded, compressed, tar file.... help!
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Yep, ik heb volgende week wel even tijd ervoor. Ik heb
't al eens voor de IBM RT / AIX aan de praat gebracht (ook door
met USERMEM te 'knoeien'), dus 't zal wel lukken.

Erik-Jan.




Date:Fri, 15 Jun 90 09:06:00 N
From:    POPPELIER AT HUTRUU53.BITNET
Subject:   BibTeX 0.99c
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Een paar jaar geleden implementeerde ik BibTeX 0.99c voor de Atari ST.
Wie heeft datzelfde gedaan voor MS-DOS? Ik heb BibTeX nodig, hier
bij Elsevier, en heb -- eerlijk gezegd -- weinig zin in compileren en
compileren en nog eens compileren als iemand dat reeds heeft gedaan.

Bij voorbaat dank,

Nico




Date:Fri, 15 Jun 90 11:23:00 MET
From:    David van Leeuwen <DAVID AT HLERUL59.BITNET>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hoi, nog even als voorbeeldje van een linker if-else-fi constructie het
volgende:

\iflandscape\vsize\else\hsize\fi = 21.07 true cm
\iflandscape\hsize\else\vsize\fi = 29.7 true cm
\advance\hsize by -1 true in \advance \vsize by -1 true in

Groet, David
         ^  note: still a lowercase v




Date:Fri, 15 Jun 90 11:54:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

MMmmmmmmmmmmmm DaVId,
                ^  ^  note: still lowercase ?????????

ik heb niet gezegd dat ik tegen IF [] FI constructies
in assignments ben. Ik vind het alleen onprettig om ze
in de lhs tegen te komen. Dit stuit me tegen de borst.

Maar waarom dan niet:

  \hsize=\iflandscape 29.7 \else 21.07 \fi true cm
  \vsize=\iflandscape 21.07 \else 29.7 \fi true cm

Over smaak valt gelukkig vaak genoeg te twisten & naar mijn
smaak leest dit prettiger, robuuster en rechtlijniger.

Erik-Jan.




Date:Fri, 15 Jun 90 13:59:00 MET
From:    David van Leeuwen <DAVID AT HLERUL59.BITNET>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

OK, Erik-Jan,

Misschien heb je wel een beetje gelijk. Ik probeerde nog een mooi voorbeeld
te vinden, maar het bleek niet mooi genoeg. Echte fleaks schrijven natuurlijk

\hsize=2\iflandscape9.\else1.0\fi7 true cm \ETC

Een fleak is behalve het resultaat van een tikfout een geflipte freak. OK, dus
if's links van een is/wordt teken zijn lelijk of ondoorzichtig. Maar mag een
constructie als deze dan wel?

\advance\pagecount by 1
\def\pagecount{\ifodd\pageno\oddpagecount\else\evenpagecount\fi}

wat C's `pagecount += 1' tegenpool is? Ik kan er niets aan doen dat \pagecount
de ene keer \evenpagecount voorstelt, en de andere keer \oddpagecount. Misschien
interesseert mij dat dan helemaal niet. (Als ik bijvoorbeeld het aantal formules
per bladzijde wil tellen in \pagecount, maar later besluit dat ik even en oneven
pags verschillend wil behandelen, toegevend dat dit nergens op slaat.)

tot zover maar weer, Avid
                     ^ note: in the central octave 440 Hz





Date:Fri, 15 Jun 90 14:32:42 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   morphemenlijst
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Een paar dagen terug stond er een probleempje op TeX-nl.
Ik citeer:

%  Heeft iemand een idee hoe ik het volgende aan zou kunnen pakken?
%Ik heb een lijst van ongeveer 40000 woorden, die met TeX in kolommen
%afgedrukt moet worden, en wel zo dat ze aligned zijn op het teken =,
%dat net als - en . een morfeemgrens aangeeft. Als het een klein lijstje
%is, zou ik het met \halign doen. Een klein stukje
%6                                       a=
%0                                      a*=
%2                                      ba=-bax-em
%                                       ba=-c` ETC.
%                                       ba=-\v\j- ETC
%                                       ba=-m ETC
%                                       ba=-n ETC.
%De getallen zijn codes voor woordsoort. Het probleem is dat ik a
%priori niet weet hoe lang voor- en achterstukken kunnen worden.
%Bovendien is het zo dat als het voorstuk lang is, het achterstuk
%kort is. Vermoedelijk valt er dus ruimte te besparen door niet overal
%de = op dezelfde plaats in de kolom te zetten.
%Hoe pak ik dit aan?
%
% Hier is een voorstel voor een oplossing.
%
% Allereerst dit: \halign zou nooit werken om dat je
% met een tabel van 40000 regels volkomen uit je geheugen knalt.
% Tabbing macros zouden hier mogelijk zijn, maar die zijn heel traag.
% Dus (zoals Knuth al suggereert op pg 235/6) doelgerichte macros.
%
% De oplossing hier is waarschijnlijk minimaal:
% je hoeft alleen \beginlijst boven,
% en \eindlijst onder de lijst te zetten. Verder geen een
% commando. (Dit is wat ik zo leuk vind aan TeX: alles kan willekeurig
% ver geautomatiseerd worden.)
% Hackers in spe mogen uitzoeken wat hier voor
% mega-trucs met catcodes uitgehaald worden (joepie de poepie!).
% En let wel: recursie zonder stack overflow!
%

\def\D{} %deze stond in de invoer. kenniknie

%%%%%%%%%%%%% A F M E T I N G E N %%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%naar behoeven bij te stellen.

%mimimaal wit tussen woordsoort en deel voor de `='
\newdimen\minimumseparatie \minimumseparatie=1cm

%maximaal breedte van voorstuk voor de `=' moet gaan schuiven
\newdimen\maximumkop
\maximumkop=4cm

%maximale breedte van het woordsoortcijfer
\newdimen\maximalesoortbreedte
{\setbox0=\hbox{999\hskip.5em} \global\maximalesoortbreedte=\wd0}

%%%%%%%%%%%%%% M A C R O S
%afblijven als je het niet snapt.
%zelfs geen commentaren verwijderen!!!

\def\beginlijst{\begingroup\catcode13=12\relax\par
    \expandafter\startlijst\hap}
\def\hap#1{}%verwijder een regeleinde
\def\startlijst{\ziespaties\paksoort}
\def\eindlijst{\endgroup\hap}

\catcode13=12 \endlinechar=-1 %enkel voor de duur van de definities.

\def\ziespaties{\bgroup\catcode32=12\relax}
\ziespaties\gdef\paksoort#1 {\gdef\soort{#1}\egroup\regel}\egroup

\def\regel#1=#2^^M{\noindent
    \hbox to \maximalesoortbreedte{\soort\hfil}
    \hskip\minimumseparatie
    \setbox1=\hbox{#1}
    \ifdim\wd1<\maximumkop \hbox to \maximumkop{\hfil#1}
          \else #1\fi
    $=$#2\par
    \ziespaties\global\futurelet\next\stoppenofdoorgaan}
\def\stoppenofdoorgaan{\ifx\next\eindlijst \egroup
    \else \let\next\paksoort \fi \next}

\endlinechar=13 \catcode13=5 %sluit definities af
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%


\beginlijst
6                                       a=
0                                      a*=
2                                      ba=-bax-em
                                       ba=-c` ETC.
                                       ba=-\v\j- ETC
                                       ba=-m ETC
                                       ba=-n ETC.
0                                      ba=-nal-i
                                       ba=\D r ETC.
0                                    abba=
2                                 o\l b-a=-kc`em
                                       ba=-m.ba-s ETC.
1                              ka\l amb-a=-va\v ca\D r
123 mor-phe-mi-sa-tie-drang-neu-ro-se= ETC.
0                                \D rmb-a=-k`ar
                                       ba=-r.ba-\v\j\ ETC.
                                       ba=-r.ba-D r ETC.
1                                 jer-b-a=-kal
1                                   nrb-a=-jayn
1                                   srb-a=-p`ayl
\eindlijst

\bye

%Problem courtesy
%Andrea de Leeuw van Weenen
%Dept of Comparative Linguistics
%Universiteit Leiden PO Box 9515, 2300 RA Leiden
%The Netherlands, LETTVA AT HLERUL2.BITNET

%Solution copyright
%Victor Eijkhout
%Flying-V soft
%all rights reserved.

Alle trucs worden uitgelegd op de cursus Advanced TeX,
3--5 september Groningen, 7--8 September Cork.

Tenslotte
- plaagstootje: is er iemand die denkt dat dit zelfs maar bij
 benadering zo makkelijk kan met LaTeX?
- dit voorbeeld sterkt me in mijn overtuiging dat een
 gedegen kennis van de basismechanismen van TeX (de 'mond', catcodes,
 expansie) cruciaal is voor ongeveer alles wat zich twee millimeter
 buiten het rechte pad begeeft. In vergelijking zijn boxen, macros,
 tabellen, en misschien zelfs uitvoerroutines triviaal.

Gross generalizations courtesy of,
yours sincerely,

Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  61 3169 (switchboard: 61 1111)
   western spiral arm           fax: +31 80 55 3450
   of the galaxy"
                                u641001 AT HNYKUN11.BITNET
                                      ^
                                      note: changed




Date:Fri, 15 Jun 90 15:13:56 MET
From:    Willem Jan Karman <U605005 AT HNYKUN11.BITNET>
Subject:   drivers gezocht
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,

Wie kan mij helpen aan de netwerk-locatie, waar ik dvi-drivers kan
vinden voor een HP-Deskjet-Plus, een voor  Atari-1040 en een voor ms-dos.

Bij voorbaat hartelijke dank,


Willem Jan Karman
Universiteit Nijmegen




Date:Fri, 15 Jun 90 15:31:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   Re: TeXline X. And now for something completely \else
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>> \hsize=2\iflandscape9.\else1.0\fi7 true cm \ETC
is helemaal flippie-de-bippie. Laat ik het zo formuleren:

Ik (ik, dus) heb slechts een beperkt brein. Ik wil graag
kunnen blijven snappen wat ik zelf doe & daarnaast de
mogelijkheid hebben te kunnen doorgronden wat anderen
bedoelen. Wanneer iemand zo'n "blabla-worstebroodje"
formule opschrijft, kost het mij Xtra moeite om de
bedoelingen te doorgronden.

Nu was het begin van deze briefwisseling een artikel van
Victor in TeXline over de mogelijkheden die TeX zou kunnen
bieden om dit soort constructies te fabrieken. Dat was
gewoon een leesbaar artikel. Alleen ik viel over zijn
opmerking dat dergelijke code "to me is superior, as well
as conceptually more correct". En wat ik vooral wil benadrukken
is, dat het, als het voor mij ondoorgrondelijker is, zeer
waarschijnlijk niet een eenduidig conceptueel correcte
oplossing kan zijn.                                   ^re

Erik-Jan.




Date:Fri, 15 Jun 90 15:34:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   RE: drivers gezocht
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

In elk geval staat op <sol.cs.ruu.nl> in de
directory </pub/ATARI-ST/tex> een file <dvidsk.arc>
waarin een deskjet-driver vanuit de Atari-ST zit.

Erik-Jan.




Date:Fri, 15 Jun 90 15:47:00 GMT
From:    WINNINK AT ECN.NL
Subject:   RE: BibTeX 0.99c
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Nico,
      Ik stuur je wel een  versie van BIBTEX0.99c voor MS-DOS. Het is een
ge uuencode 'zip'
                                Jos Winnink
interner: winnink AT ecn.nl




Date:Sat, 16 Jun 90 14:45:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   Eric Gill biografie
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hoi allemaal,

(wat mij betreft verder in het publiek gezwegen over conditionele
statements, ook al wil ik via persoonlijke mail best doorgaan over
helderheid van uitdrukken!)

Er is een paperback uitvoering van de biografie van Eric Gill door Fiona
MacCarthy door faber and faber (ff) op de markt gebracht. (First
published in 1989 by Faber and Faber Limited ... Reprinted in 1989
(three times). This paperback edition first published in 1990. ISBN
0-571-14302-4) 't Kost slechts Hfl 33,50 (UK \pounds 7.99 net, Canada
$16.95) en telt meer dan driehonderd pagina's.
Volgens de achterflap:
   "Eric Gill was perhaps the greatest English artist-craftsman of the
    twentieth century: a typographer and lettercutter of genius, and a
    master in the art of sculpture and wood-engraving.
      We are delighted to be publishing Fiona MacCarthy's widely
    acclaimed biography as a paperback to coincide with the 50th
    anniversary of Gill's Death.
      'A wonderfully detailed account of his personality - so vivid, you
    feel you know just what it would have been like to visit him at one
    of his patriarchal communes...
      A Dominican, dining with the Gills, once thought he saw a nimbus
    shining around Eric's head. Despite the sexual improprieties it
    unearths, MacCarthy's authoritative biography allows you to
    understand how someone might have thought that.' John Carey in the
    Sunday Times"

Have a nice weekend,
Erik-Jan.





Date:Mon, 18 Jun 90 00:06:00 MET
From:    CGL AT RUG.NL
Subject:   SGML-TeX bijeenkomst aug 90; Opgave cursussen en conferentie.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,
Weinig, te weinig, NTG leden hebben zich tot nu toe aangemeld.
Bedenk dat de opgave voor cursussen NU belangrijk is, omdat deze maand
besloten wordt welke cursussen doorgaan en welke geannuleerd worden.
/Wverslag
Info over SGML cursussen is dit weekend verstuurd.)
Kees




Date:Mon, 18 Jun 90 12:53:00 GMT
From:    "Gerard van Nes, ENR-Petten" <VANNES AT ECN.NL>
Subject:   NTG > information just posted to NTG members
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>




Met het weekend zijn de volgende papieren aan alle NTG leden verstuurd:
1. Ledenlijst (update 31 mei 1990) met informatie over ondermeer
   hardware configuratie.
2. Informatie over de SGML cursussen aug/sept '90 te Groningen.
3. Folder Europese TeX bijeenkomst begin begin sept te Cork.
4. Laatste informatie over de SGML-TeX bijeenkomst aug/sept '90 te
   Groningen (zie hiervoor ook het vorige NTG verslag).

NTG leden ontvangen bij zowel de conferentie te Cork als die te
Groningen een belangrijke reductie op de deelnemingskosten.


Gerard van Nes
Secretaris NTG




Date:Mon, 18 Jun 90 12:47:00 MET
From:    Daniel Kropveld <KROPVELD AT AMC.UVA.NL>
Subject:   deskjet driver
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

]Hallo,
]
]Wie kan mij helpen aan de netwerk-locatie, waar ik dvi-drivers kan
]vinden voor een HP-Deskjet-Plus, een voor  Atari-1040 en een voor ms-dos.
]
]Bij voorbaat hartelijke dank,
]
]
]Willem Jan Karman
]Universiteit Nijmegen

In Heidelberg is erg veel TeX spul.

SEND LISTSERV@DHDURZ1 SEND RUMHELP UUE
SEND LISTSERV@DHDURZ1 SEND RUMDJET UUE

``RUMDJET, a DVI driver for the HP DeskJet printer using MS-DOS,
from W. Kaspar (et al.)''

succes! Dani/"el






Date:Mon, 18 Jun 90 15:21:51 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   Pre-publication (read: shameless plug)
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Volkomen zonder bijbedoelingen (te weinig aanmeldingen voor
de cursussen? wat heb ik daarmee te maken?)
volgt hier een klein stukje TeX dat ik voor Tugboat schreef,
om meer 'tutoriele' stukjes in dat blad te hebben.

(de tugboat stijlen staan op de server)

...............................................
\documentstyle[ltugboat]{article}

\def\cs#1{{\tt \char92 #1}}
\begin{document}

\title{An indentation scheme}
\author{Victor Eijkhout}
\address{Department of Mathematics\\
        University of Nijmegen\\
        Toernooiveld 5\\
        6525 ED Nijmegen, The Netherlands}
\netaddress[\network{Bitnet}]{u641001@HNYKUN11}
\maketitle

\noindent
Indentation is one of the simpler things in \TeX:
if you leave one input line open you get a new
paragraph, and it is indented unless you say \cs{noindent}.
And if you get tired of writing \cs{noindent}
all of the time, you declare \begin{verbatim}\parindent=0pt\end{verbatim}
at the start of your document. Easy.

More sophisticated approaches to indentation are possible,
however. In this article I will sketch a quite general approach
that can easily be incorporated in existing macro packages.
For a better appreciation of what goes on, I will start
with a tutorial section on what happens when
\TeX\ starts a paragraph.

\section{Tutorial: paragraph start}

When \TeX\ is not busy typesetting mathematics, it is processing
in {\em horizontal mode}, or {\em vertical mode}. In horizontal
mode it is putting objects --~usually characters~-- next to each other,
in vertical mode it is putting objects --~usually lines of
text~-- on top of each other.

To see that there is a difference, run the following pieces of
code through \TeX:
\begin{verbatim}
\hbox{a}
\hbox{b}
\bye\end{verbatim}
and
\begin{verbatim}
a
\hbox{b}
\hbox{c}
\bye\end{verbatim}
You notice that the same objects are treated in two different ways.
The reason for this is that \TeX\ starts each job in vertical mode,
that is, stacking material. In the second piece of input
\TeX\ saw the character `a' before it saw the boxes. A~character
is for \TeX\ the sign to switch to horizontal mode, that is,
lining up material, and start building a paragraph.

Commands that can make \TeX\ switch to horizontal mode
are called `horizontal commands'. As appeared from the above
two examples characters are horizontal commands, but boxes
are not.
Let us now look at the two most obvious horizontal commands:
\cs{indent} and \cs{noindent}.

\subsection{\cs{indent} and \cs{noindent}}

\cs{indent} is the command to start a paragraph with
indentation. \TeX\ realizes the indentation by inserting
a box of width \cs{parindent}. If you say \cs{indent}
somewhere in the middle of a paragraph you get some white
space there, caused by the empty box.

\cs{noindent} is the command to start a paragraph without
indentation. After this command \TeX\ merely switches to
horizontal mode; no indentation box is inserted. If you
give this command somewhere in the middle of a paragraph
it has no effect at all.

If \TeX\ sees a horizontal command that is not \cs{indent}
or \cs{noindent}, for instance a character,
it acts as if the command was preceded
by \cs{indent}. This is why paragraphs usually start with
an indentation.

As an illustration here is a small variation on the above
two examples:
\begin{verbatim}
\noindent
\hbox{a}
\hbox{b}

\indent
\hbox{a}
\hbox{b}
\bye\end{verbatim}

\subsection{\cs{everypar}}

\TeX\ performs another action when it starts a paragraph:
it inserts whatever is currently the contents of the
token list \cs{everypar}. Usually you don't notice this,
because the token list is empty in plain \TeX\ (the
\TeX\ book~\cite{DeK} gives only a simple example,
and the exhortation `if you let your imagination
run you will think of better applications').
\LaTeX~\cite{LL}, however, makes regular use of  \cs{everypar}.
Some mega-trickery with \cs{everypar} can be found in~\cite{E}.

\everypar{$\bullet\quad$}
Just to show how this works, I put in front of this
paragraph the statement
%V I just love this
\[\hbox to \hsize{\verb>\everypar={$\bullet\quad$}>\hfil}\]
That is, I~told \TeX\ that \verb-$\bullet\quad$-
should be inserted in front of a paragraph.

There's nothing specified for this paragraph; I get the
bullet for  free, as \cs{everypar} does exactly what
its name promises: it is inserted in front of {\em every\/}
paragraph.\everypar{}

At the end of the previous paragraph I specified
\begin{verbatim}\everypar={}\end{verbatim}
so nothing is inserted from this paragraph onwards.

\subsection{Removing indentation}

Every \TeX\ user knows that
indentation can be prevented
globally by setting \cs{parindent} to zero. However, this
is rather crude, and if you use the plain \TeX\ macros
you may notice several rather unpleasant side effects of this action,
for instance when you use the macros \cs{item} and \cs{footnote}.

It is possible to use \cs{everypar} to prevent indentation,
or more correctly: to remove indentation. This can be achieved
by \begin{verbatim}\everypar={{\setbox0=\lastbox}}\end{verbatim}
This needs some explanation.

If the last item that was processed by \TeX\ is a box, then that
box is accessible by the command \cs{lastbox}. If the last item
was not a box then \cs{lastbox} is an empty box, but no error
ensues. As the \cs{everypar}
list is inserted after any indentation box, the
\cs{lastbox} command will get hold of the indentation box if
there is one.
By assigning the last box to another box register --~here
\cs{box0}~-- it is removed from where it was previously.

Finally, the statement \begin{verbatim}\setbox0=\lastbox\end{verbatim}
is enclosed in braces. \TeX's grouping mechanism restores values
when the group ends that were current when the group began.
In this case it has the effect of totally removing the indentation
box: first it is taken and assigned to \cs{box0}, then the value
of \cs{box0} is restored to whatever it was before the group began.

\subsection{Other actions at the start of a paragraph}

In the above discussion I have omitted one action that takes
place at the start of a paragraph: \TeX\ inserts
(vertical) \cs{parskip}
glue above the paragraph. As this has no relevance for
the subject of indentation I will not go into it any further.
However, in a subsequent article I will give more
information about \cs{parskip}.

\section{To indent or not to indent}

In classical book typography~\cite{M} every paragraph
is indented, with
the exception of the first paragraph of a chapter.
Nowadays a design where no paragraph indents is quite
common.
There are two mixtures between
always indenting and never indenting: occasionally indenting, and
occasionally not indenting.
Thus it seems possible to
characterize indentation strategies by two yes/no
parameters: one that decides whether paragraphs
should indent in principle, and another parameter that can overrule
those decisions. Let us now see how this can be implemented in \TeX.

\subsection{Implementation}

Above I have already indicated that changes to \cs{parindent} should
be avoided. Let us then assume that \cs{parindent} is greater
than zero, even if we will never indent a paragraph
(see \cite{BEP} for other uses for the \cs{parindent} quantity).
We must then realize unindented paragraphs by removing their
indentation as explained above.

First we need a macro for removing the indentation:
\begin{verbatim}
\def\removeindentation
    {{\setbox0=\lastbox}}
\end{verbatim}
Then we need the switches that control indentation:
\begin{verbatim}
\newif\ifNeedIndent %as a rule
\newif\ifneedindent %special cases
\end{verbatim}
Now for the definition of \cs{everypar}. This is a bit tricky.

Let us first collect some bits and pieces. The main question
is to decide when \cs{removeindent} should be called.
This is for instance the case if \cs{NeedIndentfalse},
and that parameter is not overruled by \cs{needindenttrue}.
\begin{verbatim}
\ifNeedIndent
    \ifneedindent
    \else \removeindent
\fi \fi
\end{verbatim}
Indentation should also be removed
in case \cs{NeedIndenttrue},
but when that parameter is overruled by \cs{needindentfalse}.
\begin{verbatim}
\ifNeedIndent
\else \ifneedindent
      \else \removeindent
\fi   \fi
\end{verbatim}
Next we should make sure that \cs{ifneedindent} is used
only for exceptional cases: if the user or a macro
sets this parameter to a different value from \cs{ifNeedIndent},
then that should be obeyed exactly once.
\begin{verbatim}
\ifNeedIndent
      \ifneedindent
      \else \needindenttrue \fi
\else \ifneedindent \needindentfalse
\fi   \fi
\end{verbatim}
This is then the full definition of \cs{everypar}:
\begin{verbatim}
\everypar={\controlledindentation}
\def\controlledindentation
   {\ifNeedIndent
          \ifneedindent
          \else \removeindent
                \needindenttrue
          \fi
    \else \ifneedindent
                \needindentfalse
          \else \removeindent
    \fi   \fi}
\end{verbatim}

Another implementation would be possible:
\begin{verbatim}
\def\controlledindentation
   {\ifneedindent
    \else \removeindent \fi
    \let\ifneedindent=\ifNeedIndent}
\end{verbatim}
This saves one conditional, but for most paragraphs
it involves an unnecessary \cs{let} command.

\subsection{Usage}

My aim in developing this indentation scheme was to hide all
commands pertaining to indentation in macros.
The user should have to specify only once whether paragraphs
should indent as a rule:
\begin{verbatim}\NeedIndenttrue\end{verbatim}
and then macros should declare the exceptions:
\begin{verbatim}
\def\section#1{...
    \needindentfalse
    ...}\end{verbatim}

\subsection{But couldn't you simply \dots?}

Maybe people who read this have written macros themselves that
end like
\begin{verbatim}
\def\section#1{...
    ...
    \noindent}\end{verbatim}
or
\begin{verbatim}
\def\section#1\par{...
    ...
    \noindent}\end{verbatim}
This works reasonably well, but it is not completely safe.
In the first case there shouldn't be an empty line after
a \begin{verbatim}\section{...}\end{verbatim} call,
and in the second case there can only be one empty line
after \begin{verbatim}\section ... \end{verbatim}
The reason for this is that {\em every\/} empty line
generates a \cs{par} command, which annuls the effect
of the \cs{noindent}. Hence the more drastic approach.

Such considerations as the above may not seem important.
After all: you wrote the macros, you know that there should
be only one empty line in the input. However, if your macros
are going to be used by other people than just yourself
you may as well include some safeguards. Or you may just
want to protect yourself from your own forgetfulness.
The more complicated a macro is, the higher the chance that
you'll make a mistake using it.

\section{Conclusion}

In a systematic layout indentation commands need never be
typed by the user; they can all be hidden in macros.
Using \cs{everypar} it is possible to prevent indentation
both in single instances, and throughout the document.
This has the advantage that is is not necessary
to zero the \cs{parindent} parameter or use \cs{indent} and
\cs{noindent} instructions.

The approach of employing \cs{everypar} as sketched above
can  also be used for a paragraph skip scheme, as I will
show in a subsequent article.

\begingroup
\parskip=6pt plus 3pt \parindent=0pt
\begin{thebibliography}9

\bibitem{DeK}Donald Knuth, The \TeX\ book,
Addison-Wesley Publishing Company, 1984.
%Donald Knuth, \TB, 1984.

\bibitem{LL} Leslie Lamport, \LaTeX, a document preparation
system, Addison-Wesley Publishing Company, 1986.

\bibitem{E}Victor Eijkhout,
Unusual paragraph shapes, Tugboat vol.~11 (1990) \#1, pp.~51--53.

\bibitem{M} Stanley Morison, First principles of typography,
Cambridge University Press, 1936.

\bibitem{BEP}J. Braams, V.~Eijkhout, N.A.F.M.~Poppelier,
The development of national \LaTeX\ styles,
TUGboat vol.~10 (1989) \#3, pp.~401--406.

\end{thebibliography}\endgroup

\makesignature

\end{document}


Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  61 2986 (secretary)
   western spiral arm           fax: +31 80 55 3450
   of the galaxy"
                                u641001 AT HNYKUN11.BITNET
                                      ^
                                      note: changed




Date:Tue, 19 Jun 90 11:08:00 MET
From:    "POW!!! There is a heppy lend, fur, fur a-way" <VENS AT RUG.NL>
Subject:   VoetBal.TeX door Opland
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

% VoetBal.tex naar een tekening van Opland uit "De Groene Amsterdammer" van 13
% juni 1990.
%
\parindent=0cm \nopagenumbers
%
\newdimen\balbreedte \balbreedte=10cm\relax
\newdimen\stipbreedte \stipbreedte=\balbreedte \divide\stipbreedte by4\relax
%
\def\stip{\vrule width\stipbreedte height\stipbreedte depth 0cm\relax}
\def\geenstip{\vbox to\stipbreedte{\hbox to\stipbreedte{\hfil}\vfill}}
%
\def\bal{\hsize=\balbreedte \advance\hsize by5mm\relax
  \vbox to\balbreedte{%
    \vfill\vfill
    \hbox to\balbreedte{%
      \hfill\hfill\stip\hfill\geenstip\hfill\stip\hfill\hfill}
    \vfill
    \hbox to\balbreedte{\hfill\stip\hfill}
    \vfill
    \hbox to\balbreedte{%
      \hfill\hfill\stip\hfill\geenstip\hfill\stip\hfill\hfill}
    \vfill\vfill}}
%
\long\def\boxit#1{\vbox{\hrule height2mm\hbox{\vrule width2mm\kern.25cm%
\vbox{\kern.25cm\strut#1\strut\kern.25cm}\kern.25cm\vrule width2mm}\hrule
height 2mm}}
%
\def\grasspriet{\vrule width1.1mm height2mm}
\newcount\grasteller
\def\grasjes{\grasteller=10 \loop\ifnum\grasteller>0 \hfil\grasspriet
  \advance\grasteller by-1 \repeat \hfil}
\def\grasmat{\hrule width\hsize height2cm}
%
\line{\grasjes\boxit{\bal}\grasjes}
\grasmat
\bigskip
\centerline{Het Anti-Voetbalgevoel}
%
\bye




Date:Tue, 19 Jun 90 15:00:54 -0100
From:    Kees Koster <kees AT DUTTWTA.TUDELFT.NL>
Subject:   LaTeX figuurnummering vraag
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Ik wil in een rapport mijn figuren als volgt nummeren:
fig 1, 2a, 2b, 3, 4, 5a, 5b, 6 etc.
       --  --        --  --

Hoe doe ik dit in LaTeX?

BVD voor een antwoord,

Kees Koster

----------------------------------------------------------------------
e-mail:  kees AT duttwta.tudelft.nl
----------------------------------------------------------------------




Date:Tue, 19 Jun 90 16:41:00 -0100
From:    Rob Kuyper <robk AT DUTTWTA.TUDELFT.NL>
Subject:   help
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

register Rob Kuyper
subscribe tex-nl Rob Kuyper





Date:Tue, 19 Jun 90 16:54:47 +0200
From:    vansoest AT CS.UTWENTE.NL
Subject:   latex subequations
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Zie onderstaande file subeqn.sty:

%%% File: subeqn.sty
%%% The subequations environment %%%
%
% Within the subequations environment, the only change is that
% equations are labeled differently.  The number stays the same,
% and lower case letters are appended.  For example, if after doing
% three equations, numbered 1, 2, and 3, you start a subequations
% environmment and do three more equations, they will be numbered
% 4a, 4b, and 4c.  After you end the subequations environment, the
% next equation will be numbered 5.
%
% Both text and equations can be put inside the subequations environment.
%
% If you make any improvements, I'd like to hear about them.
%
% Stephen Gildea
% MIT Earth Resources Lab
% Cambridge, Mass. 02139
% mit-erl!gildea
% gildea AT erl.mit.edu
%
\newtoks\@stequation

\def\subequations{\refstepcounter{equation}%
  \edef\@savedequation{\the\c@equation}%
  \@stequation=\expandafter{\theequation}%   %only want \theequation
  \edef\@savedtheequation{\the\@stequation}% %expanded once
  \edef\oldtheequation{\theequation}%
  \setcounter{equation}{0}%
  \def\theequation{\oldtheequation\alph{equation}}}

\def\endsubequations{%
  \setcounter{equation}{\@savedequation}%
  \@stequation=\expandafter{\@savedtheequation}%
  \edef\theequation{\the\@stequation}%
  \global\@ignoretrue}






Date:Tue, 19 Jun 90 19:36:14 met
From:    "A. Al Dhahir" <aldhahir AT MATH.UTWENTE.NL>
Subject:   LaTeX figuurnummering vraag
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Er is een multibox.sty file op Clarkson die dat in een picture
omgeving het zelfde doet. De file is te vinden op de directory:
             pub/latex-style
en kan opgehaald worden via ftp.   (sun.soe.clarkson.edu).

Alaaddin




Date:Tue, 19 Jun 90 20:25:13 met
From:    "A. Al Dhahir" <aldhahir AT MATH.UTWENTE.NL>
Subject:   fig 4a, 4b
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Beste Collega's,

In mijn vorige e-mail, heb ik eigenlijk de subfigure.sty bedoeld.

Sorry.

Alaaddin




Date:Wed, 20 Jun 90 10:54:00 MET
From:    David van Leeuwen <DAVID AT HLERUL59.BITNET>
Subject:   RE: VoetBal.TeX door Opland
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Het Anti-Voetbalgevoel wordt verhevigd wanneer afgedrukt op printer met
oranje inkt.




Date:Wed, 20 Jun 90 12:54:00 MET
From:    CGL AT RUG.NL
Subject:   A useful document about LaTeX questions asked over and over. Kees
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

From:      IN%"GUT AT FRULM11.BITNET"  "Groupe francophone des Utilisateurs
N-
   1990 21:54:32.22
To:     Kees van der LAAN -NTG chairman- <CGL AT RUG.NL>, "Erik-Jan VENS -ICCE, Uni
 Gr
   oningen-" <VENS AT RUG.NL>
CC:
Subj:   Frequently Asked Questions about TeX, etc., with answers

Received: from JNET-DAEMON by RUG.NL; Tue, 19 Jun 90 21:52 MET
Received: From FRULM11(MAILER) by HGRRUG5 with Jnet id 2941 for CGL@HGRRUG5;
 Tue, 19 Jun 90 21:52 B
Received: by FRULM11 (Mailer R2.05) id 2714; Tue, 19 Jun 90 17:39:55 SET
Date: Tue, 19 Jun 90 17:20:35 +0200
From: Philippe Louarn <Philippe.Louarn AT IRISA.FR>
Subject: Frequently Asked Questions about TeX, etc., with answers
Sender: Groupe francophone des Utilisateurs TeX <GUT AT FRULM11.BITNET>
To: Kees van der LAAN -NTG chairman- <CGL AT RUG.NL>,
 "Erik-Jan VENS -ICCE, Uni. Groningen-" <VENS AT RUG.NL>
Reply-to: Groupe francophone des Utilisateurs TeX <GUT AT FRULM11.BITNET>
Comments: Sent by  Philippe.Louarn AT irisa.fr

J'ai recupere dans le news_group comp.text.tex des news internet le
petit fichier suivant (en anglais, malheureusement...). Il me semble
qu'il peut interesser bien du monde dans la communaute TeX francophone.

Ph. Louarn - secretariat GUTenberg, c/o Irisa, Rennes.

---> coupez ici <----------------------------------------------------
\documentstyle[A4]{article}
\parindent0pt
\parskip1mm
\begin{document}
\title{Frequently Asked Questions about \TeX{}, etc., with Answers}
\author{Bobby Bodenheimer}
\date{}

\maketitle

\begin{verbatim}
|=============================================================================|
|  Bobby Bodenheimer                             @hot.caltech.edu             |
|  // BITNET: bobby AT caltech.bitnet               |                            |
|  // ARPA  : bobby AT csvax.caltech.edu            | Woof!                      |
|  // UUCP  : {amdahl,ames!elroy}!cit-vax!bobby  |                            |
|=============================================================================|
\end{verbatim}

This article contains answers to some frequently asked questions on
{\tt comp.text.tex}. Please don't ask these questions again, as they've been
answered many times before.

This article includes answers to:
\begin{enumerate}
\item Where can I get a DVI to PostScript conversion program?
\item How can I include a PostScript figure in \LaTeX{}?
\item Where can I find a DVI previewer for machine Y running Q?
\item Where can I get the manual for PiCTeX?
\item What is VorTeX and where can I get it?
\item What is OzTeX and where can I get it?
\item What is Fig and where can I get it?
\item How do I get WEB for C or FORTRAN?
\item How can I typeset music in \TeX{}?
\item What is TUG and TUGboat?
\item How do I convert Adobe's afm files to tfm format?
\item In \LaTeX{}, how do I get a double-spaced document?
\item In \LaTeX{}, how do I include a file in the verbatim environment?
\item In \LaTeX{}, how do I do Y?
\item Where can I find a \LaTeX{} style file for doing Y?
\item How do I generate an index in \TeX{}/\LaTeX{}?
\item Where  do I get METAFONT to do what I want it to do?
\item Where do I get \TeX{}/\LaTeX{} for machine Y running Q?
\item What is the Clarkson archive server?
\item Where can I get a thesis style for \LaTeX{}?
\item How do I get symbols for ``the real numbers", ``the complex numbers",
      and so on?
\item How do I get \TeX{} material if I do not have access to anonymous
      ftp?
 \end{enumerate}

These are all legitimate questions, but they seem to appear too frequently
for long-time readers of the list.

Many of the answers below tell you that you can obtain something
through anonymous ftp. Remember that anonymous ftp is a privilege
and that the system administrators for these sites have made these
files available out of their own generosity. Therefore please restrict
your ftp'ing to non-prime hours at the various sites.

I would like to acknowledge Don Hosek, Ken Yap, Tomas Rokicki, and
Micah Beck, whose postings provided many of the answers. Joe Weening,
Hal Perkins, Walter Carlip, Max Hailpern, Tad Guy, Raymond Chen, Henning
Schulzrinne, and Sebastian Rahtz provided additional material and criticisms.
The format of this document is based on that of the Frequently Asked
Questions appearing in {\tt comp.unix.wizards}, and written by Steve Hayman.
Any mistakes are mine. Corrections, suggestions, and additions to
{\tt bobby AT hot.caltech.edu}.

This is version 1.5, last changed 6/7/90.

\section{ Where can I get a DVI to PostScript conversion program?}

   Three very nice DVI to PostScript conversion programs that run
   under Unix are:
\begin{description}
\item[     dvitps] - part of the \TeX{}PS package by Stephan Bectolsheim.
       Available via anonymous ftp from {\tt arthur.cs.pur\-due.edu}
       (128.10.2.1) in {\tt ./pub/TeXPS}.
\item[     dvi3ps] - by Kevin Coombes. Available via anonymous ftp
       from {\tt tut.cis.ohio-state.edu} (128.146.8.60) in
       {\tt ./pub/dvi3ps.tar.Z }
\item[     dvips] - by Tomas Rokicki. This driver (in version 5.0 and later)
       has the ability to deal with the virtual fonts of \TeX{} 3.0.
       Version 4.21 is for versions of \TeX{} before 3.0 (or 2.995).
       Available via anonymous ftp from {\tt labrea.stanford.edu}
       (36.8.0.47) in {\tt ./pub}.
\end{description}

\section{How can I include a PostScript figure in \LaTeX{}?}

   Perhaps the best way to do this is to use the psfig macros written
   by Trevor Darrell. They are available via anonymous ftp from
   {\tt whitechapel.media.mit.edu} (18.85.0.124) in {\tt ./psfig} or
   {\tt linc.cis.upenn.edu} (130.91.6.8) in the directory {\tt ./dist/psfig}. Yo
   will also need a dvi to PostScript conversion program that supports
   the macros. The ones mentioned in question 1 do. The psfig macros
   work best with Encapsulated PostScript Files (EPS). In particular, psfig
   will need the file to have a BoundingBox (see Appendix C of the
   \_PostScript Language Reference Manual\_). If you don't have an EPS
   file, life can be difficult.


\section{ Where can I find a DVI previewer for machine Y running Q?}

   This briefly lists some previewers which are available via anonymous
   ftp:

\begin{description}
\item[      dvipage] - For SunView. Available via anonymous ftp from
        {\tt june.cs.washington.edu} (128.95.1.4) in {\tt ./tex/dvi\-pages.tar.Z
\item[      xtex] - For X Windows. Available via anonymous ftp from
        {\tt expo.lcs.mit.edu} (18.30.0.212) in {\tt ./contrib/See\-TeX-2.15.tar
\item[      dviapollo]- for Apollo Domain. Available via anonymous ftp from
        {\tt june.cs.washington.edu} in {\tt ./tex/dvi\-apol\-lo.tar.Z}.
\item[      dviis] - For Integrated Systems. Available via anonymous ftp from
        {\tt june.cs.washington.edu} in {\tt ./tex/dvi\-is.tar.Z}.
\item[      dvidis] - For VAXstation VWS. Available via anonymous ftp from
        {\tt venus.ycc.yale.edu} (130.132.1.5) in {\tt [.dvidis]} (VMS machine).
      xdvi - Also for X Windows. Available via anonymous ftp from
        {\tt expo.lcs.mit.edu} in {\tt ./contrib/xdvi.shar.Z} and
        {\tt ./contrib/xdvi.patch7.Z}
\end{description}

\section{ Where can I get the manual for PiCTeX?}

   The PiCTeX manual is not free. It is available for \$35 from the
   \TeX{} Users Group:
\begin{center}
                     \TeX{} Users Group\\
                     P. O. Box 9506\\
                     Providence, RI 02940 (USA)\\
                     401-751-7760\\
                     {\tt tug AT math.ams.com}
\end{center}

   The proceeds from this sale go to Michael Wichura, the author of PiCTeX,
   and TUG.

\section{What is VorTeX and where can I get it?}

   VorTeX is a package of programs written at the University of California.
   It includes several nice previewers and some Emacs modes for \TeX{} and
   BibTeX. It is not free. Inquiries should be directed to
   {\tt vortex AT ucbarpa.berkely.edu} or
\begin{center}
        Professor Michael A. Harrison\\
        Att. Vortex Dist.\\
        Computer Science Division\\
        University of California\\
        Berkeley, CA 94720
\end{center}

\section{What is OzTeX and where can I get it?}

   OzTeX is a public domain version of \TeX{} for the Macintosh. It was
   written by Andrew Trevorrow, and is available via anonymous ftp from
   {\tt watmsg.waterloo.edu} (129.97.129.9) in {\tt ./pub/oztex}. The most recen
   version is 1.2. It is also available from {\tt tank.uchicago.edu}
   (128.135.136.2) in {\tt ./pub/sources/OzTeX}, which contains other public
   domain \TeX{}-related software for the Mac as well. Questions about OzTeX
   may be directed to {\tt oztex AT tank.uchicago.edu}.

\section{ What is Fig and where can I get it?}

   Fig is a menu driven tool similar to MacDraw that allows you to
   draw objects on the screen of a Sun Workstation running SunView.
   TransFig is a set of tools which translate the code fig produces
   to other graphics languages including PostScript and the \LaTeX{}
   picture environment. Both are available via anonymous ftp from
   {\tt svax.cs.cornell.edu} (128.84.254.2) in {\tt ./pub/fig}. Both Fig and
   TransFig are also available from the Clarkson archive server at
   sun.soe.clarkson.ede (see question 19). Both Fig and TransFig
   are supported by Micah Beck.

   XFig is essentially the same program except that it runs under
   X Windows. It is available via anonymous ftp from {\tt expo.lcs.mit.edu}
   (18.30.0.22) in {\tt ./contrib/xfig-2.0.*.Z}. Note that version 2.0 is
   the most recent. It was written by Brian Smith.

   For complete compatibility with TransFig, be sure to get at least
   patchlevel 4 of XFig 2.0.

\section{How do I get WEB for C or FORTRAN?}

   There is a version of WEB for C called CWEB written by Silvio Levy. It
   is available via anonymous ftp from {\tt princeton.edu} (128.112.128.1) in
   the directory {\tt ./pub/cweb}.

   There is a version of WEB called Spidery WEB which supports many languages
   including ADA, awk, and C. It was written by Norman Ramsey and, while
   not in the public domain, is usable free for research purposes. It is
   available via anonymous ftp from {\tt princeton.edu} in {\tt ./pub/spiderweb.

   There is a versions of WEB call FWEB for Fortran, Ratfor, and C written
   by John Krommes. It is available via anonymous ftp from {\tt ccc.nmfecc.gov}
   (128.55.128.30) in the directory {\tt TeX\$root:[distr.fweb]} (note that this
   is a VMS machine).

\section{ How can I typeset music in \TeX{}?}

   A package called MuTeX, written by Andrea Steinbach and Angelika Schofer,
   aids in doing this. It is available via anonymous ftp from
   sol.cs.ruu.nl (131.211.80.5) in pub/TEX/mtex.tar.Z

\section{ What is TUG and TUGboat?}

    TUG is the \TeX{} User's Group. TUGboat is their newsletter, which
    publishes useful articles about \TeX{} and METAFONT. Inquiries should
    be directed to:
\begin{center}
                  \TeX{} Users Group\\
                  P. O. Box 9506\\
                  Providence, RI 02940 (USA)\\
                  401-751-7760\\
                  {\tt tug AT math.ams.com}
\end{center}

\section{How do I convert Adobe's afm files to tfm format?}

    Use the afm2tfm program distributed with dvips, available via anonymous
    ftp from {\tt labrea.stanford.edu} (36.8.0.47) in {\tt ./pub}. If you are us
    pre-VF version of \TeX{}, get dvips4.21; if you are using a version of
    \TeX{} that understands virtual fonts, get dvips5.02 (or later).

\section{In \LaTeX{}, how do I get a double-spaced document?}

    One way is to change the value of \baselinestretch to 2 or 1.5 with
    the command \renewcommand{\baselinestretch}{2}. A better way is to
    the doublespace style file doublespace.sty in {\tt ./pub/LaTeX-style} from
    {\tt sun.soe.clarkson.edu} (see question 19).

\section{ In \LaTeX{}, how do I include a file in the verbatim environment?}

    A good way to do this is to use the alltt environment defined in
    the style file alltt.sty available in {\tt ./pub/LaTeX-style} from
    {\tt sun.soe.clarkson.edu} (see question 19).

 \section{ In \LaTeX{}, how do I do Y?}

    If you can't figure out how to do something in \LaTeX{} after you
    have read the manual very carefully, asked your local \LaTeX{}
    guru, and thought about it, there is a \LaTeX{} help service
    available (more information is periodically posted about this
    by Don Hosek). Please note that the way to accomplish something
    in \LaTeX{} is often by using an appropriate style file, so please
    check this also (see question 15). If none of this works, send mail
    describing your problem to {\tt LaTeX-help AT sumex-aim.stanford.edu}.

\section{ Where can I find a \LaTeX{} style file for doing Y?}

    Before you ask for a \LaTeX{} style file to do something, please check
    the \LaTeX{} style collection at {\tt sun.soe.clarkson.edu}, either through
    the archive server or via anonymous ftp (see question 19).

\section{How do I generate an index in \TeX{}/\LaTeX{}?}

    Making an index is not trivial. There are several indexing programs
    which aid in doing this. Some are:

      makeindex - for \LaTeX{} under Unix. Available via anonymous ftp
         from {\tt ymir.claremont.edu} (134.173.4.23, VMS) in the directory
         {\tt [.tex.utilities.makeindex]}

      idxtex - for \LaTeX{} under VMS. Available via anonymous ftp from
         {\tt ymir.claremont.edu} in the directory {\tt [.tex.uti\-li\-ties.idx\

      \TeX{}ix - for \TeX{} on CMS and MacIntosh machines. Available via
         anonymous ftp from {\tt ymir.claremont.edu} in the directory
         {\tt [.tex.utilities.texix]}.

\section{ How do I get METAFONT to do what I want it to do?}

    METAFONT allows you to create your own fonts, and ordinary \TeX{} users
    will never need to use it. METAFONT, unlike \TeX{}, requires some
    customization. Each output device for which you will be generating
    fonts needs a mode associated with it. Modes are defined using the
    mode\_def convention described on page 94 of \_The METAFONTbook\_. So
    first create a file, which we will call local.mf, containing all the
    mode\_defs you will be using. The file waits.mf (in the standard
    distribution or available via anonymous ftp from {\tt labrea.stanford.edu}
    (36.8.0.47) in {\tt ./lib}) is a good starting point for this. Listings of
    settings for various output devices are also published periodically in
    TUGboat (see question 10). Now create a plain base file using inimf,
    plain.mf, and local.mf:
\begin{verbatim}
       % inimf
       This is METAFONT....
       **plain                 # you type plain
       (output)
       *input local            # you type this
       (output)
       *dump                   # you type this
       Beginning to dump on file plain....
       (output)
       %
\end{verbatim}

    This should create a base file named plain.base (or something close)
    and should be moved to the directory which contains the base files on
    your system.

    Now we need to make sure that METAFONT loads this base when it starts
    up. If METAFONT loads the plain base by default on your system, then
    you're ready to go. Under Unix, we might, for instance define a
    command mf which executes ``virmf \&plain," loading the plain base
    file.

    The usual way to create a font with plain METAFONT is to then start it
    with the line
\begin{verbatim}
       \mode=<mode name>; mag=<magnification>; input <font file name>
\end{verbatim}

    in response to the * prompt or on the METAFONT command line. If
    $<$mode name$>$ is unknown or omitted, then the mode defaults to proof
    mode. If this has happened METAFONT will produce an output file
    called $<$font file name$>$.2602gf. The $<$magnification$>$ is a floating
    point number or magstep (magsteps are defined in \_The METAFONTbook\_
    and \_The \TeX{}book\_). If mag=$<$magnification$>$ is omitted, then the
    default is 1. For example, to generate cmr10 at 12pt for an epson
    printer you would type
\begin{verbatim}
       mf \mode=epson; mag=1.2; input cmr10
\end{verbatim}

    Note that under Unix the '\' and ';' characters must usually be escaped,
    so that this would typically look something like
\begin{verbatim}
       mf \\mode=epson\; mag=1.2\; input cmr10
\end{verbatim}

    If you don't have inimf or need a special mode that isn't in the
    base, you can put its commands in a file (e.g., ln03.mf) and invoke
    it on the fly with the \verb+\smode+ command. For example, to create
    ln03.300gf for an LN03 printer, using the file
\begin{verbatim}
        % This is ln03.mf as of 2/27/90
        % mode_def courtesy of John Sauter
        proofing:=0;
        fontmaking:=1;
        tracingtitles:=0;
        pixels_per_inch:=300;
        blacker:=0.65;
        fillin:=-0.1;
        o_correction:=.5;
\end{verbatim}
    (note the absence of the mode\_def and enddef commands), we would type
\begin{verbatim}
       mf \smode="ln03"; input cmr10
\end{verbatim}

\section{ Where do I get \TeX{}/\LaTeX{} for machine Y running Q?}

    Unix - The Unix \TeX{} distribution is available for anonymous
       ftp from {\tt labrea.stanford.edu} (36.8.0.47) in the directory
       {\tt ./tex/unix}. It is large, so please be sure to observe proper
       ftp etiquette when getting it. It is also available through
       the University of Washington. Contact:
\begin{center}
                  Director\\
                  Northwest Computer Support Group\\
                  University of Washington\\
                  Mail Stop DW-10\\
                  Seattle, WA 98195 (USA)\\
                  (206)543-6259
\end{center}

    PC - A \TeX{} package for the PC, including \LaTeX{}, BibTeX, previewers,
       and drivers is available via anonymous ftp from
       {\tt eedsp.gatech.edu} (128.61.2.1) in {\tt ./pub/TeX}. The variety here
       version 30 by Wayne Sullivan. EmTeX, another \TeX{} package for the PC
       by Eberhard Mattes, is available via anonymous ftp from
       {\tt terminator.cc.umich.edu} (35.1.33.8) in {\tt ./msdos/text-mgmt/TeX/e
       and from rusmv1.rus.uni-stuttgart.de (129.69.1.12) (user:ftp,
       password: guest) in {\tt ./soft/tex/emtex}. This package includes \LaTeX{
       METAFONT, BibTex, etc., as well. All the documentation for emtex
       is in German. \TeX{} for the PC is also available through
\begin{center}
                  Jon Radel\\
                  P. O. Box 2276\\
                  Reston, VA 22090
\end{center}
       Send a self-addressed stamped envelope to obtain information
       on what's available.

    Mac - see question 6 for a public domain version.

    TOPS-20 - \TeX{} was originally written on a DEC-10 under WAITS, and so
        was easily ported to TOPS-20. A Distribution that runs on TOPS-20
        is available via anonymous ftp from {\tt science.utah.edu} (128.110.192.
        in aps:$<$tex$>$ (this is a TOPS-20 machine).

    VAX/VMS - VMS executables are available via anonymous ftp from
        {\tt ymir.claremont.edu} (134.173.4.23) in {\tt [.tex.exe]}. Source is
        available in {\tt [.tex.sources]}. Version 3.0 is available in
        {\tt [.tex.sources.tex3\_0]}. Ymir has a mailserver for those without
        ftp access. Send a message containing the line ``help" to
        {\tt mailserv AT ymir.claremont.edu}.

    Atari - \TeX{} is available for the Atari ST from {\tt dsrgsun.ces.cwru.edu}
        (129.22.16.2) in {\tt ./pub/atari/StTeX}.

    Amiga - Disk 1 of the Amiga CommonTeX distribution is available
         via anonymous ftp from {\tt xanth.cs.odu.edu} (128.82.8.1)
         in {\tt ./pub/commontex.zoo}. This file is in zoo format so you may
         need to get zoo to uncompress it: The Unix zoo distribution is
         in {\tt ./pub/zoo-2.01}; the Amiga version is available as
         {\tt ./amiga/zoo-2.00.arc}. The file copying.tex in the distribution
         contains information on how to obtain the other disks.

\section{What is the Clarkson archive server?}

    The Clarkson archive server is a program that allows you to
    retrieve files via electronic mail. So it provides a way of
    getting many neat things if you don't have anonymous ftp. To
    get the archive server to do something you should send a message
    to {\tt archive-server AT sun.soe.clarkson.edu} (128.153.12.3). To get
    started using it, send the archive server a one line message
    ``help" (case is unimportant). It will send you back a file
    describing how to use it more fully.

    In particular, the Clarkson archive contains, among other things,
    a repository for \LaTeX{} style files, AMSTeX macros and style
    files, BiBTeX style files, PiCTeX source (not the manual, see
    question 4), back issues of \TeX{}hax and \TeX{}MaG, files from
    TUGboat, and source to \TeX{}, \LaTeX{}, WEB, and various utilities.
    The archive is maintained by Michael DeCorte.

    If anonymous ftp is available to you, you may get the files directly
    from {\tt sun.soe.clarkson.edu}.

    If you have problems, contact {\tt archive-management AT sun.soe.clarkson.edu}.

\section{ Where can I get a thesis style for \LaTeX{}?}

    Thesis styles are usually very specific to your University, so it's
    usually not profitable to ask the whole newsgroup for one. If you
    want to write your own, a good place to start is the ucthesis style
    available in the \LaTeX{} style collection at {\tt sun.soe.clarkson.edu}
    (see question 19).

\section{How do I get symbols for ``the real numbers", ``the complex numbers",
    and so on?}

    These symbols are known as ``blackboard bold" and are available in
    the font ``msym" (e.g., ``msym10" for 10pt). There is a companion font
    ``msxm" as well. The fonts have a large number of mathematical symbols
    to supplement the ones provided by \TeX{}. A complete list of the symbols
    can be found in the November 1985 issue of TUGboat (see question 10).
    The fonts are available from the American Mathematical Society; also
    TFM and PK files for the standard scalings are available from the Clarkson
    archive server at sun.soe.clarkson in {\tt ./pub/tfm} and {\tt ./pub/canon30
    question 19). GF, PXL, and MF files are available via anonymous ftp from
    {\tt labrea.stanford.edu} (36.8.0.47) in the directory {\tt ./tex/amsfonts}.
    Unfortunately, the .mf files were all written in the old METAFONT79
    language, and so will not run under the new METAFONT. The file
    mssymb.tex in the same directory loads the fonts for \TeX{} users
    (Blackboard bold is the font \verb+\Bbb+). \LaTeX{} users can access them us
    the amssymbols.sty style file available from the archive server.

\section{How do I get \TeX{} material if I do not have access to anonymous ftp?}

    There are several mail servers available, i.e., programs that will
    send you files via electronic mail. Some are:

      - The mail server at Clarkson (see question 19), if you can send
        mail to the United States.

      - Also in the US, the mail server at {\tt ymir.claremont.edu} has access
        to all the \TeX{}-related material there. Send a message containing
        the line ``help" to {\tt MAILSERV AT ymir.claremont.edu}.

      - In the United Kingdom, you can get \TeX{}-related material from the
        UK \TeX{} archive at the University of Aston. (FTP access is also
        available:
\begin{verbatim}
           Site       uk.ac.aston.tex
           Username   public
           Password   public
           Top Level  \TeX{}-archive
\end{verbatim}

        A known file is {\tt [tex-archive]000directory.list}.) For electronic
        mail access, send a message to {\tt TeXserver AT uk.ac.as\-ton.tex}. The
        message must contain the following three lines starting in column 1
        (and omitting the ===$>$ part):
\begin{verbatim}
        ===>    ---
        ===>    (your address from Aston - see below)
        ===>    help
\end{verbatim}
        The server ignores anything preceding the line which commences with
        the three hyphens, such as mail headers. It also ignores the remainder
        of the line with the hyphens on it. For Internet users the return
        address is of the form {\tt name\%site@nsfnet-relay}, while for Bitnet a
        EARN it is {\tt name\%site@earn-relay}.

      - There are LISTSERV facilities for \TeX{} on {\tt LISTSERV AT TAMVM1.BITNET}
        {\tt LISTSERV AT DHDURZ1.BITNET}. Send a message containing the line ``help
        one of these addresses.

    There is also the DECUS \TeX{} collection, a collection of \TeX{} material f
    VMS, Unix, MS-DOS, and the Macintosh. It can be obtained from the DECUS
    Library (reference number VS0058) in the US, or through your DECUS office
    outside of the US. To contact the DECUS Library, send mail or call:
\begin{center}
                 The DECUS Program Library\\
                 219 Boston Post Road BP02\\
                 Marlboro, MA 01752-1850\\
                 (508)480-3418
\end{center}
    or send electronic mail to the DECUS \TeX{} Collection Editor, Ted Nieland,
    at {\tt decus\_tex AT nieland.dayton.oh.us}.



\end{document}



Date:Thu, 21 Jun 90 11:51:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:   Mijn kopie van Frequently Asked Questions was gemold. Verbeterd.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

\documentstyle[dina4]{article}
\parindent0pt
\parskip1mm
\begin{document}
\title{Frequently Asked Questions about \TeX{}, etc., with Answers}
\author{Bobby Bodenheimer}
\date{}

\maketitle

\begin{verbatim}
|=============================================================================|
|  Bobby Bodenheimer                             @hot.caltech.edu             |
|  // BITNET: bobby AT caltech.bitnet               |                            |
|  // ARPA  : bobby AT csvax.caltech.edu            | Woof!                      |
|  // UUCP  : {amdahl,ames!elroy}!cit-vax!bobby  |                            |
|=============================================================================|
\end{verbatim}

This article contains answers to some frequently asked questions on {\tt
comp.text.tex}. Please don't ask these questions again, as they've been
answered many times before.

This article includes answers to:
\begin{enumerate}
\item Where can I get a DVI to PostScript conversion program?
\item How can I include a PostScript figure in \LaTeX{}?
\item Where can I find a DVI previewer for machine Y running Q?
\item Where can I get the manual for PiCTeX?
\item What is VorTeX and where can I get it?
\item What is OzTeX and where can I get it?
\item What is Fig and where can I get it?
\item How do I get WEB for C or FORTRAN?
\item How can I typeset music in \TeX{}?
\item What is TUG and TUGboat?
\item How do I convert Adobe's afm files to tfm format?
\item In \LaTeX{}, how do I get a double-spaced document?
\item In \LaTeX{}, how do I include a file in the verbatim environment?
\item In \LaTeX{}, how do I do Y?
\item Where can I find a \LaTeX{} style file for doing Y?
\item How do I generate an index in \TeX{}/\LaTeX{}?
\item Where  do I get METAFONT to do what I want it to do?
\item Where do I get \TeX{}/\LaTeX{} for machine Y running Q?
\item What is the Clarkson archive server?
\item Where can I get a thesis style for \LaTeX{}?
\item How do I get symbols for ``the real numbers", ``the complex numbers",
      and so on?
\item How do I get \TeX{} material if I do not have access to anonymous
      ftp?
 \end{enumerate}

These are all legitimate questions, but they seem to appear too frequently for
long-time readers of the list.

Many of the answers below tell you that you can obtain something through
anonymous ftp. Remember that anonymous ftp is a privilege and that the system
administrators for these sites have made these files available out of their
own generosity. Therefore please restrict your ftp'ing to non-prime hours at
the various sites.

I would like to acknowledge Don Hosek, Ken Yap, Tomas Rokicki, and Micah Beck,
whose postings provided many of the answers. Joe Weening, Hal Perkins, Walter
Carlip, Max Hailpern, Tad Guy, Raymond Chen, Henning Schulzrinne, and
Sebastian Rahtz provided additional material and criticisms.  The format of
this document is based on that of the Frequently Asked Questions appearing in
{\tt comp.unix.wizards}, and written by Steve Hayman.  Any mistakes are mine.
Corrections, suggestions, and additions to {\tt bobby AT hot.caltech.edu}.

This is version 1.5, last changed 6/7/90.

\section{ Where can I get a DVI to PostScript conversion program?}

   Three very nice DVI to PostScript conversion programs that run
   under Unix are:
\begin{description}
\item[     dvitps] - part of the \TeX{}PS package by Stephan Bectolsheim.
       Available via anonymous ftp from {\tt arthur.cs.pur\-due.edu}
       (128.10.2.1) in {\tt ./pub/TeXPS}.
\item[     dvi3ps] - by Kevin Coombes. Available via anonymous ftp
       from {\tt tut.cis.ohio-state.edu} (128.146.8.60) in
       {\tt ./pub/dvi3ps.tar.Z }
\item[     dvips] - by Tomas Rokicki. This driver (in version 5.0 and later)
       has the ability to deal with the virtual fonts of \TeX{} 3.0.
       Version 4.21 is for versions of \TeX{} before 3.0 (or 2.995).
       Available via anonymous ftp from {\tt labrea.stanford.edu}
       (36.8.0.47) in {\tt ./pub}.
\end{description}

\section{How can I include a PostScript figure in \LaTeX{}?}

   Perhaps the best way to do this is to use the psfig macros written by
   Trevor Darrell. They are available via anonymous ftp from {\tt
   whitechapel.media.mit.edu} (18.85.0.124) in {\tt ./psfig} or {\tt
   linc.cis.upenn.edu} (130.91.6.8) in the directory {\tt ./dist/psfig}.  You
   will also need a dvi to PostScript conversion program that supports the
   macros. The ones mentioned in question 1 do. The psfig macros work best
   with Encapsulated PostScript Files (EPS). In particular, psfig will need
   the file to have a BoundingBox (see Appendix C of the \_PostScript Language
   Reference Manual\_). If you don't have an EPS file, life can be difficult.


\section{ Where can I find a DVI previewer for machine Y running Q?}

   This briefly lists some previewers which are available via anonymous ftp:

\begin{description}
\item[ dvipage] - For SunView. Available via anonymous ftp from {\tt
        june.cs.washington.edu} (128.95.1.4) in {\tt ./tex/dvi\-pages.tar.Z}
\item[ xtex] - For X Windows. Available via anonymous ftp from {\tt
        expo.lcs.mit.edu} (18.30.0.212) in {\tt ./contrib/See\-TeX-2.15.tar}
\item[ dviapollo]- for Apollo Domain. Available via anonymous ftp from {\tt
        june.cs.washington.edu} in {\tt ./tex/dvi\-apol\-lo.tar.Z}.
\item[ dviis] - For Integrated Systems. Available via anonymous ftp from {\tt
        june.cs.washington.edu} in {\tt ./tex/dvi\-is.tar.Z}.
\item[ dvidis] - For VAXstation VWS. Available via anonymous ftp from {\tt
        venus.ycc.yale.edu} (130.132.1.5) in {\tt [.dvidis]} (VMS machine).
\item[ xdvi] - Also for X Windows. Available via anonymous ftp from {\tt
        expo.lcs.mit.edu} in {\tt ./contrib/xdvi.shar.Z} and {\tt
        ./contrib/xdvi.patch7.Z} \end{description}

\section{ Where can I get the manual for PiCTeX?}

   The PiCTeX manual is not free. It is available for \$35 from the \TeX{}
   Users Group:
\begin{center}
                     \TeX{} Users Group\\
                     P. O. Box 9506\\
                     Providence, RI 02940 (USA)\\
                     401-751-7760\\
                     {\tt tug AT math.ams.com}
\end{center}

   The proceeds from this sale go to Michael Wichura, the author of PiCTeX,
   and TUG.

\section{What is VorTeX and where can I get it?}

   VorTeX is a package of programs written at the University of California.
   It includes several nice previewers and some Emacs modes for \TeX{} and
   BibTeX. It is not free. Inquiries should be directed to {\tt
   vortex AT ucbarpa.berkely.edu} or

\begin{center}
        Professor Michael A. Harrison\\
        Att. Vortex Dist.\\
        Computer Science Division\\
        University of California\\
        Berkeley, CA 94720
\end{center}

\section{What is OzTeX and where can I get it?}

   OzTeX is a public domain version of \TeX{} for the Macintosh. It was
   written by Andrew Trevorrow, and is available via anonymous ftp from {\tt
   watmsg.waterloo.edu} (129.97.129.9) in {\tt ./pub/oztex}. The most recent
   version is 1.2. It is also available from {\tt tank.uchicago.edu}
   (128.135.136.2) in {\tt ./pub/sources/OzTeX}, which contains other public
   domain \TeX{}-related software for the Mac as well. Questions about OzTeX
   may be directed to {\tt oztex AT tank.uchicago.edu}.

\section{ What is Fig and where can I get it?}

   Fig is a menu driven tool similar to MacDraw that allows you to draw
   objects on the screen of a Sun Workstation running SunView.  TransFig is a
   set of tools which translate the code fig produces to other graphics
   languages including PostScript and the \LaTeX{} picture environment. Both
   are available via anonymous ftp from {\tt svax.cs.cornell.edu}
   (128.84.254.2) in {\tt ./pub/fig}. Both Fig and TransFig are also available
   from the Clarkson archive server at sun.soe.clarkson.ede (see question 19).
   Both Fig and TransFig are supported by Micah Beck.

   XFig is essentially the same program except that it runs under X Windows.
   It is available via anonymous ftp from {\tt expo.lcs.mit.edu} (18.30.0.22)
   in {\tt ./contrib/xfig-2.0.*.Z}. Note that version 2.0 is the most recent.
   It was written by Brian Smith.

   For complete compatibility with TransFig, be sure to get at least
   patchlevel 4 of XFig 2.0.

\section{How do I get WEB for C or FORTRAN?}

   There is a version of WEB for C called CWEB written by Silvio Levy. It is
   available via anonymous ftp from {\tt princeton.edu} (128.112.128.1) in the
   directory {\tt ./pub/cweb}.

   There is a version of WEB called Spidery WEB which supports many languages
   including ADA, awk, and C. It was written by Norman Ramsey and, while not
   in the public domain, is usable free for research purposes. It is available
   via anonymous ftp from {\tt princeton.edu} in {\tt ./pub/spiderweb.}

   There is a versions of WEB call FWEB for Fortran, Ratfor, and C written by
   John Krommes. It is available via anonymous ftp from {\tt ccc.nmfecc.gov}
   (128.55.128.30) in the directory {\tt TeX\$root:[distr.fweb]} (note that
   this is a VMS machine).

\section{ How can I typeset music in \TeX{}?}

   A package called MuTeX, written by Andrea Steinbach and Angelika Schofer,
   aids in doing this. It is available via anonymous ftp from sol.cs.ruu.nl
   (131.211.80.5) in pub/TEX/mtex.tar.Z

\section{ What is TUG and TUGboat?}

    TUG is the \TeX{} User's Group. TUGboat is their newsletter, which
    publishes useful articles about \TeX{} and METAFONT. Inquiries should be
    directed to:
\begin{center}
                  \TeX{} Users Group\\
                  P. O. Box 9506\\
                  Providence, RI 02940 (USA)\\
                  401-751-7760\\
                  {\tt tug AT math.ams.com}
\end{center}

\section{How do I convert Adobe's afm files to tfm format?}

    Use the afm2tfm program distributed with dvips, available via anonymous
    ftp from {\tt labrea.stanford.edu} (36.8.0.47) in {\tt ./pub}. If you are
    using pre-VF version of \TeX{}, get dvips4.21; if you are using a version
    of \TeX{} that understands virtual fonts, get dvips5.02 (or later).

\section{In \LaTeX{}, how do I get a double-spaced document?}

    One way is to change the value of \baselinestretch to 2 or 1.5 with the
    command \renewcommand{\baselinestretch}{2}. A better way is to the
    doublespace style file doublespace.sty in {\tt ./pub/LaTeX-style} from
    {\tt sun.soe.clarkson.edu} (see question 19).

\section{ In \LaTeX{}, how do I include a file in the verbatim environment?}

    A good way to do this is to use the alltt environment defined in the style
    file alltt.sty available in {\tt ./pub/LaTeX-style} from {\tt
    sun.soe.clarkson.edu} (see question 19).

 \section{ In \LaTeX{}, how do I do Y?}

    If you can't figure out how to do something in \LaTeX{} after you have
    read the manual very carefully, asked your local \LaTeX{} guru, and
    thought about it, there is a \LaTeX{} help service available (more
    information is periodically posted about this by Don Hosek). Please note
    that the way to accomplish something in \LaTeX{} is often by using an
    appropriate style file, so please check this also (see question 15). If
    none of this works, send mail describing your problem to {\tt
    LaTeX-help AT sumex-aim.stanford.edu}.

\section{ Where can I find a \LaTeX{} style file for doing Y?}

    Before you ask for a \LaTeX{} style file to do something, please check the
    \LaTeX{} style collection at {\tt sun.soe.clarkson.edu}, either through
    the archive server or via anonymous ftp (see question 19).

\section{How do I generate an index in \TeX{}/\LaTeX{}?}

    Making an index is not trivial. There are several indexing programs which
    aid in doing this. Some are:

      makeindex - for \LaTeX{} under Unix. Available via anonymous ftp from
         {\tt ymir.claremont.edu} (134.173.4.23, VMS) in the directory {\tt
         [.tex.utilities.makeindex]}

      idxtex - for \LaTeX{} under VMS. Available via anonymous ftp from {\tt
         ymir.claremont.edu} in the directory {\tt [.tex.uti\-li\-ties.idx]}

      \TeX{}ix - for \TeX{} on CMS and MacIntosh machines. Available via
         anonymous ftp from {\tt ymir.claremont.edu} in the directory {\tt
         [.tex.utilities.texix]}.

\section{ How do I get METAFONT to do what I want it to do?}

    METAFONT allows you to create your own fonts, and ordinary \TeX{} users
    will never need to use it. METAFONT, unlike \TeX{}, requires some
    customization. Each output device for which you will be generating fonts
    needs a mode associated with it. Modes are defined using the mode\_def
    convention described on page 94 of \_The METAFONTbook\_. So first create a
    file, which we will call local.mf, containing all the mode\_defs you will
    be using. The file waits.mf (in the standard distribution or available via
    anonymous ftp from {\tt labrea.stanford.edu} (36.8.0.47) in {\tt ./lib})
    is a good starting point for this. Listings of settings for various output
    devices are also published periodically in TUGboat (see question 10). Now
    create a plain base file using inimf, plain.mf, and local.mf:
\begin{verbatim}
       % inimf
       This is METAFONT....
       **plain                 # you type plain
       (output)
       *input local            # you type this
       (output)
       *dump                   # you type this
       Beginning to dump on file plain....
       (output)
       %
\end{verbatim}

    This should create a base file named plain.base (or something close) and
    should be moved to the directory which contains the base files on your
    system.

    Now we need to make sure that METAFONT loads this base when it starts up.
    If METAFONT loads the plain base by default on your system, then you're
    ready to go. Under Unix, we might, for instance define a command mf which
    executes ``virmf \&plain," loading the plain base file.

    The usual way to create a font with plain METAFONT is to then start it
    with the line
\begin{verbatim}
       \mode=<mode name>; mag=<magnification>; input <font file name>
\end{verbatim}

    in response to the * prompt or on the METAFONT command line. If $<$mode
    name$>$ is unknown or omitted, then the mode defaults to proof mode. If
    this has happened METAFONT will produce an output file called $<$font file
    name$>$.2602gf. The $<$magnification$>$ is a floating point number or
    magstep (magsteps are defined in \_The METAFONTbook\_ and \_The
    \TeX{}book\_). If mag=$<$magnification$>$ is omitted, then the default is
    1. For example, to generate cmr10 at 12pt for an epson printer you would
    type
\begin{verbatim}
       mf \mode=epson; mag=1.2; input cmr10
\end{verbatim}

    Note that under Unix the '\' and ';' characters must usually be escaped,
    so that this would typically look something like
\begin{verbatim}
       mf \\mode=epson\; mag=1.2\; input cmr10
\end{verbatim}

    If you don't have inimf or need a special mode that isn't in the base, you
    can put its commands in a file (e.g., ln03.mf) and invoke it on the fly
    with the \verb+\smode+ command. For example, to create ln03.300gf for an
    LN03 printer, using the file
\begin{verbatim}
        % This is ln03.mf as of 2/27/90
        % mode_def courtesy of John Sauter
        proofing:=0;
        fontmaking:=1;
        tracingtitles:=0;
        pixels_per_inch:=300;
        blacker:=0.65;
        fillin:=-0.1;
        o_correction:=.5;
\end{verbatim}
    (note the absence of the mode\_def and enddef commands), we would type
\begin{verbatim}
       mf \smode="ln03"; input cmr10
\end{verbatim}

\section{ Where do I get \TeX{}/\LaTeX{} for machine Y running Q?}

    Unix - The Unix \TeX{} distribution is available for anonymous ftp from
       {\tt labrea.stanford.edu} (36.8.0.47) in the directory {\tt
       ./tex/unix}. It is large, so please be sure to observe proper ftp
       etiquette when getting it. It is also available through the University
       of Washington. Contact:
\begin{center}
                  Director\\
                  Northwest Computer Support Group\\
                  University of Washington\\
                  Mail Stop DW-10\\
                  Seattle, WA 98195 (USA)\\
                  (206)543-6259
\end{center}

    PC - A \TeX{} package for the PC, including \LaTeX{}, BibTeX, previewers,
       and drivers is available via anonymous ftp from {\tt eedsp.gatech.edu}
       (128.61.2.1) in {\tt ./pub/TeX}. The variety here version 30 by Wayne
       Sullivan. EmTeX, another \TeX{} package for the PC by Eberhard Mattes,
       is available via anonymous ftp from {\tt terminator.cc.umich.edu}
       (35.1.33.8) in {\tt ./msdos/text-mgmt/TeX/emtex} and from
       rusmv1.rus.uni-stuttgart.de (129.69.1.12) (user:ftp, password: guest)
       in {\tt ./soft/tex/emtex}. This package includes
\LaTeX{}
       METAFONT, BibTex, etc., as well. All the documentation for emtex is in
       German. \TeX{} for the PC is also available through
\begin{center}
                  Jon Radel\\
                  P. O. Box 2276\\
                  Reston, VA 22090
\end{center} Send a self-addressed stamped envelope to obtain information on
       what's available.

    Mac - see question 6 for a public domain version.

    TOPS-20 - \TeX{} was originally written on a DEC-10 under WAITS, and so
        was easily ported to TOPS-20. A Distribution that runs on TOPS-20 is
        available via anonymous ftp from {\tt science.utah.edu}
        (128.110.192.2) in aps:$<$tex$>$ (this is a TOPS-20 machine).

    VAX/VMS - VMS executables are available via anonymous ftp from {\tt
        ymir.claremont.edu} (134.173.4.23) in {\tt [.tex.exe]}. Source is
        available in {\tt [.tex.sources]}. Version 3.0 is available in {\tt
        [.tex.sources.tex3\_0]}. Ymir has a mailserver for those without ftp
        access. Send a message containing the line ``help" to {\tt
        mailserv AT ymir.claremont.edu}.

    Atari - \TeX{} is available for the Atari ST from {\tt
        dsrgsun.ces.cwru.edu} (129.22.16.2) in {\tt ./pub/atari/StTeX}.

    Amiga - Disk 1 of the Amiga CommonTeX distribution is available via
         anonymous ftp from {\tt xanth.cs.odu.edu} (128.82.8.1) in {\tt
         ./pub/commontex.zoo}. This file is in zoo format so you may need to
         get zoo to uncompress it: The Unix zoo distribution is in {\tt
         ./pub/zoo-2.01}; the Amiga version is available as {\tt
         ./amiga/zoo-2.00.arc}. The file copying.tex in the distribution
         contains information on how to obtain the other disks.

\section{What is the Clarkson archive server?}

    The Clarkson archive server is a program that allows you to retrieve files
    via electronic mail. So it provides a way of getting many neat things if
    you don't have anonymous ftp. To get the archive server to do something
    you should send a message to {\tt archive-server AT sun.soe.clarkson.edu}
    (128.153.12.3). To get started using it, send the archive server a one
    line message ``help" (case is unimportant). It will send you back a file
    describing how to use it more fully.

    In particular, the Clarkson archive contains, among other things, a
    repository for \LaTeX{} style files, AMSTeX macros and style files, BiBTeX
    style files, PiCTeX source (not the manual, see question 4), back issues
    of \TeX{}hax and \TeX{}MaG, files from TUGboat, and source to \TeX{},
    \LaTeX{}, WEB, and various utilities.  The archive is maintained by
    Michael DeCorte.

    If anonymous ftp is available to you, you may get the files directly from
    {\tt sun.soe.clarkson.edu}.

    If you have problems, contact {\tt
    archive-management AT sun.soe.clarkson.edu}.

\section{ Where can I get a thesis style for \LaTeX{}?}

    Thesis styles are usually very specific to your University, so it's
    usually not profitable to ask the whole newsgroup for one. If you want to
    write your own, a good place to start is the ucthesis style available in
    the \LaTeX{} style collection at {\tt sun.soe.clarkson.edu} (see question
    19).

\section{How do I get symbols for ``the real numbers", ``the complex numbers",
    and so on?}

    These symbols are known as ``blackboard bold" and are available in the
    font ``msym" (e.g., ``msym10" for 10pt). There is a companion font ``msxm"
    as well. The fonts have a large number of mathematical symbols to
    supplement the ones provided by \TeX{}. A complete list of the symbols can
    be found in the November 1985 issue of TUGboat (see question 10).  The
    fonts are available from the American Mathematical Society; also TFM and
    PK files for the standard scalings are available from the Clarkson archive
    server at sun.soe.clarkson in {\tt ./pub/tfm} and {\tt ./pub/canon300}
    question 19). GF, PXL, and MF files are available via anonymous ftp from
    {\tt labrea.stanford.edu} (36.8.0.47) in the directory {\tt
    ./tex/amsfonts}.  Unfortunately, the .mf files were all written in the old
    METAFONT79 language, and so will not run under the new METAFONT. The file
    mssymb.tex in the same directory loads the fonts for \TeX{} users
    (Blackboard bold is the font \verb+\Bbb+). \LaTeX{} users can access them
    using the amssymbols.sty style file available from the archive server.

\section{How do I get \TeX{} material if I do not have access to anonymous
ftp?}

    There are several mail servers available, i.e., programs that will send
    you files via electronic mail. Some are:

      - The mail server at Clarkson (see question 19), if you can send mail to
        the United States.

      - Also in the US, the mail server at {\tt ymir.claremont.edu} has access
        to all the \TeX{}-related material there. Send a message containing
        the line ``help" to {\tt MAILSERV AT ymir.claremont.edu}.

      - In the United Kingdom, you can get \TeX{}-related material from the UK
        \TeX{} archive at the University of Aston. (FTP access is also
        available:
\begin{verbatim}
           Site       uk.ac.aston.tex
           Username   public
           Password   public
           Top Level  \TeX{}-archive
\end{verbatim}

        A known file is {\tt [tex-archive]000directory.list}.) For electronic
        mail access, send a message to {\tt TeXserver AT uk.ac.as\-ton.tex}. The
        message must contain the following three lines starting in column 1
        (and omitting the ===$>$ part):
\begin{verbatim}
        ===>    ---
        ===>    (your address from Aston - see below)
        ===>    help
\end{verbatim}
        The server ignores anything preceding the line which commences with
        the three hyphens, such as mail headers. It also ignores the remainder
        of the line with the hyphens on it. For Internet users the return
        address is of the form {\tt name\%site@nsfnet-relay}, while for Bitnet
and
        EARN it is {\tt name\%site@earn-relay}.

      - There are LISTSERV facilities for \TeX{} on {\tt
        LISTSERV AT TAMVM1.BITNET} and {\tt LISTSERV AT DHDURZ1.BITNET}. Send a
        message containing the line ``help'' to one of these addresses.

    There is also the DECUS \TeX{} collection, a collection of \TeX{} material
    for VMS, Unix, MS-DOS, and the Macintosh. It can be obtained from the
    DECUS Library (reference number VS0058) in the US, or through your DECUS
    office outside of the US. To contact the DECUS Library, send mail or call:
\begin{center}
                 The DECUS Program Library\\
                 219 Boston Post Road BP02\\
                 Marlboro, MA 01752-1850\\
                 (508)480-3418
\end{center} or send electronic mail to the DECUS \TeX{} Collection Editor,
    Ted Nieland, at {\tt decus\_tex AT nieland.dayton.oh.us}.



\end{document}




Date:Thu, 21 Jun 90 12:21:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:   Sorry, nog wat fouten. Hier is een diff
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

71c71
< \section{Where can I get a DVI to PostScript conversion program?}
---
> \section{ Where can I get a DVI to PostScript conversion program?}
102c102
< \section{Where can I find a DVI previewer for machine Y running Q?}
---
> \section{ Where can I find a DVI previewer for machine Y running Q?}
121c121
< \section{Where can I get the manual for PiCTeX?}
---
> \section{ Where can I get the manual for PiCTeX?}
160c160
< \section{What is Fig and where can I get it?}
---
> \section{ What is Fig and where can I get it?}
195c195
< \section{How can I typeset music in \TeX{}?}
---
> \section{ How can I typeset music in \TeX{}?}
201c201
< \section{What is TUG and TUGboat?}
---
> \section{ What is TUG and TUGboat?}
223,225c223,225
<     One way is to change the value of \verb+\baselinestretch+ to 2 or 1.5 with
<     the command \verb+\renewcommand{\baselinestretch}{2}+. A better way is to
<     the doublespace style file doublespace.sty in {\tt ./pub/LaTeX-style} from
---
>     One way is to change the value of \baselinestretch to 2 or 1.5 with the
>     command \renewcommand{\baselinestretch}{2}. A better way is to the
>     doublespace style file doublespace.sty in {\tt ./pub/LaTeX-style} from
228c228
< \section{In \LaTeX{}, how do I include a file in the verbatim environment?}
---
> \section{ In \LaTeX{}, how do I include a file in the verbatim environment?}
234c234
<  \section{In \LaTeX{}, how do I do Y?}
---
>  \section{ In \LaTeX{}, how do I do Y?}
245c245
< \section{Where can I find a \LaTeX{} style file for doing Y?}
---
> \section{ Where can I find a \LaTeX{} style file for doing Y?}
267c267
< \section{How do I get METAFONT to do what I want it to do?}
---
> \section{ How do I get METAFONT to do what I want it to do?}
320,321c320,321
<     Note that under Unix the `\verb+\+' and '\verb+;+' characters must usually
<     be escaped, so that this would typically look something like
---
>     Note that under Unix the '\' and ';' characters must usually be escaped,
>     so that this would typically look something like
346c346
< \section{Where do I get \TeX{}/\LaTeX{} for machine Y running Q?}
---
> \section{ Where do I get \TeX{}/\LaTeX{} for machine Y running Q?}
428c428
< \section{Where can I get a thesis style for \LaTeX{}?}
---
> \section{ Where can I get a thesis style for \LaTeX{}?}
437c437
< and so on?}
---
>     and so on?}




Date:Sat, 23 Jun 90 14:15:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:   Sorry. Compress 16bits.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Twee weken geleden heb ik beloofd een 16bits versie van
compress voor de ST te maken. M'n harddisk is echter (tijdelijk)
weg en ik ben (blijkbaar) te verwend (geraakt) om nog
goed zonder te kunnen werken.
Ik kan mijn belofte dus niet nu waar maken.
Sorry,
Erik-Jan.




Date:Mon, 25 Jun 90 11:48:00 N
From:    POPPELIER AT HUTRUU53.BITNET
Subject:   VMS ZOO
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Ik heb behoefte aan ZOO voor VMS. Wat ik wil hebben is

(i) zoo.c -- dan maak ik de rest zelf wel
(ii) zoo.obj -- dan hoef ik alleen maar te linken

Johannes Braams stuurde mij eerder zoo.exe, maar die was gelinkt met
een andere versie van VMS.

*FLAME ON*
Waarom heeft DEC in hemelsnaam zoveel versies van VMS?
Waarom hebben niet alle VMS-sites in Nederland, gegeven het bovenstaande,
allemaal hetzelfde nummer?
*FLAME OFF*

Nico




Date:Tue, 26 Jun 90 16:58:00 N
From:    "Chris Evelo: MFAGKCHR@HMARL5 (BITNET)" <MFAGKCHR AT HMARL5.BITNET>
Subject:   Whitespace before section heading
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


Hoe verklein ik alweer de hoeveelheid whitespace voor een sectionheading.

(Waarom? eigenlijk heb ik helemaal geen sections, maar wel een literatuur
lijst, waarvan de heading als section heading behandeld wordt. Ik wil die
lijst wat dichter op de tekst van een abstract).

                        Chris Evelo (MFAGKCHR@HMARL5 BITNET)





Date:Wed, 27 Jun 90 11:22:50 MET
From:    "P. Wackers" <U216002 AT HNYKUN11.BITNET>
Subject:   BibTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,
Ik wil BibTeX gaan gebruiken. In mijn vak is de standaardwijze van
verwijzen het aangeven van auteursnaam en jaartal. Ik heb de
file named.bst gevonden en die doet ongeveer wat ik wil. Er zijn
echter twee problemen:
1. Bij gebruik daarvan worden auteursnaam en jaartal aan elkaar afgedrukt.
Ik wil daar een spatie tussen hebben.
2. Bij een tijdschrift, wordt gegeven: Naam tijdschrift, deelnr.:pag.nrs.,
jaar. [bijv. Literatuur, 2:96--112, 1986.]
Ik wil hebben: Naam, deelnr. (jaar), pag.nrs. dus: [Literatuur, 2 (1986),
96--112.]
Kan iemand mij zeggen wat (en waar) ik moet veranderen om dat gedaan te
krijgen? Bedankt vast.
Paul Wackers   (Vakgroep Nederlands KUN   u216002@hnykun11)




Date:Wed, 27 Jun 90 12:24:50 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   BibTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Op 27 Jun 90 schreef Paul Wackers:

 > Hallo,
 > Ik wil BibTeX gaan gebruiken. In mijn vak is de standaardwijze van
 > verwijzen het aangeven van auteursnaam en jaartal. Ik heb de
 > file named.bst gevonden en die doet ongeveer wat ik wil. Er zijn
 > echter twee problemen:
 > 1. Bij gebruik daarvan worden auteursnaam en jaartal aan elkaar afgedrukt.

Vreemd, de named.bst die ik heb (met bijbehorende named.sty) geeft een
komma ertussen.

 > Ik wil daar een spatie tussen hebben.

Om de komma te vervangen door een spatie moet ja dan de volgende regels
vervangen:

24c24
<  \def\citeauthoryear##1##2{##1, ##2}\@internalcite}
---
>  \def\citeauthoryear##1##2{##1 ##2}\@internalcite}
52c52
< \def\@biblabel#1{\def\citeauthoryear##1##2{##1, ##2}%
---
> \def\@biblabel#1{\def\citeauthoryear##1##2{##1 ##2}%

 > 2. Bij een tijdschrift, wordt gegeven: Naam tijdschrift, deelnr.:pag.nrs.,
 > jaar. [bijv. Literatuur, 2:96--112, 1986.]
 > Ik wil hebben: Naam, deelnr. (jaar), pag.nrs. dus: [Literatuur, 2 (1986),
 > 96--112.]

Probeer deze wijziging op named.bst maar eens (niet getest, maar
overgenomen uit siam.bst:

433a434,441
> FUNCTION {format.vol.year}
> { volume field.or.null
>   year empty$
>     { "empty year in " cite$ * warning$ }
>     { " (" year * ")" * * }
>   if$
> }
>
583,584c591,592
<       format.vol.num.pages output
<       format.date "year" output.check
---
>       format.vol.year output
>       format.pages output

N.B < regels zijn uit de oude file > uit de nieuwe, de getallen ervoor zijn
de regelnrs in oude resp nieuwe file, a = toevoegen, c = vervangen.

Piet van Oostrum, Vakgroep Informatica, Rijksuniversiteit Utrecht,
Padualaan 14, Postbus 80.089, 3508 TB Utrecht.
Telefoon: 030-531806   Uucp:   uunet!mcsun!hp4nl!ruuinf!piet
Telefax:  030-513791   Internet:  piet AT cs.ruu.nl




Date:Wed, 27 Jun 90 13:35:16 MET
From:    "P. Wackers" <U216002 AT HNYKUN11.BITNET>
Subject:   BibTeX
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Nog even over het gebruik van named.bst. Ik had de named.sty file er
niet bij gebruikt. Toen ik dat wel deed, kreeg ik ook een komma + een
spatie. Het werkt dus wel hetzelfde.
Bedankt voor de hulp.
Paul Wackers




Date:Thu, 28 Jun 90 01:00:00 MET
From:    CGL AT RUG.NL
Subject:   Character encoding proposal; anybody with experience on the matter
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

From:      IN%"mike AT inrs-telecom.uquebec.ca"  "Michael Ferguson" 23-JUN-1
39
   .20
To:     mwc AT doc.ic.ac.uk, x92%dhdurzi.BITNET AT cunyvm.cuny.edu, roswitha AT admin.kth
se,
    ucir001%frors31.BITNET AT cunyvm.cuny.edu, cgl%hgrrug5.BITNET AT cunyvm.cuny.edu
CC:
Subj:   Font Character Encoding

Received: from JNET-DAEMON by RUG.NL; Sat, 23 Jun 90 06:46 MET
Received: From UWOVAX(MLNET) by HGRRUG5 with Jnet id 4853 for CGL@HGRRUG5; Sat,
 23 Jun 90 06:46 B
Received: from relay.CDNnet.CA by uwovax.uwo.ca with SMTP; (pid 2074) Sat, 23
 Jun 90 00:37:16 EDT
Received: by relay.CDNnet.CA (4.1/1.14) id AA03681; Fri, 22 Jun 90 21:32:45 PDT
Date: 23 Jun 90  0:28 -0500
From: Michael Ferguson <mike AT inrs-telecom.uquebec.ca>
Subject: Font Character Encoding
To: mwc AT doc.ic.ac.uk, x92%dhdurzi.BITNET AT cunyvm.cuny.edu,
 roswitha AT admin.kth.se, ucir001%frors31.BITNET AT cunyvm.cuny.edu,
 cgl%hgrrug5.BITNET AT cunyvm.cuny.edu
Cc: beebe AT science.utah.edu, bnb AT seed.ams.com
Message-Id: <1116*mike AT inrs-telecom.uquebec.ca>
Return-Receipt-To: Michael Ferguson <mike AT inrs-telecom.uquebec.ca>

Dear Roswitha, Bernard, Joachim, Kees, and Malcolm:

This is just a note to bring you up to date with the deliberations on
character encoding that took place at the TUG90 meeting in Texas.

We had a "Birds of a Feather" meeting on font character encoding involving
myself, Jan Michael Rynning, and a number others representing various
vendors. This meeting reaffirmed a number of principles that I and others
have been espousing. I feel that we have a chance now, and will not have
another, to produce font encodings, for both text and mathematics that are
defensible internationally. In addition, I should like to see our effort
result standards that we can use in the TeX community and that we can
submit to ISO. Some of the basic principles for this effort are as follows:

  -----------------------------------


 *1. There will be only one character encoding for all (Roman) text fonts.
This means that the anomalies between the typewriter and Roman fonts will
disappear. In addition there will no longer be any difference in the
character encoding in the math italic and ordinary fonts.

 *2. The entire 256 set of codes, including the lower 128 will be assigned
values. I do not feel that the existence of a character on a Stanford or
MIT keyboard is sufficient reason to include it in the new standard.

 *3. Character encodings that correspond to ligatures will be consistently
encoded in all fonts. If a ligature does not exist in a font, then the,
probably monospaced, equivalent set of letters will placed in that
location. Thus the pair, properly spaced, "fi" will appear in the tt fonts
while the actual ligature will appear in the Roman font.

 *4. The inclusion of ligatures and punctation is essential. Exactly how this
affects language coverage remains to be seen. Careful consultation will be
required. Ligatures that can be accomplished by kerning probably should not
be included. Although people are remembering punctuation when suggesting
standards, they seem to be forgetting ligatures.

 *5. I have asked Barbara Beeton to look into the problem of specifying a
256 math symbol font. In addition, I feel that the conceptual innovation
inherent in the math extension font warrants its submission as a standard.
It is not clear at this time that it would benefit from being extended to
256 characters.

   ------------------------------------

I have received comments form Nicolas Brouard on the Nordic Proposal of Jan
Michael where he indicated that he was in substantial agreement. The major
modification as a result of the deliberations at this meeting is to
code the entire 256 characters rather than just the upper 128.
It is rather exciting to think that we might have 256 Greek, Script, and
Blackboard variables available  for mathematics. In addition I have agreed
to present a TeX modification that will allow the conversion of input to
internal (font) encodings to be programmable. I shall be doing this in the
immediate future.

Contrary to the suggestions of Janusz Bien, I do not believe that "free"
slots should be left in a definition. I think that to do so will invite a
lack of portability. In addition, I feel that making the input to internal
encoding programmable will resolve almost all of the screen display
problems. The only apparent difficulty with this solution involves the
codes that TeX uses to report errors and internal tracing.

I would hope that we could have an agreement by the end of the Cork
meeting, but I feel that it is important that we take our time and do it
"right".

Yours,

Michael J. Ferguson,
Coordinator for Multilingual Activities





Date:Thu, 28 Jun 90 10:12:41 MET
From:    "P. Wackers" <U216002 AT HNYKUN11.BITNET>
Subject:   BibTeX, named.bst
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,
Misschien vindt iemand het wel leuk om te weten dat de wijzigingen die
Piet van Oostrum beschreef voor named.bst inderdaad het gewenste
effect hebben. Het enige wat afwijkt van het door mij gewenste "format"
is dat hij geeft "pages 213--215" en niet "213--215". Ik heb
kunnen vaststellen dat dat komt door de regels 406 en 407 (in de
FUNCTION (format.pages). Als ik daar echter "pages" en "page" weghaal,
krijg ik een foutmelding. Wat doe ik verkeerd?
Paul Wackers.




Date:Thu, 28 Jun 90 12:06:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:   Q: \expandafter etc. Poor stupid me.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo,

ik ben toch niet zo goed (helemaal niet zelfs) in \expandafter's en
\afterassignment's als ik zelf wel zou willen geloven dat ik was.

Ik heb een TeX-file die <dragon3_9.tex> heet. De `famous ``dragon curve'' of
order 9', zoals Knuth zegt. (The TeXbook, pp. 389--391). Maar omdat ik behalve
deze ook wel andere dragon-curves zou willen uitproberen, en geen zin heb om
voor elke curve een edit-slag te moeten maken, wilde ik m.b.v. \jobname de
\dir en \n bepalen voor het dragon-path. Als de file <dragon3_9.tex> heet, is de
\jobname gelijk aan <dragon3_9>. \dir wordt nu 3 en \n wordt nu 9.

Vrolijk maakte ik een macro \SetDirAndN dragon#1_#2 en voerde die de waarde
van \jobname. Dat ``doesn't match it's definition''.  Toen maakte ik een
constructie:

\let\ex\expandafter \let\nx\noexpand
\message{Dragon taken from: \jobname}

\def\dosetDirAndN#1{\ex\dosetdirandn#1\setDirAndN}
\long\def\dosetdirandn#1{\futurelet\next\setDirAndN}
\long\def\setDirAndN dragon#1_#2\setDirAndN{\global\dir=#1 \global\n=#2}

\hskip6cm\path{\dosetDirAndN\jname \dragon}

Dat is ook niet goed. Voor iemand die de materie snapt, zal het wel logisch
zijn, maar ik sprokkel ook maar bij elkaar wat ik nodig denk te hebben. (The
TeXbook, pp. 374--376 en TUGboat, V9N1, pp. 57--61). Toch wil ik wel graag
begrijpen wat ik fout doe, *en* wat ik wel zou moeten doen.

Wie? Who? Wer? Qui? Kdy? Wel? Hwie?

Erik-Jan. Vens AT Rug.Nl




Date:Thu, 28 Jun 90 12:33:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:   Some more. Some more. (Frank Zappa. Tinseltown Rebellion).
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Misschien (om nog een aanvulling te geven op mijn vraag) is het nuttig om een
van de voorbeelden te laten zien, en de volgens mij bijbehorende oplossing van
mijn kant. Het stukje uit de TUGboat is van Stephan von Bechtolsheim, en dat
werkt. Daaronder is van mij, en werkt dus niet. Snif.

---------- 8< -- 8< ---- cut cut -- snipe snipe ---- 8< -- 8< -----------------

% TUGboat,Volume 9 (1988), No. 1

% Define macro to extract substring from \xx.
\def\xx{This is fun\aaa HELP ME\bbb That's it}

% Define macro \extract with three delimited parameters.
% Parameters are \aaa, \bbb and \Del.
% Macro prints substring contained between \aaa and \bbb.
\def\extract #1\aaa#2\bbb#3\Del{#2}

% Call macro to extract substring from \xx.
% Prints "HELP ME".
\expandafter\extract\xx\Del
% which is equivalent to:

\extract This is fun\aaa HELP ME\bbb That's it\Del

\bye

---------- 8< -- 8< ---- cut cut -- snipe snipe ---- 8< -- 8< -----------------

% dragon.tex  (The TeXbook, p. 391)

\input dragonmac \nopagenumbers
\let\ex=\expandafter

\message{Dragon taken from: \jobname}

\def\SetDirAndN:dragon#1_#2:{\global\dir-#1 \global\n-#2}

\hskip6cm\path{\ex\SetDirAndN:\jobname: \dragon}

\bye




Date:Thu, 28 Jun 90 14:44:03 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   Re: Q: \expandafter etc. Poor stupid me.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Erik-Jan "nooit verlegen om een citaat" Vens schrijft:

>ik ben toch niet zo goed (helemaal niet zelfs) in \expandafter's en
>\afterassignment's als ik zelf wel zou willen geloven dat ik was.
En als die hier nou er iets toe deden...

Het toverwoord hier heet \catcode!

>\jobname gelijk aan <dragon3_9>. \dir wordt nu 3 en \n wordt nu 9.
>
>Vrolijk maakte ik een macro \SetDirAndN dragon#1_#2 en voerde die de waarde

Je zegt niet hoe je het voeren deed. De correct manier is:
\expandafter\SetDirAndN\the\jobname
Had je die \the? Dan komt nu de draak onder het gras:

Let op. \jobname (en andere commando's die iets tot een string
converteren, bv \number, \string, en \the) leveren een reeks van
tekens op, elk met categoriecode 12 (inclusief letters en cijfers),
alleen spaties zijn categorie 10 (maar dat doet er even niet toe).

In het bijzonder is de underscore in de \jobname string van categorie 12;
als je echter schrijft \def\a#1_#2┼..., dan heeft die underscore
categorie 8. TeX zal zich dus het laplazerus zoeken naar een underscore
met categorie 8, en zal dus waarschijnlijk een 'runaway argument'
opleveren.

Probeer het eens zo:
┼\catcode`\_=12
 \gdef\dinges#1_#2┼ ...


(ik geef geen garantie voor correctheid, ik heb geen tijd om dit
te testen, het basisidee is in ieder geval wat je nodig hebt.)

Alweer iemand die hard aan een cursus Advanced TeX toe is!


Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  61 2986 (secretary)
   western spiral arm           fax: +31 80 55 3450
   of the galaxy"
                                u641001 AT HNYKUN11.BITNET
                                      ^
                                      note: changed




Date:Thu, 28 Jun 90 13:42:32 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   BibTeX, named.bst
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hi "P. Wackers",

On 28 Jun 90 you wrote:

 > Hallo,
 > Misschien vindt iemand het wel leuk om te weten dat de wijzigingen die
 > Piet van Oostrum beschreef voor named.bst inderdaad het gewenste
 > effect hebben. Het enige wat afwijkt van het door mij gewenste "format"
 > is dat hij geeft "pages 213--215" en niet "213--215". Ik heb
 > kunnen vaststellen dat dat komt door de regels 406 en 407 (in de
 > FUNCTION (format.pages). Als ik daar echter "pages" en "page" weghaal,
 > krijg ik een foutmelding. Wat doe ik verkeerd?

Bibtex gebruikt een stack-taaltje (zoals Postscript en Forth. Door de twee
strings weg te halen heb je de stack layout vernield. Het simpelste is ze
te vervangen door een lege string ("").

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




Date:Thu, 28 Jun 90 15:43:50 MET
From:    nspit AT FYS.RUU.NL
Subject:   Re: BibTeX, named.bst
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

>
> Hallo,
> Misschien vindt iemand het wel leuk om te weten dat de wijzigingen die
> Piet van Oostrum beschreef voor named.bst inderdaad het gewenste
> effect hebben. Het enige wat afwijkt van het door mij gewenste "format"
> is dat hij geeft "pages 213--215" en niet "213--215". Ik heb
> kunnen vaststellen dat dat komt door de regels 406 en 407 (in de
> FUNCTION (format.pages). Als ik daar echter "pages" en "page" weghaal,
> krijg ik een foutmelding. Wat doe ik verkeerd?

waarschijnlijk een * teveel; wanneer je "pages " door " "
vervangt zal het zeker goed gaan

werenfried
spit






Date:Thu, 28 Jun 90 13:42:28 CET
From:    "Sake J. Hogeveen" <A410SAKE AT HASARA11.BITNET>
Subject:   Re: BibTeX, named.bst
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>


M.b.t. BibTeX en het aanpassen van .bst files:

Op de fileserver van SARA (rekencentrum universiteiten Amsterdam) staat
in de ASTRON FILELIST een astron.bst en een bijbehorende LaTeX astron.sty,
die auteur-jaar citaten maken zoals veel sterrekundige tijdschriften die
graag zien.

Om de boel te krijgen: stuur mail naar SARASERV AT SARA.NL met daarin
als text:  GET ASTRON FILELIST.
Het bestand dat je dan toegestuurd krijgt bevat een overzicht van de
astron.bst, astron.sty en aanverwante files.
Met opniew GET <filenaam> <extensie> kun je vervolgens die files ophalen.
(Aan te bevelen is in ieder geval het READ ME file.)

Astron.bst is een aangepaste versie van APALIKE.BST van Oren Patashnik,
en het bevat ook elementen uit NAMED.BST van Peter F. Patel-Schneider.

Door al deze .bst files naast elkaar te leggen zou je een aardig idee
moeten krijgen van het effect van diverse aanpassingen.

Sake J. Hogeveen
____________________________________________________________________________
Astronomical Institute `Anton Pannekoek', Roetersstraat 15, 1018 WB Amsterdam,
The Netherlands.
Telephone +31 (0)20 525 6025/6004.
Bitnet: A410SAKE@HASARA11     Internet: A410SAKE AT SARA.NL
UUCP: l42 AT nikhefh.nikhef.nl




Date:Thu, 28 Jun 90 16:05:15 met
From:    Piet van Oostrum <piet AT CS.RUU.NL>
Subject:   Re: Q: \expandafter etc. Poor stupid me.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Hallo Victor,

Op 28 Jun 90 schreef je:

 > Het toverwoord hier heet \catcode!
 >
 > Let op. \jobname (en andere commando's die iets tot een string
 > converteren, bv \number, \string, en \the) leveren een reeks van
 > tekens op, elk met categoriecode 12 (inclusief letters en cijfers),
 > alleen spaties zijn categorie 10 (maar dat doet er even niet toe).
 >
 > In het bijzonder is de underscore in de \jobname string van categorie 12;
 > als je echter schrijft \def\a#1_#2E..., dan heeft die underscore
 > categorie 8. TeX zal zich dus het laplazerus zoeken naar een underscore
 > met categorie 8, en zal dus waarschijnlijk een 'runaway argument'
 > opleveren.

Inderdaad. Maar het is nog erger: ook de d r a g o n hebben catcode 12. Dus
in de definitiefase moeten deze ook een andere catcode krijgen. Dat heeft
wel tot gevolg dat je deze letters niet zomaar kunt gebruiken, ook niet in
\def, en zelfs niet in \catcode !!

De volgende versie werkt:
------------------------------------------------------------------------
% dragon.tex  (The TeXbook, p. 391)

\let\ex=\expandafter

\message{Dragon taken from: \jobname}
{\let\C=\catcode\let\G=\gdef
\C`d=12 \C`r=12 \C`a=12 \C`g=12 \C`o=12 \C`n=12 \C`_=12
\G\SETDIRANDN dragon#1_#2:{\SeTDIRANDN{#1}{#2}}
}
\newcount\dir \newcount\n
\def\SeTDIRANDN#1#2{\global\dir=#1\global\n=#2}
\hskip6cm{\ex\SETDIRANDN \jobname: }
------------------------------------------------------------------------

Let op de hoofdletters. Overigens zou het een stuk makkelijker zijn als de
filenaam in hoofdletters was, of door \uppercase te gebruiken.

 > (ik geef geen garantie voor correctheid, ik heb geen tijd om dit
 > te testen, het basisidee is in ieder geval wat je nodig hebt.)
 >
 > Alweer iemand die hard aan een cursus Advanced TeX toe is!
 >
Hopelijk heb je wel tijd om de cursus goed voor te bereiden :=)

                                Hartelijke groeten,
                                Piet van Oostrum.




Date:Fri, 29 Jun 90 10:17:00 MET
From:    gros d'egueulasse dit 'les gens heureux me font chier!'
Subject:    een shell-archive met de macros voor dragon curves.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Dit is een shell-archive met de dragon macros uit Knuth, The TeXbook, Appendix
D: Dirty Trick, pp. 389--391. 'k Vond 't wel leuk om eens uit te proberen. Om
het de gebruiker makkelijker te maken heb-t-ik het zo ingericht dat als de
naam van de file <drag<dir>_<n>.tex> is, de aanroep van de dragon curve
<\path{\dir=<dir> \n=<9> \dragon} zal zijn. Op deze manier houd je precies
genoeg letters over om zinvolle getallen voor <dir> en <n> in te vullen. Om
dus `the famous ``dragon curve'' of order 9' te krijgen, maak je een file
<drag3_9.tex>.

Yo! (is the place to be),

Erik-Jan. Vens AT Rug.Nl

Volgt nu het shell-archive. Om weer uit te pakken, deze hele tekst weg gooien.
# To unbundle, sh this file
echo drag3_9.tex 1>&2
sed 's/^X//' >drag3_9.tex <<'End of drag3_9.tex'
X% dragon.tex  (The TeXbook, p. 391)
X
X\input dragonmac \nopagenumbers
X\let\ex=\expandafter
X
X\message{Dragon taken from: \jobname}
X
X{
X\catcode`D=12 \catcode`R=12  \catcode`A=12 \catcode`G=12 \catcode`_=12
X\gdef\setdirandn DRAG#1_#2:{\Setdirandn{#1}{#2}}
X}
X
X\def\Setdirandn#1#2{\global\dir=#1\global\n=#2\relax
X  \ifnum\dir>3 \message{direction must be less then 4. replaced by 3}
X    \dir=3\fi
X  \ifnum\dir<0 \message{direction must be at least 0. replaced by 0}
X    \dir=0\fi
X}
X
X\edef\MakeUpperJobName{\def\noexpand\JOBNAME{\jobname}}
X\uppercase\expandafter{\MakeUpperJobName}
X
X\centerline{\path{\ex\setdirandn \JOBNAME: \dragon}}
X
X\bye
End of drag3_9.tex
echo dragonmac.tex 1>&2
sed 's/^X//' >dragonmac.tex <<'End of dragonmac.tex'
X% dragonmac.tex (The TeXbook, pp. 389--391)
X
X\input pathmac
X
X\newcount\n % the current order in the \dragon and \nogard macros
X\def\dragon{\ifnum\n>0{\advance\n-1 \dragon\L\nogard}\fi}
X\def\nogard{\ifnum\n>0{\advance\n-1 \dragon\R\nogard}\fi}
End of dragonmac.tex
echo pathmac.tex 1>&2
sed 's/^X//' >pathmac.tex <<'End of pathmac.tex'
X% pathmac.tex (The TeXbook, pp. 389--391)
X
X\font\qc=manfnt
X
X\catcode`\ =9 \endlinechar=-1 % ignore all spaces (temporarily)
X\newcount\dir \newdimen\y \newdimen\w
X\newif\ifvisible \let\B=\visibletrue \let\W=\visiblefalse
X\newbox\NE \newbox\NW \newbox\SE \newbox\SW \newbox\NS \newbox\EW
X\setbox\SW=\hbox{\qc a} \setbox\NW=\hbox{\qc b}
X\setbox\NE=\hbox{\qc c} \setbox\SE=\hbox{\qc d}
X\w=\wd\SW \dimen0=\fontdimen8\qc
X\setbox\EW=\hbox{\kern-\dp\SW \vrule height\dimen0 width\wd\SW} \wd\EW=\w
X\setbox\NS=\hbox{\vrule height\ht\SW depth\dp\SW width\dimen0} \wd\NS=\w
X\def\L{\ifcase\dir \dy+\NW \or\dx-\SW \or\dy-\SE \or\dx+\NE\dd-4\fi \dd+1}
X\def\S{\ifcase\dir \dx+\EW \or \dy+\NS \or \dx-\EW \or \dy-\NS\fi}
X\def\R{\ifcase\dir \dy-\SW\dd+4 \or\dx+\SE \or\dy+\NE \or\dx-\NW\fi \dd-1}
X\def\T{\ifcase\dir\kern-\w\dd+2\or\ey-\dd+2\or\kern\w\dd-2\or\ey+\dd-2\fi}
X\edef\dd#1#2{\global\advance\dir#1#2\space}
X\def\dx#1#2{\ifvisible\raise\y\copy#2 \if#1-\kern-2\w\fi\else\kern#1\w\fi}
X\def\dy#1#2{\ifvisible\raise\y\copy#2 \kern-\w \fi \global\advance\y#1\w}
X\def\ey#1{\global\advance\y#1\w}
X\def\path#1{\hbox{\B \dir=0 \y=0pt #1}}
X\catcode`\ =10 \endlinechar=`\^^M % resume normal spacing conventions
End of pathmac.tex
echo path.tex 1>&2
sed 's/^X//' >path.tex <<'End of path.tex'
X% path.tex
X
X\input pathmac
X
X\path{\L\R\S\R\S\R\S\S\R\R}
X
X\path{\R\R\R\R\T\S\S\L\L\L\L\L\S}
X
X\def\X{\L\T\L\L\T\L\L\T} \path{\X\X\X\X}
X
X\path{\R\R\S
X  \W\S\S\S\R\R
X  \B\R\R\S\R\S\R\S\S\S\R\S\S\S\S\S\R\S\R
X  \W\R\R\R\S\L\S
X  \B\L\S\S\S\S}
X
X\bye
End of path.tex





Date:Fri, 29 Jun 90 13:53:00 MET
From:    CGL AT RUG.NL
Subject:   Makeindex status. Seems very interesting to me, so ... Kees
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

From:      IN%"Beebe AT science.utah.edu"  "Nelson H. F. Beebe" 29-JUN-1990
4
To:     tex-archive AT science.utah.edu
CC:
Subj:   TeX archives -- MakeIndex status

Return-path: BEEBE AT science.utah.edu
Received: from science.utah.edu by RUG.NL; Fri, 29 Jun 90 01:30 MET
Date: Thu 28 Jun 90 17:15:31-MDT
From: "Nelson H. F. Beebe" <Beebe AT science.utah.edu>
Subject: TeX archives -- MakeIndex status
To: tex-archive AT science.utah.edu
Cc: Beebe AT science.utah.edu
X-US-Mail:
 "Center for Scientific Computing, South Physics, University of Utah, Salt Lake
   City, UT 84112"
X-Telephone: (801) 581-5254
Message-ID: <12601516127.19.BEEBE AT SCIENCE.utah.edu>

As a start at informing one another what we have, here is an
update on MakeIndex, the indexing package for TeX, LaTeX,
and troff.

Pehong Chen, the author of MakeIndex, has left Berkeley for
the world of private computer consulting, and no longer has
e-mail access.  I've therefore taken MakeIndex under my
wing, and recent changes applied all known bug fixes, and
brought the code up to ANSI C, with complete ANSI-style
function prototypes everywhere.  According to the README
file,

>>...
>> This current version is known to compile and run on UNIX (cc
>> and gcc), VAX/VMS (VMS cc), TOPS-20 (kcc-20 and pcc-20), and
>> IBM PC DOS (Microsoft C Version 5.0), Atari ST, Siemens
>> BS2000 (CCD-2000), and IBM MVS/XA (IBM-C370).
>>...

[More systems are now actually covered; see below.]

The current version is 2.9, and is available on
science.utah.edu in the directory aps:<tex.pub.makeindex> in
split compressed .tar files that preserve the directory
structure, and also in .arc files that can be used to
reconstruct each of the many directories.  8-bit binary
files must transferred in tenex mode, NOT binary mode.

Joachim Schrod in Darmstadt is looking at the code with a
view to enhancing the sorting capabilities, so as to do a
better job of handling accented words; no promises or
commitments are implied.

From time to time the question comes up whether MakeIndex
should be rewritten in Web.  I'm inclined to say no, because
(a) it works well as it stands, (b) C compilers are in fact
available now for every machine that TeX runs on, and (c) no
one is likely to have the time to write a Web version.

You are all welcome to grab MakeIndex 2.9, either via ftp,
or via e-mail through tuglib AT science.utah.edu (a painful
way, since you'll have to reconstruct it from pieces).

It is quite possible that others have done independent work
on MakeIndex, in which case a merger is called for.  Please
correspond with me directly (not to the whole list) if you
have a version that purports to be newer.  The LOG file from
the src directory follows:

                       Revision History for MakeIndex

This is a reverse time-ordered history of changes to MakeIndex.

-----------------------------------------------------------------
[12-Dec-1989]
        Version 2.9 released by Nelson H.F. Beebe (beebe AT science.utah.edu)

        Testing carried out on:
                PC DOS          Microsoft C 5.0, Turbo C 2.0, Lattice C 6.02
                TOPS-20         KCC-20 and PCC-20
                UNIX            Sun OS 4.0.3 cc and gcc 1.36
                VAX ULTRIX-32   cc
                VAX VMS         VMS C 2.3

        Added support for Turbo C 2.0 and Lattice C 6.02 on IBM PC DOS.

        Although compilation and linking were successful with Lattice
        C, the executable produced a 'Not enough core...abort' message
        at run time under the D, L, and H memory models.  Replacing
        malloc(n) calls by halloc(1L,n) did not remove the problem;
        debugging statements (selected by defining DEBUG at compile
        time) showed that calls to malloc() and calloc() allocated
        less than 15KB before the abort.  Curiously, a separate little
        test program that allocated 1000-byte blocks with malloc() or
        calloc() could allocate over 55KB in the small memory model,
        and over 500KB in the large models, before aborting.  Thus, we
        conclude for now that Lattice C 6.02 is not usable for
        MakeIndex.

        Added ARGS macro to simplify function declarations in ANSI and
        pre-ANSI styles.

        Added missing definition of OS_XENIX in mkind.h.

        Moved declarations of static functions from mkind.h to relevant
        *.c files to remove compiler warnings about declared, but unused,
        objects.

        Removed a couple of unreachable break statements that raised
        compiler warnings.

        Use ANSI strchr/strrchr instead of K&R index/rindex; the former
        are #defined to the latter for systems that have only the old
        names.

        Fixed scan_arabic() in scanid.c to allow ARABIC_MAX digits,
        instead of one less than that, and fix condition on which the
        error message about too many Arabic digits is triggered.

        Repair widespread confusion between NUL (the character '\0'),
        and NULL (the pointer).  NUL is a user-definable name, while
        NULL is defined by the implementation; on segmented memory
        machines, pointers and integers need not be equivalent, so it
        may hold that NULL != NUL.  Previous versions of MakeIndex used
        NULL to mean both, and redefined NULL to be '\0'.  In general,
        NULL must be typecast to a pointer of the appropriate type,
        since under ANSI C, it will usually be defined to be something
        like (void*)0 or (void*)0L.

[11/11/1989]
        Version 2.8 released by Pehong Chen (chen AT renoir.berkeley.edu).
        (1) ARABic_MAX changed from 4 to 5, duo to Sebastian Rahtz's
            (spqr%ecs.southampton.ac.uk AT NSFnet-Relay.AC.UK) report
            on TeXhax #87 (9/17/1989).
        (2) A nasty sorting bug was fixed due to a report from
            Martha Wershofen-Mersbach (GRZTEX%dbngmd21.bitnet AT NET.BIO.NET)
            of the German National Research Center For Computer Science (GMD).
        (3) Siemens BS2000 ported done by Andreas Brosig of the German
            National Research Center For Computer Science (GMD).
        (4) German word ordering, the "-g" option contributed by Brosig.
        (5) Miscellaneous bug fixes by Brosig:
            A. Blank compression routine ("-c") fixed.
            B. The "-p" option now works for MSDOS and MVS.  Have to
               logfile in binary mode for OS_PCDOS and add OS_MVSXA to an
               existing #if because fseek(...) does not work under MVS.
            C. If an indexentry contains more than 2 IDX_LEVEL '!' or more
               than 3 IDX_ACTUAL '@', MakeIndex would ignore this entry
               and writes "Extra ... at position ..." to the transcript file.
               This is now fixed.
            D. If an indexentry is too long (> STRING_MAX), MakeIndex would
               ignore it and write a message to the transcript file.
               This is now fixed.
            E. For MSDOS(OS_PCDOS) LONG_MAX is set back to 144
               and STRING_MAX to 64.  Otherwise a core error will occur
               in the case of a big IDX-file.

-----------------------------------------------------------------
[10/1/1988]
        Version 2.7 released by Pehong Chen (chen AT orc.olivetti.com).
        (1) Fixed a string printing bug reported by anita AT vax1.acs.udel.edu
            through Leslie Lamport.  The string should be an argument
            to the printf format, instead of the format itself.

-----------------------------------------------------------------
[7/14/1988]
        Version 2.6 released by Pehong Chen (chen AT orc.olivetti.com).
        (1) The documentation for UNIX man page makeindex.l went through
            revision by Rick P. C. Rodgers of UCSF (rodgers AT cca.ucsf.edu).
            Rick also provided a sample style file for MakeIndex to work
            with troff (see the man page for details).
        (2) String length (LONG_MAX) was increased from 144 to 1024.
        (3) Fixed a letter heading bug.  It used to put the heading
            below the first index entry.
        (4) Added a new feature, the terminating delimiter for page list.
            This delim_t string is null by default.  It can be redefined
            as a period if one would like a page list to be terminated
            by a period, for example.  This delimeter has no effect
            on an index entry which does not have any page number
            associated with it.

-----------------------------------------------------------------
[4/14/1988]
        Version 2.5 released by Pehong Chen (phc AT berkeley.edu),
        with VAX/VMS extensions by
            Charles Karney
            Plasma Physics Laboratory  Phone:   +1 609 243 2607
            Princeton University       MFEnet:  Karney AT PPC.MFEnet
            PO Box 451                 ARPAnet: Karney%PPC.MFEnet AT NMFECC.ARPA
            Princeton, NJ 08543-0451   Bitnet:  Karney%PPC.MFEnet AT ANLVMS.Bitnet
        The file VMSmake.com for VAX/VMS users who don't have make.
        This version also includes a fix under XENIX by
            Baron O.A. Grey             UCLA Computer Science Department
            baron AT CS.UCLA.EDU           ...!(ucbvax,ihnp4)!ucla-cs!baron

-----------------------------------------------------------------
[3/20/1988]
        Version 2.4 released by Pehong Chen (phc AT berkeley.edu),
        the ``official'' version of MakeIndex that enters public domain.

        * length() (originally defined in mkind.c) is replaced by
        the standard function strlen(), which in some C implementations
        is, or can be, expanded to in-line efficient hardware instructions
        (e.g.  Microsoft C and VAX Unix); I have not yet done this.

-----------------------------------------------------------------
[20-Jan-88]
        Portable version 2.3 released by Nelson H.F. Beebe
        (BEEBE AT SCIENCE.UTAH.EDU).

        I spent 3 days implementing MakeIndex on Sun OS3.3 Unix
        (cc and gcc), TOPS-20 (KCC-20 and PCC-20 compilers), PC
        DOS (Microsoft C Version 5.0), and VAX VMS.  This was at
        times a frustrating experience, because the effort
        revealed a great many portability problems in the
        original code (from VAX Unix, I think), plus some genuine
        bugs in MakeIndex, plus a bug in each of two compilers
        (KCC-20 and PCC-20)!

        The changes for this version over 2.2 are exclusively bug
        fixes and portability enhancements.  Thanks to the
        original authors' careful design, no functionality
        changes are likely to be necessary.

        Besides getting the code working correctly on 4 systems
        and 6 compilers, I have made several passes over the code
        to reduce the lint complaints to a minimum, and remove
        all of the warnings produced by the IBM PC Microsoft C
        Version 5.0 compiler, which is the only one of the above
        systems which completely implements October 1986 draft
        ANSI C; the ANSI function prototype checking caught
        numerous problems.

        With these changes, I believe that we now have a version
        of MakeIndex that satisfies the important goal of TeX --
        the same input will produce identical output results on
        all machines, whether they be micros, minis, mainframes,
        or supercomputers.  This is true at least for the 6
        systems for which testing has been possible at Utah.

        Here is a summary of bug corrections and other changes:

        * Several routines fell off the end without returning a
        value, when the caller expected it; this was particularly
        hard to trace (2 days of effort--the code only failed on
        PCC-20, and work correctly with the other 4).

        * Equivalence of *short and *int was incorrectly assumed
        in one routine; this made the code dependent on the byte
        storage order (it works on the little-Endian VAX
        architecture, but will fail on big-Endian architectures
        (IBM et al)).

        * Equivalence of *int and *char was incorrectly assumed
        in the call to qsort(); the only one of the 6 compilers
        which uses a different format for *char values is KCC-20,
        and that feature caught this bug (the compiler didn't
        find it for me, but when the sort failed, I tracked it down).

        * Routines which do not return a value are now explicitly
        typed `void' instead of nothing or `int', and mkind.h has
        both K&R old-style and new ANSI style function
        declarations for all routines; the choice is made on the
        basis of the compiler and operating-system switch
        selections.

        * A single (incorrect) use of backslash-dot (\.) escape
        sequence in scanid.h has been reduced to dot (.).

        * exit() was called without a valid argument in mkind.h.

        * In several places, code of the form
                char c;
                while ((c = getchar()) != EOF)
        existed; this is incorrect and will fail on many machines
        when the EOF (== -1) value returned by getchar() is
        truncated to a byte value for storage in c, then extended
        to an integer again and compared with EOF.  The correct
        approach is to use "int c;" instead of "char c;".  Type
        declarations have been changed from "short" or "int" to
        "char" or vice versa in several places in order to
        achieve consistency, and explicit typecasts are used when
        data types are intentionally changed by assignment or
        argument association.

        * mkind.h now has a SHORTNAMES section to define short
        names for the 45 long ones which clash when reduced to 6
        characters (although KCC-20 and PCC-20 both handle long
        names, they produce assembly code output, and the
        assembler limits names to 6 case-insensitive chars).

        * File names have been reduced to 6 characters, allowing
        the source to be ported to all of the above systems
        without tedious file renaming.  The TOPS-20 LINK program
        also runs under TOPS-10, and because TOPS-10 has a
        6-character file name limit, LINK-20 does too, sigh...
        The executable is called makeindex on all systems except
        PC DOS, where the 8-character limit reduces it to
        makeindx.  Similarly, filenames with special characters
        (ind+ and ind-) have been renamed to portable names.

        * Reference to sys/file.h has been eliminated; it was
        only needed for the symbol R_OK passed to access().
        sys/file.h is missing from most non-Unix C
        implementations, while the value of R_OK (4) for access()
        is consistent for all but PCC-20, where only F_OK (0) is
        implemented.

        * Makefiles have been produced for each of the above
        systems (I have the same version of a public-domain make
        running on all of them).

        * A public version of qsort.c has been included in
        MakeIndex for two reasons.  First, some non-Unix C
        implementations lack it.  Second, quicksort is not a
        `stable' sorting algorithm; that is, the order of items
        with equal keys is not necessarily identical between the
        input and the output.  Different implementations of the
        sort algorithm in the host qsort() can therefore give
        different ordering in such cases (PCC-20 and KCC-20
        differed, which is how I caught this).  qsort is
        #define'd to qqsort for all systems, in order to avoid
        possible clashes with the standard library version (this
        happens with IBM PC Microsoft C and with VAX VMS).

        * Version 2.2 did not come with any documents containing
        index entries to test MakeIndex with.  I have taken the
        liberty of preparing an index for Leslie Lamport's
        article, ../doc/makeindex.tex for a test version,
        ../test/test.tex.   This can be used both to test MakeIndex,
        as well as to illustrate the production of an index for
        new users (I'm using it in a class that I am teaching on
        LaTeX).  test.tex uses the showidx document style option
        to get the index entries displayed as marginal notes, and
        the index entries in test.tex have been carefully
        formatted  to always begin a line; that way, they can be
        easily extracted (e.g. by grep), so that one can see the
        original entries, the LaTeX output .idx file, and the
        MakeIndex output .ind file.

        * The bug fix for PCC-20 has been posted to the TOPS-20
        bulletin board; PCC-20 was developed at CS.UTAH.EDU, but
        we (SCIENCE.UTAH.EDU) now have their DEC-20, so I guess
        we have become the default PCC bug-fix site.  The bug in
        KCC-20's preprocessor has been reported to the KCC
        developers at SRI-NIC.ARPA but cannot be easily fixed
        until the draft ANSI C support in KCC-20 is complete; in
        the meantime, conditional compilation is used to provide
        alternate code which compiles correctly.

-----------------------------------------------------------------
[29-May-87]
        Version 2.2 (5/29/1987) released by Pehong Chen (phc AT berkeley.edu)
-------




Date:Fri, 29 Jun 90 13:54:00 MET
From:    CGL AT RUG.NL
Subject:   Once again an interesting state of affairs, so ... Kees
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

From:      IN%"Beebe AT science.utah.edu"  "Nelson H. F. Beebe" 29-JUN-1990
3
To:     tex-archive AT science.utah.edu
CC:
Subj:   TeX archives -- BibTeX style file status

Return-path: BEEBE AT science.utah.edu
Received: from science.utah.edu by RUG.NL; Fri, 29 Jun 90 01:37 MET
Date: Thu 28 Jun 90 17:34:12-MDT
From: "Nelson H. F. Beebe" <Beebe AT science.utah.edu>
Subject: TeX archives -- BibTeX style file status
To: tex-archive AT science.utah.edu
Cc: Beebe AT science.utah.edu
X-US-Mail:
 "Center for Scientific Computing, South Physics, University of Utah, Salt Lake
   City, UT 84112"
X-Telephone: (801) 581-5254
Message-ID: <12601519527.19.BEEBE AT SCIENCE.utah.edu>

While Oren Patashnik is finishing up BibTeX 1.0, perhaps we
can get a notion of what has been done with the latest
version, 0.99c, in the way of style files.

I'm guessing that sun.soe.clarkson.edu probably has the
latest stuff, since it took over the LaTeX style file
repository from Rochester.  Here are the current contents of
~ftp/pub/bibtex-style:

-rw-r--r--  1 325           788 May  2  1989 Description
-rw-r--r--  1 325           395 Jun 28 02:01 Index
lrwxrwxrwx  1 root           21 Jun 26  1989 Readme -> ../latex-style/Readme
-rw-r--r--  1 325         22648 Apr 15  1988 aaai-named.bst
-rw-r--r--  1 325         19367 Feb  2  1988 acm.bst
-rw-r--r--  1 325         21794 Feb  2  1988 apalike.bst
-rw-r--r--  1 325          7402 Jan  4  1989 cpp.el
-rw-r--r--  1 325         16932 Feb  2  1988 ieeetr.bst
-rw-r--r--  1 325          1002 Feb 19  1988 makebst.sh
-rw-r--r--  1 325         22924 Mar 14  1989 named.bst
-rw-r--r--  1 325         99256 Jan  4  1989 physics.btx
-rw-r--r--  1 325         17956 Feb  2  1988 siam.bst

and ~ftp/pub/bibtex has:

-rw-r--r--  1 325         20285 Dec  5  1989 abbrv.bst
-rw-r--r--  1 325         23863 Dec  5  1989 alpha.bst
-rw-r--r--  1 325         73045 Dec  5  1989 btxbst.doc
-rw-r--r--  1 325         20569 Dec  5  1989 plain.bst
-rw-r--r--  1 325         17986 Dec  5  1989 unsrt.bst

At Utah, I've recently prepared two variants of plain and
alpha, available in ps:<anonymous>is-*.bst; they include
ISBN numbers in the output.  [Is anyone aware of software
that can check ISBN numbers for legality?  According to a
Comm. ACM article several months ago, they do carry a
checksum.]

The question of a named style (apalike in 0.98, I think)
comes up regularly from people in the social sciences and
humanities; the author of apalike, Stephen Gildea, has never
updated it for 0.99c, and neither has Oren Patashnik.  Does
someone out there have a neat little bundle of other styles?
-------




Date:Fri, 29 Jun 90 15:15:27 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   Re: Q: \expandafter etc. Poor stupid me.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Ha die Piet,
>Hallo Victor,
>
>Inderdaad. Maar het is nog erger: ook de d r a g o n hebben catcode 12. Dus

Alsof ik dat niet wist. Ik wilde alleen nog wat te puzzelen over laten.

>in de definitiefase moeten deze ook een andere catcode krijgen. Dat heeft
>wel tot gevolg dat je deze letters niet zomaar kunt gebruiken, ook niet in
>\def, en zelfs niet in \catcode !!

Helaas. Verkeerde conclusie.

>
>De volgende versie werkt:
>------------------------------------------------------------------------
>% dragon.tex  (The TeXbook, p. 391)
>
>\let\ex=\expandafter
>
>\message{Dragon taken from: \jobname}
>{\let\C=\catcode\let\G=\gdef
>\C`d=12 \C`r=12 \C`a=12 \C`g=12 \C`o=12 \C`n=12 \C`_=12
>\G\SETDIRANDN dragon#1_#2:{\SeTDIRANDN{#1}{#2}}
>}

Ja, het werkt.

Ik had gehoopt dat ik met de opmerking dat \string ook categorie 12
opleverde een voldoende hint had gegeven dat Erik-Jan
de volgende oplossing zou vinden:

{\escapechar=-1 \catcode`\_=12
 \expandafter\gdef\expandafter\setdirandn\string\dragon#1_#2{blah}}

Overigens wordt hierin wel een beetje after geexpandeerd.

> > Alweer iemand die hard aan een cursus Advanced TeX toe is!
> >
>Hopelijk heb je wel tijd om de cursus goed voor te bereiden :=)

Schalk! Kom maar kijken hoe ik het er van af breng...

Overigens meen ik me te herinneren dat jij een baard hebt,
dus is de toepasselijk smiley in jouw geval :-)=

Ik heb een bril, hetgeen het B-) maakt.

En rara wat is een =:-) smiley?

Tot zover de ongein. Back to work.


Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  61 2986 (secretary)
   western spiral arm           fax: +31 80 55 3450
   of the galaxy"
                                u641001 AT HNYKUN11.BITNET
                                      ^
                                      note: changed




Date:Fri, 29 Jun 90 15:50:40 MET
From:    Victor Eijkhout <U641001 AT HNYKUN11.BITNET>
Subject:   Geen \the dus. Sorry.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

Ditmaal wel getest (en het lijkt te werken op <dragon2_5.tex>):

{\escapechar=-1 \catcode`\_=12
 \expandafter\gdef\expandafter\setdirandn\string\dragon
     #1_#2{\message{nummer:#1, subnummer:#2}}}

\expandafter\setdirandn\jobname

(dus zonder \the. mijn excuses.)

Hier zit weer een fraaie streek achter: het probleem was om een
reeks letters  d r a g o n  met categorie 12 te krijgen.
Piet* van Oostrum deed dat door al die letters even de correcte
categorie te geven. Dat kan, maar het maakt die letters onbruikbaar
voor andere doeleinden. Ik doe het hier door de control sequence
\dragon te \string-en. Het enige probleem is dat
\string\dragon de reeks  \ d r a g o n  oplevert. Maar, die
backslash is niet zomaar de backslash: die is teken nummer
\escapechar. En als dat negatief is (of groter dan 127 voor TeX2,
dan wel 255 voor TeX3) wordt er geen teken ingevoegd.
Krek wak wou!

En nu moet ik maar eens stoppen met dit soort dingen uit te
leggen, anders blijft er niets meer over voor mijn cursus :-(

Heb jij hier voldoende aan, Erik_Jan, sorry, Erik-Jan?


Victor Eijkhout                 Department of Mathematics
                                University of Nijmegen
                                Toernooiveld 5
  "Far out in the uncharted     6525 ED Nijmegen, the Netherlands
   backwaters of the unfash-
   ionable end of the           +31 80  65 2486 (office)
   western spiral arm              id   65 2986 (secretary)
   of the galaxy"                  id   44 8664 (home)
                                fax: +31 80 55 3450

                                u641001 AT HNYKUN11.BITNET




Date:Fri, 29 Jun 90 21:44:00 MET
From:    David van Leeuwen <DAVID AT HLERUL59.BITNET>
Subject:   RE: Geen \the dus. Sorry.
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

u641001 AT HNYKUN11.bitnet
      ^ note: we 've become used to it




Date:Fri, 29 Jun 90 22:34:00 MET
From:    CGL AT RUG.NL
Subject:   Interesting survey Uk-archive. Kees
Sender:    TEX-NL <TEX-NL AT HEARN.BITNET>

From:      IN%"spqr AT ecs.southampton.ac.uk"  "Sebastian Rahtz" 29-JUN-1990
82
To:     tex-archive AT science.utah.edu
CC:
Subj:   Re: archive contents

Return-path: spqr <@science.utah.edu:spqr AT ecs.southampton.ac.uk>
Received: from science.utah.edu by RUG.NL; Fri, 29 Jun 90 18:14 MET
Received: from NSFnet-Relay.AC.UK by science.utah.edu with TCP; Fri 29 Jun 90
 10:10:43-MDT
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK via Janet with
 NIFTP  id aa18680; 29 Jun 90 16:31 BST
Received: from vicky.ecs.soton.ac.uk by hilliard.ecs.soton.ac.uk; Fri, 29 Jun
 90 16:31:16 BST
Date: Fri, 29 Jun 90 16:31:20 bst
From: Sebastian Rahtz <spqr AT ecs.southampton.ac.uk>
Subject: Re: archive contents
To: tex-archive AT science.utah.edu
Message-Id: <19724.9006291531 AT manutius.ecs.soton.ac.uk>
In-Reply-To: <614.9006291412 AT hilliard.ecs.soton.ac.uk>

Nelson asked for a summary of what archives hold. Can I attempt to
summarize the UK archive?

 1) we are not inaccessible outside the UK; our mail server does a
    thriving business worldwide. but ftp is only available within the UK

 2) we aim to have a complete archive; there are no known significant
    omissions (though we may well not know about packages). there are
    no specialisms.

 3) the archive working party includes VMS, Unix, MS-DOS and Mac
    experts, and we have a VM/CMS backup person.  VMS, SMDOS and Unix versions
    of software tend to get the best treatment. We have some Atari
    material, and Aston funded the development of OzTeX, so that is
    well-covered.

 4) our biggest problem is lack of interactive access, and the
    enormous difficulty in cataloguing and `maintaining' the holdings.
    we keep our heads above water, but only just. our second biggest
    bugbear is the incompatibility in binary file formats between VMS
    and everyone else.

Sebastian Rahtz