View source for Help:Extension:Translate/Configuration/zh

<languages />
{{Extension-Translate}}
[[Special:MyLanguage/MediaWiki Language Extension Bundle|MediaWiki语言扩展包]]提供了配置翻译扩展所需的全部代码和安装步骤；本页会详细讲解可用的配置选项，以防[[Special:MyLanguage/Help:Extension:Translate/Installation|安装介绍和要求]]没有帮到你。

<span id="Sample_configuration"></span>
== 示例配置 ==

前往MediaWiki目录的<code>LocalSettings.php</code>进行配置。

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

# 如果你要开启页面翻译，加上这一行
$wgGroupPermissions['sysop']['pagetranslation'] = true;

# 用于机器翻译服务的私有API键
#$wgTranslateTranslationServices['Apertium']['key'] = '';
</syntaxhighlight>

<span id="User_rights"></span>
== 用户权限 ==

翻译扩展会引入以下用户权限：

{| class="wikitable"
|-
! 用户权限
! 定义
! 说明
|-
| <code>translate</code>
| {{int|right-translate}}
| 允许用户编辑译文。
|-
| <code>translate-manage</code>
| {{int|right-translate-manage}}
| 允许用户通过网络界面更新和管理信息组。
|-
| <code>translate-import</code>
| {{int|right-translate-import}}
| 允许用户用web界面从离线工具本身导入翻译更新（仍不稳定）。这个组是可选的。除非有翻译需要从外部来源导入，否则这个组就是不需要的。
|-
| <code>pagetranslation</code>
| {{int|right-pagetranslation}}
| 允许用户管理内容页面的译文。
|-
| <code>translate-messagereview</code>
| {{int|right-translate-messagereview}}
| 允许用户标记翻译为已审核。
|-
| <code>translate-proofr</code>
| -
| 这个组拥有<code>translate-messagereview</code>权限以及将其他用户加进<code>translate-proofr</code>组的权限。
|-
| <code>translate-groupreview</code>
| {{int|right-translate-groupreview}}
| 允许用户更改一个组的工作流状态。这个组是可选的，并且在$wgTranslateWorkflowStates变量默认被禁用时没有必要。如果启用，工作流状态就会定义在$wgTranslateWorkflowStates变量中。
|}

<span id="Configuration_variables"></span>
== {{LC zh|C|zh-hans=配置变量|zh-hant=組態變數}} ==

为方便于你，下面文档拷贝自<code>Translate.php</code>。配置选项会随着时间而改变，所以如果有疑问，您Translate.php的中的是最好的记录之一。此份拷贝记录于2016-04-21。

{{note|1=<span lang="en" dir="ltr" class="mw-content-ltr">This section has not been updated since Translate was migrated to extension registration.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Currently there is no good way to automatically generate this kind of documentation page from extension.json.</span>}}

<span id="Basic_configuration"></span>
== 基本配置 ==
<syntaxhighlight lang=php>
/**
 * 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 (assistant languages).
 * Each user can override this setting in their preferences.
 * If MediaWiki core has a fallback for this language in Messages*.php, then
 * that fallback language is used, so use this variable only if you want to add more
 * languages to that fallback.
 * This feature works only if the value of the assistant languages
 * preference ('translate-editlangs') is the string 'default'.
 * Example:
 *  $wgTranslateLanguageFallbacks['fi'] = 'sv';
 *  $wgTranslateLanguageFallbacks['sv'] = [ '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
 *
 * For Microsoft Azure AI Translator, you will need to setup your instance
 * in the "global" region or it will not work.
 * 
 * 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' => 'https://api.cognitive.microsofttranslator.com/',
	'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';

/**
 * If set, displays a warning and does not allow user to move
 * translatable pages having more subpages than this value
 */
$wgTranslatePageMoveLimit = 500;
</syntaxhighlight>


<div lang="en" dir="ltr" class="mw-content-ltr">
=== Page translation feature ===
</div>
<syntaxhighlight lang=php>
/**
 * 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;
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Message group configuration ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Following configuration variable names have been renamed:
</div>

* <code>TranslateBlacklist</code> --> <code>TranslateDisabledTargetLanguages</code>
* <code>TranslateAuthorBlacklist</code> --> <code>TranslateAuthorExclusionList</code>
* <code>TranslateCheckBlacklist</code> --> <code>TranslateValidationExclusionFile</code>

<div lang="en" dir="ltr" class="mw-content-ltr">
The old variables will be supported for MLEB 2021.07 release but removed in the MLEB 2021.10 release.
</div>

<syntaxhighlight lang=php>
/**
 * 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:
 * $wgTranslateDisabledTargetLanguages = 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',
 *     ),
 * );
 */

$wgTranslateDisabledTargetLanguages = array();

/**
 * File containing checks that are to be skipped. See
 * https://gerrit.wikimedia.org/r/plugins/gitiles/translatewiki/+/refs/heads/master/groups/validation-exclusion-list.php
 * for example.
 */
$wgTranslateValidationExclusionFile = false;

/**
 * Two-dimensional array of rules that exclude 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. Inclusion
 * always overrules exclusion. 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.
 */
$wgTranslateAuthorExclusionList = array();
$wgTranslateAuthorExclusionList[] = 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();
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== System setup related configuration ===
</div>
<syntaxhighlight lang=php>
/**
 * 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
 * @deprecated Since MLEB 2021.10. Always inserted into the JobQueue
 */
$wgTranslateDelayedMessageIndexRebuild = false;
</syntaxhighlight>

==== PHPlot ====
{{info|1=<span lang="en" dir="ltr" class="mw-content-ltr">PHPlot is no longer necessary since MLEB 2020.10.</span> <span lang="en" dir="ltr" class="mw-content-ltr">It has been replaced with [[Phab:T134634|a JavaScript based solution]]:</span> Chart.js}}
<syntaxhighlight lang=php>
/**
 * 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';
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== YAML driver ====
</div>
<syntaxhighlight lang=php>
/**
 * 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';
</syntaxhighlight>

<span id="Sandbox"></span>
====沙盒====
<syntaxhighlight lang=php>
/**
 * 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;
</syntaxhighlight>

<span id="Unsorted"></span>
=== 未分类 ===
<syntaxhighlight lang=php>
/**
 * 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();
</syntaxhighlight>

<span id="Troubleshooting"></span>
== 故障排除 ==

{{anchor|Page translation: translated version of page is empty}}
<span id="Translation_page_is_empty_or_error_&#039;Unbalanced_{{tag|translate|open}}_tag&#039;_shown"></span>
=== 翻譯頁是空白的或出現在錯誤'未平衡的{{tag|translate|open}} 標籤'===

<div lang="en" dir="ltr" class="mw-content-ltr">
Provided that the closing {{tag|translate|close}} tag exists, the source page is too big. This starts happening with some translations if the source page size is near 50 kilobytes. Make the page shorter or increase <code>pcre.backtrack_limit</code> by setting
 ini_set( 'pcre.backtrack_limit', 400000 );
in LocalSettings.php or
 pcre.backtrack_limit=400000 
in your PHP configuration (php.ini).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== In TUX mode (the new UI) no messages are shown ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have overridden <code>$wgTranslateTasks</code>, make sure task <code>custom</code> is not excluded from it.
</div>

<span id="The_tool_doesn&#039;t_load_in_Special:Translate"></span>
=== 工具未在Special:Translate中载入 ===

<div lang="en" dir="ltr" class="mw-content-ltr">
If you see something [[:File:Extension Translate interface not loading.png|like this]] with endless "Loading messages...", the {{ll|ResourceLoader}} is broken: set <syntaxhighlight lang=php inline>$wgResourceLoaderMaxQueryLength = 1024;</syntaxhighlight> or lower until it works.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If that's not enough, have you remembered to install and enable {{ll|Extension:UniversalLanguageSelector|UniversalLanguageSelector}}?
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Saving translation fails with Unknown error: "tpt-unknown-page" ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">This happens when page has been marked for translation, but the background job has not yet been processed.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In this case you can run job queue manually, or even better, setup continuous job running as described in {{ll|Manual:Job queue}}. If that doesn't solve the issue, try running php extensions/Translate/scripts/createMessageIndex.php.</span>

[[Category:Extension:Translate{{#translation:}}|Configuration]]