We had translated some configuration options into Japanese until https://www.mediawiki.org/w/index.php?title=Extension:MobileFrontend/ja&oldid=2180852, but they were lost along with the migration to GitHub. Where should we post translations now?
Topic on Extension talk:MobileFrontend
Hi @Ochaochaocha3 that's a good question. I wasn't aware of translations existing so thank you for bringing these to my attention!
@Nikerabbit is there any similar patterns for translating README's?
@JHernandez (WMF) we could automatically deploy the README to a wiki page (we'd have to convert from Markdown to MediaWiki however)
@Ochaochaocha3 The migration was from the wiki page to the code repository (active one is in gerrit https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/MobileFrontend, github is a mirror of that one).
The reason is that configuration is very dependent on the version of the code, so by being tied to the code it is versioned with it. So if you need to check the configuration variables for a release/version of MobileFrontend, with checking the README of the code you'll have up to date documentation. In the wiki it was hard to check docs for older versions of MobileFrontend and relate the documentation with the code.
The problem as mentioned is having multilanguage docs for the config. I think there are two possible solutions:
- Have translations of README.md (something like README.ja.md)
- Translators need to be comfortable with git/gerrit (higher barrier to entry)
- Maybe hard to keep translations up to date with code?
- Have subpages of Extension:MobileFrontend on mediawiki.org with translations of the latest configuration
- Similar workflow as before
- Markdown to wikitext conversion needed (either manually or automatically)
- Doable with something like pandoc or parsoid (markdown to html and html to wiki via parsoid)
What do you feel more comfortable with? I lean towards having Extension:MobileFrontend/Configuration listing subpages and explaining that this is the latest config from the repository and it's translations, and then having language specific translations at Extension:MobileFrontend/Configuration/ja for example.
Thoughts?
@JHernandez (WMF) Thank you for giving me the details! I think the latter is preferable, because the Translate extension is widely used for translating MediaWiki-related documents and it makes it easier to update translations.
Ok, I've created a phab ticket T143308 to chat about this and added you, to talk with other devs about it and figure out a good way forward. I've summarized what's up and options, please chime in and let's keep the discussion there. Once we come up with the approach we'll work on it!
Sorry for the inconveniences @Ochaochaocha3