翻译页面
可用工具
- Translation Workflow describes the workflow to migrate to the new translation system
流程
- 申请加入译者用户组：
- 单击侧栏的获取翻译权限
- 单击图标，然后输入您的用户名和语言，以及是否想线下翻译的信息
- 单击保存
- 加入译者用户组后（您应该会收到电邮通知），单击侧栏的开始翻译
Note
- 单击您想翻译的页面
- In the Translate page set in the first drop-down list
- Check that the correct language code is showing
- In the section, click on the link to the left of the message you want to translate
- Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.
- Click on to continue with the next message or to save the translation if you wish to stop working.
Warning
提示和技巧
Image display instructions
A typical example is [[Image:Plasma-kickoff.jpg|right|160px]]. The whole of this is a system instruction on how to display the image. None of it is translated.
分类
把 "Category" 这个英语单词想成一个系统保留词，别翻译他。比如，[[Category:Administration]]应译为[[Category:管理//zh-cn]]
为保持一致，我们都有个Category Translation 简体中文 to 正體中文表来供您——也希望您——翻译时比照。
链接到其他 UserBase 页面
These take the form [[Special:myLanguage/Other page|link text]] The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.
Note: "myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.
站外链接
These take the form [http://example.com link text] Like the internal links, retain the actual link and translate the link text.
信息框
These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.
某段译文标为 fuzzy
Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.
The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this
<!--}}-->{{Info|1=Beginning of long info box...
and in a later unit
...end of long info box}}<!--{{-->
If the offending bracket is part of a smiley, you can replace it with an emoticon icon. For the standard smiley, :-), you can use the template {{Smiley}}
Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.
Language Statistics discrepancies
You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.
如果您用谷歌浏览器……
Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.