TeXhax@cs.washington.edu (TeXhax Digest) (07/26/89)
TeXhax Digest Friday, July 14, 1989 Volume 89 : Issue 68
Moderators: Tiina Modisett and Pierre MacKay
%%% The TeXhax digest is brought to you as a service of the TeX Users Group %%%
%%% in cooperation with the UnixTeX distribution service at the %%%
%%% University of Washington %%%
Today's Topics:
***Announcing BibTeX v0.99c for MS-DOS***
Kern between `A' and `v' in cmr
Strange kern in cmr10
Pronunciation of TeX
Silicon Graphics TeX
LaTeX style for underlining with \em
LaTeX questions concerning vspace, two-column, footers
Previewers for TeX...
Toshiba ExpressWriter 301
-------------------------------------------------------------------
Date: Thu, 20 JUL 89 11:51:16 BST
From: TEX%rmcs.cranfield.ac.uk@NSFnet-Relay.AC.UK
Subject: BibTeX v0.99c for MS-DOS
Keywords: BibTeX v0.99c for MS-DOS
After several unanswered requests to TeXhax and UKTeX for a public domain
implementation of BibTeX v0.99 that would run on an IBM PC, I decided to
produce my own version. After several months of Beta testing at several
sites, the time for general release has come.
FEATURES
********
This implementation is a (hand) translation of the original WEB into C
suitable for the Borland Turbo C v2.0 compiler, emulating the behaviour of the
original WEB as closely as is practicable.
The MS-DOS environment variables TEXINPUTS and TEXBIB are used when searching
for style (.BST) files and database (.BIB) files respectively.
At startup, the amount of memory available is determined and the internal
arrays are sized accordingly. A usable BibTeX is now possible with as little
as 300kB of free memory.
The source code is available.
FILES DISTRIBUTED
*****************
Four files are distributed with this implementation, namely:
00README.TXT - A quick guide telling you how to get started.
BTXGUIDE.TEX - The LaTeX source for a user guide detailing this
implementation of BibTeX and how to install it.
BTX-ARC.EXE - A self-extracting archive containing all need to
get BibTeX up and running, including the program,
style files and documentation.
SRC-ARC.EXE - A self-extracting archive containing source code for
this implementation of BibTeX.
The files are bit too large for mailing (around 500kB after encoding), so
ideally, I'd like somebody to volunteer to make the files available for
anonymous FTP in the USA - any takers ?
Niel Kempson
| JANET: tex@uk.ac.cranfield.rmcs |
| BITNET: tex%uk.ac.cranfield.rmcs@ukacrl |
| INTERNET: tex%uk.ac.cranfield.rmcs@nsfnet-relay.ac.uk |
| Smail: School of Electrical Engineering & Science, Royal Military |
| College of Science, Shrivenham, SWINDON SN6 8LA, U.K. |
| Phone: Swindon (0793) 785687 (UK), +44-793-785687 (International) |
-------------------------------------------------------------------------
Date: Wed, 19 Jul 89 18:03:25 EDT
From: "Karl Berry." <karl%mote.umb.edu@RELAY.CS.NET>
Subject: Kern between `A' and `v' in cmr
Keywords: fonts, cmr, kern
When I wrote to Knuth about this, he said, essentially, ``Yes, there
should be a kern, but it's too late now.'' I think he is committed to
keeping the TFM files frozen. I'm not sure I agree with this decision,
but they're his fonts.
----------------------------------------------------------------------
Date: Wed, 19 Jul 89 16:01:49 CDT
From: hrp@boring.cray.com (Hal Peterson)
Subject: Strange kern in cmr10
Keywords: fonts, cmr10.pl
I bumped into this in cmr10.pl:
(CHARACTER C k
(CHARWD R 0.527781)
(CHARHT R 0.694445)
(COMMENT
(KRN C a R -0.055555)
(KRN C e R -0.027779)
(KRN C a R -0.027779)
(KRN C o R -0.027779)
(KRN C c R -0.027779)
)
)
Notice that "ka" has two different kerns. Why?
Hal Peterson Domain: hrp@cray.com
Cray Research Old style: hrp%cray.com@uc.msc.umn.edu
1440 Northland Dr. UUCP: uunet!cray!hrp
Mendota Hts, MN 55120 USA Telephone: +1 612 681 3145
---------------------------------------------------------------------------
Date: 19 Jul 89 08:44 GMT+0200
From: anne.brueggemann-klein@sun1.ruf.uni-freiburg.dbp.de
Subject: Pronunciation of TeX
Keywords: TeX, pronunciation
Three different ways to pronounce the 'X' in TeX
The problem with Knuth's instruction on the pronunciation
of TeX is that it is contradictory, at least for Germans.
Knuth claims that TeX should rhyme with Blech, with the
'ch' sounding like in the word ach. Unfortunately, the
pronounciation of 'ch' in these two German words is different.
The phonetic equivalent of 'ch' in blech is 'cedilla-c',
and it sounds "as in whispered 'huge', or 'yes' in
a prolonged forced whisper" (Cassell's German-English
dictionary), whereas the phonetic equivalent of 'ch'
in ach is 'x' as in the Scottish loch.
On top of that,
Knuth claims that TeX is a derivation of the Greek word
techne. The English language has derived the word
technique from techne, and the German language has
Technik. The phonetic equivalent of 'ch' in technique
is 'k', whereas the pronounciation of 'ch' in Technik
is 'cedilla-c' (the same as in Blech).
Empirical evidence on the pronounciation of TeX
From my experience, discussed with Rosemary Bailey in
Exeter, native English speakers pronounce the 'ch' in
TeX as 'k', like in technique, whereas German speakers
pronounce it as 'cedilla-c', like in Technik. At least
this holds for high German. Bavarians pronounce the
'ch' in Technik more like the 'x' in the Scottish loch.
Hence, their pronounciation of TeX, also derived from
Technik, is more acceptable
to North-American and British ears.
The status quo seems to be that everyone pronounces
TeX the same way they pronounce the Greek techne,
thus consistently following one of Knuth's
instructions.
Conclusion
We are lucky that few things in the TeXbook are so
confusing as the instructions on how to pronounce
TeX.
Anne Brueggemann-Klein
-------------------------------------------------------------------------
Date: Mon, 10 Jul 89 08:51:40 NZT
From: Russell Fulton <ccc032u@aucc1.aukuni.ac.nz>
Subject: Silicon Graphics TeX
Keywords: UNIX, MIPS 3000, Silicon Graphics, TeX
We are considering the purchase of a unix machine. One of the possibilities
is a Silicon Graphics machine based on the MIPS 3000 chip set. Does any body
have TeX running on such a machine? Does anybody have TeX and a previewer going
on one of their workstations?
Presumably the standard unix distribution with an x11 previewer will work but
I have been in this business long enough to know that what should be so is not
always so!. ( Just call me paranoid!)
Russell
Organisation: "Computer Centre, University of Auckland
Private Bag, Auckland, New Zealand"
telephone: "+64 9 737-999 X 8955 (GMT +12,nzt)"
fax: "+64 9 303-2467"
internet: "rj.fulton@aukuni.ac.nz"
-----------------------------------------------------------------------------
Date: Tue, 4 Jul 89 20:37 PDT
From: <ASND%TRIUMFRG.BITNET@UWAVM.ACS.WASHINGTON.EDU>
Subject: LaTeX style for underlining with \em
Keywords: LaTeX, underlining
In response to Vivian Harrington's request for an underlining style:
In order to underline text for submission to journals, I worked on
an underlining style. My first `brilliant' approach was to typeset
the underlined text as a separate paragraph and then piece together
the underlined lines with the preceding text. This was a miserable
failure because there was often not enough stretch left to give a
seamless junction. Here is my less-transparent but more-robust
effort:
%- - - - - - - - - - ULEM.STY - - - - - - - - - - - - - - - - - - -
%
% Style file to make \em turn on underlining until the end of the group.
% This is far from an ideal replacement for \em, but it does allow line
% breaks, and even primitive hyphenation, within the underlined text.
% Every word is set in an underlined box, so normally it cannot be hyphenated,
% but explicit discretionary hyphens (\-) can be used to allow hyphenation.
% Since spaces are used to delimit words, there may be some difficulty with
% syntactical spaces (e.g. 2.3_pt). Some effort is made to handle these, but
% they will cause problems if the last thing before the command with spaces
% is glue; e.g., "the \macro 2.3 pt end". This is almost never a problem
% because of braces...
%
% One important incompatability is with grouping: EVERYTHING IN BRACES IS
% TREATED LIKE AN MBOX. Thus braces will prevent linebreaks in the text they
% enclose. Moreover, the specially-taken-care-of commands \-, \ , and
% \hspace (\hskip) will fail if they appear inside extra braces. Thus, the
% only braces you should use are those delimiting parameters to commands, or
% those with simple text inside.
%
% Nested \em commands produce underlined italics, but heed the warnings
% about braces above. To get italics without underlining, use \it.
% Donald Arseneau 1989
\def\ULem{\let\em\LA@em\UL@on}
\def\UL@on{\expandafter\ULine\expandafter{\ifnum0=`}\fi}%% -> \ULine{
\let\LA@em\em
\let\em\ULem
\newbox\UL@hyphenbox
\newbox\UL@box
\newcount\UL@spfactor
\newcount\UL@penalty
\newskip\UL@skip
\newdimen\UL@lht
\newdimen\UL@ldp
\newdimen\UL@kern
\let\LA@space\ \let\LA@hskip\hskip
\def\UL@end*{\relax\relax}% something unlikely to be found elsewhere,
% but harmless
\def\ULine#1{\leavevmode\let\-\UL@dischyp \let\ \UL@space \let\hskip\UL@hskip
\everymath{\UL@hrest}%
\setbox\UL@box\hbox{(}\UL@ldp\dp\UL@box\UL@lht-\UL@ldp\advance\UL@lht.4\p@
\setbox\UL@hyphenbox\hbox{\setbox\UL@box\hbox{-}\UL@putbox}%
\UL@word#1\global\UL@spfactor\spacefactor{} \UL@end* }
\def\UL@start{\setbox\UL@box\hbox\bgroup\everyhbox{\UL@hrest}\let\UL@start\empty
\kern-3sp\kern3sp} % kerns so I can test for beginning of list
\def\UL@stop{\global\UL@penalty\lastpenalty
\ifdim\lastkern=3sp \egroup % Nothing in hbox,
\egroup\ifdim\wd\UL@box=\z@ % make doubly sure, and don't put on list
\else \UL@putbox \fi
\else
\egroup \UL@putbox
\fi}
\def\UL@putbox{\vrule height\UL@lht depth\UL@ldp width\wd\UL@box
\kern-\wd\UL@box \box\UL@box
\ifnum\UL@penalty=0 \else \penalty\UL@penalty \fi}
\def\UL@word#1 {\UL@start#1 \ifx\UL@end#1\egroup % must be entirely expandable
% outside ifs
\let\UL@word\egroup \unskip \unskip \unskip % remove extra leader
\spacefactor\UL@spfactor
\else % not finished
\ifmmode\else \ifdim\lastskip=\z@\else % this should allow syntactical
% spaces
\global\UL@skip\lastskip \unskip
\UL@stop \UL@leaders
\fi\fi
\fi \UL@word}
% with interword leaders, give some overlap to avoid gaps caused by
% round-off errors in the printing program. Needs 3 \unskips above.
\def\UL@leaders{{\@tempdima.003truein \advance \UL@skip 2\@tempdima
\LA@hskip-\@tempdima
\leaders\hrule height\UL@lht depth\UL@ldp\LA@hskip\UL@skip
\LA@hskip-\@tempdima}}
\def\UL@hskip{\UL@stop \afterassignment\UL@reskip \global\UL@skip}
\def\UL@reskip{\UL@leaders \UL@start}
\def\UL@hrest{\let\hskip\LA@hskip \let\ \LA@space \let\-\UL@dischyp}
\def\UL@space{\LA@space \global\UL@skip\lastskip \unskip \UL@stop \UL@reskip}
\def\UL@dischyp{\penalty\z@ % no penalty => no break (see \UL@stop)
\UL@stop \discretionary{\box\UL@hyphenbox}{}{}\UL@start}
\endinput
%
% HERE IS A DIFFICULT EXAMPLE
%
% \documentstyle[12pt,ulem]{article}
% \setlength\textwidth{3.3in}
% \begin{document}
% No, I did {\em not} act in the movie {\em {\em The}
% {\em Persecu}\-{\em tion} {\em and} {\em Assassination}
% {\em of Jean-Paul Marat}, as per\-formed by the Inmates
% of the Asylum of Charenton under the Direction of the
% Marquis de~Sade!} But I {\em did} see it.
% \end{document}
Donald Arseneau
asnd@triumfcl (.bitnet)
arseneau@mtsg.ubc.ca
-----------------------------------------------------------------------------
Date: Mon,10 Jul 89 10:28:06 BST
From: R.A.Reese%HULL.AC.UK@UWAVM.ACS.WASHINGTON.EDU
Subject: LaTeX questions concerning vspace, two-column, footers
Keywords: LaTeX, vspace, two-column, footers
I'm trying to set out a single page flysheet with two columns of text
but a full width head and foot. This has generated a number of
problems.
1) Standard LaTeX doesn't provide any mechanism for putting information
in a foot, apart from the page number. The LaTeX Manual says that the
TeX \foottext command is redundant, but does not indicate what replaces
it - footnotes do not, since footnotes appear on one page but I want a
running footer. This problem is general.
2) The following two page layouts are similar except for an identical
request to push down the text in each column. However the first example
causes the two columns both to be flush against the full width rule, but
the second pushes the left hand column down further than the right hand.
I thought it was caused by an elastic measure, but the top lines and
column-rules do not line up when I comment out \flushbottom.
a) What adds the extra point or two at the top of the left-hand
column?
b) What could I look at to find that out for myself? I'm not a
wizard and the log file contains no information.
I'm using TurboLaTeX provided by Kinch Computer, running on an Opus
PC clone. Output is by DVIALW (supplied by Kinch) or CDVI public
domain screen preview.
Example 1.
%----------
\documentstyle[a4,twocolumn]{article}
\pagestyle{empty}\nofiles\textheight 4in%for demonstration
\columnseprule=0.4pt
\oddsidemargin=0pt
\columnsep=30pt
\def\myhead{\Large\bf\parindent=0pt\relax}
%\flushbottom
\pretolerance=1000
\begin{document}
\twocolumn[\centerline{\Large Overall TITLE line
\today}\vspace{15pt}\hrule]
\vspace*{5pt}
{\parskip=0pt\myhead Column 1 head}
\hrule
This is Example 1..
This is the sort of text that will appear in the left hand column of this
two column sheet set up using standard LaTeX. There is the same
\verb/\vspace/ at the top of each column but they don't line up. Each
header is one line and is followed by an \verb/\hrule/ so these should also
line up.
\section*{}
{\myhead Still in the same column}
The hrule at the top extends the width of the page, but now in two column
mode an hrule only extends across the textwidth of one column.
\vfill
\hrule
\pagebreak
\vspace*{5pt}
{\parskip=0pt\myhead Column 2 head}
\hrule
The text in the second column is wanted to line up with the first column at
top, and also at bottom if \verb/\flushbottom/ is in effect. For some
reason the first column is dropped a few points despite \verb/\parskip/
being set to 0 and non-elastic.
I also would like a footer streching across both columns. The standard
page styles all force the footer to be empty---why can't LaTeX allow the
TeX \verb/\footertext/ command?
\vfill
\hrule
\onecolumn
\hrule\vspace{15pt}
\centerline{\Large This should be a footer}
\end{document}
Example 2
%---------
\documentstyle[a4,twocolumn]{article}
\pagestyle{empty}\nofiles\textheight 4in%for demonstration
\columnseprule=0.4pt
\oddsidemargin=0pt
\columnsep=30pt
\def\myhead{\Large\bf\parindent=0pt\relax}
%\flushbottom
\pretolerance=1000
\begin{document}
\twocolumn[\centerline{\Large Overall TITLE line
\today}\vspace{15pt}\hrule]
%\vspace*{5pt}
{\parskip=0pt\myhead Column 1 head}
\hrule
This is Example 2.
This is the sort of text that will appear in the left hand column of this
two column sheet set up using standard LaTeX. In this version the
\verb/\vspace/ at the top of each column is commented out. Each
header is one line and is followed by an \verb/\hrule/ so these should also
line up.
\section*{}
{\myhead Still in the same column}
\hrule
The hrule at the top extends the width of the page, but now in two column
mode an hrule only extends across the textwidth of one column.
\vfill
\hrule
\pagebreak
%\vspace*{5pt}
{\parskip=0pt\myhead Column 2 head}
\hrule
The text in the second column is wanted to line up with the first column at
top, and also at bottom if \verb/\flushbottom/ is in effect. For some
reason the first column is dropped a few points despite \verb/\parskip/
being set to 0 and non-elastic.
I also would like a footer streching across both columns. The standard
page styles all force the footer to be empty---why can't LaTeX allow the
TeX \verb/\footertext/ command?
\vfill
\hrule
\onecolumn
\hrule\vspace{15pt}
\centerline{\Large This should be a footer}
\end{document}
Any help would be appreciated. I need to set the flysheet this week,
so a very dirty solution is to make the left-column space smaller
(by trial and error), and to paste the footer on.
Allan Reese
R.A.Reese@hull.ac.uk Post: Computer Centre
JANET: R.A.Reese@uk.ac.hull | University of Hull
Internet: R.A.Reese%hull.ac.uk@cunyvm.cuny.edu | Hull HU6 7RX
EARN/BITNET: R.A.Reese%hull.ac.uk@UKACRL | UK
|Phone +44 482 465296
|FAX +44 482 466205
------------------------------------------------------------------------
Date: Wed, 19 Jul 89 16:59:42 CDT
From: Howard Meadows <BWCHTM@RESVAX.WEEG.UIOWA.EDU>
Subject: Previewers for TeX...
Keywords: information, previewers, DEC terminals, IBM-PC, CGA, VGA
I am a brand new TeX user (on a VAX/VMS system), and I'm interested
in obtaining any information anyone may have on any previewers that might
be available for DEC terminals, and IBM-PCs with CGA & VGA cards. One
terminal I'd specifically like to know about is DECs VCB02 Video Subsystem
that comes with their VaxStation 3500 series.
Please send any responses to BWCHTM@RESVAX.WEEG.UIOWA.EDU on the
Internet (128.255.64.129).
Thank You,
Howard Meadows
----------------------------------------------------------------------------
Date: Thu, 20 Jul 89 11:02 GMT
From: Peter Flynn UCC <CBTS8001%IRUCCVAX.UCC.IE@UWAVM.ACS.WASHINGTON.EDU>
Subject: Toshiba ExpressWriter 301
Keywords: printer, Toshiba ExpressWriter 301
Further to my last msg about this printer, if you use it with thermal
paper the results are excellent. I was using it with a thermal ribbon
and plain paper, which is why I got patchy output. Since I got thermal
paper (a pain, but worth it) I am impressed. Recommended.
Peter
-----------------------------------------------------------------------
%%% Further information about the TeXhax Digest, the TeX
%%% Users Group, and the latest software versions is available
%%% in every tenth issue of the TeXhax Digest.
%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%%
%%% BITNET: send a one-line mail message to LISTSERV@xxx
%%% SUBSCRIBE TEX-L <your name> % to subscribe
%%% or UNSUBSCRIBE TEX-L
%%%
%%% Internet: send a similar one line mail message to
%%% TeXhax-request@cs.washington.edu
%%% JANET users may choose to use
%%% texhax-request@uk.ac.nsf
%%% All submissions to: TeXhax@cs.washington.edu
%%%
%%% Back issues available for FTPing as:
%%% machine: directory: filename:
%%% JUNE.CS.WASHINGTON.EDU TeXhax/TeXhaxyy.nn
%%% yy = last two digits of current year
%%% nn = issue number
%%%
%%%\bye
%%%
End of TeXhax Digest
**************************
-------