On Tue, 16 Dec 2003, Matsumoto, Masakazu wrote:
>   BTW, did you design grayfont.c compatible to double-byte characters?

Not quite.  It's compatible with double-byte characters, yes, but the
antialiased fonts require a contiguous range of character numbers,
otherwise space is wasted.  Moreover, there is a 64K limit on the glyph
info.  Since each glyph info record takes 12 bytes, this means that there
is about a 5300 character limit--and all must lie in a contiguous
range.  I don't know if 5300 characters is reasonable for CJK use or not.

The "contiguous range" issue is easily handled--just put into a font
package a new resource that specifies a mapping table, and then modify
grayfont.c to look for that resource, and use it when available.  The
trick is making a mapping table that can be easily searched through.  If
all of the characters can be contained within a 30000 character contiguous
range, then the table can be a simple lookup table.  Otherwise, a binary
search might be needed, which would be slow, or else some other trick.

The 5300 character limit could be handled in some way or other.

All of this would require modifications to PalmFontConv.  Currently,
topalmtext only converts characters in the 0-255 range, and togray is also
similarly limited.  These limits are very easy to remove, but unicode or
other mapping tables must be supplied.  I will be happy to commit a patch
to the PalmFontConv project, as long as any extensions to the file format
are fully documented.

All that said, we're talking about enormous bitmap files.  Since all of
the data gets loaded into RAM, this may be a problem.

Alex

--
Dr. Alexander R. Pruss  || e-mail: [EMAIL PROTECTED]
Philosophy Department   || online papers and home page:
Georgetown University   ||  www.georgetown.edu/faculty/ap85
Washington, DC 20057    ||
U.S.A.                  ||
-----------------------------------------------------------------------------
   "Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
       - Paul of Worczyn (1424)

_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to