From: Rob Pike <rob@mightycheese.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Thai Chicken
Date: Tue, 24 Feb 2004 08:04:30 -0800 [thread overview]
Message-ID: <21148210-66E3-11D8-A0FF-000A95B984D8@mightycheese.com> (raw)
In-Reply-To: <20040224150553.1dbff498.martin@parvat.com>
> Surely it would be better if every font contained a full Unicode set
> (without
> any bloat/duplication)?
without any bloat? no chance. unicode has gotten bloated lately.
linear B, anyone?
there are several reasons why the fonts aren't all full:
1) unicode keeps growing, so they can only be full temporarily.
2) it's easy to forget, but there were no unicode fonts when plan 9
adopted
unicode. bigelow and holmes made lucida sans unicode for us, and
that
was the first - still partial, even today - unicode font. in other
words, font
coverage is spotty.
3) for many applications, you don't want the full set of fonts and
there is no
need to pay the full memory footprint for them.
4) on slow lines, it can be very painful to cat a file by mistake that
has a lot
of unusual characters, such as a binary file or a japanese file when
working
in ascii. try a drawterm across the country and run unicode
8000-B000 or
something like that.
number 4 may be mitigated by improving networks, but in the early days
of plan 9 only the diehards ran with a relatively full font set.
-rob
next prev parent reply other threads:[~2004-02-24 16:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 22:46 dbailey27
2004-02-23 21:56 ` boyd, rounin
2004-02-23 22:51 ` dbailey27
2004-02-24 4:41 ` Martin C.Atkins
2004-02-24 3:57 ` andrey mirtchovski
2004-02-24 8:05 ` [9fans] plan9 web server vdharani
2004-02-24 4:51 ` andrey mirtchovski
2004-02-24 8:32 ` vdharani
2004-02-24 7:33 ` Fco.J.Ballesteros
2004-02-24 8:17 ` boyd, rounin
2004-02-25 0:34 ` vdharani
2004-02-24 22:14 ` David Presotto
2004-02-24 9:35 ` [9fans] Re: Thai Chicken Martin C.Atkins
2004-02-24 9:43 ` Charles Forsyth
2004-02-24 8:52 ` boyd, rounin
2004-02-24 9:53 ` Geoff Collyer
2004-02-24 16:04 ` Rob Pike [this message]
2004-02-25 5:52 ` Martin C.Atkins
2004-02-25 5:13 ` andrey mirtchovski
2004-02-25 8:46 ` Chris Hollis-Locke
2004-02-26 5:51 ` boyd, rounin
2004-02-25 19:53 ` rog
2004-02-24 10:04 ` Chris Hollis-Locke
2004-02-24 10:47 ` Lucio De Re
2004-02-25 12:40 ` Dave Lukes
2004-02-25 12:54 ` Lucio De Re
2004-02-26 5:59 ` boyd, rounin
2004-02-28 5:44 ` Martin C.Atkins
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=21148210-66E3-11D8-A0FF-000A95B984D8@mightycheese.com \
--to=rob@mightycheese.com \
--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).