From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new links binary+source
Date: Fri, 19 Dec 2003 15:49:25 +0900 [thread overview]
Message-ID: <c1a7ba2de19a3028b88d5115715d96b2@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <Pine.LNX.4.44.0312182315230.11619-100000@fbsd.cpsc.ucalgary.ca>
> in my estimation we need about 10-12 different heights from each different
> font that people may be thinking of using to cover a reasonable set of
> people's desires..
How about to use lucida and lucidasans, where I have many sizes.
Kenji
prev parent reply other threads:[~2003-12-19 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 21:03 mirtchov
2003-12-17 21:23 ` Axel Belinfante
2003-12-18 2:16 ` okamoto
2003-12-18 2:33 ` Geoff Collyer
2003-12-18 2:52 ` okamoto
2003-12-19 6:10 ` okamoto
2003-12-19 6:20 ` andrey mirtchovski
2003-12-19 6:41 ` okamoto
2003-12-19 14:15 ` mirtchov
2003-12-19 6:49 ` okamoto [this message]
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=c1a7ba2de19a3028b88d5115715d96b2@granite.cias.osakafu-u.ac.jp \
--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).