unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs failes to communicate with other X clients
Date: Mon, 26 May 2003 16:09:41 +0900 (JST)	[thread overview]
Message-ID: <200305260709.QAA13971@etlken.m17n.org> (raw)
In-Reply-To: <usmr21bsz.fsf@knight.6test.edu.cn> (message from Robin Hu on Mon, 26 May 2003 06:06:52 +0000)

In article <usmr21bsz.fsf@knight.6test.edu.cn>, Robin Hu <huxw@knight.6test.edu.cn> writes:
>     Of course Hangul characters can not be received when
> we set locale to zh_CN.GBK, but I think this is the right
> behavior. For example, while I set keyboard-coding-system
> to chinese-gbk, I can not input Hangul characters, because
> it's my responsibility to set correct keyboard coding
> system for chinese input. So I think that's also my
> responsibility to set correct locale for X paste.

The reason why you can't input Hangul characters is that
your input method doesn't support it or it generates data
only in chiense-gbk encoding which can't contain Hangul
characters.

Provided that you have an input method that produces both
Chinese and Hangul and sends data to Emacs in compound-text
encoding, and you set keyboard-coding-system to
compound-text, Emacs should accept all characters, shouldn't
it?

Emacs is a multilingual editor and its functionality should
not be limited by locale.

>     Another problem with current implementation is, some
> characters can be encoded in different char-settings. For
> example, I set file coding system to chinese-iso-8bit, and
> selection coding system to compound-text-with-extension,
> and copy/paste a very long chinese article from
> mozilla. Every thing seems to go fine, but this article
> just cannot be saved. This is because X encode some
> characters as if they are not chinese-iso-8bit characters,
> but emacs decode them to emacs-mule successfully, and
> finally file coding system cannot encode emacs-mule to
> chinese-iso-8bit.

In that case, Emacs asks you to select some of safe coding
systems.  If your Emacs supports chinese-gbk, it should also
be listed as a safe coding system.  I think that behaviour
is better than refusing characters not supported by
chinese-iso-8bit from the beginning.

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

>     Chinese-gbk is my extension to Emacs, I believe I have
> post it in m17n's maillist.

Oops, then, I'm very sorry that I completely forgot about
that mail.  Could you send it to me again?  Then I'll check
why:

>    Yeah, icccm list had been appended with GBK-0, that's why my emacs
>    can decode some gbk characters correctly, but problems are still
>    there. In the example I gived in the previous post, one embeded gbk
>    character will make all characters fail to be decoded. ;-(

that happens.

By the way, the name non-standard-icccm-encodings-alist is
wrong.  "icccm" should actually be "ctext".  I'll fix it
soon.

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

  reply	other threads:[~2003-05-26  7:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23  9:19 Emacs failes to communicate with other X clients Robin Hu
2003-05-23 17:22 ` Eli Zaretskii
2003-05-24 11:10   ` Robin Hu
2003-05-24 17:38     ` Eli Zaretskii
2003-05-26  2:56       ` Robin Hu
2003-05-26  4:54         ` Kenichi Handa
2003-05-26  6:06           ` Robin Hu
2003-05-26  7:09             ` Kenichi Handa [this message]
2003-05-26  8:42               ` Robin Hu
2003-05-27 12:26                 ` Kenichi Handa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200305260709.QAA13971@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).