1 |
if theres no file 02local you have to create it and set your locales there. |
2 |
after donig this run env-update |
3 |
|
4 |
regards |
5 |
|
6 |
Dominik |
7 |
|
8 |
On Fri, May 30, 2008 at 3:34 PM, Kevin O'Gorman <kogorman@×××××.com> wrote: |
9 |
|
10 |
> On Thu, May 29, 2008 at 4:09 PM, Daniel Pielmeier < |
11 |
> daniel.pielmeier@××××××××××.com> wrote: |
12 |
> |
13 |
>> Kevin O'Gorman schrieb: |
14 |
>> |
15 |
>> On Thu, May 29, 2008 at 3:18 PM, Mick <michaelkintzios@×××××.com> wrote: |
16 |
>>> |
17 |
>>> On Thursday 29 May 2008, Kevin O'Gorman wrote: |
18 |
>>>> |
19 |
>>>>> On Thu, May 29, 2008 at 2:29 PM, Mick <michaelkintzios@×××××.com> |
20 |
>>>>> wrote: |
21 |
>>>>> |
22 |
>>>>>> On Thursday 29 May 2008, Kevin O'Gorman wrote: |
23 |
>>>>>> |
24 |
>>>>>>> When I crank up K3b, it complains about my setup, with the message |
25 |
>>>>>>> |
26 |
>>>>>>> "System locale charset is ANSI_X3.4-1968 |
27 |
>>>>>>> Your system's locale charset (i.e. the charset used to encode |
28 |
>>>>>>> filenames) is set to ANSI_X3.4-1968. It is highly unlikely that this |
29 |
>>>>>>> has been done intentionally. |
30 |
>>>>>>> Most likely the locale is not set at all. An invalid setting |
31 |
>>>>>>> will result in problems when creating data projects. |
32 |
>>>>>>> Solution: To properly set the locale charset make sure the LC_* |
33 |
>>>>>>> environment variables are set. Normally the distribution setup tools |
34 |
>>>>>>> take care of this." |
35 |
>>>>>>> |
36 |
>>>>>>> It is correct that this is not intentional (it does seem antique). I |
37 |
>>>>>>> |
38 |
>>>>>> have |
39 |
>>>>>> |
40 |
>>>>>> configured .mybashrc to set my LANG to "en_US", but nothing beyond |
41 |
>>>>>>> that. What "distribution setup tools" is it referring to, so that I |
42 |
>>>>>>> |
43 |
>>>>>> can |
44 |
>>>> |
45 |
>>>>> correct this on gentoo? |
46 |
>>>>>>> |
47 |
>>>>>> What have you set up in your /etc/locale.gen ? |
48 |
>>>>>> |
49 |
>>>>> I won't take credit for setting this up, because I don't think I did. |
50 |
>>>>> On |
51 |
>>>>> the other hand, |
52 |
>>>>> I've had occasion to internationalize a web page to dutch and polish, |
53 |
>>>>> |
54 |
>>>> which |
55 |
>>>> |
56 |
>>>>> appear |
57 |
>>>>> in the list. So I dunno where it came from. |
58 |
>>>>> |
59 |
>>>>> But here's what's there: |
60 |
>>>>> |
61 |
>>>>> # /etc/locale.gen: list all of the locales you want to have on your |
62 |
>>>>> |
63 |
>>>> system |
64 |
>>>> |
65 |
>>>>> # |
66 |
>>>>> # The format of each line: |
67 |
>>>>> # <locale> <charmap> |
68 |
>>>>> # |
69 |
>>>>> # Where <locale> is a locale located in /usr/share/i18n/locales/ and |
70 |
>>>>> # where <charmap> is a charmap located in /usr/share/i18n/charmaps/. |
71 |
>>>>> # |
72 |
>>>>> # All blank lines and lines starting with # are ignored. |
73 |
>>>>> # |
74 |
>>>>> # For the default list of supported combinations, see the file: |
75 |
>>>>> # /usr/share/i18n/SUPPORTED |
76 |
>>>>> # |
77 |
>>>>> # Whenever glibc is emerged, the locales listed here will be |
78 |
>>>>> |
79 |
>>>> automatically |
80 |
>>>> |
81 |
>>>>> # rebuilt for you. After updating this file, you can simply run |
82 |
>>>>> `locale-gen` |
83 |
>>>>> # yourself instead of re-emerging glibc. |
84 |
>>>>> |
85 |
>>>>> en_US ISO-8859-1 |
86 |
>>>>> en_US.UTF-8 UTF-8 |
87 |
>>>>> #ja_JP.EUC-JP EUC-JP |
88 |
>>>>> #ja_JP.UTF-8 UTF-8 |
89 |
>>>>> #ja_JP EUC-JP |
90 |
>>>>> #en_HK ISO-8859-1 |
91 |
>>>>> #en_PH ISO-8859-1 |
92 |
>>>>> #de_DE ISO-8859-1 |
93 |
>>>>> #de_DE@euro ISO-8859-15 |
94 |
>>>>> es_MX ISO-8859-1 |
95 |
>>>>> #fa_IR UTF-8 |
96 |
>>>>> fr_FR ISO-8859-1 |
97 |
>>>>> fr_FR@euro ISO-8859-15 |
98 |
>>>>> #it_IT ISO-8859-1 |
99 |
>>>>> pl_PL ISO-8859-15 |
100 |
>>>>> |
101 |
>>>> This looks fine. If when you run $ locale you get a list with |
102 |
>>>> LANG=en_US |
103 |
>>>> but |
104 |
>>>> further down LC_ALL= (blank), then set export LC_ALL=xxx in your |
105 |
>>>> .bashrc |
106 |
>>>> to |
107 |
>>>> whatever you want your locale set to. |
108 |
>>>> |
109 |
>>>> |
110 |
>>> Halfway there. I did that, and now "locale" looks like |
111 |
>>> |
112 |
>>> kevin@treat ~ $ locale |
113 |
>>> LANG=en_US |
114 |
>>> LC_CTYPE="en_US" |
115 |
>>> LC_NUMERIC="en_US" |
116 |
>>> LC_TIME="en_US" |
117 |
>>> LC_COLLATE="en_US" |
118 |
>>> LC_MONETARY="en_US" |
119 |
>>> LC_MESSAGES="en_US" |
120 |
>>> LC_PAPER="en_US" |
121 |
>>> LC_NAME="en_US" |
122 |
>>> LC_ADDRESS="en_US" |
123 |
>>> LC_TELEPHONE="en_US" |
124 |
>>> LC_MEASUREMENT="en_US" |
125 |
>>> LC_IDENTIFICATION="en_US" |
126 |
>>> LC_ALL=en_US |
127 |
>>> kevin@treat ~ $ |
128 |
>>> |
129 |
>>> However, when I start k3b from the KDE menus, it still complains. |
130 |
>>> |
131 |
>>> On the other hand, if I start k3b from the shell that gives the "locale" |
132 |
>>> results above, |
133 |
>>> it starts clean. So the issue seems to be that I need to inform KDE |
134 |
>>> about |
135 |
>>> the |
136 |
>>> locale. |
137 |
>>> |
138 |
>>> I did a fresh boot, and that did not help, so I wonder if .mybashrc is |
139 |
>>> the |
140 |
>>> correct |
141 |
>>> place to do this. |
142 |
>>> |
143 |
>>> |
144 |
>> try /etc/env.d/02locale |
145 |
>> |
146 |
>> LANG="en_US" |
147 |
>> LC_ALL="en_US" |
148 |
>> |
149 |
>> For details take a look at the localisation guide. |
150 |
>> http://www.gentoo.org/doc/en/guide-localization.xml |
151 |
>> -- |
152 |
>> gentoo-user@l.g.o mailing list |
153 |
>> |
154 |
>> |
155 |
> The file /etc/env.d/02locale does not exist on my system. I can create it, |
156 |
> of course, |
157 |
> but I suspect I may be missing something. Is there a package I should |
158 |
> emerge? |
159 |
> |
160 |
> ++ kevin |
161 |
> |
162 |
> -- |
163 |
> Kevin O'Gorman, PhD |
164 |
> |