From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] charon fixes for utf8
Date: Mon, 5 Feb 2001 13:26:31 +0900 [thread overview]
Message-ID: <20010205042736.A662D199D7@mail.cse.psu.edu> (raw)
>It looks like there is still a bug in the lexer, as
>viewing http://plan9.bell-labs.com/wiki/plan9/22
This is a font problem in charon.
In charon, fonts are fixed to /fonts/lucidasans in charon_gui.b, where
there is no Kanji font defined. If you want to see that page, you may change
the lines of definition of fonts=array[NumFnt] of,
say "/fonts/lucidasans/unicode.8.font" to /fonts/pelm/unicode.9.font".
However, this will lead to Rob's grumble/complain ^_^ before, ie., we only
have very limited fonts there. :-)
Kenji
next reply other threads:[~2001-02-05 4:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 4:26 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 1:12 okamoto
2001-02-06 16:14 rob pike
2001-02-06 5:11 okamoto
2001-02-06 1:01 okamoto
2001-02-05 18:18 Russ Cox
2001-02-05 4:42 okamoto
2001-02-05 10:26 ` Boyd Roberts
2001-02-02 21:04 Russ Cox
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=20010205042736.A662D199D7@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).