> Fontconfig uses a new naming scheme which is currently "similar" to CSS2 > in design and will move closer to CSS2 in the near future as there's no > real reason to be gratuitously incompatible. > > While fontconfig provides a text representation for font names, most > applications that use it use the structured representation instead which > is easier for applications to deal with. > > Fontconfig has a brand new manual page, and I just wrote a paper on it that > I'm hoping to present next month at Guadec. As with lots of other papers > I've done, that is available at: > > http://xfree86.org/~keithp/talks
What user is Fontconfig for? End user? Applications? It's very nice that font configuration will be easier, but I wouldn't like to see that faces / colors are accidentally altered by this. An interface for the-very-end user should be as easy as possible, like, ``I want to use Adobe Helvetica for default face. Adobe Courier for type face.'' Graphical applications (WWW browser, drawing tools, or tookits) are special in that they need many kind of faces, colors, scales, and so on. For other purposes we need only a very small set of faces. (Imagine LaTeX.) A font API should provide a low level interface for these applications. And other applications should use only a higher interface to avoid such a situation that windows have different faces in their toolbars. In short, the design can be more layerd, IMHO. But thanks, my life is really getting better off by your works. Regards, Masao _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
