Around 10 o'clock on Dec 14, Steve Swales wrote:
> Since render is not yet a standard extension, and making this change would > disable Xft on all commercial X servers aside from XFree86, I would caution > against it at this time. The idea is to provide a core-protocol fallback where the Render extension is not yet available. I agree that without this, Xft would become significantly less useful. I beleive switching from server-side fonts to client-side fonts will dramatically improve the utility of Xft for sophisticated application development, especially as we move to more accurate presentation of information in a wide variety of languages. I've implemented systems like this in the past and have found that text performance is adequate, even over low speed links. Anti-aliasing might require a high-speed connection, but I think that's reasonable. I think this offers a better solution than the current Xft architecture Right now, when connected to a legacy X server, applications are faced with a very different set of fonts and no access to non-X font data. We loose all of the advantages of client-side fonts from the applications perspective, only serving to further isolate people left without Render support. Keith Packard XFree86 Core Team Compaq Cambridge Research Lab _______________________________________________ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
