public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] LINGUAS
Date: Thu, 19 Aug 2010 16:21:29 +0300	[thread overview]
Message-ID: <AANLkTintw7JUtFiw+H7gcuAM7xQPBd5yWPRPS2_Ns=Z=@mail.gmail.com> (raw)
In-Reply-To: <BC1EB861-5F9A-419C-9365-B7A637DA7D21@floriancrouzat.net>

On 8/19/10, Florian CROUZAT <gentoo@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 access to this box where linguas=fr is set.
> Check this output:
>  $ type -a [
> [ est une primitive du shell
> [ est /usr/bin/[
>
> [ is a shell built-in becomes "est une primitive du shell"
> I can't see any use flags in coreutils/bash that informs me it will be
> emerged with the linguas support.
> How do I know which package will be localized then ? Just curious, I don't
> tweak my linguas.

Check for the tell-tale USE="nls" flag in the ebuilds.

Not all ebuild's bother listing explicitly out all of the LINGUAS
their sources actually support. coreutils is one of the lazy ones.

Just look at its sources: 39 different .po files, that's 39
localizations available. No point printing out such monstrous long
lists -- your localization is in there, period! ;)  But coreutils does
obey LINGUAS anyway. It only installs what you have in your LINGUAS
(check, e.g., with equery files coreutils).

Openoffice is a special case (surprise!). Its ebuild depends
dynamically on spell-check packages depending on the value of LINGUAS
-- so the poor Gentoo OOo maintainers must list out every supported
lingua in the ebuild. :)

-- 
Arttu V. -- Running Gentoo is like running with scissors



  reply	other threads:[~2010-08-19 13:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 21:25 [gentoo-user] LINGUAS Elmar Hinz
2010-08-18 21:39 ` Alan McKinnon
2010-08-19 11:48   ` Elmar Hinz
2010-08-19 11:56     ` Alan McKinnon
2010-08-19 12:21     ` Nganon
2010-08-19 12:27     ` Graham Murray
2010-08-19 12:37       ` Florian CROUZAT
2010-08-19 13:21         ` Arttu V. [this message]
2010-08-19 14:17         ` Bill Longman
2010-08-19 12:57       ` Elmar Hinz
2010-08-19 13:13         ` Arttu V.
2010-08-19 13:38           ` Elmar Hinz
2010-08-19 13:33         ` Andrea Conti
2010-08-19 13:53           ` Elmar Hinz
2010-08-19 14:26             ` Bill Longman
2010-08-19 19:48             ` Mike Edenfield
2010-08-19 19:45           ` Mike Edenfield
2010-08-20  6:18             ` Andrea Conti
     [not found] <fiYZz-3aF-3@gated-at.bofh.it>
     [not found] ` <fiYZz-3aF-1@gated-at.bofh.it>
     [not found]   ` <fjbN8-7SC-9@gated-at.bofh.it>
2010-08-19 13:27     ` David W Noon
     [not found] <20060729145743.GA24325@brego.pewamo.office>
2006-07-29 15:20 ` Alexander Skwar
2006-07-29 20:41   ` Michael George
2006-07-29 21:08     ` Alexander Skwar
2006-07-29 20:16 ` Richard Fish
2006-08-01 16:01   ` Michael George
2006-07-29 20:41 ` Benno Schulenberg
  -- strict thread matches above, loose matches on Subject: below --
2006-04-05 11:48 [gentoo-user] emerge without download go moko
2006-04-05 12:50 ` Benno Schulenberg
2006-04-05 15:46   ` Matthias Bethke
2006-04-05 21:03     ` [gentoo-user] LINGUAS Benno Schulenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTintw7JUtFiw+H7gcuAM7xQPBd5yWPRPS2_Ns=Z=@mail.gmail.com' \
    --to=arttuv69@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox