On Fri, 2018-01-05 at 18:53 +, Grant Edwards wrote:
> I haven't changed LINGUAS or L10N for ages, but I've noticed that
> suddely other packages are being rebuild without linguas_en and
> linguas_en_us.
>
> Is make.conf's LINGUAS variable no longer being expanded?
Correct.
See
On 01/05/2018 12:53 PM, Grant Edwards wrote:
I tried to update today using my normal "emerge --sync; emerge -auvND
world" sequence and it's failing when it gets to iso-codes:
Emerging (1 of 1) app-text/iso-codes-3.75::gentoo
* iso-codes-3.75.tar.xz BLAKE2B SHA512 size ;-) ...
I tried to update today using my normal "emerge --sync; emerge -auvND
world" sequence and it's failing when it gets to iso-codes:
>>> Emerging (1 of 1) app-text/iso-codes-3.75::gentoo
* iso-codes-3.75.tar.xz BLAKE2B SHA512 size ;-) ...
Neil Bothwick wrote:
> On Sat, 25 Jun 2016 09:57:57 -0500, Dale wrote:
>
>>> The point of the news item is not to make it work now, it already
>>> does. The advice is there to help you get your system into a state
>>> where it won't stop working when the next stage of the switch occurs.
>> I get
On Sat, 25 Jun 2016 09:57:57 -0500, Dale wrote:
> > The point of the news item is not to make it work now, it already
> > does. The advice is there to help you get your system into a state
> > where it won't stop working when the next stage of the switch occurs.
> I get that but that didn't make
Mick wrote:
> On Friday 24 Jun 2016 18:47:11 Dale wrote:
>> Alan McKinnon wrote:
>>> On 24/06/2016 17:40, Dale wrote:
Peter Humphrey wrote:
> On Friday 24 Jun 2016 09:54:35 Dale wrote:
>> I agree that the news item was confusing. The guide it linked to
>> wasn't
>> much
Neil Bothwick wrote:
> On Fri, 24 Jun 2016 18:47:11 -0500, Dale wrote:
>
>> I read the news item and was confused. I read it again and was even
>> more confused. After the third time, I didn't see any point in reading
>> it again so I went to the link, hoping it would be better. Well, not
>>
On Fri, 24 Jun 2016 18:47:11 -0500, Dale wrote:
> I read the news item and was confused. I read it again and was even
> more confused. After the third time, I didn't see any point in reading
> it again so I went to the link, hoping it would be better. Well, not
> really. So, I just started
On Friday 24 Jun 2016 18:47:11 Dale wrote:
> Alan McKinnon wrote:
> > On 24/06/2016 17:40, Dale wrote:
> >> Peter Humphrey wrote:
> >>> On Friday 24 Jun 2016 09:54:35 Dale wrote:
> I agree that the news item was confusing. The guide it linked to
> wasn't
> much better either. In
Alan McKinnon wrote:
> On 24/06/2016 17:40, Dale wrote:
>> Peter Humphrey wrote:
>>> On Friday 24 Jun 2016 09:54:35 Dale wrote:
>>>
I agree that the news item was confusing. The guide it linked to
wasn't
much better either. In the end, I just fiddled with the setting
until I
On Friday 24 Jun 2016 22:33:38 Alan McKinnon wrote:
> ... all my posts in the last 30 minutes are redundant.
Er...
:-)
--
Rgds
Peter
On 24/06/2016 20:58, Dale wrote:
Since Alan's post makes more sense to me than the docs, I added the L10N
to make.conf and I got a clean output. So, that works. Mine is what
Alan posted. I guess I'm ready for the future now.;-)
And gmail helpfully delivered half my mail after me being out
On 24/06/2016 22:09, Dale wrote:
allan gottlieb wrote:
On Fri, Jun 24 2016, Alan McKinnon wrote:
On 24/06/2016 16:06, allan gottlieb wrote:
Having read the latest news article and rereading parts of the
localization guide, it is not clear to me what action, if any, I need to
take.
My
On 24/06/2016 17:40, Dale wrote:
Peter Humphrey wrote:
On Friday 24 Jun 2016 09:54:35 Dale wrote:
I agree that the news item was confusing. The guide it linked to wasn't
much better either. In the end, I just fiddled with the setting until I
found a setting that didn't change what I already
allan gottlieb wrote:
> On Fri, Jun 24 2016, Alan McKinnon wrote:
>
>> On 24/06/2016 16:06, allan gottlieb wrote:
>>> Having read the latest news article and rereading parts of the
>>> localization guide, it is not clear to me what action, if any, I need to
>>> take.
>>>
>>> My systems are US
Alan McKinnon wrote:
> On 24/06/2016 16:06, allan gottlieb wrote:
>> Having read the latest news article and rereading parts of the
>> localization guide, it is not clear to me what action, if any, I need to
>> take.
>>
>> My systems are US English only
>>
>> /etc/portage/make.conf has
>>
On Fri, Jun 24 2016, Alan McKinnon wrote:
> On 24/06/2016 16:06, allan gottlieb wrote:
>> Having read the latest news article and rereading parts of the
>> localization guide, it is not clear to me what action, if any, I need to
>> take.
>>
>> My systems are US English only
>>
>>
Peter Humphrey wrote:
> On Friday 24 Jun 2016 09:54:35 Dale wrote:
>
>> I agree that the news item was confusing. The guide it linked to wasn't
>> much better either. In the end, I just fiddled with the setting until I
>> found a setting that didn't change what I already have, in other words,
>>
On 24/06/2016 16:06, allan gottlieb wrote:
> Having read the latest news article and rereading parts of the
> localization guide, it is not clear to me what action, if any, I need to
> take.
>
> My systems are US English only
>
> /etc/portage/make.conf has
>LINGUAS="en"
>
> /etc/local.gen
On Friday 24 Jun 2016 09:54:35 Dale wrote:
> I agree that the news item was confusing. The guide it linked to wasn't
> much better either. In the end, I just fiddled with the setting until I
> found a setting that didn't change what I already have, in other words,
> I got a clean emerge -uvaDN
allan gottlieb wrote:
> Having read the latest news article and rereading parts of the
> localization guide, it is not clear to me what action, if any, I need to
> take.
>
> My systems are US English only
>
> /etc/portage/make.conf has
>LINGUAS="en"
>
> /etc/local.gen has just comments plus
>
Having read the latest news article and rereading parts of the
localization guide, it is not clear to me what action, if any, I need to
take.
My systems are US English only
/etc/portage/make.conf has
LINGUAS="en"
/etc/local.gen has just comments plus
en_US ISO-8859-1
en_US.UTF-8 UTF-8
Hi Francisco,
On 2015-11-12 15:20, Francisco Ares wrote:
> Is there a way for specifying particular "LINGUAS" for individual
> packages?
Sure there is. In fact, "LINGUAS=pt_BR" is just syntactical sugar for
"USE=linguas_pt_BR". So for your specific case with tesseract, you would add a
line to
Hi, all.
My locale language is "pt_BR" (Brazilian Portuguese), and many applications
now support native translations.
And there is the "pt" possible LINGUAS entry, and there is no "pt_PT"
(Portugal spoken Portuguese), for instance, neither any derivatives for
other Portuguese speaking countries,
Francisco Ares wrote:
> Hi, all.
>
> My locale language is "pt_BR" (Brazilian Portuguese), and many
> applications now support native translations.
>
> And there is the "pt" possible LINGUAS entry, and there is no "pt_PT"
> (Portugal spoken Portuguese), for instance, neither
It's the official (as far as
there is such a thing) place to store the list of gettext translations
you want on your system, and most autotools-based builds and binary
package managers also recognize it.
I didn't know that. Thanks for clarifying!
andrea
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar Hinz
did opine thusly:
The gentoo wiki suggests in different places to set the LINGUAS
environment variable in make.conf.
What has LINGUAS todo with make? I would expect
Apparently, though unproven, at 13:48 on Thursday 19 August 2010, Elmar Hinz
did opine thusly:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar
Hinz
did opine thusly:
The gentoo wiki suggests in different places
On 19 August 2010 14:48, Elmar Hinz oss.el...@googlemail.com wrote:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar
Hinz
did opine thusly:
The gentoo wiki suggests in different places to set the LINGUAS
Elmar Hinz oss.el...@googlemail.com writes:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar Hinz
did opine thusly:
The gentoo wiki suggests in different places to set the LINGUAS
environment variable in make.conf.
On 19 août 2010, at 14:27, Graham Murray wrote:
Elmar Hinz oss.el...@googlemail.com writes:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar
Hinz
did opine thusly:
The gentoo wiki suggests in different places to
Even than, LINGUAS has rather to do with OpenOffice.
Has it anything to do with portage at all?
Several packages, not just OpenOffice, can include/support different
languages. Portage uses the value of LINGUAS to tell these packages
which languages to include/support.
When Portage
On 8/19/10, Elmar Hinz oss.el...@googlemail.com wrote:
Even than, LINGUAS has rather to do with OpenOffice.
Has it anything to do with portage at all?
Several packages, not just OpenOffice, can include/support different
languages. Portage uses the value of LINGUAS to tell these packages
On 8/19/10, Florian CROUZAT gen...@floriancrouzat.net wrote:
On 19 août 2010, at 14:27, Graham Murray wrote:
Several packages, not just OpenOffice, can include/support different
languages. Portage uses the value of LINGUAS to tell these packages
which languages to include/support.
I have
On Thu, 19 Aug 2010 13:50:02 +0200, Elmar Hinz wrote about Re:
[gentoo-user] LINGUAS:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010,
Elmar Hinz did opine thusly:
The gentoo wiki suggests in different places to set
On the other hand LINGUAS is still a general variable AFAIK and not
portage specific.
LINGUAS is strictly portage-specific. It's used to control the
compile-time inclusion of languages and/or locales for packages which
have that kind of option (i.e. OpenOffice, KDE, Firefox and many
others); as
No, I think you're mixing up compile-time and run-time values -- and
also reading too much into the file names. make.conf should really
rather be called portage.conf. That would make much more sense IMHO.
:)
As long as the source is the documentation, it should be possible by
concept to
2010/8/19 Andrea Conti a...@alyf.net:
On the other hand LINGUAS is still a general variable AFAIK and not
portage specific.
LINGUAS is strictly portage-specific.
Really?
Researching the web I understand it origins from gettext and portage
has implemented it. If I understand right, it would
On 08/19/2010 05:37 AM, Florian CROUZAT wrote:
On 19 août 2010, at 14:27, Graham Murray wrote:
Elmar Hinz oss.el...@googlemail.com writes:
2010/8/18 Alan McKinnon alan.mckin...@gmail.com:
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar
Hinz
did opine thusly:
On 08/19/2010 06:53 AM, Elmar Hinz wrote:
2010/8/19 Andrea Conti a...@alyf.net:
On the other hand LINGUAS is still a general variable AFAIK and not
portage specific.
LINGUAS is strictly portage-specific.
Really?
Researching the web I understand it origins from gettext and portage
has
On 8/19/2010 9:33 AM, Andrea Conti wrote:
On the other hand LINGUAS is still a general variable AFAIK and not
portage specific.
LINGUAS is strictly portage-specific. It's used to control the
compile-time inclusion of languages and/or locales for packages which
have that kind of option (i.e.
On 8/19/2010 9:53 AM, Elmar Hinz wrote:
But is the following generalization correct?
* LINGUAS is the compile time setting (for multiple languages)
* LANG is the runtime setting (for the current language).
Yes, as long as you're aware that LINGUAS support is recommended, but
optional. A
The gentoo wiki suggests in different places to set the LINGUAS
environment variable in make.conf.
What has LINGUAS todo with make? I would expect it in rc.conf near the
UNICODE setting.
Al
Apparently, though unproven, at 23:25 on Wednesday 18 August 2010, Elmar Hinz
did opine thusly:
The gentoo wiki suggests in different places to set the LINGUAS
environment variable in make.conf.
What has LINGUAS todo with make? I would expect it in rc.conf near the
UNICODE setting.
It
On Friday 23 May 2008, Neil Bothwick wrote:
On Fri, 23 May 2008 17:02:19 +0100, Mick wrote:
Despite my LINGUAS settings I have noticed that kcontrol only shows
US English under languages. Country Region allows me to select
UK, but the only option that I have/can add under languages is US.
On Sat, 24 May 2008 07:17:35 +0100, Mick wrote:
emerge kde-i18n
Just as was ready to reply I already have I found out that I have
not . . . Ha!
I wonder if it should be a dependency of kdelibs if $LINGUAS is set to
anything but en_US.
--
Neil Bothwick
We've all heard that a million
2008/5/22 [EMAIL PROTECTED]:
On Wed, May 21, 2008 at 03:13:44PM +0100, Uwe Thiem wrote:
Does it matter in which order languages are emerged?
Mplayer emerge says it uses the first one as the default language, and
one firefox emerge showed all help menus etc in some non-English
language.
On Fri, 23 May 2008 17:02:19 +0100, Mick wrote:
Despite my LINGUAS settings I have noticed that kcontrol only shows
US English under languages. Country Region allows me to select
UK, but the only option that I have/can add under languages is US.
Spelling is en_US, although I would like to
On Monday 19 May 2008, Michał 'shpaq' Laszuk wrote:
Dnia 2008-05-18, nie o godzinie 23:02 +0100, Graham Murray pisze:
Michał 'shpaq' Laszuk [EMAIL PROTECTED] writes:
The LINGUAS variable should be only en. en_US is a localization.
In that case why do packages such as mozilla-firefox
On Wed, May 21, 2008 at 10:26:58AM +0100, Mick wrote:
Mine has been set to LINGUAS=en_GB el for many years now, but mplayer still
shows up with scrambled characters on the terminal (aterm/rxvt). However,
when rebuilt like:
LINGUAS=en_US emerge -DV mplayer
no more scrambled messages!
On Wednesday 21 May 2008, [EMAIL PROTECTED] wrote:
On Wed, May 21, 2008 at 10:26:58AM +0100, Mick wrote:
Mine has been set to LINGUAS=en_GB el for many years now, but
mplayer still shows up with scrambled characters on the terminal
(aterm/rxvt). However, when rebuilt like:
On Wed, May 21, 2008 at 03:13:44PM +0100, Uwe Thiem wrote:
Does it matter in which order languages are emerged?
Mplayer emerge says it uses the first one as the default language, and
one firefox emerge showed all help menus etc in some non-English
language. Wheteher anything else cares, I do
On Sun, 18 May 2008 16:28:07 -0700, [EMAIL PROTECTED] wrote:
LINGUAS is a system-wide setting, it does not make choices for
individual users, but it does control their range of choice.
Well, nice theory :-) but mplayer emerge says this --
LOG: setup
For MPlayer's language
On 19 May 2008, at 00:02, [EMAIL PROTECTED] wrote:
...
I have had bad luck with LINGUAS. I tried setting it to all the
languages I knew of --
LINGUAS=en_US af ar az bg bn br bs ca cs cy da de el en_GB eo
es et eu fa fi fr fy ga gl he hi hr hu is it ja km ko lt lv mk mn
ms nb nds nl nn
Dnia 2008-05-18, nie o godzinie 23:02 +0100, Graham Murray pisze:
Michał 'shpaq' Laszuk [EMAIL PROTECTED] writes:
The LINGUAS variable should be only en. en_US is a localization.
In that case why do packages such as mozilla-firefox support (amongst
others) linguas_en, linguas_en_GB and
I only need English support, but USan English is preferred. I have in
make.conf
LINGUAS=en_US en
thinking that if an app supports en_US that will be used since it's
first. Is that the way it works?
I guess this is just a trivia question -- I don't even know if there
are apps which could use
Dnia 2008-05-18, nie o godzinie 15:07 -0500, »Q« pisze:
ng that if an app supports en_US that will be used since it's
first. Is that the way it works?
The LINGUAS variable should be only en. en_US is a localization.
--
Nie istnieje bariera nieskończenie ostateczna,
Nie istnieje nic, co nie
Michał 'shpaq' Laszuk [EMAIL PROTECTED] writes:
The LINGUAS variable should be only en. en_US is a localization.
In that case why do packages such as mozilla-firefox support (amongst
others) linguas_en, linguas_en_GB and linguas_en_US? They use the
LINGUAS variable to select which localised
On Sun, May 18, 2008 at 11:02:07PM +0100, Graham Murray wrote:
Micha?? 'shpaq' Laszuk [EMAIL PROTECTED] writes:
The LINGUAS variable should be only en. en_US is a localization.
In that case why do packages such as mozilla-firefox support (amongst
others) linguas_en, linguas_en_GB and
On Sun, 18 May 2008 16:02:25 -0700, [EMAIL PROTECTED] wrote:
What is LINGUAS supposed to do?
Tell portage which languages you want support for when building an
application. It does not set the default language for that application,
which is either handled by the locale environment variables or
On Mon, May 19, 2008 at 12:22:45AM +0100, Neil Bothwick wrote:
On Sun, 18 May 2008 16:02:25 -0700, [EMAIL PROTECTED] wrote:
What is LINGUAS supposed to do?
Tell portage which languages you want support for when building an
application. It does not set the default language for that
On Sonntag, 18. Mai 2008, »Q« wrote:
I only need English support, but USan English is preferred. I have in
make.conf
LINGUAS=en_US en
thinking that if an app supports en_US that will be used since it's
first. Is that the way it works?
no. It installs the en_US and en language files.
Set
On 7/29/06, Michael George [EMAIL PROTECTED] wrote:
The docs I found on gentoo localization indicate that I can set LINGUAS
in make.conf and build for just the languages I desire. I set it to:
LINGUAS=en_US
but all that does is prepend en_US to the beginning of the string above.
Thanks to all
Michael George schrieb:
I am building OOo 2.0.3 and I happened to notice in the verbose emerge
output that there is a long list of languages listed in the LINGUAS
variable:
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%
On 7/29/06, Michael George [EMAIL PROTECTED] wrote:
The docs I found on gentoo localization indicate that I can set LINGUAS
in make.conf and build for just the languages I desire. I set it to:
LINGUAS=en_US
but all that does is prepend en_US to the beginning of the string above.
Look closer;
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%
Michael George schrieb:
On Sat, Jul 29, 2006 at 05:20:13PM +0200, Alexander Skwar wrote:
Michael George schrieb:
I am building OOo 2.0.3 and I happened to notice in the verbose emerge
output that there is a long list of languages listed in the LINGUAS
variable:
LINGUAS=-af% -ar% -be_BY% -bg%
Matthias Bethke wrote:
on Wednesday, 2006-04-05 at 14:50:29, you wrote:
Just put LINGUAS=fr en. I'm unsure whether en-us is
recognized.
The Localization Guide isn't very clear about the syntax of
these, nor how to get a list of available codes. I guess the
basic ones are the two-letter
68 matches
Mail list logo