<div dir="ltr"><div class="gmail_quote"><div dir="ltr">Campbell Barton <<a href="mailto:ideasman42@gmail.com">ideasman42@gmail.com</a>> 於 2016年2月20日 週六 上午2:10寫道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Recently I found this article about 2 other projects migrating from a<br>
Wiki to Sphinx [0] for very similar reasons to us.<br>
<br>
These are quite technical projects, and some of the pain-points we ran<br>
into (build times and having to write our own tools in some cases)<br>
aren't mentioned.<br>
Nevertheless, interesting to see how other projects handle this.<br>
<br>
[0]: <a href="https://opensource.com/business/16/1/scale-14x-interview-dru-lavigne" rel="noreferrer" target="_blank">https://opensource.com/business/16/1/scale-14x-interview-dru-lavigne</a><br>
<br></blockquote><div><br></div><div>As a translator, I would like to endorse the ability of Sphinx to create po file to do multilingual support. Wiki systems are hard to achieve that. The most resources are in English, and the official content is English too. In order to spread more widely and lower the boundaries for local newcomers, translations are a key way to make blender globally. In all, we do need translations for blender manual.<br><br>In the past, translators have to track English pages for changes and update the translations accordingly. Most end giving up because the diff work is tiring. Although there is a <a href="http://translatewiki.net">translatewiki.net</a> translate extension, I hardly find other FLOSS projects using this technology. I am not sure if it actually works or not.<br><br></div><div>Anyway, in my own opinion, I strongly suggest finding some ways for translators to work on easier, no matter what the platform is.<br></div></div></div>