Skip to content

Translating json rst 162 #541

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from

Conversation

husohome
Copy link
Contributor

@husohome husohome commented Aug 5, 2023

No description provided.

library/json.po Outdated
Comment on lines 146 to 150
msgstr "如果 *allow_nan* 設為 False (預設值為 ``True``), 那麼串聯化 (serialize)"
":class:`float` 的特殊值 (``nan``, ""``inf``, ``-inf``) 會觸發 :exc:`ValueError`"
"這麼設定是為了遵守較嚴格的 JSON 規範 (strict JSON specification)。 如果設為 True,"
"則串聯化這些極值不會出錯,而是會被自動代換成 JavaScript 上等價的值去(``NaN``,"
"``Infinity``, ``-Infinity``)"
Copy link
Collaborator

Choose a reason for hiding this comment

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

  • strict JSON specification 我覺得不是專有名詞不用附上原文
  • 標點符號相關修正
Suggested change
msgstr "如果 *allow_nan* 設為 False (預設值為 ``True``), 那麼串聯化 (serialize)"
":class:`float` 的特殊值 (``nan``, ""``inf``, ``-inf``) 會觸發 :exc:`ValueError`"
"這麼設定是為了遵守較嚴格的 JSON 規範 (strict JSON specification)。 如果設為 True,"
"則串聯化這些極值不會出錯,而是會被自動代換成 JavaScript 上等價的值去(``NaN``,"
"``Infinity``, ``-Infinity``)"
msgstr "如果 *allow_nan* 設為 False預設值為 ``True``),那麼串聯化 (serialize)"
":class:`float` 的特殊值 (``nan``, ``inf``, ``-inf``) 會觸發 :exc:`ValueError`"
"這麼設定是為了遵守較嚴格的 JSON 規範如果設為 True,"
"則串聯化這些極值不會出錯,而是會被自動代換成 JavaScript 上等價的值去 (``NaN``,"
"``Infinity``, ``-Infinity``)"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

感謝修正 有稍微再調一下斷行

@mattwang44
Copy link
Collaborator

發現有重複的 PR #525
同一翻譯任務請在同一個 branch/PR 上修正,請不要重複開歐;要請你關掉 #525#541

@husohome
Copy link
Contributor Author

husohome commented Aug 9, 2023

感激 依照建議關掉PR

@husohome husohome closed this Aug 9, 2023
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.

2 participants