[comp.text] TeXhax Digest V88 #87

TeXhax@Score.Stanford.EDU (TeXhax Digest) (10/08/88)

TeXhax Digest   Friday, October  7, 1988   Volume 88 : Issue 87

Moderator: Malcolm Brown

Today's Topics:

        re: reference works for document layout (TeXhax81.88)
                         Answer and Question
               AMS fonts for higher resolution printers
                       TeX for Proffesional 380
               Re: TeXhax Digest V88 #84 (LaTeX notes)
                            LaTeX question
                "n of m" pagination LaTeX style option
                       TeX at I.P.Sharp inquiry
                      Re: TeXhax Digest V88 #84
                     small capitals (TeXhax84.88)
                     Question (UNIX, typesetter)
                                dview
                  How to get the PC previewer DVIEW?
                        Driver for HP DeskJet
                          Re: METAFONT modes
                      Re: LaTeX Style Questions
                   Journals that accept TeX (flame)

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


Date: Sat, 24 Sep 88 03:08:25 EDT
From: jonradel@icecream (Jon Radel)
Subject: re: reference works for document layout (TeXhax81.88)

Jan V. White has written a complete book on the subject:  Graphic 
Design for the Electronic Age--The manual for traditional and desktop 
publishing.  (Xerox Press/Watson-Guptill Publications, 1988.  ISBN 
0-8230-2121-1 0-8230-2122-X(pbk.))  It's my current favorite of the 
rules-of-thumb for laying things out so as to keep your readers happy 
while they read your stuff for maximum comprehension.
 
He keeps computer technology in mind, but the book isn't tainted by 
any of the quickly dated:  "This is how program XYZ does X."  In one 
or two places, though, he makes it obvious that his background is 
largely in typography rather in computers.  He states as a bald fact: 
"Getting type to appear in a direction different from the normal 
portrait mode requires having four separate versions of the font in 
memory..."  So much for page description languages or putting the 
paper into the printer upside down. :-)
 
--Jon Radel

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

Date: 27 Sep 88 02:26:00 EST
From: "NJITX::HXN8477" <hxn8477%njitx.decnet@njitc.njit.edu>
Subject: Answer and Question

I have an answer to a previously asked question about the availability
of a TeX previewer for the IBM pc and compatible.  I saw two previewers
on simtel20.arpa.  They are cdvi, and dview.  They are in directory
pd1:<msdos.tex> and available for FTPing.

The question is: how does one generate a backslash "\" in latex, in 
the ordinary -as opposed to verbatim- mode?  The escape character
is itself a backslash.  And if you put two backslashes in sequence, 
it will be understood by latex as the end of line command.

Hamed

| Hamed Nassar             | Internet  : hxn8477%njitx.decnet@njitc.njit.edu |
| EE Department            | UUCP      : bellcore!argus!mars!nancy           |
| NJ Inst. of Tech         | CompuServe: 74000,130                           |

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

Date:       Tue, 27 Sep 88 12:01:19 BST
From:       David Osborne <cczdao%CLAN.NOTT.AC.UK@Forsythe.Stanford.EDU>
Subject:    AMS fonts for higher resolution printers

i see in the latest Unix TeX distribution (May 1988) that the AMS fonts
(Cyrillic and Euler) in subdirectory amsfonts/gf are available in three
different resolutions of 118, 200 and 300 dpi.
    i know these are not available in METAFONT source form, so i can't
build the fonts for higher resolution printers myself (we're expecting
a 400 dpi Agfa P3400 soon).
    is it possible to use these fonts on higher resolution devices,
such as Agfa P400s, Linotronic and Autologic typesetters, etc
(all of which use a higher, sometimes much higher, res than 300) ?
any advice welcome.


David Osborne

 Cripps Computing Centre, University of Nottingham, Nottingham NG7 2RD, UK
 (Phone: +44 602 484848 x2064)
 JANET:    dao@uk.ac.nott.clan        BITNET: dao%uk.ac.nott.clan@ukacrl.bitnet
 Internet: dao%uk.ac.nott.cs@nss.cs.ucl.ac.uk ,
       or: dao%uk.ac.nott.cs%ukacrl.bitnet@cunyvm.cuny.edu
 UUCP: ,...!mcvax-!ukc!nott-cs!dao

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

Date:     Tue, 27 Sep 88 15:41 N
From:     <EAROSAM%EBRUPC51.BITNET@Forsythe.Stanford.EDU>
Subject:  TeX for Proffesional 380

  Does anyone know about a version of TeX available for the Proffesional 380?
  I would also need a previewer and a driver for the LA50 printer.

  Thanks for your help,

        Rosa Martin
        Facultad de Informatica de Barcelona
        C/ Pau Gargallo, 5
        08028 Barcelona
        SPAIN

        Phone +34 3 3338308 (x 316)
        Fax   +34 3 2406302

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

Date: Tue, 27 Sep 88 08:08:40 PDT
From: lamport@src.dec.com (Leslie Lamport)
Subject: Re: TeXhax Digest V88 #84 (LaTeX notes)

Various people have asked recently about making an index.  I thought
this was answered on several occasions in TeXHaX. The program is called
makeindex, and it was written by Pee-Hong Chen at Berkeley.  It's a C
program, so it should be easy to make it work on most systems.  I
believe it's on the Unix distribution tape.

Hubert Partl writes:

   Page 113 of my LaTeX Manual tells me that the vertical separation
   between list items is \itemsep .  The comments in my file ARTICLE.DOC
   and my own experience tell me that it is \itemsep + \parskip .  Have I
   got a wrong (old) version of the LaTeX Manual?

Yes.  The errata in ADDENDUM.TEX file includes

   \subsubsection*{page 113}
   Change the label on the arrow above Item~2 from \verb|\itemsep| to
   \verb|\itemsep + \parsep|.

There have also been some questions about making boxes.  The one by
Paul Bartholdi seems to revolve around the problem of getting the right
amount of space at the bottom of a parbox.  As I recall, this was a
particularly nasty problem because of TeX's rules, the commands to end
the box that are required to get the correct spacing depend on what's
in the box, so it's impossible to write a \parbox command that works
properly in all possible cases.  The best approach is probably to avoid
adding space and to end the box a strut.  As I recall, the command
\strut produces the right sized strut for ordinary text.  Thus, you
might do something like

  \newcommand{\foo}[1]{ ... \parbox[t]{123.4mm}{#1\strut}...}

However, an extra space at the end of the argument to foo could
produce a line in the parbox consisting only of the strut.  This
can be avoided by 

  \newcommand{\foo}[1]{ ... \parbox[t]{123.4mm}{#1\unskip\strut}...}

but this will produce an error if the argument of \foo ends with
a blank line, or something else that leaves TeX in vertical mode.

As you can see, it's a lot easier to define commands if you know
exactly how they're going to be used, which is the case if you're
defining them for your own use, but not if you're writing a document
style for others to use.


Vivian Harrington writes

   I wish to adapt the letter.sty file to allow for headed stationary.  If
   the letter runs to more than one page I do not want the the space left
   for the header on subsequent pages as in the first page.  Has anyone
   already devised a solution for this request?

I don't understand why this should be a problem.  Whatever command
prints the salutation and other stuff that begins a letter can easily
start with a \vspace* command.  

Leslie Lamport

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

Date: Tue, 27 Sep 88 13:43:59 EDT
From: lang@PRC.Unisys.COM
Subject: LaTeX question

I'm sure this is simple, but I haven't been able to do it.
Any suggestions will be appreciated.
In LaTeX, I'd like \paragraph and \subparagraph sections not to have
the text start on the same line as the title of the \(sub)paragraph,
but rather have some vertical space left between the title and the text,
the way there is in the \section, \subsection, and \subsubsection sections.
Can somebody provide a way to do this?  Many thanks.

Francois-Michel Lang
Paoli Research Center, Unisys Corporation lang@prc.unisys.com (215) 648-7256
Dept of Comp & Info Science, U of PA      lang@cis.upenn.edu  (215) 898-9511

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

Date: Tue, 27 Sep 88 10:44:56 PDT
From: Max Hailperin <HAILPERIN@SUMEX-AIM.Stanford.EDU>
Subject: "n of m" pagination LaTeX style option

I recall a while ago one or more people asking on TeXHaX for a LaTeX document
style option to generate page numberin of the form "n of m".  I don't recall
any responses, except one or two suggestions as to general strategy.  If I'm
mistaken, I apologize.

It turns out that the most obvious solution actually works, namely using
\label and \pageref.  The below document style option does that automatically.

% This is a LaTeX document style option for "n of m" style pagination.
% It produces a centered header in the above style, and no footer; variations
% to put the information elsewhere, incorporate other information, or include
% the word "page" should be easy.  This option works by recording the last
% page's page number in the .aux file (using the standard label/pageref
% mechanism).  Therefore, you will have to run LaTeX a second time if the
% number of pages changes, in order to get correct output.
%
% WARNING: This completely disables \thispagestyle as a quick and dirty
%          way to avoid the automatic \thispagestyle{plain} that occurs
%          for the first page and first index page in the usual styles.
%          It seems that "n of m" users would in general not want that,
%          nor want to use \thispagestyle themselves.  The relevant line
%          (first thing after the identifying typeout below) is easy to
%          comment out if you disagree with this.
%
%     -- Max Hailperin, 9/27/88

\typeout{Document Style Option 'nofm' -- Released 27 September 1988}

\def\thispagestyle#1{}  %  SEE ABOVE WARNING

% The following definitions produce the headers and footers in the desired
% format; they should be changed for variations.
\def\@oddhead{\rm\hfil \thepage\ of \pageref{@last-page} \hfil}
\def\@evenhead{\@oddhead}
\def\@oddfoot{}\def\@evenfoot{\@oddfoot}

% The below is reproduced from the latex.tex file, version 2.09 of 27 October
% 1986, Copyright (C) 1985 by Leslie Lamport, with the exception of the
% marked change in the first line----vvvvvvvvvvvvvvvvvv.
\def\enddocument{\@checkend{document}\label{@last-page}\clearpage\begingroup  
\if@filesw \immediate\closeout\@mainaux 
\def\global\@namedef##1##2{}\def\newlabel{\@testdef r}%
\def\bibcite{\@testdef b}\@tempswafalse \makeatletter\input \jobname.aux
\if@tempswa \@warning{Label(s) may have changed.  Rerun to get
cross-references right}\fi\fi\endgroup\deadcycles\z@\@@end}

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

Date:         Tue, 27 Sep 88 16:59:10 EDT
From:         Chris Carruthers <CJC%UOTTAWA.BITNET@Forsythe.Stanford.EDU>
Subject:      TeX at I.P.Sharp inquiry

About 2 years ago a colleague of mine gave me a photocopy of an article
entitled ``Using TeX for Electronic Publishing at I.P.Sharp Associates'' by
David Manson.  What I would like to know is the source of this article, that
is, what publication did it appear in if any?

Thanks in advance, Chris.

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

Date:     Tue, 27 Sep 88 15:55 CST
From:     <HANK%AUDUCVAX.BITNET@Forsythe.Stanford.EDU>
Subject:  Re: TeXhax Digest V88 #84

Our mailer is unable to reach J.D. Mcdonald, so I'll try TeXhax.
In TeXhax v88, #82 J.D. Mcdonald writes:

> I need to know how to change the actual format of Bibtex citations.
> In a local style file I found the line
>      \renewcommand\@cite[1]{$^{\mbox{\scriptsize #1}}$}
> While I can play around with what is inside the outer {} to change the
> format from the superscript present there, what I need is to leave
> this laone and introduce a completely new command, say \citenosuper,
> that will just put the number, alone, in normal size text in the
> output. Presumably I will need to define a new \citenosuper and
> a new \@citenosuper. However, I am too new at this to figure out
> how to do it and where to put it. Any help?
> Doug McDonald (mcdonald@uiucuxe)

In latex.tex, Lamport writes that \b@FOO has the tag for citation FOO. So, for
example, you could write a macro
  \makeatletter
  \newcommand{\thecite}[1]{\csname b@#1\endcsname}
  \makeatother
and then \thecite{FOO} would print the number.  This is sloppy, since it does
not check that \b@FOO is defined.  Further, I assume that you want your
\citenosuper to work just like \cite, except for the frills.  In particular, I
assume that \citenosuper should generate the .aux file stuff.

One method is to just copy the \cite code from latex.tex, and make new
commands for \cite and \@cite (like you suggested).  I used \plaincite.
This may be somewhat more than you need, since it will allow the syntax
of \cite.  My guess is that you don't need constructions like
`\plaincite[Theorem 1]{ONE,TWO,...}'.

%---------------------------------------------------------------------------
\makeatletter
\def\plaincite{\@ifnextchar [{\@tempswatrue\@plaincitex}%
{\@tempswafalse\@plaincitex[]}}

\def\@plaincitex[#1]#2{{\def\@cite##1##2{\@plaincite{##1}{##2}}%
\@citex[#1]{#2}}}

\def\@plaincite#1#2{{#1\if@tempswa , #2\fi}}
\makeatother
%---------------------------------------------------------------------------

--darrel (Bitnet: hank@auducvax)

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

Date: Wed, 28 Sep 88 03:26:17 EDT
From: jonradel%icecream.Princeton.EDU@Princeton.EDU (Jon Radel)
Subject: small capitals (TeXhax84.88)

According to {\it Computer Modern Typefaces}, p. 30:
 
cmcsc10 goes with cmr10
cmtcsc10 goes with cmtt10

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

Date: Wed, 28 Sep 88 10:22:40 EDT
From: Daniel Zwillinger <zwilling%linus@mitre-bedford.ARPA>
Subject: Question (UNIX, typesetter)

TeXHaX --

My publishing and I are trying to get my book (3 Mbytes of .dvi file)
produced.
The people we have chosen to run the photo-typsetter have a VMS based
system, while we have a UNIX based system.
After two unsucessful attempts of sending them the .dvi file;
we are stymied.

1) I first sent them a   tar   tape.  They couldn't read it.
2) I then sent them a tape created with dd (the disk dump command).
   They could read part of it, but not all of it.
3) They can't/won't use remote ftp or a modem.

Apparently the order of the bytes is different in a VMS and a UNIX
system.  What to do ?


Dr. Daniel Zwillinger        CSNET: linus!zwilling@mitre-bedford.arpa
The MITRE Corporation        work: 617/271-3404 
Bedford, MA 01730            home: 617/646-8565  

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

Date: Wed, 28 Sep 88 14:40:30 EDT
From: Mr. Scott Bodarky (ART-UGRAD) <bodarky@umbc3.UMD.EDU>
Subject: dview

Hi, sorry to bother you with this, but my mail to the contributer of
the article in TeXhax bounced.  Jacques J. Goldberg, 
<PHR00JG%TECHNION.BITNET@Forsythe.Stanford.EDU>, mentioned a program called
DVIEW, which he said was public domain.  Do you (or does he) know how I can
obtain this previewer for VGA (or EGA)?

Thanx

%%% Jacques replies:

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

Date:    Thu, 29 Sep 88 09:04:55 IST
From:    "Jacques J. Goldberg" <PHR00JG%TECHNION.BITNET@Forsythe.Stanford.EDU>
Subject:      How to get the PC previewer DVIEW?

People keep asking me how to get DVIEW.

1. Bitnet users.
================
TELL TRICKLE AT TREARN /PDGET <MSDOS.TEX>DVIEW.ARC
or
TELL TRICKLE AT DKTC11 /PDGET <MSDOS.TEX>DVIEW.ARC
or
TELL LISTSERV AT RPICICGE /PDGET PD:<MSDOS.TEX>DVIEW.ARC
depending on where you are located.

2. Arpanet users.
=================
ftp to simtel20, extract the file from the same directory structure as above.

3. Fonts.
=========

Although I make no profit but get a lot of headache with this, I will continue
to mail on request 5 diskettes with all 74 CM fonts and 11 Latex fonts at mags
0,1/2,1,2,3 for DVIEW, with the program itself and an Hercules work around.
I expect such users to later send me 20$ after they have received and tried the
material. DVIEW.ARC contains 7 AM files only, and works with CGA or compatibble
adaptors only, hence my fonts and the public domain SIMCGA40 (not mine) for
Hercules owners. Since people who ask for the fonts get DVIEW with them anyway,
this may save them the downloading and un-arcing of the server file.

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

Date: Wed, 28 Sep 88 12:08:05 PDT
From: white@ee.UCLA.EDU (Joseph White)
Subject: Driver for HP DeskJet

I modified the PD driver that was on the net a few months
ago to work with the DeskJet. It does not use the downloadable
fonts, just creates and downloads the bitmap. Currently it is 
running on an IBM AT and it is very slow since it swaps memory to
the disk.

A better solution if you have a Macintosh is to use TeXtures and
the DeskJet driver written by DataPak Software (Sherman Oaks, CA).

-Joe White		white@ee.ucla.edu

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

Date:     Wed, 28 Sep 88 16:08:11 CDT
From: William LeFebvre <phil@rice.edu>
Subject:  Re: METAFONT modes

Alternatively, if you have "inimf" and "virmf" available (and assuming
that "plain.mf" has been installed in the appropriate place), you can
create your own base file as follows (user's input underlined):

	% inimf plain
	  -----------
	[ lots of junk omitted ]
	*input local
	 -----------
	(local.mf)
	*dump.
	 -----
	[ lots more stuff omitted ]

Now you have a "plain.base" in the current directory.  Rename this to
whatever you want, say "local.base", then you can use virmf as follows:

	% virmf '&local \mode=mymode; mag=2; input cmr10'

This is how you add your own local modes to plain:  put them in a
different file and input that file in the same place "local" was
inserted above.  Creating your own base file will probably result in
faster execution if you plan on using it often.

			William LeFebvre
			Department of Computer Science
			Rice University
			<phil@Rice.edu>

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

To:   texhax@score.stanford.edu
From: Z3000PA%AWITUW01.BITNET@Forsythe.Stanford.EDU
SUBJECT: Re: LaTeX Style Questions

About a month ago, I posted a question on how to modify the LaTeX
page layout.  I received very few, but very valuable answers.  The
basic summary is:

   All the information that is needed to change the document style
   within LaTeX can be found quite easily in the following set of
   sources:
     1. the LaTeX manual
     2. the layout article in TUGboat Vol.9,No.1 (April 1988)
     3. the files ARTICLE.DOC, ART10.DOC, etc.
     4. the file LATEX.TEX
     5. the TeXbook
   What you then have to do is:  find the relevant original defi-
   nitions,  copy them into a file xxx.sty,  change them to your
   needs, and insert the option name xxx into the optional argument
   of your \documentstyle command - that's it!

Of course, before you change the document layout, you should have the
new layout designed by someone who knows what to do and how and why.
(- Dr.Lamport IS right in his opinions on this matter, and I have learnt
a lot about it in Paul Stiff's and Sue Brooks' workshops at this year's
European TeX Conference in Exeter. -)

Happy styling!

Hubert Partl, Technical University of Vienna (z3000pa@awituw01.bitnet)

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

Date:         Thu, 29 Sep 88 16:34:04 MET
From:         Victor Eijkhout <U641000%HNYKUN11.BITNET@Forsythe.Stanford.EDU>
Subject:      Journals that accept TeX (flame)

Let's try to play the devil's advocate............

Some scientific journals allow authors to submit articles
in the form of TeX code. I have two reasons not to be
overly enthousiastic about this.

One. As TeX is still intimately connected to the Computer Modern
font, journals tend to wind up with two kinds of articles with
totally different outlook. This is ugly, irrespective of
whether you like the CM. It may be acceptable (or rather, it is
common practise) for rapid dissemination proceedings, it just
won't do for regular scientific publication.

Two. It is my fear that (1) journals may view accepting TeX source as
a way of saving typesetter costs; (2) journals will have to employ
a TeX hacker (next to their regular typesetting staff), which they
probably won't do. Witness the SIAM journal on Numerical Analysis
(a leading publication in its field) which published an article set
in TeX a while ago (though it doesn't advertise the possibility),
which contained both beginners' mistakes such as
an omitted italic correction, and silly but ugly errors such as
a tenpoint formula in an eightpoint abstract. Did no typesetter
ever set eyes on that article, or did they not know what to
do about it?

Certain journals that accept TeX state that this will not speed up
the process of reviewing and printing. What then are the
benefits of submitting TeX source? A good journal ought to
publish quality articles, and present them in quality layout.
I don't want to see a layman's layout anymore than I want to
study a layman's articles.

Let's hope this sparks some discussion.

Victor Eijkhout                                  u641000@hnykun11.bitnet
Department of Mathematics
University of Nijmegen
Nijmegen, the Netherlands

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

%%%
%%% Concerning subscriptions, address changes, unsubscribing:
%%%     BITNET: send a one-line mail message to LISTSERV@TAMVM1.BITNET:
%%%         SUBSCRIBE TEX-L <your name>    % to subscribe
%%%
%%%     All others: send mail to
%%%           texhax-request@score.stanford.edu
%%%     please send a valid arpanet address!!
%%%
%%%
%%% All submissions to: texhax@score.stanford.edu
%%%
%%% Back issues available for FTPing as:
%%%          machine:      directory:  filename:
%%%   [SCORE.STANFORD.EDU]<TEX.TEXHAX>TEXHAXnn.yy
%%%      nn = issue number
%%%      yy = last two digits of current year
%%%\bye
%%%

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

End of TeXhax Digest
**************************
-------

thomas@gmdzi.UUCP (Thomas Gordon) (10/12/88)

From article <23523@labrea.Stanford.EDU>, by TeXhax@Score.Stanford.EDU (TeXhax Digest):
> 
> Let's try to play the devil's advocate............
> 
> Some scientific journals allow authors to submit articles
> in the form of TeX code. I have two reasons not to be
> overly enthousiastic about this. ...
> 
> I don't want to see a layman's layout anymore than I want to
> study a layman's articles.
> 

Perhaps such concerns make it clear why the Association of American 
Publishers, AAP, is pushing SGML, Standard Generalized Markup Language,
an ISO standard for marking the logical components of manuscripts
(footnotes, references, titles, author ...) rather than the visual
layout.   Authors are responsible for the content and structure 
of their manuscripts, but publishers remains responsible for
typesetting.  The AAP has published a set of "document types" for
describing scientific manuscripts, including mathematical formulas.



-- 
Thomas F. Gordon		email: thomas@gmdxps.uucp
GMD / F3			phone: (+49 2241) 14-2665
Schloss Birlinghoven
D-5205 Sankt Augustin 1, FRG