Page MenuHomePhabricator

Allow translating non-wikitext pages with configuration option
Open, MediumPublic2 Estimated Story PointsFeature


Feature summary (what you would like to be able to do and where):

I would like to be able to translate non-wikitext pages, e.g. Scribunto modules, with the Translate extension. This should probably be behind some sort of configuration.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

A non-Wikimedia wiki that I am an administrator of, the FTB Wiki, makes heavy use of translated modules (particularly with navboxes). The recent change (T163254 + makes us unable to mark new modules for translation, breaking our current setup.

Benefits (why should this be implemented?):

This empowers individual wikis to make a decision about what content types should be allowed to be marked for translation on their wikis.

Event Timeline

While there are certainly non-wikitext content models that would welcome translation (so this feature request is definitely valid), I don’t think module is one of them. Actually, there’s an ongoing project for supporting module translation better, without having to mix Lua and Translate syntax: T238417: Structured localization framework for Scribunto modules. It should already be usable, although it could be made more convenient.

As I wrote, this feature request is valid, even if not the best solution for the current problem. For example, for a content type similar to ProofreadPage’s one (which is basically a “wikitext plus”), allowing using <translate> tags would be the best fit.

Change #1014997 had a related patch set uploaded (by TK-999; author: TK-999):

[mediawiki/extensions/Translate@master] Support translating non-wikitext content models

abi_ triaged this task as Medium priority.Mar 28 2024, 8:23 AM
abi_ moved this task from Backlog to page translation on the MediaWiki-extensions-Translate board.