Update zh-CN translations #807
Conversation
|
cc @laurence6 and @3442853561, mind taking a look? |
zh-CN/contribute-bugs.md
Outdated
| you'll need elevated GitHub permissions to apply labels, but this is | ||
| easy to obtain for somebody with a bit of experience in the | ||
| project. Ask a [team member][team]. | ||
| Rust 始终需要人们来[分流]问题：重现 bug， |
There was a problem hiding this comment.
The link to "triage" seems missing.
|
|
||
| * The [Library Team][library_team] is responsible for the Rust standard | ||
| library, rust-lang crates, and conventions. | ||
| * [库团队][library_team]负责 Rust 标准库、rust-lang 包装箱，及公约。 |
There was a problem hiding this comment.
"rust-lang 包装箱" seems a little weird? Is "rust-lang 包" or "rust-lang crates" probably better?
There was a problem hiding this comment.
@laurence6 Google the "rust 包装箱", it has some use. I did not find a wide translation. "包" like the "Package", no traits. Keep it is shy away but not solve it.
Since we don't have an authoritative translation for the "crates", I want to push this process. If anyone is dissatisfied with the current translation, it can make a change and discuss rather than keep it.
zh-CN/contribute-libs.md
Outdated
| then libraries are where it's at: since Rust is a young language, | ||
| there are many types of libraries that either do not exist yet | ||
| or are incomplete and in need of improvement or competition. | ||
| 如果你想通过编写 Rust 代码来为 Rust 处理， |
|
我不确定应该把“crates”翻译成“包装箱” |
|
@alexcrichton I think this translation is generally good, except for individual sentences. I think it can be merged. @laurence6 may have other suggestions |
zh-CN/faq.md
Outdated
|
|
||
| <h3><a href="#why-has-rust-changed-so-much" name="why-has-rust-changed-so-much"> | ||
| 为什么 Rust 随时间推移在大幅变化？ | ||
| </a></h3> | ||
|
|
||
| Rust started with a goal of creating a safe but usable systems programming language. In pursuit of this goal it explored a lot of ideas, some of which it kept (lifetimes, traits) while others were discarded (the typestate system, green threading). Also, in the run up to 1.0 a lot of the standard library was rewritten as early designs were updated to best use Rust's features and provide quality, consistent cross-platform APIs. Now that Rust has reached 1.0, the language is guaranteed to be "stable"; and while it may continue to evolve, code which works on current Rust should continue to work on future releases. | ||
| Rust 起步的目标是创建一个安全且合用的系统编程语言。为了追求这个目标，它探索了很多想法，其中一些（生命周期、traits）被保留，而其他则被丢弃（类型体系系统、绿色线程）。 Also, in the run up to 1.0 a lot of the standard library was rewritten as early designs were updated to best use Rust's features and provide quality, consistent cross-platform APIs. 现在的 Rust 已达到了 1.0，语言保证为“稳定”（stable）；虽然它可能继续演变，但对于目前的 Rust 来说，代码在未来的发行版本上能继续工作。 |
There was a problem hiding this comment.
Also, in the run up to 1.0 a lot of the standard library was rewritten as early designs were updated to best use Rust's features and provide quality, consistent cross-platform APIs.
并且，为了最大程度地利用 Rust 的特性并提供高质量的、一致的跨平台 API，在 1.0 版本的之前许多标准库代码被重写了。
|
It looks good. : ) |
|
Thanks! |
|
|
|
Also, the "Fork 在 GitHub 上的代码" looks was cut off, there was not enough space. |
|
@yfdyh000 正是因为 Fork 在 GitHub 上的代码 过长的缘故，才采用意译的方式的。另外我认为friends最好不要翻译 |
|
@3442853561 But I think the past "从GitHub上拷贝源码" is not appropriate for the original meaning, it is "Copy Source from GitHub". I hope the friends.html be translated, it is a good page for localized readers and SEO. |
This is a large changes, but the not 100% complete of the translation and carefully review. I don't know whether this needs to be comments and corrects, or direct release and meet for next pull request.