On Fri, 17 Feb 2006 12:07:02 -0500, Michael Jennings <[EMAIL PROTECTED]> wrote:
| On Saturday, 18 February 2006, at 02:12:24 (+0900),
| Yasufumi Haga wrote:
|
| > There was no setting for the encoding in my .xsession at that time,
| > so I guess it should have been ja_JP.eucJP. But when I checked the
| > values of LANG and LC_ALL with two terminals: kterm and Eterm, LANG
| > was ja_JP.UTF-8 and LC_ALL was ja_JP.eucJP in kterm, while in Eterm
| > both LANG and LC_ALL were ja_JP.eucJP. Now I'm setting LANG and
| > LC_ALL to ja_JP.UTF-8 in the .xsession and checking those values
| > again, but they don't change. I tried running gnome-terminal and
| > checking them in this environment, and it resulted in ja_JP.eucJP
| > for both of them. I also understood the state of Eterm.
|
| ja_JP.eucJP is correct for Eterm. I suspect making sure the locale
| uses EUCJ instead of UTF-8 encoding will correct the display problems.
| Remember, this means both the locale Eterm starts in *and* the locale
| of the shell running inside it.
I'm setting LANG and LC_ALL to ja_JP.eucJP in both .xsession and
.bash_profile, and then running Eterm after logging in again.
"echo $LANG" and "echo $LC_ALL" show ja_JP.eucJP. But the situation
is still the same. I set those variables before starting e17
in my .xsession, but is there a possibility that e17 overrides
my settings for LANG and LC_ALL?
---
Yasufumi Haga [EMAIL PROTECTED]
http://homepage3.nifty.com/peterpan/
fingerprint:0EFA 299A BC32 7D68 1FEF BA2B 804E 9B15 C4F0 F9F0
pgpqwnPEkZ1Nn.pgp
Description: PGP signature
