9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] fixes to unicode fonts (not in the plan9 distribution)
Date: Tue, 22 Jul 2003 17:23:31 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0307221616420.11184-100000@fbsd.cpsc.ucalgary.ca> (raw)

If you're using any of the 10646 fonts converted to plan9 recently you may
have observed that some of the characters are missing (most notably -- tilde
(~) isn't there).

this was traced to a bug in bdf2subf which caused the last glyph of any
subfont not to be displayed. corresponding man page snippet from cachechars(2):

	 The info array has n+1 elements, one each for characters 0 to n-1 plus
	an additional entry so the size of the last character can be calculated.
	Thus the width, w, of the Image associated with a Subfont s is
	s->info[s->n].x.

bdf2subf wasn't creating the n-th array index.

the new, updated packages are on the web at the same place:

	http://pages.cpsc.ucalgary.ca/~mirtchov/p9/fonts/

including even the 18x18ko korean glyphs we couldn't encode the last time.

I've tested all fonts to the best of my knowledge using 'unicode
0x0-0xffff'.

andrey

ps: the fonts that look the best are:


 	10x20 6x13 7x13 8x13 9x15 9x18

pps: i've started the efonts conversion, but that'll take a few hours. then
testing is a few more, so wait until tomorrow to download ~70mb of fonts :)






             reply	other threads:[~2003-07-22 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 23:23 andrey mirtchovski [this message]
2003-07-23  5:55 ` Skip Tavakkolian

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=Pine.LNX.4.44.0307221616420.11184-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).