9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Thai Chicken
Date: Wed, 25 Feb 2004 19:53:59 +0000	[thread overview]
Message-ID: <cb1442450af0384c5d2d070d100363e9@vitanuova.com> (raw)
In-Reply-To: <20040225112245.0739a51b.martin@parvat.com>

> Please, I'm not trying to make a row. I simply don't understand why this seemingly
> obvious solution, apparently has problems I don't understand! Or is the 'problem'
> simply that "no-one has got around to doing it yet" - which is fine!)

one "obvious" reason why this is a problem is that fonts don't
necessarily come in all sizes.  there's no point in my tiny 7 point
font dragging in chinese chars from a much larger font - either
they'll be truncated, or the tiny font will have a much larger height
than it should.

i guess that's an argument for on-demand rendering of scalable fonts,
but that's not a trivial problem, as chris found out...

i have to say i'd like to see a more standard convention for naming
fonts; i very rarely use other than the standard acme or rio fonts,
(although i'd sometimes like to) and the fact that fonts have no
consistent naming scheme doesn't really help.

just the act of grouping a load of consistent fonts in one place, as
chris did for charon, helps a lot:

	charon/(bold cw italic plain).(tiny small normal large vlarge).font

at least then i can remember where to find typefaces that more-or-less
go with one another, and have as large a coverage as is possible,
consistent with the font appearance.



  parent reply	other threads:[~2004-02-25 19:53 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
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 [this message]
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=cb1442450af0384c5d2d070d100363e9@vitanuova.com \
    --to=rog@vitanuova.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).