1 |
On Mon, 21 Jul 2008 00:34:29 +0200 |
2 |
David Sveningsson wrote: |
3 |
|
4 |
> David Relson skrev: |
5 |
> > On Sun, 20 Jul 2008 22:29:15 +0200 |
6 |
> > David Sveningsson wrote: |
7 |
> >> This sounds like a font issue to me. Can you see the characters |
8 |
> >> correctly if you cat the files? |
9 |
> > |
10 |
> > Hi David, |
11 |
> > |
12 |
> > Using a Gnome terminal and the default character set "Current Local |
13 |
> > Ansi_X3.4-1968" all the asian characters are bad. Using "Unicode |
14 |
> > (UTF-8)" all look good. So cat'ing _does_ work properly. |
15 |
> > |
16 |
> > On the plus side, being able to display correctly in (1) a Gnome |
17 |
> > terminal and (2) in Eclipse's source code window (which uses |
18 |
> > "Monospace") and (3) in a Claws-Mail window indicates that all |
19 |
> > needed fonts are available. |
20 |
> > |
21 |
> > On the minus side, e experiments to change emacs' mule encoding to |
22 |
> > ascii, chinese, and utf-8 don't seem to have any effect :-< |
23 |
> > |
24 |
> > And in an emacs *shell* window (with "mule...set UTF-8", the strings |
25 |
> > show up like: |
26 |
> > |
27 |
> > String sh = "zh: \344\270\226\347\225u"\345\245\275"; |
28 |
> > |
29 |
> > which interprets as the octal codes corresponding to UTF-8 char. |
30 |
> > |
31 |
> > David |
32 |
> > |
33 |
> > |
34 |
> |
35 |
> I assume you are using xemacs, does it work if you're not using |
36 |
> xemacs (use the -nw flag when launching)? I have never used mule |
37 |
> myself as it is not needed with emacs 22. Since everything seems to |
38 |
> work in your terminal I cannot see why it wouldn't work in emacs, but |
39 |
> I'm not an expert. |
40 |
> |
41 |
> Just to be sure, have you followed the steps in |
42 |
> http://www.gentoo.org/doc/en/utf-8.xml? |
43 |
> -- |
44 |
|
45 |
I've got both emacs and xemacs installed. Using xemacs, most of the |
46 |
chinese, japanese, and korean characters show up as hex codes like |
47 |
\226. emacs does the better job (with japanese being correct). |
48 |
|
49 |
I've looked at the utf-8.xml page and what I've got is a combination of |
50 |
en_US.UTF-8 and "C" (see the end of this message). |
51 |
|
52 |
My 2.6.24 kernel has iso8859-1 as its default and I'm rebuilding with |
53 |
UTF-8 as the default to see if this helps. |
54 |
|
55 |
Regards, |
56 |
|
57 |
David |
58 |
|
59 |
**************************************************** |
60 |
In /etc/locale.gen is: |
61 |
|
62 |
en_US.UTF-8 UTF-8 |
63 |
|
64 |
In /etc/profile.env is: |
65 |
|
66 |
export LANG='en_US.UTF-8' |
67 |
|
68 |
In /etc/env.d/02locale.gen is: |
69 |
|
70 |
LANG="en_US.UTF-8" |
71 |
|
72 |
"env-update" and "source /etc/profile" have been run. |
73 |
|
74 |
Running "locale" reports: |
75 |
|
76 |
LANG=en_US.UTF-8 |
77 |
LC_CTYPE="C" |
78 |
LC_NUMERIC="C" |
79 |
LC_TIME="C" |
80 |
LC_COLLATE="C" |
81 |
LC_MONETARY="C" |
82 |
LC_MESSAGES="C" |
83 |
LC_PAPER="C" |
84 |
LC_NAME="C" |
85 |
LC_ADDRESS="C" |
86 |
LC_TELEPHONE="C" |
87 |
LC_MEASUREMENT="C" |
88 |
LC_IDENTIFICATION="C" |
89 |
LC_ALL=C |
90 |
|
91 |
Running "locale -a" reports: |
92 |
|
93 |
C |
94 |
POSIX |
95 |
en_US.utf8 |