On Tue, May 22, 2012 at 10:51 AM, Tim Cera wrote:
>>>
>> Docstrings are not stored in .rst files but in the numpy sources, so there
>> are some non-trivial technical and workflow details missing here. But
>> besides that, I think translating everything (even into a single language)
>> is a massive
>
>
>> Docstrings are not stored in .rst files but in the numpy sources, so
> there are some non-trivial technical and workflow details missing here. But
> besides that, I think translating everything (even into a single language)
> is a massive amount of work, and it's not at all clear if there's
On Mon, May 21, 2012 at 10:44 PM, Ralf Gommers
wrote:
> Thinking about what languages to translate into would also make sense, since
> having a bunch of partial translations lying around doesn't help anyone.
> First thought: Spanish, Chinese.
It's not like one can tell two translator volunteers t
On Sun, May 20, 2012 at 11:59 PM, Tim Cera wrote:
> Are you thinking only about documentation in .rst files (like the
>> tutorials), or also the docstrings themselves? The former may be feasible,
>> the latter I think will be difficult.
>>
>>
> Everything. Within the documentation editor the RST
>
> Are you thinking only about documentation in .rst files (like the
> tutorials), or also the docstrings themselves? The former may be feasible,
> the latter I think will be difficult.
>
>
Everything. Within the documentation editor the RST docstrings are parsed
from the functions, so instead of
On Sun, May 20, 2012 at 12:04 AM, Tim Cera wrote:
> I have thought for a long time that it would be nice to have numpy/scipy
> docs in multiple languages. I didn't have any idea how to do it until I
> saw http://sphinx.pocoo.org/intl.html. The gettext builder which is a
> requirement to make th
On Sat, May 19, 2012 at 8:16 PM, Nathaniel Smith wrote:
> help() just returns the __doc__ attribute, but a large number of numpy's
> __doc__ attributes are set up by code at import time, so in principle even
> these could be run through gettext pretty easily.
>
I didn't know that. I suggested mo
On May 19, 2012 11:04 PM, "Tim Cera" wrote:
> A user would then install a language kit, maybe something like scikits
and access the translated docstring with a new 'np.info'. As near as I can
figure, Python 'help' command can't be replaced by something else, so
'help' would always display the Eng
I have thought for a long time that it would be nice to have numpy/scipy
docs in multiple languages. I didn't have any idea how to do it until I
saw http://sphinx.pocoo.org/intl.html. The gettext builder which is a
requirement to make this happen is relatively new to sphinx.
Outline of above ap
