From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 12 Aug 2014 17:41:43 +0200
From: Carsten Kunze <carsten.kunze@arcor.de>
To: 9fans@9fans.net
Message-ID: <1488628310.1109153.1407858103209.JavaMail.ngmail@webmail18.arcor-online.net>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_Part_1109151_1837478105.1407858103208"
Subject: [9fans] Many bugs in eqn(1)
Topicbox-Message-UUID: 0e569722-ead9-11e9-9d60-3106f5b1d025

------=_Part_1109151_1837478105.1407858103208
Content-Type: multipart/alternative;
	boundary="----=_Part_1109150_217323715.1407858103208"

------=_Part_1109150_217323715.1407858103208
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello,

I'm somewhat disappointed about the troff software in Plan9.

I did few initial tests with eqn(1) and in addition to the TAB problem I saw that the root sign line and large brackets are not aligned. The attached file shows these problems. It can be processed to PostScript with

eqn eqn.tr | troff | tr2post | psfonts > eqn.ps

(Actually on UNIX using plan9port.)

Does nobody use troff on Plan9? eqn(1) is maybe from around 1990, why had these bugs not been fixed?

Also the font for e.g. "pi" is not as expected (like from DWB or Solaris or groff).

Why does Plan9 troff uses other fonts than UNIX troff does?

--Carsten

------=_Part_1109150_217323715.1407858103208--

------=_Part_1109151_1837478105.1407858103208
Content-Type: text/troff
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=eqn.tr

.nf
TAB does not work:
.sp
.ta 0.5i +0.5i +0.5i
.EQ
x sub 1	+x sub 2	+s sub 1	=^10
.EN
.EQ
-2x sub 1		+s sub 1	=^42
.EN
.EQ
delim $$
.EN
.sp
Root sign line is shifted to the right side:
.sp
.EQ
sqrt {b sup 2 - 4ac}
.EN
.sp
Brackets are not aligned:
.sp
$P=R left [ 1^-^{1+1 sup n} over i right ]$

------=_Part_1109151_1837478105.1407858103208--