9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Chris Hollis-Locke" <chris@hollis-locke.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Thai Chicken
Date: Tue, 24 Feb 2004 23:04:13 +1300	[thread overview]
Message-ID: <004301c3fabd$afe99670$0a8b58db@laptop> (raw)
In-Reply-To: <20040224101119.0136e11b.martin@parvat.com>

I looked into this when thinking about doing a font server for Inferno.
The problem is that the remapping file really has to be hand written on a
face by face basis as there is no suitable font metric against which to
automatically decide on the mapping.  Faces of the same 'height' can vary in
rendered size dramatically - think Arial Vs. Dunhill - they just will not go
together.  This greatly complicates the way the draw device would have to
handle baselines and the sizing of its cached subfont image.  This also
skirts around the fact that the han unification area should have separate
renderings, an automatic mapping could end up being composed of renderings
specific to different locales.

Just my $0.02
Chris.

----- Original Message -----
From: "Martin C.Atkins" <martin@parvat.com>
To: <9fans@cse.psu.edu>
Sent: Tuesday, February 24, 2004 5:41 PM
Subject: Re: [9fans] Re: Thai Chicken


> On Mon, 23 Feb 2004 17:46:05 -0500 dbailey27@ameritech.net wrote:
> > Hm, I think I get this.
>
> What I never understood was why there isn't a "if the character isn't
found,
> then look in *this* font" entry.
>
> OK, this could recurse, etc horribly (and that would have to be
> avoided somehow), but the advantage is that a single font could be
> defined with all the Unicode characters, and made the default for the
> other fonts. Then every font would be complete, and we wouldn't have
> had this discussion!!!
>
> Martin
>
> --
> Martin C. Atkins martin@parvat.com
> Parvat Infotech Private Limited http://www.parvat.com{/,/martin}
>



  parent reply	other threads:[~2004-02-24 10: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
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 [this message]
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='004301c3fabd$afe99670$0a8b58db@laptop' \
    --to=chris@hollis-locke.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).