From mediawiki.org
Jump to navigation Jump to search
This page is a translated version of the page Help:Extension:Translate/Configuration and the translation is 96% complete.
Other languages:
Deutsch • ‎English • ‎Nederlands • ‎català • ‎dansk • ‎español • ‎français • ‎polski • ‎português • ‎português do Brasil • ‎suomi • ‎čeština • ‎русский • ‎українська • ‎العربية • ‎हिन्दी • ‎বাংলা • ‎தமிழ் • ‎中文 • ‎日本語

Das MediaWiki Language Extension Bundle bietet Dir alle Code- und Installationsschritte, die für die Konfiguration von Translate wirklich erforderlich sind. Auf dieser Seite wird detailliert beschrieben, welche Konfigurationsoptionen für den Fall verfügbar sind, falls Du noch weitere benötigst und die Installationseinführung und -anforderungen nicht geholfen haben.


Diese Konfiguration wechselt zur Datei LocalSettings.php im MediaWiki-Verzeichnis.

wfLoadExtension( 'Translate' );
$wgGroupPermissions['translator']['translate'] = true;
$wgGroupPermissions['translator']['skipcaptcha'] = true; // Bug 34182: needed with ConfirmEdit
$wgTranslateDocumentationLanguageCode = 'qqq';

# Füge dies hinzu, wenn Du den Zugriff auf die Seitenübersetzung aktivieren möchtest
$wgGroupPermissions['sysop']['pagetranslation'] = true;

# Persönliche API-Schlüssel für maschinelle Übersetzungsdienste
#$wgTranslateTranslationServices['Apertium']['key'] = '';


Übersetzungserweiterung führt neue Benutzerrechte ein:

Benutzerrecht Definition Beschreibung
translate Bearbeitungen mithilfe der Übersetzungsoberfläche tätigen Erlaube Benutzern Übersetzungen zu bearbeiten.
translate-manage Nachrichtengruppen verwalten Erlaubt Benutzern Nachrichtengruppen mit der Web-Schnittstelle zu aktualisieren und zu verwalten.
translate-import Offlineübersetzungen importieren Erlaubt es Benutzern Übersetzungsaktualisierungen aus Offline-Werkzeugen mit Hilfe der Web-Schnittstelle selbst zu importieren (noch instabil). Diese Gruppe ist optional. Sie ist nicht notwendig, solange Übersetzungen nicht aus einer externen Quelle importiert werden müssen.
pagetranslation Seitenversionen zur Übersetzung freigeben Erlaubt es Benutzern Übersetzungen der Inhaltsseiten zu verwalten.
translate-messagereview Übersetzungen überprüfen Erlaubt es Benutzern Übersetzungen als überprüft zu markieren.
translate-proofr - Diese Gruppe hat das translate-messagereview -Recht und die Berechtigung andere Benutzer zu der translate-proofr-Gruppe hinzuzufügen.
translate-groupreview Arbeitsablaufstatus von Nachrichtengruppen ändern Ermöglicht Benutzern, den Workflowstatus einer Gruppe zu ändern. Diese Gruppe ist optional und wird nicht benötigt, wenn die Variable $wgTranslateWorkflowStates standardmäßig deaktiviert ist. Wenn aktiviert, werden die Workflow-Zustände in der Variablen $wgTranslateWorkflowStates definiert.


Die folgende Dokumentation wurde zur Vereinfachung von Translate.php kopiert. Die Konfigurationsoptionen ändern sich im Laufe der Zeit. Im Zweifelsfall ist die Dokumentation in Deiner Translate.php die beste. Für die Aufzeichnung ist dies $Datum.

This section has not been updated since Translate was migrated to extension registration. Currently there is no good way to automatically generate this kind of documentation page from extension.json.

Grundlegende Einrichtung

 * Language code for message documentation. Suggested values are qqq or info.
 * If set to false (default), message documentation feature is disabled.
$wgTranslateDocumentationLanguageCode = false;

 * Name of the bot which will invalidate translations and do maintenance
 * for page translation feature. Also used for importing messages from external
 * sources.
$wgTranslateFuzzyBotName = 'FuzzyBot';

 * Add a preference "Do not send me email newsletters" in the email preferences.
$wgTranslateNewsletterPreference = false;

 * Default values for list of languages to show translators as an aid when
 * translating. Each user can override this setting in their preferences.
 * Example:
 *  $wgTranslateLanguageFallbacks['fi'] = 'sv';
 *  $wgTranslateLanguageFallbacks['sv'] = array( 'da', 'no', 'nn' );
$wgTranslateLanguageFallbacks = array();

 * Text that will be shown in translations if the translation is outdated.
 * Must be something that does not conflict with actual content.
if ( !defined( 'TRANSLATE_FUZZY' ) ) {
	define( 'TRANSLATE_FUZZY', '!!FUZZY!!' );

 * Define various web services that provide translation suggestions.
 * Translation memories are documented in our main documentation.
 * @see https://www.mediawiki.org/wiki/Help:Extension:Translate/Translation_memories
 * For Apertium, you should get an API key.
 * @see http://wiki.apertium.org/wiki/Apertium_web_service
 * Yandex translation helper also provides langlimit option to limit total
 * number of suggestions (set to 0 to get all possible translations)
 * and langorder array to sort languages. Yandex translate engine is based on
 * wordnet, generated from search index, so number of indexed websites should be
 * a good heuristic to define the default language order.
 * The machine translation services are provided with the following information:
 * - server ip address
 * - versions of MediaWiki and Translate extension
 * - clients ip address encrypted with $wgProxyKey
 * - source text to translate
 * - private API key if provided
$wgTranslateTranslationServices = array();
$wgTranslateTranslationServices['TTMServer'] = array(
	'database' => false, // Passed to wfGetDB
	'cutoff' => 0.75,
	'type' => 'ttmserver',
	'public' => false,
$wgTranslateTranslationServices['Microsoft'] = array(
	'url' => 'http://api.microsofttranslator.com/V2/Http.svc/Translate',
	'key' => null,
	'timeout' => 3,
	'type' => 'microsoft',
$wgTranslateTranslationServices['Apertium'] = array(
	'url' => 'http://api.apertium.org/json/translate',
	'pairs' => 'http://api.apertium.org/json/listPairs',
	'key' => null,
	'timeout' => 3,
	'type' => 'apertium',
$wgTranslateTranslationServices['Yandex'] = array(
	'url' => 'https://translate.yandex.net/api/v1.5/tr.json/translate',
	'key' => null,
	'pairs' => 'https://translate.yandex.net/api/v1.5/tr.json/getLangs',
	'timeout' => 3,
	'langorder' => array( 'en', 'ru', 'uk', 'de', 'fr', 'pl', 'it', 'es', 'tr' ),
	'langlimit' => 1,
	'type' => 'yandex',

 * List of tasks in Special:Translate. If you are only using page translation
 * feature, you might want to disable 'optional' task. Example:
 *  unset($wgTranslateTasks['optional']);
$wgTranslateTasks = array(
	'view' => 'ViewMessagesTask',
	'untranslated' => 'ViewUntranslatedTask',
	'optional' => 'ViewOptionalTask',
	'acceptqueue' => 'AcceptQueueMessagesTask',
	'reviewall' => 'ReviewAllMessagesTask',
	'export-as-po' => 'ExportasPoMessagesTask',
	'export-to-file' => 'ExportToFileMessagesTask',
	'custom' => 'CustomFilteredMessagesTask',

 * Experimental support for an "Ask" help button.
 * Might change into a hook later on.
 * This is an array with keys page, url and params.
 * - page is a title of a local wiki page
 * - url is an URL to use as is (e.g. an issue tracker submission form)
 *   which will override the page if set
 * - params is an array of key-value pairs of request params
 * -- each param value can contain the variable %MESSAGE%
 *    which will be replaced with the full page name.
 * @since 2011-03-11
$wgTranslateSupportUrl = false;

 * Like $wgTranslateSupportUrl, but for a specific namespace.
 * Each $wgTranslateSupportUrl-like array needs to be the value
 * assigned to the numerical ID of a namespace of the wiki.
 * @since 2015.09
$wgTranslateSupportUrlNamespace = array();

 * When unprivileged users open a translation editor, they will
 * see a message stating that a special permission is needed for translating
 * messages. If this variable is defined, there is a button which will
 * take the user to that page to ask for permission.
 * The target needs to be reiterated with the second variable to have
 * the same result with sandbox enabled where users can't enter the sandbox.
$wgTranslatePermissionUrl = 'Project:Translator';
$wgTranslateSecondaryPermissionUrl = 'Project:Translator';


 * Enable page translation feature.
 * Page translation feature allows structured translation of wiki pages
 * with simple markup and automatic tracking of changes.
 * @defgroup PageTranslation Page Translation
 * @see https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_administration
$wgEnablePageTranslation = true;

 * Number for the Translations namespace. Change this if it conflicts with
 * other namespace in your wiki.
$wgPageTranslationNamespace = 1198;

 * If set to true, when a user selects an interface language via ULS (Universal
 * Language Selector), if the current page is a translatable page or a translation
 * page then the user is also redirected to the corresponding translation page
 * in the selected language.
 * The language of the translation pages visited afterwards will still depend on the
 * links followed (it will be the interface language only if the links use the
 * Special:MyLanguage syntax).
 * @since 2013-03-10
$wgTranslatePageTranslationULS = false;

Einrichtung der Nachrichtengruppe

 * Two-dimensional array of languages that cannot be translated.
 * Input can be exact group name, first part before '-' or '*' for all.
 * Second dimension should be language code mapped to reason for disabling.
 * Reason is parsed as wikitext.
 * Example:
 * $wgTranslateBlacklist = array(
 *     '*' => array( // All groups
 *         'en' => 'English is the source language.',
 *     ),
 *     'core' => array( // Exact group
 *         'mul' => 'Not a real language.',
 *     ),
 *     'ext' => array( // Wildcard-like group
 *         'mul' => 'Not a real language',
 *     ),
 * );

$wgTranslateBlacklist = array();

 * File containing checks that are to be skipped. See
 * https://gerrit.wikimedia.org/r/gitweb?p=translatewiki.git;a=blob;f=check-blacklist.php;hb=HEAD
 * for example.
 * @since 2012-10-15
$wgTranslateCheckBlacklist = false;

 * Two-dimensional array of rules that blacklists certain authors from appearing
 * in the exports. This is useful for keeping bots and people doing maintenance
 * work in translations not to appear besides real translators everywhere.
 * Rules are arrays, where first element is type: white or black. Whitelisting
 * always overrules blacklisting. Second element should be a valid pattern that
 * can be given a preg_match(). It will be matched against string of format
 * "group-id;language;author name", without quotes.
 * As an example by default we have rule that ignores all authors whose name
 * ends in a bot for all languages and all groups.
$wgTranslateAuthorBlacklist = array();
$wgTranslateAuthorBlacklist[] = array( 'black', '/^.*;.*;.*Bot$/Ui' );

 * List of namespace that contain messages. No talk namespaces.
 * @see https://www.mediawiki.org/wiki/Help:Extension:Translate/Group_configuration
$wgTranslateMessageNamespaces = array();

 * CC = Custom classes.
 * Custom classes can register themselves here.
 * Key is always the group id, while the value is an message group object
 * or callable function.
 * @deprecated Use TranslatePostInitGroups hook instead.
$wgTranslateCC = array();

 * Location in the filesystem to which paths are relative in custom groups.
$wgTranslateGroupRoot = '/var/www/externals';

 * The newest and recommended way of adding custom groups is YAML files.
 * See examples under Translate/groups
 * Usage example:
 *  $wgTranslateGroupFiles[] = "$IP/extensions/Translate/groups/Shapado/Shapado.yml";
$wgTranslateGroupFiles = array();

 * List of possible message group review workflow states and properties
 * for each state.
 * The currently supported properties are:
 * * color: the color that is used for displaying the state in the tables.
 * * right: additional right that is needed to set the state.
 * Users who have the translate-groupreview right can set this in
 * Special:Translate.
 * The state is visible in Special:Translate, Special:MessageGroupStats and
 * Special:LanguageStats.
 * If the value is false, the workflow states feature is disabled.
 * State name can be up to 32 characters maximum.
 * Example:
 * $wgTranslateWorkflowStates = array(
 *      'new' => array( 'color' => 'FF0000' ), // red
 *      'needs_proofreading' => array( 'color' => '0000FF' ), // blue
 *      'ready' => array( 'color' => 'FFFF00' ), // yellow
 *      'published' => array(
 *          'color' => '00FF00', // green
 *          'right' => 'centralnotice-admin',
 *      ),
 * );
$wgTranslateWorkflowStates = false;

 * Map from deprecated group IDs to their current ID
 * Example value: array( 'core' => 'mediawiki-core' )
$wgTranslateGroupAliases = array();

Systemeinrichtungsbezogene Konfiguration

 * Set location of cache files. Defaults to $wgCacheDirectory.
$wgTranslateCacheDirectory = false;

 * Configures how the message index is stored.
 * The other backends need $wgCacheDirectory to be functional.
$wgTranslateMessageIndex = array( 'DatabaseMessageIndex' );
// $wgTranslateMessageIndex = array( 'SerializedMessageIndex' );
// $wgTranslateMessageIndex = array( 'CDBMessageIndex' );

 * If you have lots of message groups, especially file based ones, and the
 * message index rebuilding gets slow, set this to true to delay the rebuilding
 * via JobQueue. This only makes sense if you have configured jobs to be
 * processed outside of requests via cron or similar.
 * @since 2012-05-03
$wgTranslateDelayedMessageIndexRebuild = false;


 * For Special:TranslationStats PHPlot is needed to produce graphs.
 * Set this the location of phplot.php.
$wgTranslatePHPlot = false;

 * The default font for PHPlot for drawing text. Only used if the automatic
 * best font selection fails. The automatic best font selector uses language
 * code to call fc-match program. If you have open_basedir restriction or
 * safe-mode, using the found font is likely to fail. In this case you need
 * to change the code to use hard-coded font, or copy fonts to location PHP
 * can access them, and make sure fc-match returns only those fonts.
$wgTranslatePHPlotFont = '/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf';


 * Currently supported YAML drivers are phpyaml, spyc and syck.
 * For phpyaml see https://php.net/book.yaml
 * For syck we're shelling out to perl. So you need:
 * * At least perl 5.8 (find out what you have by running "perl -v")
 * * Install these modules from CPAN
 *   * YAML::Syck
 *   * PHP::Serialization.
 *   * File::Slurp
 * You should be able to do this with:
 *   for module in 'YAML::Syck' 'PHP::Serialization' 'File::Slurp'; do cpanp -i $module; done
 * For the shell to work, you also need an en.UTF-8 locale installed on your system.
 * add a line "en.UTF-8" to your /etc/locale.gen or uncomment an existing one and run locale-gen
 * if you do not have it already.
 * phpyaml is the fastest and based on libyaml so the output should be most
 * compatible. spyc output format is least compatible. syck is slowest but
 * almost as good as phpyaml.
$wgTranslateYamlLibrary = 'spyc';


 * Whether to allow users to sign up via a sandbox. Sandboxed users cannot do
 * much until approved and thus they can be get rid of easily.
 * @since 2013.04
$wgTranslateUseSandbox = false;

 * To which group the translators are promoted. If left at false, they will just
 * be removed from sandbox and become normal users.
 * @since 2013.04
$wgTranslateSandboxPromotedGroup = false;

 * List of page names to always suggest for sandboxed users.
 * @since 2013.10
$wgTranslateSandboxSuggestions = array();

 * Maximum number of translations a user can make in the sandbox.
 * @since 2013.10
$wgTranslateSandboxLimit = 20;


 * Pre-save transform for message pages. MediaWiki does this by default
 * (including for pages in the MediaWiki-namespace). By setting this to
 * false it allows users to put untransformed syntax such as "~~~~" into
 * a page without having them be transformed upon save.
$wgTranslateUsePreSaveTransform = false;

 * Default action for the RecentChanges filter, which makes it possible to filter
 * translations away or show them only.
 * Possible values: ('noaction', 'only', 'filter', 'site')
$wgTranslateRcFilterDefault = 'filter';

 * Set this to config like $wgTranslateTranslationServices if you want to run
 * SolrTTMServer tests.
 * @since 2013-01-04
$wgTranslateTestTTMServer = null;

 * List of user names that are allowed to alter their privileges and do other
 * things. Used for supporting integration testing.
 * @since 2013.10
$wgTranslateTestUsers = array();



Wenn beim Übersetzen übersetzbarer Seiten ein Problem mit dem NAmensraum auftritt (Symptome: Definition nicht angezeigt, Seitentitel beginnt mit Doppelpunkt), füge diese beiden zu LocalSettings.php hinzu:

$wgExtraNamespaces[$wgPageTranslationNamespace]   = 'Translations';
$wgExtraNamespaces[$wgPageTranslationNamespace+1] = 'Translations_talk';

Dieses Problem tritt auf, wenn etwas die Sprachklasse sehr früh beendet und der Namensraum zu spät hinzugefügt wird, um sie bedingt zu aktivieren.

Übersetzungsseite ist leer oder Fehler 'Unvollständiger <translate> Befehl' wird angezeigt

Sofern das schließende </translate> Tag vorhanden ist, ist die Quellseite zu groß. Dies geschieht bei einigen Übersetzungen, wenn die Quellenseitengröße in die Nähe von 50 Kilobyte rückt. Verkleinere die Seite oder erhöhe pcre.backtrack_limit durch die Einstellung von

ini_set( 'pcre.backtrack_limit', 400000 );

in der LocalSettings.php oder


in Deiner PHP-Konfiguration (php.ini).

Schriftarten mit PHPlot

Wenn Zeichen in einigen Sprachen als Kästchen angezeigt werden, überprüfe zunächst, ob Du eine geeignete Schriftart installiert hast. Wenn dies nicht hilft, aktiviere das Font-Debugging-Protokoll. Möglicherweise musst Du zuerst Deinen MediaWiki-Cache leeren. Auf einigen Systemen kann PHP nicht auf die Zeichensätze zugreifen, die der Befehl fc-list bereitstellt.

$wgDebugLogGroups['fcfont'] = '/path/to/writable/logfile';

Im TUX-Modus (der neuen Benutzerschnittstelle) werden keine Nachrichten angezeigt

Wenn Du $wgTranslateTasks überschrieben haben solltest, stelle sicher, dass die Task custom nicht davon ausgeschlossen ist.

Das Tool wird nicht in Special:Translate geladen

Wenn Du etwas wie dieses mit endlosem "Laden von Nachrichten ..." siehst, ist der ResourceLoader defekt: setze $wgResourceLoaderMaxQueryLength = 1024; oder niedriger, bis es funktioniert.

Wenn das nicht reichen sollte, hast Du dann daran gedacht,UniversalLanguageSelector zu installieren und zu aktivieren?

Das Speichern der Übersetzung schlägt mit Unknown error: "tpt-unknown-page" fehlt

Dies geschieht, wenn die Seite zur Übersetzung markiert wurde, der Hintergrundjob jedoch noch nicht verarbeitet wurde. In diesem Fall kannst Du die Jobwarteschlange manuell ausführen oder, noch besser, die fortlaufende Ausführung von Jobs wie in Manual:Job queue/de beschrieben, einrichten. Wenn das Problem dadurch nicht behoben wird, führe php extensions/Translate/scripts/createMessageIndex.php aus.