-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Bobo,
translating the official documentation from python.org is a great idea! Cool! But I am not sure whether your approach, if I understand it correctly, is the best way to do it. You want to copy the original documentation and make a line by line translation of the text inside the text, so that you end up with a source containing two languages. I think that it will be hard to read the source and work with it. But there is an other thing. What will you do, if someone changes the original file of the english documentation? You must then somehow merge the changes into your file and translate them. The documentation of Python lives in some versioning system. I am not sure if it is svn or any DVCS. I would recommend to start a standalone chinese transation of the documentation in the same repository or in your own. If you need to have a side by side view of the english and chinese version, you can arrange the editor windows on your screen. You can rely more or less on linenumbers to find the translation of any line in the original. When you are finished with your translation you just have to track the changes in the original with the RSS-stream of the repository or the notifications on the mailing list (there is one, isn't it?) What you are asking for is a mechanism to mark a file as a translation of an other file to build a multilingual website. The Python CMS Plone has such a feature. It is called LinguaPlone. With Plone you can build multilingual websites, that means that you can click on a link to see the chinese or german translation of an english text. This indeed would be an interesting feature in Sphinx too. But I would say that you should never mix languages in one file but have seperate files for each translation. Imagine a text translated into the 26 languages of the European Union. ;-) This could be made by marking one text as the canonical language, which means that the content of this file is canonical and that all translations are mere translations. Then you must somehow link this file to the translation files. This could be made by hand but each translation should have links to the other language versions so that I can jump from one translation to the other. The really tricky part is the navigation, because you need to have different navigation trees for all languages. Anyway, I think it would be cool to have a chinese translation of the Python documentation and I hope that my remarks are helpful. Regards, juh - -- Plone 3 http://www.hasecke.com/plone-benutzerhandbuch/3.3.5/ Plone 4 http://www.hasecke.com/plone-benutzerhandbuch/4.0/ Über PayPal für das Benutzerhandbuch spenden: http://bit.ly/k5ay2E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6pAaUACgkQPUzUEFbILMQokQCeK3Y07aOZQhuAgkES7eBplAmN oocAoJQprkHTnJg4I/9OMg8MZTHfsbne =n1Iy -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
