Community Wishlist Survey 2021/Translation/Easy and effective way to translate gadgets and userscripts

Random proposal ►◄ Translation The survey has concluded. Here are the results!

Easy and effective way to translate gadgets and userscripts

Problem: Gadgets and Userscripts are an important part of the Wikiverse. There are numerous such scripts that are used by a large number of users. Currently, those scripts are often copy-pasted from one wiki to another, to allow to translate them into the local language of the wikis. By that process lots of duplicates emerge that need to be maintained and improved independently. Further often several different scripts exist for one problem, because the script was not known outside the origin wiki, often again due to the language barrier (as well as the issue of missing findability of scripts – but this problem is currently tackled by a different WMF project).

Some scripts have translations into multiple languages integrated (mostly on Commons/Wikidata), there are issues with that. See below.

Who would benefit: All editors and some readers
Proposed solution: There should be one simple way to make the user interfaces of an userscript/gadget translatable (known as i18n). The mechanism has to full fill the following requirements:
1. Easy to use for tool developers. Something like mw.translate("English text") should be enough.
2. The translations should be saved separated to the script. Probably as a page with content model JSON.
3. All regular editors should have the rights to translate scripts. Which user group ("autoconfirmed", "editor", …) will be needed is up to debate but the current situation where only the script author and sysops can translate the script must be avoided.
4. Translating should not require technical know-how. An easy-to-use user interface is required.
More comments:
Phabricator tickets:
Proposer: MichaelSchoenitzer (talk) 16:52, 21 November 2020 (UTC)[reply]

point 1 is technically already possible. mw.msg() translates a message-key into a translated string (just like used in core). Gadget authors can add their own keys and translations by making a json table and importing each key with mw.messages.set(). It just lacks in terms of conventions for gadget authors on how to store the translations and to a large degree also people simply putting in the effort to consistently add internatinalization as well as a way in which more users can contributed with the translation process. —TheDJ (talk • contribs) 19:20, 21 November 2020 (UTC)[reply]
Are you thinking of something like a Wikimedia Weblate instance, MichaelSchoenitzer? HLHJ (talk) 01:10, 24 November 2020 (UTC)[reply]
This will possibly be addressed by the mw:Translatable modules project. Its initial scope is for Scribunto modules, but it may be extended also to gadgets. --Amir E. Aharoni (talk) 08:47, 27 November 2020 (UTC)[reply]

Support MarioSuperstar77 (talk) 21:18, 8 December 2020 (UTC)[reply]
Support Iniquity (talk) 23:50, 8 December 2020 (UTC)[reply]
Support as someone from a primary language who'd benefit greatly from such an innovation, I support Leftowiki (talk) 00:41, 9 December 2020 (UTC)[reply]
Support PianistHere (talk) 01:54, 9 December 2020 (UTC)[reply]
Support Kambai Akau (talk) 02:52, 9 December 2020 (UTC)[reply]
Support --Ciao • Bestoernesto • ✉ 03:12, 9 December 2020 (UTC)[reply]
Support Yeah, a translation interface sounds like a great idea. Opalzukor (talk) 08:05, 9 December 2020 (UTC)[reply]
Support — putnik 19:22, 9 December 2020 (UTC)[reply]
Support Nehaoua (talk) 22:11, 9 December 2020 (UTC)[reply]
Support Libcub (talk) 20:35, 10 December 2020 (UTC)[reply]
Support Evad37 (talk) 03:22, 11 December 2020 (UTC)[reply]
Support --Alaa :)..! 01:24, 12 December 2020 (UTC)[reply]
Support Michel Bakni (talk) 14:01, 14 December 2020 (UTC)[reply]
Support Baum64 (talk) 12:06, 15 December 2020 (UTC)[reply]
Support Kpjas (talk) 13:07, 15 December 2020 (UTC)[reply]
Support Genius idea. Joalbertine (talk) 20:45, 19 December 2020 (UTC)[reply]