# Post machine-translation reviewing for Simplified Chinese version of Rust survey 2023

## A. General

1. The button "Next" has been written as "继续-" in the localized survey, with an extra dash at the end. The dash should be removed.

2. Within plain text and all contents, when using Latin script within Han script contents, a whitespace should be inserted as delimiter if it's not next to punctuation (Only when the platform doesn't automatically add such space with advanced typography features)

3. Newly added: the other button written as "返回" would be better written as "后退"

## B. Front matter (page 1 in PDF)
1. "今天" in "无论您今天是否使用Rust编程语言" means literally "this day", can be changed to "现在" to better communicate the meaning.

2. "评估工作情况" corresponds to original text "how we're doing", but literally corresponds to something like "evaluate the professional performance", which might miscommunicate the reality of the Rust Project, i'd suggest change to "评价项目现状" (evaluate/rate the current status of the project)

3. "拥有发言权"(have the right to speak) sounds very bureaucratic, as if people has no right to speak at other times. I'd suggest changing to "建言献策"(offer advice and suggestions)

4. " 常见问题 " has extra spaces around the link, which is a common mistake when English->Chinese localization. Remove the extra whitespaces. "10-25" should be changed to " 10~25 ", with extra spaces around as said in `A.2`

## C. Do you use Rust? (page 2 in PDF)
1. "Rust" should be surrounded with whitespaces in the Q, and prepended with whitspaces in the As(as they are followed by punctuations. As said in `A.2`

2. "过去"(past) should be changed to "曾经"(have ever)

## D. ...why did you stop using Rust? (page 3 in PDF)
1. "既然您已经表示不再使用Rust，您为什么停止使用Rust？" didn't capture the original meaning. I'd suggest changing it to: "很遗憾听到您已不再使用 Rust，是什么原因使您停止使用它？"

2. "太难学了" sounds like a complain than a choice with the modal word, doesn't fit the survey language very well, I'd suggest changing it to "学习太难".

3. "缺乏礼貌"(lack of politeness) sounds more like "uncivilized" than the original text "rude" in Chinese culture. I'd suggest "不太礼貌"(not very polite).

## E. Why don't you use Rust? (page 4 in PDF)
1. "您为什么不用Rust？" sounds more like "why not Rust?" as an advice, changing it to "您为什么不使用 Rust？" will improve.

2. "Rust未能帮我达成目标" should be "Rust 不能帮助我达成目标"

3. "太难学或学起来会花太多时间" should be "学习太难或者会花太多时间"

4. "缺乏礼貌" be changed to "不太礼貌", same as `D.3`

## F. "On average"..."When did you learn", (page 5 in PDF)

1. "平均而言，您一般多久进行一次编码/设计工作？" seems inconsistent with the prev question repr, i'd suggest change it to "您进行编码、设计工作的平均频率是多少？"

2. "每周或几乎每周一次" be changed to "每周或几乎每周" for consistency with above question.

3. "每月或几乎如此" be changed to "每月或几乎每月" for consistency with above question.

4. Add whitspaces before and after word "Rust" as said in `A.2`

5. Somehow there's a few raw`<span>` and `</span>`s in the displayed text. Not that familiar with SH, but fix it somehow.

6. "仍然在" was italic in the English version, make it italic too.

## G. "Which operating systems"..."Which operating systems", (page 6 in PDF)

1. "这是关于您用于开发的系统，而不是您的所有目标系统。" is not smooth sentence. Change it to "这是在问您个人用于进行开发的系统，而不是您的那些目标系统。".

2. "适用于Linux的Windows子系统" add spaces, changing to "适用于 Linux 的 Windows 子系统"

3. "Mac OS" should be "macOS", the English version is correct.

4. "您经常使用哪些操作系统进行Rust开发?" is plain wrong. Should be "您经常以哪些操作系统为目标系统进行Rust开发？"

5. "这特别是关于您的目标操作系统或运行时，而不是您用于开发的系统，也不是特定的目标构（例如x86与ARM）。" should be "这是在问您的目标操作系统或运行时环境，既不是您用于开发的系统，也不是你的目标架构（如x86 或 ARM）。"

6. "裸金属" should be "裸机"

## H. "Which version(s) of Rust"..., (page 7 in PDF)

1. better add spaces before "Rust", before and after "1.67"(twice), before "Nightly"(twice), before "fork"

## I. "If you use nightly, why?"..."Which editor or IDE setup", (page 8 in PDF)

1. "对于我需要的特定语言特性" should be "为了我需要的特定语言特性"

2. "有关夜间功能" => "有关 Nightly 功能"

3. "为在CI中测试" => "用于在 CI 中测试"

4. "一个crate依赖需要它" => "依赖 crate 需要"

5. "我用的一个工具要求它" => "我使用的工具需要"

6. "您在任何开发任务中使用的Rust的最旧版本是什么？" => "您在开发任务中使用的最旧版本的 Rust 是什么？"

7. "每晚" => "Nightly" (twice)

8. "IntelliJ/CLion/其他 JetBrains IDE + Rust 插件" => "IntelliJ、CLion、其他 JetBrains IDE + Rust 插件"

## J. (continuation from last page) (page 9 in PDF)

nothing

## K. "In your opinion, how..." (page 10 in PDF)

1. "您认为，Rust 的以下几个方面的工作应该如何优先考虑？" => "您认为，Rust 的以下若干个方面的工作哪些应该优先进行？"

2. "请仅选择您有意见的方面" => "请仅对您持有观点的那些方面进行选择"

3. "不应该被优先考虑" => "不应优先进行"

4. "即编译时rustc使用了多少RAM" => "即编译时rustc对RAM的使用量"

5. "编译器中的错误（即 ICE，又名内部编译器错误、错误编译等）" => "编译器中的问题（即 ICE（又名内部编译器错误）、误编译等）"

6. "编译器错误消息" => "编译器报错信息"

7. "IDE体验" => "IDE 体验"

8. "调试经验" => "调试体验"

9. "货物" => "Cargo"

10. "Rust 语言和标准库文档" => "Rust 语言文档与标准库文档"

11. "您认为未实现的（或仅夜间）功能应该在 Rust 中稳定吗？" => "您认为 Rust 中目前处于未实现状态（或仅Nightly可用）的功能应该稳定化吗？"

12. "我认为未实现的功能应该稳定下来" => "我认为处于未实现状态的功能应该稳定化"

13. "我希望 Rust 项目不要添加重大新功能（或者放慢开发速度）" => "我希望 Rust 项目不再添加重大新功能（或者放慢扩充速度）"

## L. "Which unimplemented or ..." (page 11 in PDF)

1. "您希望哪些未实现的或（仅限夜间）功能保持稳定？" => "您希望哪些目前处于未实现状态（或仅Nightly可用）的功能进行稳定化？"

2. "请在此处提及 \*Rust 编译器\* 的功能，这些功能目前位于功能门后面（仅可使用 Rust 编译器的不稳定/每夜版本），或者缺少但您认为对 Rust 生态系统有益或有益的功能。你的工作。此列表不包括编译器周围的其他工具，例如 Cargo、rustup、rustfmt 等。" => "请在此处提名 *Rust 编译器*的功能开关(feature gate)未启用的(仅在 Rust 编译器的非稳定/Nightly版本中提供的)功能，以及目前不存在但您认为对 Rust 生态或您的工作有益的功能。此处不需要列举编译器周边其他工具的功能，例如 cargo、rustup、rustfmt 等。"

3. "请仅选择您有意见的方面" => "请仅对您持有观点的那些方面进行选择"

4. "不应该被优先考虑" => "不应优先进行"

5. "专业化" => "特化"

6. "If/while let 链" => "if/while let 连接(chain)"

7. "尝试块" => "try 表达式块"

8. "从不打字" => "永无(never)类型"

9. "改进的特征（特征别名、隐含边界、关联类型默认值）" => "对特质(trait)的改进（特质别名、隐式约束、默认关联类型）"

10. "改进的 const（通用 const 表达式、自定义类型的 const expr、const 特征方法）" => "对常数化(const)的改进（泛型常数表达式、非内置类型的常数表达式、常数化特质方法）"

11. "可变泛型 => 变长泛型"

12. "分配器特性，更好的 OOM 处理" => "分配器(allocator)特质、更优的 OOM 处理"

13. "稳定的ABI" => "稳定化的 ABI"

14. "您是否希望优先考虑上面未提及的任何功能？" => "有没有什么未在上面提及的功能是您希望优先进行相关工作的？"

## M. "Which of these problems ..." (page 12 in PDF)

1. "您记得去年遇到过以下哪些问题？" => "您在过去的一年里在以下的哪些方面遇到过问题？"

2. "在元组上实现事物" => "对元组类型增加实现时"

3. "将东西分装在板条箱中" => "将代码拆分为多个crate时"

4. "必须手动执行迭代器实现" => "必须手工实现迭代器"

5. "在 const fn 中做得不够" => "在 const fn 中能做的事情不够多"

6. "Rust 插件需要下降到 C ABI" => "Rust 插件需要下沉使用 C ABI"

7. "特征和泛型" => "特质与泛型"

8. "借阅检查器" => "借取检查器"

9. "如何构建 Rust 项目" => "您如何构建您的 Rust 项目"

10. "我使用货运" => "我使用 Cargo"

11. "我将 Cargo 和另一个构建系统结合起来" => "我将 Cargo 与其他构建系统结合使用"

12. "如果您将 Cargo 与（或仅使用）其他构建系统一起使用，您会使用哪些？" => "若您将 Cargo 与其他构建系统结合使用（或仅使用其他构建系统），您使用的是哪些？"

13. "如何下载 crate 来构建 Rust 项目？" => "您构建 Rust 项目时如何下载 crate？"

14. "我使用自定义/本地/公司注册表" => "我使用自定义/本地/公司注册库(registry)"

## N. "Do you agree...", (page 13 in PDF)

1. A few italics didn't pass through to Chinese text because they're escaped by accident
2. "*稳定*" => " *stable* " (twice)
3. "*每晚*" => " *nightly* "
4. "，或者对我的代码" => "，或只需对我的代码"
5. "或对我的代码" => "，或只需对我的代码"

## O. "Roughly how often...", (page 14 in PDF)

1. "您参与Rust社区的频率大致是多少" => "您大致以什么频次参与 Rust 社区活动？"
2. "消费有关Rust的信息内容" => "接收有关 Rust 的信息内容"
3. add delimiting spaces between Han script and Latin words, around "rust-lang", "Github", "YouTube", "Rust Twitter", "Zulip", "Discord", like `A.2` said.
4. "您在Rust社区的感觉如何？" => "您在下列 Rust 社区空间的体验如何？"
5. "官方Rust社区论坛或聊天室（users.rust-lang.org、internals.rust- lang.org、官方Rust Discord或Rust Zulip）" => "Rust *官方*社区论坛或聊天室（users.rust-lang.org、internals.rust-lang.org、官方 Rust Discord 或 Rust Zulip）"
6. "非官方的Rust社区论坛或聊天室（如reddit.com/r/rust、Hacker News，Rust Community Discord，等等）" => "Rust *非官方*社区论坛或聊天室（如reddit.com/r/rust、Hacker News 或 Rust Community Discord 等等）"
7. "社区专注于 Rust 软件开发的特定领域（例如游戏开发、音频等）" => "专注于 Rust 软件开发特定领域（例如游戏开发、音频等）的社区"
8. "参加Rust会议" => "Rust 会议"
9. "在rust-lang GitHub组织的仓库中进行讨论（问题、PR等）" => "在 rust-lang GitHub组织*之内*的仓库中进行讨论（问题、PR等）"
10. "在GitHub的rust-lang组织之*外*的仓库中的讨论（issue、pull request等）" => "在GitHub的rust-lang组织*之外*的仓库中的讨论（问题、PR等）"

## P. "If you indicated that ...", (page 15 in PDF)

no changes

## Q. "Are you currently taking a course ...", (page 16 in PDF)

1. "您目前或去年是否参加过使用或教授Rust的课程或培训？" => "您是否现在正在参加或过去的一年参加过使用或教授 Rust 的课程或培训？"

## R. "Are you employed...", (page 17 in PDF)

1. "个人贡献者（即非经理）" => "贡献者人员（而不是作为经理）"

## S. "Are you personally...", (page 18 in PDF)

1. Inserted whitespaces between Latin and Han, for the words "Rust", as `A.2` said.

2. "对于我的大多数代码" => "我大部分的编码工作都在用"

3. "以下哪一项陈述适用于" => "以下哪些陈述适用于"

4. "我们很可能在未来再次使用Rust" => "我们在未来很可能会继续使用Rust"

5. SUSPICIOUS: It seems the translation text doesn't match the PDF here in the last options of "Which of the following statements are reasons why you use Rust at work?" Cannot access the original text and localized form.
I've attached the correct translations here, please check.

"We find it easy to prototype with": "我们认为用它进行原型实现很方便"

"We must interact with existing Rust code": "我们必须与现有的 Rust 代码进行交互" (i've added spaces)

"We find it easy to use": "我们发现它易于使用" (doesn't have this in the original text, only in the localized text)

## T. "What about your usage of Rust..." (page 19 in PDF)

## U. "In what technology domain..." (page 20 in PDF)

1. Inserted whitespaces between Latin and Han, for the words "Rust", as `A.2` said.

2. "裸金属" => "裸机"

3. "数据库实施" => "数据库实现"

4. "不要担心这里的精确性！跟随你的直觉。" => "不用特别在意这里的数字准确程度！请按照直觉判断回答。"

## V. "Is your organisation planning on..." (page 21 in PDF)

1. "计划聘请其他开发商" => "打算招聘其他的开发者"

2. "不打算雇用任何开发人员" => "不打算招聘任何开发者"

## W. "Which of the following statements about Rust..." (page 22 in PDF)

1. Inserted whitespaces between Latin and Han, for the words "Rust", as `A.2` said.

2. "您对Rust有以下哪些看法？" => "您觉得以下对Rust 的陈述哪些是符合实际情况的？"

## X. "Please share your assessment of..." (page 23 in PDF)

nothing to change.

## Y. "Your responses to the following questions..." (page 24 in PDF)

1. "审稿人进行队列分析" => "复审人员进行群组分析"

2. "请根据您的舒适度回答" => "请对您愿意回答的问题作答"

3. "神经发散" => "大脑功能异常"

## Z. "Are you..." (page 25 in PDF)

1. "您是否是一名全日制或兼职的学生？" => "您是全日制学生或者非全日制学生吗？"

2. "在硕士课程中" => "目前是硕士生"

3. "在博士项目中" => "目前是博士生"

4. "在职业培训中" => "目前是职业培训生"

## AA. "Where do you live?" (page 26 in PDF)

nothing to change

## AB. "In what ways are you comfortable" (page 27 in PDF)

1. SUSPICIOUS: seems some mistake occurred with a question: "我能自如地阅读英语的书面技术教育资料（如技术书籍、博客文章等）" (second occurrence, as question) => "您在技术交流时倾向于使用的语言有哪些？"

## AC. "Is there anything..." (page 28 in PDF)

nothing to change

Note: `A.3` was added at a later stage.