add Chinese translation document

[imsingo]

The pull request contains the Chinese translation for "Guide and Overviews (Core)" part.

The translation covers the doc in http://docs.scala-lang.org/overviews/ , except Reflection & Macros

We used transifex as our working platform, the address is https://www.transifex.com/projects/p/12345-1/

The translated doc list:

• The Scala Actors Migration Guide
• Value Classes and Universal Traits
• String Interpolation
• Implicit Classes
• Futures and Promises
• Scala’s Parallel Collections Library
• The Architecture of Scala Collections
• The Scala Actors API
• Scala’s Collections Library

[heathermiller]

Hi all, first off, wonderful job (as far as I can tell!) What a tremendous amount of work! I'd like to pull this in right away, but I can't get it to build. I'm getting (amongst others) the following ruby exception that fails generation:

 ___________________________________________________________________________
| Maruku tells you:
+---------------------------------------------------------------------------
| Could not find ref_id = "t" for md_link(["T"],"t")
| Available refs are []
+---------------------------------------------------------------------------
!/Library/Ruby/Gems/1.8/gems/maruku-0.6.1/lib/maruku/errors_management.rb:49:in `maruku_error'
!/Library/Ruby/Gems/1.8/gems/maruku-0.6.1/lib/maruku/output/to_html.rb:716:in `to_html_link'
!/Library/Ruby/Gems/1.8/gems/maruku-0.6.1/lib/maruku/output/to_html.rb:970:in `send'
!/Library/Ruby/Gems/1.8/gems/maruku-0.6.1/lib/maruku/output/to_html.rb:970:in `array_to_html'
!/Library/Ruby/Gems/1.8/gems/maruku-0.6.1/lib/maruku/output/to_html.rb:961:in `each'
\___________________________________________________________________________
Not creating a link for ref_id = "t".  Liquid Exception: wrong argument type Array (expected Regexp) in overview-large.html
error: wrong argument type Array (expected Regexp). Use --trace to view backtrace

How have you been building the site? Have you changed anything in _config.yml?

[SethTisue]

@imsingo are you still interested in pursuing this?

[SethTisue]

@heathermiller @dickwall do we know of anyone who could review this?

[heathermiller]

Actually, no, I don't. For some reason I don't know any enthusiastic Chinese Scala programmers :(

[dickwall]

Sorry - me either. We could put a call out in the next scalawags maybe?

[SethTisue]

call for help put out on Twitter: https://twitter.com/scala_lang/status/635597445511184385

[eed3si9n]

When I need help reviewing Mandarin document for sbt I ping @pengisgood, @XuefengWu , @fsi206914, and @jasonqu and one of them magically show up. 先谢了!

[kunkun-tang]

I'd like to help out. and how to make a review?

[eed3si9n]

@fsi206914 Add comments on the commit if you find mistakes.
Also "更要特别感谢的是在此次翻译工作中付出辛勤劳动的、广大的翻译志愿者朋友们，他们是：
（以下按姓氏拼音排序）" in the Thanks.md page seem to indicate that this work was an effort of 21 volunteers. Google translates says

Special thanks also to the hard work is paying in the translation work, the majority of the volunteer interpreters friends, they are:
(Hereinafter sorted by last name spelling)"

Is that correct? If so we could considered it more or less vetted.

[SethTisue]

when I try to build this branch locally, I get the same wrong argument type Array (expected Regexp) error that Heather saw in 2014. so at minimum, someone will need to make a new PR (since @imsingo has apparently disappeared) including the same commits plus a fix for that

[kunkun-tang]

@eed3si9n The google translation is correct.

[eed3si9n]

when I try to build this branch locally, I get the same wrong argument type Array (expected Regexp) error that Heather saw in 2014.

I don't think these guys actually ran Jekyll. The wrong argument type Array likely is coming from the incorrect language/languages YAML head matter (which I don't think is documented). I was able to fix that: eed3si9n/docs.scala-lang@ad733b8

There are few more wiring up that are needed, but once they are done I can send a new PR.

[SethTisue]

closing since #450 was merged. if anyone's coming to this PR from Twitter, welcome, and see #450 for further to-dos