Hi Lukasz,

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 transifex.
I would like to share our experience that Transifex is not ideal for large documents.
I hope this is a good input for requirements when considering another translation system
or improving Transifex.

We first use Transifex to translate strings, and after completing the first round
of translations, we use GitHub. It lowered the initial barrier.
During the review phase, only a few folks including me edited PO files directly
and other folks focused on the review (read the drafts and comments on GitHub).
It can be done through the web interface. There were few confusions and it worked.

However, this process requires some person(s) who edit/update the PO files
and it may increase the barrier to join translations.

Thanks,
Akihiro




On Sat, Nov 2, 2013 at 7:29 AM, Łukasz Jernaś <deejay1@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...

Regards,
--
Łukasz [DeeJay1] Jernaś


On Mon, Oct 28, 2013 at 6:19 PM, Akihiro Motoki <amotoki@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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n