Re: Emacs failes to communicate with other X clients

[Kenichi Handa <handa@m17n.org>]

In article <uznla2z61.fsf@knight.6test.edu.cn>, Robin Hu <huxw@knight.6test.edu.cn> writes:
>     My point is that compound-text decoding should be left
> to X itself, rather then by emacs itself. It should be
> better be transparent to emacs, for better portable and
> better extensible.

>     My patch implements this idea, it use
> XmbTextPropertyToTextList to decode compound-text, then
> delegate the result to selection_data_to_lisp_data, who
> will call decode_region with chinese-gbk to translate gbk
> coding characters to emacs-mule. It works fine for me
> these days.

XmbTextPropertyToTextList can handle only such compound-text
that contains characters supported in the current X locale.
So, in your way, if you are in GBK locale, Emacs can't
receive, for instance, Hangul chacaters even if
compound-text can correctly encode Hangul characters and
Emacs itself can handle Hangul in any locales.

So, I beleive we should avoid such kind of change.

By the way, the coding system chinese-gbk is not yet
supported in the current Emacs.  Or, are you using
emacs-unicode?

---
Ken'ichi HANDA
handa@m17n.org