>
>
> But can be too : menu in the notebook, the graphical web interface for the
> cloud, the alphabet (czech,...) or keyboard, the latex translator...the
> localization of various software (pari,...) included in SAGE.
>
>
Sagenb itself is fully localizable. As for
SMC, https://github.com/sa
On Wed, 5 Aug 2015, William Stein wrote:
There's a (depressing) discussion about this problem here:
http://stackoverflow.com/questions/27214065/how-to-docstring-in-python-for-multiple-languages
Assuming we would have all the needed software, how would we use them?
Let's assume that foo(x) is
I am not so sure about the needed "localization"...
Yes, could be the docstrings (= the text used as comment in various parts
of SAGE python component)in that case, I guess as a python newbee, you
have python tool for extract text comments from code and polib to merge
them all in text fil
Well there isn't much tooling (since one rarely wants to translate
docstrings), but its easy to programmatically extract docstrings. Then just
write them out in a pofile, translate, and change ? to look up the
translation.
--
You received this message because you are subscribed to the Google G
On Wed, Aug 5, 2015 at 8:41 AM, kcrisman wrote:
> Surely this is far too late but as I think you know from other stuff (you
> are the one contributing this, I believe) the sagenb can be localized, Sage
> proper does not (yet) have any facility for doing so.
>
There's a (depressing) discussion abo
Surely this is far too late but as I think you know from other stuff (you
are the one contributing this, I believe) the sagenb can be localized, Sage
proper does not (yet) have any facility for doing so.
I have an idea to create Ukrainian localization of Sage. It will be useful
> for many Ukrai
