From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] charon fixes for utf8
Date: Wed, 7 Feb 2001 10:12:11 +0900 [thread overview]
Message-ID: <20010207011256.09224199EA@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
Those sources have time stamp of Jun 13, 2000, and are for release 2 Plan 9.
I've started to try to compile it from last night. I expect we will have various JIS
fonts of various sizes, such as 7, 9, 12, 14, 20, 28, 32, 48 dotts (all are free
fonts made by various authors in Japan). I'll ask you, if I have trouble with it.
Please wait a while...
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 2057 bytes --]
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] charon fixes for utf8
Date: Tue, 6 Feb 2001 11:14:55 -0500
Message-ID: <20010206161518.A5A88199EA@mail.cse.psu.edu>
> By the way, I found /sys/src/cmd/tcs/font directory just now. Yes, this is my
> first time to see this directory. I suppose this includes tools for making many
> 9 subfonts from existing ones. I suppose we didn't see this before (2ed), did we?
I didn't even know it existed. It slipped out when I wasn't looking, I guess.
It might help you but it's written for a very old version of the system.
It'll take some work to get it running, whatever it is. I'm not exactly sure.
It might be what was used to import the original Chinese fonts.
-rob
next reply other threads:[~2001-02-07 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 1:12 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
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-05 4:26 okamoto
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=20010207011256.09224199EA@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).