Around 11 o'clock on Nov 15, Tomohiro KUBOTA wrote:
> I am now interested in a project which is trying to use Xft. > However, I cannot find how to use Xft. The Xft(3) manual > describes not many features and, furthermore, the manual says > that Xft will be changed radically. You can read a nearly complete manual included in my XFree86 technical conference paper (http://xfree86.org/~keithp/talks). Xft is changing radically, but I'm trying to provide reasonable compatibility to the new version. The largest change in the API is that while the existing Xft exposes a font-dependent encoding to applications, the new version exposes a strict Unicode API alongside a bare glyph API for applications accessing the underlying FreeType data structures. For TrueType fonts, there is no functional change here; Xft only supported the Unicode encoding in those fonts in any case. Probably the most radical internal change is that the library has been split into two pieces -- a minimal X interface library (Xft) and the X-independent font configuration and matching code (tentatively named 'fontconfig'). For shared library users, this causes no problem but for applications linking statically, build procedures will need to be modified to include this new library. I am attempting to preserve binary compatibility for as many existing applications as possible; certainly the core X applications and libraries that are in heavy use (Qt 2,3/Gtk+ 2) should work just fine. Officially, I should probably issue this with a new major version number; I'd like to avoid that if possible so that existing applications can take advantage of the new features. I should probably commit the new library to CVS so that others can take a peek; anyone interested should let me know. [EMAIL PROTECTED] XFree86 Core Team SuSE, Inc. _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
