[Openstack-i18n] experiences and tips in ops-guide translation (a case of Japanese community)
amotoki at gmail.com
Sat Nov 2 09:43:25 UTC 2013
The approach we used is not ideal and it is just a workaround.
I agree that the problem that the initial barrier becomes higher than using
I would like to share our experience that Transifex is not ideal for large
I hope this is a good input for requirements when considering another
or improving Transifex.
We first use Transifex to translate strings, and after completing the first
of translations, we use GitHub. It lowered the initial barrier.
During the review phase, only a few folks including me edited PO files
and other folks focused on the review (read the drafts and comments on
It can be done through the web interface. There were few confusions and it
However, this process requires some person(s) who edit/update the PO files
and it may increase the barrier to join translations.
On Sat, Nov 2, 2013 at 7:29 AM, Łukasz Jernaś <deejay1 at srem.org> wrote:
> Hi Akihiro!
> The workflow pretty much sums up how I've been doing translations for
> the GNOME Project in the past. Translators would use their preferred
> tools to work on PO files, commit them into a repository and then a
> reviewer would go through the changes (or the whole file sometimes)
> and add his comments above/below the strings, commit it, and so on
> until no comments were left. Then the PO file would be pushed into the
> upstream repository.
> Only problem was, that the initial learning curve is higher than using
> transifex or other systems...
> Łukasz [DeeJay1] Jernaś
> On Mon, Oct 28, 2013 at 6:19 PM, Akihiro Motoki <amotoki at gmail.com> wrote:
> > Hi I18N community,
> > I summarized our experiences and tips of Japanese community
> > in ops-guide translation.
> > While several months passed after the ops-guide translation finished,
> > I believe it is still useful to clarify requirements for document
> > and it may bring us some ideas in the discussion in Hong Kong and the
> > I don't think our approach works well for everyone and is ideal,
> > but at least it works for us and makes us much efficient compared
> > to a case where we use Transifex.
> > Thanks,
> > Akihiro
> > _______________________________________________
> > Openstack-i18n mailing list
> > Openstack-i18n at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack-i18n