1 |
On 5/11/2011 12:54 PM, Dale wrote: |
2 |
|
3 |
> root@fireball / # locale -a |
4 |
> C |
5 |
> POSIX |
6 |
> en_US |
7 |
> en_US.iso88591 |
8 |
> en_US.utf8 |
9 |
|
10 |
So you have three locales installed (C and POSIX are internal and always |
11 |
present) that are the same language and region with different character |
12 |
sets. You probably don't need to do this anymore, since most every |
13 |
modern application can handle UTF-8 character data and, even if it |
14 |
can't, UTF-8 data looks identical to US-ASCII data for most English |
15 |
language text. |
16 |
|
17 |
> root@fireball / # locale |
18 |
> LANG= |
19 |
> LC_CTYPE="POSIX" |
20 |
> LC_NUMERIC="POSIX" |
21 |
> LC_TIME="POSIX" |
22 |
> LC_COLLATE="POSIX" |
23 |
> LC_MONETARY="POSIX" |
24 |
> LC_MESSAGES="POSIX" |
25 |
> LC_PAPER="POSIX" |
26 |
> LC_NAME="POSIX" |
27 |
> LC_ADDRESS="POSIX" |
28 |
> LC_TELEPHONE="POSIX" |
29 |
> LC_MEASUREMENT="POSIX" |
30 |
> LC_IDENTIFICATION="POSIX" |
31 |
> LC_ALL= |
32 |
> root@fireball / # |
33 |
|
34 |
This means that your UTF-8 setup is clearly *not* working :) Your locale |
35 |
is not being set anywhere, it's using the glibc default of POSIX. POSIX |
36 |
is approximately equal to en_US as far as date/time, sorting, etc. but |
37 |
lacks most of the numeric formatting (no currency symbol, no thousands |
38 |
separator, etc). It's also using the default US-ASCII character set. |
39 |
|
40 |
--Mike |