| commit | f0a678fe549fb8c3f904769532be5b491c0db9c5 | [log] [tgz] |
|---|---|---|
| author | Translation updater bot <[email protected]> | Mon Dec 04 09:05:21 2023 +0100 |
| committer | Translation updater bot <[email protected]> | Mon Dec 04 09:05:21 2023 +0100 |
| tree | 3e9e1927b3800c10b64e06e10b27886ecc3e6fb6 | |
| parent | d115a9881fe242f4a00a7b75c117bf1e1c08aa43 [diff] |
Localisation updates from https://translatewiki.net. Change-Id: Ic7abbd823d3381a5286cd84a46a9cd32d499bf22
The ParserMigration extension provides an interface for comparing article rendering with a new non-default version of the MediaWiki parser, thus serving as a parser migration tool.
It was deployed on the Wikimedia production cluster during 2018 to compare Tidy-based output with a RemexHTML-based replacement.
In 2023 it was overhauled to compare legacy parser output with Parsoid output.
Add:
wfLoadExtension( 'ParserMigration' );
to your LocalSettings.php to enable.
Running npm test and composer test will run automated code checks.
This extension adds action=parser-migration to the MediaWiki action API, which parses a page with two different parser configurations and returns one or both variants in the API response.
It also adds 'Enable parser migration tool' to the list of 'Developer tools' options at the bottom of the 'Editing' options for a user. When this is enabled, an "Edit with migration tool" link is added to the Tools menu in the sidebar for article pages. Clicking this on an article page will bring up a variant of the "preview edit" page which allows you to compare the legacy parser output against Parsoid output.