|
|
|
|
@ -200,4 +200,183 @@ export default {
|
|
|
|
|
line: "Line Messenger",
|
|
|
|
|
mattermost: "Mattermost",
|
|
|
|
|
deleteStatusPageMsg: "是否確定刪除這個 Status Page？",
|
|
|
|
|
"Push URL": "推送網址",
|
|
|
|
|
needPushEvery: "您應每 {0} 秒呼叫此網址。",
|
|
|
|
|
pushOptionalParams: "選填參數：{0}",
|
|
|
|
|
defaultNotificationName: "我的 {notification} 通知 ({number})",
|
|
|
|
|
here: "此處",
|
|
|
|
|
Required: "必填",
|
|
|
|
|
"Bot Token": "機器人權杖",
|
|
|
|
|
wayToGetTelegramToken: "您可以從 {0} 取得 Token。",
|
|
|
|
|
"Chat ID": "聊天 ID",
|
|
|
|
|
supportTelegramChatID: "支援 對話/群組/頻道的聊天 ID",
|
|
|
|
|
wayToGetTelegramChatID: "傳送訊息給機器人，並前往以下網址以取得您的 chat ID：",
|
|
|
|
|
"YOUR BOT TOKEN HERE": "在此填入您的機器人權杖",
|
|
|
|
|
chatIDNotFound: "找不到 Chat ID；請先傳送訊息給機器人",
|
|
|
|
|
"Post URL": "Post 網址",
|
|
|
|
|
"Content Type": "Content Type",
|
|
|
|
|
webhookJsonDesc: "{0} 適合任何現代的 HTTP 伺服器，如 Express.js",
|
|
|
|
|
webhookFormDataDesc: "{multipart} 適合 PHP。 JSON 必須先經由 {decodeFunction} 剖析。",
|
|
|
|
|
secureOptionNone: "無 / STARTTLS (25, 587)",
|
|
|
|
|
secureOptionTLS: "TLS (465)",
|
|
|
|
|
"Ignore TLS Error": "忽略 TLS 錯誤",
|
|
|
|
|
"From Email": "寄件人",
|
|
|
|
|
emailCustomSubject: "自訂主旨",
|
|
|
|
|
"To Email": "收件人",
|
|
|
|
|
smtpCC: "CC",
|
|
|
|
|
smtpBCC: "BCC",
|
|
|
|
|
"Discord Webhook URL": "Discord Webhook 網址",
|
|
|
|
|
wayToGetDiscordURL: "您可以前往伺服器設定 -> 整合 -> Webhook -> 新 Webhook 以取得",
|
|
|
|
|
"Bot Display Name": "機器人顯示名稱",
|
|
|
|
|
"Prefix Custom Message": "前綴自訂訊息",
|
|
|
|
|
"Webhook URL": "Webhook 網址",
|
|
|
|
|
wayToGetTeamsURL: "您可以前往此頁面以了解如何建立 Webhook 網址 {0}。",
|
|
|
|
|
Number: "號碼",
|
|
|
|
|
Recipients: "收件人",
|
|
|
|
|
needSignalAPI: "您需要有 REST API 的 Signal 客戶端。",
|
|
|
|
|
wayToCheckSignalURL: "您可以前往下列網址以了解如何設定：",
|
|
|
|
|
signalImportant: "注意: 不得混合收件人的群組和號碼！",
|
|
|
|
|
"Application Token": "應用程式權杖",
|
|
|
|
|
"Server URL": "伺服器網址",
|
|
|
|
|
Priority: "優先度",
|
|
|
|
|
"Icon Emoji": "Emoji 圖示",
|
|
|
|
|
"Channel Name": "頻道名稱",
|
|
|
|
|
"Uptime Kuma URL": "Uptime Kuma 網址",
|
|
|
|
|
aboutWebhooks: "更多關於 Webhook 的資訊: {0}",
|
|
|
|
|
aboutChannelName: "如果您不想使用 Webhook 頻道，請在 {0} 頻道名稱欄位填入您想使用的頻道。例如: #其他頻道",
|
|
|
|
|
aboutKumaURL: "如果您未填入 Uptime Kuma 網址。將預設使用專案 Github 頁面。",
|
|
|
|
|
emojiCheatSheet: "Emoji 一覽表: {0}",
|
|
|
|
|
PushByTechulus: "Push by Techulus",
|
|
|
|
|
clicksendsms: "ClickSend SMS",
|
|
|
|
|
GoogleChat: "Google Chat (僅限 Google Workspace)",
|
|
|
|
|
"User Key": "使用者金鑰",
|
|
|
|
|
Device: "裝置",
|
|
|
|
|
"Message Title": "訊息標題",
|
|
|
|
|
"Notification Sound": "通知音效",
|
|
|
|
|
"More info on:": "更多資訊: {0}",
|
|
|
|
|
pushoverDesc1: "緊急優先度 (2) 的重試間隔為 30 秒並且會在 1 小時後過期。",
|
|
|
|
|
pushoverDesc2: "如果您想要傳送通知到不同裝置，請填寫裝置欄位。",
|
|
|
|
|
"SMS Type": "簡訊類型",
|
|
|
|
|
octopushTypePremium: "Premium (快速 - 建議用於警報)",
|
|
|
|
|
octopushTypeLowCost: "Low Cost (緩慢 - 有時會被營運商阻擋)",
|
|
|
|
|
checkPrice: "查看 {0} 價格：",
|
|
|
|
|
apiCredentials: "API 認證",
|
|
|
|
|
octopushLegacyHint: "您使用的是舊版的 Octopush (2011-2020) 還是新版？",
|
|
|
|
|
"Check octopush prices": "查看 octopush 價格 {0}。",
|
|
|
|
|
octopushPhoneNumber: "電話號碼 (intl 格式，例如：+33612345678) ",
|
|
|
|
|
octopushSMSSender: "簡訊寄件人名稱：3-11位英數字元及空白 (a-zA-Z0-9)",
|
|
|
|
|
"LunaSea Device ID": "LunaSea 裝置 ID",
|
|
|
|
|
"Apprise URL": "Apprise 網址",
|
|
|
|
|
"Example:": "範例：{0}",
|
|
|
|
|
"Read more:": "深入瞭解：{0}",
|
|
|
|
|
"Status:": "狀態：{0}",
|
|
|
|
|
"Read more": "深入瞭解",
|
|
|
|
|
appriseInstalled: "已安裝 Apprise。",
|
|
|
|
|
appriseNotInstalled: "尚未安裝 Apprise。{0}",
|
|
|
|
|
"Access Token": "存取權杖",
|
|
|
|
|
"Channel access token": "頻道存取權杖",
|
|
|
|
|
"Line Developers Console": "Line 開發者控制台",
|
|
|
|
|
lineDevConsoleTo: "Line 開發者控制台 - {0}",
|
|
|
|
|
"Basic Settings": "基本設定",
|
|
|
|
|
"User ID": "使用者 ID",
|
|
|
|
|
"Messaging API": "Messaging API",
|
|
|
|
|
wayToGetLineChannelToken: "首先，前往 {0}，建立 provider 和 channel (Messaging API)。接著您就可以從上面提到的選單項目中取得頻道存取權杖及使用者 ID。",
|
|
|
|
|
"Icon URL": "圖示網址",
|
|
|
|
|
aboutIconURL: "您可以在 \"圖示網址\" 中提供圖片網址以覆蓋預設個人檔案圖片。若已設定 Emoji 圖示，將忽略此設定。",
|
|
|
|
|
aboutMattermostChannelName: "您可以在 \"頻道名稱\" 欄位中填寫頻道名稱以覆蓋 Webhook 的預設頻道。必須在 Mattermost 的 Webhook 設定中啟用。例如：#其他頻道",
|
|
|
|
|
matrix: "Matrix",
|
|
|
|
|
promosmsTypeEco: "SMS ECO - 便宜，但是很慢且經常過載。僅限位於波蘭的收件人。",
|
|
|
|
|
promosmsTypeFlash: "SMS FLASH - 訊息會自動在收件人的裝置上顯示。僅限位於波蘭的收件人。",
|
|
|
|
|
promosmsTypeFull: "SMS FULL - 高級版，您可以使用您的寄件人名稱 (必須先註冊名稱。對於警報來說十分可靠。",
|
|
|
|
|
promosmsTypeSpeed: "SMS SPEED - 系統中的最高優先度。快速、可靠，但昂貴 (約 SMS FULL 的兩倍價格)。",
|
|
|
|
|
promosmsPhoneNumber: "電話號碼 (若收件人位於波蘭則無需輸入區域代碼)",
|
|
|
|
|
promosmsSMSSender: "簡訊寄件人名稱：預先註冊的名稱或以下的預設名稱：InfoSMS、SMS Info、MaxSMS、INFO、SMS",
|
|
|
|
|
"Feishu WebHookUrl": "飛書 WebHook 網址",
|
|
|
|
|
matrixHomeserverURL: "Homeserver 網址 (開頭為 http(s)://，結尾可能帶連接埠)",
|
|
|
|
|
"Internal Room Id": "Internal Room ID",
|
|
|
|
|
matrixDesc1: "您可以在 Matrix 客戶端的房間設定中的進階選項找到 internal room ID。應該看起來像 !QMdRCpUIfLwsfjxye6:home.server。",
|
|
|
|
|
matrixDesc2: "使用您自己的 Matrix 使用者存取權杖將賦予存取您的帳號和您加入的房間的完整權限。建議建立新使用者，並邀請至您想要接收通知的房間中。您可以執行 {0} 以取得存取權杖",
|
|
|
|
|
Method: "方法",
|
|
|
|
|
Body: "主體",
|
|
|
|
|
Headers: "標頭",
|
|
|
|
|
PushUrl: "Push URL",
|
|
|
|
|
HeadersInvalidFormat: "要求標頭不是有效的 JSON：",
|
|
|
|
|
BodyInvalidFormat: "請求主體不是有效的 JSON：",
|
|
|
|
|
"Monitor History": "監測器歷史紀錄",
|
|
|
|
|
clearDataOlderThan: "保留 {0} 天內的監測器歷史紀錄。",
|
|
|
|
|
PasswordsDoNotMatch: "密碼不相符。",
|
|
|
|
|
records: "記錄",
|
|
|
|
|
"One record": "一項記錄",
|
|
|
|
|
"Showing {from} to {to} of {count} records": "正在顯示 {count} 項記錄中的 {from} 至 {to} 項",
|
|
|
|
|
steamApiKeyDescription: "若要監測 Steam 遊戲伺服器，您將需要 Steam Web-API 金鑰。您可以在此註冊您的 API 金鑰：",
|
|
|
|
|
"Current User": "目前使用者",
|
|
|
|
|
recent: "最近",
|
|
|
|
|
Done: "完成",
|
|
|
|
|
Info: "資訊",
|
|
|
|
|
Security: "安全性",
|
|
|
|
|
"Steam API Key": "Steam API 金鑰",
|
|
|
|
|
"Shrink Database": "壓縮資料庫",
|
|
|
|
|
"Pick a RR-Type...": "選擇資源記錄類型...",
|
|
|
|
|
"Pick Accepted Status Codes...": "選擇可接受的狀態碼...",
|
|
|
|
|
Default: "預設",
|
|
|
|
|
"HTTP Options": "HTTP 選項",
|
|
|
|
|
"Create Incident": "建立事件",
|
|
|
|
|
Title: "標題",
|
|
|
|
|
Content: "內容",
|
|
|
|
|
Style: "樣式",
|
|
|
|
|
info: "資訊",
|
|
|
|
|
warning: "警告",
|
|
|
|
|
danger: "危險",
|
|
|
|
|
primary: "主要",
|
|
|
|
|
light: "淺色",
|
|
|
|
|
dark: "暗色",
|
|
|
|
|
Post: "發佈",
|
|
|
|
|
"Please input title and content": "請輸入標題及內容",
|
|
|
|
|
Created: "建立",
|
|
|
|
|
"Last Updated": "最後更新",
|
|
|
|
|
Unpin: "取消釘選",
|
|
|
|
|
"Switch to Light Theme": "切換至淺色佈景主題",
|
|
|
|
|
"Switch to Dark Theme": "切換至深色佈景主題",
|
|
|
|
|
"Show Tags": "顯示標籤",
|
|
|
|
|
"Hide Tags": "隱藏標籤",
|
|
|
|
|
Description: "說明",
|
|
|
|
|
"No monitors available.": "沒有可用的監測器。",
|
|
|
|
|
"Add one": "新增一個",
|
|
|
|
|
"No Monitors": "無監測器",
|
|
|
|
|
"Untitled Group": "未命名群組",
|
|
|
|
|
Services: "服務",
|
|
|
|
|
Discard: "捨棄",
|
|
|
|
|
Cancel: "取消",
|
|
|
|
|
"Powered by": "技術支援",
|
|
|
|
|
shrinkDatabaseDescription: "觸發 SQLite 的資料庫清理 (VACUUM)。如果您的資料庫是在 1.10.0 版本後建立，AUTO_VACUUM 已自動啟用，則無需此操作。",
|
|
|
|
|
serwersms: "SerwerSMS.pl",
|
|
|
|
|
serwersmsAPIUser: "API 使用者名稱 (包括 webapi_ 前綴)",
|
|
|
|
|
serwersmsAPIPassword: "API 密碼",
|
|
|
|
|
serwersmsPhoneNumber: "電話號碼",
|
|
|
|
|
serwersmsSenderName: "SMS 寄件人名稱 (由客戶入口網站註冊)",
|
|
|
|
|
stackfield: "Stackfield",
|
|
|
|
|
smtpDkimSettings: "DKIM 設定",
|
|
|
|
|
smtpDkimDesc: "請參考 Nodemailer DKIM {0} 使用方式。",
|
|
|
|
|
documentation: "文件",
|
|
|
|
|
smtpDkimDomain: "網域名稱",
|
|
|
|
|
smtpDkimKeySelector: "DKIM 選取器",
|
|
|
|
|
smtpDkimPrivateKey: "私密金鑰",
|
|
|
|
|
smtpDkimHashAlgo: "雜湊演算法 (選填)",
|
|
|
|
|
smtpDkimheaderFieldNames: "要簽署的郵件標頭 (選填)",
|
|
|
|
|
smtpDkimskipFields: "不簽署的郵件標頭 (選填)",
|
|
|
|
|
gorush: "Gorush",
|
|
|
|
|
alerta: "Alerta",
|
|
|
|
|
alertaApiEndpoint: "API Endpoint",
|
|
|
|
|
alertaEnvironment: "環境",
|
|
|
|
|
alertaApiKey: "API 金鑰",
|
|
|
|
|
alertaAlertState: "警示狀態",
|
|
|
|
|
alertaRecoverState: "恢復狀態",
|
|
|
|
|
Proxies: "代理伺服器",
|
|
|
|
|
default: "預設",
|
|
|
|
|
enabled: "啟用",
|
|
|
|
|
setAsDefault: "設為預設",
|
|
|
|
|
deleteProxyMsg: "您確定要為所有監測器刪除此代理伺服器嗎？",
|
|
|
|
|
proxyDescription: "必須將代理伺服器指派給監測器才能運作。",
|
|
|
|
|
enableProxyDescription: "此代理伺服器在啟用前不會在監測器上生效，您可以藉由控制啟用狀態來暫時對所有的監測器停用代理伺服器。",
|
|
|
|
|
setAsDefaultProxyDescription: "預設情況下，新監測器將啟用此代理伺服器。您仍可分別停用各監測器的代理伺服器。",
|
|
|
|
|
};
|
|
|
|
|
|
Louis Lam
2 years ago