Thanks Chris,
I am not trying to cut out of the loop Pootle, I am trying to cut out of
the loop the manual work. There are so many PO files that it is impossible
to upload all of them manually as frequently as I would like.
I would prefer to do the merge offline, on the desktop, using tools like
Lokalize, which are wonderful for merging PO files. Then I would like
to upload the merged PO files automatically.
Probably some curl script can do the job. I will have to try it.
Another question:
Once I have downloaded all the PO files (which can be done easily)
how can I apply them so that I can check the translations in the context?
For example, for some other (gnome) application I can convert PO files to MO
files, put them to a special location (directory), and restart the application.
However I am not sure whether this works with LibreOffice PO files as well.
Can somebody help with this?
Regards,
Dashamir
P.s. Chris, I see on the admin panel that you are listed as an Albanian language
user (cjl). How come?
On Fri, Sep 14, 2012 at 6:36 PM, Chris Leonard <[email protected]> wrote:
> On Fri, Sep 14, 2012 at 11:33 AM, Dashamir Hoxha <[email protected]> wrote:
>> I would like to be able to export PO files from the command line,
>> and to import them from the command line again.
>>
>> If all the PO files are kept in a GIT repository, this can be done easily:
>> first CLONE the repository, and then PULL to get the latest version of
>> the PO files, modify them locally, and finally PUSH to import them into
>> the main repository (upstream).
>>
>> Dashamir
>>
>
>
> Well, pulling all of the PO files is easily done from the command line
> with wget on the download "Zip of Directory" link on the Translate
> tab.
>
> https://translations.documentfoundation.org/sq/llibo_ui/export/zip
> https://translations.documentfoundation.org/sq/libo_help/export/zip
>
> That will get you the current PO files hosted in Pootle.
>
> I personally find the deeply nested folder structure of the LO UI on
> Pootle a bit challenging, although I understand why it is set up that
> way. I developed a little script (collapse36.sh) to help me get all
> of the PO files into a single folder (only one layer deep). Please
> note that to accomplish this is it necessary to rename files that
> share a name but are differentiated by their location in the folder
> hierarchy.
>
> The renaming is easy enough to decipher and reverse by just looking at
> the lines of the shell script. Please note that the script is
> intentionally destructive of the original folders in order to monitor
> completeness, so only do it with a copy of your downloaded and
> unzipped file in a directory of it's own.
>
> Upload is another question entirely. Speaking only for myself (as
> Translation Team Coordinator of another project, not LO). Direct
> commit to the git repository /po directories bypassing Pootle is a
> simply bad idea. The Pootle workflow serves multiple important
> purposes all of which are defeated by direct git commits of PO files.
>
> I cannot think of an easy way to do mass uploads via the Pootle web
> UI. Unless you are going to be given an elevated level of privs on
> the Pootle server itself (and SHH access to log in), this may remain a
> repeated manual process to get the PO files into Pootle (where they
> belong). Again, speaking only for Sugar Labs (and not LO) I can tell
> you that very few people will ever get a privileged login to our
> Pootle server, this is not something you just hand out for convenience
> sake.
>
> Pootle is an important tool for collaboration and quality control.
> Trying to cut it out of the loop is not recommended.
>
> Just my 2 cents.;
>
> cjl
--
Unsubscribe instructions: E-mail to [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
