From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese Font
Date: Mon, 19 Feb 2001 11:13:22 +0900 [thread overview]
Message-ID: <20010219021402.ECF29199E4@mail.cse.psu.edu> (raw)
Well, I've been testing those various sized Japanese fonts in our environment,
and got an different view from the first impression below.
>In my case, I editted as follows:
>
>lucidasans/unicode.6.font for 10x10 Kanji
>lucida/unicode.5.font for 12x10 kanji
>lucida/unicode.6.font for 14x14 kanji
>lucida/unicode.7.font for 16x16 kanji
>lucida/unicode.8.font for 20x20 kanji
>lucida/unicode.10.font for 24x24 kanji
>lucida/unicode.14.font for 32x32 kanji
>lucida/unicode.16.font for 40x40 kanji
>lucida/unicode.20.font for 48x48 kanji
Now, I'm incorporating those as:
lucidasans/unicode.6.font for 10x10 Kanji
lucidasans/unicode.7.font for 12x10 Kanji
lucidasans/unicode.8.font for 14x14 Kanji
lucidasans/unicode.9.font for 16x16 Kanji
lucidasans/unicode.10.font for 20x20m Kanji
lucidasans/unicode.13.font for 24x24 Kanji
lucidasans/boldunicode.10.font for 20x20b Kanji
I appllied medium fonts to those tentatively, althoughwe lack other
bold faces. This is also true for typeunidoee.*.font.
I'm now, then, using lucidasans fonts as our default fonts, because I felt
lucida fonts are too light...
The default acme proportinal font is lucidasans/euro.8.font, and I replaced
this by lucidasans/unicode.9.font for 1600x1200 desktop, and lucidasans/
unicode.8.font for 1024x768 notebook. This is because 14x14 dotts Kanji
font does not always present right Kanji. The lucidasans/unicode.7.font
may help you when you are using lower resolution display...
Kenji
next reply other threads:[~2001-02-19 2:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 2:13 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-20 3:14 suzuki
2001-02-19 2:18 okamoto
2001-02-19 2:11 suzuki
2001-02-15 4:50 okamoto
2001-02-13 7:24 okamoto
2001-02-13 5:35 okamoto
2001-02-09 4:16 okamoto
2001-02-09 3:41 rob pike
2001-02-09 3:34 okamoto
2001-02-09 3:14 rob pike
2001-02-09 3:06 okamoto
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=20010219021402.ECF29199E4@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).