Origin/translate-email-charset #736
Closed
Conversation
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
|
要記得 rebase 歐 |
mattwang44
force-pushed
the
origin/translate-email-charset
branch
from
a71af4e to
7955811
Compare
mattwang44
reviewed
Dec 6, 2023
| @@ -107,13 +110,19 @@ msgid "" | |||
| "``charset.BASE64`` (for base64 encoding), or ``charset.SHORTEST`` for the " | |||
| "shortest of QP or BASE64 encoding. Otherwise, it will be ``None``." | |||
| msgstr "" | |||
| ＂如果字元集合被用在電子郵件標題前必須被編碼的話，＂ | |||
There was a problem hiding this comment.
不少地方用到全形引號了，要改成半形
Suggested change
| ＂如果字元集合被用在電子郵件標題前必須被編碼的話，＂ | |
| "如果字元集合被用在電子郵件標題前必須被編碼的話，" |
There was a problem hiding this comment.
在 github 上看還是怪怪的，可以的話請跟原文的 "" 符號比對一下，可以發現並不一樣（雖然乍看之下不容易分辨）。
| @@ -107,13 +110,19 @@ msgid "" | |||
| "``charset.BASE64`` (for base64 encoding), or ``charset.SHORTEST`` for the " | |||
| "shortest of QP or BASE64 encoding. Otherwise, it will be ``None``." | |||
| msgstr "" | |||
| ＂如果字元集合被用在電子郵件標題前必須被編碼的話，＂ | |||
| ＂這個屬性會被設為 ``charset.QP`` （表quoted-printable編碼），＂ | |||
| ＂ ``charset.BASE64`` （表base64編碼格式），或是 ``charset.SHORTEST`` 表示最短的 QP或是base64編碼格式。" | |||
There was a problem hiding this comment.
- 半形引號
- 中英文間要有空格
Suggested change
| ＂ ``charset.BASE64`` （表base64編碼格式），或是 ``charset.SHORTEST`` 表示最短的 QP或是base64編碼格式。" | |
| "``charset.BASE64`` （表 base64 編碼格式），或是 ``charset.SHORTEST`` 表示最短的 QP 或是base64編碼格式。" |
mattwang44
force-pushed
the
origin/translate-email-charset
branch
from
7955811 to
c67d059
Compare
cschan1828
requested changes
Mar 26, 2024
| @@ -107,13 +110,19 @@ msgid "" | |||
| "``charset.BASE64`` (for base64 encoding), or ``charset.SHORTEST`` for the " | |||
| "shortest of QP or BASE64 encoding. Otherwise, it will be ``None``." | |||
| msgstr "" | |||
| ＂如果字元集合被用在電子郵件標題前必須被編碼的話，＂ | |||
There was a problem hiding this comment.
在 github 上看還是怪怪的，可以的話請跟原文的 "" 符號比對一下，可以發現並不一樣（雖然乍看之下不容易分辨）。
| @@ -122,28 +131,35 @@ msgid "" | |||
| "will contain the name of the character set output will be converted to. " | |||
| "Otherwise, it will be ``None``." | |||
| msgstr "" | |||
| ＂部分的字元集合在用於電子郵件的標題或內文前必須先被轉換。＂ | |||
There was a problem hiding this comment.
Suggested change
| ＂部分的字元集合在用於電子郵件的標題或內文前必須先被轉換。＂ | |
| "部分的字元集合在用於電子郵件的標題或內文前必須先被轉換。" |
| @@ -122,28 +131,35 @@ msgid "" | |||
| "will contain the name of the character set output will be converted to. " | |||
| "Otherwise, it will be ``None``." | |||
| msgstr "" | |||
| ＂部分的字元集合在用於電子郵件的標題或內文前必須先被轉換。＂ | |||
| ＂如果 *input_charset* 是這些字元集合中的其中之一，這個屬性將會包含輸出時被轉換的字元集合名稱。＂ | |||
There was a problem hiding this comment.
Suggested change
| ＂如果 *input_charset* 是這些字元集合中的其中之一，這個屬性將會包含輸出時被轉換的字元集合名稱。＂ | |
| "如果 *input_charset* 是這些字元集合中的其中之一，這個屬性將會包含輸出時被轉換的字元集合名稱。" |
|
|
||
| #: ../../library/email.charset.rst:69 | ||
| msgid "" | ||
| "Same as *header_encoding*, but describes the encoding for the mail message's " | ||
| "body, which indeed may be different than the header encoding. ``charset." | ||
| "SHORTEST`` is not allowed for *body_encoding*." | ||
| msgstr "" | ||
| ＂與 *header_encoding* 相同，但敘述郵件訊息內文的編碼格式，則與上述的標題編碼格式不同。＂ |
There was a problem hiding this comment.
Suggested change
| ＂與 *header_encoding* 相同，但敘述郵件訊息內文的編碼格式，則與上述的標題編碼格式不同。＂ | |
| "與 *header_encoding* 相同，但敘述郵件訊息內文的編碼格式，則與上述的標題編碼格式不同。" |
|
|
||
| #: ../../library/email.charset.rst:69 | ||
| msgid "" | ||
| "Same as *header_encoding*, but describes the encoding for the mail message's " | ||
| "body, which indeed may be different than the header encoding. ``charset." | ||
| "SHORTEST`` is not allowed for *body_encoding*." | ||
| msgstr "" | ||
| ＂與 *header_encoding* 相同，但敘述郵件訊息內文的編碼格式，則與上述的標題編碼格式不同。＂ | ||
| ＂ ``charset.SHORTEST`` 是不被允許在 *body_encoding* 使用。＂ |
There was a problem hiding this comment.
Suggested change
| ＂ ``charset.SHORTEST`` 是不被允許在 *body_encoding* 使用。＂ | |
| "``charset.SHORTEST`` 是不被允許在 *body_encoding* 使用。" |
|
close it in favor of #989 |
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.
No description provided.