Programming with Scratch (Linux Journal)

Posted Jun 30, 2010 7:25 UTC (Wed) by Im26 (subscriber, #48749)
In reply to: Programming with Scratch (Linux Journal) by sasha
Parent article: Programming with Scratch (Linux Journal)

The software I write doesn't have translations. I have neither the need nor the desire to do this.

I don't think that makes my work any less valuable. It just not one of my goals.

If I perceived that there is market for making it accessible to different languages then I'd put some effort in. If someone else wanted to do the translations then that would be fantastic.

Programming with Scratch (Linux Journal)

Posted Jun 30, 2010 7:40 UTC (Wed) by sasha (guest, #16070) [Link] (1 responses)

You do not need to make translation yourself. But the infrastructure for translations of the particular software is not the task of translator.

> If someone else wanted to do the translations then that would be fantastic.
Someone else can't do anything as long as your software does not provide an easy way to incorporate the translation. As far as I see, as soon as software provides an easy way to translate it, there are a lot of translators for many different language happily contributing to it. When there are no generic translation support, it looks too hard to ask the developers to do something with a translation for any given language.

Programming with Scratch (Linux Journal)

Posted Jun 30, 2010 9:05 UTC (Wed) by mpr22 (subscriber, #60784) [Link]

I agree. I will in passing note that supporting generic translation well (gettext() only supports translation "well" for static text and simple computer-ese messages like "%s: file not found") is surprisingly effortful.