From jni at redhat.com Mon Apr 16 10:04:52 2012 From: jni at redhat.com (James Ni) Date: Mon, 16 Apr 2012 06:04:52 -0400 (EDT) Subject: [zanata-devel] path issue of push-trans-only option In-Reply-To: Message-ID: <6843dff0-875c-49c7-8a56-38581028ce52@zmail14.collab.prod.int.phx2.redhat.com> Hi Sean, David, Ding, I just finished the implementation of '--push-trans-only' option for zanata-python-client, python client can support the offline feature now. I have push the implementation to git-hub, you can test it on your side, if there is issues, please let me know. I think there still some issues left for the '--push-trans-only' option, the main issue is the path. For my implementation, when pushing translations, user only need to specify the transdir option or default to current path if not specified. So we don't know the directory layout of source files on the server. If the directory is not correct, server will complain about that "requested resource is not available". I can give a example for that: 1) pushing source of publican project to server with srcdir default to current path, all the pot files are in ./pot folder zanata push --project-type=podir then the directory on server will be displayed as 'pot/' 2) pushing translation zanata push --push-trans-only --project-type=podir all the translations under locale folders will be pushed to server. then the server will complain about "requested resource is not available" To fix this issue, user have to specify the srcdir to ./pot: "zanata push --project-type=podir --srcdir='./pot'" , then everything should be OK. For gettext project, it is a bit of tricky, since the source file name is different to translation file name (like ibus-table.pot and zh_CN.po), and we use source file name to create the PUT/POST request sent to server, so we have to get the file list of source files first, then get the translation files base on that. So my suggestion is: Maybe i should retrieve the source file list from server first? and try to find translations base on the file list, then pushing translations to server. I think these process could address the issues i just mentioned. What do you think? Best regards James Ni From sflaniga at redhat.com Fri Apr 27 08:29:00 2012 From: sflaniga at redhat.com (Sean Flanigan) Date: Fri, 27 Apr 2012 18:29:00 +1000 Subject: [zanata-devel] Zanata repo split Message-ID: <4F9A58CC.1070101@redhat.com> I think the repo split has mostly settled down now, but there is a change you will need to make on your development machines, to make sure you can always resolve zanata dependencies (and zanata-parent). Just add the attached profile definitions to your ~/.m2/settings.xml between and . This will add the jboss and zanata (cloudbees) repos whenever you do a Maven build. You can disable the repos by using -Dzanata.repo.off and -Djboss.repo.off. I know it's a nuisance, but we'll need it anyway, so that we can get the elements out of our poms. Among other reasons, it's a requirement if we're going to get Zanata into Maven Central. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: zanata-repo.xml Type: text/xml Size: 3333 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: