From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/man/2:ran
Date: Wed, 17 Sep 2003 09:50:05 +0100 [thread overview]
Message-ID: <fd9758fb5b4fea0e6c0b6c67a0d5b267@caldo.demon.co.uk> (raw)
In-Reply-To: <d0c2409b96146c774fbb5682fa051014@sdgm.net>
>>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 \(<= so it
looks right when actually printed, or run through proof or page. unfortunately
\(<= 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= (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 Windows to try it).
might be something else, but nonetheless that original Unicode input is intended to work
(in Plan 9 troff). /sys/lib/tmac/tmac.uni (which i think is undocumented)
is sometimes used by documents to get even more unicode to work.
the use of ≤ is built-in though.
next prev parent reply other threads:[~2003-09-17 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 23:37 boyd
2003-09-16 23:47 ` Russ Cox
2003-09-17 8:50 ` Charles Forsyth [this message]
2003-09-17 9:17 ` Charles Forsyth
2003-09-17 9:34 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd9758fb5b4fea0e6c0b6c67a0d5b267@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).