What happens when the iso10646 font does not have all the
char/glyphs in a iso8859-x encoding?
The strageties I can think of are:
1) produce a iso8859-x font with missing glyphs
This seems likely to cause "blank" chars to be
displayed. It's my impression that most X apps tend
to assume that non-iso10646 X fonts have all the
glyphs in the encoding and do not actually query the
font for the valid glyph list. Without knowing the
valid glyph list there is no way to fill in the
missing glyphs from other fonts.
2) don't make the iso8859-x font
Markus Kuhn wrote:
>
> "Mike A. Harris" wrote on 2002-02-04 08:27 UTC:
> > Do I understand correctly that the xfs font server and also the
> > Xserver can both now re-encode ISO10646 BDF fonts on the fly to
> > the various ISO8859-* and other encodings?
>
> I don't think so. At the moment, we use the Perl script ucs2any
> in order to recorde the ISO10646-1 BDF files at font file
> installation time.
>
> > If it does not do this currently, is anyone already working on it
> > or planning to?
>
> Juliusz has though about it several times, and each time decided that
> he doesn't feel like doing it and that he got fed up with BDF/PCF.
> I'm not aware of any plans or progress here.
>
> Markus
>
> --
> Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
> Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
>
> _______________________________________________
> Fonts mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/fonts
--
Brian Stell
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
