9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Martin C.Atkins <martin@parvat.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Thai Chicken
Date: Sat, 28 Feb 2004 11:14:27 +0530	[thread overview]
Message-ID: <20040228111427.7d734606.martin@parvat.com> (raw)
In-Reply-To: <1077712856.17036.35.camel@zevon>

Sorry, I was out of the office for a couple of days...

On Wed, 25 Feb 2004 12:40:56 +0000 Dave Lukes <davel@anvil.com> wrote:
> > What I never understood was why there isn't a "if the character isn't found,
> > then look in *this* font" entry.
>
> Danger, Will Robinson, Danger!  That way lies TrueType.

Most of the arguments against my suggestion seem to fall into:

1) It will be difficult to find fonts that work well together

2) If badly configured, the consequences could be horrible

3) My suggestion is too hacky

4) Sometimes one doesn't need/want this

To address these in turn:
1) It will be difficult to find fonts that work well together:
Maybe. However, having characters "disappear" isn't too good either!
(unless one accidentally cat'ed a binary, in which case you don't really
care what the output looks like. In other cases, presumably the
characters were there for some purpose?)

2) If badly configured, the consequences could be horrible
This is true of just about everything in software (and elsewhere).
So don't configure it badly - at least you would have another option
to help with the configuration.

3) My suggestion is too hacky
Possibly: I was hoping that people could suggest better approaches
that would solve the problem, rather than just saying "Ugh, that's
horrible". For example, one could introduce a new layer in the font
files, with the first layer defining the font size, and a list of
second-layer files to be searched in order for glyphs. The second
layer would be much like the current font files, but without the font
size information, and the last layer would be the current sub-font
files. This would solve the "recursion" problem, and provide a common
font size across all the files, but was a more dramatic change than I
wanted to propose.

4) Sometimes one doesn't need/want this
So have some fonts that don't use the new mechanism! No-one is saying
that every font *has* to have a default, or that all fonts have to
have the *same* default. If this is *sometimes* useful, then is it
worth the costs? That is surely the trade-off that we, as engineers,
should be discussing? (The answer might well be "no", but surely
there is some balance of cost/benefits one way or the other?)

Martin

--
Martin C. Atkins			martin@parvat.com
Parvat Infotech Private Limited		http://www.parvat.com{/,/martin}


      parent reply	other threads:[~2004-02-28  5:44 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
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 [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=20040228111427.7d734606.martin@parvat.com \
    --to=martin@parvat.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).