On Fri, Sep 14, 2012 at 11:33 AM, Dashamir Hoxha <dashoho...@gmail.com> 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 l10n+h...@global.libreoffice.org 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