<div dir="ltr">Not really, if the main bulk of documentation is to be stored in docstrings or made from them automatically for every future release. These things go untranslated for years for less common languages, cause problems with non-ASCII characters and so on.<br><br>But I think that there is not much need for translated docstrings. At least in Russia, everyone in IT/CS and nearly everyone in life sciences knows at least some English. What I was talking about is multilingual wiki or at least a few manuals, cookbooks and "Getting started"s, or maybe Biopython workshop, because it may help bioinformatics teachers.<br><div class="gmail_extra"><br><div class="gmail_quote">2014-10-14 19:36 GMT+09:00 Peter Cock <span dir="ltr"><<a href="mailto:p.j.a.cock@googlemail.com" target="_blank">p.j.a.cock@googlemail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Alexey,<br>
<br>
I am not aware of any Russian translation (another interesting language<br>
in terms of non-ASCII characters and the potential markup implications).<br>
<br>
Do you have any thoughts on if and how to track any future translation<br>
work in the main Biopython repository side by side with the English<br>
version to help keep things up to date?<br>
<span class="HOEnZb"><font color="#888888"><br>
Peter<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Tue, Oct 14, 2014 at 11:32 AM, Alexey Morozov<br>
<<a href="mailto:alexeymorozov1991@gmail.com">alexeymorozov1991@gmail.com</a>> wrote:<br>
> Speaking of translations, is Biopython documentation being translated into<br>
> Russian? I could contribute to such a work, but definitely won't make it all<br>
> alone.<br>
><br>
> 2014-10-14 18:48 GMT+09:00 Peter Cock <<a href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>>:<br>
>><br>
>> Hi Yanbo,<br>
>><br>
>> Translations are an interesting case - some of the tutorial was also<br>
>> translated into Japanese once, but this work often goes out of date :(<br>
>> Using LaTeX it would be possible to embed alternative versions<br>
>> into the same file - even at a chapter or section level (you can have<br>
>> conditional blocks with if statements - so new sections could be in<br>
>> English only initially while waiting for translation). I don't think you<br>
>> can do this with Sphinx - or can you?<br>
>><br>
>> Peter<br>
>><br>
>> P.S. The source files for the Chinese translation is here, plus a port<br>
>> of the LaTeX tutorial into *.rst:<br>
>> <a href="https://github.com/bigwiv/Biopython-cn" target="_blank">https://github.com/bigwiv/Biopython-cn</a><br>
>><br>
>><br>
>> On Tue, Oct 14, 2014 at 10:00 AM, Yanbo Ye <<a href="mailto:yeyanbo289@gmail.com">yeyanbo289@gmail.com</a>> wrote:<br>
>> > For the Tutorial of Sphinx, here is a Chinese version that we translated<br>
>> > last year. All format seems ok, including equations, chapter<br>
>> > hyperlinks,<br>
>> > references, etc. But it cannot pass the pdf compiling process on<br>
>> > readthedocs. I'm not a expert on this. Maybe someone can give it a try.<br>
>> ><br>
>> > <a href="http://biopython-cn.readthedocs.org/zh_CN/latest/index.html" target="_blank">http://biopython-cn.readthedocs.org/zh_CN/latest/index.html</a><br>
>> _______________________________________________<br>
>> Biopython-dev mailing list<br>
>> <a href="mailto:Biopython-dev@mailman.open-bio.org">Biopython-dev@mailman.open-bio.org</a><br>
>> <a href="http://mailman.open-bio.org/mailman/listinfo/biopython-dev" target="_blank">http://mailman.open-bio.org/mailman/listinfo/biopython-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Alexey Morozov,<br>
> LIN SB RAS, bioinformatics group.<br>
> Irkutsk, Russia.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><font face="arial,helvetica,sans-serif">Alexey Morozov,<br>LIN SB RAS, bioinformatics group.<br>Irkutsk, Russia.<br></font>
</div></div>