1 |
First draft of news item for proceeding with LINGUAS USE_EXPAND rename |
2 |
to L10N independently of the INSTALL_MASK feature additions. |
3 |
|
4 |
I hope English natives will improve the sentence flow and grammar here |
5 |
:) |
6 |
Perhaps there's also a better title than with the technical USE_EXPAND |
7 |
mention. |
8 |
|
9 |
|
10 |
Title: LINGUAS USE_EXPAND renamed to L10N |
11 |
Author: Mart Raudsepp <leio@g.o> |
12 |
Content-Type: text/plain |
13 |
Posted: 2016-06-06 |
14 |
Revision: 1 |
15 |
News-Item-Format: 1.0 |
16 |
|
17 |
The LINGUAS USE_EXPAND has been renamed to L10N, to avoid a conceptual |
18 |
clash with the standard gettext LINGUAS behaviour. |
19 |
L10N controls which extra localization support will be installed. |
20 |
This is usually used in case of extra downloads of language packs. |
21 |
|
22 |
If you have set LINGUAS in your make.conf, you should either copy or |
23 |
rename it to L10N, depending on if you want to filter the supported |
24 |
languages at build time or not via the gettext LINGUAS environment |
25 |
variable behaviour as described below. Note that this filtering does not |
26 |
affect only installed gettext catalog files (*.mo), but also lines of |
27 |
translations in an always shipped file (e.g *.desktop). |
28 |
|
29 |
LINGUAS maintains the standard gettext behaviour and will now work as |
30 |
expected with all package managers. It controls which language |
31 |
translations are built and installed. An unset value means all |
32 |
available, an empty value means none, and a value can be an unordered |
33 |
list of gettext language codes, with or without country codes. |
34 |
Usually only two letter language codes suffice, but can be limited with |
35 |
country codes with a 'll_CC' formatting, where 'll' is the language code |
36 |
and 'CC' is the country code, e.g en_GB. Some rare languages also have |
37 |
three letter language codes. |
38 |
If you want English with a set LINGUAS, it is suggested to list it with |
39 |
the desired country code, in case the default is not the usual en_US. |
40 |
It is also common to list "en" then, in case a package is natively |
41 |
written in a different language, but does provide an English translation |
42 |
for whichever country. |
43 |
A list of LINGUAS language codes is available at |
44 |
http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes |
45 |
|
46 |
Note that LINGUAS affects build time, and thus filters what ends up |
47 |
in binary packages. If you are building generic binary packages that |
48 |
should support all available language, you should not set LINGUAS. |
49 |
|
50 |
If you have per-package customizations of LINGUAS USE_EXPAND, you |
51 |
should also rename those from LINGUAS to L10N. This typically means |
52 |
renaming linguas_* to l10n_*. |
53 |
|
54 |
https://wiki.gentoo.org/wiki/Localization/Guide has also been updated |
55 |
to reflect this change. |