From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Cc: ext@sidvind.com
Subject: Re: [gentoo-user] emacs and asian languages
Date: Sun, 20 Jul 2008 20:09:24 -0400 [thread overview]
Message-ID: <20080720200924.2a17f449@osage.osagesoftware.com> (raw)
In-Reply-To: <4883BD75.9080800@sidvind.com>
On Mon, 21 Jul 2008 00:34:29 +0200
David Sveningsson wrote:
> David Relson skrev:
> > On Sun, 20 Jul 2008 22:29:15 +0200
> > David Sveningsson wrote:
> >> This sounds like a font issue to me. Can you see the characters
> >> correctly if you cat the files?
> >
> > Hi David,
> >
> > Using a Gnome terminal and the default character set "Current Local
> > Ansi_X3.4-1968" all the asian characters are bad. Using "Unicode
> > (UTF-8)" all look good. So cat'ing _does_ work properly.
> >
> > On the plus side, being able to display correctly in (1) a Gnome
> > terminal and (2) in Eclipse's source code window (which uses
> > "Monospace") and (3) in a Claws-Mail window indicates that all
> > needed fonts are available.
> >
> > On the minus side, e experiments to change emacs' mule encoding to
> > ascii, chinese, and utf-8 don't seem to have any effect :-<
> >
> > And in an emacs *shell* window (with "mule...set UTF-8", the strings
> > show up like:
> >
> > String sh = "zh: \344\270\226\347\225u"\345\245\275";
> >
> > which interprets as the octal codes corresponding to UTF-8 char.
> >
> > David
> >
> >
>
> I assume you are using xemacs, does it work if you're not using
> xemacs (use the -nw flag when launching)? I have never used mule
> myself as it is not needed with emacs 22. Since everything seems to
> work in your terminal I cannot see why it wouldn't work in emacs, but
> I'm not an expert.
>
> Just to be sure, have you followed the steps in
> http://www.gentoo.org/doc/en/utf-8.xml?
> --
I've got both emacs and xemacs installed. Using xemacs, most of the
chinese, japanese, and korean characters show up as hex codes like
\226. emacs does the better job (with japanese being correct).
I've looked at the utf-8.xml page and what I've got is a combination of
en_US.UTF-8 and "C" (see the end of this message).
My 2.6.24 kernel has iso8859-1 as its default and I'm rebuilding with
UTF-8 as the default to see if this helps.
Regards,
David
****************************************************
In /etc/locale.gen is:
en_US.UTF-8 UTF-8
In /etc/profile.env is:
export LANG='en_US.UTF-8'
In /etc/env.d/02locale.gen is:
LANG="en_US.UTF-8"
"env-update" and "source /etc/profile" have been run.
Running "locale" reports:
LANG=en_US.UTF-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C
Running "locale -a" reports:
C
POSIX
en_US.utf8
next prev parent reply other threads:[~2008-07-21 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 14:12 [gentoo-user] emacs and asian languages David Relson
2008-07-20 20:29 ` David Sveningsson
2008-07-20 21:50 ` David Relson
2008-07-20 21:57 ` David Relson
2008-07-20 22:34 ` David Sveningsson
2008-07-21 0:09 ` David Relson [this message]
2008-07-21 13:08 ` Hong Hao
2008-07-21 13:49 ` David Sveningsson
2008-07-21 22:58 ` David Relson
2008-07-22 6:27 ` David Sveningsson
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=20080720200924.2a17f449@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=ext@sidvind.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox