Hi Sophie, all,
On 2010-12-30 at 15:18 +0300, Sophie Gautier wrote:
I download/update my language .po files using svn (with a very simple script)
and use Lokalize with a Translation Memory database, which is now 125M, for
translation and a glossary for words of .5 MB. Uploading is using svn commit.
Compared to using Pootle this is far more easy. Using svn or git for download
and upload is using less bandwith, because only the differences are
transported.
Thank you very much for your feedback on this. It's great if we can
share others experience on this.
The only thing I'm afraid of is the technical skills needed for the
steps to download or upload the files. Also what will be the process
under Windows, is it easy to commit on git or svn or whatever using
other OS than Linux (I remember at the very beginning of the OOo FR
site, I was under Windows 98 and comits to the cvs repository was not
exactly what I call fun ;-)
I've just found
http://translate.sourceforge.net/wiki/pootle/version_control
that describes how to connect Pootle with a version control system.
From what I understand, this is built into Pootle.
Basically, it suggests what Freek says - having git as the authoritative
source, while providing all the strengths of Pootle as Andras explained
(xliff, downloading/uploading of tarballs, etc.)
An admin with the appropriate rights gets an [Update] button that
transparently updates the files from git (should there be changes in git
by the translators that commit their changes directly). The page says
that there is also possible to trigger commit from the Pootle server,
though there are some troubles there; I'll look more.
If this works, to me it seems that this is be the best from all the
worlds:
- for Freek, or others who prefer to work with version control system
directly, the method known from Gnome and KDE would be available, ie.
work directly with the .po files in git
- for Martin, or others that prefer uploading tarballs somewhere, they
could decide whether to work directly with git (change of their
workflow), or to upload the .zips to Pootle, and let an admin do the git
updates
- for people that do not want, or are not used to work with a version
control system directly, or want to use xliff as the source, they could
work with Pootle only, and let the updates and commits on an admin
How does that sound?
Regards,
Kendy
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
Context
- Re: [libreoffice-l10n] LO Pootle · Jan Holesovsky
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.