Skip to content

Translate c-api/hash.po - #1259

Open
lilwad-0730 wants to merge 2 commits into
python:3.15from
lilwad-0730:c-api/hash
Open

lilwad-0730 wants to merge 2 commits into
python:3.15from
lilwad-0730:c-api/hash

Conversation

@lilwad-0730

Copy link
Copy Markdown

完成 c-api/hash.po 中原先未翻譯的 6 筆條目,涵蓋雜湊演算法識別值、短緩衝區最佳化,以及緩衝區雜湊函式的說明。保留 reST 引用標記並修正最後一筆譯文的成員引用格式。

Closes #1257

驗證:

  • sphinx-lint c-api/hash.po 通過。
  • PO 解析通過,40 筆內容均已翻譯,無 fuzzy 標記。
  • 與官方 3.15 比對,英文原文字串未變,所有行皆不超過 79 字元。
  • git diff --check 通過。
  • 尚未執行完整 Sphinx 文件建置。

@ken71301 ken71301 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Thanks for the translation! I rendered c-api/hash.po against 3.15 and checked the 6 new entries (Py_HASH_ALGORITHM, Py_HASH_FNV/SIPHASH*, Py_HASH_CUTOFF x2, Py_HashBuffer x2). They all render correctly, with the reST roles and links intact, and the terminology (雜湊, 緩衝區, 緩衝協定, 門檻值, 不可變物件) is consistent with the glossary. The meaning matches the English source.

Two suggestions:

  1. Stray space after 。 — several paragraphs render with a space after a full-width period, e.g. …雜湊演算法。 雜湊演算法可透過…, …設為 7,…。 若在… and …一致。 此雜湊值…. This is probably a space left at a wrapped line join in the PO. Removing it (or running make wrap) should fix it.
  2. Optional wording — the second Py_HashBuffer paragraph, 「對透過 tp_richcompare 函式與另一個物件的緩衝區進行比較的不可變物件實作其雜湊功能」, is a long chain of modifiers. Something like 「用於為不可變物件實作雜湊,其 tp_richcompare 函式會與另一個物件的緩衝區進行比較」 may read more easily.

Nothing blocking. I only checked how the changed entries render, not the rest of the file.

This branch has not been deployed

No deployments
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.

Translate c-api/hash.po

2 participants