Hi,
Several Wikidata-related extensions are not translatable on translatewiki.net.
The ones I could find are: * Wikibase DataModel * Wikibase DataModel JavaScript * Wikidata build * WikimediaBadges * The various DataValues extensions
All extensions need at least a translatable description for Special:Version, and some of the above have actual messages to translate.
If I understand correctly, the reasons for this is that it's more comfortable for their developers to have the code review in GitHub, and translatewiki's MediaWiki extensions L10n export scripts work only with Gerrit. The question is, is it feasible to sync GitHub and Gerrit, so that these extensions would be easily translatable?
If I understand correctly, something like this is already done for some MediaWiki extensions, among the SemanticResultFormats and Maps.
Thanks for any assistance.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Hey,
For PHP libraries such DataModel, all the overhead of the translation setup is not worthwhile just to have the thing on Special:Version be translated. Indeed, a good portion of these libraries don't even add anything to Special:Version to begin with.
Components with messages should of course have translatewiki support. As you mention, this can be done by syncing the GitHub repo with the WMF one, as done with for instance Maps. I suggest filing issues for those where this is not done yet. Of course if we want to avoid new repos being created and them not being set up in this way because it's such a hassle, then the obvious thing to do is to make translatewiki not bound to the WMF git repos.
Cheers
-- Jeroen De Dauw - http://www.bn2vs.com Software craftsmanship advocate Evil software architect at Wikimedia Germany ~=[,,_,,]:3
On Sat, Sep 27, 2014 at 10:51 AM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
Hi,
Several Wikidata-related extensions are not translatable on translatewiki.net.
The ones I could find are:
- Wikibase DataModel
- Wikibase DataModel JavaScript
- Wikidata build
As far as I am concerned and if no one objects, I would be okay with moving the Wikidata build (resources) component to gerrit, if that helps with translations.
https://github.com/wmde/WikidataBuildResources
For other things like data model and data values, the preference is for github and I defer to Jeroen, Lydia, etc.
Cheers, Katie
* WikimediaBadges
- The various DataValues extensions
All extensions need at least a translatable description for Special:Version, and some of the above have actual messages to translate.
If I understand correctly, the reasons for this is that it's more comfortable for their developers to have the code review in GitHub, and translatewiki's MediaWiki extensions L10n export scripts work only with Gerrit. The question is, is it feasible to sync GitHub and Gerrit, so that these extensions would be easily translatable?
If I understand correctly, something like this is already done for some MediaWiki extensions, among the SemanticResultFormats and Maps.
Thanks for any assistance.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Hi Amir,
tere must be working exort scripts to github, since we translate e.g. etherpad lite, which is maintained on github, and there are commits from translatewiki.net, see: https://github.com/ether/etherpad-lite/tree/develop/src/locales
Purodha
"Amir E. Aharoni" amir.aharoni@mail.huji.ac.il wrote
Hi, Several Wikidata-related extensions are not translatable on translatewiki.net[http://translatewiki.net]. The ones I could find are: * Wikibase DataModel * Wikibase DataModel JavaScript * Wikidata build * WikimediaBadges * The various DataValues extensions All extensions need at least a translatable description for Special:Version, and some of the above have actual messages to translate. If I understand correctly, the reasons for this is that it's more comfortable for their developers to have the code review in GitHub, and translatewiki's MediaWiki extensions L10n export scripts work only with Gerrit. The question is, is it feasible to sync GitHub and Gerrit, so that these extensions would be easily translatable? If I understand correctly, something like this is already done for some MediaWiki extensions, among the SemanticResultFormats and Maps.
Thanks for any assistance.
P. Blissenbach, 27/09/2014 19:46:
tere must be working exort scripts to github, since we translate e.g. etherpad lite, which is maintained on github, and there are commits from translatewiki.net, see: https://github.com/ether/etherpad-lite/tree/develop/src/locales
That's not the l10n-bot operated by Raimond. Let's not forget that l10n updates rely on his daily work, which we should strive not to complicate further.
Nemo