dre@cs.nott.ac.uk (David Evans) (02/24/88)
We use the TranScript package here to send stuff from ditroff to our Apple LaserWriter plus. Most of the time this is fine, but the underlines and bold rules generated from "tbl" do not line up on the LaserWriter. Does anybody have a solution for this problem, such as sending some PostScript down with each job, or prepended to the prologue file? David R Evans, JANET: dre@cs.nott.ac.uk Electronic Publishing Research Group, ARPA: dre%nott.cs@cs.ucl.ac.uk Department of Computer Science, UUCP: ... !mcvax!ukc!nott-cs!dre University of Nottingham, Tel. NOTTINGHAM(0602) 506101 NOTTINGHAM, ENGLAND, NG7 2RD. Ext. 2765
eggert@sea.sm.unisys.com (Paul Eggert) (02/27/88)
In article <511@robin.cs.nott.ac.uk> dre@cs.nott.ac.uk (David Evans) writes: We use the TranScript package.... Underlines and bold rules generated from "tbl" do not line up on the LaserWriter. TranScript 2.1 fixes this, among other things. To fix 2.0, try the following patch to psdit.pro posted 1987/10/12 by comet!feldman (Steve Feldman). 191c191 < /br{0 750 moveto 0 -1000 rls}def --- > /br{0 880 moveto 0 -1040 rls}def
barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) (02/29/88)
Steve Feldman <feldman@tymix.UUCP> suggested the following patch.
It seems to work fine.
*** psdit.pro.old Fri Sep 11 17:02:13 1987
--- psdit.pro Fri Sep 11 17:03:57 1987
***************
*** 189,193 ****
/vr{0 800 moveto 0 -770 rls}def
/bv{0 800 moveto 0 -1000 rls}def
! /br{0 750 moveto 0 -1000 rls}def
/ul{0 -140 moveto 500 0 rls}def
/ob{200 250 rmoveto currentpoint newpath 200 0 360 arc closepath stroke}def
--- 189,193 ----
/vr{0 800 moveto 0 -770 rls}def
/bv{0 800 moveto 0 -1000 rls}def
! /br{0 880 moveto 0 -1040 rls}def
/ul{0 -140 moveto 500 0 rls}def
/ob{200 250 rmoveto currentpoint newpath 200 0 360 arc closepath stroke}def
--
Bruce G. Barnett <barnett@ge-crd.ARPA> <barnett@steinmetz.UUCP>
uunet!steinmetz!barnettjwilson@POLYA.STANFORD.EDU (James Wilson) (03/03/88)
>From: steinmetz!vdsvax!barnett@uunet.uu.net (Bruce G. Barnett)
Organization: General Electric CRD, Schenectady, NY
Steve Feldman <feldman@tymix.UUCP> suggested the following patch.
It seems to work fine.
*** psdit.pro.old Fri Sep 11 17:02:13 1987
--- psdit.pro Fri Sep 11 17:03:57 1987
***************
*** 189,193 ****
/vr{0 800 moveto 0 -770 rls}def
/bv{0 800 moveto 0 -1000 rls}def
! /br{0 750 moveto 0 -1000 rls}def
/ul{0 -140 moveto 500 0 rls}def
/ob{200 250 rmoveto currentpoint newpath 200 0 360 arc closepath stroke}def
--- 189,193 ----
/vr{0 800 moveto 0 -770 rls}def
/bv{0 800 moveto 0 -1000 rls}def
! /br{0 880 moveto 0 -1040 rls}def
/ul{0 -140 moveto 500 0 rls}def
/ob{200 250 rmoveto currentpoint newpath 200 0 360 arc closepath stroke}def
--
Bruce G. Barnett <barnett@ge-crd.ARPA> <barnett@steinmetz.UUCP>
uunet!steinmetz!barnett
-------z30085@tansei.cc.u-tokyo.JUNET (Murao Hirokazu) (03/08/88)
There is a similar problem with eqn.
To include an expression of a determinant,
we write
left | matrix { ... } right |
and this causes the same problem on LaserWriter,
although another implementation using the fonts
contained in Documentor's Workbench prints out very nicely.
In this case, the problem arose from the fact that eqn
translates vertical line specification into multiple "|"s,
and I wondered whether to rearrange the font itself.
But I finally decided to add new specifications to eqn:
{left|right} {v|V}
where "v" yields \(br and "V" does \(bv.