You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once the multilingual setup described in #46 is in place, it could be nicer to set up the translation on TranslateWiki.net, which would reuse an existing platform that's well integrated with Wikimedia projects, and provide us with more visibility among the community of translators (meaning, hopefully, more available languages for end users).
At that point, the i18n work done on our custom system, assuming it is a simple one, should be primarily in the translation side, so it would be reusable in the most part, by importing the existing translations into TWN.
The text was updated successfully, but these errors were encountered:
Krinkle's Intuition tool will probably be easier than integrating directly with Translatewiki. Here's some documentation, and this section in particular should be helpful for the initial setup.
Alternatively, he suggested to take a look at jQuery.i18n, which is fully client-side but still supports features like PLURAL, GENDER, etc.
Once the multilingual setup described in #46 is in place, it could be nicer to set up the translation on TranslateWiki.net, which would reuse an existing platform that's well integrated with Wikimedia projects, and provide us with more visibility among the community of translators (meaning, hopefully, more available languages for end users).
At that point, the i18n work done on our custom system, assuming it is a simple one, should be primarily in the translation side, so it would be reusable in the most part, by importing the existing translations into TWN.
The text was updated successfully, but these errors were encountered: