On Sat, Aug 02, 2003 at 10:10:03PM +0900, Jungshik Shin wrote: >On Sat, 2 Aug 2003, Chisato Yamauchi wrote: > >> Although the pliability of handling such special fonts is also important, >> non BMP plane in XLFD is now the most important problem. Confusion is >> already seen such as linux-utf8 list. An official definition should be >> indicated right now. Why has XFree86 left this? > > That's because XFree86 is moving away from 15year-old XLFD-based >approach. As Owen wrote, we'd better let that poor thing rest in peace >and move along. With fontconfig/Xft, we don't need to worry about XLFD >any more except for the sake of backward compatibility. For non-BMP >characters, there isn't much issue with back. comp. to worry about.
Just so people don't get the wrong idea about what "XFree86" is doing, core (server-side) font support will continue to be supported and maintained while ever there are sections of our user base that need it. The same is true of our inclusion of the 'xtt' module as an alternative to the 'freetype' module. Non BMP planes in XLFD hasn't been addressed by XFree86 because it wasn't a pressing issue for anyone. It is being addressed now via this discussion. Since few people seem to be interested in this issue, and if the death of XLFD is imminent, then it's probably good enough for those who are interested to agree on how to handle it according to their needs. > Yeah, TTCap is useful, but it appears that we're trying to solve the >wrong problem turning away from the real issue. The real problem is >that we don't have quality CJK fonts in multiple styles. A practical engineering solution is about getting the results you need today with the resources available. It doesn't matter if TTCap one day becomes unnecessary because of the availability of better fonts. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
