>> 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.
TK> There are no standardized way other than XIM to input CJK
TK> languages.
I know. I am sorry about that.
TK> Please develop an alternative protocol if you think so.
This is most definitely a task for the community that uses IMs.
I have no doubt that the community will be able to develop new input
method mechanisms. At any rate, this will become necessary as we move
towards RENDER fonts and away from core fonts.
TK> Canna, Wnn, and SKK themselves are not XIM
I am aware of this fact. I cannot comment on any of these protocols,
as they do not seem to be documented in any language I can read.
Regards,
Juliusz
_______________________________________________
I18n mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/i18n
