Steven, thanks for this reply. It is correct.

I'll just add this:
1. https://www.mediawiki.org/wiki/Localisation is quite developer-oriented, but should be useful to everyone.
2. Don't be afraid of committing translations early. Some software projects wait until a late stage with publishing translatable strings, but we believe that getting early feedback from translators is very useful.

If you have any more questions, we should probably do it off-list :)


--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬


2014-02-03 Steven Walling <swalling@wikimedia.org>:

On Sun, Feb 2, 2014 at 9:41 AM, Luis Villa <lvilla@wikimedia.org> wrote:

When you get around to it, please ask Language Engineering - we'd love to help making not only readable, but easier to translate as well.

I'm curious - what's the normal process for that in Foundation software? i.e., whose responsibility is it, when is the best time to start thinking about that, etc.? It is not something Legal has been involved in much in the past, so I don't know much about the process (though I've been involved with it for other open source projects for many years, so I am familiar with many of the concepts).

The related guide at https://www.mediawiki.org/wiki/Localisation is extremely comprehensive. The TL;DR: answer is it's ultimately the responsibility of the developers and product managers on a team to make sure localization is possible/easy. The Language Engineering team largely assists directly through advice and code review, not to mention maintaining/supporting translatewiki.net. 


--
Steven Walling,
Product Manager