TeXhax@cs.washington.edu (TeXhax Digest) (10/17/89)
TeXhax Digest Monday, October 16, 1989 Volume 89 : Issue 92
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:
RE: T.Rokicki's dvips printer driver
TeXtures and Apple Imagewriter LQ
MacIntosh figures (yet again)
LATeX circles (and lines)
Query on LaTeX tabular
Re: Latex question I can't answer--\def in preamble
\label within \caption gives vertical space \LaTeX bug?
Re: TeX/LaTeX and multinational character sets
----------------------------------------------------------------------------
Date: Thu, 12 Oct 89 15:57:43 CDT
From: byerly@TTMATH (Robert Byerly)
Subject: RE: T.Rokicki's dvips printer driver
Keywords: dviware
We have recently acquired T. Rokicki's dvips printer driver, which
has support for psfig and tpic specials. These two topics have often
been alluded to in TeXhax, but, at least in the last hundred issues or
so of TeXhax, there has been no discussion of what they are and how
to obtain them!!! Would some knowledgable person care to enlighten
us?
Bob Byerly,
Dept. of Math.
Texas Tech University
---------------------------------------------------------------------------
Date: 11 Oct 89 1555 PDT
From: Arthur Keller <ARK@SAIL.Stanford.EDU>
Subject: TeXtures and Apple Imagewriter LQ
Keywords: TeXtures, Apple Imagewriter LQ
I have TeXtures on a Mac IIx and am printing my output on an Imagewriter
LQ. Unfortunately, the fonts supplied with TeXtures (and LaTeX) are too
low resolution, so the results on the LQ printer are not much better than
they would be on an ordinary Apple Imagewriter. How do I get larger sizes
of the Plain and LaTeX fonts? Also, how I get an ordinary Metafont font
into TeXtures font format? Thanks.
Arthur
-----------------------------------------------------------------------
Date: Wed, 11 Oct 89 15:08:06 PDT
From: Darrell Long <darrell@midgard.ucsc.edu>
Subject: MacIntosh figures (yet again)
Keywords: MacIntosh, figures, TeX
I'm having trouble including MacIntosh figures into my TeX documents. I am
interested to hear if anyone has a good solution.
In the past we had used a locally hacked version of dvips (0.83); but it
generates non-conformant PostScript (or so I am told). It's also very old
and does other things wrong.
What is the one true way of including MacIntosh figures? If anyone knows,
please drop me a note. I'm really getting tired of scissors and glue.
Darrell D. E. Long
Baskin Center for Computer Engineering & Information Sciences
Applied Sciences Building
University of California
Santa Cruz, CA 95064
(408) 459-2616
---------------------------------------------------------------------------
Date: Wed, 11 Oct 89 11:32:09 -0500
From: "J.D. McDonald " <mcdonald@uxe.cso.uiuc.edu>
Subject: LATeX circles (and lines)
Keywords: LaTeX, circles, lines
There are indeed problems with circles, ovals, and slanted lines
in Latex. The first problem is that many people are using
incorrectly generated fonts. The Latex line and circle fonts
will be WRONG if generated with a MEtafont that has Computer
Modern stuff preloaded. You need to generate them with a
virgin Metafont.
But that is not all. The roundoff algorithms in many dvi drivers
(those that derive the numbers from some ur-version from long ago)
won't get the ends to line up right. Apparently Knuth, or
whoever wrote this first program, never considered trying to
line up things pixel-exact. The problem can be seen in the Beebe
drivers in the routimes moveover and movedown. One has a 5
where the other has a one. The five should be smaller to fix this
problem- probably one also. There is also a tolerance
parameter that needs to be made smaller. So indeed there is a problem
in the drivers.
Also, for LAtex slanted lines there is an additional problem.
That is, you can only get them to line up with no glitches if
the lengths defined in the Metafont file are an EXACT (within the
accuracy of a float variable) multiple of your physical output device.
This an incurable device dependency. There is no easy cure. What I did
is to make a new Latex line (and linew) font set called line9 and
linew9. In this I defined the length to be an exact multiple of
1/300 inch - for a 300 d.p.i. printer of course. I believe 36/300 inch
works well. Then redo lfonts .tex to use line9 and linew9
instead of line10 etc. The way the macros are defined you don't have
to change your Latex code. This will get rid of glitches for all
line lengths not using a "5" in their definition. A 1/10 inch
length will work for all but those with a 4. A 1/5 inch will work
for all slopes, but the shortest line gets longer. (These are for
300 d.p.i. devices.)
Doug McDonald
----------------------------------------------------------------------------
Date: Tue, 10 Oct 89 17:32:10 BST
From: "T.R.Hopkins" <trh%ukc.ac.uk@NSFnet-Relay.AC.UK>
Subject: Query on LaTeX tabular
Keywords: LaTeX, tabular
I have been typesetting an index of ACM algorithms by setting each
entry in the following format:
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
7
&{\raggedright {E}uclidian Algorithm \\}
&{\raggedright {\bf C3:240} \\}
\end{tabular}}
Using LaTeX 2.09 (4 Aug 1988) each entry was set with a small interentry
gap (slightly wider than the interline gap). For example
6 Triangular Decomposition 17:195
7 Inversion of a Positive 17:198
Definite Matrix
1. With LaTeX 2.09 (24 May 1989) the same source produces a much greater
interentry gap (about 3 times the old gap).
(The change that matters is probably the one dated 14/Jan/89 at line
4815 in latex.tex.)
2. If I remove the \\ from the end of each {\raggedright ... \\} block I
get the original spacing but the second and third entries are NO LONGER
set raggedright but flushright.
Questions:
1. How can I get my old format back again using the new version of LaTeX?
2. Why does removing the \\ from the {\raggedright ... \\} blocks set the
text fully justified?
Tim Hopkins, { trh@ukc.ac.uk
Computing Laboratory, trh%ukc@cs.ucl.ac.uk
University of Kent, na.hopkins@score.stanford.edu }
Canterbury CT2 7NF, Kent, UK.
%--------------------------------------------------------------------------
Sample
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
7
&{\raggedright {E}uclidian Algorithm \\}
&{\raggedright {\bf C3:240} \\}
\end{tabular}}
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
35
&{\raggedright {SIEVE} \\}
&{\raggedright {\bf C4:151} C5:209 C5:438 C10:570 \\}
\end{tabular}}
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
61
&{\raggedright Procedures For Range Arithmetic \\}
&{\raggedright {\bf C4:319} \\}
\end{tabular}}
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
68
&{\raggedright Augmentation \\}
&{\raggedright {\bf C4:339} C4:498 \\}
\end{tabular}}
\noindent
{\small \begin{tabular}{p{0.4in}@{}p{2.75in}@{}p{1.4in}}
72
&{\raggedright Composition Generator \\}
&{\raggedright {\bf C4:498} C5:439 \\}
\end{tabular}}
-----------------------------------------------------------------------------
Date: Thu, 12 Oct 1989 13:38:33 PDT
From: Max Hailperin <mxh@sumex-aim.stanford.edu>
Subject: Re: Latex question I can't answer--\def in preamble
Keywords: LaTeX, \def, preamble
> <<<Can you offer a quick suggestion about this? Please don't ask why I
> <<<want to do such a silly thing..the \def is actually more complicated
> <<<than shown but i stripped it down for ease of reading.
>
> <<<\documentstyle{article}
> <<<\def\bar#1#2#3{ \multicolumn{1}{#1} &
> <<< \multicolumn{1}{#2} &
> <<< \multicolumn{1}{#3}
> <<<}
> <<<
> <<<\begin{document}
> <<<\begin{tabular}{lll}
> <<<\bar{Column 1}{Column 2}{Column 3}
> <<<\end{tabular}
> <<<\end{document}
>
> <<<It seems the \multicolumn is expanded too soon, causing a huge hiccup.
> <<<\bar shouldn't be looking up the definition of \multicolumn, it should
> <<<merely replace "\multicolumn" at the calling point and allowing
> <<<the tabular environment to expand it.
> <<<-------
>
> Here is your original example, altered slightly:
>
> \documentstyle{article}
> \def\bar#1#2#3{\multicolumn{1}{c}{#1} &
> \multicolumn{1}{c}{#2} &
> \multicolumn{1}{c}{#3}
> }
>
> \begin{document}
> \begin{tabular}{lll}
> \bar{Column 1}{Column 2}{Column 3}
> \end{tabular}
> \end{document}
>
> In order to get your example to run through LaTeX, I added the {c}
> field below. (If you look on page 182ff in the LaTeX manual, you will
> see that that argument is required.--I'm assuming
> this was an oversight which occurred when you were
> simplifying your example.) When I ran it through LaTeX, my
> output looked like this:
>
>
> Column 1 Column 2 Column 3
>
>
> This is the ouput I expected. As I see no hiccup, I would appreciate your
> sending me either a clearer statement of your problem or a more
> detailed example with which I can generate the problem.
> Please send this directly to me and not to the
> mailing list. Good Luck!!
>
> Michelle McElvany
> Aerospace Technology Center
> Allied--Signal Aerospace Company
> michelle@atc.bendix.com
>
>
> <Sorry for exclusion of the format specification in my example.
> <Here's the actual file. Today, I modified the \def\submilestone
> <to not use an ampersand within the \def, on someone's suggestion that
> <TeX might be very sensitive to its use within \def. This code,
> <however, fails the same way.
> <
> <Thanks for your help.
> <---------------------------------------------------------------------------
> \documentstyle{article}
> \def\mc{\multicolumn}
> \count105=36 %Initialize a counter to 36
> \def\submilestone#1{
> \ifnum \count105 = 36 %Check if previous line filled
> \count105=0 % Yes---reset counter
> \mc{1}{|l|}{\parbox[t]{3in}{#1}}& % Build column 1
> \else %Last line incomplete---error
> \makeatletter
> \@latexerr{Last submilestone did not specify all 36 months}{}
> \makeatother
> \fi
> }
>
> %%%%%%%%%%%%%%%%%%%%%%% S O L I D %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> % This macro is called to draw a solid rule 5pt in height %
> % and #1 columns in width. Each column is 12.04pts wide %
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \def\solid#1{ \dimen102=#1%
> \multiply\dimen102 by 394690
> \mc{#1}{\rule[5pt]{\dimen102}{5pt}}
> \advance\count105 by #1
> }
> %%%%%%%%%%%%%%%%%%%%%%% H O L L O W %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> % This macro is called to draw a hollow rule 5pt in height%
> % and #1 columns in width. Each column is 12.04pts wide %
> % This is done by dropping a .4pt tall rule (a), hspacing %
> % back to the start of that rule, and then dropping a %
> % second rule 5pt higher than the first one (c), after %
> % dropping a 5pt tall, .4pt long rule prior and after %
> % to draw the left and right walls (b) and (d) %
> % %
> % (c) %
> % ________________ %
> % (b) |________________| (d) %
> % (a) %
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \def\hollow#1{ \dimen103=#1%
> \multiply\dimen103 by 394690
> \mc{#1}{\rule[5pt]{.4pt}{5pt}%
> \rule[5pt]{\dimen102}{.4pt}%
> \rule[5pt]{.4pt}{5pt}%
> \hspace*{-.4pt}%
> \hspace*{-\dimen102}%
> \rule[10pt]{\dimen102}{.4pt}}%
> \advance\count105 by #1
> }
> %%%%%%%%%%%%%%%%%%%%%%% B L A N K %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> % This macro is called to space out #1 columns to finish %
> % the line (and allow tabular to draw the ending vertical %
> % rule) (i. e. \begin{tabular}{....llll|}) %
> % ^ %
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \def\blank#1{ \dimen104=#1%
> \multiply\dimen104 by 394690
> \mc{#1}{\rule[5pt]{\dimen104}{0pt}}
> \advance\count105 by #1
> }
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \begin{document}
> {\bf MILESTONES}
> \begin{tabular}{|l|llllllllllll|llllllllllll|llllllllllll|}
> \submilestone{Task A}&\black{14}&\white{8}&\blank{14}\\
> \end{tabular}
> \end{document}
>
> ___________________________________________________________________
>
>
> I don't know how to fix this; so, I am forwarding it to Latex-help-toughies.
> Good Luck.
>
> Michelle
The problem is that the \multicolumn has to be the first thing in the column,
after macro expansion. As page 184 of the LaTeX book says:
A \multicolumn command must either begin the row or else immediately
v follow an &.
In this case the (first-encountered) problem is the \count105=0 line in
\submilestone. If you move that from in front of the \multicolumn (for
example into its third argument) the misplaced \omit error will go away.
The other definitions have similar problems, but of course LaTeX will first
choke on \black being undefined.
-----------------------------------------------------------------------
Date: Tue, 10 Oct 89 22:10 MET
From: JL_Braams%pttrnl.nl@UWAVM.ACS.WASHINGTON.EDU
Subject: \label within \caption gives vertical space \LaTeX bug?
Keywords: LaTeX, \label, \caption, bug
Hi all,
I think have discovered an anomaly in LaTeX and would like to
consultyou all about it. Let me first tell you what I was
trying to accomplish.
I wanted to have *long* figure and table captions look like:
figure 1: text, more text, still more text in paragraph
mode, hanging from the identification.
So, I set out to modify the effect of the \caption command
and found I had to fiddle with \@makecaption from the
documentstyles. As I was using Victor Eijkhouts artikel1.sty
at the time I went in there and found:
\long\def\@makecaption#1#2{
\vskip 10pt
\setbox\@tempboxa\hbox{#1: #2}
\ifdim \wd\@tempboxa >\hsize \unhbox\@tempboxa\par \else \hbox
to\hsize{\hfil\box\@tempboxa\hfil}
\fi}
This means Victor has been working from an older version of
article.sty, because in there I find:
(article.doc dated <16 Mar 88>)
% \@makecaption{NUMBER}{TEXT} : Macro to make a figure or table caption.
% NUMBER : Figure or table number--e.g., 'Figure 3.2'
% TEXT : The caption text.
% Macro should be called inside a \parbox of right width, with \normalsize.
% changed 25 Jun 86 to fix according to Howard Trickey:
% instead of \unhbox\@tempboxa\par we do #1: #2\par
\long\def\@makecaption#1#2{
\vskip 10pt
\setbox\@tempboxa\hbox{#1: #2}
\ifdim \wd\@tempboxa >\hsize % IF longer than one line:
#1: #2\par % THEN set as ordinary paragraph.
\else % ELSE center.
\hbox to\hsize{\hfil\box\@tempboxa\hfil}
\fi}
which differs slightly. But that turned out not to be the problem.
I wanted to the maximum width of the captions to be less than the
width of the text, so I use \@tempdima to get the width of the
enclosing box, and subtract two times \unitindent from it.
(So, if the caption needs it full width it lines up with all
other indents)
If the caption is wider than this with I put the indentification
of the current float in a temporary box, measure it's width and
subtract that from \@tempdima to find out how much width the
hanging paragraph can use. I put the two parts of the caption
both in a \vtop, and center the complete caption.
The code looks like:
\long\def\@makecaption#1#2{%
\@tempdima\hsize\advance\@tempdima -2\unitindent%
\vskip 10pt%
\setbox\@tempboxa\hbox{{\bf #1:} #2}%
\ifdim \wd\@tempboxa >\@tempdima %
\setbox\@tempboxa\hbox{{\bf #1:} }%
\advance\@tempdima -\wd\@tempboxa%
\hbox to \hsize{\hfil\vtop{\box\@tempboxa}%
\vtop{\hsize\@tempdima\@parboxrestore #2}\hfil}%
\else%
\hbox to\hsize{\hfil\box\@tempboxa\hfil%
\fi}%
So far so good. I tested this with a figure I took from a document
I was writing. This document had several figures and tables and
cross references. What I use to do is put \label commands inside
the argument of the \caption{}, to be sure to get the right
numbers. I didn't expect to get any problems, as the LaTeX-book
states on page 72:
... with the \label command going either after
the \caption command or in its argument.
^^^^^^^^^^^^^^^^^^
Now as it turns out, it's not a good idea to put the \label
inside the \caption because... it leaves some VERTICAL SPACE
in the second \vtop I'm using.
This took me a couple of hours to find out. The caption kept
comming out like
figure 1:
text, more text, still more text in paragraph
mode, hanging from the identification.
That is until I removed the \label{} from within the \caption.
Is this a bug, an anomaly or a feature???
Is there a way to fix it? (by modifying the \label command?)
------------------------------------------------------------
Date: Fri, 13 Oct 89 08:49:54 CDT
From: Rick Troth <TROTH@ricevm1.rice.edu>
Subject: Re: TeX/LaTeX and multinational character sets
Keywords: TeX, LaTeX, multinational character sets
>We are looking for a version of TeX (or rather, LaTeX) which accepts
>full 8-bit character sets *on input*, for instance DEC's multinational
>character set, ISO-8859/2, IBM PC multinational character set, etc.
I wrote a program called TEXT2TeX which converts plain text
into TeXable text. It currently processes IBM Code Page 37 (EBCDIC
not ASCII) but could easily be reconfigured for ISO-8859-1. I would
be quite happy to send it to you. You would have to make adjustments
for 8859-2 on your own as I do not have an example of 8859-2.
This is a stop-gap program until the day when TeX will accept
8-bit input, but it does get the job done. Also know that, as it
stands now, text2tex converts TeX control characters: { to \lbrace,
^ to \hat, # to \#, etc. but this again is a simple matter of massaging
the header file to the C source.
Rick Troth <TROTH@RICEVM1.RICE.EDU> ------------- Rice ONCS VM Systems Support
-------------------------------------------------------------------------------
%%% 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
**************************
-------