Keith Packard wrote:
> ...
> 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?
The app should be able to present a list but my gut level feeling
is a callback is needed.
> > 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.
This is not a caching issue. The concern is that, if for example
there are 27 fonts needed to display unicode then regardless of
whether the 27 font is needed 1st or not, the font placeholders
in the list are in the same order. Number 27 is always #27 in
the list.
Brian Stell
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
