| View previous topic :: View next topic |
| Author |
Message |
Elleni
Veteran
Joined: 23 May 2006
Posts: 1291
|
 Posted: Tue Oct 31, 2017 2:17 pm Post subject: |
 |
|
| What about kde4-l10n? |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 9334
|
| Posted: Tue Oct 31, 2017 2:24 pm Post subject: |
|
|
That has zero relevance to Plasma, being in kde-apps/ category.
It is explained there anyway ^ did you actually read that link? Please also note that it is part of the Applications section, not Plasma. |
|
| Back to top |
|
|
Mr. T.
Guru
Joined: 26 Dec 2016
Posts: 477
|
| Posted: Tue Oct 31, 2017 4:17 pm Post subject: |
|
|
A software may support a feature named internationalization. This feature defines a method to ease the translation process for software programmers.
| GNU Gettext wrote: | | By internationalization, one refers to the operation by which a program, or a set of programs turned into a package, is made aware of and able to support multiple languages. This is a generalization process, by which the programs are untied from calling only English strings or other English specific habits, and connected to generic ways of doing the same, instead. Program developers may use various techniques to internationalize their programs. Some of these have been standardized. GNU gettext offers one of these standards. See Programmers. |
The "internationalized feature" defines a process to manipulate a set of data that can be translated and the "localization feature" provides the set of translated data.
| GNU Gettext wrote: | | By localization, one means the operation by which, in a set of programs already internationalized, one gives the program all needed information so that it can adapt itself to handle its input and output in a fashion which is correct for some native language and cultural habits. This is a particularisation process, by which generic methods already implemented in an internationalized program are used in specific ways. The programming environment puts several functions to the programmers disposal which allow this runtime configuration. The formal description of specific set of cultural habits for some country, together with all associated translations targeted to the same native language, is called the locale for this language or country. Users achieve localization of programs by setting proper values to special environment variables, prior to executing those programs, identifying which locale should be used. |
We may use the LINGUAS environment variable to limit the set of installed localization data (organized per language) because we may not need all the available languages provided by a package.
| GNU Gettext wrote: | | Internationalized packages have usually many ll.po files. Unless translations are disabled, all those available are installed together with the package. However, the environment variable LINGUAS may be set, prior to configuration, to limit the installed set. LINGUAS should then contain a space separated list of two-letter codes, stating which languages are allowed. |
| GNU Gettext wrote: | | One uses the expression Native Language Support, or merely NLS, for speaking of the overall activity or feature encompassing both internationalization and localization, allowing for multi-lingual interactions in a program. |
In my opinion, the mentions about localization in the Wiki articles should be reworded (add specific words and general information about localization) to avoid confusion or misinterpretation.
| asturm wrote: | | nls: it's just a regular global USE flag enabling localisation in packages / pulling in additional packages to get localisation. |
| mail-client/alpine-*.ebuild: | econf \
$(use_enable nls) |
| kde-frameworks/knotifications-*.ebuild: | DEPEND="${RDEPEND}
nls? ( $(add_qt_dep linguist-tools) )
X? ( x11-proto/xproto )
" |
Link: GNU Gettext
helecho. |
|
| Back to top |
|
|
Mr. T.
Guru
Joined: 26 Dec 2016
Posts: 477
|
| Posted: Tue Oct 31, 2017 4:33 pm Post subject: |
|
|
Asturm, could anyone update the developer manual?
| asturm wrote: | | krinn wrote: | | https://devmanual.gentoo.org/general-concepts/use-flags/index.html wrote: | | The VIDEO_CARDS, INPUT_DEVICES and LINGUAS variables are automatically expanded into USE flags |
|
You are invited to check for any kde-plasma/ and kde-apps/ ebuild to have LINGUAS use flag. You won't find any where it isn't just used as environment variable.
See also: https://gentoo.org/support/news-items/2016-06-23-l10n-use_expand.html |
helecho. |
|
| Back to top |
|
|
Mr. T.
Guru
Joined: 26 Dec 2016
Posts: 477
|
| Posted: Tue Oct 31, 2017 6:14 pm Post subject: |
|
|
krinn, I disagree: it is the N option that implies the rebuild because of the USE flag change.
| krinn wrote: | | And -U will rebuild package when useflags changes are done by the user (so ignoring changes that comes from new ebuild or profile) while -u will always rebuild them if useflags has changed. One or the other, in this case, the user has done the change. |
N.B: man -Tpdf emerge >> ~/emerge.pdf
helecho. |
|
| Back to top |
|
|
Kollin
Veteran
Joined: 25 Feb 2006
Posts: 1139
Location: Sofia/Bulgaria
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
