[sugar] Non English fallbacks for translations

[Mikus Grinbergs]

> ... This breaks existing i18n code. This means, activities which call
> "from gettext import gettext as _" will not be able to use translations.
> Removing that import line would work fine though. Is that OK ?

When you talk about translating "from gettext import gettext as _", 
(a statement in a python module) you are opening a can of worms.

It has been my experience that, for software that a product 
executes, there should be only a single "master" copy (e.g., the 
English text of that python module).  If there exist "derivative" 
copies (e.g., that same python module translated into another 
language), whoever inserts the "derivative" (so that the derivative 
gets executed instead of the "master") takes on the burden of 
debugging that substituted software, and keeping it up-to-date. 
[Note: translating "constants" should not introduce misbehavior.]

I do not intend to doubt the learning gotten by pupils in writing 
their own software (using a language familiar to them).  But if 
Sugar subsequently changes (say, from Fedora-9 to Fedora-10), will 
the author of a "derivative" module still be around to apply any 
function-call changes necessitated by future Sugar-core changes ?

mikus