Welcome to join the Pulsar translation project! Before translating, read translation workflow and guidelines.
You can find Apache Pulsar translation project on Crowdin. For further details about the functions of Crowdin, see Crowdin. Here are the steps of the translation workflow:
Sign in Apache Pulsar Crowdin project. 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.
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.
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. 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. Then you can submit the PR.
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 文档翻译术语库 while translating.
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.
Masakazu shares a more detailed swimlane for the workflow.
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.
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 文档翻译术语库. Welcome to add and modify terms in this document.
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.
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.
To unify the language style, you’d better omit “you”. If it is necessary, you can translate it into “你“.
You’d better translate comments in the sample code. If the comment is simple, you can omit it.
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.
You can omit ” ’s “ to make the text easy to read. Here are some examples :
If you translate all the “的”, it can’t read smoothly:
Deleting the unnecessary “的” seems better:
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 :
Translate “a” into “一个” :
Deleting the redundant ”一个“ makes the text more concise.
You don’t need to use “被” in translation. For example :
You don’t need to translate “will” to “将要......”. It is better to use the present tense. For example :
You can adjust your words according to the context when you translate “Here’s sth”. For example:
Keep your words simple and smooth. Therefore, please double check your words after finishing translation.
When your first pull request is merged, feel free to add your name to the contributor list.