Bugzilla Bug 40896

As many other packages now make use of the LINGUAS (like kde-18n) env-variable,
openoffice should maybe do that too.

The only problem I see is that LINGUAS can contain more than one lang and
LANGUAGE contains only one.

At least it would be much more consistent for people with only one language in
the system. Those with more than one language have a problem with openoffice
anyway as it seems to support only a single language. right?

Reproducible: Always
Steps to Reproduce:

Current openoffice can indeed only support one language. Further we would need
to do some translation from LINGUAS to language settings that openoffice
understands.

According to
http://tools.openoffice.org/dev_docs/build_linux.html#BuildingLocalised
it seems possible to at least build more than one language.

and looking at openoffice-1.1.0-r3.ebuild there seems to be already bi-language
support (custom and ENUS)

-- snip --

if [ "LANGNAME" != "ENUS" ]; then
                LANGNAME="${LANGNAME},ENUS"
        fi
        ./configure --enable-gcc3 \
                --with-jdk-home=${JAVA_HOME} \
                --with-lang=${LANGNAME}\
                --with-x || die


-- snip --

What the current openoffice ebuild does is build multiple install sets. It
allways builds the us english one because the other builds need some parts from
that. It does not build runtime or user configurable localization. The url you
point at gives the instructions for doing that. As a result you can only have
one language of openoffice on your system.

where is the problem to extract at most 1 lang out of LINGUAS (first none 'en'
one) and use this (after translation to LANGUAGE systax)? If there're more
langs in LINGUAS, there could be an einfo message, that only the 1st one is
used. If both variables are set (LINGUAS *and* LANGUAGE), then use LANGUAGE, so
one can select the wanted lang, if i.e. LINGUAS="de en es"

Ok, this is a little work, but would help alot! Since most ppl. have either
only one lang (their native) in LINGUAS or "<native> en".

Why not creating multiple ebuilds? For example openoffice-en openoffice-de, 
... and then install them to /opt/openoffice-en/, /opt/openoffice-de, ...
Maybe there should be an additional useflag for "build all languages in
LINGUAS" or "build only first" (default) and build only selected (if LANGUAGE
is set for backward compatibility). The openoffice-ebuild only would have 
to evaluate the LINGUAS and then depend on the selected openoffice-ebuilds.
Aditionally it should print the usage with einfo.
This way it should be possible to install multiple languages and it would 
even be possible to select the right language-pack for the helpfiles (in a
valid way, see Bug #55187) ...
Of course one should write a openoffice.exclass since most of the
openoffice-* ebuilds would be exactly the same.
The only drawback in doing so would be having more ebuilds in portage and 
of course the need to build every language seperately (which would take a 
lot of time). On the other hand, for now you can only build one single 
language version of openoffice, so it would only take more time, if you need
this additional feature. 

*** Bug 78987 has been marked as a duplicate of this bug. ***

It does now, thanks for reporting :)