Michael George wrote:
>  LINGUAS="-af% -ar% -be_BY% -bg% -bn% -bs% -ca% -cs% -cy% -da%
> -de% -el% -en% -en_GB% -en_US% -en_ZA% -es% -et% -fa% -fi% -fr%
> -gu_IN% -he% -hi_IN% -hr% -hu% -it% -ja% -km% -ko% -lt% -mk% -nb%
> -nl% -nn% -nr% -ns% -pa_IN% -pl% -pt% -pt_BR% -ru% -rw% -sh_YU%
> -sk% -sl% -sr_CS% -st% -sv% -sw_TZ% -th% -tn% -tr% -ts% -vi% -xh%
> -zh_CN% -zh_TW% -zu%"
>
> Does this mean that NONE of those languages will be built in or
> that ALL of them will be?

None, as they all start with a minus sign.

> I set it to: LINGUAS="en_US"
> but all that does is prepend en_US to the beginning of the string
> above.

Not quite: it also removes the -en_US.  It makes no difference, 
though, as the ebuild uses en_US by default when LINGUAS is empty.

> Where are those settings coming from?

>From the ebuild: it specifies that it can handle LANGS="af ar ...".

Benno
-- 
[email protected] mailing list

Reply via email to