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