I agree with this. We have to consider many factors, like what the document is, and who can translate it/verify the translation. Right now, we have exactly one person per language (except I guess we have two for Czech), so our ability to verify translations, much less make them is very limited. If we tried to do it outside of Code-In, we would have to drop the review requirement, as there's simply no one else to verify it, which makes me a little uneasy about it. As was mentioned earlier, it's better to have no translation than a poor translation, and while I'm not saying that anybody is poor at translating, the fact is, with no quality assurance, we simply don't know how good it is.
But I agree that some things, like the webpage or Wikipedia articles, are very good to translate for outreach purposes. So Ondrej, with your work, is http://www.google-melange.com/gci/task/view/google/gci2011/7127301 still relevant? If so, can you update it with what still needs to be done? Otherwise, let's close it. Aaron Meurer > Language competence isn't a binary thing. I'm sure that a large majority > of French Python programmers can understand a typical docstring, but > most of them are probably not comfortable reading a long text in > English. Having a tutorial in French can give them an easy entry point, > allowing them to decide whether it's worth their time to make the effort > of understanding the rest of the docs. > > > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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/sympy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy?hl=en.
