Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs(library/uuid): update translation#1213

Open
rockleona wants to merge 1 commit intopython:3.14from
rockleona:library/uuid
Open

docs(library/uuid): update translation#1213
rockleona wants to merge 1 commit intopython:3.14from
rockleona:library/uuid

Conversation

@rockleona
Copy link
Collaborator

screenshotScreenShot Tool -20260304004518

Copy link
Contributor

CopilotAI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the zh_TW translation for theuuid library documentation to cover newly added/updated UUID RFC 9562-related text.

Changes:

  • Added translations for multiple previously-untranslateduuid doc strings inlibrary/uuid.po.
  • Updated/filled in translations for new UUID version behaviors (e.g., versions 6/7/8, timestamp/counter descriptions, RFC 9562 references).

💡Add Copilot custom instructions for smarter, more guided reviews.Learn how to get started.


"當指定時,參數 *a*、*b* 和 *c* 預期為分別為 48、12 和 62 位元的正整數。如果它們超"
"過了預期的位元數,則只保留它們的最低有效位元;未指定的參數將被替換為適當大小的偽隨機整數。"

Copy link

CopilotAIMar 3, 2026

Choose a reason for hiding this comment

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

There’s a whitespace-only line after the msgstr (line contains spaces). This can cause powrap/pre-commit to reformat the file or fail linting. Please remove the trailing spaces so the separator line is either completely empty or omitted.

Suggested change

Copilot uses AI. Check for mistakes.
@josixjosix self-requested a reviewMarch 14, 2026 02:53
Copy link
Collaborator

@josixjosix left a comment

Choose a reason for hiding this comment

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

感謝翻譯貢獻!整體翻譯品質不錯,reST 語法保留正確,標點符號使用也大致符合規範。以下是需要修正的項目:

需修正 (Blocking)

  1. zh_CN 用詞:硬體地址硬體位址地址 是簡體中文用法,繁體應使用位址
  2. 尾隨空白 — msgstr 區塊後有一行包含 4 個空格的空行,需改為完全空行

建議改善 (Non-blocking)

  1. 「generate」翻譯不一致 — 新增翻譯多用生成,但既有翻譯用產生,建議統一
  2. 時間戳 vs時間戳記 — 同一檔案中兩種用法並存,建議統一為時間戳記

"address as a 48-bit positive integer. When a sequence number *clock_seq* is "
"not specified, a pseudo-random 14-bit positive integer is generated."
msgstr ""
"如果未指定 *node*,則使用 :func:`getnode` 取得硬體地址,作為 48 位元的正整數。"
Copy link
Collaborator

Choose a reason for hiding this comment

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

issue:硬體地址 應為硬體位址

地址 是簡體中文用法,繁體中文應使用位址。此檔案中其他地方(如getnode() 相關段落)也一致使用位址

Suggested change
"如果未指定 *node*,則使用 :func:`getnode`取得硬體地址,作為 48 位元的正整數。"
+"如果未指定 *node*,則使用 :func:`getnode`取得硬體位址,作為 48 位元的正整數。"


"當指定時,參數 *a*、*b* 和 *c* 預期為分別為 48、12 和 62 位元的正整數。如果它們超"
"過了預期的位元數,則只保留它們的最低有效位元;未指定的參數將被替換為適當大小的偽隨機整數。"

Copy link
Collaborator

Choose a reason for hiding this comment

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

issue: 此行有尾隨空白(4 個空格),應為完全空行。

尾隨空白在 PO 檔案中可能導致解析問題,請移除多餘的空格。

Suggested change
+

"func:`uuid3` for UUID version 3, and so on. Note that UUID version 2 is "
"deliberately omitted as it is outside the scope of the RFC."
msgstr ""
"這個模組提供了不可變的 :class:`UUID` 物件(:class:`UUID` 類別)和用於生成對應於 "
Copy link
Collaborator

@josixjosixMar 14, 2026
edited
Loading

Choose a reason for hiding this comment

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

suggestion (non-blocking): 整個檔案中「generate」的翻譯不一致——新增的翻譯大量使用生成,但檔案中既有翻譯多處使用產生(如 line 252「以多行程安全的方式產生 UUID」、line 294「產生 UUID」)。

"epoch (1582-10-15 00:00:00) for versions 1 and 6, or the 48-bit timestamp in "
"milliseconds since Unix epoch (1970-01-01 00:00:00) for version 7."
msgstr ""
"60 位元的時間戳,對於版本 1 和 6 是自格里高利紀元 (Gregorian Epoch, 1582-10-15 00:00"
Copy link
Collaborator

@josixjosixMar 14, 2026
edited
Loading

Choose a reason for hiding this comment

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

suggestion (non-blocking): 此處使用時間戳,但 line 365 使用時間戳記,這邊可以看看需不需要統一用詞

"epoch (1582-10-15 00:00:00) for versions 1 and 6, or the 48-bit timestamp in "
"milliseconds since Unix epoch (1970-01-01 00:00:00) for version 7."
msgstr ""
"60 位元的時間戳,對於版本 1 和 6 是自格里高利紀元 (Gregorian Epoch, 1582-10-15 00:00"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
"60位元的時間戳,對於版本 1 和 6 是自格里高利紀元 (Gregorian Epoch, 1582-10-15 00:00"
"60位元的時間戳記,對於版本 1 和 6 是自格里高利紀元 (Gregorian Epoch, 1582-10-15 00:00"

@josix
Copy link
Collaborator

fix#1212

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

Reviewers

@josixjosixjosix requested changes

Copilot code reviewCopilotCopilot left review comments

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@rockleona@josix

[8]ページ先頭

©2009-2026 Movatter.jp