Translate email charset rst: 27-39 #601
Open
Conversation
This file contains 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
|
commit history 有舊的 commit，請先 rebase 到最新的 3.12 branch 上再 push 上來 🙏🏽 |
|
Translate email charset rst: 27-39 revised. :) |
|
Hi Isa, |
Hi Matt, I've rebased it. :) |
|
Hi @isabellechiu |
isabellechiu
force-pushed
the
translate-email-charset
branch
from
43af438
to
2e9e957
Compare
mattwang44
reviewed
Oct 13, 2023
library/email.charset.po
Outdated
|
|
||
| #: ../../library/email.charset.rst:27 | ||
| msgid "Map character sets to their email properties." | ||
| msgstr "" | ||
| msgstr "將字元集合對應到其電子郵件的屬性。" |
There was a problem hiding this comment.
通常 attribute 會翻譯成屬性、property 翻成特性
Suggested change
| msgstr "將字元集合對應到其電子郵件的屬性。" | |
| msgstr "將字元集合對應到其電子郵件的特性。" |
|
|
||
| #: ../../library/email.charset.rst:35 | ||
| msgid "" | ||
| "Certain character sets must be encoded with quoted-printable or base64 when " | ||
| "used in email headers or bodies. Certain character sets must be converted " | ||
| "outright, and are not allowed in email." | ||
| msgstr "" | ||
| "在電子郵件標題或內文用特定字元集合時必須使用 quoted-printable 或 base64 來編碼。" |
There was a problem hiding this comment.
https://zh.wikipedia.org/zh-tw/Quoted-printable
Suggested change
| "在電子郵件標題或內文用特定字元集合時必須使用 quoted-printable 或 base64 來編碼。" | |
| "在電子郵件標題或內文用特定字元集合時必須使用可列印字元編碼 (quoted-printable) 或 base64 來編碼。" |
或者
Suggested change
| "在電子郵件標題或內文用特定字元集合時必須使用 quoted-printable 或 base64 來編碼。" | |
| "在電子郵件標題或內文用特定字元集合時必須使用 quoted-printable（可列印字元編碼）或 base64 來編碼。" |
| @@ -69,13 +69,18 @@ msgid "" | |||
| "codecs. Given a character set, it will do its best to provide information " | |||
| "on how to use that character set in an email message in an RFC-compliant way." | |||
| msgstr "" | |||
| "此類別提供相關資訊關於電子郵件對特定字元集合的要求。" | |||
There was a problem hiding this comment.
好像不太通順
Suggested change
| "此類別提供相關資訊關於電子郵件對特定字元集合的要求。" | |
| "此類別提供有關於電子郵件對特定字元集的規範資訊。" |
| @@ -69,13 +69,18 @@ msgid "" | |||
| "codecs. Given a character set, it will do its best to provide information " | |||
| "on how to use that character set in an email message in an RFC-compliant way." | |||
| msgstr "" | |||
| "此類別提供相關資訊關於電子郵件對特定字元集合的要求。" | |||
| "同時也提供轉換字元集合之間便利的做法，並給予適用的編解碼器 (codecs) 可用性。" | |||
There was a problem hiding this comment.
可以在幫忙想想看怎麼修改比較通暢
- 這邊的 given 比較像是「考慮到...」
- routine 指的不單只是「做法」
Suggested change
| "同時也提供轉換字元集合之間便利的做法，並給予適用的編解碼器 (codecs) 可用性。" | |
| "考慮到適用之編解碼器 (codec) 的可用性，它還提供了在字元集合之間進行轉換的便利慣用做法。" |
| @@ -69,13 +69,18 @@ msgid "" | |||
| "codecs. Given a character set, it will do its best to provide information " | |||
| "on how to use that character set in an email message in an RFC-compliant way." | |||
| msgstr "" | |||
| "此類別提供相關資訊關於電子郵件對特定字元集合的要求。" | |||
| "同時也提供轉換字元集合之間便利的做法，並給予適用的編解碼器 (codecs) 可用性。" | |||
| "給定一個字元集合，此類別將會提供這個字元集合在電子郵件訊息中符合RFC (RFC-compliant) 的使用方式。" | |||
There was a problem hiding this comment.
- 稍微調換順序
- 中文字和英文字間記得要留有空格
Suggested change
| "給定一個字元集合，此類別將會提供這個字元集合在電子郵件訊息中符合RFC (RFC-compliant) 的使用方式。" | |
| "給定一個字元集合，它將盡量提供有關如何以符合 RFC (RFC-compliant) 的方式在電子郵件訊息中使用該字元集合的資訊。" |
| @@ -69,13 +69,18 @@ msgid "" | |||
| "codecs. Given a character set, it will do its best to provide information " | |||
| "on how to use that character set in an email message in an RFC-compliant way." | |||
| msgstr "" | |||
| "此類別提供相關資訊關於電子郵件對特定字元集合的要求。" | |||
| "同時也提供轉換字元集合之間便利的做法，並給予適用的編解碼器 (codecs) 可用性。" | |||
| "給定一個字元集合，此類別將會提供這個字元集合在電子郵件訊息中符合RFC (RFC-compliant) 的使用方式。" | |||
There was a problem hiding this comment.
- 稍微調換順序
- 中文字和英文字間記得要留有空格
Suggested change
| "給定一個字元集合，此類別將會提供這個字元集合在電子郵件訊息中符合RFC (RFC-compliant) 的使用方式。" | |
| "給定一個字元集合，它將盡量提供有關如何以符合 RFC (RFC-compliant) 的方式在電子郵件訊息中使用該字元集合的資訊。" |
| @@ -89,6 +94,11 @@ msgid "" | |||
| "with base64, bodies will not be encoded, but output text will be converted " | |||
| "from the ``euc-jp`` character set to the ``iso-2022-jp`` character set." | |||
| msgstr "" | |||
| "備註 *input_charset* 描述如下；字元集合會被強制轉換為小寫。經過別名標準化後，" | |||
| "會進到字元集合登錄檔 (registry)去查詢此字元集合使用的標題編碼、內文編碼以及輸出轉換編解碼器 (codec)。" | |||
There was a problem hiding this comment.
中文字與半形標點符號間也要留空白
Suggested change
| "會進到字元集合登錄檔 (registry)去查詢此字元集合使用的標題編碼、內文編碼以及輸出轉換編解碼器 (codec)。" | |
| "會進到字元集合登錄檔 (registry) 去查詢此字元集合使用的標題編碼、內文編碼以及輸出轉換編解碼器 (codec)。" |
| "例如：如果 *input_charset* 是 ``iso-8859-1`` 標題跟內文會被用 quoted-printable 編碼並且不需要輸出轉換編解碼器 (codecs)。" | ||
| "如果 *input_charset* 是 ``euc-jp`` 標題則會被編碼成 base64 但內文不會被編碼而輸出的文字則會從 ``euc-jp`` " |
There was a problem hiding this comment.
Suggested change
| "例如：如果 *input_charset* 是 ``iso-8859-1`` 標題跟內文會被用 quoted-printable 編碼並且不需要輸出轉換編解碼器 (codecs)。" | |
| "如果 *input_charset* 是 ``euc-jp`` 標題則會被編碼成 base64 但內文不會被編碼而輸出的文字則會從 ``euc-jp`` " | |
| "例如：如果 *input_charset* 是 ``iso-8859-1``，標題跟內文會被用 quoted-printable 編碼並且不需要輸出轉換編解碼器 (codecs)。" | |
| "如果 *input_charset* 是 ``euc-jp``，標題則會被編碼成 base64，但內文不會被編碼，而輸出的文字則會從 ``euc-jp`` " |
|
@isabellechiu |
對的, 但進度落後了, 有需要先關PR嗎? |
|
@isabellechiu |
isabellechiu
force-pushed
the
translate-email-charset
branch
from
2e9e957
to
7951fd2
Compare
mattwang44
force-pushed
the
translate-email-charset
branch
from
7951fd2
to
4df64cd
Compare
|
最近會有新進度嗎～ |
|
Dear Matt,
不好意思，因工作小忙，最近荒廢了 ><
BR,
Isabelle
…On Mon, 29 Apr 2024 at 13:31, Wei-Hsiang (Matt) Wang < ***@***.***> wrote:
最近會有新進度嗎～
—
Reply to this email directly, view it on GitHub
<#601 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJOJULXGFMPPRQBWATUNYTDY7XLMNAVCNFSM6AAAAAA3XJJCU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRHEYTONJWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.