Last modified: 2014-04-09 16:22:20 UTC
The site is currently untranslatable, as far as I know. I suspect strings are also hardcoded in the code, which is the perfect recipe to achieve messaging of extremely low quality. For MediaWiki we apply the principle that i18n after day 0 is already too late. You're quite into development by now...
I agree with the principle but I don't know how should we proceed. Can we leverage e.g. TranslateWiki.net somehow? Also, how would the access to the different languages be done? Connected to this, I'd rather handle most/all the text strings as variables somewhere, in order to avoid direct HTML editing via GitHub pull requests...
Yes, it's possible to use translatewiki.net; all translators can translate in all languages and projects there. The easiest way might be Intuition (i18n framework for labs) https://github.com/Krinkle/TsIntuition/wiki/Documentation#usage ; otherwise, JSON is one supported format (see https://translatewiki.net/wiki/Translating:New_project ).
Nemo, pretty cool. Right now we are not using any 18n/l10n framework and only EEUU/UK is supported. I am not pretty sure about the priority we are going to put for this important task in our development. In order to have more info: * Could we use TsIntuition outside Wikimedia gerrit? * Is it time to move the dashboard to Wikimedia gerrit? Is there a formal process to follow? Is it a good idea? Cheers
(In reply to comment #3) > * Could we use TsIntuition outside Wikimedia gerrit? It's only on GitHub. > * Is it time to move the dashboard to Wikimedia gerrit? Is there a formal > process to follow? Is it a good idea? No idea and it doesn't matter for this bug.
(In reply to comment #4) > (In reply to comment #3) > > * Could we use TsIntuition outside Wikimedia gerrit? > > It's only on GitHub. I was thinking in using the full translatewiki.net process, this is why I was thinking in the need to be in Wikimedia gerrit. TsIntuition seems to be design for using with PHP. Right now the dashboard is totally client side (maybe this could change in the future) so I think we need a Javascript i18n/l10n framework for managing the translated strings (i18n) and also the localization. And the tool used for translating the string, I am not sure about it. > > > * Is it time to move the dashboard to Wikimedia gerrit? Is there a formal > > process to follow? Is it a good idea? > > No idea and it doesn't matter for this bug. Right. I was thinking in reusing the full translate process in Wikimedia. This is why I was thinking in the need to upload the project to Wikimedia gerrit.
As implied above, GitHub is supported by translatewiki.net, see instructions linked from comment 2. Thanks for your interest!
For frontend i18n you can consider using jquery.i18n (can be found on github) and json file format. This is the direction MediaWiki itself is going as well, though it will use ResourceLoader for loading messages.
