public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [SOLVED] LINGUAS issue
Date: Thu, 12 Nov 2015 23:05:53 -0200	[thread overview]
Message-ID: <CAHH9eM4rTKc2XKz0A8fB3maDN5d8z35s2BnnzNCmZWkZxZmsyg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2736 bytes --]

2015-11-12 16:27 GMT-02:00 <wabenbau@gmail.com>:

> Francisco Ares <frares@gmail.com> 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 any derivatives
> > for other Portuguese speaking countries, which possibly have their
> > own regional differences.
>
> You can add locales by editing /etc/locale.gen and running locale-gen.
> As i saw in /usr/share/i18n/SUPPORTED, pt_PT is supported.
>
> > There are a few applications that do not distinguish "pt_BR" from
> > "pt" and treat Portuguese language as simply "pt". An example is the
> > OCR program "tesseract", that builds language specifics according to
> > the LINGUAS environment variable.
> >
> > Is there a way for specifying particular "LINGUAS" for individual
> > packages?  I would not like to have to build dozens of applications to
> > include "pt" to my "LINGUAS" definition just to have "tesseract" to
> > include my native language support.  I've found some old messages
> > about this on the net, but did not get any real solution.
>
> You can define package specific environment variables for package
> builds in /etc/portage/env/
>
> If you need package specific environment variables for runtime you
> could create simple scripts to set the env and start the program.
>
> #!/bin/sh
> #
> # start_tesseract.sh
> #
> LINGUAS="pt"
> tesseract
>
> Then modify the according menu entries / starter buttons to use the
> script.
>
> > Or should I ask the "tesseract" package maintainer to add "pt_BR" to
> > the available options?
>
> That's a good idea.
>
> --
> Regards
> wabe
>
>

Thanks Florian, Jörg and wabe, it is finally solved.

It happens that I also had LINGUAS set in /etc/profile

So, as it seems, this setting bypasses all others.  I've had found that
"LINGUAS_pt" use flag trick before, in an old post, but as it didn't work
at a first attempt, and as the post was a bit old, I supposed that this
feature was not in portage anymore.

But now with 3 persons saying basically the same thing, I went deeper in my
/etc files.

The trick brought up by wabe was crucial, as I tried to include another USE
flag on the same "env" configuration; when I asked to rebuild tesseract,
the USE flag was there, but the LINGUAS wasn't. So I started to look for
other instances and found it in that /etc/profile file, edited in 2012,
probably when I first installed Gentoo on this machine as a newbie.

Going now into a full revision into /etc .

Thanks a lot!
Francisco

[-- Attachment #2: Type: text/html, Size: 3649 bytes --]

                 reply	other threads:[~2015-11-13  1:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAHH9eM4rTKc2XKz0A8fB3maDN5d8z35s2BnnzNCmZWkZxZmsyg@mail.gmail.com \
    --to=frares@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