翻译页面
可用工具
- 翻译流程 描述了转移到新翻译系统的流程
工作流程
- 申请加入翻译组：
- 点击侧边栏的获得翻译帐号
- 点击图标
并输入用户名、要翻译的语言和是否离线工作 - 使用保存信息
- 加入翻译组后会收到通知，点击侧边栏的开始翻译
- 输入要翻译的并点击
- 点击列表中要翻译的页面
- 在翻译页面设置第一个下拉列表为
- 确认显示了正确的语言代码
- 在 部分，点击要翻译内容左边的链接
- 输入翻译 - Google 翻译的内容仅作为参考，自己的翻译才是比较通顺的。
- 点击 会打开下一条信息，而如果想停止工作，请点击。
提示和技巧
图片显示指令
典型示例为[[Image:Plasma-kickoff.jpg|right|160px]]。这是完整的显示图片指令。所有内容都不可翻译。
Category 语句
这里可以把"Category"看作是系统关键字，所以不应该翻译。例如，[[Category:Administration]] 应该翻译为[[Category:Administrasi/id]]
For consistency, UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at Translation Help Needed. Please request help if you need it.
Links to other pages on TechBase
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.
Links to external sites
These take the form [http://example.com link text]. Like the internal links, retain the actual link and translate the link text.
Links in the Sidebar
Instructions for translating those sidebar links can be found at Modifying_the_Sidebar#Translating_Sidebar_Items
Info-boxes
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.
Translated units are marked as 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, please 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.
If you use the Chromium or Chrome browser...
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.