Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

i wondered if we can have localized openoffice-bin ebuilds in portage (bug
#20609 has a spanish version).

i got a working german version but i'm not sure about commiting it.

this bug is mainly meant for discussion here

regards

It is impossible to solve this issue with only one ebuild file because
OpenOffice.org doesn't support "locale".
I think the best solution to the localized openoffice-bin problem is to make a
localized openoffice-bin ebuild for each language.

This issue seems to be not active. Please discuss this issue immediately,
Gentoo OpenOffice Team.

Created an attachment (id=27914) [details]
openoffice-bin ebuild for Japanese

Example: openoffice-bin ebuild for Japanese.

isn't there a 'more or less' standardized location where we could use e.g.:
OOoLANG="de" emerge openoffice-bin style??

regards

I have an czech binary ebuild contributed by someone on irc, and I could
contribute a danish ebuild. It would be great if some kind of consensus could
be reached regarding this as there seems to be a lot of open bugs. And as
pointed out, some of then are quite old.

What Thomas proposes seems like a good solution, given that the ebuilds are
very similar, and it seems the case.

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

See also bug #40896 and #42512. (They are for app-office/openoffice though)

Created an attachment (id=42903) [details]
openoffice-bin-1.1.3.ebuild-linguas.diff 

This is a diff to openoffice-bin-1.1.3.ebuild.
It uses LINGUAS environment to support
Czech, Danish, German, French, Italian,
Japanese, Dutch, Chinese(simplified) and
Chinese(Traditional). I tested it with Japanese,
Chinese(simplified) and Chinese(traditional).

Created an attachment (id=42904) [details]
openoffice-bin-fontpath-gentoo.diff

Patch to add /usr/share/fonts/* to fontpath.

@usata: Your fonts-patch doesn't do anything for me, I guess all the fonts in
/usr/share/fonts should be autoadded, but they don't show up for me, I still
have to add them manually. Is there something I am missing? Does it work for
you?

I've now added the automatic font detection to the wrapper, better place to put
it, there it even works ;)

I really would like to get this into portage, but there are some issues with it
that need to be resolved first, which are non-trivial:

*) Atm, the ebuild downloads all variants in your LINGUAS + the english one,
this is a blocker for me, it should only download one.

*) Also: How to handle upgrades? The translated version are not released at the
same time, some even skip versions. So people happily using - let's say - a
japanese version of 1.1.3 are automatically upgraded to an english 1.1.4.

The alternative - to use different ebuilds for each and every localized version
- is a way I don't want to go (and won't). This would introduce a lot of new
packages in the portage dir, which will be obsolete anyway, when 2.0 arrives
(which should support language packs), also all of this packages would have to
block each other, which would be quite a mess.

Comments? Ideas?

After looking for a working solution, I can quite safely say, there is no
satisfying one for OOo 1.1.x, so won't do this for this series. BUT: I've just
put a new 2.0-pre version into portage (openoffice-bin-1.9.91-r1) which has
LINGUAS support. Still hard masked, but thanks to the new language packs, this
closes this bug :)