Conversation
… of the original text, otherwise it wouldn't be understandable in chinese
Dr-XYZ
reviewed
Jul 22, 2025
library/contextvars.po
Outdated
| "return the default value for the context variable, if it was created with " | ||
| "one; or" | ||
| msgstr "" | ||
| msgstr "回傳情境變數的預設值(如果是用情境變量建立的的話);否則" |
Collaborator
There was a problem hiding this comment.
Suggested change
| msgstr "回傳情境變數的預設值(如果是用情境變量建立的的話);否則" | |
| msgstr "回傳情境變數的預設值(如果它在建立時有指定的話);否則" |
Contributor
Author
There was a problem hiding this comment.
想請問這麼建議翻有沒有什麼理由?
因為我會把那個 if it was created with "one" 的 "one" 解釋成 context variable,而且中文語境其實沒有那麼常用「它」,比較常重複「它」所直接指涉的對象,我也不太確定翻成「指定」是不是哪裡的慣例還是?
請大大指教
Collaborator
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
nice! thanks! Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Collaborator
|
Hi @husohome |
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Co-authored-by: Dr.XYZ <dr.xyz.tw@gmail.com>
Dr-XYZ
reviewed
Jul 31, 2025
Dr-XYZ
approved these changes
Jul 31, 2025
Contributor
Author
|
感謝大大們的指教 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


contextvars.po
註: effective 的翻法:
因為英文中 effective 不一定是指有效的,有時是 in effect 或甚至 in fact 的意思
#: ../../library/contextvars.rst:147
Each thread has its own "effective" stack of :class:
!Contextobjects. The :term:current contextis the :class:!Contextobject at the top of the current thread's stack. All :class:!Contextobjects in the stacks are considered to be entered.這裡翻成「目前執行緒堆疊頂端的」是因為這個 effective stack 並不是專有名詞,他就是指實際上正在主控的那個 stack
#: ../../library/contextvars.rst:170
Exiting a context "effectively" reverts any changes made to context variables while the context was entered (if needed, the values can be restored by re-entering the context).
這裡的 effectively 也不是有效的,而是「實際上的效果是」的意思