<html><body>
<p><font size="2" face="sans-serif">What tools did you use for comments and review while you were doing translations for GNOME ?</font><br>
<font size="2" face="sans-serif">Did you use the same tool "GitHub Pull Request" to manage the discussion during reviewing?</font><br>
<br>
<font size="2" face="sans-serif">Regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<tt><font size="2">Łukasz Jernaś <deejay1@srem.org> wrote on 2013/11/02 06:29:39:<br>
<br>
> Łukasz Jernaś <deejay1@srem.org> </font></tt><br>
<tt><font size="2">> 2013/11/02 06:29</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Akihiro Motoki <amotoki@gmail.com>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-i18n] experiences and tips in ops-guide translation <br>
> (a case of Japanese community)</font></tt><br>
<tt><font size="2">> <br>
> Hi Akihiro!<br>
> <br>
> The workflow pretty much sums up how I've been doing translations for<br>
> the GNOME Project in the past. Translators would use their preferred<br>
> tools to work on PO files, commit them into a repository and then a<br>
> reviewer would go through the changes (or the whole file sometimes)<br>
> and add his comments above/below the strings, commit it, and so on<br>
> until no comments were left. Then the PO file would be pushed into the<br>
> upstream repository.<br>
> Only problem was, that the initial learning curve is higher than using<br>
> transifex or other systems...<br>
> <br>
> Regards,<br>
> -- <br>
> Łukasz [DeeJay1] Jernaś<br>
> <br>
> <br>
> On Mon, Oct 28, 2013 at 6:19 PM, Akihiro Motoki <amotoki@gmail.com> wrote:<br>
> > Hi I18N community,<br>
> ><br>
> > I summarized our experiences and tips of Japanese community<br>
> > in ops-guide translation.<br>
> > <a href="https://docs.google.com/presentation/d/">https://docs.google.com/presentation/d/</a><br>
> 1kQN-9765PzNbTSw5YoSl9kNOsUU_Gj74HQZSWBBtD5M/edit?usp=sharing<br>
> ><br>
> > While several months passed after the ops-guide translation finished,<br>
> > I believe it is still useful to clarify requirements for document <br>
> translations<br>
> > and it may bring us some ideas in the discussion in Hong Kong and <br>
> the future.<br>
> ><br>
> > I don't think our approach works well for everyone and is ideal,<br>
> > but at least it works for us and makes us much efficient compared<br>
> > to a case where we use Transifex.<br>
> ><br>
> > Thanks,<br>
> > Akihiro<br>
> ><br>
> > _______________________________________________<br>
> > Openstack-i18n mailing list<br>
> > Openstack-i18n@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> <br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> Openstack-i18n@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
</font></tt></body></html>