Hmm I'm unsure if there's a bugzilla keyword or something for "intentional regressions", so to say. :)

(In reply to comment #1)

Hmm I'm unsure if there's a bugzilla keyword or something for "intentional
regressions", so to say. :)

It was a time available vs effort needed decision made by the product owners for the 2014 scholarship cycle. Their rationale was that the 2014 Wikimania will be primarily conducted in English and that it would be reasonable that scholarship applicants have enough mastery of the language to read and understand the application form.

I'd like to see someone add good support for i18n/l10n to the project in the future including integration with translatewiki.net, but that's not going to get done in time for this application cycle.

(In reply to comment #2)

(In reply to comment #1)

Hmm I'm unsure if there's a bugzilla keyword or something for "intentional
regressions", so to say. :)

It was a time available vs effort needed decision made by the product owners
for the 2014 scholarship cycle. Their rationale was that the 2014 Wikimania
will be primarily conducted in English and that it would be reasonable that
scholarship applicants have enough mastery of the language to read and
understand the application form.

It's a mistake. As long as we support i18n now then what's the effort for us? We just have to provide the final english text and the translators will do their jobs. And if we don't have complete translations on day 1 for launch? We'll update a week later when we do :)

I'd like to see someone add good support for i18n/l10n to the project in the
future including integration with translatewiki.net, but that's not going to
get done in time for this application cycle.

We support i18n now. There's /no/ point in intentionally regressing it.

Actually I'm taking over this bug and totally repurposing it. We localize everything, and we've already got a localization system in place.

It just needs some TLC. I'm going to do it today.

Here's my plan of action:

1. Finish moving untranslated portions of the UI into the i18n file
2. Make sure all i18n strings are in supported language files
3. Blank all translations, as they refer to old software and are mostly wrong now

Once we get the final english text, we'll put it in and then the translators can get to work as if it's a fresh application (which it is).

For now, I'm only planning on supporting the existing supported languages (de, en, fr, ja, pl, zh), as the list is hardcoded and fixing that is outside the scope of this (we should open a second lower priority bug for that bit).

I think the only task left for this is to get the project setup with translatewiki.