From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] scat and latin1.6
Date: Mon, 27 Sep 2004 13:03:09 -0600 [thread overview]
Message-ID: <aa5ff50cedc2fec987bba0db4a728ca0@plan9.ucalgary.ca> (raw)
scat uses the following font when plotting objects:
/lib/font/bit/lucida/unicode.6.font
unicode.6.font defines 0x0 to 0xff to use the file named 'latin1.6'
which doesn't exist in /lib/font/bit/lucida. there are two other
files, namely latin1.6.0 and latin1.6.1 with which scat works fine.
is there a bug in the .font file or has anything else changed? was
cachechars ever supposed to find out the depth of the font image file
itself? scat used to work a couple of years ago but i have no dumps
from that time so i have no idea whether the font was removed at some
point.
by the way, exporting "The Digitized Sky Survey, 102 CD-ROMs" as a
(grid) service on sources could be a good idea ☺
andrey
next reply other threads:[~2004-09-27 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 19:03 andrey mirtchovski [this message]
2004-09-28 0:40 ` Rob Pike
2004-09-28 1:48 ` andrey mirtchovski
2004-09-28 5:38 ` Kenji Okamoto
2004-09-28 5:40 ` Kenji Okamoto
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=aa5ff50cedc2fec987bba0db4a728ca0@plan9.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).