Re: [Doc-SIG] Translating sample programs in documentation
Hi Julien, Our current sphinx-docs configuration (default about this matter) is not to provide those blocs in the po files. (It's the `gettext_additional_targets entry).` If I understand correctly, that makes it technically impossible to achieve what I described, unless we change the sphinx-docs configuration? Yes, until we change the cpython sphinx-docs configuration in `Doc/conf.py`. Thanks I'll see how to change that. Above said, I totally agree this practice means much more work when translating, not to mention the potential controversies even among Chinese developers. Still, I'd look forward to trying the idea out somewhere proper. I think we can resume this thread when ~6 translations have reach ~99% translated (is there a currently living translation of the doc in chinese? Heard of https://github.com/python-doc-tw/python-doc-tw for zh-tw and heard of some work on transifex for zh-cn (1.4% translated as of fall 2017). Frankly, I don't see the relevance between the progress of translation and whether this discussion can be continued. The ability to translate elements in sample programs would certainly give me more motivation to contribute. Best wishes, Xuan. ___ Doc-SIG maillist - Doc-SIG@python.org https://mail.python.org/mailman/listinfo/doc-sig
Re: [Doc-SIG] Translating sample programs in documentation
> > Frankly, I don't see the relevance between the progress of translation and > whether this discussion can be continued. The ability to translate elements > in sample programs would certainly give me more motivation to contribute. > Personally speaking, I'm strong -1 on translating code, especially for identifiers. (weak -1 on comments and docstring, strong -1 on identifiers). In Japan, many Pythonista doesn't use Japanese identifiers regulally. There are many "looks similar, but different" characters in Japanese. So ASCII is more readable than Japanese Hanji. I don't know about Chinese practice, but how popular Chinese identifiers are? If you're participating large Chinese community, could you try survey about it there? At least, I think Chinese translation team's agreement is needed before trying it. Regards, -- INADA Naoki ___ Doc-SIG maillist - Doc-SIG@python.org https://mail.python.org/mailman/listinfo/doc-sig
Re: [Doc-SIG] Translating sample programs in documentation
Thanks for the feedback. A couple of months ago, I heard from one experienced Japanese developer that he thought Japanese naming for variables and functions are easy to read and write in his practice. He also mentioned that many others don't like the practice. Similarly in Chinese developer community, more developers dislike Chinese naming, even though IMO this opposition is not well-grounded in most cases. Additionally and pitifully, quite some developers, especially beginners, don't even know they can use unicode naming in Python (or any programming languages) and it may result in better readability. From my own experience with some projects in Java/JavaScript, Chinese naming is more readable even for myself, who have programmed in English-speaking environment for many years. Also, I know there are beginners in China who would love to have tutorials that contain sample programs with Chinese naming, based on the discussions in the github organization I created for programming in Chinese language. IMO it's almost impossible to verify if this practice is generally better for beginners or not, without actually trying it out in limited scope, like the official tutorial. To clarify, I'm not pushing other languages to do the same. Best wishes, Xuan. On 4/16/18 3:28 AM, INADA Naoki wrote: Frankly, I don't see the relevance between the progress of translation and whether this discussion can be continued. The ability to translate elements in sample programs would certainly give me more motivation to contribute. Personally speaking, I'm strong -1 on translating code, especially for identifiers. (weak -1 on comments and docstring, strong -1 on identifiers). In Japan, many Pythonista doesn't use Japanese identifiers regulally. There are many "looks similar, but different" characters in Japanese. So ASCII is more readable than Japanese Hanji. I don't know about Chinese practice, but how popular Chinese identifiers are? If you're participating large Chinese community, could you try survey about it there? At least, I think Chinese translation team's agreement is needed before trying it. Regards, ___ Doc-SIG maillist - Doc-SIG@python.org https://mail.python.org/mailman/listinfo/doc-sig
