[Openstack-i18n] experiences and tips in ops-guide translation (a case of Japanese community)

Łukasz Jernaś deejay1 at srem.org
Fri Nov 1 22:29:39 UTC 2013

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.
> https://docs.google.com/presentation/d/1kQN-9765PzNbTSw5YoSl9kNOsUU_Gj74HQZSWBBtD5M/edit?usp=sharing
> While several months passed after the ops-guide translation finished,
> I believe it is still useful to clarify requirements for document translations
> and it may bring us some ideas in the discussion in Hong Kong and the future.
> 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

More information about the Openstack-i18n mailing list