8000 Fill missing translations in tutorial/interpreter.po by Wayne1316 · Pull Request #16 · python/python-docs-zh-tw · GitHub
[go: up one dir, main page]

Skip to content

Fill missing translations in tutorial/interpreter.po #16

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 1 commit into from

Conversation

Wayne1316
Copy link

翻譯以下文件

直譯器unix安裝路徑
直譯器windows安裝路徑
直譯器模式說明
首行編碼
首行編碼範例

尚有兩個未翻譯

直譯器unix安裝路徑
直譯器windows安裝路徑
直譯器模式說明
首行編碼
首行編碼範例
@adrianliaw adrianliaw changed the base branch from master to 3.7 July 12, 2018 18:52
@adrianliaw adrianliaw changed the title Wayne Fill missing translations in tutorial/interpreter.po Jul 17, 2018
Copy link
Collaborator
@adrianliaw adrianliaw left a comment

Choose a reason for hiding this comment

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

Hi @Wayne1316, thanks so much for the contribution! It's a good work if you're new to open-source project contributions ✨ However, there are a lot that I think should be changed at the moment, please feel free to leave a comment if you don't agree with my thoughts. If you need any help, feel free to ping me on Telegram also.

One thing I also want to mention is that, it's always better to name a branch or pull-request meaningfully, I've changed the PR title so it better describes what you're doing.

@@ -34,6 +35,9 @@ msgid ""
"local/bin` in your Unix shell's search path makes it possible to start it by "
"typing the command:"
msgstr ""
"Python 直譯器通常安裝在: file: '/usr/local/bin/python3.7 ' 的作業系統上,它"
Copy link
Collaborator

Choose a reason for hiding this comment

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

:file:`/usr/local/bin/python3.7` is an rST "interpreted text" syntax [1], which should remain the same in the translation. Please use the ASCII colon and backticks (instead of quotes) for these interpreted text syntax, and don't forget to remove the redundant space between :file: and `/usr/local/bin/python3.7`.

Also, I'm very sorry to say this but I think the translation does not deliver the meaning well, in terms of both semantics and grammar. Please refine the translation so that the translation's meaning matches the source documentation.

[1] http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#interpreted-text

@@ -34,6 +35,9 @@ msgid ""
"local/bin` in your Unix shell's search path makes it possible to start it by "
"typing the command:"
msgstr ""
"Python 直譯器通常安裝在: file: '/usr/local/bin/python3.7 ' 的作業系統上,它"
"是可以用的;放置直譯器檔案在: '/usr/local/bin ‘,在您的 Unix shell 的搜尋路徑"
"中通過輸入命令可以啟動它:"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Note that the halfwidth colon should be translated into fullwidth colon in the translation, except for the ones that represents rST syntax such as "double-colon" (::) or "interpreted text" described previously.

@@ -53,6 +57,9 @@ msgid ""
"To add this directory to your path, you can type the following command into "
"the command prompt in a DOS box::"
msgstr ""
"在 Windows 作業系統上,Python 通常安裝在:file:'C:\\\\Python36 中, 您可以在安"
Copy link
Collaborator

Choose a reason for hiding this comment

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

As mentioned in the previous comment, the rST syntax should remain the same in the translations.

Also, the comma should be fullwidth.

s/安裝/被安裝/ (passive voice grammar
s/您可以/不過您也可以/ (notice the word "though" in the source

@@ -53,6 +57,9 @@ msgid ""
"To add this directory to your path, you can type the following command into "
"the command prompt in a DOS box::"
msgstr ""
"在 Windows 作業系統上,Python 通常安裝在:file:'C:\\\\Python36 中, 您可以在安"
"裝程式時更改此路徑。 將此目錄添加到您的執行路徑中,可以在 DOS 視窗中的命令提"
Copy link
Collaborator

Choose a reason for hiding this comment

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

The word "installer" can be and should be translated into "安裝程式" on its own, so it would be awkward to add "時" right after "安裝程式" since "安裝程式" is a noun in a grammatical sense.

s/將此目錄...../欲將此目錄/ (notice the word "to" in the source

@@ -53,6 +57,9 @@ msgid ""
"To add this directory to your path, you can type the following command into "
"the command prompt in a DOS box::"
msgstr ""
"在 Windows 作業系統上,Python 通常安裝在:file:'C:\\\\Python36 中, 您可以在安"
"裝程式時更改此路徑。 將此目錄添加到您的執行路徑中,可以在 DOS 視窗中的命令提"
"示字元下輸入以下命令:"
Copy link
Collaborator

Choose a reason for hiding this comment

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

s/命令/指令/

The colon here, please follow the last point in our translation guideline about rST syntax [1] since this is a double-colon which means differently from single-colon in rST.

[1] https://github.com/python/python-docs-zh-tw#rst

@@ -168,6 +175,11 @@ msgid ""
"dots (``...``). The interpreter prints a welcome message stating its version "
"number and a copyright notice before printing the first prompt:"
msgstr ""
"當從 tty 讀取命令時, 直譯器提示目前為 * 交互模式 *。 在此模式下,它會提示使"
"用 * 主提示符號 * 輸入下一個命令,主提示通常使用三個大於符號 (``>>>``)表"
Copy link
Collaborator

Choose a reason for hiding this comment

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

s/提示符號/提示字元/

There should be zero-width space before and after the double-backticks in order to make the markup work.

@@ -168,6 +175,11 @@ msgid ""
"dots (``...``). The interpreter prints a welcome message stating its version "
"number and a copyright notice before printing the first prompt:"
msgstr ""
"當從 tty 讀取命令時, 直譯器提示目前為 * 交互模式 *。 在此模式下,它會提示使"
"用 * 主提示符號 * 輸入下一個命令,主提示通常使用三個大於符號 (``>>>``)表"
"示;對於多行的程式, 它會提示使用 * 次提示符 *, 預設情況下為三個點 (``..."
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same comment as the previous ones.

8000
"當從 tty 讀取命令時, 直譯器提示目前為 * 交互模式 *。 在此模式下,它會提示使"
"用 * 主提示符號 * 輸入下一個命令,主提示通常使用三個大於符號 (``>>>``)表"
"示;對於多行的程式, 它會提示使用 * 次提示符 *, 預設情況下為三個點 (``..."
"``)。在輸出第一個提示符號之前,直譯器會輸出一則歡迎訊息,說明目前使用的版本"
Copy link
Collaborator

Choose a reason for hiding this comment

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

s/輸出/印出/ ("輸出" is mainly the meaning of "output" or "export"

@@ -212,6 +224,7 @@ msgid ""
"To declare an encoding other than the default one, a special comment line "
"should be added as the *first* line of the file. The syntax is as follows::"
msgstr ""
"若要聲明非預設編碼, 應將特殊註解添加在為檔案的 * 首 * 行。 結構如下所示::"
Copy link
Collaborator

Choose a reason for hiding this comment

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

The comma should be replaced with the full-width comma. The second sentence has two verb occurrences, "添加" and "為", which wouldn't make a lot of sense in grammar.

The italic text markup should follow the previous comments. The redundant space after the full stop should be removed.

s/結構/語法/

The final double-colon in the line should be translated with the last rule of the rST guidelines [1]

[1] https://github.com/python/python-docs-zh-tw#rst

@@ -221,7 +234,7 @@ msgstr ""
msgid ""
"For example, to declare that Windows-1252 encoding is to be used, the first "
"line of your source code file should be::"
msgstr ""
msgstr "例如,要聲明使用Windows-1252的編碼,您的原始碼首行應為::"
Copy link
Collaborator

Choose a reason for hiding this comment

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

As described in the third point in the translation guidelines [1], "Windows-1252" should have a space both before and after the word.

The colon, again, should follow the rST guidelines.

[1] https://github.com/python/python-docs-zh-tw#id7

@StevenHsuYL
Copy link
Contributor

tutorial/interpreter.po was finished at #67
This PR could be closed.
Thanks for your work!

@mattwang44 mattwang44 closed this Sep 27, 2021
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.

4 participants
0