yao zhang wrote:
> ...
> The 'character set' idea will be very help. Internally, the unicode
> char map is really a bitset. "An ascii formatted version of" the bitset can
> be specified in a font pattern. But a group of pre-defined bitsets should also
> be specified by the "character set" part of an existing standard (not the
> "encodinging" part of the standard): "Latin-1", "GB2312", "BIG5", "CJK
> Unified Ideographs", etc. Those string constant are just aliases to the
> underline unicode char maps.
> It is very useful since most existing fonts
> are design for one particular character set of a standard anyway.
This may have been (generally) true of X fonts but TrueType fonts
are being designed for Unicode and do not support all of Unicode.
> > The application is expected to compute the set of glyphs needed to
> > represent the data.
Not all apps know which characters will be needed when until after the
font is needed/loaded.
Consider:
browser display a pages "as they arrive"
word processors display pages "as the user types"
--
Brian Stell
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
