OpenOffice translation files

l10n
#1

Hi Anousak,

Von: Anousak Souphavanh
Gesendet: 05.11.10 09:34 Uhr

I was wondering if we are going to move/migrate translation files from
OpenOffice to translations.documentation.org. What about build
process, where we pull those files from and etc?

We surely need to do this and will do this. But target to get this in place
is after 3.3 release.

I'd be happy if someone would dive into the details of the localization
build process. Goran already had some thoughts on this, and there is the
idea that we should get rid of sdf at all. But this really needs time.

For the moment we should concentrate on two things:

- get LibreOffice additional strings (lo-build.po) to 100% (I hope, we can announce
the stringfreeze at the weekend or early next week and then trigger translation
round for this)

- get late changes for full translation of some languages (like danish,
Afrikaans, Zulu, breton ...) into LibreOffice (I try to coordinate this
with Petr)

regards,

André

#2

El dv 05 de 11 de 2010 a les 09:50 +0100, en/na Andre Schnabel va
escriure:

I'd be happy if someone would dive into the details of the localization
build process. Goran already had some thoughts on this, and there is the
idea that we should get rid of sdf at all. But this really needs time.

As a translator I couldn't agree more. But this would mean changing a
lot of source code (I guess we would opt for gettext...). In Catalan
(Valencian) case that'd be great! (we could start using modifiers.

Regards,

Pau

#3

2010.11.05. 10:05 keltezéssel, Pau Iranzo írta:

El dv 05 de 11 de 2010 a les 09:50 +0100, en/na Andre Schnabel va
escriure:

I'd be happy if someone would dive into the details of the localization
build process. Goran already had some thoughts on this, and there is the
idea that we should get rid of sdf at all. But this really needs time.

As a translator I couldn't agree more. But this would mean changing a
lot of source code (I guess we would opt for gettext...). In Catalan
(Valencian) case that'd be great! (we could start using modifiers.

There are 3 different things IMHO that should not be mixed.

1. Internal handling of messages in the source code.
2. Presentation of messages to localizers.
3. Store translations in git.

IMHO gettext is not suitable for the wide range of file types that
contain localizable content in LibreOffice.

Localizers can work with PO files (or with XLIFF files) for a while. PO
and XLIFF can be converted to SDF and vice versa.

What about if we stored translations in PO (or XLIFF or any suitable
file format) in git and generated SDF files build time?

Andras

#4

Hi,

El dv 05 de 11 de 2010 a les 13:02 +0100, en/na Andras Timar va
escriure:

There are 3 different things IMHO that should not be mixed.

1. Internal handling of messages in the source code.
2. Presentation of messages to localizers.
3. Store translations in git.

You're right. In my case I would like LibreOffice to identify itself
using besides the traditional language codes, modifiers like @valencia
or @latin that Catalan (Valencian) and Serbian languages need. For
example, Ubuntu implements the ca_ES.utf8@valencia locale that apply all
the gnome translations in Catalan (Valencian). If there is no Catalan
(Valencian) translation then it uses the default Catalan translation.

But when it comes to OpenOffice.org (and now LibreOffice) even if there
is Catalan (Valencian) translation, it doesn't identify itself as a
ca@valencian but ca_XV, so the system can't recognize it and won't use
it. I don't have the technical knowledge to find out if there is a
workaround or other kind of solution for this.

Ok, I'm rambling... (stop now!)

Pau

#5

Hi Pau,

2010.11.05 15:32, Pau Iranzo rašė:

But when it comes to OpenOffice.org (and now LibreOffice) even if there
is Catalan (Valencian) translation, it doesn't identify itself as a
ca@valencian but ca_XV, so the system can't recognize it and won't use
it. I don't have the technical knowledge to find out if there is a
workaround or other kind of solution for this.

Try to adapt the solution from here:
http://www.mail-archive.com/debian-user@lists.debian.org/msg477907.html

It didn't seem to work for me though, but I remember there was a time when Russian was set up as a fallback for Lithuanian in one distro, and it worked, so I think it is possible.

also, as a workaround, you should be able to use a command like this:

LANG=ca_XV LANGUAGE=ca_XV LC_ALL=ca_XV libreoffice

Hope this helps,
Rimas

#6

Hi Pau,

2010.11.05 15:32, Pau Iranzo rašė:

But when it comes to OpenOffice.org (and now LibreOffice) even if there
is Catalan (Valencian) translation, it doesn't identify itself as a
ca@valencian but ca_XV, so the system can't recognize it and won't use
it. I don't have the technical knowledge to find out if there is a
workaround or other kind of solution for this.

Try to adapt the solution from here:
http://www.mail-archive.com/debian-user@lists.debian.org/msg477907.html

It didn't seem to work for me though, but I remember there was a time when Russian was set up as a fallback for Lithuanian in one distro, and it worked, so I think it is possible.

also, as a workaround, you should be able to use a command like this:

LANG=ca_XV LANGUAGE=ca_XV LC_ALL=ca_XV libreoffice

Hope this helps,
Rimas

P.S. I wonder why we can't have a proper locale code for Valencian though. Does anyone know? I don't think the file format would have anything to do with that...

#7

Hi Rimas,

El dv 05 de 11 de 2010 a les 21:51 +0200, en/na Rimas Kudelis va
escriure:

Try to adapt the solution from here:
http://www.mail-archive.com/debian-user@lists.debian.org/msg477907.html

It didn't seem to work for me though, but I remember there was a time
when Russian was set up as a fallback for Lithuanian in one distro, and
it worked, so I think it is possible.

also, as a workaround, you should be able to use a command like this:

LANG=ca_XV LANGUAGE=ca_XV LC_ALL=ca_XV libreoffice

Very interesting! But I'm not sure Ubuntu developers (or other distros
developers) are going to accept this. I mean, it's very interesting for
me now to solve this locale problem and this workaround seems to be
really useful, but our target (one day...) is to get locale modifiers
into LO (maybe paying? :D...).

Well, nice solution! We usually prepare our owns Ubuntu cds in
Valencian, so this is going to help us :slight_smile:

Regards,

Pau