On Sat, 18 Feb 2006 00:45:31 +0900, Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
| On Fri, 17 Feb 2006 19:10:37 +0900 (JST) Yasufumi Haga | <[EMAIL PROTECTED]> babbled: | | > Hello | > | > I built Eterm 0.9.4 and libast from the CVS source today. | > In my e16 environment Eterm 0.9.4 works normally, no problem | > at all. It also works fine in e17 when starting Eterm *before* | > e17 in .xsession. But when I start Eterm in e17 environment, | > the behavior gets strange. I uploaded the screenshot on my site: | > | > http://homepage3.nifty.com/peterpan/x00/eterm-problem.jpg | > | > All the Japanese characters on the buttonbar are completely broken, | > and some Japanese characters in the terminal are also broken. | > In addition, The size of ASCII characters in the terminal is | > smaller than the normal ones, and the terminal itself gets smaller. | > XIM works, but the characters I enter via XIM are messed up. | > | > Is it a known issue? | | what encoding? utf8? etemr's utf8 support is very experiemntal last i talked | with mej if its utf8... ? 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. Thanks for your reply. Regards. --- Yasufumi Haga [EMAIL PROTECTED] http://homepage3.nifty.com/peterpan/ fingerprint:0EFA 299A BC32 7D68 1FEF BA2B 804E 9B15 C4F0 F9F0
pgpCKxN0a5sqU.pgp
Description: PGP signature
