1fanwang commented on code in PR #70417:
URL: https://github.com/apache/airflow/pull/70417#discussion_r3651731945


##########
airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/common.json:
##########
@@ -218,6 +226,47 @@
   },
   "selectLanguage": "选择语言",
   "selected": "已选择",
+  "shortcuts": {
+    "categories": {
+      "code": "代码",
+      "dagView": "Dag 视图",
+      "filters": "筛选",
+      "global": "全局",
+      "logs": "日志",
+      "navigation": "导航",
+      "runActions": "执行与任务操作",

Review Comment:
   Keeping 执行与任务操作. Matches zh-TW (執行與任務操作).



##########
airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/common.json:
##########
@@ -218,6 +226,47 @@
   },
   "selectLanguage": "选择语言",
   "selected": "已选择",
+  "shortcuts": {
+    "categories": {
+      "code": "代码",
+      "dagView": "Dag 视图",
+      "filters": "筛选",
+      "global": "全局",
+      "logs": "日志",
+      "navigation": "导航",
+      "runActions": "执行与任务操作",
+      "search": "搜索"
+    },
+    "descriptions": {
+      "clearRun": "清除 $t(dagRun_one)",
+      "clearTaskInstance": "清除 $t(taskInstance_one)",
+      "downloadLogs": "下载日志",
+      "focusFilterSearch": "聚焦筛选搜索框",
+      "focusLogSearch": "搜索日志",

Review Comment:
   Going with 搜索日志. The value is just 'Search logs' (no 'focus'), and it lines 
up with zh-TW 搜尋日誌.



##########
airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/common.json:
##########
@@ -218,6 +226,47 @@
   },
   "selectLanguage": "选择语言",
   "selected": "已选择",
+  "shortcuts": {
+    "categories": {
+      "code": "代码",
+      "dagView": "Dag 视图",
+      "filters": "筛选",
+      "global": "全局",
+      "logs": "日志",
+      "navigation": "导航",
+      "runActions": "执行与任务操作",
+      "search": "搜索"
+    },
+    "descriptions": {
+      "clearRun": "清除 $t(dagRun_one)",
+      "clearTaskInstance": "清除 $t(taskInstance_one)",
+      "downloadLogs": "下载日志",
+      "focusFilterSearch": "聚焦筛选搜索框",
+      "focusLogSearch": "搜索日志",
+      "focusSearch": "聚焦搜索框",
+      "markRunFailed": "标记 $t(dagRun_one) 为失败",
+      "markRunSuccess": "标记 $t(dagRun_one) 为成功",
+      "markTaskFailed": "标记 $t(task_one) 为失败",
+      "markTaskGroupFailed": "标记 $t(taskGroup_one) 为失败",
+      "markTaskGroupSuccess": "标记 $t(taskGroup_one) 为成功",
+      "markTaskSuccess": "标记 $t(task_one) 为成功",
+      "navigateTasks": "导航 $t(task_other)",
+      "openGraphFilters": "打开图形筛选",
+      "scrollBottom": "滚动到最下方",
+      "scrollTop": "滚动到最上方",
+      "searchDags": "搜索 $t(dag_other)",
+      "showHelp": "显示 $t(shortcuts.title)",
+      "toggleExpand": "展开或收起所有分组",
+      "toggleFullscreen": "切换全屏",
+      "toggleGraphGrid": "切换图形 / 网格视图",
+      "toggleSource": "切换源代码",
+      "toggleTaskGroup": "展开或收起 $t(taskGroup_one)",
+      "toggleTimestamp": "切换时间戳",
+      "toggleWrap": "切换 $t(wrap.wrap)"

Review Comment:
   Keeping 展开或收起所有分组; it mirrors the en 'Expand or collapse all groups'. 
toggleWrap reads 切换 because its en is 'Toggle wrap', so the two differ by 
source.



##########
airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/common.json:
##########
@@ -281,10 +333,12 @@
   "taskGroup_other": "任务分组",
   "taskId": "任务 ID",
   "taskInstance": {
+    "additionalAttributes": "任务实例附加属性",
     "dagVersion": "Dag 版本",
     "executor": "执行器",
     "executorConfig": "执行器配置",
     "hostname": "主机名称",
+    "id": "ID",

Review Comment:
   Consistent with the source: additionalAttributes en is 'Additional Task 
Instance Attributes' so 任务实例附加属性, while hostname en is just 'Hostname' so 主机名称. 
The prefix comes from the English.



##########
airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/common.json:
##########
@@ -294,11 +348,13 @@
     "queuedWhen": "开始排队时间",
     "renderedMapIndex": "已渲染映射索引",
     "scheduledWhen": "开始调度时间",
+    "trigger": "触发器",
     "triggerer": {

Review Comment:
   Keeping 触发器. Matches zh-TW 觸發器. This is the noun (the Trigger object); the 
verb would be 触发.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to