docs: refine zh translations

This commit is contained in:
Zaiming (Stone) Shi 2023-03-29 15:05:32 +02:00
parent 624c168dde
commit 94726eb7f1
1 changed files with 12 additions and 12 deletions

View File

@ -581,7 +581,7 @@ emqx_ee_bridge_kafka {
en: "Set how many bytes to pull from Kafka in each fetch request. " en: "Set how many bytes to pull from Kafka in each fetch request. "
"Please note that if the configured value is smaller than the message size in Kafka, it may negatively impact the fetch performance." "Please note that if the configured value is smaller than the message size in Kafka, it may negatively impact the fetch performance."
zh: "设置每次从 Kafka 拉取数据的字节数。" zh: "设置每次从 Kafka 拉取数据的字节数。"
"如果该配置小于 Kafka 中消息到大小,则可能会影响消费性能。" "如该配置小于 Kafka 消息的大小,可能会影响消费性能。"
} }
label { label {
en: "Fetch Bytes" en: "Fetch Bytes"
@ -592,7 +592,7 @@ emqx_ee_bridge_kafka {
consumer_max_rejoin_attempts { consumer_max_rejoin_attempts {
desc { desc {
en: "Maximum number of times allowed for a member to re-join the group. If the consumer group can not reach balance after this configured number of attempts, the consumer group member will restart after a delay." en: "Maximum number of times allowed for a member to re-join the group. If the consumer group can not reach balance after this configured number of attempts, the consumer group member will restart after a delay."
zh: "允许一个消费组成员重新加入小组的最大次数。如果超过改配置次数后仍不能成功加入消费组,则会在延迟一段时间后再重试。" zh: "消费组成员允许重新加入小组的最大次数。如超过该配置次数后仍未能成功加入消费组,则会在等待一段时间后重试。"
} }
label { label {
en: "Max Rejoin Attempts" en: "Max Rejoin Attempts"
@ -603,7 +603,7 @@ emqx_ee_bridge_kafka {
desc { desc {
en: "Defines from which offset a consumer should start fetching when there " en: "Defines from which offset a consumer should start fetching when there "
"is no commit history or when the commit history becomes invalid." "is no commit history or when the commit history becomes invalid."
zh: "当没有偏移量的历史记录,或则历史记录失效后,消费者应该使用哪个偏移量重新开始消费。" zh: "如不存在偏移量历史记录或历史记录失效,消费者应使用哪个偏移量开始消费。"
} }
label { label {
en: "Offset Reset Policy" en: "Offset Reset Policy"
@ -623,7 +623,7 @@ emqx_ee_bridge_kafka {
consumer_topic_mapping { consumer_topic_mapping {
desc { desc {
en: "Defines the mapping between Kafka topics and MQTT topics. Must contain at least one item." en: "Defines the mapping between Kafka topics and MQTT topics. Must contain at least one item."
zh: "指定 Kafka 主题和 MQTT 主题之间的映射关系。 必须至少包含一项。" zh: "指定 Kafka 主题和 MQTT 主题之间的映射关系。 至少包含一项。"
} }
label { label {
en: "Topic Mapping" en: "Topic Mapping"
@ -637,7 +637,7 @@ emqx_ee_bridge_kafka {
"<code>none</code> Uses the key from the Kafka message unchanged." "<code>none</code> Uses the key from the Kafka message unchanged."
" Note: in this case, the key must be a valid UTF-8 string.\n" " Note: in this case, the key must be a valid UTF-8 string.\n"
"<code>base64</code> Uses base-64 encoding on the received key." "<code>base64</code> Uses base-64 encoding on the received key."
zh: "定义了在通过MQTT转发之前如何处理Kafka消息的 Key。" zh: "通过 MQTT 转发之前如何处理 Kafka 消息的 Key。"
"<code>none</code> 使用 Kafka 消息中的 Key 原始值,不进行编码。" "<code>none</code> 使用 Kafka 消息中的 Key 原始值,不进行编码。"
" 注意在这种情况下Key 必须是一个有效的 UTF-8 字符串。\n" " 注意在这种情况下Key 必须是一个有效的 UTF-8 字符串。\n"
"<code>base64</code> 对收到的密钥或值使用 base-64 编码。" "<code>base64</code> 对收到的密钥或值使用 base-64 编码。"
@ -654,7 +654,7 @@ emqx_ee_bridge_kafka {
"<code>none</code> Uses the value from the Kafka message unchanged." "<code>none</code> Uses the value from the Kafka message unchanged."
" Note: in this case, the value must be a valid UTF-8 string.\n" " Note: in this case, the value must be a valid UTF-8 string.\n"
"<code>base64</code> Uses base-64 encoding on the received value." "<code>base64</code> Uses base-64 encoding on the received value."
zh: "定义了在通过MQTT转发之前如何处理Kafka消息的 Value。" zh: "通过 MQTT 转发之前如何处理 Kafka 消息的 Value。"
"<code>none</code> 使用 Kafka 消息中的 Value 原始值,不进行编码。" "<code>none</code> 使用 Kafka 消息中的 Value 原始值,不进行编码。"
" 注意在这种情况下Value 必须是一个有效的 UTF-8 字符串。\n" " 注意在这种情况下Value 必须是一个有效的 UTF-8 字符串。\n"
"<code>base64</code> 对收到的 Value 使用 base-64 编码。" "<code>base64</code> 对收到的 Value 使用 base-64 编码。"