I am not sure if this works with the current system.

We use {{en|1=text}} {{he|1=text}} etc. to translate stuff.

What makes more sense is to have some kind of a system for translating file descriptions on Commons.

ContentTranslation doesn't seem like the right system for this.

It would make more sense to do it with the Translate extension, or maybe Wikidata, or maybe something else entirely. It's more of a Multimedia bug, but with strong relationship to I18n.

Wow, I could've sworn that Commons had a gadget for this. Is there really nothing?

I had thought of a mwparserfromhell/Parsoid-based translation assistant, but ditched it in the hope that 'structured data' weren't that far.

Can't just a script getting text from these {{en|1=}} and of the kind templates as well as adding new ones be created? Like all these other scripts adding some problem templates and whatever. If it does not exist that is. (This thought occurred in my head before but I never really searched). I don't think it should be kept simple for the start. When there will be a working solution something more sophisticated like an Extension could be created. Though it might happen so that the script will work that fine that priority of such a development will fall down considerably.

In T114980#1719887, @Base wrote:

Can't just a script getting text from these {{en|1=}} and of the kind templates as well as adding new ones be created?

Not only wikitext is hard to parse, but there are also countless templates for file information (e.g. Artwork) and multilingual descriptions (e.g. Mld).

Well that is a problem that must be dealt with in any case. It doesn't matter whether it is for an extension to do the parsing or a script. But scripts usually are more flexible

User:MarkTraceur/editDescriptions.js pretty much already does this, at least for normal {{Information}} templates. You can test it by adding

importScript( 'User:MarkTraceur/editDescriptions.js' );

to your common.js. Pinging @MarkTraceur

@El_Grafo, @MarkTraceur: Is there any reason that shouldn't be made into a Gadget on Commons?

In T114980#1739136, @kaldari wrote:

@El_Grafo, @MarkTraceur: Is there any reason that shouldn't be made into a Gadget on Commons?

If it is stable and i18n suppot (from translatewiki?) we can make it a into a Gadget! :-)

I think it would be useful to have some equivalent to http://recommend.wmflabs.org/ a kind of ranking system for translations for each subject based on things like most used content, quality image etc.

The scope of this report is very unclear.

Please reopen if there's something specific left to do.