Around 22 o'clock on Jun 4, Brian Stell wrote:
> Mozilla also falls back to a language tag based on the locale if > the document does not have one and the encoding of the document's > data does not imply a language. It seems that we need a more complete font matching spec than is provided by CSS2 then; that matching algorithm doesn't mention language tags at all. I'm still relatively optimistic that we can build an algorithm that meets the needs of both Pango and Mozilla; so far, all we've learned is that the current matching algorithm is deficient for both projects, but deficient in very similar ways. I'm going to try to finish getting Pango using my new fancy FcFontSort API to push as much matching from Pango into Fontconfig and then start considering how to take the current CSS2 spec and add language-tags in a sensible fashion. It looks like that will entail adding some new data to the font configuration file. At least *that* part will be easy enough. Keith Packard XFree86 Core Team HP Cambridge Research Lab _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
