You’re right: the manual uses Sphinx. If you’re up for the task of working on the translation and feel like that’s where you can make the most contribution, you should feel free to go ahead.
But you might find it more efficient to not try to offer a translation of the manual and instead just write an independent document. The Japanese tutorials on Julia we’ve seen, for example, don’t try to be translations at all, which means that they can keep their own pace and don’t fall out of sync because of changes made to the English documentation. — John On Feb 20, 2014, at 9:58 PM, Ismael VC <[email protected]> wrote: > Julia seems to be using sphinx? (I don't know a thing about it but I'm > catching up!) > > https://github.com/JuliaLang/julia/search?q=sphinx&ref=cmdform > > Aparently sphinx already has i8n support: > > http://sphinx-doc.org/intl.html > > But right now I'm lost at the configuration options: > > http://sphinx-doc.org/config.html#intl-options > > I'd really love to start helping an open source project, and participate in > GSoC, etc. but since I'm new to coding, I may be better at doing this sort of > thing for the time being, I believe I will learn Julia better by doing this, > plus I wan't to teach it to my friends at university. :) > > Ismael VC > > El jueves, 20 de febrero de 2014 23:19:28 UTC-6, John Myles White escribió: > I think we historically have encouraged people to not invest too much energy > into translating documentation because the documentation changes frequently, > which means that you end up with either out-of-date documentation or an > endless supply of additional translation work to do. Of, of course, you might > end up with both. > > FWIW, it would be absolutely amazing if Julia had nice i8n for all of its > documentation, including the help docs available in the REPL. But we probably > need to at least get a fully functioning documentation system in English > before we could handle any sort of translation task > > — John
