Juliusz Chroboczek <[EMAIL PROTECTED]> writes:
> >> However, XIM support imposes that we use font sets, thus pulling in
> >> a whole new range of bugs.
>
> TK> Are you saying that nothing should be added to XTerm?
>
> No. I am not objecting to the use of fontsets. I am objecting to the
> facts that XIM (i) imposes the use of a specific output mechanism, and
> (ii) makes it visible to the application. (Either of those alone
> would be an issue, but XIM has both.)
>
> Think of a client that never sees core fonts or fontsets, but only
> uses RENDER client-side fonts, or DPS fonts, or GL pseudo-fonts, or
> whatever. It should be possible to write such a client with no
> reference to core fonts or fontsets; but XIM precludes this. In other
> words, your choice of input mechanism imposes that you must use a
> given output mechanism. I consider this a design flaw in XIM.
Only for the over-the-spot input style. You can use on-the-spot
and root-window input styles with XIM without encountering this
problem, and that's what GTK+-2.0 does.
(XIM has other issues, and hopefully we'll see a move to something
better, perhaps IIIMF, someday. But certainly its possible to
use XIM without using over-the-spot rendering.)
Regards,
Owen
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
