1 |
Alan McKinnon wrote: |
2 |
> On 24/06/2016 16:06, allan gottlieb wrote: |
3 |
>> Having read the latest news article and rereading parts of the |
4 |
>> localization guide, it is not clear to me what action, if any, I need to |
5 |
>> take. |
6 |
>> |
7 |
>> My systems are US English only |
8 |
>> |
9 |
>> /etc/portage/make.conf has |
10 |
>> LINGUAS="en" |
11 |
>> |
12 |
>> /etc/local.gen has just comments plus |
13 |
>> en_US ISO-8859-1 |
14 |
>> en_US.UTF-8 UTF-8 |
15 |
>> |
16 |
>> Should I add |
17 |
>> L10N="en-US" |
18 |
>> to /etc/portage/make.conf ? |
19 |
>> |
20 |
>> Should I run local-gen ? |
21 |
>> |
22 |
>> Thanks |
23 |
>> allan |
24 |
>> |
25 |
> Add |
26 |
> |
27 |
> L10N="en" to make.conf |
28 |
> |
29 |
> "en" has no tweaks to be made to the new naming style so that's all you |
30 |
> do. Other folks who use, for example, Brazilian Portuguese, will need to |
31 |
> make tweaks and look up the correct value in the file the news item |
32 |
> references. |
33 |
> |
34 |
> For now LINGUAS and L10N will work in parallel and the devs will do the |
35 |
> heavy lifting. For the moment all changes will be light touch, the big |
36 |
> tasks will happen later. |
37 |
> |
38 |
> One day you will need to remove LINGUAS from make.conf entirely, but |
39 |
> that day is not today. |
40 |
> |
41 |
> And all of this is necessary because making a USE_EXPAND env var called |
42 |
> LINGUAS was a really stupid idea from day one. |
43 |
> |
44 |
> |
45 |
|
46 |
Since Alan's post makes more sense to me than the docs, I added the L10N |
47 |
to make.conf and I got a clean output. So, that works. Mine is what |
48 |
Alan posted. I guess I'm ready for the future now. ;-) |
49 |
|
50 |
Dale |
51 |
|
52 |
:-) :-) |