From: Tatsuya Kinoshita <tats@vega.ocn.ne.jp>
To: czkmt@remus.dti.ne.jp, emacs-devel@gnu.org
Cc: nori1@dolphin.c.u-tokyo.ac.jp
Subject: Re: tmm.el: non-ASCII characters with locale-coding-system
Date: Thu, 17 Apr 2008 23:21:31 +0900 (JST) [thread overview]
Message-ID: <20080417.232131.217760969.tats%nobody@tats.iris.ne.jp> (raw)
In-Reply-To: <20080417.011529.240672663.tats%nobody@tats.iris.ne.jp>
On April 17, 2008 at 1:15AM +0900,
tats (at vega.ocn.ne.jp) wrote:
> > The patch is created by Tetsuo Tsukamoto (czkmt at remus.dti.ne.jp)
> > at http://mail.ring.gr.jp/skk/200803/msg00009.html to prevent a
> > problem of displaying Japanese characters with tmm.el reported
> > by Noritada Kobayashi at Debian BTS http://bugs.debian.org/470646.
[...]
> Hmm, the encoding scheme is decided as follows, quoting from
> skk-e21.el:
>
> | (defvar skk-e21-coding-system (cond
> | ((memq window-system '(w32 nil))
> | nil)
> | ((and (boundp 'mac-carbon-version-string)
> | window-system
> | (find-coding-system 'utf-8))
> | 'utf-8)
> | (t
> | locale-coding-system)))
>
> Should it be set to 'utf-8? What's the correct way to handle a
> non-ASCII character of a menu item?
Wow, I set skk-e21-coding-system to nil, and then the problem has
gone away. The SKK Japanese menu item can be displayed with tmm.el
and also with the menu bar.
Tetsuo, is locale-coding-system really needed? If not, please set
skk-e21-coding-system to nil by default.
Thanks,
--
Tatsuya Kinoshita
prev parent reply other threads:[~2008-04-17 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 13:09 tmm.el: non-ASCII characters with locale-coding-system Tatsuya Kinoshita
2008-04-16 15:38 ` Stefan Monnier
2008-04-16 16:15 ` Tatsuya Kinoshita
2008-04-17 14:21 ` Tatsuya Kinoshita [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080417.232131.217760969.tats%nobody@tats.iris.ne.jp \
--to=tats@vega.ocn.ne.jp \
--cc=czkmt@remus.dti.ne.jp \
--cc=emacs-devel@gnu.org \
--cc=nori1@dolphin.c.u-tokyo.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.