Open Stack

2015-11-18 14:34 GMT+09:00 KATO Tomoyuki <tomo at dream.daynight.jp>:
>> On 2015-11-17 13:05, KATO Tomoyuki wrote:
>> >> openstack-manuals is open again.
>> >>
>> >> We still do not publish translated manuals, I'm fixing this (needs a
>> >> project-config change), the rest looks fine but I appreciate if you keep
>> >> your eyes open and speak up if I missed anything,
>> >
>> > Andreas,
>> >
>> > Needless to say, not your overlook.
>> > I think we can improve translation resource generation method in recent days.
>> > As long as Liberty, we publish only install guides,
>> > so we can simply generate one pot file without common-rst.
>> > I checked our tool chain, it looks okay to improve by updating doc/generatepot-rst.
>> > Also, openstack-doc-tools skip common-rst process if it doesn't exist.
>> >
>> > Thought?
>> >
>> > [1] https://git.openstack.org/cgit/openstack/openstack-manuals/tree/tools/generatepot-rst.sh#n38
>> > [2] https://git.openstack.org/cgit/openstack/openstack-doc-tools/tree/bin/doc-tools-check-languages#n63
>>
>> We could do - but wouldn't that make it harder to copy translations back
>> to master?
>
> Here is a refined idea: https://review.openstack.org/#/c/246751/
> I'm not sure I18n team want to copy install guide translations back to master,
> but it uses standard common-rst.pot, so I do not think it make it harder to copy process.
> This reduces messages from 2228 to 1849.
> # Huge translation resources sometimes demotivate translators :)

Talking about translation merge back to master, IMO it should be avoided,
at least we should be careful.
In my experience, merging in Zanata sometimes leads to some confusion.
If we use a merge in Zanata, a target branch of a merge should be
marked read-only.
Otherwise, some works in the target branch will be lost.

>
> Thanks,
> KATO Tomoyuki
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs