Release status: stable
|Implementation||User interface, Page action|
|Description||Tool that allows editors to translate an article from one language to another with the help of machine translation and other translation aids.|
|Latest version||1.0.0 (Continuous updates)|
|Compatibility policy||release branches|
|License||GNU General Public License 2.0 or later|
|Translate the ContentTranslation extension if it is available at translatewiki.net|
|Check usage and version matrix.|
|Issues||Open tasks · Report a bug|
The ContentTranslation extension is a tool that allows editors to translate an article from one language to another with the help of machine translation and other translation aids. See Content translation for background and additional information. The extension is being developed by the Wikimedia Language Engineering team.
The extension can be retrieved directly from Git [?]:
- Browse code
- Some extensions have tags for stable releases.
- Browse tags
- Select the tag
- Click "snapshot"
- Each branch is associated with a past MediaWiki release. There is also a "master" branch containing the latest alpha version (might require an alpha version of MediaWiki).
- Browse branches
- Select a branch name
- Click "Continue"
Extract the snapshot and place it in the extensions/ContentTranslation/ directory of your MediaWiki installation.
If you are familiar with git and have shell access to your server, you can also obtain the extension as follows:
cd extensions/ git clone
- If using Vagrant, install with
vagrant roles enable contenttranslation --provision
- Manual installation
- Download and place the file(s) in a directory called
- Add the following code at the bottom of your LocalSettings.php:
wfLoadExtension( 'ContentTranslation' );
- Run the update script which will automatically create the necessary database tables that this extension needs.
- Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
The extension needs the Content Translation server (a.k.a. cxserver) up and running.
See Content translation/cxserver/Setup for setting up the Content Translation server.
When running Content Translation locally, following can be added to
LocalSettings.php to use production cxserver:
$wgContentTranslationSiteTemplates['cx'] = 'https://cxserver.wikimedia.org/v1';
This extension has an optional dashboard feature, which allows translators to see all the translations across all languages.
In a multilingual installation of this extension, for example in Wikimedia wikis, a central database is required to serve the dashboard feature.
Table definitions for that database are in
sql directory in the extension source code; Content translation/Product Definition/Database has more details.
Once database is created, set the
$wgContentTranslationDatabase global configuration variable as the name of database:
$wgContentTranslationDatabase = 'db_name';
ContentTranslation depends on the following extensions:
|VisualEditor||required||Required for editor component.|
|GuidedTour||optional||If installed, it will be used to show an explanation about moving a page out of user space.|
|Echo||optional||If installed, it will be used for showing "congratulations" notifications after completing translation milestones.|
|Wikibase||optional||If installed and configured similarly to Wikipedia, it will be used for automatic addition of interlanguage links (as sitelinks).|
|EventLogging||optional||If installed, can be used to log publishing, errors, and other events.|
|BetaFeatures||optional||If installed, ContentTranslation will appear as a beta feature in the preferences.|
|Cite||optional||Required if you want to support references while translating.|
|This section is currently a draft.|
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
For the full list and defaults, see extension.json in the source repository.
- Used to map between non-standard language codes and actual domains. The default is the same as in Wikipedia codes and domains.
- Configuration of RESTBase URL and connection parameters. The defaults are for Wikipedia.
- The name of the database in which the common tables for managing translations across wikis are stored. The default is null, which means that the default database is used.
- In a Wikipedia-like database configuration, the name of the cluster on which the database is hosted. The default is null, which means that the default cluster is used.
- Whether EventLogging is enabled. The default is false.
- A category to which pages that have a high level of machine translation are added upon publishing. The default is null.
- Templates for essential URLs. The defaults assume Wikipedia, so this variable must be configured differently for other sites. Where relevant, $1 is replaced by the language code, and $2 is replaced by the page title.
- Whether to open Special:ContentTranslation in the target wiki when clicking the button in the entry point. The domain will be based on $wgContentTranslationSiteTemplates. The default is to open Special:ContentTranslation on the same wiki. (For Wikipedia this is set to true.)
- Whether ContentTranslation is a beta feature.
- The default target namespace for published articles. The default is Main.
- Campaigns that are available in the URL as valid values for the campaign parameter in the URL. This allows automatic enabling of the beta feature and event logging.
- CXServer connection configuration.
- Whether to use the suggestions tab and automatic suggestions. This needs the GapFinder API. This is false by default, but true in Wikipedia.
- The URL for the GapFinder API, needed if ContentTranslationEnableSuggestions is true.
|This extension is being used on one or more Wikimedia projects. This probably means that the extension is stable and works well enough to be used by such high-traffic websites. Look for this extension's name in Wikimedia's CommonSettings.php and InitialiseSettings.php configuration files to see where it's installed. A full list of the extensions installed on a particular wiki can be seen on the wiki's Special:Version page.|