Revision as of 08:22, 14 November 2011 by Fengchao (Talk | contribs) (Created page with "在下一个单元中")

Jump to: navigation, search
Other languages:
čeština • ‎Ελληνικά • ‎English • ‎español • ‎suomi • ‎italiano • ‎मराठी • ‎Nederlands • ‎português do Brasil • ‎русский • ‎slovenčina • ‎українська • ‎中文(中国大陆)‎



  • 申请加入翻译组:
    • 点击侧边栏的获得翻译帐号
    • 点击编辑图标Userbase-edit.png 并输入用户名、要翻译的语言和是否离线工作
    • 使用保存页面保存信息
  • 加入翻译组后会收到通知,点击侧边栏的开始翻译
  • 输入要翻译的语言代码并点击开始
输入 en (English) 作为语言码不会显示任何未翻译信息,因为所有原始内容都是英语写成
  • 点击列表中要翻译的页面
  • 翻译页面设置第一个下拉列表为查看全部未翻译信息
  • 确认显示了正确的语言代码
  • 导航 部分,点击要翻译内容左边的链接
  • 输入翻译 - Google 翻译的内容仅作为参考,自己的翻译才是比较通顺的。
  • 点击保持并打开下一条 会打开下一条信息,而如果想停止工作,请点击保存本页




Category 语句

这里可以把"Category"看作是系统关键字,所以不应该翻译。例如,[[Category:Administration]] 应该翻译为[[Category:Administrasi/id]]

为了保持一致,用户基地维护了一个统一的类别翻译。翻译组可以采用类似的列表,参见需要翻译帮助。 需要时可以请求帮助。


采用[[Special:myLanguage/Other page|链接文字]]这样的形式。不应该翻译链接,而链接的文本应该翻译。如果没有链接文本,请自行添加翻译后的文本。

注意: "myLanguage" 将会先尝试用用户设置中选定的语言载入页面,如果没有找到,再载入对于的英文原始页面,所以在所有内部链接中都能使用。


使用如下形式:[http://example.com 链接文本]。和内部链接一样,保留原始链接并翻译链接文本。




这些信息框包含一个头部"Information" 和可编辑的信息内容。要翻译"Information"字段,需要建立一个本地化的模板。如有需要,可以申请帮助。



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



 ...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.

Also See

Content is available under Creative Commons License SA 4.0 unless otherwise noted.