UKTeX V90 #09       Friday 23 March 1990 

              BibTeX: writing bst files for European conventions
                              Problem with PSdvi
                            DECWindows TeX-preview
                                     TeX
               TeXserver now permits wildcards in file requests

Editor Peter Abbott

Latest TeXhax in the Archive is #31
Latest TeXmag in the Archive is V3N4 (in 2 parts)                      

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

Via: UK.AC.ASTON.MAIL; Mon, 19 Mar 90  10:34 GMT
Via: UK.AC.NOTTINGHAM.CCC.VAX; Mon, 19 Mar 90  10:31 GMT
Date:		Mon, 19 MAR 90 10:28:28 GMT
From:		CCZDGR@UK.AC.NOTTINGHAM.CCC.VAX
Subject:        BibTeX: writing bst files for European conventions
Sender:         JANET"CCZDGR@UK.AC.NOTTINGHAM.CCC.VAX" <CCZDGR@UK.AC.NOTTINGHAM.CCC.VAX>
Message-Id:     <20400205_0011A588.00933E8C19610A40$8_1@UK.AC.NOTTINGHAM.CCC.VAX>
Originally-to:  JANET"abbottp@uk.ac.aston"
Originally-from:CCZDGR       "David Rhead"
Mailer:         Janet_Mailshr V3.5 ( 13-OCT-1989 14:07:27 )

I was trying to produce some bst files that gave output as shown in
BS 5605 "Citing publications by bibliographical references" and in
Judith Butcher's "Copy-editing" (Cambridge U. P., 1981).
 
One problem was that, in styles that have titles in lowercase except for the
first letter, the BS 5605 examples and Butcher's "Select bibliography" keep
lowercase after a colon, whereas BibTeX's change.case$ with the t option
makes the first letter after a colon (and white space) into a capital.
Thus I couldn't get a bst file that produced the effect shown by BS 5605
and Butcher.
 
I mailed Oren Patashnik to suggest that, as well as accepting l, u and t,
change.case$ should accept something else that acted like t, but didn't
upper-case the letter following a colon.  His reply included the following:
 
- --------------------------------------------------------------------------
I think I'm convinced that I should indeed allow the 4th option.
Barring some unlikely change of mind, I'll implement it for BibTeX
version 1.00 (due out at the beginning of summer) and I'll probably
use `f' for the option name.
 
[Version 1.00 of BibTeX and the standard styles will be the "frozen"
versions, after which I'll be leaving Stanford and will make changes
only for outright bugs.  If you know of any European conventions in
the same vein as the one above (the one suggesting the case.change$
change) by all means let me know within the next two months, else
they will forever be the responsibility of European .bst-writers.]
- --------------------------------------------------------------------------
 
Thus, if you have any opinions about "conventions in the same vein",
you have 2 months to let him know.  He can be mailed as
      opbibtex@neon.stanford.edu
 
 
 
                                                      David Rhead
                                                      Nottingham University

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

Via: UK.AC.ASTON.MAIL; Mon, 19 Mar 90  15:11 GMT
Via: UK.AC.EARN-RELAY; Mon, 19 Mar 90  15:07 GMT
Received:
          from UKACRL by UK.AC.RL.IB (Mailer X1.25) with BSMTP id 2482; Mon, 19
                Mar 90 15:05:52 GM
X-Delivery-Notice: SMTP MAIL FROM does not correspond to sender.
Received:
           from pttrnl.nl (BRAAMS@HLSDNL5) by UKACRL.BITNET (Mailer X1.25) with
                BSMTP id 5882; Mon, 19 Mar 90 15:05:36
Date:           Mon, 19 Mar 90 10:58 MET
From:           "Johannes L. Braams" <JL_Braams@NL.PTTRNL>
Subject:        Problem with PSdvi
Message-id:     <C16FACA136BF2024DB@pttrnl.nl>
X-Organization: PTT Research Neher Laboratories, The Netherlands
X-Envelope-to:  InfoTeX@aston.ac.UK
X-VMS-To:       UKTEX-SUBM
X-VMS-Cc:       BRAAMS
Comments:       This mail was sent by PMDF V3.1

 
    Hi,
 
        We're using Andrew Trevorrows PSdvi to print TeX on Postscript
        LN03S printers. We've encountered a problem with the handling
        of \special's.
        One of our users has a PostScript file with a bitmap in it.
        When he prints this file on a PostScript printer he get's the
        figure he wants on paper, but when he includes this file in a
        in a TeX-document, using the \special command (\special{file.ps})
        the text is put on paper correctly, but the contents of the included
        file disappear. They DO appear in the output from PSdvi though.
        What is happening here and how can I solve it?
 
        Please answer directly to me and I'll summarize for the list.
 
    Regards,
 
        Johannes Braams
 
PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams@pttrnl.nl

E-mail was :
    EARN/BITnet : BRAAMS@HLSDNL5   UUCP        : hp4nl!dnlunx!johannes
    SURFnet     : DNLTS::BRAAMS    INTERnet    : BRAAMS%HLSDNL5@CUNYVM.cuny.edu
 PSS (DATAnet1) : +204 1170358::BRAAMS

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

From:	CBS%UK.AC.EAN-RELAY::DE.DBP.UNI-HAMBURG.INFORMATIK.RZ::FRIESLAND 19-MAR-1990 16:20:53.91

Via: UK.AC.ASTON.MAIL; Mon, 19 Mar 90  16:20 GMT
Via: UK.AC.EAN-RELAY; Mon, 19 Mar 90  16:16 GMT
Received: from mhs-relay.ac.uk by Ean-Relay.AC.UK   via Ethernet with SMTP
           id aa07139; 19 Mar 90 16:08 GMT
X400-Received: by mta mhs-relay.ac.uk in /PRMD=uk.ac/ADMD= /C=gb/; Relayed;
               Mon, 19 Mar 90 16:07:34 +0000
X400-Received: by /PRMD=uni-hamburg/ADMD=dbp/C=de/; Relayed;
               Mon, 19 Mar 90 13:38:09 +0100
Date: Mon, 19 Mar 90 13:38:09 +0100
X400-Originator: friesland@de.dbp.uni-hamburg.informatik.rz
X400-Recipients: abbottp@uk.ac.aston
X400-MTS-Identifier: [/PRMD=uni-hamburg/ADMD=dbp/C=de/;900319133809]
X400-Content-Type: P2-1984 (2)
Content-Identifier: 520
From: Gerd Friesland <friesland@de.dbp.uni-hamburg.informatik.rz>
Message-ID: <520*friesland@rz.informatik.uni-hamburg.dbp.de>
Subject: DECWindows TeX-preview
Importance: Low
Sensitivity: Undefined (value=0)
Sender: friesland%de.dbp.uni-hamburg.informatik.rz@uk.ac.mhs-relay

dear peter,
Some months ago i gave you a DECWindows-preview for TeX, that a student
had written here based on Nelson Beebe's driver family. Have you heard
of any feedback on that software; is it used ?

The reason i ask is that we now have an improved version, which we
would like to substitute for the initial release -if it's being used-.


yours, Gerhard Friesland-Koepke

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

Originally-from:   CBS%UK.CO.INMOS::DES
 
has anyone got the spider web stuff in the aston archive to work -- to
my mind there's something missing -- either source files or perhaps
documentation to tell me what to do with what i've got or perhaps both!
in any case the README instructions rapidily result in make failing to
find awktangle. any pointers appreciated.

david shepherd
INMOS ltd

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

Via: UK.AC.ASTON.MAIL; Tue, 20 Mar 90  17:05 GMT
Via: UK.AC.SUNDERLAND-POLY.VAX1; Tue, 20 Mar 90  17:01 GMT
Date:           Tue, 20 Mar 90  16:57 GMT
From:           HS0PDU@UK.AC.SUNDERLAND-POLY.VAX1
Subject:        TeX

Can you send me advice/help on the TeX progs available?
My first requirement is for a Hewlett Packard LaserJet Plus (actually
a C.ITOH clone). This is for a IBM PC TeX implementation.
More generally I'd like to put up TeX/METAFONT on a variety of our
systems (I'm trying to encourage wide use of TeX here!)

Many Thanks
Peter Dunne (P_DUNNE(at)UK.AC.SUNDP.V1)

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

Originally-from:   CBS%UK.AC.CAMBRIDGE.COMPUTER-LAB::MAJ
 
I said that I would report back on the TeXPS package written by
Stephan v. Bechtolsheim.

First of all, the package definitely works, and does now support
A4 paper (you can even make it the default).  The program compiled
and ran with no changes needed on a DECsystem 5400.

Good points:

- The installation instructions, makefiles etc actually work.
- I have not had to change a single line of code.
- Lots of things are configurable from ONE file containing local
  dependencies. You can keep many independent sets of configuration
  options in the one file.
- The documentation is extensive.
- Ordinary users can tweak things like encoding vectors, font metrics
  etc without needing a guru to install anything.
- There is a clean way of modifying the AFM->TFM conversion process,
  by overriding defaults in a "PFD" file.
- GF, PK and PXL formats all supported for pixel fonts.
  
Bad points:

- The documentation is garrulous in places. The author is clearly
  not a native speaker of English.
- The configuration is a bit daunting at first, and you can't print
  out the documentation until you have made the package work.
- The PostScript output is rather hungry of VM in the PostScript
  interpreter.  I have sent svb a suggestion for an improvement in
  this area.
- I'm not sure about the mainline code, but the installation stuff
  solidly assumes Unix.
- A "big" LaTeX is needed to build the documentation, so this is
  not a package for small systems.

I am certainly going to have a go at using it as our main DVI to
PostScript converter (I'm about to pre-release to guinea-pig users).

It definitely ought to be in the archive, but I am not convinced
that it would be helpful to install it in the way other packages
are.  It comes as a compressed "tar" image plus a set of "patch"
files (currently there are two).  This whole mechanism is very
Unix dependent.  If you store the files in a VMS directory structure,
you will be doing Unix customers a disservice because:

- They will have to retrieve lots of small files.
- The filenames will be case-folded.
- File timestamps are lost.

The second problem is a major one for this package, since many
of the filetitles are in mixed case and need to be for the makefiles
to work.  (I had exactly this problem with one of the other converters
I picked up from Aston, but fortunately there was only one file
affected.  In TeXPS there would be dozens.)


Martyn Johnson
University of Cambridge Computer Lab

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

 
    Hi,
 
        Did you ever need a bold sans seriff font in LaTeX? Or any other
        CM-font that isn't normally available in LaTeX?
 
        Adding a font to LaTeX, and doing it in such a way that it changes
        size automatically, so that you don't need a different command for
        each point-size you want to have the font available in looks like
        a hard job. At first sight parts of lfonts.tex have to be redone.
 
        The style-file sfb.sty, which is included at the bottom of this
        message adds the command \sfb to LaTeX. It also takes care of
        redefinig internal LaTeX-commands to guarantee that \Large has
        the same effect on \sfb as it has on \sf.
 
    Regards,
 
        Johannes Braams
 
PTT Research Neher Laboratorium,        P.O. box 421,
2260 AK Leidschendam,                   The Netherlands.
Phone    : +31 70 3325051               E-mail : JL_Braams@pttrnl.nl
- ------------------------------------------------------------------------------
E-mail was :
    EARN/BITnet : BRAAMS@HLSDNL5   UUCP        : hp4nl!dnlunx!johannes
    SURFnet     : DNLTS::BRAAMS    INTERnet    : BRAAMS%HLSDNL5@CUNYVM.cuny.edu
 PSS (DATAnet1) : +204 1170358::BRAAMS
- ------------------------------------------------------------------------------
%
% File sfb.sty
% For use with LaTeX Version 2.09 dated 13 jun 1989
% Author : J.L. Braams (JL_Braams@pttrnl.nl)
% Date   : 21 mar 1990
% Version: 1.0
%
% Please direct bug-reports and other comments to:
%        Johannes Braams
%        PTT Research Neher Laboratories
%        P.O.box 421
%        2260 AK Leidschendam
%        The Netherlands
%        Tel.: +3170 3325051
%        Fax : +3170 3326477
%        Net : JL_Braams@pttrnl.nl
%
% This file defines a new font for LaTeX, the bold sans serif font.
% The command \sfb is defined and automatic size-changes are enable
% by adding a line of code to the commands \vpt etc. from lfonts.tex
%
% These fonts are loaded, the others are loaded on demand.
%
\font\tensfb  = cmssbx10
\font\elvsfb  = cmssbx10 \@halfmag   % bold sans serif
\font\twlsfb  = cmssbx10 \@magscale1 % bold sans serif
\font\frtnsfb = cmssbx10 \@magscale2 % bold sans serif
%\font\svtnsfb = cmssbx10 \@magscale3 % bold sans serif
%\font\twtysfb = cmssbx10 \@magscale4 % bold sans serif
%\font\twfvsfb = cmssbx10 \@magscale5 % bold sans serif
%+
%     A new family for the font
%-
\newfam\sfbfam
%+
%     and a protected font name
%-
\def\sfb{\protect\psfb}
%+
%    Size changing
%    We have to take care here, the goal is to add something to the
%    definition of commands like \vpt, \xpt, etc. In order to do this
%    the commands are redefined, in terms of themselves. To get this
%    right, the first level expansion is stored in a token register.
%    The definition for the command \psfb is also stored in a token
%    register for the same reason.
%    When the token-registers are filled the commands are redefined
%    globally, using \xdef.
%
%    First we start a group, to keep the use of the token registers local,
%    The define \vpt
%-
{\toks1={\@subfont\sfb\rm}
\toks0=\expandafter{\vpt}
\xdef\vpt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \vipt
%
\toks0=\expandafter{\vipt}
\xdef\vipt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \viipt
%
\toks0=\expandafter{\viipt}
\xdef\viipt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \viiipt
%
\toks0=\expandafter{\viiipt}
\xdef\viiipt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \ixpt
%
\toks0=\expandafter{\ixpt}
\xdef\ixpt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \xpt, from here on the contents of \toks1 will differ.
%    Also more is stored in it, apart from the definition-text of
%    \psfb
%
\toks0=\expandafter{\xpt}
\toks1={{\fam\sfbfam\tensfb}\textfont\sfbfam\tensfb
    \scriptfont\sfbfam\tensfb \scriptscriptfont\sfbfam\tensfb}
\xdef\xpt{\the\toks0\def\noexpand\psfb\the\toks1}
%
%    \xipt
%
\toks0=\expandafter{\xipt}
\toks1={{\fam\sfbfam\elvsfb}\textfont\sfbfam\elvsfb
    \scriptfont\sfbfam\tensfb \scriptscriptfont\sfbfam\tensfb}
\xdef\xipt{\the\toks0\def\noexpand\psfb\the\toks1}
%
%    \xiipt
%
\toks0=\expandafter{\xiipt}
\toks1={{\fam\sfbfam\twlsfb}\textfont\sfbfam\twlsfb
    \scriptfont\sfbfam\tensfb \scriptscriptfont\sfbfam\tensfb}
\xdef\xiipt{\the\toks0\def\noexpand\psfb\the\toks1}
%
%    \xivpt
%
\toks0=\expandafter{\xivpt}
\toks1={{\fam\sfbfam\frtnsfb}\textfont\sfbfam\frtnsfb
    \scriptfont\sfbfam\tensfb \scriptscriptfont\sfbfam\tensfb}
\xdef\xivpt{\the\toks0\def\noexpand\psfb\the\toks1}
%
%    \xviipt, from now on the fonts are loaded on demand
%
\toks0=\expandafter{\xviipt}
\toks1={\@getfont\psfb\sfbfam\@xviipt{cmssbx10\@magscale3}}
\xdef\xviipt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \xxpt
%
\toks0=\expandafter{\xxpt}
\toks1={\@getfont\psfb\sfbfam\@xxpt{cmssbx10\@magscale4}}
\xdef\xxpt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    \xxvpt
%
\toks0=\expandafter{\xxvpt}
\toks1={\@getfont\psfb\sffam\@xxpt{cmssbx10\@magscale5}}
\xdef\xxvpt{\the\toks0\def\noexpand\psfb{\the\toks1}}
%
%    Don't forget to close the group.
%
}

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

Via: UK.AC.CRANFIELD.RMCS; Wed, 21 Mar 90  20:51 GMT
Date:		Wed, 21 MAR 90 20:47:03 GMT
From:		TEX@UK.AC.CRANFIELD.RMCS
Subject:        TeXserver now permits wildcards in file requests
Actually-to:    <ABBOTTP@UK.AC.ASTON.TEX>
Sender:         JANET"TEX@UK.AC.CRANFIELD.RMCS" <TEX@UK.AC.CRANFIELD.RMCS>
Message-Id:     <00000CE5_0016D788.00934074DAACAD00$15_1@UK.AC.CRANFIELD.RMCS>
Acknowledge-to: RMCS TeX Account
Originally-to:  ABBOTTP
Originally-from:TEX          "RMCS TeX Account"
Mailer:         Janet_Mailshr V3.5 ( 13-OCT-1989 14:07:27 )
 
The TeXserver receipting interface has been enhanced so that it can now 
resolve wildcards in the specifications of files requested from it.

The usual VMS wildcards may be used:
   * (asterisk) represents 0 or more characters in a filename or filetype
   % (percent)  represents exactly one character position

Within directory specifications, an asterisk takes the above meaning to match
with any directory at that current level, whilst ... (three dots, an elipsis)
represents "the current directory and all subdirectories below it". 

If you specify a directory part in a files request (i.e. something enclosed in 
square brackets), this will be used, otherwise the default top-level archive 
directory [TEX-ARCHIVE] will be substituted.  You may, if you wish, refer to a 
subdirectory within the archive by omitting the TEX-ARCHIVE from a directory 
specification, provided you supply the square brackets and the leading dot.

As an example, earlier today I sent the following request to 
TeXserver@uk.ac.aston.tex:

---
tex@cran.rmcs
files
[.tex.new.vms]*.*
[tex.new]00files.txt

Shortly thereafter I received the following receipt from the TeXserver:

Date:           Wed, 21 Mar 90  20:37 GMT
From:           University of Aston TeX Archive mail server 
		<TEXSERVER@UK.AC.ASTON.VAX.KIRK>
To:             TEX@UK.AC.CRANFIELD.RMCS
Subject:        RE: your <000011D6_0016D788.00934072AFF84800$1_1@
		UK.AC.CRANFIELD.RMCS> - successful FILES

Your TeXserver request for FILES has been received
and validated.  The files following your return
address below will be sent.  If any files are
inaccessible, these will be listed at the end
of this message, preceded by a suitable warning.
---
tex@cran.rmcs
files
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]00FILES.TXT
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]00README.TXT
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]BIG-TRIP.CH
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]BUILD_TEX.CLD
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]DESCRIP.MMS
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX-BIGTEX.CH
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX-INITEX.CH
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX-TRIP.CH
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX.CH
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX.CLD
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]TEX.TEST_CLD
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]WEBMERGE.COM
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]WMERGE.C
$1$DUA14:[TEX-ARCHIVE.TEX.NEW.VMS]WMERGE.MMS
$1$DUA14:[TEX-ARCHIVE.TEX.NEW]00FILES.TXT

And the server has the appropriate expanded request in its queue for later 
batch processing --- now I must go off and stop it, because I don't really 
want all those files!

                               Brian {Hamilton Kelly}

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ JANET:     tex@uk.ac.cranfield.rmcs                                     +
+ BITNET:    tex%uk.ac.cranfield.rmcs@ac.uk                               +
+ INTERNET:  tex%uk.ac.cranfield.rmcs@nsfnet-relay.ac.uk                  +
+ UUCP:      ...!mcvax!rmcs.cranfield.ac.uk!tex                           +
+         OR ...!ukc!rmcs.cranfield.ac.uk!tex                             +
+ Smail:     School of Electrical Engineering & Science, Royal Military   +
+            College of Science, Shrivenham, SWINDON SN6 8LA, U.K.        +
+ Phone:     Swindon (0793) 785252 (UK), +44-793-785252 (International)   +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

------------------------
  
!!
!!   Files of interest 
!!      [tex-archive]000aston.readme           [tex-archive]000directory.list
!!      [tex-archive]000directory_dates.list   [tex-archive]000directory.size
!!      [tex-archive]000last30days.files
!!
!! Editor - I have a tape labelled TeX 2.99 LaTeX 2.09 Metafont 1.7
!! Unix 4.2/3BSD & System V. Tar 1600 bpi blocked 20 1 file dated 
!! 25 July 1989 (from washington.edu). 
!!
!!  FTP access site               uk.ac.aston.tex
!!             username           public
!!             password           public
!!
!! I have the facility to copy this tape for anyone who sends the following
!! 1 2400 tape with return labels AND RETURN postage. (2.50 pounds sterling 
!! for UK users, payable to `Aston University') Outside UK please ask me.
!! UK users send 4.25 for two tapes or 6.60 for three tapes. 
!! Send to
!!
!! P Abbott
!! Computing Service
!! Aston University
!! Aston Triangle
!! Birmingham B4 7ET
!!
!! A VMS backup of the archive requires 2 (two ) 2400' tapes at 6250bpi.
!! Remaining details as above.
!!  
!! A VMS backup of TeX 2.991 plus PSprint is available one tape is needed.
!!
!! Exabyte tape drive with Video 8 cassettes.
!! 
!! Same formats available as 1/2in tapes.  We use the following tapes
!! SONY Video 8 cassette  P5 90MP, MAXCELL Video 8 cassette P5-90
!! TDK Video 8 cassette P5-90MPB
!! Postage 35p UK (stamp please), 1 pound sterling Europe, other areas 2 pounds
!!
!! OzTeX - Send 10 UNFORMATTED (800k) disks with return postage.
!!
!!  Replies/submissions to            info-tex@uk.ac.aston   please
!!  distribution changes to   info-tex-request@uk.ac.aston   please 
!! 
!!   end of issue