Re: [libreoffice-l10n] Git repo for l10n?

Hi,


Am 04.10.2010 20:44, schrieb Guido Ostkamp:
> 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 ;) )


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

regards,

André
--
To unsubscribe, send an empty e-mail to l10n+unsubscribe@libreoffice.org
List archives are available at http://www.libreoffice.org/lists/l10n/
All messages you send to this list will be publicly archived and cannot be deleted.