多语化/预备翻译
|
第一章：基础
导入文本到 wiki 中
只需简单的去做 :-) 复制要翻译的源文本到 wiki 页面。
语言框和<languages />标记
您需要启用页面顶部的语言框，这里可以链接到所有正在进行和已完成的译文。
要实现只需添加：
<languages />
或
<languages/>
反斜线之前的空格是可选的，添加或移除不会改变页面渲染的效果（不过翻译管理员可在伪编辑中利用它再次标记相同页面需要更新它在所有语言中的译文状态，当这些页面过时时）。
如果该待译页面是个模板或需要转置的页面，则该标记应放在 noinclude 段中（避免在该段末增加换行）：
<noinclude><languages /></noinclude> （模板的剩余部分请参照此处）
单元和 <translate></translate> 标记
翻译被切分成各独立单元，这些便于管理。看看下面这个文本块：
The 'Principia' deals primarily with massive bodies in motion, initially under a variety of conditions and hypothetical laws of force in both non-resisting and resisting media, thus offering criteria to decide, by observations, which laws of force are operating in phenomena that may be observed.
要成为翻译单元，只需添加 <translate> [...] </translate> 例如：
<translate>The 'Principia' deals primarily with massive bodies in motion, initially under a variety of conditions and hypothetical laws of force in both non-resisting and resisting media, thus offering criteria to decide, by observations, which laws of force are operating in phenomena that may be observed.</translate>
数字、超链接和内链
固定变量（如数字、超链接和内链）应使用“翻译变量”或 <tvar name="..."> 标记括住。
这些标记由三部分组成，由下表所示：
- 标记
- 变量名
- 变量自身
例如：
To contact us, either see our contacts page, [www.twitter.com tweet us], phone us on 555-1212 or email us at info
wikimedia.org
下面是处理这四种情况的方式：
To contact us, either see our [[<tvar name="mainpage">Main page</tvar>|contacts page]], [<tvar name="tweeturl">www.twitter.com</tvar> tweet us], phone us on <tvar name="phonenumber">555-1212</tvar> or email us at <tvar name="infoemail">info
Wikilinks and URLs are very similar in that the target page is contained within variable and will remain fixed whereas the text can be localised. The phone number and the email however are entirely static and should not be change in anyway by translators.
Caution: although most translators do this correctly, errors can be made.
标记翻译
After saving the page, you will see a link at the top of the page saying "Mark this page for translation" (or "This page contains changes which are not marked for translation." if you are not a translation administrator). Click on that link.
- Click the "Mark this page for translation" link.
You will see that your text has been split into translation units. The first unit is the title of the page, the second is the first paragraph or line, the third is the header of the second paragraph and so on. You can give names to the translation units but it is often best to simply stick to the default numbering. - Ensure that your text has been split up appropriately. That there aren't any unnecessarily long units.
- Click the "Mark this version for translation" button.
Chapter 2. What to do next – Notify your volunteers!
邀请人们进行翻译
You've set up your request and marked and ready for translation, but now we need to get people translating. :) At this point you need to move on the chapter 3 where the various forms of seeking translations are discussed in depth. :)
Appendix 1 – Complex requests
表格和图片
When dealing with images and tables, you want to handle them in a similar fashion. Tables can often contain complex markup which should at all cost be excluded from translation units. They key is to have the contents of the table as units and not the table itself.
So here is about as complicated an example as you could really expect to have to translate. I am sure it could be more complicated but the theme effectively remains the same.
{| style="border:2px solid #eeeeee; background:white; margin:auto;"
|-
| [[File:WMF Annual Report 2011–12 EN cover rgb 300ppi.png|250px|border|2011–2012 Annual Report|link=//upload.wikimedia.org/wikipedia/commons/4/48/WMF-AR_2011%E2%80%9312_EN_SHIP2_17dec12_300dpi_hi-res.pdf|center]]
| [[File:2012-13 Wikimedia Foundation Plan FINAL FOR WEBSITE.pdf|435px|link=//upload.wikimedia.org/wikipedia/foundation/4/4f/2012-13_Wikimedia_Foundation_Plan_FINAL_FOR_WEBSITE.pdf]]
|- style="vertical-align:top;"
|
Download the 2011–12 Annual Report:
* '''[[Media:WMF-AR 2011–12 EN SHIP2 17dec12 300dpi hi-res.pdf|
PDF version (3.9 MB)]]'''
||
'''<translate>Download the 2012-13 Annual Plan:</translate>'''
* '''[[Media:2012-13 Wikimedia Foundation Plan FINAL FOR WEBSITE.pdf|
PDF version (400 KB)]]'''
* '''[[2012-2013 Annual Plan Questions and Answers|
Annual Plan questions and answers]]'''
|}
We can break this down into its various components.
表格
{| style="border:2px solid #eeeeee; background:white; margin:auto;"
|-
| Some text
|}
In this instance you place the translate tags within the cell so that it appears thusly:
{| style="border:2px solid #eeeeee; background:white; margin:auto;"
|-
|'''<translate>'''Some text'''</translate>'''
|}
图片与文件
Here is some markup for a file:
[[File:2012-13 Wikimedia Foundation Plan FINAL FOR WEBSITE.pdf|435px|The Wikimedia Foundation annual plan|link=//upload.wikimedia.org/wikipedia/foundation/4/4f/2012-13_Wikimedia_Foundation_Plan_FINAL_FOR_WEBSITE.pdf]]
Unlike in a wikilink where we used a <tvar name="...">...</tvar> variable for the page, image markup is slightly more complicated. Since normally all we need to translate is the caption rather than including the entirety of the image. the translate tags should be used inside the image markup like so:
[[File:2012-13 Wikimedia Foundation Plan FINAL FOR WEBSITE.pdf|435px|<translate>The Wikimedia Foundation annual plan</translate>|link=//upload.wikimedia.org/wikipedia/foundation/4/4f/2012-13_Wikimedia_Foundation_Plan_FINAL_FOR_WEBSITE.pdf]]</nowiki>
Appendix 2 – Some cautionary words
复杂翻译
Keep translation units as simple as possible. Complexity means the increased likelihood for errors, it raises the bar to translator participation reducing the amount of complete translations you will get. It may mean that links get broken which means time and effort fixing links. Simple = efficient. :)
Long translations – Translator time
It takes time for volunteers to translate, time that could be spent taking photo's, writing articles or news stories. The longer the translation, the more effort and resources it will use up. Ask yourself, does this page need to be translated into every single language. Are there more important priorities? More of this will be touched on in the communications chapter.
Long translations – Admin time
Be aware that pages like Fundraising 2012/Translation/FAQ take a long time to set up and this particular request isn't even the best set up. Keep it as simple as you can get away with when dealing with such cases.
Appendix 3 – Making changes to a request page
Marking a new version for translation
You might find that you may need to make some changes to a translation. This may be slightly altering text or adding new swathes of paragraphs. Either way you need to know how to update your translation request. :)
It's fairly simple actually when you make a change, you will see that at the top of the page it will now say "This page has changes since it was last marked for translation.". Click on last marked for translation and simply follow the steps above for marking for translation. :)
Does your new text really need retranslating?
As will be constantly reiterated throughout, we want to keep unnecessary work down to a minimum. If the change you made is merely a stylistic one, or spelling or grammar correction its important you mark "Do not invalidate translations". If you don't it will say that the unit needs translation.
If however the changes you make are extensive and important then of course it may make sense to invalidate the old translation and request a new one.