On Fri, 15 Aug 2003, Dave Maddock wrote:
> Since I've been playing with the unicode functions in the parser and
> viewer, I think I may have a viable idea for displaying unicode
> characters. This is kind of how my i-mode patch works (only using
> bitmaps instead of fonts of course).
>
> The big problem is that PalmOS doesn't support unicode so to display
> non-Latin 1 characters we need to create custom fonts. However, as I
> understand it, you can't create a palm font with more than 255
> glyphs--but we can create several 255-glyph fonts.
My gray-scale font code supports fonts with more than 255 glyphs. It
would be trivial to add a black-and-white only extension to the format.
The current format however requires an entry, perhaps a blank one, for
every glyph within a range of glyph numbers. If the glyph numbers jump
around too much, then this is a waste of memory. But it would be easy to
extend things with a binary search for non-sequential glyphs. But the
speed may be too low. (A best solution for occasional Unicode might be to
require sequential numbers with no skips in the 0-255 range, and then
allow things to jump around.)
> As the viewer will always use the built-in Palm fonts over external
> font pdbs, the viewer is always forward-compatible.
How will this work with my custom font loading?
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
