Am 27.11.2011 22:10, schrieb Vladimir Perić:
Yeah. I always thought .po files would be the way to go,
Me too. I do not think anything better is even possible; not if the goal
is "the minimum amount of maintenance burden that allows us to have a
reasonable solution".
There are powerful translation workbenches, but my understanding is that
they are built for teams of full-time translators, which we are not.
(Among the things such a workbench typically requires is that you build
an as complete as possible domain-specific terminology, then it will
automatically do 80% of the translation work for you - but setting up
that terminology is so much work that we'd end up doing more work, and
you'd need to be specifically trained to even work on the terminology.)
guess any problems will get noticed sooner rather than later. We
should probably do the same for the tutorial (in the long run, I
wouldn't mess around with it for GCI),
I agree with that.
We can put the translations into the gettext infrastructure after the fact.
> if we do agree that we want to
keep translating documentation (though, again, I don't really see the
value in that).
It depends on the target audience.
Math&physics researchers should know English already, it's their lingua
franca anyway.
Highschool students can have a better grasp of mathematics than English;
if we wish to serve these, translations would help.
Engineers... it depends. Some countries expect their engineers to learn
English as a matter of course, others don't. E.g. I would expect French
universities to discourage people to doing too much in English.
Regards,
Jo
--
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.
