Toolhub is currently envisioned as a Django application rather than a MediaWiki extension. As such it will not have direct connection to the existing on-wiki translation communities on mediawiki.org and meta. We do however want to provide multi-lingual support in the project.
We should be able to register the Django project itself at translatewiki.net and receive user interface translations from that community. The bigger area in need of exploration is what if anything we can do to provide translations of toolinfo.json content strings as well as any additional "annotations" that are added by users via the Toolhub APIs and web interface.
- Is there a way to feed selected strings from the user generated content to translatewiki.net and get translations back?
- Yes, we have identified 2 ways this might be accomplished: via a git repo of exported strings; via Action API calls to TWN. A "tech spike" is needed to provide a better idea of the feasibility of an API driven approach. We would need to make both TWN and ourselves comfortable with the latencies and load that an API based approach would place on TWN.
- Is there a robust Django translation app that can be reused to provide in-app translations? Review https://github.com/bbmokhtari/django-translations and look for other competing solutions.
- See T259838#6460927
- Can we leverage wikidata Qs and their translations as a way to localize content on the fly? This may be the nicest approach for "tag" or "category" elements in the system.