From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] /sys/man/2:ran From: Charles Forsyth In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Date: Wed, 17 Sep 2003 09:50:05 +0100 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 3b9eea34-eacc-11e9-9e20-41e7f4b1d025 >>the troff was broken. i'm not sure that's right; i think the problem lies elsewhere. if it had been the use of that character, a better thing to do might have= been to use \(<=3D so it looks right when actually printed, or run through proof or page. unfortu= nately \(<=3D would produce a different discouraging effect in your case, so there's little point in doing that. >>we don't all live in 1127[1] so don't expect the rest of >>the world to be like it. actually, i suspect russ is elsewhere, but if not, it still doesn't matter because it does work correctly at two other Plan 9 sites, with that font=3D (and the ones i normally use). if there is a problem, it might have been with the font file (arguably all but special-purpose ones should have those symbols), or perhaps with the troff configuration. perhaps it's drawterm (seems possible to me, but i haven't yet booted Win= dows to try it). might be something else, but nonetheless that original Unicode input is i= ntended to work (in Plan 9 troff). /sys/lib/tmac/tmac.uni (which i think is undocument= ed) is sometimes used by documents to get even more unicode to work. the use of =E2=89=A4 is built-in though.