Re: [Hyperledger Technical WG China] [i18n] Status report on translation of Fabric docs
toggle quoted messageShow quoted text
Thanks for your replay, for now our translating work is mainly for fabric project and Chinese language, and just a dozen translators, so that the workflow is good for us now. We are also looking for a way adopting different projects and manage the updates conveniently, because we also want to translate the docs of other projects like Indy. We have learned the workflow of kubernetes, they also use github for translating jobs, they made scripts to generate github issues automatically, and developed a slack robot to manage the issues. We want to use the same workflow, but Fabric is different with kubernetes, the docs are separated from code repo and showed in a website they developed, not readthedocs. So we have to find other ways and tools, maybe we also have to develop some tools for this job. We will not use Transifex because it is really inefficient for us, translate with text editor and manage the translations with github is more efficient, we will keeping using github for translating until find a better way.
Now, what we want is :
1. Show the Chinese translations in the official docs page, so that more developers would see the translations, and may attract more translators.
2. Create a new repo in github named “fabric-i18n” or “hyperledger-i18n”, so we can put the docs of different projects into the same repo, like sdk, fabric-ca, Indy projects not only Fabric.
About in-app localization, we won’t do it right now, it is much complex we should change many codes in Fabric, and actually most developers are used to English output, so the translation is not necessary now.
At 2020-01-17 12:07:40, "Brian Behlendorf" <bbehlendorf@...> wrote:
This has gone without a reply since it was posted so I thought I would add one,