Hi Jennifer,
On Wed, Jul 17, 2019 at 8:38 PM Jinfeng Huang <[email protected]> wrote:
> Hi Masakazu,
>> Thanks for your reply.
>>
>> It is designed to create a pull request with the schedule ("Topic,
>> translator, reviewer, status (translated/approved)), and provide a platform
>> for effective communication between translators and reviewers.
>>
>
Do you mean we will have a file that contains a table with those columns
and a modification against the file (table) will be shown as the diff? It
sounds like creating an Issue instead is enough to me.
https://swimlanes.io/d/8L04SRASw
An example pull request may help understand the flow. Could you make it on
a test repo?
>
>> Surely, contributors can contribute to translation guidelines, workflow,
>> terms, and other content on GitHub later with PR, and use this repo to
>> report translation issues.
>>
> The actual translation strings are still on Crowdin.
>
>>
>> I've pasted the workflow below, and also sent with attachment (in case
>> one way does not work).
>>
>
Now I can see the workflow, thanks. It would be great if we could have the
source file (ideally editable with free tools) on the repo so that anybody
can modify it and suggest a new flow in the future.
I'm sorry to bother you, but I just want to understand your proposal
correctly. I hope this conversation will reduce future questions.
Thanks,
Masakazu
> [image: translation-workflow.png]
>> Best Regards,
>> Jennifer
>>
>>
