Skip to content

Conversation

@dyrone
Copy link

@dyrone dyrone commented Jun 11, 2025

Thanks for taking the time to contribute to Git! Please be advised that the
Git community does not use github.com for their contributions. Instead, we use
a mailing list ([email protected]) for code submissions, code reviews, and
bug reports. Nevertheless, you can use GitGitGadget (https://gitgitgadget.github.io/)
to conveniently send your Pull Requests commits to our mailing list.

For a single-commit pull request, please leave the pull request description
empty
: your commit message itself should describe your changes.

Please read the "guidelines for contributing" linked above!

@github-actions
Copy link

github-actions bot commented Jun 11, 2025

Warnings found by git-po-helper in workflow #1005:

------------------------------------------------------------------------------
INFO [po/zh_CN.po@2249978]	5818 translated messages, 1 fuzzy translation. 
INFO checking commits: 1 passed.                  
------------------------------------------------------------------------------
INFO downloading pot file from https://github.com/git-l10n/pot-changes/raw/pot/master/po/git.pot 
------------------------------------------------------------------------------
WARNING [po/zh_CN.po@2249978]	1 fuzzy string(s) in your 'po/XX.po' 
WARNING [po/zh_CN.po@2249978]                        
WARNING [po/zh_CN.po@2249978]	  > po/XX.po:27901: this message needs to be reviewed by the translator 
WARNING [po/zh_CN.po@2249978]                        

@dyrone dyrone force-pushed the tl/zh_CN_2.50_rnd branch from 11cb418 to a5d08c7 Compare June 11, 2025 14:15
@jiangxin
Copy link
Member

我会逐一检查补丁中的中文翻译内容:

"对象过滤器不被支持:'%s'"
建议改为: "不支持对象过滤器:'%s'"
原因:语序可以更自然

"引用和 --all 需搭配使用"
建议改为: "--all 选项不能与具体引用同时使用"
原因:原译文含义不够准确和清晰

"使用 --cruft 时,只重新打包小于此大小的废弃包"
建议改为: "使用 --cruft 时,仅重新打包小于此大小的废弃包文件"
原因:增加"文件"使意思更完整

"无法从 %s 的包头 '%s' 中解析类型 "
存在问题:末尾有多余空格
应改为: "无法从 %s 的包头 '%s' 中解析类型"

"不能打开 '%s'"
建议改为: "无法打开 '%s'"
原因:保持用语一致性,文中类似表述大多用"无法"

"--maintenance 选项的模式未知: %s"
存在问题:冒号使用英文冒号,不符合中文习惯
应改为: "--maintenance 选项的模式未知:%s"

"尝试 mmap %,超过了最大值 %"
建议增加技术术语的解释,如:
"尝试内存映射(mmap) %,超过了最大值 %"

总的来说,这份翻译质量还不错,主要需要改进的是:

  • 个别词语选择可以更准确自然
  • 标点符号使用需要符合中文习惯
  • 技术术语可以适当增加解释
  • 注意删除多余的空格
  • 保持用语的一致性

@dyrone dyrone force-pushed the tl/zh_CN_2.50_rnd branch 2 times, most recently from 66a286d to 3c51161 Compare June 12, 2025 03:48
@dyrone dyrone force-pushed the tl/zh_CN_2.50_rnd branch from 3c51161 to 1da44b1 Compare June 12, 2025 06:55
Helped-by: 依云 <[email protected]>
Helped-by: Jiang Xin <[email protected]>
Signed-off-by: Teng Long <[email protected]>
@dyrone dyrone force-pushed the tl/zh_CN_2.50_rnd branch from 1da44b1 to 2249978 Compare June 12, 2025 06:58
@jiangxin
Copy link
Member

cherry-picked your commit, and fix one fuzzy translation.

@jiangxin jiangxin closed this Jun 12, 2025
Copy link

@fangyi-zhou fangyi-zhou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

抱歉周中的时候比较忙,没来得及 review。如果可以的话,可以在下一次窗口再并入。

#: builtin/diff-pairs.c
#, c-format
msgid "unable to parse object id: %s"
msgstr "不能解析对象ID:%s"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-msgstr "不能解析对象ID:%s"
+msgstr "不能解析对象 ID:%s"


#: builtin/update-ref.c
msgid "batch reference updates"
msgstr "批量引用更新"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

此处的 batch 应该是动词?
https://github.com/git/git/blob/f1ca98f609f9a730b9accf24e5558a10a0b41b6c/builtin/update-ref.c#L790

是否应该译为 “批量处理引用更新”

#: object-file.c
#, c-format
msgid "unable to parse type from header '%s' of %s"
msgstr "无法从 %s 的包头 '%s' 中解析类型"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里两个 %s 是不是应该反过来?

@jiangxin
Copy link
Member

抱歉周中的时候比较忙,没来得及 review。如果可以的话,可以在下一次窗口再并入。

See PR #868

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants