<div dir="ltr">Thank you for your inputs, as of right now, I think I will simply update the specified HTextFlowTargets' state to 3 in the database (I've done this on my test database and apparently it hasn't broken anything yet).<div> </div><div>Regards,</div><div> </div><div>Nghia</div></div><div class="gmail_extra"> <div class="gmail_quote">2013/9/24 Isaac Rooskov <<a href="mailto:irooskov@redhat.com" target="_blank">irooskov@redhat.com</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree with Sean on the topic of defaults for this, and that of course we will allow people to alter this as is best for their project. Thanks, Isaac<div class="HOEnZb"><div class="h5"> On 09/17/2013 01:24 PM, Sean Flanigan wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> From the project maintainer's point of view, I think it could be argued that "requires-approval" projects should only include approved translations when pulling (unless otherwise specified). Otherwise unreviewed translations could be accidentally included in a software/documentation release. So this is a quality issue. Then if someone wants to fetch the translated (non-approved) translations to do some offline translation, that could enabled by a client option. And then you have the problem of preview builds, where someone (maintainer or a translator) pulls down all the translations to generate some sort of preview (eg a Publican build, or a software build), perhaps even as part of the review process. For preview builds, you may want the unapproved translations. The problem is that all three use cases are using the same command, and the most sensible default is different for each use case. Whatever the default should be, we definitely need the ability for the client to choose. On 2013-09-16 08:33, Patrick Huang wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi Nghia, Priority of RFE (Request for enhancement) is discussed and set by Isaac our product owner before each release. We will finish off Zanata 3.1 release in October and start planning next version. Let's see if it will be scheduled for the next one. As for the ext parameter, it stands for extension. Right now we only support two extensions: "gettext"(deal with PO header etc) and "comment"(comment in PO file). Forcing pulling only Approved translation can be a new RFE. If you want you can fire a bug at <a href="https://bugzilla.redhat.com/enter_bug.cgi?format=guided&product=Zanata" target="_blank">https://bugzilla.redhat.com/enter_bug.cgi?format=guided&product=Zanata</a> (You can also access this link from you Zanata instance via footer link Support->Report problem and put "RFE" in front of your bug summary). We will then pick it up from there and prioritize it accordingly. Regards, Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat ------------------------------------------------------------------------ *From: *"Nghia Duong" <<a href="mailto:nghia.duong@crossknowledge.com" target="_blank">nghia.duong@crossknowledge.com</a>> *To: *"David Mason" <<a href="mailto:damason@redhat.com" target="_blank">damason@redhat.com</a>> *Cc: *"Patrick Huang" <<a href="mailto:pahuang@redhat.com" target="_blank">pahuang@redhat.com</a>>, <a href="mailto:zanata-users@redhat.com" target="_blank">zanata-users@redhat.com</a> *Sent: *Friday, September 13, 2013 5:06:22 PM *Subject: *Re: [zanata-users] Bulk-approval of translations? Hi David and Patrick, Thank you both for the quick answers. @Patrick: It helps to know that this is in your backlog. I am also aware that reviews can be made optional but I am currently trying to sketch out some localization workflows and translation reviews appear essential to me, at least for the QA phase. Would you have any timeline info on when that functionality will be implemented? If I remember correctly, the TranslatedDocResource endpoint of the REST API supports an "ext" <<a href="https://zanata.ci.cloudbees.com/job/zanata-api-site/site/zanata-common-api/rest-api-docs/resource_TranslatedDocResource.html#PUT" target="_blank">https://zanata.ci.cloudbees.com/job/zanata-api-site/site/zanata-common-api/rest-api-docs/resource_TranslatedDocResource.html#PUT</a>> parameter when pushing translations, is there anyway I can "force" the approved status there instead? (I can't seem to find the documentation about the content of "ext") @David: Thank you for the documentation, it is very clear to me, but as I said above, I think reviews is necessary for our project. Keep up the good work though! Regards, Nghia 2013/9/13 David Mason <<a href="mailto:damason@redhat.com" target="_blank">damason@redhat.com</a> <mailto:<a href="mailto:damason@redhat.com" target="_blank">damason@redhat.com</a>>> Hi Nghia, ----- Original Message ----- > From: "Patrick Huang" <<a href="mailto:pahuang@redhat.com" target="_blank">pahuang@redhat.com</a> <mailto:<a href="mailto:pahuang@redhat.com" target="_blank">pahuang@redhat.com</a>>> ... > We are working on documentations in current release but just so you know, > approved state is only required when your project version requires > translation review. The documentation mentioned by Patrick can be previewed at <a href="http://zanata.org/new/help/review/review-workflow/" target="_blank">http://zanata.org/new/help/review/review-workflow/</a> Let me know if you feel there is anything missing or that could be presented better and I can adjust it. Cheers, David Mason Software Engineer L10n Engineering Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 > > > From: "Nghia Duong" <<a href="mailto:nghia.duong@crossknowledge.com" target="_blank">nghia.duong@crossknowledge.com</a> <mailto:<a href="mailto:nghia.duong@crossknowledge.com" target="_blank">nghia.duong@crossknowledge.com</a>>> > To: <a href="mailto:zanata-users@redhat.com" target="_blank">zanata-users@redhat.com</a> <mailto:<a href="mailto:zanata-users@redhat.com" target="_blank">zanata-users@redhat.com</a>> > Sent: Friday, September 13, 2013 1:13:49 AM > Subject: [zanata-users] Bulk-approval of translations? > > Hi all, > > I would like to know whether there is a way for reviewers to approve all > translations of a given document on Zanata? > > I have a set of approved translations (from PO files) that I have uploaded > (via the REST API) to Zanata. But now they are only saved as translated and > not approved, is there any way to approve all of the translations without > going through each and everyone of them (I have a lot)? > > Regards, > > Nghia _______________________________________________ zanata-users mailing list <a href="mailto:zanata-users@redhat.com" target="_blank">zanata-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/zanata-users" target="_blank">https://www.redhat.com/mailman/listinfo/zanata-users</a> </blockquote> </blockquote> -- </div></div> Isaac Rooskov Supervisor, Localization Services Product Manager, Zanata Red Hat </blockquote></div> </div>