Skip to content

Commit

Permalink
New translations en.json (Chinese Traditional)
Browse files Browse the repository at this point in the history
  • Loading branch information
@sulkaharo
sulkaharo committed Sep 23, 2024
1 parent 274a80a commit fa0905b
Showing 1 changed file with 70 additions and 70 deletions.
140 changes: 70 additions & 70 deletions translations/zh_TW.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -628,80 +628,80 @@
"Carbs average": "碳水化合物平均：",
"Eating Soon": "即將用餐",
"Last entry {0} minutes ago": "最後一筆記錄是在 {0} 分鐘前",
"change": "change",
"Speech": "Speech",
"Target Top": "Target Top",
"Target Bottom": "Target Bottom",
"Canceled": "Canceled",
"Meter BG": "Meter BG",
"predicted": "predicted",
"future": "future",
"ago": "ago",
"Last data received": "Last data received",
"Clock View": "Clock View",
"Protein": "Protein",
"Fat": "Fat",
"Protein average": "Protein average",
"Fat average": "Fat average",
"Total carbs": "Total carbs",
"Total protein": "Total protein",
"Total fat": "Total fat",
"change": "變更",
"Speech": "語音",
"Target Top": "目標上限",
"Target Bottom": "目標下限",
"Canceled": "已取消",
"Meter BG": "血糖機血糖值",
"predicted": "預測",
"future": "未來",
"ago": "之前",
"Last data received": "上次資料接收時間",
"Clock View": "時鐘檢視",
"Protein": "蛋白質",
"Fat": "脂肪",
"Protein average": "蛋白質平均值",
"Fat average": "脂肪平均值",
"Total carbs": "總碳水化合物",
"Total protein": "總蛋白質",
"Total fat": "總脂肪",
"Database Size": "資料庫大小",
"Database Size near its limits!": "資料庫大小接近上限！",
"Database size is %1 MiB out of %2 MiB. Please backup and clean up database!": "資料庫大小為 %1 MiB，總容量為 %2 MiB。請備份並清理資料庫！",
"Database file size": "資料庫檔案大小",
"%1 MiB of %2 MiB (%3%)": "%1 MiB of %2 MiB (%3%)",
"Data size": "資料大小",
"virtAsstDatabaseSize": "%1 MiB. That is %2% of available database space.",
"virtAsstTitleDatabaseSize": "Database file size",
"Carbs/Food/Time": "Carbs/Food/Time",
"You have administration messages": "You have administration messages",
"Admin messages in queue": "Admin messages in queue",
"Queue empty": "Queue empty",
"There are no admin messages in queue": "There are no admin messages in queue",
"Please sign in using the API_SECRET to see your administration messages": "Please sign in using the API_SECRET to see your administration messages",
"Reads enabled in default permissions": "Reads enabled in default permissions",
"Data reads enabled": "Data reads enabled",
"Data writes enabled": "Data writes enabled",
"Data writes not enabled": "Data writes not enabled",
"Color prediction lines": "Color prediction lines",
"Release Notes": "Release Notes",
"Check for Updates": "Check for Updates",
"Open Source": "Open Source",
"Nightscout Info": "Nightscout Info",
"The primary purpose of Loopalyzer is to visualise how the Loop closed loop system performs. It may work with other setups as well, both closed and open loop, and non loop. However depending on which uploader you use, how frequent it is able to capture your data and upload, and how it is able to backfill missing data some graphs may have gaps or even be completely empty. Always ensure the graphs look reasonable. Best is to view one day at a time and scroll through a number of days first to see.": "The primary purpose of Loopalyzer is to visualise how the Loop closed loop system performs. It may work with other setups as well, both closed and open loop, and non loop. However depending on which uploader you use, how frequent it is able to capture your data and upload, and how it is able to backfill missing data some graphs may have gaps or even be completely empty. Always ensure the graphs look reasonable. Best is to view one day at a time and scroll through a number of days first to see.",
"Loopalyzer includes a time shift feature. If you for example have breakfast at 07:00 one day and at 08:00 the day after your average blood glucose curve these two days will most likely look flattened and not show the actual response after a breakfast. Time shift will compute the average time these meals were eaten and then shift all data (carbs, insulin, basal etc.) during both days the corresponding time difference so that both meals align with the average meal start time.": "Loopalyzer includes a time shift feature. If you for example have breakfast at 07:00 one day and at 08:00 the day after your average blood glucose curve these two days will most likely look flattened and not show the actual response after a breakfast. Time shift will compute the average time these meals were eaten and then shift all data (carbs, insulin, basal etc.) during both days the corresponding time difference so that both meals align with the average meal start time.",
"In this example all data from first day is pushed 30 minutes forward in time and all data from second day 30 minutes backward in time so it appears as if you had had breakfast at 07:30 both days. This allows you to see your actual average blood glucose response from a meal.": "In this example all data from first day is pushed 30 minutes forward in time and all data from second day 30 minutes backward in time so it appears as if you had had breakfast at 07:30 both days. This allows you to see your actual average blood glucose response from a meal.",
"Time shift highlights the period after the average meal start time in gray, for the duration of the DIA (Duration of Insulin Action). As all data points the entire day are shifted the curves outside the gray area may not be accurate.": "Time shift highlights the period after the average meal start time in gray, for the duration of the DIA (Duration of Insulin Action). As all data points the entire day are shifted the curves outside the gray area may not be accurate.",
"Note that time shift is available only when viewing multiple days.": "Note that time shift is available only when viewing multiple days.",
"Please select a maximum of two weeks duration and click Show again.": "Please select a maximum of two weeks duration and click Show again.",
"Show profiles table": "Show profiles table",
"Show predictions": "Show predictions",
"Timeshift on meals larger than %1 g carbs consumed between %2 and %3": "Timeshift on meals larger than %1 g carbs consumed between %2 and %3",
"Previous": "Previous",
"Previous day": "Previous day",
"Next day": "Next day",
"Next": "Next",
"Temp basal delta": "Temp basal delta",
"Authorized by token": "Authorized by token",
"Auth role": "Auth role",
"view without token": "view without token",
"Remove stored token": "Remove stored token",
"Weekly Distribution": "Weekly Distribution",
"Failed authentication": "Failed authentication",
"A device at IP address %1 attempted authenticating with Nightscout with wrong credentials. Check if you have an uploader setup with wrong API_SECRET or token?": "A device at IP address %1 attempted authenticating with Nightscout with wrong credentials. Check if you have an uploader setup with wrong API_SECRET or token?",
"Default (with leading zero and U)": "Default (with leading zero and U)",
"Concise (with U, without leading zero)": "Concise (with U, without leading zero)",
"Minimal (without leading zero and U)": "Minimal (without leading zero and U)",
"Small Bolus Display": "Small Bolus Display",
"Large Bolus Display": "Large Bolus Display",
"Bolus Display Threshold": "Bolus Display Threshold",
"%1 U and Over": "%1 U and Over",
"Event repeated %1 times.": "Event repeated %1 times.",
"minutes": "minutes",
"Last recorded %1 %2 ago.": "Last recorded %1 %2 ago.",
"Security issue": "Security issue",
"Weak API_SECRET detected. Please use a mix of small and CAPITAL letters, numbers and non-alphanumeric characters such as !#%&/ to reduce the risk of unauthorized access. The minimum length of the API_SECRET is 12 characters.": "Weak API_SECRET detected. Please use a mix of small and CAPITAL letters, numbers and non-alphanumeric characters such as !#%&/ to reduce the risk of unauthorized access. The minimum length of the API_SECRET is 12 characters.",
"less than 1": "less than 1",
"MongoDB password and API_SECRET match. This is a really bad idea. Please change both and do not reuse passwords across the system.": "MongoDB password and API_SECRET match. This is a really bad idea. Please change both and do not reuse passwords across the system."
"virtAsstDatabaseSize": "%1 MiB，佔用可用資料庫空間的 %2%。",
"virtAsstTitleDatabaseSize": "資料庫檔案大小",
"Carbs/Food/Time": "碳水化合物/食物/時間",
"You have administration messages": "你有管理訊息",
"Admin messages in queue": "管理訊息在佇列中",
"Queue empty": "佇列是空的",
"There are no admin messages in queue": "佇列中沒有管理訊息",
"Please sign in using the API_SECRET to see your administration messages": "請使用 API_SECRET 登入以查看你的管理訊息",
"Reads enabled in default permissions": "預設權限中啟用了讀取功能",
"Data reads enabled": "資料讀取已啟用",
"Data writes enabled": "資料寫入已啟用",
"Data writes not enabled": "資料寫入未啟用",
"Color prediction lines": "顏色預測線",
"Release Notes": "版本說明",
"Check for Updates": "檢查更新",
"Open Source": "開源",
"Nightscout Info": "Nightscout 資訊",
"The primary purpose of Loopalyzer is to visualise how the Loop closed loop system performs. It may work with other setups as well, both closed and open loop, and non loop. However depending on which uploader you use, how frequent it is able to capture your data and upload, and how it is able to backfill missing data some graphs may have gaps or even be completely empty. Always ensure the graphs look reasonable. Best is to view one day at a time and scroll through a number of days first to see.": "Loopalyzer 的主要目的是視覺化展示 Loop 閉環系統的運作情況。它也可能適用於其他系統配置，包括閉環、開環或非閉環系統。然而，根據你使用的上傳器類型、資料捕捉與上傳的頻率，以及填補遺失資料的方式，有些圖表可能會有空白或甚至完全沒有資料。請務必確認圖表顯示的資料合理。建議一次檢視一天，並先瀏覽多天的資料以進行檢查。",
"Loopalyzer includes a time shift feature. If you for example have breakfast at 07:00 one day and at 08:00 the day after your average blood glucose curve these two days will most likely look flattened and not show the actual response after a breakfast. Time shift will compute the average time these meals were eaten and then shift all data (carbs, insulin, basal etc.) during both days the corresponding time difference so that both meals align with the average meal start time.": "Loopalyzer 包含一個時間偏移功能。如果你某天在 07:00 吃早餐，而隔天在 08:00 吃早餐，那麼這兩天的平均血糖曲線很可能會被平滑化，無法顯示實際的早餐後反應。時間偏移功能會計算這些餐點的平均進餐時間，並將這兩天所有的資料（碳水化合物、胰島素、基礎胰島素等）按相應的時間差進行偏移，讓這兩次餐點與平均進餐時間對齊。",
"In this example all data from first day is pushed 30 minutes forward in time and all data from second day 30 minutes backward in time so it appears as if you had had breakfast at 07:30 both days. This allows you to see your actual average blood glucose response from a meal.": "在此範例中，第一天的所有資料會被往前推30分鐘，而第二天的所有資料則會被往後推30分鐘，這樣看起來就像是你兩天的早餐都是在 07:30 進行的。這樣你就可以看到實際的平均血糖反應。",
"Time shift highlights the period after the average meal start time in gray, for the duration of the DIA (Duration of Insulin Action). As all data points the entire day are shifted the curves outside the gray area may not be accurate.": "時間偏移功能會將平均進餐時間之後、胰島素作用時間（DIA，Duration of Insulin Action）內的區間以灰色顯示。由於整天的資料點都被移動過，灰色區域外的曲線可能不太準確。",
"Note that time shift is available only when viewing multiple days.": "請注意，時間偏移功能僅在檢視多日資料時可用。",
"Please select a maximum of two weeks duration and click Show again.": "請選擇最多兩週的時間範圍，然後再次點擊顯示。",
"Show profiles table": "顯示設定檔表格",
"Show predictions": "顯示預測",
"Timeshift on meals larger than %1 g carbs consumed between %2 and %3": "將時間偏移應用於碳水化合物攝取量超過 %1 克、並在 %2 到 %3 之間消耗的餐點。",
"Previous": "前一個",
"Previous day": "前一天",
"Next day": "下一天",
"Next": "下一個",
"Temp basal delta": "臨時基礎胰島素變動量",
"Authorized by token": "透過權杖授權",
"Auth role": "驗證角色",
"view without token": "未使用權杖檢視",
"Remove stored token": "移除儲存的權杖",
"Weekly Distribution": "每週分佈",
"Failed authentication": "驗證失敗",
"A device at IP address %1 attempted authenticating with Nightscout with wrong credentials. Check if you have an uploader setup with wrong API_SECRET or token?": "IP 位址 %1 的裝置嘗試以錯誤的憑證連線 Nightscout。請檢查是否有上傳器設定了錯誤的 API_SECRET 或權杖？",
"Default (with leading zero and U)": "預設（包含前置零和 U）",
"Concise (with U, without leading zero)": "簡潔（包含 U，無前置零）",
"Minimal (without leading zero and U)": "極簡（無前置零和 U）",
"Small Bolus Display": "小劑量注射顯示",
"Large Bolus Display": "大劑量注射顯示",
"Bolus Display Threshold": "注射顯示臨界值",
"%1 U and Over": "%1 單位及以上",
"Event repeated %1 times.": "事件重複 %1 次。",
"minutes": "分鐘",
"Last recorded %1 %2 ago.": "上次紀錄於 %1 %2 前。",
"Security issue": "安全問題",
"Weak API_SECRET detected. Please use a mix of small and CAPITAL letters, numbers and non-alphanumeric characters such as !#%&/ to reduce the risk of unauthorized access. The minimum length of the API_SECRET is 12 characters.": "檢測到強度較弱的 API_SECRET。請使用大小寫字母、數字和非字母數字的特殊字元（例如 !#%&/）的組合，以降低未授權存取的風險。API_SECRET 的最小長度為 12 個字元。",
"less than 1": "小於 1",
"MongoDB password and API_SECRET match. This is a really bad idea. Please change both and do not reuse passwords across the system.": "MongoDB 密碼和 API_SECRET 相同。這是一個非常危險的做法。請更改兩者，並避免在系統中重複使用密碼。"
}

0 comments on commit fa0905b

Please sign in to comment.