You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by hj...@apache.org on 2019/09/05 02:47:59 UTC
[pulsar-translation] branch master updated (ae5064b -> ad6fcfb)
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git.
from ae5064b Merge pull request #3 from apache/add-license-1
new 9f8e4a9 Add workflow_guidelines
new e8aaee9 Merge pull request #1 from ireneontheway/ireneontheway-patch-1
new f74782e Add translation workflow guidlines
new 2d85f07 Delete translation_workflow.md
new 14a2f14 Delete workflow_guidelines.md
new 681dfad Add workflow-guidelines
new dcfdc35 Update workflow_guidelines.md
new bb6be63 Apply suggestions from code review
new ad6fcfb Merge pull request #6 from ireneontheway/master
The 25 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
workflow_guidelines.md | 177 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 177 insertions(+)
create mode 100644 workflow_guidelines.md
[pulsar-translation] 24/25: Apply suggestions from code review
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit bb6be63414bee98f51139de2fe70a89b1b577bb7
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 29 11:20:54 2019 +0800
Apply suggestions from code review
Co-Authored-By: Anonymitaet <50...@users.noreply.github.com>
---
workflow_guidelines.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/workflow_guidelines.md b/workflow_guidelines.md
index e247ddc..335ecce 100644
--- a/workflow_guidelines.md
+++ b/workflow_guidelines.md
@@ -13,7 +13,7 @@ Here are the steps of the translation workflow:
2. After signing in, click **Join** at the upper right corner on the crowdin page.
> #### Note
-> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
+> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French, and Japanese.
> Select a language. Take the **Simplified Chinese Translation Project** as an example.
@@ -31,12 +31,12 @@ Files in **master > docs** are the source files of the latest versions on Pulsar
Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
-After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
+After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
### Label Setting
-- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
-- Assignees : Choose yourself to receive notifications.
-- Label : Choose “translation”.
+- Reviewers: No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
+- Assignees: Choose yourself to receive notifications.
+- Label: Choose “translation”.
### Translating
While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
@@ -60,7 +60,7 @@ After receiving the comment, reviewers start to review. The reviewer can make si
If there are no problems, the reviewer will approve this PR and merge it.
-The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
+The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
@@ -96,7 +96,7 @@ In order to improve the readability of Chinese and English mixed documents, you
Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
-Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
+Dealing with different items: Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
[pulsar-translation] 20/25: Delete translation_workflow.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 2d85f07cd850ef6ed4afd35da1afa9588a17cf1b
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 22 11:19:50 2019 +0800
Delete translation_workflow.md
---
translation_workflow.md | 177 ------------------------------------------------
1 file changed, 177 deletions(-)
diff --git a/translation_workflow.md b/translation_workflow.md
deleted file mode 100644
index af670e8..0000000
--- a/translation_workflow.md
+++ /dev/null
@@ -1,177 +0,0 @@
-# Translation workflow and guidelines
-
-Welcome to join the Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
-
-## Workflow
-
-You can find [Apache Pulsar translation project](https://crowdin.com/project/apache-pulsar) on Crowdin. For further details about the functions of Crowdin, see [Crowdin](https://crowdin.com/).
-Here are the steps of the translation workflow:
-
-### Join the Pulsar translation project
-1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
-
-
-2. After signing in, click **Join** at the upper right corner on the crowdin page.
-> #### Note
-> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
-> Select a language. Take the **Simplified Chinese Translation Project** as an example.
-
-
-### Choose a file to translate and submit a PR
-1. Click **Simplified Chinese Translation Project**.
-2. Click **master > docs**, and check out the status of each file.
-Files in **master > docs** are the source files of the latest versions on Pulsar official website. You only need to translate these markdown files.
-
-
-- Green: translated and approved
-- Blue: translated but not approved
-- Grey: not translated
-
-
-
-Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
-
-After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
-
-### Label Setting
-- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
-- Assignees : Choose yourself to receive notifications.
-- Label : Choose “translation”.
-
-### Translating
-While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
-> ####mportant
-> Don’t modify, omit or add a space in a tag, as the omission or relocation of a tag leads to mistakes shown on the website.
-
-
-
-You can modify and save the content directly. Your version will appear automatically at the top of the translation list, as Crowdin will record different versions from different translators. **TM AND MT TRANSLATION** in the bottom-right corner offers you TMs in Pulsar, Crowdin, and other websites.
-
-
-
-> #### Tip
-> You can use and update [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC) while translating.
-
-### Review
-After finishing a translation, please leave a comment in your PR. :
-For example, I've finished the translation, could you help review?
-
-After receiving the comment, reviewers start to review. The reviewer can make simple comments and notify the translator. Direct discussion in PR is encouraged.
-
-If there are no problems, the reviewer will approve this PR and merge it.
-
-The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
-Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
-
-
-
-## Guidelines
-Here are some common problems during translation. This guideline provides some advice. Please read and follow this guideline carefully before start translation. This could help improve the quality of Pulsar translation files and unify the translation style.
-
-
-### 1. Terms
-
-Pulsar, Pulsar Functions, BookKeeper, ZooKeeper: no need to translate (keep the same capitalization)
-broker, bookie, proxy: no need to translate (keep the same capitalization)
-topic, producer, consumer: translate to “主题”, “生产者”, “消费者”.
-
-More details about Pulsar TB, see [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC). Welcome to add and modify terms in this document.
-
-
-### 2. Add space between Chinese and English characters and numbers
-
-
-In order to improve the readability of Chinese and English mixed documents, you should add spaces between Chinese and English characters and numbers.
-
-
-- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
-
-- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
-
-> ####Note
-> You don’t need to add spaces behind Chinese punctuations, even if they are followed by English words.
-
-### 3. Chinese punctuation
-
-
-Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
-
-Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
-
- 
-
-
-This example use (。) at the end of each practice.
-
-### 4.Translate “you“ to “你“
-
-To unify the language style, you’d better omit "you". If it is necessary, you can translate it into “你“.
-
-### 5. Comments in the sample code
-
-You’d better translate comments in the sample code. If the comment is simple, you can omit it.
-
-### 6. The liberal translation is better than the literal translation
-
-You’d better not translate word by word. After translating, please check out your words and pay attention to the accuracy and brevity. Based on your full understanding of the source text, you can adopt the liberal translation method. Sometimes, you can omit the translation of quantifier, auxiliary, subject and so on to keep the sentence easy to read.
-
-#### 6.1 ...的...的...的...
-
-You can omit ” ’s “ to make the text easy to read. Here are some examples :
-
-- Pulsar’s documentation is located in the docs folder in Pulsar’s source code repository.
-
-If you translate all the “的”, it can’t read smoothly:
-
-- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
-
-Deleting the unnecessary “的” seems better:
-
-- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
-
-#### 6.2 一个……
-
-
-When you translate English into Chinese, you don’t need to translate all the plural; you don’t need to translate ”a” or ”an”. Here are some examples :
-
-
-- Using a Pulsar client with the proxy
-
-Translate “a” into “一个” :
-
-- 使用有 proxy 的一个 Pulsar 客户端 ❌
-
-Deleting the redundant ”一个“ makes the text more concise.
-
-- 使用有 proxy 的 Pulsar 客户端 ✅
-
-### 7. Use passive tense as little as possible
-
-
-You don’t need to use “被” in translation. For example :
-
- - source : Once the message above is successfully published to the topic, you can see it in the standard output: Hello Pulsar.
- - original : 一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它 : Hello Pulsar”。 ❌
- - adjusted : 上面的消息成功发布到主题后，你会在标准输出中看到 : Hello Pulsar。 ✅
-
-### 8. Simple future tense
-You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
-
-- This will publish a single message to the Pulsar topic.
-- original : 这将向Pulsar的Topic发送单条消息。 ❌
-- adjusted : （......）给 Pulsar 主题发布一条信息。 ✅
-
-### 9. Examples
-You can adjust your words according to the context when you translate “Here’s sth”. For example:
-
-- Here's an example.
-- original : 这里有一个示例。 ❌
-- adjusted : 下面是一个示例。 ✅
-
-### 10. Keep your words easy to read
-Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
-
-## Add you as a contributor
-When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
-
-
[pulsar-translation] 14/25: Create LICENSE
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 57bbd89bc5fbe619170d791ea3a944995b72fba5
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Wed Aug 14 22:25:13 2019 +0800
Create LICENSE
---
LICENSE | 201 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 201 insertions(+)
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..261eeb9
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
[pulsar-translation] 17/25: Add workflow_guidelines
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 9f8e4a95fa766e8eedd7d408fb529d324b788f85
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 15 15:17:34 2019 +0800
Add workflow_guidelines
add workflow_guidelines
---
workflow_guidelines.md | 176 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 176 insertions(+)
diff --git a/workflow_guidelines.md b/workflow_guidelines.md
new file mode 100644
index 0000000..5d5ed0f
--- /dev/null
+++ b/workflow_guidelines.md
@@ -0,0 +1,176 @@
+# Translation workflow and guidelines
+
+Welcome to join the Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
+
+## Workflow
+
+You can find [Apache Pulsar translation project](https://crowdin.com/project/apache-pulsar) on Crowdin. For further details about the functions of Crowdin, see [Crowdin](https://crowdin.com/).
+Here are the steps of the translation workflow:
+
+### Join the Pulsar translation project
+1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
+
+
+2. After signing in, click **Join** at the upper right corner on the crowdin page.
+> #### Note
+> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
+> Select a language. Take the **Simplified Chinese Translation Project** as an example.
+
+
+### Choose a file to translate and submit a PR
+1. Click **Simplified Chinese Translation Project**.
+2. Click **master > docs**, and check out the status of each file.
+Files in **master > docs** are the source files of the latest versions on Pulsar official website. You only need to translate these markdown files.
+
+
+- Green: translated and approved
+- Blue: translated but not approved
+- Grey: not translated
+
+
+
+Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
+
+After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
+
+### Label Setting
+- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
+- Assignees : Choose yourself to receive notifications.
+- Label : Choose “translation”.
+
+### Translating
+While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
+> ####mportant
+> Don’t modify, omit or add a space in a tag, as the omission or relocation of a tag leads to mistakes shown on the website.
+
+
+
+You can modify and save the content directly. Your version will appear automatically at the top of the translation list, as Crowdin will record different versions from different translators. **TM AND MT TRANSLATION** in the bottom-right corner offers you TMs in Pulsar, Crowdin, and other websites.
+
+
+
+> #### Tip
+> You can use and update [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC) while translating.
+
+### Review
+After finishing a translation, please leave a comment in your PR. :
+For example, I've finished the translation, could you help review?
+
+After receiving the comment, reviewers start to review. The reviewer can make simple comments and notify the translator. Direct discussion in PR is encouraged.
+
+If there are no problems, the reviewer will approve this PR and merge it.
+
+The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
+Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
+
+
+
+## Guidelines
+Here are some common problems during translation. This guideline provides some advice. Please read and follow this guideline carefully before start translation. This could help improve the quality of Pulsar translation files and unify the translation style.
+
+
+### 1. Terms
+
+-Pulsar, Pulsar Functions, BookKeeper, ZooKeeper: no need to translate (keep the same capitalization)
+-broker, bookie, proxy: no need to translate (keep the same capitalization)
+-topic, producer, consumer: translate to “主题”, “生产者”, “消费者”.
+
+More details about Pulsar TB, see [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC). Welcome to add and modify terms in this document.
+
+
+### 2. Add space between Chinese and English characters and numbers
+
+
+In order to improve the readability of Chinese and English mixed documents, you should add spaces between Chinese and English characters and numbers.
+
+
+- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
+
+- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
+
+> ####Note
+> You don’t need to add spaces behind Chinese punctuations, even if they are followed by English words.
+
+### 3. Chinese punctuation
+
+
+Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
+
+Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
+
+ 
+
+
+This example use (。) at the end of each practice.
+
+### 4.Translate “you“ to “你“
+
+To unify the language style, you’d better omit "you". If it is necessary, you can translate it into “你“.
+
+### 5. Comments in the sample code
+
+You’d better translate comments in the sample code. If the comment is simple, you can omit it.
+
+### 6. The liberal translation is better than the literal translation
+
+You’d better not translate word by word. After translating, please check out your words and pay attention to the accuracy and brevity. Based on your full understanding of the source text, you can adopt the liberal translation method. Sometimes, you can omit the translation of quantifier, auxiliary, subject and so on to keep the sentence easy to read.
+
+#### 6.1 ...的...的...的...
+
+You can omit ” ’s “ to make the text easy to read. Here are some examples :
+
+- Pulsar’s documentation is located in the docs folder in Pulsar’s source code repository.
+
+If you translate all the “的”, it can’t read smoothly:
+
+- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
+
+Deleting the unnecessary “的” seems better:
+
+- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
+
+#### 6.2 一个……
+
+
+When you translate English into Chinese, you don’t need to translate all the plural; you don’t need to translate ”a” or ”an”. Here are some examples :
+
+
+- Using a Pulsar client with the proxy
+
+Translate “a” into “一个” :
+
+- 使用有 proxy 的一个 Pulsar 客户端 ❌
+
+Deleting the redundant ”一个“ makes the text more concise.
+
+- 使用有 proxy 的 Pulsar 客户端 ✅
+
+### 7. Use passive tense as little as possible
+
+
+You don’t need to use “被” in translation. For example :
+
+ - source : Once the message above is successfully published to the topic, you can see it in the standard output: Hello Pulsar.
+ - original : 一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它 : Hello Pulsar”。 ❌
+ - adjusted : 上面的消息成功发布到主题后，你会在标准输出中看到 : Hello Pulsar。 ✅
+
+### 8. Simple future tense
+You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
+
+- This will publish a single message to the Pulsar topic.
+- original : 这将向Pulsar的Topic发送单条消息。 ❌
+- adjusted : （......）给 Pulsar 主题发布一条信息。 ✅
+
+### 9. Examples
+You can adjust your words according to the context when you translate “Here’s sth”. For example:
+
+- Here's an example.
+- original : 这里有一个示例。 ❌
+- adjusted : 下面是一个示例。 ✅
+
+### 10. Keep your words easy to read
+Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
+
+## Add you as a contributor
+When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
+
[pulsar-translation] 01/25: Add some initial files,
and will improve them soon
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 2f4661cfab51a7b177ed37cc9d01602911f91fc0
Author: Jinfeng Huang <hj...@streamnative.io>
AuthorDate: Mon Jul 22 09:47:13 2019 +0800
Add some initial files, and will improve them soon
---
.github/ISSUE_TEMPLATE.md | 14 +++
.github/ISSUE_TEMPLATE/bug_report.md | 30 ++++++
.github/ISSUE_TEMPLATE/feature_request.md | 20 ++++
.github/PULL_REQUEST_TEMPLATE.md | 48 +++++++++
CONTRIBUTING.md | 104 +++++++++++++++++++
CONTRIBUTORS.md | 13 +++
README.md | 161 ++++++++++++++++++++++++++++++
media/example-comma.jpg | Bin 0 -> 370095 bytes
media/id-tag.jpg | Bin 0 -> 216164 bytes
media/translation-interface.jpg | Bin 0 -> 882284 bytes
media/translation-status.jpg | Bin 0 -> 254840 bytes
media/translation-workflow.jpg | Bin 0 -> 51785 bytes
schedule.md | 14 +++
13 files changed, 404 insertions(+)
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000..00c4b58
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,14 @@
+#### Expected behavior
+
+Tell us what should happen
+
+#### Actual behavior
+
+Tell us what happens instead
+
+#### Steps to reproduce
+
+How can we reproduce the issue
+
+#### System configuration
+**Pulsar version**: x.y
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..b9be206
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: type/bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+
+**Additional context**
+Add any other context about the problem here.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..5b8022c
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: type/feature
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..85285cc
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,48 @@
+<--
+### Contribution Checklist
+
+ - Name the pull request in the form "[Issue XYZ][component] Title of the pull request", where *XYZ* should be replaced by the actual issue number.
+ Skip *Issue XYZ* if there is no associated github issue for this pull request.
+ Skip *component* if you are unsure about which is the best component. E.g. `[docs] Fix typo in produce method`.
+
+ - Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
+
+ - Each pull request should address only one issue, not mix up code from multiple issues.
+
+ - Each commit in the pull request has a meaningful commit message
+
+ - Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
+
+**(The sections below can be removed for hotfixes of typos)**
+-->
+
+*(If this PR fixes a github issue, please add `Fixes #<xyz>`.)*
+
+Fixes #<xyz>
+
+*(or if this PR is one task of a github issue, please add `Master Issue: #<xyz>` to link to the master issue.)*
+
+Master Issue: #<xyz>
+
+### Motivation
+
+*Explain here the context, and why you're making that change. What is the problem you're trying to solve.*
+
+### Modifications
+
+*Describe the modifications you've done.*
+
+### Verify this change
+
+- [ ] Make sure that the change is correct.
+- For how to check and verify, refer to [Translation and localization](https://github.com/apache/pulsar/tree/master/site2#translation-and-localization).
+
+
+### Documentation
+
+ - Is this pull request related to crowdin usage? (yes / no)
+ - Is this pull request related to translation quality? (yes / no)
+ - If yes, how to improve?
+ - Is this pull request related to translation guidelines?(yes / no)
+ - Is this pull request related to translation workflow?(yes / no)
+ - If a sth is not documented yet in this PR, please create a followup issue for adding the documentation.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..e087a98
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,104 @@
+# Making contributions
+
+## Markdown
+All files in the pulsar-translation repository are written in [Markdown](https://www.markdownguide.org/). If you do not know how to use Markdown, learn how to [get started](https://www.markdownguide.org/getting-started).
+
+
+## Workflow
+
+### Step 1: Fork
+
+1. Visit https://github.com/apache/pulsar-translation
+2. Click `Fork` button (top right) to establish a cloud-based fork.
+
+### Step 2: Clone fork to local machine
+
+Create your clone.
+
+```sh
+$ cd $working_dir
+$ git clone https://github.com/$user/pulsar-translation
+```
+
+Set your clone to track upstream repository.
+
+```sh
+$ cd $working_dir/pulsar-translation
+$ git remote add upstream https://github.com/apache/pulsar-translation.git
+```
+
+Use the `git remote -v` command, you find the output looks as follows:
+
+```
+origin https://github.com/$user/pulsar-translation.git (fetch)
+origin https://github.com/$user/pulsar-translation.git (push)
+upstream https://github.com/apache/pulsar-translation (fetch)
+upstream https://github.com/apache/pulsar-translation (push)
+```
+
+### Step 3: Keep your branch in sync
+
+Get your local master up to date.
+
+```sh
+$ cd $working_dir/pulsar-translation
+$ git checkout master
+$ git fetch upstream
+$ git rebase upstream/master
+$ git push origin master
+```
+
+### Step 4: Create your branch
+
+Branch from master.
+
+```sh
+$ git checkout -b myfeature
+```
+
+### Step 5: Edit the code
+
+You can now edit the code on the `myfeature` branch.
+
+
+### Step 6: Commit
+
+Commit your changes.
+
+```sh
+$ git add <filename>
+$ git commit -m "$add a comment"
+```
+
+Likely you'll go back and edit-build-test in a few cycles.
+
+The following commands might be helpful for you.
+
+```sh
+$ git add <filename> (used to add one file)
+git add -A (add all changes, including new/delete/modified files)
+git add -a -m "$add a comment" (add and commit modified and deleted files)
+git add -u (add modified and deleted files, not include new files)
+git add . (add new and modified files, not including deleted files)
+```
+
+### Step 7: Push
+
+When your commit is ready for review (or just to establish an offsite backup of your work), push your branch to your fork on `github.com`:
+
+```sh
+$ git push origin myfeature
+```
+
+### Step 8: Create a pull request
+
+1. Visit your fork at https://github.com/$user/pulsar-translation (replace `$user` obviously).
+2. Click the `Compare & pull request` button next to your `myfeature` branch.
+
+### Step 9: Get a code review
+
+Once you open your pull request, at least two reviewers will participate in reviewing. Those reviewers will conduct a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and style.
+
+Commit changes made in response to review comments to the same branch on your fork.
+
+Very small PRs are easy to review. Very large PRs are very difficult to review.
diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
new file mode 100644
index 0000000..25800ea
--- /dev/null
+++ b/CONTRIBUTORS.md
@@ -0,0 +1,13 @@
+# Contributors
+
+- Bu Xing (https://github.com/xingbu110)
+- Francis Du (https://github.com/francis-du)
+- Jennifer Huang (https://github.com/Jennifer88huang)
+- Jia Zhai (https://github.com/jiazhai)
+- Lei Yang ()
+- Sijie Guo (https://github.com/sijie)
+- Susan (https://github.com/Ssssssusan)
+- Tianci Gao (https://github.com/bilahepan)
+- Tuten (https://github.com/tuteng)
+- Yiming Li ()
+- Ying Zhan (https://github.com/Monica-zy)
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..31bd3d3
--- /dev/null
+++ b/README.md
@@ -0,0 +1,161 @@
+# Translation workflow and guidelines
+
+Welcome to join Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
+
+## Workflow
+Pulsar 的翻译项目放在 [Apache Pulsar Crowdin](https://crowdin.com/project/apache-pulsar) 上。想进一步了解 Crowdin 功能，参阅 [Crowdin 网站](https://crowdin.com/) 。
+我们的翻译流程主要有以下几步。
+
+### 注册 Crowdin 账号，加入 Pulsar 翻译项目组
+登录 [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar) 页面。如果没有 Crowdin 账户，点击右上角 **SIGN UP**，输入个人信息创建账户。如果你已经有 Github、Facebook，Google，Twitter，Gitlab 账号，直接在注册页面关联以上任意账号即可。
+
+登录成功后，在右上角选择 **Join（加入）**。
+> 注意
+> Pulsar 的源文件为英文，翻译项目分为中文、法语和日语。
+> 选择翻译目标语言，点击进入浏览。本文以“简体中文翻译项目”为例。
+
+### 选择翻译文件，提 PR
+点开“简体中文翻译项目”，进入 **master > docs** 目录中，查看每个文件的翻译进度。 **master > docs** 目录中的文件是 Pulsar 官网最新版本的源文件，只需要翻译这个目录中的 markdown 文件即可。其中：
+
+- 绿色：翻译并通过审阅
+- 蓝色：翻译未审阅
+- 灰色：未翻译
+
+
+
+根据自己对 Pulsar 及相关技术的理解，优先选择自己熟悉、尚未翻译的内容进行翻译。
+
+选择要翻译的文件后，查看 [Translation schedule](https://github.com/streamnative/translation-guidelines/schedule) 中是否有其他人在翻译这个文件。如果已经有，可以重新选择；如果没有，参考 [PR 模版](https://github.com/streamnative/translation-guidelines/blob/master/.github/PULL_REQUEST_TEMPLATE.md)，把自己要翻译的文件和姓名分别添加进 [Translation schedule](https://github.com/streamnative/translation-guidelines/schedule)，提交 PR。
+
+### 打标签
+- Reviewers：无需设置，负责人会自动收到您提交的 PR 申请，会安排人员处理。
+- Assignees：选择您自己，方便你后续收到进度通知。
+- Label：选择 `translation`。
+
+### 翻译
+译者开始翻译。在打开的翻译界面，文件 id 不需要翻译。翻译中的 tag 和源文件保持一致。
+> **重要
+> 一定不要修改、遗漏 tag，或者在 tag 后面加空格。tag 遗漏或错位会造成中文网站内容显示错乱。**
+
+
+
+如果看到有翻译需要修改的地方，直接在翻译界面修改、保存。你的翻译结果会自动出现在翻译列表的最上方，Crowdin 会自动记载不同译者的翻译版本。右下方的 **TM AND MT TRANSLATION** 中会提供 Pulsar、Crowdin 和网站上其他的术语库，翻译时可供参考。
+
+
+
+翻译过程中，如需参考或者追加 Pulsar 文档术语库，可以使用 [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC)。
+
+### 审阅
+翻译完成后，在您提交的 PR 页面留言告知：
+“I've finished translation, could you please help review?”
+
+Reviewer 收到通知后，开始审阅翻译内容。审阅完成后，在 PR 中告知译者，并做简单点评反馈。如有需要讨论的地方，可以直接在 PR 中交流讨论。
+
+审阅无误后，reviewer approve 该 PR，并 merge。
+
+The following image gives a general workflow. The workflow source file is shared at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
+Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
+
+
+## Guidelines ##
+本规范主要列出了一些常见的翻译问题，并提供了一些指导意见和建议。开始翻译前，请认真阅读并尽量遵守本文的规范，这能有效提高 Pulsar 翻译文件质量，统一翻译风格。
+
+### 1. 专有名词
+
+涉及到 Pulsar、Pulsar Functions、BookKeeper、ZooKeeper，按照上述大小写格式，保留英文不翻译。
+涉及到 broker，bookie，proxy 等，在句中保持英文小写形式，不用翻译。
+涉及到 topic，producer，consumer 等，翻译成“主题”，“生产者”，“消费者”。
+
+更多有关 Pulsar 文档术语库，参考 [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC)。欢迎在这个文档补充和修改术语库。
+
+### 2. 汉字与英文、数字之间需空格
+
+汉字与英文或数字之间以空格隔开，以增强中英文混排的美观性和可读性。
+
+- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
+
+- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
+
+**注意：**中文标点符号前后不需要跟空格，即使前后挨着的是英文单词。
+
+### 3. 中文标点符号
+
+中文里面请使用中文标点符号。英文中没有顿号，应该使用顿号的地方在英文中一般使用的是逗号，在翻译时应注意将其翻译为顿号。比如 “Kubernetes, Mesos, Docker“ 应该翻译成 “Kubernetes、Mesos、Docker“。
+
+在涉及到多个 items 时，如果是短语，后面用分号（；）结束，最后一个 item 以句号（。）结尾。
+
+如果每个 item 是个句子，或者已经使用过分号（；），每个 item 以句号结尾。
+
+ 
+
+上面这个例子中，使用句号（。）给每条实践结尾。
+
+### 4. “you“翻译为“你“
+
+为了风格统一，在翻译“you”时，可以省略时，尽量省略不用；必须使用时，用“你”，而不是“您”。
+
+### 5. 示例代码及注释
+
+示例代码中的注释最好能够翻译，当然也可以不翻译（当注释很简单时）。
+
+### 6. 意译优于直译
+
+翻译时尽量避免翻译腔，即把原文一字不漏地、逐句翻译出来。这样并不代表翻译更准确，有时候读着会很别扭。翻译完后，自己多读几遍，看看是否符合原意、是否绕口、是否简洁。在充分理解原文的基础上，可以适当采用意译的方式来翻译。有时候为了简化句子，有些数量词、助词、主语都可以省略。
+
+#### 6.1 ...的...的...的...
+
+比如英文中经常会用 ‘s 来表达从属关系，一字不落地都将其翻译成 “的“ 会有翻译腔。在中文里面有些 “的“ 完全可以去掉，不会影响表达的意思，还能简洁很多，看下面的例子。
+
+- Pulsar‘s documentation is located in the docs folder in Pulsar’s source code repository.
+
+当然，你可以将“的“字都翻译出来，但是读起来很不顺畅：
+
+- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
+
+去掉不必要的“的“字，就会简洁很多：
+
+- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
+
+#### 6.2 一个……
+
+英文一般比较严谨，当代表多个时，会使用复数名字，在翻译成中文时，一般不需要刻意把这些复数翻译出来。
+
+在英文里，当单数为可数名词时，前面一般会有 ”a“ 或 ”an“；中文中，我们一般不需要把”一个...“翻译出来。比如下面这个例子：
+
+- Using a Pulsar client with the proxy
+
+我们可以把”a“翻译成”一个“：
+
+- 使用有 proxy 的一个 Pulsar 客户端 ❌
+
+虽然看起来没什么问题，但是这里的”一个“是多余的，去掉之后不但不会影响翻译效果，而且更加简洁。
+
+- 使用有 proxy 的 Pulsar 客户端 ✅
+
+### 7. 尽量少用被动句
+
+英文文档中，有时以物为主语，中文翻译过程中，不需要把”被“字翻译出来。例如：
+
+ - 英文：Once the message above has been successfully published to the topic, you should see it in the standard output: Hello Pulsar.
+ - 原翻译：一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它：Hello Pulsar”。 ❌
+ - 翻译调整：上面的消息成功发布到主题后，你会在标准输出中看到: Hello Pulsar。 ✅
+
+### 8. Will 将来时态
+英文中有“will”时，不用翻译成“将要......”，直接转化成一般现在时翻译就行。例如：
+
+- This will publish a single message to the Pulsar topic.
+- 原翻译：这将向Pulsar的Topic发送单条消息。 ❌
+- 翻译调整：（......）给 Pulsar 主题发布一条信息。 ✅
+
+### 9. 示例
+在英文中遇到 “Here‘s sth”，根据上下文语境做调整。例如：
+
+- Here's an example.
+- 原翻译：这里有一个示例。 ❌
+- 翻译调整：下面是一个示例。 ✅
+
+### 10. 语言简洁、流畅
+语言尽量简单、通顺，翻译完后，读一遍，适合中国人的阅读习惯。英语中有时会用从句，翻译中文时，尽量拆成几个简单的句子。
+
+## Join contributors
+When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/streamnative/translation-guidelines/blob/master/CONTRIBUTORS.md).
diff --git a/media/example-comma.jpg b/media/example-comma.jpg
new file mode 100644
index 0000000..5f0afe3
Binary files /dev/null and b/media/example-comma.jpg differ
diff --git a/media/id-tag.jpg b/media/id-tag.jpg
new file mode 100644
index 0000000..362fda0
Binary files /dev/null and b/media/id-tag.jpg differ
diff --git a/media/translation-interface.jpg b/media/translation-interface.jpg
new file mode 100644
index 0000000..a326879
Binary files /dev/null and b/media/translation-interface.jpg differ
diff --git a/media/translation-status.jpg b/media/translation-status.jpg
new file mode 100644
index 0000000..3632f2d
Binary files /dev/null and b/media/translation-status.jpg differ
diff --git a/media/translation-workflow.jpg b/media/translation-workflow.jpg
new file mode 100644
index 0000000..e43eb4c
Binary files /dev/null and b/media/translation-workflow.jpg differ
diff --git a/schedule.md b/schedule.md
new file mode 100644
index 0000000..f96f9fe
--- /dev/null
+++ b/schedule.md
@@ -0,0 +1,14 @@
+# Translation schedule
+
+
+Topic | Translator | Reviever | Status
+:-----|:-----------|:---------|:------
+admin-api-partitioned-topics | Tianci Gao | Jennifer Huang | Approved
+administration-proxy | Tianci Gao | Jennifer Huang | Approved
+admin api non persistent | liyiming2002 | | Translated
+admin api permission | liyiming 2002 | | Translated
+cookbooks-partitioned | Tianci Gao |Jennifer Huang | Approved
+cookbooks-message-queue | Ying Zhan | Susan | Approved
+
+
+
[pulsar-translation] 23/25: Update workflow_guidelines.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit dcfdc35bcf337a17d5bfbf5649641c702a7365ce
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Tue Aug 27 11:23:53 2019 +0800
Update workflow_guidelines.md
Co-Authored-By: Anonymitaet <50...@users.noreply.github.com>
---
workflow_guidelines.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/workflow_guidelines.md b/workflow_guidelines.md
index af670e8..e247ddc 100644
--- a/workflow_guidelines.md
+++ b/workflow_guidelines.md
@@ -8,7 +8,7 @@ You can find [Apache Pulsar translation project](https://crowdin.com/project/apa
Here are the steps of the translation workflow:
### Join the Pulsar translation project
-1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
+1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter, or Gitlab account, you can link any of them to sign in.
2. After signing in, click **Join** at the upper right corner on the crowdin page.
[pulsar-translation] 18/25: Merge pull request #1 from
ireneontheway/ireneontheway-patch-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit e8aaee9504635a560c91945298e14a6ab3c1075d
Merge: c3759d7 9f8e4a9
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 15 16:50:37 2019 +0800
Merge pull request #1 from ireneontheway/ireneontheway-patch-1
Add workflow_guidelines
workflow_guidelines.md | 176 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 176 insertions(+)
[pulsar-translation] 08/25: Merge pull request #2 from
Ssssssusan/Ssssssusan-patch-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 4af257c3a612b1af1882f60d4febf0e359c194e6
Merge: 7102c0c 48cbac8
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:46:45 2019 +0800
Merge pull request #2 from Ssssssusan/Ssssssusan-patch-1
Update schedule.md
schedule.md | 37 ++++++++++++++++---------------------
1 file changed, 16 insertions(+), 21 deletions(-)
[pulsar-translation] 19/25: Add translation workflow guidlines
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit f74782e6e0c842d2ce1543b57641dd833948c9c0
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 22 11:15:15 2019 +0800
Add translation workflow guidlines
---
translation_workflow.md | 177 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 177 insertions(+)
diff --git a/translation_workflow.md b/translation_workflow.md
new file mode 100644
index 0000000..af670e8
--- /dev/null
+++ b/translation_workflow.md
@@ -0,0 +1,177 @@
+# Translation workflow and guidelines
+
+Welcome to join the Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
+
+## Workflow
+
+You can find [Apache Pulsar translation project](https://crowdin.com/project/apache-pulsar) on Crowdin. For further details about the functions of Crowdin, see [Crowdin](https://crowdin.com/).
+Here are the steps of the translation workflow:
+
+### Join the Pulsar translation project
+1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
+
+
+2. After signing in, click **Join** at the upper right corner on the crowdin page.
+> #### Note
+> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
+> Select a language. Take the **Simplified Chinese Translation Project** as an example.
+
+
+### Choose a file to translate and submit a PR
+1. Click **Simplified Chinese Translation Project**.
+2. Click **master > docs**, and check out the status of each file.
+Files in **master > docs** are the source files of the latest versions on Pulsar official website. You only need to translate these markdown files.
+
+
+- Green: translated and approved
+- Blue: translated but not approved
+- Grey: not translated
+
+
+
+Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
+
+After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
+
+### Label Setting
+- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
+- Assignees : Choose yourself to receive notifications.
+- Label : Choose “translation”.
+
+### Translating
+While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
+> ####mportant
+> Don’t modify, omit or add a space in a tag, as the omission or relocation of a tag leads to mistakes shown on the website.
+
+
+
+You can modify and save the content directly. Your version will appear automatically at the top of the translation list, as Crowdin will record different versions from different translators. **TM AND MT TRANSLATION** in the bottom-right corner offers you TMs in Pulsar, Crowdin, and other websites.
+
+
+
+> #### Tip
+> You can use and update [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC) while translating.
+
+### Review
+After finishing a translation, please leave a comment in your PR. :
+For example, I've finished the translation, could you help review?
+
+After receiving the comment, reviewers start to review. The reviewer can make simple comments and notify the translator. Direct discussion in PR is encouraged.
+
+If there are no problems, the reviewer will approve this PR and merge it.
+
+The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
+Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
+
+
+
+## Guidelines
+Here are some common problems during translation. This guideline provides some advice. Please read and follow this guideline carefully before start translation. This could help improve the quality of Pulsar translation files and unify the translation style.
+
+
+### 1. Terms
+
+Pulsar, Pulsar Functions, BookKeeper, ZooKeeper: no need to translate (keep the same capitalization)
+broker, bookie, proxy: no need to translate (keep the same capitalization)
+topic, producer, consumer: translate to “主题”, “生产者”, “消费者”.
+
+More details about Pulsar TB, see [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC). Welcome to add and modify terms in this document.
+
+
+### 2. Add space between Chinese and English characters and numbers
+
+
+In order to improve the readability of Chinese and English mixed documents, you should add spaces between Chinese and English characters and numbers.
+
+
+- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
+
+- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
+
+> ####Note
+> You don’t need to add spaces behind Chinese punctuations, even if they are followed by English words.
+
+### 3. Chinese punctuation
+
+
+Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
+
+Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
+
+ 
+
+
+This example use (。) at the end of each practice.
+
+### 4.Translate “you“ to “你“
+
+To unify the language style, you’d better omit "you". If it is necessary, you can translate it into “你“.
+
+### 5. Comments in the sample code
+
+You’d better translate comments in the sample code. If the comment is simple, you can omit it.
+
+### 6. The liberal translation is better than the literal translation
+
+You’d better not translate word by word. After translating, please check out your words and pay attention to the accuracy and brevity. Based on your full understanding of the source text, you can adopt the liberal translation method. Sometimes, you can omit the translation of quantifier, auxiliary, subject and so on to keep the sentence easy to read.
+
+#### 6.1 ...的...的...的...
+
+You can omit ” ’s “ to make the text easy to read. Here are some examples :
+
+- Pulsar’s documentation is located in the docs folder in Pulsar’s source code repository.
+
+If you translate all the “的”, it can’t read smoothly:
+
+- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
+
+Deleting the unnecessary “的” seems better:
+
+- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
+
+#### 6.2 一个……
+
+
+When you translate English into Chinese, you don’t need to translate all the plural; you don’t need to translate ”a” or ”an”. Here are some examples :
+
+
+- Using a Pulsar client with the proxy
+
+Translate “a” into “一个” :
+
+- 使用有 proxy 的一个 Pulsar 客户端 ❌
+
+Deleting the redundant ”一个“ makes the text more concise.
+
+- 使用有 proxy 的 Pulsar 客户端 ✅
+
+### 7. Use passive tense as little as possible
+
+
+You don’t need to use “被” in translation. For example :
+
+ - source : Once the message above is successfully published to the topic, you can see it in the standard output: Hello Pulsar.
+ - original : 一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它 : Hello Pulsar”。 ❌
+ - adjusted : 上面的消息成功发布到主题后，你会在标准输出中看到 : Hello Pulsar。 ✅
+
+### 8. Simple future tense
+You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
+
+- This will publish a single message to the Pulsar topic.
+- original : 这将向Pulsar的Topic发送单条消息。 ❌
+- adjusted : （......）给 Pulsar 主题发布一条信息。 ✅
+
+### 9. Examples
+You can adjust your words according to the context when you translate “Here’s sth”. For example:
+
+- Here's an example.
+- original : 这里有一个示例。 ❌
+- adjusted : 下面是一个示例。 ✅
+
+### 10. Keep your words easy to read
+Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
+
+## Add you as a contributor
+When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
+
+
[pulsar-translation] 02/25: update readme
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit c3759d7a917b5190b3bc570efd58d40dfe6cd1f0
Author: Jinfeng Huang <hj...@streamnative.io>
AuthorDate: Mon Jul 22 09:55:07 2019 +0800
update readme
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 31bd3d3..d2b5fa5 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ Pulsar 的翻译项目放在 [Apache Pulsar Crowdin](https://crowdin.com/project
根据自己对 Pulsar 及相关技术的理解，优先选择自己熟悉、尚未翻译的内容进行翻译。
-选择要翻译的文件后，查看 [Translation schedule](https://github.com/streamnative/translation-guidelines/schedule) 中是否有其他人在翻译这个文件。如果已经有，可以重新选择；如果没有，参考 [PR 模版](https://github.com/streamnative/translation-guidelines/blob/master/.github/PULL_REQUEST_TEMPLATE.md)，把自己要翻译的文件和姓名分别添加进 [Translation schedule](https://github.com/streamnative/translation-guidelines/schedule)，提交 PR。
+选择要翻译的文件后，查看 [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md) 中是否有其他人在翻译这个文件。如果已经有，可以重新选择；如果没有，创建一个 PR，把自己要翻译的文件和姓名分别添加进 [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md)，提交 PR。
### 打标签
- Reviewers：无需设置，负责人会自动收到您提交的 PR 申请，会安排人员处理。
@@ -158,4 +158,4 @@ Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for
语言尽量简单、通顺，翻译完后，读一遍，适合中国人的阅读习惯。英语中有时会用从句，翻译中文时，尽量拆成几个简单的句子。
## Join contributors
-When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/streamnative/translation-guidelines/blob/master/CONTRIBUTORS.md).
+When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
[pulsar-translation] 04/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 7e2d7ab267269104602861433d4f09a4b60fcb79
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Mon Aug 5 20:49:10 2019 +0800
Update schedule.md
---
schedule.md | 6 ------
1 file changed, 6 deletions(-)
diff --git a/schedule.md b/schedule.md
index 2ef038c..f6bc82c 100644
--- a/schedule.md
+++ b/schedule.md
@@ -38,9 +38,3 @@ io-redis | Bu Xing | | In Progress
io-solr | Bu Xing | | In Progress
io-tcp | Bu Xing | | In Progress
task #26 #28 | 0 contributors
-
-
-Tutorial for Using Debezium Connectors With Apache Pulsar | Jennifer | Anonymitaet | Published
-When Flink & Pulsar Come Together | Susan | Sijie & Jennifer & Anonymitaet | Published
-Apache Pulsar Blackpaper | Yong & Susan & Qingying | Jennifer & Anonymitaet & Jia Zhai | TBD
-Getui Use Case | Qingying | | TBD
[pulsar-translation] 05/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 6ec9b2ceaca5ec9f942563bbd851aa364d3e471b
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 10:32:27 2019 +0800
Update schedule.md
---
schedule.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/schedule.md b/schedule.md
index f6bc82c..7e4707b 100644
--- a/schedule.md
+++ b/schedule.md
@@ -6,6 +6,7 @@ Topic | Translator | Reviewer | Status
admin api non persistent | liyiming2002 | | Translated
admin api permissions | liyiming 2002 | | Translated
admin-api-partitioned-topics | bilahepan (Tianci Gao) | Jennifer Huang | Approved
+administration-load-balance | bilahepan (Tianci Gao) | | In Progress
administration-proxy | bilahepan (Tianci Gao) | Jennifer Huang | Approved
admin-load-distribution | bilahepan (Tianci Gao) | | In Progress
client-libraries-cpp | liyiming2002 | | In Progress
@@ -17,12 +18,16 @@ client-libraries-python | liyiming2002 | | Translated
client-libraries-websocket | Francis Du | | Translated
client-libraries-websocket | liyiming2002 | | Translated
concepts-messaging | liyiming 2002 | | Translated
+cookbooks-bookkeepermetadata | bilahepan (Tianci Gao) | | In Progress
+cookbooks-deduplication | bilahepan (Tianci Gao) | | In Progress
+cookbooks-message-queue | bilahepan (Tianci Gao) | | In Progress
cookbooks-message-queue | Ying Zhan | Susan | Approved
cookbooks-message-queue | Ying Zhan | Susan97 | Approved
cookbooks-partitioned | bilahepan (Tianci Gao) |Jennifer Huang | Approved
cookbooks-retention-expiry | bilahepan (Tianci Gao) | | Translated
deploy-bare-metal | bilahepan (Tianci Gao) | | Translated
deploy-kubernetes | KarenGirl | | In Progress
+deploy-monitoring | bilahepan (Tianci Gao) | | In Progress
developing tools | Susan97 | | In Progress
functions-api | Luke (ete0918) | | In Progress
functions-deploying | Luke (ete0918) | | In Progress
@@ -37,4 +42,5 @@ io-rabbitmq | Bu Xing | | In Progress
io-redis | Bu Xing | | In Progress
io-solr | Bu Xing | | In Progress
io-tcp | Bu Xing | | In Progress
-task #26 #28 | 0 contributors
+security-extending | bilahepan (Tianci Gao) | | In Progress
+task #26 | 0 contributors
[pulsar-translation] 03/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit a6915f90045bcfdba6d97bd467abbdd623421d33
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Thu Aug 1 05:07:04 2019 +0800
Update schedule.md
---
schedule.md | 44 ++++++++++++++++++++++++++++++++++++++------
1 file changed, 38 insertions(+), 6 deletions(-)
diff --git a/schedule.md b/schedule.md
index f96f9fe..2ef038c 100644
--- a/schedule.md
+++ b/schedule.md
@@ -1,14 +1,46 @@
# Translation schedule
-Topic | Translator | Reviever | Status
+Topic | Translator | Reviewer | Status
:-----|:-----------|:---------|:------
-admin-api-partitioned-topics | Tianci Gao | Jennifer Huang | Approved
-administration-proxy | Tianci Gao | Jennifer Huang | Approved
admin api non persistent | liyiming2002 | | Translated
-admin api permission | liyiming 2002 | | Translated
-cookbooks-partitioned | Tianci Gao |Jennifer Huang | Approved
+admin api permissions | liyiming 2002 | | Translated
+admin-api-partitioned-topics | bilahepan (Tianci Gao) | Jennifer Huang | Approved
+administration-proxy | bilahepan (Tianci Gao) | Jennifer Huang | Approved
+admin-load-distribution | bilahepan (Tianci Gao) | | In Progress
+client-libraries-cpp | liyiming2002 | | In Progress
+client-libraries-go | liyiming2002 | | In Progress
+client-libraries-java | liyiming2002 | | In Progress
+client-libraries-python | Bu Xing | | Translated
+client-libraries-python | Francis Du | | Translated
+client-libraries-python | liyiming2002 | | Translated
+client-libraries-websocket | Francis Du | | Translated
+client-libraries-websocket | liyiming2002 | | Translated
+concepts-messaging | liyiming 2002 | | Translated
cookbooks-message-queue | Ying Zhan | Susan | Approved
+cookbooks-message-queue | Ying Zhan | Susan97 | Approved
+cookbooks-partitioned | bilahepan (Tianci Gao) |Jennifer Huang | Approved
+cookbooks-retention-expiry | bilahepan (Tianci Gao) | | Translated
+deploy-bare-metal | bilahepan (Tianci Gao) | | Translated
+deploy-kubernetes | KarenGirl | | In Progress
+developing tools | Susan97 | | In Progress
+functions-api | Luke (ete0918) | | In Progress
+functions-deploying | Luke (ete0918) | | In Progress
+functions-gurantees | Susan97 | | In Progress
+functions-quickstart | KarenGirl | | In Progress
+io-file | Bu Xing | | In Progress
+io-hbase | Bu Xing | | In Progress
+io-hdfs | Bu Xing | | In Progress
+io-kafka | KarenGirl | | Translated
+io-netty | Bu Xing | | In Progress
+io-rabbitmq | Bu Xing | | In Progress
+io-redis | Bu Xing | | In Progress
+io-solr | Bu Xing | | In Progress
+io-tcp | Bu Xing | | In Progress
+task #26 #28 | 0 contributors
-
+Tutorial for Using Debezium Connectors With Apache Pulsar | Jennifer | Anonymitaet | Published
+When Flink & Pulsar Come Together | Susan | Sijie & Jennifer & Anonymitaet | Published
+Apache Pulsar Blackpaper | Yong & Susan & Qingying | Jennifer & Anonymitaet & Jia Zhai | TBD
+Getui Use Case | Qingying | | TBD
[pulsar-translation] 13/25: update personal address
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit f904073400c4820b3a79f3e45c769fe5c44e246b
Author: 杨磊 <ya...@ifeng.com>
AuthorDate: Wed Aug 14 14:27:09 2019 +0800
update personal address
---
CONTRIBUTORS.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
index 25800ea..e4cd728 100644
--- a/CONTRIBUTORS.md
+++ b/CONTRIBUTORS.md
@@ -4,7 +4,7 @@
- Francis Du (https://github.com/francis-du)
- Jennifer Huang (https://github.com/Jennifer88huang)
- Jia Zhai (https://github.com/jiazhai)
-- Lei Yang ()
+- Lei Yang (https://github.com/yangleimiao)
- Sijie Guo (https://github.com/sijie)
- Susan (https://github.com/Ssssssusan)
- Tianci Gao (https://github.com/bilahepan)
[pulsar-translation] 25/25: Merge pull request #6 from
ireneontheway/master
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit ad6fcfb7fa2bd73f3ea0ae8e72892561e32f059e
Merge: ae5064b bb6be63
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Thu Sep 5 10:47:55 2019 +0800
Merge pull request #6 from ireneontheway/master
Add workflow-guidelines
workflow_guidelines.md | 177 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 177 insertions(+)
[pulsar-translation] 09/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit eac59dc754d13c6155404ebed0234ad14c72a091
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:50:35 2019 +0800
Update schedule.md
---
schedule.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schedule.md b/schedule.md
index 37732c2..7bfb577 100644
--- a/schedule.md
+++ b/schedule.md
@@ -18,7 +18,7 @@ concepts-messaging | liyiming 2002 | | Translated
cookbooks-bookkeepermetadata | bilahepan(Tianci Gao) | | In Progress
cookbooks-deduplication | bilahepan(Tianci Gao) | | In Progress
cookbooks-message-queue | bilahepan(Tianci Gao) & Ying Zhan | Susan97 | Approved
-cookbooks-partitioned | bilahepan(Tianci Gao) |Jennifer Huang | Approved
+cookbooks-partitioned | bilahepan(Tianci Gao) | Jennifer Huang | Approved
cookbooks-retention-expiry | bilahepan(Tianci Gao) | | Translated
deploy-bare-metal | bilahepan(Tianci Gao) | | Translated
deploy-kubernetes | KarenGirl | | In Progress
[pulsar-translation] 11/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 0d0499848c9b578ddaacc4f70c53bf988b6660a1
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:57:23 2019 +0800
Update schedule.md
---
schedule.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/schedule.md b/schedule.md
index 7bfb577..c6b7035 100644
--- a/schedule.md
+++ b/schedule.md
@@ -1,5 +1,8 @@
# Translation schedule
+> Note
+> Status: In progress / Translated / Approved
+> When a topic is selected and translated by a translator, you can choose other topics.
Topic | Translator | Reviewer | Status
:-----|:-----------|:---------|:------
@@ -38,4 +41,3 @@ io-redis | Bu Xing | | In Progress
io-solr | Bu Xing | | In Progress
io-tcp | Bu Xing | | In Progress
security-extending | bilahepan(Tianci Gao) | | In Progress
-task #26 | 0 contributors
[pulsar-translation] 12/25: Merge pull request #1 from
Ssssssusan/patch-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 6e8073f9f648747731c1e008f1f70c83031020e5
Merge: c3759d7 0d04998
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:58:21 2019 +0800
Merge pull request #1 from Ssssssusan/patch-1
Update schedule.md
schedule.md | 47 ++++++++++++++++++++++++++++++++++++++---------
1 file changed, 38 insertions(+), 9 deletions(-)
[pulsar-translation] 16/25: Merge pull request #3 from
apache/add-license-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit ae5064bda9745d452da27ffbdd3194258d2c3005
Merge: a08f6aa 57bbd89
Author: Sijie Guo <si...@apache.org>
AuthorDate: Thu Aug 15 00:16:47 2019 +0800
Merge pull request #3 from apache/add-license-1
### Motivation
Add a license to a repository.
### Modifications
Add Apache License 2.0.
LICENSE | 201 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 201 insertions(+)
[pulsar-translation] 22/25: Add workflow-guidelines
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 681dfad39da376c1ad7b212694793de3bef9a389
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 22 11:29:23 2019 +0800
Add workflow-guidelines
Add workflow-guidelines
---
workflow_guidelines.md | 177 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 177 insertions(+)
diff --git a/workflow_guidelines.md b/workflow_guidelines.md
new file mode 100644
index 0000000..af670e8
--- /dev/null
+++ b/workflow_guidelines.md
@@ -0,0 +1,177 @@
+# Translation workflow and guidelines
+
+Welcome to join the Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
+
+## Workflow
+
+You can find [Apache Pulsar translation project](https://crowdin.com/project/apache-pulsar) on Crowdin. For further details about the functions of Crowdin, see [Crowdin](https://crowdin.com/).
+Here are the steps of the translation workflow:
+
+### Join the Pulsar translation project
+1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
+
+
+2. After signing in, click **Join** at the upper right corner on the crowdin page.
+> #### Note
+> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
+> Select a language. Take the **Simplified Chinese Translation Project** as an example.
+
+
+### Choose a file to translate and submit a PR
+1. Click **Simplified Chinese Translation Project**.
+2. Click **master > docs**, and check out the status of each file.
+Files in **master > docs** are the source files of the latest versions on Pulsar official website. You only need to translate these markdown files.
+
+
+- Green: translated and approved
+- Blue: translated but not approved
+- Grey: not translated
+
+
+
+Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
+
+After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
+
+### Label Setting
+- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
+- Assignees : Choose yourself to receive notifications.
+- Label : Choose “translation”.
+
+### Translating
+While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
+> ####mportant
+> Don’t modify, omit or add a space in a tag, as the omission or relocation of a tag leads to mistakes shown on the website.
+
+
+
+You can modify and save the content directly. Your version will appear automatically at the top of the translation list, as Crowdin will record different versions from different translators. **TM AND MT TRANSLATION** in the bottom-right corner offers you TMs in Pulsar, Crowdin, and other websites.
+
+
+
+> #### Tip
+> You can use and update [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC) while translating.
+
+### Review
+After finishing a translation, please leave a comment in your PR. :
+For example, I've finished the translation, could you help review?
+
+After receiving the comment, reviewers start to review. The reviewer can make simple comments and notify the translator. Direct discussion in PR is encouraged.
+
+If there are no problems, the reviewer will approve this PR and merge it.
+
+The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
+Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
+
+
+
+## Guidelines
+Here are some common problems during translation. This guideline provides some advice. Please read and follow this guideline carefully before start translation. This could help improve the quality of Pulsar translation files and unify the translation style.
+
+
+### 1. Terms
+
+Pulsar, Pulsar Functions, BookKeeper, ZooKeeper: no need to translate (keep the same capitalization)
+broker, bookie, proxy: no need to translate (keep the same capitalization)
+topic, producer, consumer: translate to “主题”, “生产者”, “消费者”.
+
+More details about Pulsar TB, see [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC). Welcome to add and modify terms in this document.
+
+
+### 2. Add space between Chinese and English characters and numbers
+
+
+In order to improve the readability of Chinese and English mixed documents, you should add spaces between Chinese and English characters and numbers.
+
+
+- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
+
+- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
+
+> ####Note
+> You don’t need to add spaces behind Chinese punctuations, even if they are followed by English words.
+
+### 3. Chinese punctuation
+
+
+Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
+
+Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
+
+ 
+
+
+This example use (。) at the end of each practice.
+
+### 4.Translate “you“ to “你“
+
+To unify the language style, you’d better omit "you". If it is necessary, you can translate it into “你“.
+
+### 5. Comments in the sample code
+
+You’d better translate comments in the sample code. If the comment is simple, you can omit it.
+
+### 6. The liberal translation is better than the literal translation
+
+You’d better not translate word by word. After translating, please check out your words and pay attention to the accuracy and brevity. Based on your full understanding of the source text, you can adopt the liberal translation method. Sometimes, you can omit the translation of quantifier, auxiliary, subject and so on to keep the sentence easy to read.
+
+#### 6.1 ...的...的...的...
+
+You can omit ” ’s “ to make the text easy to read. Here are some examples :
+
+- Pulsar’s documentation is located in the docs folder in Pulsar’s source code repository.
+
+If you translate all the “的”, it can’t read smoothly:
+
+- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
+
+Deleting the unnecessary “的” seems better:
+
+- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
+
+#### 6.2 一个……
+
+
+When you translate English into Chinese, you don’t need to translate all the plural; you don’t need to translate ”a” or ”an”. Here are some examples :
+
+
+- Using a Pulsar client with the proxy
+
+Translate “a” into “一个” :
+
+- 使用有 proxy 的一个 Pulsar 客户端 ❌
+
+Deleting the redundant ”一个“ makes the text more concise.
+
+- 使用有 proxy 的 Pulsar 客户端 ✅
+
+### 7. Use passive tense as little as possible
+
+
+You don’t need to use “被” in translation. For example :
+
+ - source : Once the message above is successfully published to the topic, you can see it in the standard output: Hello Pulsar.
+ - original : 一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它 : Hello Pulsar”。 ❌
+ - adjusted : 上面的消息成功发布到主题后，你会在标准输出中看到 : Hello Pulsar。 ✅
+
+### 8. Simple future tense
+You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
+
+- This will publish a single message to the Pulsar topic.
+- original : 这将向Pulsar的Topic发送单条消息。 ❌
+- adjusted : （......）给 Pulsar 主题发布一条信息。 ✅
+
+### 9. Examples
+You can adjust your words according to the context when you translate “Here’s sth”. For example:
+
+- Here's an example.
+- original : 这里有一个示例。 ❌
+- adjusted : 下面是一个示例。 ✅
+
+### 10. Keep your words easy to read
+Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
+
+## Add you as a contributor
+When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
+
+
[pulsar-translation] 10/25: Merge pull request #3 from
Ssssssusan/Ssssssusan-patch-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 473bdcfed3127db041d0a9125463cdd95eb8cab8
Merge: 4af257c eac59dc
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:50:58 2019 +0800
Merge pull request #3 from Ssssssusan/Ssssssusan-patch-1
Update schedule.md
schedule.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[pulsar-translation] 07/25: Update schedule.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 48cbac861a4eb680fca30357536513d7856a4425
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 11:46:05 2019 +0800
Update schedule.md
---
schedule.md | 37 ++++++++++++++++---------------------
1 file changed, 16 insertions(+), 21 deletions(-)
diff --git a/schedule.md b/schedule.md
index 7e4707b..37732c2 100644
--- a/schedule.md
+++ b/schedule.md
@@ -5,32 +5,27 @@ Topic | Translator | Reviewer | Status
:-----|:-----------|:---------|:------
admin api non persistent | liyiming2002 | | Translated
admin api permissions | liyiming 2002 | | Translated
-admin-api-partitioned-topics | bilahepan (Tianci Gao) | Jennifer Huang | Approved
-administration-load-balance | bilahepan (Tianci Gao) | | In Progress
-administration-proxy | bilahepan (Tianci Gao) | Jennifer Huang | Approved
-admin-load-distribution | bilahepan (Tianci Gao) | | In Progress
+admin-api-partitioned-topics | bilahepan(Tianci Gao) | Jennifer Huang | Approved
+administration-load-balance | bilahepan(Tianci Gao) | | In Progress
+administration-proxy | bilahepan(Tianci Gao) | Jennifer Huang | Approved
+admin-load-distribution | bilahepan(Tianci Gao) | | In Progress
client-libraries-cpp | liyiming2002 | | In Progress
client-libraries-go | liyiming2002 | | In Progress
client-libraries-java | liyiming2002 | | In Progress
-client-libraries-python | Bu Xing | | Translated
-client-libraries-python | Francis Du | | Translated
-client-libraries-python | liyiming2002 | | Translated
-client-libraries-websocket | Francis Du | | Translated
-client-libraries-websocket | liyiming2002 | | Translated
+client-libraries-python | Bu Xing & Francis Du & liyiming2002 | | Translated
+client-libraries-websocket | Francis Du & liyiming2002 | | Translated
concepts-messaging | liyiming 2002 | | Translated
-cookbooks-bookkeepermetadata | bilahepan (Tianci Gao) | | In Progress
-cookbooks-deduplication | bilahepan (Tianci Gao) | | In Progress
-cookbooks-message-queue | bilahepan (Tianci Gao) | | In Progress
-cookbooks-message-queue | Ying Zhan | Susan | Approved
-cookbooks-message-queue | Ying Zhan | Susan97 | Approved
-cookbooks-partitioned | bilahepan (Tianci Gao) |Jennifer Huang | Approved
-cookbooks-retention-expiry | bilahepan (Tianci Gao) | | Translated
-deploy-bare-metal | bilahepan (Tianci Gao) | | Translated
+cookbooks-bookkeepermetadata | bilahepan(Tianci Gao) | | In Progress
+cookbooks-deduplication | bilahepan(Tianci Gao) | | In Progress
+cookbooks-message-queue | bilahepan(Tianci Gao) & Ying Zhan | Susan97 | Approved
+cookbooks-partitioned | bilahepan(Tianci Gao) |Jennifer Huang | Approved
+cookbooks-retention-expiry | bilahepan(Tianci Gao) | | Translated
+deploy-bare-metal | bilahepan(Tianci Gao) | | Translated
deploy-kubernetes | KarenGirl | | In Progress
-deploy-monitoring | bilahepan (Tianci Gao) | | In Progress
+deploy-monitoring | bilahepan(Tianci Gao) | | In Progress
developing tools | Susan97 | | In Progress
-functions-api | Luke (ete0918) | | In Progress
-functions-deploying | Luke (ete0918) | | In Progress
+functions-api | Luke(ete0918) | | In Progress
+functions-deploying | Luke(ete0918) | | In Progress
functions-gurantees | Susan97 | | In Progress
functions-quickstart | KarenGirl | | In Progress
io-file | Bu Xing | | In Progress
@@ -42,5 +37,5 @@ io-rabbitmq | Bu Xing | | In Progress
io-redis | Bu Xing | | In Progress
io-solr | Bu Xing | | In Progress
io-tcp | Bu Xing | | In Progress
-security-extending | bilahepan (Tianci Gao) | | In Progress
+security-extending | bilahepan(Tianci Gao) | | In Progress
task #26 | 0 contributors
[pulsar-translation] 06/25: Merge pull request #1 from
Ssssssusan/Ssssssusan-patch-1
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 7102c0cce173af691b6cba77b8d5b2d977fea62c
Merge: 7e2d7ab 6ec9b2c
Author: Ssssssusan <37...@users.noreply.github.com>
AuthorDate: Wed Aug 7 10:45:46 2019 +0800
Merge pull request #1 from Ssssssusan/Ssssssusan-patch-1
Update schedule.md
schedule.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
[pulsar-translation] 21/25: Delete workflow_guidelines.md
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit 14a2f14a87b1112fffeb9559ae9dba157efed9e0
Author: ireneontheway <48...@users.noreply.github.com>
AuthorDate: Thu Aug 22 11:20:07 2019 +0800
Delete workflow_guidelines.md
---
workflow_guidelines.md | 176 -------------------------------------------------
1 file changed, 176 deletions(-)
diff --git a/workflow_guidelines.md b/workflow_guidelines.md
deleted file mode 100644
index 5d5ed0f..0000000
--- a/workflow_guidelines.md
+++ /dev/null
@@ -1,176 +0,0 @@
-# Translation workflow and guidelines
-
-Welcome to join the Pulsar translation project! Before translating, read translation [workflow](#workflow) and [guidelines](#guidelines).
-
-## Workflow
-
-You can find [Apache Pulsar translation project](https://crowdin.com/project/apache-pulsar) on Crowdin. For further details about the functions of Crowdin, see [Crowdin](https://crowdin.com/).
-Here are the steps of the translation workflow:
-
-### Join the Pulsar translation project
-1. Sign in [Apache Pulsar Crowdin project](https://crowdin.com/project/apache-pulsar). If you don’t have a Crowdin account, on the crowdin page, click **SIGN UP** at the upper right corner and fill in the information to create an account. If you have a GitHub, Facebook, Google, Twitter or Gitlab account, you can link any of them to sign in.
-
-
-2. After signing in, click **Join** at the upper right corner on the crowdin page.
-> #### Note
-> The source language of Pulsar files is English. The target languages of our translation projects are Chinese, French and Japanese.
-> Select a language. Take the **Simplified Chinese Translation Project** as an example.
-
-
-### Choose a file to translate and submit a PR
-1. Click **Simplified Chinese Translation Project**.
-2. Click **master > docs**, and check out the status of each file.
-Files in **master > docs** are the source files of the latest versions on Pulsar official website. You only need to translate these markdown files.
-
-
-- Green: translated and approved
-- Blue: translated but not approved
-- Grey: not translated
-
-
-
-Based on your knowledge about Pulsar, you can translate the content that you are familiar with first.
-
-After choosing the file to translate, please check it out in [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). If you find someone is translating this file, please choose another one. If not, you can create a PR and add the file name to [Translation schedule](https://github.com/apache/pulsar-translation/blob/master/schedule.md). Then you can submit the PR.
-
-### Label Setting
-- Reviewers : No need to set up. Reviewers will receive the notification of PR you submitted automatically and will designate someone to handle it.
-- Assignees : Choose yourself to receive notifications.
-- Label : Choose “translation”.
-
-### Translating
-While translating, you don’t need to translate the ID of the file and keep the tag the same as the source file.
-> ####mportant
-> Don’t modify, omit or add a space in a tag, as the omission or relocation of a tag leads to mistakes shown on the website.
-
-
-
-You can modify and save the content directly. Your version will appear automatically at the top of the translation list, as Crowdin will record different versions from different translators. **TM AND MT TRANSLATION** in the bottom-right corner offers you TMs in Pulsar, Crowdin, and other websites.
-
-
-
-> #### Tip
-> You can use and update [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC) while translating.
-
-### Review
-After finishing a translation, please leave a comment in your PR. :
-For example, I've finished the translation, could you help review?
-
-After receiving the comment, reviewers start to review. The reviewer can make simple comments and notify the translator. Direct discussion in PR is encouraged.
-
-If there are no problems, the reviewer will approve this PR and merge it.
-
-The following image gives a general workflow. The workflow source file is available at [lucidchat](https://www.lucidchart.com/invitations/accept/0ebad9d8-ddf3-4a92-8ee6-e813a9bc58ff).
-Masakazu shares a more detailed [swimlane](https://swimlanes.io/d/8L04SRASw) for the workflow.
-
-
-
-## Guidelines
-Here are some common problems during translation. This guideline provides some advice. Please read and follow this guideline carefully before start translation. This could help improve the quality of Pulsar translation files and unify the translation style.
-
-
-### 1. Terms
-
--Pulsar, Pulsar Functions, BookKeeper, ZooKeeper: no need to translate (keep the same capitalization)
--broker, bookie, proxy: no need to translate (keep the same capitalization)
--topic, producer, consumer: translate to “主题”, “生产者”, “消费者”.
-
-More details about Pulsar TB, see [Pulsar 文档翻译术语库](https://shimo.im/sheets/5jozGy5WIUQQf5JV/MODOC). Welcome to add and modify terms in this document.
-
-
-### 2. Add space between Chinese and English characters and numbers
-
-
-In order to improve the readability of Chinese and English mixed documents, you should add spaces between Chinese and English characters and numbers.
-
-
-- Apache Pulsar是一个开源的分布式发布-订阅消息系统，由Apache软件基金会管理，并于2018年9月成为Apache顶级开源项目。❌
-
-- Apache Pulsar 是一个开源的分布式发布-订阅消息系统，由 Apache 软件基金会管理，并于 2018 年 9 月成为 Apache 顶级开源项目。✅
-
-> ####Note
-> You don’t need to add spaces behind Chinese punctuations, even if they are followed by English words.
-
-### 3. Chinese punctuation
-
-
-Please use Chinese punctuations in Chinese documents: You should use “、” rather than “，” when you translate English into Chinese. For example, “Kubernetes, Meso, Docker“ should be translated to “Kubernetes、Mesos、Docker“. Vice versa.
-
-Dealing with different items : Please use (。) at the end of one sentence and use (；) at the end of one item. If each item involves one sentence, please use (。) at the end of each item.
-
- 
-
-
-This example use (。) at the end of each practice.
-
-### 4.Translate “you“ to “你“
-
-To unify the language style, you’d better omit "you". If it is necessary, you can translate it into “你“.
-
-### 5. Comments in the sample code
-
-You’d better translate comments in the sample code. If the comment is simple, you can omit it.
-
-### 6. The liberal translation is better than the literal translation
-
-You’d better not translate word by word. After translating, please check out your words and pay attention to the accuracy and brevity. Based on your full understanding of the source text, you can adopt the liberal translation method. Sometimes, you can omit the translation of quantifier, auxiliary, subject and so on to keep the sentence easy to read.
-
-#### 6.1 ...的...的...的...
-
-You can omit ” ’s “ to make the text easy to read. Here are some examples :
-
-- Pulsar’s documentation is located in the docs folder in Pulsar’s source code repository.
-
-If you translate all the “的”, it can’t read smoothly:
-
-- Pulsar 的文档位于 Pulsar 的源码仓库的 docs 文件夹中。 ❌
-
-Deleting the unnecessary “的” seems better:
-
-- Pulsar 文档位于 Pulsar 源码仓库的 docs 文件夹中。 ✅
-
-#### 6.2 一个……
-
-
-When you translate English into Chinese, you don’t need to translate all the plural; you don’t need to translate ”a” or ”an”. Here are some examples :
-
-
-- Using a Pulsar client with the proxy
-
-Translate “a” into “一个” :
-
-- 使用有 proxy 的一个 Pulsar 客户端 ❌
-
-Deleting the redundant ”一个“ makes the text more concise.
-
-- 使用有 proxy 的 Pulsar 客户端 ✅
-
-### 7. Use passive tense as little as possible
-
-
-You don’t need to use “被” in translation. For example :
-
- - source : Once the message above is successfully published to the topic, you can see it in the standard output: Hello Pulsar.
- - original : 一旦上面的消息被成功发布到Topic中，您会在标准输出中看到它 : Hello Pulsar”。 ❌
- - adjusted : 上面的消息成功发布到主题后，你会在标准输出中看到 : Hello Pulsar。 ✅
-
-### 8. Simple future tense
-You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
-
-- This will publish a single message to the Pulsar topic.
-- original : 这将向Pulsar的Topic发送单条消息。 ❌
-- adjusted : （......）给 Pulsar 主题发布一条信息。 ✅
-
-### 9. Examples
-You can adjust your words according to the context when you translate “Here’s sth”. For example:
-
-- Here's an example.
-- original : 这里有一个示例。 ❌
-- adjusted : 下面是一个示例。 ✅
-
-### 10. Keep your words easy to read
-Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
-
-## Add you as a contributor
-When your first pull request is merged, feel free to add your name to the [contributor list](https://github.com/apache/pulsar-translation/blob/master/CONTRIBUTORS.md).
-
[pulsar-translation] 15/25: Merge pull request #2 from
yangleimiao/master
Posted by hj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hjf pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-translation.git
commit a08f6aac9ca355858adb37a4e3e89d5a756e1053
Merge: 6e8073f f904073
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Wed Aug 14 22:28:42 2019 +0800
Merge pull request #2 from yangleimiao/master
update personal address
CONTRIBUTORS.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)