From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese Font
From: okamoto@granite.cias.osakafu-u.ac.jp
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-mxfmnnjxhfzntvwssxrubxghxg"
Message-Id: <20010209033524.BBBFB199EF@mail.cse.psu.edu>
Date: Fri,  9 Feb 2001 12:34:41 +0900
Topicbox-Message-UUID: 5f761f98-eac9-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-mxfmnnjxhfzntvwssxrubxghxg
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hmm, my English has big problem...

I have now compressed subfont images for 32 bitts Kanji font, and I can see
those by tweak, and which was my test to compare the 16 and 24 bitts fonts
between yours and mine.

Now, I'm going into next step, ie. to make Kanji subfonts non-multiple of eight,
such as 14 dotts, 12 dotts and even 8 dotts.  To achieve those, we need an
algorism (of course, we can do it only by strong force, too :-)) to pack redundant
bitts included in BDF BITMAP lines.  For an example, each bitmap of k14.bdf file
includes 14 lines as below lines:  (those are expressed as hexadecimal number)

x000 0000 0000 000x
x000 0000 0000 000x
         ....
x000 0000 0000 000x

where 'x' bit are the redundant bit, and are always 0.

I think we have to eliminate all the redundant 'x' to make 14x14 bit subfont
image.

Kenji


--upas-mxfmnnjxhfzntvwssxrubxghxg
Content-Type: message/rfc822
Content-Disposition: inline

Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by granite.cias.osakafu-u.ac.jp; Fri Feb  9 12:12:42 JST 2001
Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2])
	by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id MAA03307;
	Fri, 9 Feb 2001 12:16:01 +0900
Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6])
	by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-01020211) with ESMTP id MAA28337;
	Fri, 9 Feb 2001 12:15:31 +0900 (JST)
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id 6F66E199FA; Thu,  8 Feb 2001 22:15:09 -0500 (EST)
Received: from plan9.cs.bell-labs.com (ampl.com [204.178.31.2])
	by mail.cse.psu.edu (CSE Mail Server) with SMTP id D7F5F199E1
	for <9fans@cse.psu.edu>; Thu,  8 Feb 2001 22:14:49 -0500 (EST)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese Font
From: "rob pike" <rob@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010209031449.D7F5F199E1@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Thu, 8 Feb 2001 22:14:37 -0500

Pack the characters as tightly as you can without overlap.  The associated
width information (Fontchar) has sufficient information to extract them.
	tweak /lib/font/bit/lucidasans/lsb.24
(or any other subfont file) to see what a subfont looks like.

If you have a routine that can extract a single character image from the
.bdf file, then draw() is all you need to pack the pixels.

-rob

--upas-mxfmnnjxhfzntvwssxrubxghxg--