Git repo for l10n?

l10n
#1

Hello,

a couple of years ago I've helped improving the German online help texts. It however has always been a nightmare to get corrections into it by opening issues, describing the exact locations, discussing this with Sun etc.

My question is whether the l10n stuff is now being made available through a Git repository, that can be easily cloned and modified.

Even if not every author will get direct push rights to the master repo, it should be much easier to automatically generate patches and send them in or push stuff to an intermediate Git repo where a maintainer can fetch it from.

Best regards

Guido

#2

Hi,

Hello,

a couple of years ago I've helped improving the German online help
texts. It however has always been a nightmare to get corrections into it
by opening issues, describing the exact locations, discussing this with
Sun etc.

Well, this has changed a lot since that time. Today it's normally enough to file an issue, containing the help index, wrong and right text ... and assign the issue to me.
German UI issues get fixed within hrs. , Help at least before the next release.

Although translation is not directly done in source repository, it's quite easy to contribute.

Only problem at OOo is, that the translations are integrated very late in the release cycle. So although transaltions are fixed, we often see then only short before RC phase in the product.

My question is whether the l10n stuff is now being made available
through a Git repository, that can be easily cloned and modified.

Even if not every author will get direct push rights to the master repo,
it should be much easier to automatically generate patches and send them
in or push stuff to an intermediate Git repo where a maintainer can
fetch it from.

I'm not in favour of using git directly. This is normally not the tool, translators work with.

We currently focus on pootle. See
http://pootle.sunvirtuallab.com/ (current OOo setup)
http://stage1.services.openoffice.org/ (next version at OOo, we will provide quite the same version)

http://translate.sourceforge.net/wiki/pootle/index?redirect=1
for genereal info on pootle.

After all, we can use a git repository as backend for the pootle files, but the process is more complex (needs to be to please translators :wink: )

Anyway .. I'm open for discussion on how to handle the translations.

regards,

André

#3

A big +1!

It should also be a goal to move all locale data into this repository
and modify the build system to look for them in this new separate
module. But this is something we have a power to set up, no need for
someone else to amend this change. Unfortunately, I do not have time to
dive into this now but I would be happy to test and send feedback to
whoever pick this as goal and join the development effort later.

A few weeks ago I have started mapping all this items on the
OpenOffice.org wiki:
http://wiki.services.openoffice.org/wiki/User:Goranrakic/Localization

We can use that as a starting point. Localization of our software
product is much more than translating PO/SDF and a lot of info available
is lost, missing or outdated.

I am happy to participate in this discussion. There are many
contributors with a huge experience in OpenOffice.org localization
affiliated with the Document Foundation and I am sure that working
together we will be able to improve localization work flow for LibO.

Kind regards,
Goran Rakic
Serbian OpenOffice.org
native-language project lead

#4

Hi Goran,

It should also be a goal to move all locale data into this repository
and modify the build system to look for them in this new separate
module. But this is something we have a power to set up, no need for
someone else to amend this change. Unfortunately, I do not have time to
dive into this now but I would be happy to test and send feedback to
whoever pick this as goal and join the development effort later.

Anything we can do that you have more time for us? :slight_smile:

I did hope, you could help with the build system and the needed scripting stuff - I know, you do have experience on this.

I curently have a good idea, what needs to be done regardings scripting, but am very new to the build system and have only some basic ideas how translations are handeled there.

regards,

André

#5

André:

I want to get involved on L10N infrastructure as much as I can. I've been working integrating spanish translations on our own QA builds and have a good understanding on tools involved (Pootle, translate toolkit tools, gsicheck, etc.). Perhaps I'm lacking a better understanding on build tools scripting.

If I can help you or Goran in any form, please indicate it.

Best regards,

Santiago