Update translation: zh-CN (Simplified Chinese)

[op200]

Update Simple Chinese (zh-CN) translation

msgmerge pot(this branch)->po from branch feature (arch1t3cht), manual confirmation is correct

The translations of all functional options have been tested by me to ensure accuracy

• Complete the translation
  (The newly added part or untranslated part)

  e.g.
  Open Recent -> 最近打开
Visual Typesetting Tools Alpha -> 可视化绘图工具透明度
Skip over whitespace -> 跳过空行

• Revise a small amount of translations to use more contemporary language
  Standardize inconsistent translations throughout
  Uniform punctuation usage

  e.g.
  热键 -> 快捷键
偏好 -> 首选项
： -> :

[oborozuk1]

It looks like you added some personal annotations rather than strictly following the original text. Anyway, before discussing the content, I have a couple of questions:

• Why did you use the translation from version 3.2 as the base instead of 3.4?
• What is the purpose of using half-width punctuation instead of full-width in Chinese?
• Is it necessary to include the branch-related content (though it’s commented out)?

---

你的英语水平过关吗

[EL-File4138]

I will provide some review suggestions later, for now, I'm seeing:

• “时间轴” is roughly simplified to “时轴” (from a self-explanatory term to a dictionary entries style term);
• “计时” becomes “时轴” (covering "timing" with a more general "timestamp", which loses semantics precision);
• “特效标签” becomes "tag" (regression);
• Inconsistent "cursor": “文本光标”, “文本编辑光标”, “游标”
• Mixed zh-Hant term: framerate - “影格率”
• Commenting term from source language: “粗体版本(bold variant)”
• Incoherent proofreading: “在文本光标处分割 行” (one excessive space)

some from your example:

• "Skip over whitespace": only “空行”(empty line), or what the code intends to do, “空白” (which includes inline whitespace character sector)?

… also, as long as you're still using “喔唷，Aegisub娘崩溃啦！”, I feel it's still not very proper to remove the contribution remark from Vmoe Fansub.

Overall still a solid job, but it could use some more polish. Would be grateful if you could later respond to review comments.

[op200]

It looks like you added some personal annotations rather than strictly following the original text. Anyway, before discussing the content, I have a couple of questions:

* Why did you use the translation from version 3.2 as the base instead of 3.4?

* What is the purpose of using half-width punctuation instead of full-width in Chinese?

* Is it necessary to include the branch-related content (though it’s commented out)?

你的英语水平过关吗

1. branch master 提交比 branch 3.4 提前，为啥你说 master 是 3.2 ？package 里的版本号都是 3.4，我也是根据 master 生成的 pot
   我不清楚 Aegisub 的项目结构
2. 只有个别标点统一为了半角，有利于对齐
3. 子集 po 通过超集 po + 对应分支的 pot 生成，根本不需要关心注释

---

我的英语水平一坨，可喜可贺的是英语水平一坨翻译的句子能让新手一眼看懂，而不是原来某些

动名词都分不清的翻译

　

和

一句话用两句都表意不清的废话文学

　

并且我能找到的、且需要翻译的功能，我都使用了一遍，原文本身就含有大量的表意不清，须按照实际含义翻译，否则新手根本看不懂

[oborozuk1]

branch master 提交比 branch 3.4 提前，为啥你说 master 是 3.2 ？

我是说你的翻译用的是旧的（3.2 版本），而不是 3.4 修订过的

我最后那句话没有任何批评的意思，只是说你的 PR 我差点没看懂

[op200]

I will provide some review suggestions later, for now, I'm seeing:

* “时间轴” is roughly simplified to “时轴” (from a self-explanatory term to a dictionary entries style term);

* “计时” becomes “时轴” (covering "timing" with a more general "timestamp", which loses semantics precision);

* “特效标签” becomes "tag" (regression);

* Inconsistent "cursor": “文本光标”, “文本编辑光标”, “游标”

* Mixed zh-Hant term: framerate - “影格率”

* Commenting term from source language: “粗体版本(bold variant)”

* Incoherent proofreading: “在文本光标处分割 行” (one excessive space)

some from your example:

* "Skip over whitespace": only “空行”(empty line), or what the code intends to do, “空白” (which includes inline whitespace character sector)?

… also, as long as you're still using “喔唷，Aegisub娘崩溃啦！”, I feel it's still not very proper to remove the contribution remark from Vmoe Fansub.

Overall still a solid job, but it could use some more polish. Would be grateful if you could later respond to review comments.

I did not delete any info about Vmoe, I even kept the header info intact in the comments for possible future restoration

About original text, I think there are many unreasonable aspects: whitespace appeared in the 翻译助手, it will enter the next line when submitting

If you open the option Skip over whitespace, it will skip empty line

The original text have a large number of similar thing (bugs), so that's why feature based translation is needed instead of original text based translation

[op200]

branch master 提交比 branch 3.4 提前，为啥你说 master 是 3.2 ？

我是说你的翻译用的是旧的（3.2 版本），而不是 3.4 修订过的

我最后那句话没有任何批评的意思，只是说你的 PR 我差点没看懂

几乎无法直接合并，用 pot 重新生成 po 后，文本对比功能也废了，所以我手动跟 3.4 的 po 对比了一个多小时……

例如 karaoke timing 我原本的 po 就是 3.2 版本的 xxx 计时，我看到 3.4 的修改后，才修改的，我选择直接删除了这句翻译

关于 计时 时轴 时间 之类的翻译，原文是 time timing timer，非常混乱，例如我会把 timer （原译 计时器）翻译成 时轴，这是因为这个字符串出现的位置是顶部工具栏，这里的 时轴 泛指整个 时间轴处理 相关概念（功能），且整个工具栏除了 自动化 都是两个字，看起来也舒服

而 timing 就难以分清具体指代了，甚至连词性都无法从原文看出来，karaoke timing 我根本找不到在哪出现，也看不懂源码，所以为了防止错译就暂时删除了（未翻译的行直接能搜出来，错译的就麻烦了）

[EL-File4138]

whitespace appeared in the 翻译助手, it will enter the next line when submitting

So your understanding of what the toggle is doing is a bit off.
Skipping empty line is what the toggle additionally do, as the toggle is exactly made for "white space".

Please try:

• Enclose 2 part of text on one line with ass tag;
• Leave some space (character) between the groups;
• Try to translate using the tool; Switch the toggle on and off, see whether the whitespace part got picked up.

(I'll supplement a video later)

Please do not assume the source language is "faulty" before you can confidently support your acclaim with proper understanding of the functionality.

[oborozuk1]

几乎无法直接合并，用 pot 重新生成 po 后，文本对比功能也废了，所以我手动跟 3.4 的 po 对比了一个多小时……

或许你可以参考 git 的提交。

但 3.4 版本大部分新翻译都被改回去了，这部分还是有不少改进的，请见 #210。

karaoke timing 我根本找不到在哪出现

在 编辑 > 撤销，还有一处 combining 也是在这，原本翻译是错的。

[oborozuk1]

Translating "recombine" as "合并" may cause confusion with "join," as their behaviors are different.

[op200]

whitespace appeared in the 翻译助手, it will enter the next line when submitting

So your understanding of what the toggle is doing is a bit off. Skipping empty line is what the toggle additionally do, as the toggle is exactly made for "white space".

Please try:

* Enclose 2 part of text on one line with ass tag;

* Leave some space (character) between the groups;

* Try to translate using the tool; Switch the toggle on and off, see whether the whitespace part got picked up.

(I'll supplement a video later)

Please do not assume the source language is "faulty" before you can confidently support your acclaim with proper understanding of the functionality.

text	close	open
{some tags}	skip	skip
	not	skip
text	not	not

Now I understand your means, thank you for your reminder

Firstly, I had never noticed before that it treats tags as empty

Secondly, I know before that its function is to skip whitespace, 空行 != empty string. There was indeed an issue with my response above, it was my mistake

A few months ago, I translated it as 跳过空行 that has no problem, I don't know why I gave this translation as an e.g. in PR
Maybe my brain went down after not sleeping all night

[op200]

几乎无法直接合并，用 pot 重新生成 po 后，文本对比功能也废了，所以我手动跟 3.4 的 po 对比了一个多小时……

或许你可以参考 git 的提交。

但 3.4 版本大部分新翻译都被改回去了，这部分还是有不少改进的，请见 #210。

karaoke timing 我根本找不到在哪出现

在 编辑 > 撤销，还有一处 combining 也是在这，原本翻译是错的。

等我睡一觉后再核对一遍😭

已经感觉快4了

[op200]

Translating "recombine" as "合并" may cause confusion with "join," as their behaviors are different.

我想起来了，我可以先把 3.4 的 po 生成新 po，然后再做文本比较

唉woc😭白白浪费一两个小时

[op200]

Already fully cmp the 3.4 po

I thought that could finish soon, but it still took over an hour😭

Fortunately, made many necessary modifications to the translation

zh_CN.zip

org po + pot -> new 3.4 po
used for cmp

[oborozuk1]

Is that so? I still see some differences—were they intentional?

• 强制以 X 的比例显示视频画面 → 强制视频为X宽高比
• 退格：解除最后的连结 → 空格: 解除最后的连结 (This is incorrect. And you changed the translation of "link" from "连结" to "配对", but these instructions were left unchanged.)
• 字体没有正确的unicode映射时有用 → 字体没有合适的unicode映射时有用

[op200]

Is that so? I still see some differences—were they intentional?

* `强制以 X 的比例显示视频画面` → `强制视频为X宽高比`

* `退格：解除最后的连结` → `空格: 解除最后的连结` (This is incorrect. And you changed the translation of "link" from "连结" to "配对", but these instructions were left unchanged.)

* `字体没有正确的unicode映射时有用` → `字体没有合适的unicode映射时有用`

第一个 ratio 作为比值（系数）翻译，所以不写 :1，和后面的 msgid "Force video to a custom aspect ratio" msgstr "强制视频为自定义宽高比" 对应

第二个那一大段我没注意到……改了，连结 也都统一成 3.4 中使用的 配对 了（我说怎么按空格没反应捏）

第三个改成 "文字编码，仅当使用unicode时，字体没有正确的unicode映射时生效" 了

[oborozuk1]

Alright, now we've finally reached the first step, which is reviewing the translation. I agree with @EL-File4138's opinion. I'll go through your translation later again.

[oborozuk1]

I've reviewed these for now. I think we should discuss whether some annotations are really necessary or if we should follow the original text instead.

[EL-File4138]

Review of Change (1/3)

This review covers the first 2000 lines of only the changing part. The inherited part will be done separately.

[arch1t3cht]

I'm slowly getting back to Aegisub development after being busy with personal projects for a few months. What's the status of this language PR? I see some unresolved review comments, does everyone here agree this is ready to merge, or are there still disagreements?

[EL-File4138]

I would suggest putting it on hold if there isn't a recent plan to release a new version. I'm still consulting with a variety of zh-CN communities for feedback.

[op200]

I will resolve it when free
within 3 months at the latest

[0tkl]

好久没留意这个 PR 了。由于最近快发新版了，主开发者比较愿意合 PR，不知您是否有空继续推进。我看到大半年之前您提到「不知道出现在哪里的 timing」

Aegisub/po/zh_CN.po

Lines 153 to 160 in 1fd46d9

	#: ../src/audio_timing_dialogue.cpp:514 ../src/audio_timing_dialogue.cpp:520
	#: ../src/command/time.cpp:176
	msgid "timing"
	msgstr "时间轴"
	#: ../src/audio_timing_karaoke.cpp:240
	msgid "karaoke timing"
	msgstr "卡拉OK时间轴"

根据文件里提供的文件名与行数，找到相应位置：

Aegisub/src/audio_timing_dialogue.cpp

Lines 512 to 521 in 1fd46d9

	if (user_triggered)
	{
	context->ass->Commit(_("timing"), AssFile::COMMIT_DIAG_TIME);
	commit_id = -1; // never coalesce with a manually triggered commit
	}
	else
	{
	AssDialogue *amend = modified_lines.size() == 1 ? (*modified_lines.begin())->GetLine() : nullptr;
	commit_id = context->ass->Commit(_("timing"), AssFile::COMMIT_DIAG_TIME, commit_id, amend);
	}

Aegisub/src/audio_timing_karaoke.cpp

Lines 237 to 243 in 1fd46d9

	void AudioTimingControllerKaraoke::DoCommit() {
	active_line->Text = kara->GetText();
	file_changed_slot.Block();
	commit_id = c->ass->Commit(_("karaoke timing"), AssFile::COMMIT_DIAG_TEXT, commit_id, active_line);
	file_changed_slot.Unblock();
	pending_changes = false;
	}

Aegisub/src/command/time.cpp

Lines 162 to 177 in 1fd46d9

	static void snap_subs_video(agi::Context *c, bool set_start) {
	auto const& sel = c->selectionController->GetSelectedSet();
	if (sel.empty()) return;
	int start = c->videoController->TimeAtFrame(c->videoController->GetFrameN(), agi::vfr::START);
	int end = c->videoController->TimeAtFrame(c->videoController->GetFrameN(), agi::vfr::END);
	for (auto line : sel) {
	if (set_start || line->Start > start)
	line->Start = start;
	if (!set_start || line->End < end)
	line->End = end;
	}
	c->ass->Commit(_("timing"), AssFile::COMMIT_DIAG_TIME);
	}

它们均涉及 context->ass->Commit()。找到相应的成员函数：

Aegisub/src/ass_file.h

Lines 174 to 180 in 1fd46d9

	/// @brief Flag the file as modified and push a copy onto the undo stack
	/// @param desc Undo description
	/// @param type Type of changes made to the file in this commit
	/// @param commitId Commit to amend rather than pushing a new commit
	/// @param single_line Line which was changed, if only one line was
	/// @return Unique identifier for the new undo group
	int Commit(wxString const& desc, int type, int commitId = -1, AssDialogue *single_line = nullptr);

所以这几处 timing 的语境是，当用户修改了字幕行的起讫时间戳后，程序会记录这一操作，倘若用户想撤销或重做先前的操作时，会在「编辑」菜单中看到相应的字符串。您之前赞成过本地化「要基于 feature 而不拘泥于原文」这一原则，因此我推荐把这几处描述，翻成动宾形式，「调整时间」或者「调轴」或者「改轴」。

[op200]

#350 (comment)

这几处翻译，用户会在 GUI 中看到吗？如果仅是日志之类的，我觉得不翻译更好

[0tkl]

会

[op200]

#350 (comment)

根据我对 gettext 的理解，菜单上的 Timing 对应的是这里吧？小写的 timing 我没在 GUI 上看到过
https://github.com/op200/Aegisub/blob/c85903edda5277c9a099d710dc9294b23acb1c21/po/zh_CN.po#L6292-L6294

[0tkl]

我指的是这两处，不是上面的一级菜单栏里的那个时间轴

[op200]

懂了，刚才犯困没看清你上文的描述，不好意思

---

• timing -> 调整时轴
• karaoke timing -> 调整卡拉OK时轴

翻译成这样如何？

[op200]

我目前将 Video/Audio/Subtitle provider 翻译为 视频/音频/字幕 服务后端，原翻译是 视频/音频/字幕 来源 和 视频/音频/字幕 来自

我觉得 服务后端 还是有些词不达意，可能 模块 组件​ 之类的翻译更好？

不知大家有没有什么更好的想法

[op200]

@0tkl 请问这个 pr 能否合并？

我之前 fork 了 arch1t3cht 的库，GitHub 不允许我从 TypesettingTools fork，我打算等这个 pr 合并后删除库重新 fork，不然我每次得手动拉取并解决冲突

[0tkl]

你可以参考 https://github.com/orgs/community/discussions/22103#discussioncomment-14468953 把自己仓库的上游从 arch1t3cht 那里改成 TypesettingTools 这里

[op200]

This branch has conflicts. Should I open a new PR? @0tkl @arch1t3cht

I plan to further update the .po file based on the new .pot file

[op200]

This branch has conflicts. Should I open a new PR?

And redundant commit records caused by previous upstream merge issues

[op200]

This branch has conflicts. Should I open a new PR?

And redundant commit records caused by previous upstream merge issues

After resolving the conflict, the previous redundant commits have disappeared. It seems there's no need to open a new PR

[op200]

13df081

I have completed the translation based on the current .po file

There may be a synchronization issue between .pot and .po files. Since all visible GUI have been translated, I will wait for the next unified update of the .po file to complete the remaining translations

[EL-File4138]

Review of Change and Legacy Translation

Apart from the following specific issues above, I think the following generic principles need discussion:

• For user-facing units, I prefer 毫秒, 秒, and 像素 over mixing them with ms, s, and px. These Chinese terms are short and established, and using them consistently avoids switching conventions between related controls.
• For provider, neither 服务后端 nor 模块 / 组件 sounds right. The former is implementation language, while the latter two can imply that the provider is directly included inside Aegisub, which is often not. 来源 describes the user's choice without making that architectural claim, so I support using it consistently for audio, video, and subtitle providers.
• For the add/remove-border resolution modes, I suggest retaining both the operation and result, for example 添加边框 (等比适应) and 移除边框 (等比铺满). The current labels otherwise make the same modes look unrelated across the two dialogs.
• For ASS Outline, I strongly prefer 描边 across its color, width, and Style Editor labels. Border style is a separate ASS property, so translating both as 边框 makes the controls appear to edit the same concept. The outline and shadow color help should likewise call them 颜色, not 填充色.
• For ASS Layer, I support 层级 in full labels and 层 only in the compact grid header. This keeps the header short without alternating among 层, 层级, and 层次 in explanatory text.
• I suggest keeping the spell-check dictionary as 词典, while translating the separate thesaurus as 同义词词典. This preserves the distinction between the two menus instead of presenting both as the same feature.
• I think built-in Automation macros should be unified to have translated Chinese-only names. The current mixture of Chinese-only, English-only, and English - Chinese titles does not establish a useful rule; these are localized visible names rather than fixed identifiers.
• I suggest unifying the use of 首选项 for the command, help, and dialog for preferences. The command opens the Preferences dialog directly, so two names suggest two different surfaces.

Additionally, some inconsistencies that could be fixed by mechanical editing:

• The standard spelling 模板 instead of 模版 should be used throughout the karaoke-template strings.
• 时轴处理器 instead of 时轴后处理器 / 时间处理器
• 可视化排版工具 instead of 可视化编辑工具 / 可视化绘图工具
• 日志 / 记录 are same-feature naming conflicts. I suggest choosing one name for each family and applying it as one pass.
• 提交 instead of 接受 for audio commit
• 平移 / 偏移 for shift (likely context-dependent)
• 撤销 / 撤消 for undo
• Paste Over 文本 / 文字
• The missing accelerator on Skip Override Tags
• Untranslated English in the FFmpeg log levels, font diagnostics, and edit-box field help.
• Inconsistent use of ASCII/CJK symbols like () !? needs reconciliation.

[op200]

Review of Change and Legacy Translation

Apart from the following specific issues above, I think the following generic principles need discussion:

* For user-facing units, I prefer `毫秒`, `秒`, and `像素` over mixing them with `ms`, `s`, and `px`. These Chinese terms are short and established, and using them consistently avoids switching conventions between related controls.

这些单位的英文缩写都是常用的，ms s 等更是国际标准单位，且翻译的上下文在末尾的括号里，不会产生歧义，即使没见过 px 的用户也能通过上下文推断出含义，统一这些单位为英文缩写虽然没有特别的好处，但也没有坏处

* For provider, neither `服务后端` nor `模块` / `组件` sounds right. The former is implementation language, while the latter two can imply that the provider is directly included inside Aegisub, which is often not. `来源` describes the user's choice without making that architectural claim, so I support using it consistently for audio, video, and subtitle providers.

来源 是极其糟糕的翻译，我绝对不会认同这点，并且我觉得 服务后端 是我能想到的最合适的翻译

* For the add/remove-border resolution modes, I suggest retaining both the operation and result, for example `添加边框 (等比适应)` and `移除边框 (等比铺满)`. The current labels otherwise make the same modes look unrelated across the two dialogs.

已修正

* For ASS `Outline`, I strongly prefer `描边` across its color, width, and Style Editor labels. `Border style` is a separate ASS property, so translating both as `边框` makes the controls appear to edit the same concept. The outline and shadow color help should likewise call them `颜色`, not `填充色`.

已将 填充色 -> 颜色

* For ASS Layer, I support `层级` in full labels and `层` only in the compact grid header. This keeps the header short without alternating among `层`, `层级`, and `层次` in explanatory text.

已将 msgstr "层(&L)" -> msgstr "层级(&L)"

* I suggest keeping the spell-check `dictionary` as `词典`, while translating the separate `thesaurus` as `同义词词典`. This preserves the distinction between the two menus instead of presenting both as the same feature.

已修正

* I think built-in Automation macros should be unified to have translated Chinese-only names. The current mixture of Chinese-only, English-only, and `English - Chinese` titles does not establish a useful rule; these are localized visible names rather than fixed identifiers.

我认为保留原标题才能保证所有用户都能判断脚本根本上是哪个，即使翻译修改也能保证用户从原标题判断，翻译只起到了速览的作用，无法在几个字内概括脚本的作用，那么还不如保留原标题

* I suggest unifying the use of `首选项` for the command, help, and dialog for preferences. The command opens the Preferences dialog directly, so two names suggest two different surfaces.

如果你指的是 Preferences 和 Option 的重复问题，这应当改 cpp，改 po 文件没法解决这个问题

Additionally, some inconsistencies that could be fixed by mechanical editing:

统一用词的部分我尽量修正，有些关键字搜不到的就不好修了

[op200]

I found that wxstd.mo would replace the translations in aegisub.mo

I'm not sure if the compiled content of /po/*.po will replace wxstd.mo. If not, it will cause GUI display bugs

@0tkl @arch1t3cht
Could you please take a look at the related issues?

[op200]

* The standard spelling `模板` instead of `模版` should be used throughout the karaoke-template strings.

已修正

* `时轴处理器` instead of `时轴后处理器` / `时间处理器`

原文中有 Post，主要的功能也是后处理，所以翻译成 后处理器 没啥问题

* `可视化排版工具` instead of `可视化编辑工具` / `可视化绘图工具`

已完善

* `日志` / `记录` are same-feature naming conflicts. I suggest choosing one name for each family and applying it as one pass.

已统一为 日志

* `提交` instead of `接受` for audio commit

已将原文为 Commit 的翻译统一为 提交

* `平移` / `偏移` for shift (likely context-dependent)

这个不好统一，混用也不会导致歧义，以后看到了慢慢改吧

* `撤销` / `撤消` for undo

已统一为 撤销

* Paste Over `文本` / `文字`

这个更不好改，暂且不动

* The missing accelerator on `Skip Override Tags`

已修正 （msgid "S&kip Override Tags"）

* Untranslated English in the FFmpeg log levels, font diagnostics, and edit-box field help.

日志级别都是专有名词，保留原文（不过一些词被覆盖翻译了）

另两个的 GUI 控件在哪？我没看懂指的是哪个

* Inconsistent use of ASCII/CJK symbols like () !? needs reconciliation.

标点一直是统一的，主要为了对齐，部分标点统一为半角