MK> So I think, we can now drop bdftruncate from the ucs-fonts installation
MK> procedure, as people merely have to add [0_0x31ff] to an XLFD to achieve
MK> the same effect.
MK> Any opinions?
JC> I don't think it is a good idea.
Sorry, I was in a rush yesterday evening and didn't have time to be
more explicit.
Bdftrucate should stay. All the current UTF-8 clients that I know do
not use the subrange XLFD hack, and so dropping bdftruncate would
strongly penalise them. Writing new clients that split a iso10646-1
font into pieces using the XLFD subrange extension is a loss of time,
as new clients should just use Xft and forget about the core fonts
Xlib support (or only use it as a fallback).
An alternative would be to add a server option to castrate iso10646-1
fonts on the fly in the BDF and PCF backends.
Juliusz
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
