Lee-W commented on code in PR #51558:
URL: https://github.com/apache/airflow/pull/51558#discussion_r2137612348


##########
airflow-core/src/airflow/ui/src/i18n/locales/zh-TW/admin.json:
##########
@@ -0,0 +1,146 @@
+{
+  "columns":{
+    "description": "描述",
+    "key": "鍵",
+    "name": "名稱",
+    "value": "值"
+  },
+  "config":{
+    "columns":{
+      "section": "區段"
+    },
+    "title": "Airflow 設定"
+  },
+  "connections":{
+    "add":"新增連線",
+    "columns":{
+      "connectionId": "連線 ID",
+      "connectionType": "連線類型",
+      "host": "主機",
+      "port": "埠"
+    },
+    "delete":{
+      "deleteConnection_one": "刪除 {{count}} 個連線",

Review Comment:
   I thought it would always be one. Do we need to pass variable here?



##########
airflow-core/src/airflow/ui/src/i18n/locales/zh-TW/assets.json:
##########
@@ -0,0 +1,10 @@
+{
+  "columns": {
+    "consumingDags": "消費Dag",
+    "group": "群組",
+    "lastAssetEvent": "上次資源事件",

Review Comment:
   ```suggestion
       "lastAssetEvent": "最後資源事件",
   ```



##########
airflow-core/src/airflow/ui/src/i18n/locales/zh-TW/common.json:
##########
@@ -49,13 +63,14 @@
   "noItemsFound": "找不到{{modelName}}",
   "pools": {
     "deferred": "已延後",
-    "open": "開啟",
+    "open": "開放",
     "pools_one": "資源池",
     "pools_other": "資源池",
     "queued": "排隊中",
     "running": "執行中",
     "scheduled": "已排程"
   },
+  "runId": "執行ID",

Review Comment:
   ```suggestion
     "runId": "執行 ID",
   ```



##########
airflow-core/src/airflow/ui/src/i18n/locales/zh-TW/assets.json:
##########
@@ -0,0 +1,10 @@
+{
+  "columns": {
+    "consumingDags": "消費Dag",

Review Comment:
   ```suggestion
       "consumingDags": "消費者 Dag",
   ```
   
   Basically, `consumingDags` are the dags that consume this asset event, and 
the downstream ones are consumers. I think it might be better to understand a 
bit 🤔 



-- 
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