维基媒体:翻译管理员/准备翻译页面
Appearance
下面是指导您如何创建可译页面的基本步骤,这样的页面能利用翻译扩展的功能。
阅读手册。
评估页面是否适合翻译及需要翻译。
- 本地计划可能无需翻译。
- 某些页面可能包含不适合翻译的结构。
- 如果需要帮助,请在这里询问一位活跃的翻译管理员
评估您是否有能力“迁移已有译文”到新系统。 It may be a lot of work to copy the old translation into the new one. If you aren't able to spend a lot of time or you are unable find the proposed translation units in the new system, ask for help. Do not proceed until you are sure that you and the people who promised to help are able to migrate everything within a few days, if it is a policy, even within a few hours. Whether you have the capabilities to migrate to the new system usually depends on
- The volume of existing translations.
- The status of the existing translations (outdated, current)
- The page length and structure
- Beispiel → Example/de
- Exemple - Example/fr
- Ekzemplo → Example/eo
- Eksempel → Example/da
- …
- Local name → English name/语言代码
Example
which is located at Exemple
, you have to move it to Example/fr
to ensure the page history, which also servers for the attribution requirement of the Creative Commons License, all texts at Commons are licensed under, is merged. If you do not move it, the subpages created by the Extension (as soon as a translation to one language was started) must be deleted and the page where the translation was copied from must be moved there (both moving to and deleting a subpage require temporary unmarking a page from translation). After moving, the deleted revisions can be restored (History merge)Prepare the page for translation. Some templates were designed to help keeping it easy for the translators. Further help is available in the manual.
Mark the page for translation (you must be translationadmin for doing so). FuzzyBot will now overwrite all existing translations with the source version (English). So hurry to complete the next step.