Re: [Render] OpenType support in Pango

[Keith Packard <keithp keithp com>]

> My only (somewhat hypothetical) concern with this method is there
> might be two fonts matched by a pattern, one of which has a 
> iso10646 charmap, one which doesn't. When I load the font with
> "glyph-unencoded", if I get the font without the iso10646 
> charmap, then its hard to fix things up.

Hmm.  I'll have to think about this, perhaps you're right and an 
additional field in the font name could be "unencoded" which had the match 
occur on the encoding but then didn't use that encoding for rendering.

> Hmmm. Does this mean that I can't assume that the FT_Face for a
> particular XftFont will stay the same over time? (I assume the reason
> for this call is so you can unshare as necessary.)

No.  A font is derived from a fixed face, the reason is that many fonts 
may be generated (at different sizes) from the same face.  The code you 
have loads the face multiple times wasting memory.  Additionally, I also 
share fonts now so that you'll get the same pointer back if the resulting 
glyphs would be identical (including encoding and optional rendering 
features).

keithp keithp com	 XFree86 Core Team		SuSE, Inc.