Markus Kuhn wrote:
>
> I have tried to use 0xFFFF, but curiously this has caused a space
> character to be displayed for unavailable glyphs instead of
> DEFAULT_CHAR.
That's, um, interesting. A bug in Xlib or the X server, perhaps?
> I have therefore used 0xFFFE as the DEFAULT_CHAR value,
> which is equally guaranteed not to be a valid Unicode character.
I guess this is a good work-around.
> You can download the updated 6x13.bdf font now from
>
> http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html
>
> This font will in the next few days probably be added to the forthcoming
> XFree86 4.0 release, so now is your last chance of testing and reviewing
> it.
I am thinking of adding support for "*-iso10646-1" fonts in Mozilla.
However, I really need to know which glyphs are there. Mark Leisher's
ClearlyU and Roman Czyborra's unifont both provide this info since they
are not fixed width fonts, so their XFontStructs contain the per_char
array, which can be examined for glyphs with non-zero bounding boxes.
How about a font property that contains the glyph ranges? I have not
seen any specs for such a property, but I have seen a system that
returned a property with a name that sounded like this. Maybe it was
CHARACTER_SET_RANGES or something? I can try to find this again if
needed...
Erik
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:45 EDT