> > > Just curious on how that may have come along. At least for the notebook > it > > would be great to have some additional localization - and it would be a > good > > step toward localizing the cloud, or Sage proper, etc. > > I would love to do Hindi and Punjabi translations(Indian Languages). > Please provide the steps to do. > > Hi Arshpreet,
(cc: sage-devel as this is really of more general interest...) That would be most welcome. There are two current types of localization projects. 1) Translating various non-dynamically-generated documentation. See e.g. http://git.sagemath.org/sage.git/tree/src/doc/fr/tutorial for some examples. Basically, you take the English documentation and create new .rst files etc. See http://www.sagemath.org/doc/developer/sage_manuals.html for (a few) more details on this. If you have a Trac account (http://trac.sagemath.org/) then you could even create your own branch for review; otherwise it is possible to email a few of us who are interested a file and have someone turn it into something that could be reviewed. (For which purpose we would need another speaker of Hindi familiar with math and programming in those languages! Or two or three.) By the way (to others listening), this is not the "canonical" way to do this. But I don't know if it would be worth doing the entire workflow at http://sphinx-doc.org/latest/intl.html especially since we already have a number of translations going. That might be more sustainable long-term, on the other hand, especially when things change - some translations of the tutorial are probably fairly outdated. (Well, the tutorial itself is fairly outdated!) 2) Localizing the Sage notebook. This does not involve any math, really, but rather of creating a new locale and localization in the notebook so that things like "Save" and "Stop this worksheet" etc. are in the appropriate language (everything but "Sage", really!). See https://github.com/sagemath/sagenb/blob/master/README.rst#localization for at least a few directions. Again, this in principle happens on github, but one could send files to an interested party. (See also https://github.com/sagemath/sagenb/pull/237 and https://github.com/sagemath/sagenb/pull/238 for some progress in making this more sustainable as well.) Good luck and I hope we hear from you! *) To others - so... what about starting to plan for localizing the Sage *documentation*? This would be a mammoth project, but I'm wondering how difficult it would be to build in the infrastructure only. Does autodoc (or whatever Sphinx we use for this) play well with the Sphinx internationalization stuff? - kcrisman -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
