UKTeX Digest Thu, 3 May 90 Volume 90 : Issue 14
From: uktex@uk.ac.aston
Reply-To: uktex@uk.ac.aston
Sender: JANET"uktex@uk.ac.aston" (UKTeX) <uktex@uk.ac.aston>
Subject: UKTeX Digest volume 90 number 14
Date: Thu, 3 May 90 14:44:42
Moderator: Peter Abbott
Submissions: uktex@uk.ac.aston
Administration: uktex-request@uk.ac.aston
Back Issues: These are stored in the Aston archive, in the directory
DISK$TEX:[TEX-ARCHIVE.DIGESTS.UKTEX.90]
Latest TeXhax #41
Back Issues: These are stored in the Aston archive, in the directory
DISK$TEX:[TEX-ARCHIVE.DIGESTS.TEXHAX.90]
Latest TeXmag V3 N4 (2 parts)
Back Issues: These are stored in the Aston archive, in the directory
DISK$TEX:[TEX-ARCHIVE.DIGESTS.TEX-MAG]
Today's Topics:
[uktex] addition to the archive for MSDOS & OS/2
[uktex] emTeX - caveat on texcad, and appeal for translator
[uktex] ILATEX and TIE in Aston Archive
[uktex] more notes on emTeX
emTeX in UK TeX archive (correction)
forwarded message from Eberhard Mattes
LaTeX on A4 Paper (2 msgs)
Modula-2 Compiler? (2 msgs)
PCTeX main memory problems (2 msgs)
TeX archive contribution
web2c-5_0a - problems (2 msgs)
----------------------------------------------------------------------
Date: Sat, 28 Apr 90 17:58:49 gmt
From: Sebastian Rahtz <spqr@uk.ac.soton.ecs>
Subject: [uktex] addition to the archive for MSDOS & OS/2
The Aston TeX archive has a new version of TeX for MSDOS and OS/2,
contributed by Eberhard Mattes from Stuttgart. This release comprises
*all* of TeX, Metafont, support programs (BibTeX, Makeindex, webware
etc), dvi drivers, previewer, and drawing package for LaTeX pictures
(texcad).
On the good side:
- there are separate binaries for normal MSDOS, for a 286 processor,
and for OS/2 protected mode
- the release has a full Metafont
- expanded memory is used if present
- there are `big' versions of TeX and Metafont; the former is a boon
for LaTeX users who load lots of extra macros (such as PiCTeX)
- the TeX is as fast as, if not faster than, sbTeX
On the down side:
- the documentation is all in German. And why not, you may ask? it
only matters to the uneducated among us!
- the printer drivers are for dot matrix and laser printers, but
*not* for PostScript
- I haven't tested the previewer or driver, as fonts are not
distributed (probably just as well), and I haven't sorted out the
documentation for what formats etc they want
- TeX 3.0 isn't available yet (but promised soon)
- the huge TeX is rather slow
If any or all of these apply to you:
- you have a reading knowledge of German
- you want TeX for OS/2
- you need a big TeX
- you need a fast free PC Metafont
then you should check out emTeX. On the whole, new users in the UK and
USA are probably better off getting Wayne Sullivan's excellent sbTeX,
now in TeX version 3.0, as it does nearly all you want and will be
simpler to set up.
The files are a set of BOO-encoded .zip archives in
[tex-archive.tex.msdos.emtex]
at Aston University. See regular note at the end of UkTeX for now to
retrieve files from Aston.
I append `Features.emtex'
Sebastian Rahtz
Der Autor von emtex beschreibt sein Programm wie folgt:
Vorteile (kein Anspruch auf Vollstaendigkeit)
- Komplettpaket, alles was man braucht, inklusive
sty-Dateien, Druckertreiber, Zeichensaetze usw. ist dabei.
- Volle Groesse (64 KWort) auch bei wenig DOS-Speicher,
da virtueller Speicher benutzt wird.
SB29TEX und MicroTeX z.B. bieten nur soviel
TeX-Speicher (main memory) wie Speicher frei ist.
- Es gibt bigTeX (262141 Speicherwoerter).
- Expanded Memory wird verwendet, falls vorhanden.
- Schnell. Vermutlich schneller als alle anderen
(bisher verglichen mit SB29TEX, publicTeX (Dante),
MicroTeX und PC-TeX 2.1).
- Relativ Fehlerfrei. Bei publicTeX funktioniert der
virtuelle Speicher nicht (zumindest bei der Version,
die auf der rusmv1 liegt). Zuverlaessig, da von
einer Maschine uebersetzt (es gibt tatsaechlich
Leute, die TeX aus dem Buch abgetippt und von Hand
in C uebersetzt haben).
- Ziemlich neue TeX-Version (2.99). Version 2.993
(3.0 sobald zwei Monate ohne Fehler) demnaechst.
- Umlaute und andere Sonderzeichen werden auf Wunsch
in die entsprechenden TeX-Sequenzen umgesetzt.
- METAFONT wird mitgeliefert.
- Recht gute Druckertreiber fuer Nadeldrucker
(z.Z. EPSON RX-80, FX-80, LQ-800; NEC P6, P7;
C.ITOH 8510A, Apple Imagewriter) und HP LaserJet+.
Leider noch kein PostScript-Treiber. Nadeldruckertreiber,
der sich an (fast) beliebige Nadeldrucker anpassen
laesst.
- Sehr guter Screen-Previewer (z.B. Darstellung mit
Graustufen bei Verkleinerung).
- Alle dvi-Treiber koennen Grafikdateien in den
Text einfuegen, ausserdem ist Liniengrafik moeglich.
- Alle Programme laufen auch unter OS/2 im protected Mode.
emTeX ist schneller und groesser als OS2TEX.
- Netzwerkfaehig.
- Zusatzprogramme wie MakeIndx und texchk werden mitgeliefert.
- MFjob, ein Programm zum bequemen Aufruf von METAFONT
wird mitgeliefert.
- Demnaechst wird TeXCAD mitgeliefert, ein Programm
zum interaktiven Entwerfen eines picture environments auf dem
Bildschirm (ich verhandle noch mit dem Autor).
- Fehler werden recht schnell beseitigt.
Nachteile (ohne Anspruch auf Vollstaendigkeit).
- Ziemlich viel Plattenplatz noetig, da ziemlich viel
mitgeliefert wird.
- Noch kein PostScript-Treiber.
Nochmal kurz der Vergleich mit anderen TeX-Versionen:
MicroTeX langsamer, weniger Speicher verfuegbar, nicht kostenlos.
PC-TeX Die einzige vertretbare Alternative, aber nicht kostenlos.
MuTeX Noch nicht verglichen (angeblich schlechter, mir
wurde aber nicht gesagt warum). Nicht kostenlos.
DOSTEX Noch nicht verglichen (vermutlich sehr viel langsamer).
publicTeX Langsamer, fehlerhaft.
OS2TEX Langsamer, weniger Speicher verfuegbar, nur OS/2.
SB29TEX Langsamer, um volle TeX-Speichergroesse zu haben,
muss das DOS ziemlich abgemagert werden.
TurboTeX Was ist das?
------
README und Changes in /soft/tex/emtex sind nicht auf dem neuesten Stand,
ich werde ihnen demn"achst neue Versionen zukommen lassen.
In der Hoffnung, da"s nicht noch mehr derart peinliche Fehler vorhanden
sind und die n"achste emTeX-Distribution erst bei TeX 3.0 f"allig wird
(das habe ich schon letztes Jahr gehofft),
Eberhard Mattes (mattes@azu.informatik.uni-stuttgart.de)
------------------------------
Date: Mon, 30 Apr 90 20:50:33 bst
From: Sebastian Rahtz <spqr@uk.ac.soton.ecs>
Subject: [uktex] emTeX - caveat on texcad, and appeal for translator
Two notes to follow up my posting announcing the availability of emTeX
in the UK TeX Archive:
a) `texcad', the interactive drawing package which generates LaTeX
picture commands, is not public domain but Shareware. I urge users
to respect this, and not to make extensive use without paying the
requisite fee to the author.
b) The authors are looking for a volunteer to translate the manual
for the dvi driver family from German into English; does any UK
TeX reader feel competent to translate a comprehensive technical
manual for the good of the community?
Sebastian Rahtz
------------------------------
Date: Wed, 2 May 90 21:30:57 bst
From: Sebastian Rahtz <spqr@uk.ac.soton.ecs>
Subject: [uktex] ILATEX and TIE in Aston Archive
Two additions to the archive have been supplied by Joachim Schrod
(with apologies for the delay in installation): ILATEX and TIE, for
making language-portable versions of LaTeX. They are in
[tex-archive.ilatex]
[tex-archive.tie]
and I append Joachim's README
Sebastian Rahtz
%---------------------------------------------------------
ILaTeX (International LaTeX) is a version of LaTeX where all fixed
strings which will be output by LaTeX have been replaced by macro
calls. These macros default to their American texts; style options
can be used to change this (e.g. to get texts in an other language).
ILaTeX is created by changing the LaTeX files, but these changes are
not done by hand. Instead there exist changefiles -- well known to
all WEB programmers -- which are merged in the original LaTeX files.
This is done by the TIE processor.
This distribution contains
1. the TIE processor,
2. the ILaTeX files -- ready for usage,
3. the original LaTeX files,
4. the ILaTeX changefiles to yield (2) from (3), and
5. additional documentation.
Please note that all stuff made by me or THD/ITI (i.e. TIE, the
changefiles, and part of the documentation) is copyrighted. It is
distributed under the conditions of the GNU General Public License
which you will find at prominent places in a file named COPYING. I
strongly sympathisize with the principles of the Free Software
Foundations although economical reasons often force me to sell
software (e.g. our drivers or our TeX system for the Atari ST) --
human beings must still have something to eat...
The files are delivered in two archives, named `tie' and `ilatex'.
The TIE processor will be placed in a directory tie, all ILaTeX-files
in a directory ilatex. At Aston these archives have been expanded into
the correct hierarchies.
I hope that you will find our stuff useful. If you have any problems
feel free to contact me. I prefer e-mail and I will acknowledge your
message within four days.
Joachim
current address:
Detig Schrod \TeX{}sys
Joachim Schrod
Kranichweg 1
D-6074 R\"odermark-Urberach
FR Germany
Bitnet: XITIJSCH@DDATHD21
Phone: (+6074) 1617
---
------------------------------
Date: Wed, 2 May 90 17:52:33 bst
From: Sebastian Rahtz <spqr@uk.ac.soton.ecs>
Subject: [uktex] more notes on emTeX
Two notes about the availablity of the emTeX package in the UK TeX
Archive:
a) Eberhard Mattes has sent me an English translation of the README
file. It stored as README.ENG.
b) My previous posting was probably misleading as I implied that the
package was lacking fonts. In fact Eberhard supplies a full set of
fonts for the drivers and previewer, it was just that I had not
installed them. They will be added shortly. Naturally you are
tioed in any way to particular drivers, so people with existing
TeX setups can carry on with whatever previewers and drivers they
already have, if they like
Sebastian Rahtz
------------------------------
Date: Sat, 28 Apr 90 18:02:27 gmt
From: Sebastian Rahtz <spqr@uk.ac.soton.ecs>
Subject: emTeX in UK TeX archive (correction)
further to my recent note about emTeX, I got the directory name wrong.
read
[tex-archive.tex.ms-dos.emtex]
instead of
`msdos'
Sebastian
------------------------------
Date: Thu, 3 MAY 90 09:28:21 BST
From: ARCHIVEGROUP@UK.AC.ASTON.VAXA
Subject: forwarded message from Eberhard Mattes
This might be of interest following my notes on emtex
------- Start of forwarded message -------
From: Eberhard Mattes <mattes@de.uni-stuttgart.informatik>
Date: Mon, 30 Apr 90 13:03:57 +0200
Dear Mr Rahtz,
- - readme.doc has been translated to English (by an American).
I hope dvidrv.doc is currently being translated (but I have
doubts). The big job (no volunteer found yet) is to translate
dvidrv.dvi. If you find someone, I shall send him/you the
newest version (the one for the next release---includes
virtual fonts and DeskJet support). tcman.dvi hasn't been
translated too.
- - I'll ask the author of TeXcad, whether he could give me the
source (the program is Shareware) or translate it himself.
- - I'll inform you of any updates. May 2, I'll start shipping
the test version of emTeX 3.0, METAFONT 2.0, and dvidrv
(via snail mail, I don't want to send it out to the world,
as the drivers are still under development). The final
release of the next emTeX distribution will take place
in some weeks.
- - Mr Wujastyk sent me dvitops (by James Clark).
Yours,
Eberhard Mattes (mattes@azu.informatik.uni-stuttgart.de)
------- End of forwarded message -------
------------------------------
Date: Fri, 27 APR 90 17:19:36 BST
From: Dave Love <FX@UK.AC.DARESBURY.NNGA>
Subject: LaTeX on A4 Paper
Aston TeX Archivists <Archivegroup@Uk.Ac.Aston.VaxA>
Originally-sent:Fri, 27 Apr 90 17:06 GMT
Originally-To: infotex@aston
Original-Ident: <27 APR 1990 17:06:56 FX@UK.AC.DARESBURY.NNGA>
Originally-from:Dave Love <FX@UK.AC.DARESBURY.NNGA>
The a4.sty and a4wide.sty in the archive are not satisfactory. For one
thing, they don't work properly with twosided printing. There is one
from Braams and Poppelier which is in print in TUGboat, it seems, which
is pretty good. I will forward it for the archive. The one thing it
doesn't do right IMHO is twocolumn. I have another, otherwise very
similar, version which does but which the Dutch version beat to TUGboat.
It's about time there was a definitive a4.sty in the archive!
------------------------------
Date: Fri, 27 APR 90 18:21:28 BST
From:
Subject: LaTeX on A4 Paper
Dave Love <FX@UK.AC.DARESBURY.NNGA> writes
> The a4.sty and a4wide.sty in the archive are not satisfactory. For one
> thing, they don't work properly with twosided printing. There is one
> from Braams and Poppelier which is in print in TUGboat, it seems, which
> is pretty good. I will forward it for the archive. The one thing it
> doesn't do right IMHO is twocolumn. I have another, otherwise very
> similar, version which does but which the Dutch version beat to TUGboat.
> It's about time there was a definitive a4.sty in the archive!
On the contrary IM not so HO, having prepared many styles for A4
format documents, there can be no such thing as a definitive (or even
canonical) A4.STY, as is clearly demonstrated by the phrases "not
satisfactory" and "doesn't do right" above: presumably the H authors
of those files do not agree with Dave.
The archive would welcome Dave's A4.STY but will not endow it
with the description "definitive".
Chris Rowley
on behalf of The Archive Group
------------------------------
Date: Tue, 1 May 90 11:30:55 BST
From: Michael Elphick <M.J.Elphick@uk.ac.newcastle>
Subject: Modula-2 Compiler?
The OzTeX User Guide distributed with the latest version 1.2 of OzTeX
(which is such an excellent product -- thanks to all involved in its
creation and dissemination) refers to
"the Modula compiler used to develop OzTeX ... (freely available)".
Could you tell me:
(a) Is this compiler now in the public domain?
(b) Is this compiler available from Aston's archives?
(c) Will it run as a normal application (i.e. do I need MPW)?
+--------------------------------+
| Michael Elphick | Room 323 |
|--------------------------------|
| 'Phone 091-222-7983 |
+--------------------------------+
------------------------------
Date: Tue, 1 May 90 17:03 BST
From: Peter Abbott - Computing Service <ABBOTTP@UK.AC.ASTON.VAX.SPOCK>
Subject: Modula-2 Compiler?
P_ABBOTT@UK.AC.ASTON.VAXA
Subject: RE: Modula-2 Compiler?
>From: Michael Elphick <M.J.Elphick@uk.ac.newcastle>
>Subject: Modula-2 Compiler?
>
> The OzTeX User Guide distributed with the latest version 1.2 of OzTeX
(which is such an excellent product -- thanks to all involved in its
>? creation and dissemination) refers to
>
> "the Modula compiler used to develop OzTeX ... (freely available)".
>
> Could you tell me:
>
> (a) Is this compiler now in the public domain?
>
> (b) Is this compiler available from Aston's archives?
>
> (c) Will it run as a normal application (i.e. do I need MPW)?
>
(a) I have been informed that it is NOT and asked to remove from the
distribution kit.
(b) Sorry No.
(c) Pass - All I know is that Andrew used MPW at Aston when developing the
latest version.
Peter
------------------------------
Date: Thu, 3 MAY 90 09:20:36 BST
From: Mike Piff <PM1MJP @ UK.AC.SHEFFIELD.PRIMEA>
Subject: PCTeX main memory problems
Aston TeX Archivists <Archivegroup@Uk.Ac.Aston.VaxA>
Originally-sent:Wed, 02 May 90 11:33:36
Originally-To: infotex @ ASTON
Originally-from:Mike Piff <PM1MJP @ UK.AC.SHEFFIELD.PRIMEA>
X-Serial: 00000009
------------------------------------------------------------------------------
From Dr M. J. Piff, Department of Pure Mathematics, University of Sheffield,
The Hicks Building, Hounsfield Road, SHEFFIELD S3 7RH, England.
Tel. SHEFFIELD(0742) 768555 Extension 4431.
JANET PM1MJP@UK.AC.SHEF.PA or PM1MJP@UK.AC.SHEF.IBM
------------------------------------------------------------------------------
A colleague is having difficulties with PCTeX running out of main memory at a
ridiculously early stage, with LOG's such as
! TeX capacity exceeded, sorry [main memory size=65535].
***usual rude messages***
Here is how much of TeX's memory you used:
58 strings out of 2672
318 string characters out of 22967
22794 words of memory out of 65535
962 multiletter control sequences out of 3000
14794 words of font info for 50 fonts, out of 18492 for 127
14 hyphenation exceptions out of 307
11i,15n,13p,95b,65s stack positions out of 200i,40n,60p,1024b,600s
whilst other versions of TeX appear not to crash. He is drawing simple
diagrams, and compared with what LaTeX on the PC is capable of, the amount on a
page is trivial.
After a lot of work, I have isolated a short file which illustrates the way our
version of PCTeX runs out of memory. The macro \br has been changed by me to
its new form. My colleague's original version is commented out, but that
crashes a lot sooner.
I should be interested in the views of anyone with an intimate knowledge of
either PCTeX or of the way main memory is/should be used. Also, why are none
of the limits in the LOG file exceeded, yet PCTeX claims to be out of memory?
Mike Piff
%PLAIN TEX FILE
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\newcount\brcount
\def\br{{-}\mkern-3mu}% \def\br{-\!\!\!} %***is even more fragile***
\def\barlen#1{\brcount0 \loop\advance\brcount1 \br\ifnum\brcount<#1\repeat}
\def\vvlra{\hbox{$\,\barlen{15}{\longrightarrow}\,$}}
\def\llgpd{\mathrel{\lower1pt\rlap{$\vvlra$}\raise2pt\hbox{$\mkern5mu \vvlra$}}}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%test program
\newcount\ct \ct0
\loop
\advance\ct1 %
\message{\the\ct}%
\rlap{$\llgpd$}%
\ifnum\ct<1000
\repeat
\bye
------------------------------
Date: Thu, 3 MAY 90 13:49:08 BST
From:
Subject: PCTeX main memory problems
while the failure of pcTeX is very interesting, surely
this is the responsibility of (a) the dealer (who i guess
is ewart north) and (b) pc TeX themselves. or is the
subtext a `don't use pcTeX' message. clarify.
!this is not archivegroup material! it might be uktex!
malcolm
------------------------------
Date: Fri, 27 Apr 90 17:10 GMT
From: Dave Love <FX@UK.AC.DARESBURY.NNGA>
Subject: TeX archive contribution
Here is the Dutch a4.sty which I referred to in message I just sent to
infotex. I think it should replace the latex.contrib]a4.sty, but I
guess that would make it inconsistent with Clarkson.
\def\fileversion{1.2}
\def\filedate{26 Feb 90}
\def\docdate {26 Feb 90}
%
%% \CheckSum{134}
%% \CharacterTable
%% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
%% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
%% Digits \0\1\2\3\4\5\6\7\8\9
%% Exclamation \! Double quote \" Hash (number) \#
%% Dollar \$ Percent \% Ampersand \&
%% Acute accent \' Left paren \( Right paren \)
%% Asterisk \* Plus \+ Comma \,
%% Minus \- Point \. Solidus \/
%% Colon \: Semicolon \; Less than \<
%% Equals \= Greater than \> Question mark \?
%% Commercial at \@ Left bracket \[ Backslash \\
%% Right bracket \] Circumflex \~ Underscore \_
%% Grave accent \` Left brace \{ Vertical bar \|
%% Right brace \} Tilde \%}
%%
%
%\iffalse
% Style option `A4' to be used with LaTeX V2.09
%
% Please report errors to: J.L. Braams
% JL_Braams@pttrnl.nl (Braams@hlsdnl5.bitnet)
% or: N.A.F.M. Poppelier
% Poppelier@hutruu53.bitnet}
%
% \changes{v1.0}{10 Jan 90}{Changed the margins for one-sided printing}
% \changes{v1.1}{23 Jan 90}{Added \WideMargins macros}
% \changes{v1.2}{26 Feb 90}{Consolidated setting of \marginparwidth}
%
%\fi
%
% \title{A style option to adapt the standard \LaTeX\ document
% styles to A4 paper\thanks{This file
% has version number \fileversion --
% last revision \filedate, documentation dated \docdate.}}
%
% \author{Nico Poppelier}
% \address{\TeX nique \\
% Washingtondreef 153\\
% 3564 KD Utrecht}
% \netaddress{Poppelier@hutruu53.bitnet}
% \author{Johannes Braams}
% \address{PTT Research Neher Laboratories\\
% P.O. Box 421\\
% 2260 AK Leidschendam}
% \netaddress{JL_Braams@pttrnl.nl}
%
% \date{Printed \today}
%
% \maketitle
%
% \begin{abstract}
% This article describes a new style option that can be used with the
% document styles that are distributed with the \LaTeX\ distributions.
% It modifies the page layout to conform to the paper format most
% commonly used in Europe, portrait A4.
% \end{abstract}
%
% \section{Introduction}
%
% This file is based on the document style options \verb+A4.sty+ and
% \verb+A4wide.sty+, which can be found in the Rochester style archive.
% The original style option \verb+A4.sty+ we started from was written by
% John Pavel, and is dated May 1987. This option only changes the vertical
% size of the text somewhat, by increasing the number of lines on a page.
% The style option \verb+A4wide.sty+ was written by Jean-Francois Lamy,
% and is dated July 1986. This option only increases the width of the text.
%
% \section{Goals and design decisions}
%
% As many people before us, we found the page layout as implemented in the
% standard \LaTeX\ document styles too much geared towards the
% American-sized paper, which is somewhat wider than A4 paper, but also
% noticeably less high.
%
% Our goal was to get a page layout that was suitable for A4 paper, and
% produced legible texts. There are a number of layout parameters that
% influence the legibility of a text. A parameter of major importance is
% the number of words (or characters) on a line. The maximum number of
% words per line is ten to twelve for optimal legibility, a rule-of-thumb
% that can be found in typographic literature (we used%\cite{treebus}).
% This results in a number of characters per line which lies somewhere
% between sixty and seventy.
%
% Another important parameter is the amount of white space surrounding the
% text. Here we have to distinguish between texts that are printed
% one-sided and texts that are printed two-sided (back to back). In the
% first case the margins on odd and even pages should be equal; in the
% latter case care should be taken that the texts on both sides of the
% paper overlap.
% Also a printed document is likely to be bound some way or another, so
% there should be enough white space in the `inner' margin\footnote{For
% two-sided printing, this is the left margin on odd-numbered pages and the
% right margin on even-numbered ones; for one-sided printing, this is
% always the left margin.} of the text to allow this.
%
% There is yet one more thing to take into account when designing a page
% layout. \LaTeX\ offers the possibility of using marginal notes and if
% someone wants to use marginal notes, they should of course fit on
% the paper.
%
% So, we have the following goals:
% \begin{enumerate}
% \item Choose the text width such that there will be sixty to seventy
% characters on a line;
% \item See to it that in documents that are printed two-sided, the
% texts which end up on two sides of one sheet of paper overlap;
% \item Leave enough white space in the `inner' margin to allow for
% the binding of the document;
% \item Leave enough white space in the `outer' margin
% for marginal notes if they are going to be used.
% \end{enumerate}
%
%
% \section{The implementation}
%
% \subsection{The starting point}
%
% Thus we set out to modify some of the design decisions in the standard
% document styles. Because we knew that we were not the first to tackle
% the problem, we started by having a look at what was already available.
% We came up with the two options mentioned earlier, which are publicly
% available. Undoubtedly there will exist many more such files, some of
% them maybe modifications of those two files.
%
% We had a look at the layout produced by both options and were not
% satisfied with it. For one thing, both of the original options \verb+A4+
% and \verb+A4wide+ modify only one aspect of the page layout. The first
% thing to do was to put these two files together. This resulted in a
% layout which was still unsatisfactory, since for the 10-point and
% 11-point options lines in the text contained on the average eighty
% characters or more.
%
% \subsection{What else?}
%
% \DescribeMacro\textwidth
% \DescribeMacro\marginparwidth
% Because the result so far gave us lines that contained too many
% characters, we decreased the \verb+\textwidth+ to get lines that
% contain about sixty to seventy characters for all three size options.
% Still more work had to be done. As it turned out, using our new
% \verb+A4.sty+ together with the option \verb+twosided+ had a drawback:
% when the document was printed two-sided the texts on both side of one
% piece of paper overlapped only partly, which does not look good. We
% solved this by modifying the width of the margins for two-sided
% printing. At the same time we modified the \verb+\marginparwidth+ so
% that if someone uses a marginal note it would completely fit on the
% paper instead of falling off the page, which obviously would render
% the note unreadable.
%
% \DescribeMacro\WideMargins
% The decisions described above allow for marginal notes to be printed
% along with the normal text, but if someone makes heavy use of marginal
% notes, the resultant layout will not be very satisfactory, because if
% the full width of the marginal notes is used, they will take up too
% much space in the `outer' margin. For this case we provide the macro
% \verb+\WideMargins+. This macro modifies the page-layout parameters in
% such a way that the width reserved for marginal notes becomes 1.5
% inches. To achieve this the width of the main body of the text is
% decreased. This macro is meant to be used only in the preamble of the
% document.
%
%\StopEventually{
% \section{Conclusion}
%
% We have presented a new approach to adapt the page layout of the
% document styles that are part of the standard \LaTeX\ distributions to
% the dimensions of A4 paper. The width of marginal notes has been taken
% into account and a means to get wider marginal notes at the cost of
% shorter lines in the main body of the text has been provided.
%
% \begin{thebibliography}{9}
% \bibitem{treebus} K.F. Treebus.
% {\em Tekstwijzer, een gids voor het grafisch verwerken van tekst.}
% SDU Uitgeverij ('s-Gravenhage, 1988). A Dutch book on layout
% design and typography.
% \end{thebibliography}
%
% \makesignature
% }
%
% \subsection{The code}
%
% We begin by identifying the version of this file on the terminal and
% in the transcript file.
% \begin{macrocode}
\typeout{Style option `A4' \fileversion\space<\filedate> (NP and JLB)}
\typeout{English documentation\space\space\space<\docdate> (JLB)}
% \end{macrocode}
%
% \begin{macro}{\topmargin}
% First, we redefine the \verb+\textheight+ and \verb+\topmargin+. The
% \verb+\topmargin+ is the distance from the reference point on the page
% to the top of the page of text. In most cases extra white space is not
% necessary since one inch of white space at the top of the page suffices.
% \begin{macrocode}
\topmargin 0pt
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\textheight}
% The dimension parameter \verb+\textheight+ gives the total height of the
% text, including footnotes and figures, excluding the running head and
% foot. This height is given as an integral number times the
% \verb+\baselineskip+, which results in an integral number of lines on a
% page.
%
% \noindent
% We have to include definitions of all relevant dimension parameters for
% each of the cases 10-point, 11-point and 12-point. We do this with a
% case statement:
%
% \begin{macrocode}
\ifcase \@ptsize
\textheight 53\baselineskip
% \end{macrocode}
% \noindent
% which modifies the height of the text for texts to be produced
% with the ten-point typeface:
% \begin{macrocode}
\or
\textheight 46\baselineskip
% \end{macrocode}
% \noindent
% the same for eleven point:
% \begin{macrocode}
\or
\textheight 42\baselineskip
% \end{macrocode}
% \noindent
% and for twelve point. Finally we close the \verb+\ifcase+ statement:
% \begin{macrocode}
\fi
% \end{macrocode}
%
% \noindent
% The only thing left to be done is to add the \verb+\topskip+ to
% the \verb+\textheight+.
% The value of \verb+\topskip+ appears always to be 10pt.
%
% \begin{macrocode}
\advance\textheight by \topskip
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\textwidth}
% \begin{macro}{\oddsidemargin}
% \begin{macro}{\evensidemargin}
% That was the `vertical part' of the work. Now we have some work to do
% to get things right horizontally. Again we have to distinguish between
% the various character sizes because sixty eleven-point characters take
% up more space than sixty ten-point characters. But there's more to
% take into account. If documents are printed two-sided, the texts on
% both sides of the paper should overlap completely. This can be done be
% assigning appropriate values to \verb+\oddsidemargin+ and
% \verb+\evensidemargin+, the parameters that define the left margins on
% odd and even pages respectively.
%
% \noindent
% First we start a case statement to distinguish between the various
% typeface sizes.
% \begin{macrocode}
\ifcase \@ptsize
% \end{macrocode}
% Then we specify the width of the text.
% \begin{macrocode}
\textwidth 5.00in
% \end{macrocode}
% \noindent
% Also specify the width of marginal notes. They must have a
% reasonable width to be of any use, and this should be the same for
% either one-sided or two-sided printing.
% \begin{macrocode}
\marginparwidth 1.00in
% \end{macrocode}
% \noindent
% Here we need an if statement to test whether the option \verb+twosided+
% has been specified.
% \begin{macrocode}
\if@twoside
% \end{macrocode}
% \noindent
% If it was, assign appropriate values to the margin parameters
% \begin{macrocode}
\oddsidemargin 0.55in
\evensidemargin 0.75in
\else
% \end{macrocode}
% \noindent
% If the option \verb+twosided+ was not used, both margin parameters
% must have the same value, for texts on consecutive pages have to
% be put in the same place on the paper.
% \begin{macrocode}
\oddsidemargin 0.55in
\evensidemargin 0.55in
% \end{macrocode}
% \noindent
% Now we close the if statement.
% \begin{macrocode}
\fi
% \end{macrocode}
% \noindent
% We are ready with the modifications for the ten-point typeface size, so
% now we do something similar for the eleven-point typeface.
% \begin{macrocode}
\or
\textwidth 5.20in
\marginparwidth 1.00in
\if@twoside
\oddsidemargin 0.45in
\evensidemargin 0.65in
\else
\oddsidemargin 0.45in
\evensidemargin 0.45in
\fi
% \end{macrocode}
% \noindent
% One more time, now for the twelve-point typeface.
% \begin{macrocode}
\or
\textwidth 5.70in
\marginparwidth 0.80in
\if@twoside
\oddsidemargin 0.20in
\evensidemargin 0.40in
\else
\oddsidemargin 0.20in
\evensidemargin 0.20in
\fi
% \end{macrocode}
% \noindent
% Finally we close the case statement.
% \begin{macrocode}
\fi
% \end{macrocode}
% \end{macro}
% \end{macro}
% \end{macro}
%
% \begin{macro}{\WideMargins}
% This macro is somewhat tricky: it has to find out
% which typeface size is used, whether the document should be printed
% two-sided, and whether the \verb+\reversemarginpar+ is in effect.
% \verb+\reversemarginpar+ makes the marginal notes appear in the
% margin on the opposite side of the normal placement.
% \begin{macrocode}
\def\WideMargins{%
% \end{macrocode}
% \noindent
% Because for each typeface size the changes to the parameters that
% need to be made are similar, the macro \verb+\WideMargins+
% uses an internal macro \verb+\@widemargins+.
%
% \begin{macro}{\ExtraWidth}
% In order to store the amount of extra width needed for the marginal
% notes an extra dimension parameter is defined.
%
% \begin{macrocode}
\newdimen\ExtraWidth
% \end{macrocode}
% \end{macro}
%
% \noindent
% First find out about the point size, then call \verb+\@widemargins+ to
% modify the margin widths by the amount given in \verb+\ExtraWidth+.
% \begin{macrocode}
\ifcase \@ptsize
% \end{macrocode}
%
% \noindent
% For both 10-point and 11-point texts the width for marginal notes is
% already 1 inch, so we increase it by half an inch. We subtract half an
% inch from the text width and modify the margins appropriately.
%
% \begin{macrocode}
\ExtraWidth = 0.5in
\@widemargins
\or
\ExtraWidth = 0.5in
\@widemargins
\or
% \end{macrocode}
%
% \noindent
% For 12-point texts the marginal notes are only 0.8 inch wide, so
% now we have to add 0.7 inch to get them 1.5 inch wide.
%
% \begin{macrocode}
\ExtraWidth = 0.7in
\@widemargins
% \end{macrocode}
%
% \noindent
% This macro should only be called once, during the preamble of a
% document, so we \verb+\let+ it be equal to \verb+\relax+ as soon
% as the work is done.
% \begin{macrocode}
\fi\let\WideMargins\relax\let\@widemargins\relax}
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\@preamblecmds}
% We add \verb+\WideMargins+ to \verb+\@preamblecmds+, which is a
% list of commands to be used only in the preamble of a document.
%
% \begin{macrocode}
{\def\do{\noexpand\do\noexpand}
\xdef\@preamblecmds{\@preamblecmds \do\WideMargins}
}
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\@widemargins}
% This macro modifies the margin parameters. To do this it uses
% the dimension variable \verb+\ExtraWidth+, which was defined by
% \verb+\WideMargins+.
%
% \noindent
% First the \verb+\ExtraWidth+ is subtracted from the \verb+\textwidth+
% and added to the \verb+\marginparwidth+.
% \begin{macrocode}
\def\@widemargins{%
\global\advance\textwidth by -\ExtraWidth
\global\advance\marginparwidth by \ExtraWidth
% \end{macrocode}
%
% \noindent
% Then we modify the margins, but the value of the switch
% \verb+\if@twoside+ has to be taken into account. Because
% we have to test another switch (\verb+\if@reversemargin+)
% we add another level of macros to modify the margin parameters%
%
% \begin{macrocode}
\if@twoside
\tw@sidedwidemargins
\else
\@nesidedwidemargins
\fi}
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\tw@sidedwidemargins}
% Normally the marginal notes are printed in the `outer' margins, so
% we have to increase the \verb+\evensidemargin+ to keep the text
% balanced on both sides of the paper, but if \verb+\reversemarginpar+
% is in effect we have to increase the \verb+\oddsidemargin+ and
% decrease the \verb+\evensidemargin+ accordingly.
%
% \begin{macrocode}
\def\tw@sidedwidemargins{%
\if@reversemargin
% \end{macrocode}
%
% \noindent
% Notice that for documents printed two-sided, the
% \verb+\evensidemargin+ is wider than the \verb+\oddsidemargin+;
% this difference in width is transferred to the other margin.
%
% \begin{macrocode}
\@tempdima=\evensidemargin
\advance\@tempdima by -\oddsidemargin
\advance\oddsidemargin by \ExtraWidth
\advance\oddsidemargin by \@tempdima
\advance\evensidemargin by -\@tempdima
\else
% \end{macrocode}
%
% \noindent
% If the marginal notes go on the normal side of the paper, only the
% \verb+\evensidemargin+ has to be increased.
%
% \begin{macrocode}
\advance\evensidemargin by \ExtraWidth
\fi}
% \end{macrocode}
% \end{macro}
%
% \begin{macro}{\@nesidedwidemargins}
% For documents that are printed one-sided, both margins have the same
% width. The default placement for the marginal notes is in the right
% margin, so if \verb+\reversemarginpar+ is {\em not\/} in effect the
% margin parameters need not be modified. If it is in effect, both the
% \verb+\oddsidemargin+ and the \verb+\evensidemargin+ need to be
% increased.
%
% \begin{macrocode}
\def\@nesidedwidemargins{%
\if@reversemargin
\advance\oddsidemargin by \ExtraWidth
\advance\evensidemargin by \ExtraWidth
\fi}
% \end{macrocode}
% \end{macro}
%
% \Finale
\endinput
------------------------------
Date: Tue, 1 MAY 90 19:18:48 BST
From: Ze'ev Shtadler <steed@EARN.TECHUNIX>
Subject: web2c-5_0a - problems
Aston TeX Archivists <Archivegroup@Uk.Ac.Aston.VaxA>
Originally-sent:Tue, 1 May 90 21:05:10 +0300
Originally-To: CS1CWM@UK.AC.SHEFFIELD.PRIMEA, Aston TeX Archivists <Archivegroup@
Original-Ident: <9005011805.AA02421@techunix.bitnet>
Originally-from:Ze'ev Shtadler <steed@EARN.TECHUNIX>
> On Apr 19, 10:56, ARCHIVEGROUP@UK.AC.ASTON.VAXA wrote about
> "web2c-5_0a - problems":
> Peter:
>
> Seeing Sebastian's note, I downloaded web-5_0a and web2c-5_0a to our Sun 3/60
.
>
> I have had some problems getting it going and it has just given up while tryi
ng
> to compile Metafont (INIMF).
>
> The problems are these:
>
> 1) tangle: there doesn't appear to be a tangle.h in the distribution, I
> eventually downloaded one from the old distribution (??)
>
> 2) TeX: in compiling itex.c it gave the warning "statement not reached" for
> lines 705 733 2102 and 2805. In compiling tex0.c it gave the same warnin
g
> at line 653.
>
> 3) Metafont: in compiling imf.c it gave the error "syntax error at or near
> symbol ;" at line 273 and the "statement not reached" warning at line 42
0.
> The code it complains of is
>
> dumpint ( strstart [ k ] ) ;
> while ( k++ < for_end) ; }
>
> (this is hand-transcribed and may not be absolutely accurate).
>
> The alterations to the top-level makefile are
> CC=cc
> and choosing sunlib instead of X11
>
> I know a little about C and it looks as though the syntax error is spurious.
It's a syntax error if dumpint if #defined to be a block (as it is
on out BSD4.3 VAX (old version of MF). try "cc -E imf.c > new.imf.c"
(or /lib/cpp) and look at the output of the preprocessor. I guess
you'll find something like:
{ ... } ;
while (k++ < for_end);
and that is not pure C ...
This is a result of a bug (?) in web2c that does not enclose the body
of the original for loop inside curly brackets. If you are interested
I'll try to dig the change I made to web2c and send you. As a
temporary fix, change
dumpint ( strstart [ k ] ) ;
to
{ dumpint ( strstart [ k ] ) ; }
>
> Chris Martin
Ze'ev.
--
Ze'ev Shtadler. ARPANET: steed%techunix.bitnet@cunyvm.cuny.edu
Computer Science Faculty, UUCP: ...!psuvax1!techunix.bitnet!steed
Technion, Israel Institute of Technology, BITNET: steed@techunix
Haifa Israel Domain: steed@techunix.technion.ac.il
Phone (work): (+972) 4-294304 CSNET: steed%techunix.bitnet@csnet-relay.csnet
------------------------------
Date: Tue, 1 MAY 90 19:18:48 BST
From: Ze'ev Shtadler <steed@EARN.TECHUNIX>
Subject: web2c-5_0a - problems
Aston TeX Archivists <Archivegroup@Uk.Ac.Aston.VaxA>
Originally-sent:Tue, 1 May 90 21:05:10 +0300
Originally-To: CS1CWM@UK.AC.SHEFFIELD.PRIMEA, Aston TeX Archivists <Archivegroup@
Original-Ident: <9005011805.AA02421@techunix.bitnet>
Originally-from:Ze'ev Shtadler <steed@EARN.TECHUNIX>
> On Apr 19, 10:56, ARCHIVEGROUP@UK.AC.ASTON.VAXA wrote about
> "web2c-5_0a - problems":
> Peter:
>
> Seeing Sebastian's note, I downloaded web-5_0a and web2c-5_0a to our Sun 3/60
.
>
> I have had some problems getting it going and it has just given up while tryi
ng
> to compile Metafont (INIMF).
>
> The problems are these:
>
> 1) tangle: there doesn't appear to be a tangle.h in the distribution, I
> eventually downloaded one from the old distribution (??)
>
> 2) TeX: in compiling itex.c it gave the warning "statement not reached" for
> lines 705 733 2102 and 2805. In compiling tex0.c it gave the same warnin
g
> at line 653.
>
> 3) Metafont: in compiling imf.c it gave the error "syntax error at or near
> symbol ;" at line 273 and the "statement not reached" warning at line 42
0.
> The code it complains of is
>
> dumpint ( strstart [ k ] ) ;
> while ( k++ < for_end) ; }
>
> (this is hand-transcribed and may not be absolutely accurate).
>
> The alterations to the top-level makefile are
> CC=cc
> and choosing sunlib instead of X11
>
> I know a little about C and it looks as though the syntax error is spurious.
It's a syntax error if dumpint if #defined to be a block (as it is
on out BSD4.3 VAX (old version of MF). try "cc -E imf.c > new.imf.c"
(or /lib/cpp) and look at the output of the preprocessor. I guess
you'll find something like:
{ ... } ;
while (k++ < for_end);
and that is not pure C ...
This is a result of a bug (?) in web2c that does not enclose the body
of the original for loop inside curly brackets. If you are interested
I'll try to dig the change I made to web2c and send you. As a
temporary fix, change
dumpint ( strstart [ k ] ) ;
to
{ dumpint ( strstart [ k ] ) ; }
>
> Chris Martin
Ze'ev.
--
Ze'ev Shtadler. ARPANET: steed%techunix.bitnet@cunyvm.cuny.edu
Computer Science Faculty, UUCP: ...!psuvax1!techunix.bitnet!steed
Technion, Israel Institute of Technology, BITNET: steed@techunix
Haifa Israel Domain: steed@techunix.technion.ac.il
Phone (work): (+972) 4-294304 CSNET: steed%techunix.bitnet@csnet-relay.csnet
------------------------------
End of UKTeX Digest Volume 90 : Issue 14
!!
!! 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.993(==3.0) LaTeX 2.09 Metafont 1.9 (2.0)
!! Unix 4.2/3BSD & System V. Tar 1600 bpi blocked 20 1 file dated
!! 28 March 1990 (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