Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

2013/10/15 Mateusz Zasuwik <>

So how can we prevent our work from this updates? One word could have 3
different translations and if updating concern all files, there could
appears many new errors. Perspective of eternal correcting the same words
isn't motivating to work.

How can we an mass and repeatedly compare files from LO 4.0 with 4.1

I don't have any One Good Solution.

Perhaps you/someone could write a script that downloads files for desired
branches (say, 4.0 and 4.1) from Pootle, then runs a local update (from 4.1
templates) on the 4.0 files and compares those with 4.1 files downloaded
from Pootle. An immediate problem with this is that strings that have been
moved to new files will probably appear lost.

Another way would be to work on a local copy (using software with
translation memory and a hopefully more reliable update mechanism than
Pootle), update the files from templates yourself, and upload the
translated files to Pootle as needed. Admittedly that approach could be
difficult for larger teams where people have different roles, like
translator, reviewer, manager, etc.

Of course ideally, someone who can should just fix Pootle...

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.