<div dir="ltr"><div>On Tue, 3 Jul 2018 at 00:45 Shengjing Zhu <<a href="mailto:zsj950618@gmail.com">zsj950618@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I just looked at the current status for zh_CN/zh_TW translation<br>
coverage. For python-newest, zh_CN is 3.06%, zh_TW is 0.95%; for<br>
python-36, zh_CN is 0.93%, zh_TW is 1%. Both are far behind :( ,so<br>
opencc won't help much here.<br><br></blockquote><div><br></div><div>Agree. For zh_TW translations, we're still working on tutorials, glossary and builtin functions, they're not that much compared to other parts of the documentations.</div><div><br></div><div>But once we both reach the first phase goal, I think we can start collaborating with opencc, e.g. the zh_TW team work on the translations for Library Reference and the zh_CN team work on Language Reference, then both teams will have someone periodically take each other's translations, process them using opencc, and then adjust them as Shengjing mentioned, and eventually merge them.</div><div><br></div><div>This can definitely work out, we'll just have to make sure we're working on different parts of the documentation, we can do that through a shared project board or something like that.</div><div><br></div><div>Actually, right now I think library/functions is a great chance for us to experiment on opencc as our team have barely translated the page, but I saw the zh_CN translations have that translated about 2/3 of them already.</div><div><br></div><div>Best Regards,</div><div>Adrian</div></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Wey-Han "Adrian" Liaw (@adrianliaw2000)</div><div><a href="https://linkedin.com/in/adrianliaw">https://linkedin.com/in/adrianliaw</a></div><div><a href="https://github.com/adrianliaw">https://github.com/adrianliaw</a></div></div></div>