Around 16 o'clock on Sep 29, Brian Stell wrote:
> While font matching may be done by a layer above Xft, it would > probably help if Xft could render from the list selected from > the layer above. Mozilla implements this by having a list of > fonts, mLoadedFonts, that the measuring/drawing code scans. The > the first font in the loaded fonts list that has a glyph for > the character is used. Now that's a good idea -- allow the application to hand additional fonts to Xft to "fill-in" the holes. Applications would then be in control of how those additional fonts were selected if they so chose. Would you like a per-font callback invoked when an attempt to access non-existant glyphs was made? Or should the application detect this case before presenting data to the library? > Regardless of the order in which character are encountered > the list must always have the same fonts in the same order. > Moz does this by have a place holder for each font regardless > of whether a X font was actually needed (eg: loaded). Thus > the mLoadedFonts list holds the font placeholders and only > when needed is a font is actually loaded into the placeholder. Yes, of course. That would be automatically handled if Xft started caching FreeType faces. [EMAIL PROTECTED] XFree86 Core Team SuSE, Inc. _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
