Hi Stefan,
On Mon, Nov 28, 2011 at 5:13 AM, [email protected] <[email protected]> wrote: > Hi, > > About a day ago I've merged the bulgarian translation of the tutorial and a > number of problems showed up. I've just gone trough all the translation task > to check for the same problems. Most of them are present. So here is a > summary: Thanks a lot for your summary. We've been quite inconsistent, as it was the first time and we didn't have the infrastructure. After yesterday, I think we agreed to use gettext at least for the webpages. For the tutorials, there is a task: http://www.google-melange.com/gci/task/view/google/gci2011/7127301 http://code.google.com/p/sympy/issues/detail?id=2795 to implement gettext support in sphinx as well. I think that will be the ultimate goal, to have (just) the tutorial in gettext, so that if we change the git English version, we just (automatically) extract the translation strings, merge it with the translation and simply use some tool like "poedit" to see what new strings have to be translated and if they are not, it will simply reuse the English version for that particular string. So things will always be 100% uptodate, possibly not 100% translated (and it will be easy for translators to simply fix the few updates in the translation by sending a pull request with the new po file). So for now I suggest to get the translations in, merge it in some form at least (txt, rst) and then once we implement gettext support, we can maybe create some GCI tasks in December to convert it to it. Ondrej -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
