Translated using Weblate (Traditional Chinese)

Currently translated at 100.0% (2603 of 2603)
This commit is contained in:
Tony Chen 2013-06-23 08:04:55 +02:00 committed by Weblate
parent c900872cf0
commit 3788e016ad

View File

@ -4,7 +4,7 @@ msgstr ""
"Project-Id-Version: phpMyAdmin 4.0.4-dev\n"
"Report-Msgid-Bugs-To: phpmyadmin-devel@lists.sourceforge.net\n"
"POT-Creation-Date: 2013-06-03 09:16-0400\n"
"PO-Revision-Date: 2013-06-22 12:06+0200\n"
"PO-Revision-Date: 2013-06-23 08:04+0200\n"
"Last-Translator: Tony Chen <tonychen@finenet.com.tw>\n"
"Language-Team: Traditional Chinese "
"<http://l10n.cihar.com/projects/phpmyadmin/4-0/zh_TW/>\n"
@ -317,7 +317,7 @@ msgstr "phpMyAdmin 設定儲存功能未能啟動, %s請按此%s 查出問題原
#: libraries/server_privileges.lib.php:2864 libraries/structure.lib.php:757
#: tbl_tracking.php:762
msgid "Table"
msgstr "表"
msgstr "資料表"
#: db_printview.php:100 libraries/Table.class.php:351
#: libraries/build_html_for_db.lib.php:31 libraries/import.lib.php:181
@ -1246,8 +1246,8 @@ msgid ""
"than %d seconds. It is advisable to set this long_query_time 0-2 seconds, "
"depending on your system."
msgstr ""
"slow_query_log 已經被啟用,但是伺服器仍然只為執行時間大於 %d 秒的查詢做紀錄。"
"建議根據您的系統將 long_query_time 設定為 0-2 秒。"
"slow_query_log 已經被啟用,但是伺服器仍然只為執行時間大於 %d 秒的查詢做記錄。建議根據您的系統將 long_query_time "
"設定為 0-2 秒。"
#: js/messages.php:137
#, php-format
@ -1318,7 +1318,7 @@ msgstr "單位"
#: js/messages.php:157
msgid "From slow log"
msgstr "從較慢的查詢紀錄檔"
msgstr "從緩慢日誌檔"
#: js/messages.php:158
msgid "From general log"
@ -1326,11 +1326,11 @@ msgstr "從普通的查詢記錄檔"
#: js/messages.php:159
msgid "Analysing logs"
msgstr "分析用的紀錄檔"
msgstr "分析用的日誌檔"
#: js/messages.php:160
msgid "Analysing & loading logs. This may take a while."
msgstr "讀取且分析紀錄檔中. 這可能會花費一些時間。"
msgstr "讀取且分析日誌檔中. 這可能會花費一些時間。"
#: js/messages.php:161
msgid "Cancel request"
@ -1354,11 +1354,11 @@ msgstr ""
#: js/messages.php:164
msgid "Log data loaded. Queries executed in this time span:"
msgstr "紀錄檔已被讀取,時間區間:"
msgstr "日誌檔已載入,查詢執行時間區間:"
#: js/messages.php:166
msgid "Jump to Log table"
msgstr "跳轉至紀錄檔的資料表"
msgstr "跳轉至日誌檔的資料表"
#: js/messages.php:167
msgid "No data found"
@ -1366,7 +1366,7 @@ msgstr "無資料"
#: js/messages.php:168
msgid "Log analysed, but no data found in this time span."
msgstr "紀錄檔已經被分析了,但是在這個時間區段內沒有任何資料。"
msgstr "已分析日誌檔,但是在這個時間區間內沒有任何資料。"
#: js/messages.php:170
msgid "Analyzing…"
@ -1412,12 +1412,12 @@ msgstr "系列"
#. l10n: A collection of available filters
#: js/messages.php:182
msgid "Log table filter options"
msgstr "紀錄檔篩選"
msgstr "日誌檔篩選選項"
#. l10n: Filter as in "Start Filtering"
#: js/messages.php:184
msgid "Filter"
msgstr "過濾"
msgstr "篩選"
#: js/messages.php:185
msgid "Filter queries by word/regexp:"
@ -1439,7 +1439,7 @@ msgstr "總計:"
#: js/messages.php:190
msgid "Loading logs"
msgstr "載入紀錄檔中"
msgstr "載入日誌檔中"
#: js/messages.php:191
msgid "Monitor refresh failed"
@ -1513,7 +1513,7 @@ msgstr "詳細的規則"
#: js/messages.php:212
msgid "Justification"
msgstr "校正"
msgstr "調整"
#: js/messages.php:213
msgid "Used variable / formula"
@ -1890,7 +1890,7 @@ msgstr "隱藏控制面板"
#: js/messages.php:376
msgid "The requested page was not found in the history, it may have expired."
msgstr "無法在錄中找到您所要求的頁面,它可能已經過期了。"
msgstr "無法在歷史記錄中找到您所要求的頁面,它可能已經過期了。"
#: js/messages.php:379 setup/lib/index.lib.php:188
#, php-format
@ -2580,7 +2580,7 @@ msgstr "查詢花費 %01.4f 秒"
#: libraries/structure.lib.php:1357 libraries/structure.lib.php:1364
#: server_databases.php:319 server_databases.php:322
msgid "With selected:"
msgstr "選中項:"
msgstr "選中項"
#: libraries/DisplayResults.class.php:5045
#: libraries/DisplayResults.class.php:5046
@ -5004,11 +5004,11 @@ msgstr "快速訪問圖示的目標"
msgid ""
"Defines the minimum number of items (tables, views, routines and events) to "
"display a filter box."
msgstr "定義最少的物件數 (資料表、視表、程序和事件)以顯示在過濾框。"
msgstr "定義最少的項目數 (資料表、視表、程序和事件) 以顯示在篩選框。"
#: libraries/config/messages.inc.php:307
msgid "Minimum number of items to display the filter box"
msgstr "顯示過濾框的最少的物件數量"
msgstr "顯示篩選框的最少的項目數量"
#: libraries/config/messages.inc.php:308
msgid "Minimum number of databases to display the database filter box"
@ -5223,7 +5223,7 @@ msgstr "再次瀏覽資料表時,之前的排序偏好會被記錄"
#: libraries/config/messages.inc.php:356
msgid "Remember table's sorting"
msgstr "錄資料表的排序偏好"
msgstr "錄資料表的排序偏好"
#: libraries/config/messages.inc.php:357
msgid "Repeat the headers every X cells, [kbd]0[/kbd] deactivates this feature"
@ -5623,8 +5623,7 @@ msgstr "「介面偏好」資料表"
msgid ""
"Whether a DROP DATABASE IF EXISTS statement will be added as first line to "
"the log when creating a database."
msgstr ""
"設定當資料庫建立時,是否在紀錄檔第一行加上 DROP DATABASE IF EXISTS 指令。"
msgstr "設定當資料庫建立時,是否在記錄檔第一行加上 DROP DATABASE IF EXISTS 指令。"
#: libraries/config/messages.inc.php:436
msgid "Add DROP DATABASE"
@ -5634,7 +5633,7 @@ msgstr "新增 DROP DATABASE"
msgid ""
"Whether a DROP TABLE IF EXISTS statement will be added as first line to the "
"log when creating a table."
msgstr "設定當資料表建立時,是否在錄檔前面加上 DROP TABLE IF EXISTS 指令。"
msgstr "設定當資料表建立時,是否在錄檔前面加上 DROP TABLE IF EXISTS 指令。"
#: libraries/config/messages.inc.php:438
msgid "Add DROP TABLE"
@ -5644,7 +5643,7 @@ msgstr "新增 DROP TABLE"
msgid ""
"Whether a DROP VIEW IF EXISTS statement will be added as first line to the "
"log when creating a view."
msgstr "設定當視表建立時,是否在錄檔前面加上 DROP 視表 IF EXISTS 命令。"
msgstr "設定當視表建立時,是否在錄檔前面加上 DROP 視表 IF EXISTS 命令。"
#: libraries/config/messages.inc.php:440
msgid "Add DROP VIEW"
@ -8345,7 +8344,7 @@ msgstr "執行以下的查詢時發生錯誤:「%s」"
#: libraries/rte/rte_events.lib.php:134
msgid "Sorry, we failed to restore the dropped event."
msgstr "抱歉,系統回復被刪除的 Event 時失敗。"
msgstr "抱歉,系統回復被刪除的事件時失敗。"
#: libraries/rte/rte_events.lib.php:137 libraries/rte/rte_routines.lib.php:325
#: libraries/rte/rte_triggers.lib.php:109
@ -8355,12 +8354,12 @@ msgstr "備份用的查詢是:"
#: libraries/rte/rte_events.lib.php:144
#, php-format
msgid "Event %1$s has been modified."
msgstr "Event %1$s 已被修改。"
msgstr "事件 %1$s 已被修改。"
#: libraries/rte/rte_events.lib.php:164
#, php-format
msgid "Event %1$s has been created."
msgstr "建立 Event %1$s 成功。"
msgstr "建立事件 %1$s 成功。"
#: libraries/rte/rte_events.lib.php:175 libraries/rte/rte_routines.lib.php:366
#: libraries/rte/rte_triggers.lib.php:147
@ -8369,7 +8368,7 @@ msgstr "<b>處理您的請求時出現一個或多個錯誤:</b>"
#: libraries/rte/rte_events.lib.php:228
msgid "Edit event"
msgstr "編輯 Event"
msgstr "編輯事件"
#: libraries/rte/rte_events.lib.php:255 libraries/rte/rte_routines.lib.php:464
#: libraries/rte/rte_routines.lib.php:1478
@ -8387,11 +8386,11 @@ msgstr "詳細"
#: libraries/rte/rte_events.lib.php:420
msgid "Event name"
msgstr "Event 名稱"
msgstr "事件名稱"
#: libraries/rte/rte_events.lib.php:441 server_binlog.php:186
msgid "Event type"
msgstr "Event 類型"
msgstr "事件類型"
#: libraries/rte/rte_events.lib.php:463 libraries/rte/rte_routines.lib.php:954
#, php-format
@ -8438,23 +8437,23 @@ msgstr "定義必須是 \"username@hostname\" 格式"
#: libraries/rte/rte_events.lib.php:574
msgid "You must provide an event name"
msgstr "您必須為 Event 指定一個名稱"
msgstr "您必須為事件指定一個名稱"
#: libraries/rte/rte_events.lib.php:588
msgid "You must provide a valid interval value for the event."
msgstr "您必須為 Event 指定一個正確的時間間隔。"
msgstr "您必須為事件指定一個正確的時間間隔。"
#: libraries/rte/rte_events.lib.php:603
msgid "You must provide a valid execution time for the event."
msgstr "您必須為 Event 指定一個正確的執行時間。"
msgstr "您必須為事件指定一個正確的執行時間。"
#: libraries/rte/rte_events.lib.php:607
msgid "You must provide a valid type for the event."
msgstr "您必須為 Event 指定一個正確的類型。"
msgstr "您必須為事件指定一個正確的類型。"
#: libraries/rte/rte_events.lib.php:631
msgid "You must provide an event definition."
msgstr "您必須為 Event 給予一個正確的定義。"
msgstr "您必須為事件給予一個正確的定義。"
#: libraries/rte/rte_footer.lib.php:91
msgid "OFF"
@ -8466,7 +8465,7 @@ msgstr "開啟"
#: libraries/rte/rte_footer.lib.php:108
msgid "Event scheduler status"
msgstr "Event 排程狀態"
msgstr "事件排程狀態"
#: libraries/rte/rte_list.lib.php:55
#| msgid "Return type"
@ -8555,7 +8554,7 @@ msgstr "返回選項"
#: libraries/rte/rte_routines.lib.php:1037
msgid "Is deterministic"
msgstr "是確定的"
msgstr "確定性"
#: libraries/rte/rte_routines.lib.php:1047
#| msgid "Security"
@ -8659,7 +8658,7 @@ msgstr "您必須為觸發器提供一個有效的時機"
#: libraries/rte/rte_triggers.lib.php:466
msgid "You must provide a valid event for the trigger"
msgstr "您必須為 Event 指定一個正確觸發條件"
msgstr "您必須為事件指定一個正確觸發條件"
#: libraries/rte/rte_triggers.lib.php:474
#| msgid "Invalid table name"
@ -8736,12 +8735,12 @@ msgstr "沒有觸發器可供顯示。"
#: libraries/rte/rte_words.lib.php:46
msgid "Add event"
msgstr "新增 Event"
msgstr "新增事件"
#: libraries/rte/rte_words.lib.php:48
#, php-format
msgid "Export of event %s"
msgstr "匯出 Event %s"
msgstr "匯出事件 %s"
#: libraries/rte/rte_words.lib.php:49
msgid "event"
@ -8749,12 +8748,12 @@ msgstr "事件"
#: libraries/rte/rte_words.lib.php:50
msgid "You do not have the necessary privileges to create an event"
msgstr "您沒有足夠的權限建立一個 Event"
msgstr "您沒有足夠的權限建立一個事件"
#: libraries/rte/rte_words.lib.php:51
#, php-format
msgid "No event with name %1$s found in database %2$s"
msgstr "在資料庫「%2$s」中找不到名為「%1$s」的 Event"
msgstr "在資料庫 %2$s 中找不到名為 %1$s 的事件"
#: libraries/rte/rte_words.lib.php:52
#| msgid "There are no files to upload"
@ -9043,7 +9042,7 @@ msgstr "允許建立 views."
#: libraries/server_privileges.lib.php:247
#: libraries/server_privileges.lib.php:894 server_privileges.php:71
msgid "Allows to set up events for the event scheduler"
msgstr "允許爲 Event 設定排程"
msgstr "允許為事件設定排程"
#: libraries/server_privileges.lib.php:251
#: libraries/server_privileges.lib.php:898 server_privileges.php:92
@ -9406,12 +9405,11 @@ msgid ""
"please reduce your SQL query input to the single query that causes problems, "
"and submit a bug report with the data chunk in the CUT section below:"
msgstr ""
"您可能發現了 SQL 解析器的缺陷 (bug)。請仔細檢查您的查詢,包括引號是否正確及是"
"否符合。其它可能的失敗原因可能由於您上傳了超過引用文字區域外的二進制資料。您"
"還可以在 MySQL 命令行界面試一下您的查詢。如果可能的話,以下會列出 MySQL 服務"
"器的錯誤輸出,這可能對您解決問題有一定的幫助。如果您仍然有問題,或者命令行界"
"面執行成功而解析器出錯,請將您的 SQL 查詢縮減到導致問題的某一條指令,然後和下"
"面剪切區中的資料一起送出一個缺陷 (bug) 報告:"
"您可能發現了 SQL 解析器的缺陷 "
"(bug)。請仔細檢查您的查詢,包括引號是否正確及是否符合。其它可能的失敗原因也許由於您上傳了超過引號文字外的二進制資料。您還可以在 MySQL "
"命令行界面試一下您的查詢。如果可能的話,以下會列出 MySQL "
"服務器的錯誤輸出,這可能對您解決問題有一定的幫助。如果您仍然有問題,或者命令行界面執行成功而解析器出錯,請將您的 SQL "
"查詢縮減到導致問題的某一條指令,然後和下面剪切區中的資料一起送出一個缺陷 (bug) 報告:"
#: libraries/sqlparser.lib.php:173
msgid "BEGIN CUT"
@ -10505,7 +10503,7 @@ msgid ""
"enabled. Note however, that the general_log produces a lot of data and "
"increases server load by up to 15%"
msgstr ""
"PhpMyAdmin 監測器可以幫您最佳化伺服器的配置和追特定的查詢。後者需要設定 log_output 為 'TABLE',並啟用 "
"PhpMyAdmin 監測器可以幫您最佳化伺服器的配置和追特定的查詢。後者需要設定 log_output 為 'TABLE',並啟用 "
"slow_query_log 或 general_log。但請注意 general_log 將產生大量的資料,而且最多會增加伺服器的負載達 15 %"
#: server_status_monitor.php:558
@ -10604,7 +10602,7 @@ msgstr "圖表中的序列:"
#: server_status_monitor.php:675
#| msgid "Show statistics"
msgid "Log statistics"
msgstr "紀錄統計"
msgstr "日誌統計"
#: server_status_monitor.php:676
#| msgid "Select page"
@ -10663,7 +10661,7 @@ msgstr "查詢數量"
#: server_status_variables.php:78 server_variables.php:156
msgid "Filters"
msgstr "過濾"
msgstr "篩選"
#: server_status_variables.php:82 server_variables.php:158
#| msgid "Do not change the password"
@ -12167,7 +12165,7 @@ msgstr "您可能需要增加 {long_query_time} 或最佳化緩慢查詢日誌
#: libraries/advisory_rules.txt:68
#, php-format
msgid "The slow query rate should be below 5%%, your value is %s%%."
msgstr "緩慢查詢率應低於 5%,您的值是 %s%%。"
msgstr "緩慢查詢率應低於 5%%,您的值是 %s%%。"
#: libraries/advisory_rules.txt:70
#| msgid "Flush query cache"
@ -12195,24 +12193,24 @@ msgstr "超長查詢時間"
msgid ""
"{long_query_time} is set to 10 seconds or more, thus only slow queries that "
"take above 10 seconds are logged."
msgstr ""
msgstr "{long_query_time} 設為 10 秒或更多,因此只會記錄超過 10 秒的緩慢查詢。"
#: libraries/advisory_rules.txt:81
msgid ""
"It is suggested to set {long_query_time} to a lower value, depending on your "
"environment. Usually a value of 1-5 seconds is suggested."
msgstr ""
msgstr "根據您的環境將 {long_query_time} 設定調低,通常建議設為 1-5 秒。"
#: libraries/advisory_rules.txt:82
#, php-format
#| msgid "long_query_time is set to %d second(s)."
msgid "long_query_time is currently set to %ds."
msgstr "long_query_time 設為 %d 秒。"
msgstr "long_query_time 目前設為 %d 秒。"
#: libraries/advisory_rules.txt:84 libraries/advisory_rules.txt:91
#| msgid "Show query box"
msgid "Slow query logging"
msgstr "緩慢查詢錄"
msgstr "緩慢查詢錄"
#: libraries/advisory_rules.txt:87 libraries/advisory_rules.txt:94
#| msgid "slow_query_log is enabled."
@ -12223,23 +12221,23 @@ msgstr "已禁用緩慢查詢。"
msgid ""
"Enable slow query logging by setting {log_slow_queries} to 'ON'. This will "
"help troubleshooting badly performing queries."
msgstr ""
msgstr "要啟用緩慢查詢記錄請將 {log_slow_queries} 設為 'ON',這將有助於不良查詢的故障排除。"
#: libraries/advisory_rules.txt:89
#| msgid "long_query_time is set to %d second(s)."
msgid "log_slow_queries is set to 'OFF'"
msgstr "log_slow_queries 設為 'OFF'"
msgstr "log_slow_queries 設為 'OFF'"
#: libraries/advisory_rules.txt:95
msgid ""
"Enable slow query logging by setting {slow_query_log} to 'ON'. This will "
"help troubleshooting badly performing queries."
msgstr ""
msgstr "要啟用緩慢查詢記錄請將 {slow_query_log} 設為 'ON',這將有助於不良查詢的故障排除。"
#: libraries/advisory_rules.txt:96
#| msgid "long_query_time is set to %d second(s)."
msgid "slow_query_log is set to 'OFF'"
msgstr "slow_query_log 設為 'OFF'"
msgstr "slow_query_log 設為 'OFF'"
#: libraries/advisory_rules.txt:100
#| msgid "Select Tables"
@ -12248,13 +12246,13 @@ msgstr "釋放序列"
#: libraries/advisory_rules.txt:103
msgid "The MySQL server version less than 5.1."
msgstr ""
msgstr "MySQL 伺服器版本低於 5.1。"
#: libraries/advisory_rules.txt:104
msgid ""
"You should upgrade, as MySQL 5.1 has improved performance, and MySQL 5.5 "
"even more so."
msgstr ""
msgstr "您應該升級到 MySQL 5.1 或 5.5,以獲得更好的性能。"
#: libraries/advisory_rules.txt:105 libraries/advisory_rules.txt:112
#: libraries/advisory_rules.txt:119
@ -12270,13 +12268,13 @@ msgstr "次要版本"
#: libraries/advisory_rules.txt:110
msgid "Version less than 5.1.30 (the first GA release of 5.1)."
msgstr ""
msgstr "版本小於 5.1.30 (5.1 官方第一個推薦版本)。"
#: libraries/advisory_rules.txt:111
msgid ""
"You should upgrade, as recent versions of MySQL 5.1 have improved "
"performance and MySQL 5.5 even more so."
msgstr ""
msgstr "您應該升級到 MySQL 5.1 或 5.5 最近的版本,以獲得更好的性能。"
#: libraries/advisory_rules.txt:117
msgid "Version less than 5.5.8 (the first GA release of 5.5)."
@ -12468,8 +12466,8 @@ msgid ""
"using this formula: (query_cache_size - qcache_free_memory) / "
"qcache_queries_in_cache"
msgstr ""
"大量碎片很可能會增加 Qcache_lowmem_prunes也許是由於 {query_cache_size} "
"過小而導致大量查詢快取低記憶體縮減。刷新查詢快取 (可能會鎖住查詢快取很長的時間) 可以暫時解決這個問题。仔細調整 "
"大量碎片很可能會增加 Qcache_lowmem_prunes 的行為,也許是由於 {query_cache_size} "
"過小而導致大量查詢快取低記憶體的清理。刷新查詢快取 (可能會鎖住查詢快取很長的時間) 可以暫時解決這個問题。仔細調整 "
"{query_cache_min_res_unit} 到一個更小的值將有所幫助,例如您可以使用下列公式來計算並設置您查詢快取大小的平均值: "
"(query_cache_size - qcache_free_memory) / qcache_queries_in_cache"
@ -12484,7 +12482,7 @@ msgstr "快取碎片已達到 %s%%,當達到 100%% 時意味著查詢快取幾
#: libraries/advisory_rules.txt:188
#| msgid "Query cache"
msgid "Query cache low memory prunes"
msgstr "查詢快取低記憶體縮減"
msgstr "查詢快取低記憶體清理"
#: libraries/advisory_rules.txt:191
#| msgid "The amount of free memory for query cache."
@ -12516,13 +12514,13 @@ msgstr "查詢快取最大大小"
msgid ""
"The query cache size is above 128 MiB. Big query caches may cause "
"significant overhead that is required to maintain the cache."
msgstr ""
msgstr "查詢快取超过 128 MB過大的查詢快取可能會引起額外的維謢開銷。"
#: libraries/advisory_rules.txt:199
msgid ""
"Depending on your environment, it might be performance increasing to reduce "
"this value."
msgstr ""
msgstr "根據您的環境,減少這個值可能可以提高效能。"
#: libraries/advisory_rules.txt:200
#, php-format
@ -12557,7 +12555,7 @@ msgstr ""
#: libraries/advisory_rules.txt:207
msgid "query_cache_limit is set to 1 MiB"
msgstr "query_cache_limit 設為 1 MB"
msgstr "query_cache_limit 設為 1 MB"
#: libraries/advisory_rules.txt:211
#| msgid "Allows creating temporary tables."
@ -12580,7 +12578,7 @@ msgstr "根據您的系統記憶體多寡,考慮增加 {sort_buffer_size} 和
msgid ""
"%s%% of all sorts cause temporary tables, this value should be lower than 10%"
"%."
msgstr ""
msgstr "有 %s%% 的排序會產生臨時表,這個值應低於 10%%。"
#: libraries/advisory_rules.txt:218
#| msgid "Allows creating temporary tables."
@ -12592,7 +12590,7 @@ msgstr "排序產生的臨時表比率"
#| msgid "Sort buffer size"
msgid ""
"Temporary tables average: %s, this value should be less than 1 per hour."
msgstr "平均臨時表: %s此值應每小時小於1。"
msgstr "平均臨時表: %s此值應每小時小於 1。"
#: libraries/advisory_rules.txt:225
#| msgid "Textarea rows"
@ -12601,7 +12599,7 @@ msgstr "排序筆數"
#: libraries/advisory_rules.txt:228
msgid "There are lots of rows being sorted."
msgstr ""
msgstr "有大量的資料被排序。"
#: libraries/advisory_rules.txt:229
msgid ""
@ -12609,12 +12607,12 @@ msgid ""
"want to make sure that the queries which require a lot of sorting use "
"indexed columns in the ORDER BY clause, as this will result in much faster "
"sorting"
msgstr ""
msgstr "雖然大量的排序不是什麼問題,但您最好能儘可能在 ORDER BY 子句中使用索引欄位,這樣能導致更快的排序"
#: libraries/advisory_rules.txt:230
#, php-format
msgid "Sorted rows average: %s"
msgstr ""
msgstr "平均排序筆數: %s"
#: libraries/advisory_rules.txt:233
#| msgid "There are no files to upload"
@ -12630,13 +12628,13 @@ msgstr "有太多的結合未使用索引。"
msgid ""
"This means that joins are doing full table scans. Adding indexes for the "
"columns being used in the join conditions will greatly speed up table joins"
msgstr ""
msgstr "這意味著結合將會掃描整個資料表,在結合條件中使用索引欄位將可大幅加快資料表的處理"
#: libraries/advisory_rules.txt:238
#, php-format
#| msgid "Sort buffer size"
msgid "Table joins average: %s, this value should be less than 1 per hour"
msgstr "平均資料表結合: %s此值應每小時小於1"
msgstr "平均資料表結合: %s此值應每小時小於 1"
#: libraries/advisory_rules.txt:240
#| msgid "There are no files to upload"
@ -12657,12 +12655,14 @@ msgid ""
"scans. Other than that full index scans can only be reduced by rewriting "
"queries."
msgstr ""
"這通常表示頻繁的掃描整個索引。整個索引掃描會比資料表掃描速度快,但在大資料表還是要消耗不少 CPU 時間,如果那些資料表有大量的更新和刪除操作,執行 "
"'OPTIMIZE TABLE' 可以減少整個索引掃描次數或提升速度。致於其他只能靠重寫查詢來減少掃描整個索引。"
#: libraries/advisory_rules.txt:245
#, php-format
#| msgid "Sort buffer size"
msgid "Index scans average: %s, this value should be less than 1 per hour"
msgstr "平均索引掃瞄: %s此值應每小時小於1"
msgstr "平均索引掃瞄: %s此值應每小時小於 1"
#: libraries/advisory_rules.txt:247
#| msgid "Format of imported file"
@ -12679,14 +12679,14 @@ msgid ""
"This indicates that many queries need to sort results and/or do a full table "
"scan, including join queries that do not use indexes. Add indexes where "
"applicable."
msgstr ""
msgstr "這表示許多查詢結果需要排序或做整個資料表掃描,包括未使用索引的結合查詢。請在適當的地方增加索引。"
#: libraries/advisory_rules.txt:252
#, php-format
msgid ""
"Rate of reading fixed position average: %s, this value should be less than 1 "
"per hour"
msgstr ""
msgstr "平均固定位置讀取率平均: %s這個值應每小時低於 1"
#: libraries/advisory_rules.txt:254
#| msgid "Create table"
@ -12702,18 +12702,18 @@ msgstr "讀取資料表下一筆比例過高。"
msgid ""
"This indicates that many queries are doing full table scans. Add indexes "
"where applicable."
msgstr ""
msgstr "這表示有許多查詢做了整個資料表的掃描,請適時地增加索引。"
#: libraries/advisory_rules.txt:259
#, php-format
#| msgid "Sort buffer size"
msgid ""
"Rate of reading next table row: %s, this value should be less than 1 per hour"
msgstr "平均讀取資料表下一筆: %s此值應每小時小於1"
msgstr "平均讀取資料表下一筆: %s此值應每小時小於 1"
#: libraries/advisory_rules.txt:262
msgid "tmp_table_size vs. max_heap_table_size"
msgstr ""
msgstr "tmp_table_size 對 max_heap_table_size"
#: libraries/advisory_rules.txt:265
msgid "{tmp_table_size} and {max_heap_table_size} are not the same."
@ -12859,7 +12859,7 @@ msgstr "從記憶體中讀取索引的百分比"
#: libraries/advisory_rules.txt:321
#, php-format
msgid "The %% of indexes that use the MyISAM key buffer is low."
msgstr ""
msgstr "使用 MyISAM 鍵值緩衝的索引百分比太低。"
#: libraries/advisory_rules.txt:322
msgid "You may need to increase {key_buffer_size}."
@ -12914,7 +12914,7 @@ msgstr "考慮增加 {open_files_limit},請在更改後重新開機,並檢
#, php-format
msgid ""
"The number of opened files is at %s%% of the limit. It should be below 85%%"
msgstr ""
msgstr "開啟的檔數已達允許的 %s%%,這個值應低於 85%%"
#: libraries/advisory_rules.txt:341
#| msgid "Format of imported file"
@ -12945,7 +12945,7 @@ msgstr "太多的資料表鎖定並未立即給予。"
#: libraries/advisory_rules.txt:352 libraries/advisory_rules.txt:359
msgid "Optimize queries and/or use InnoDB to reduce lock wait."
msgstr ""
msgstr "最佳化查詢或使用 InnoDB 來減少鎖定等待。"
#: libraries/advisory_rules.txt:353
#, php-format
@ -12955,7 +12955,7 @@ msgstr "立即資料表鎖定: %s%%,這個值應該在 95%% 以上"
#: libraries/advisory_rules.txt:355
msgid "Table lock wait rate"
msgstr ""
msgstr "資料表鎖定等待率"
#: libraries/advisory_rules.txt:360
#, php-format
@ -12972,16 +12972,16 @@ msgstr "執行緒快取"
msgid ""
"Thread cache is disabled, resulting in more overhead from new connections to "
"MySQL."
msgstr ""
msgstr "執行緒快取已被禁用,因而有更多開銷要重新連接到 MySQL。"
#: libraries/advisory_rules.txt:366
msgid "Enable the thread cache by setting {thread_cache_size} > 0."
msgstr ""
msgstr "設定 {thread_cache_size} > 0 以啟用執行緒快取。"
#: libraries/advisory_rules.txt:367
#| msgid "Tracking is not active."
msgid "The thread cache is set to 0"
msgstr "執行緒快取設為零"
msgstr "執行緒快取設為零"
#: libraries/advisory_rules.txt:369
#, php-format
@ -12996,7 +12996,7 @@ msgstr "執行緒快取並不是很有效率。"
#: libraries/advisory_rules.txt:373
msgid "Increase {thread_cache_size}."
msgstr ""
msgstr "增加 {thread_cache_size}。"
#: libraries/advisory_rules.txt:374
#, php-format
@ -13023,11 +13023,11 @@ msgstr "這通常發生在系統超載的情況下,您需要仔細地監視您
#: libraries/advisory_rules.txt:381
#, php-format
msgid "%s thread(s) took longer than %s seconds to start, it should be 0"
msgstr ""
msgstr "%s 個執行緒啟動花了超過 %s 秒,這個值應該是 0"
#: libraries/advisory_rules.txt:383
msgid "Slow launch time"
msgstr ""
msgstr "緩慢啟動時間"
#: libraries/advisory_rules.txt:386
#| msgid "long_query_time is set to %d second(s)."
@ -13056,7 +13056,7 @@ msgstr "已使用的連線百分比"
msgid ""
"The maximum amount of used connections is getting close to the value of "
"{max_connections}."
msgstr ""
msgstr "最大已用連線數接近 {max_connections}。"
#: libraries/advisory_rules.txt:396
msgid ""
@ -13064,12 +13064,14 @@ msgid ""
"that do not close database handlers properly get killed sooner. Make sure "
"the code closes database handlers properly."
msgstr ""
"增加 {max_connections} 或減少 {wait_timeout} "
"可以使得未正常結束資料庫連線者更快速的被移除,以確保程式碼能正確的結束資料庫連線。"
#: libraries/advisory_rules.txt:397
#, php-format
msgid ""
"Max_used_connections is at %s%% of max_connections, it should be below 80%%"
msgstr ""
msgstr "Max_used_connections 已達 max_connections 的 %s%%,這個值應低於 80%%"
#: libraries/advisory_rules.txt:399
#| msgid "Persistent connections"
@ -13122,12 +13124,12 @@ msgid ""
"Clients are usually aborted when they did not close their connection to "
"MySQL properly. This can be due to network issues or code not closing a "
"database handler properly. Check your network and code."
msgstr ""
msgstr "用戶端沒有正確地結束 MySQL 的連線而被中止,通常是由於網路的問題或程式未正確關閉資料庫的連線。請檢查您的網路和程式碼。"
#: libraries/advisory_rules.txt:418
#, php-format
msgid "%s%% of all clients are aborted. This value should be below 2%%"
msgstr ""
msgstr "有 %s%% 的用戶端被中止,這個值應低於 2%%"
#: libraries/advisory_rules.txt:420
#| msgid "Format of imported file"
@ -13142,7 +13144,7 @@ msgstr "客端中斷率為 %s這個值應該每小時低於 1"
#: libraries/advisory_rules.txt:429
msgid "Is InnoDB disabled?"
msgstr ""
msgstr "是不是 InnoDB 被禁用?"
#: libraries/advisory_rules.txt:432
#| msgid "Could not save recent table"
@ -13151,11 +13153,11 @@ msgstr "您未啟用 InnoDB。"
#: libraries/advisory_rules.txt:433
msgid "InnoDB is usually the better choice for table engines."
msgstr ""
msgstr "通常 InnoDB 資料表引擎是更好的選擇。"
#: libraries/advisory_rules.txt:434
msgid "have_innodb is set to 'value'"
msgstr ""
msgstr "have_innodb 設為 'value'"
#: libraries/advisory_rules.txt:436
#| msgid "Buffer pool size"
@ -13182,6 +13184,12 @@ msgid ""
"fine. See also <a href=\"http://mysqldatabaseadministration.blogspot."
"com/2007/01/increase-innodblogfilesize-proper-way.html\">this blog entry</a>"
msgstr ""
"在 InnoDB 資料表有大量寫入的系統上,您應設定 {innodb_log_file_size} 為 "
"{innodb_buffer_pool_size} 的 25%%。然而此值越大,在資料庫崩潰恢復的時間將越長,所以這個值就不應該高於 256 "
"MB。然而請注意不是只更改此變數的值就好您還需要關閉伺服器的服務刪除 InnoDB 的日誌檔,在 my.cnf "
"中設定新的值,啟動伺服器,如果一切都很順利再檢查錯誤日誌。請參見 <a "
"href=\"http://mysqldatabaseadministration.blogspot.com/2007/01/increase-"
"innodblogfilesize-proper-way.html\">這篇部落格文章</a>"
#: libraries/advisory_rules.txt:441
#, php-format
@ -13198,7 +13206,7 @@ msgstr "最大 InnoDB 日誌大小"
#: libraries/advisory_rules.txt:446
msgid "The InnoDB log file size is inadequately large."
msgstr ""
msgstr "InnoDB 日誌檔的大小是不夠大。"
#: libraries/advisory_rules.txt:447
#, php-format
@ -13213,11 +13221,18 @@ msgid ""
"mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-"
"proper-way.html\">this blog entry</a>"
msgstr ""
"通常將 {innodb_log_file_size} 設為 {innodb_buffer_pool_size} 的 25%% 就已足夠。過大的 "
"{innodb_log_file_size} 會嚴重減緩資料庫崩潰後恢復的時間,請參見 <a "
"href=\"http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-"
"innodb_log_file_size/\">這篇文章</a>。您需要關閉伺服器的服務,刪除 InnoDB 的日誌檔,在 my.cnf "
"中設定新的值,啟動伺服器,如果一切都很順利再檢查錯誤日誌。請參見 <a "
"href=\"http://mysqldatabaseadministration.blogspot.com/2007/01/increase-"
"innodblogfilesize-proper-way.html\">這篇部落格文章</a>"
#: libraries/advisory_rules.txt:448
#, php-format
msgid "Your absolute InnoDB log size is %s MiB"
msgstr ""
msgstr "你的 InnoDB 日誌絕對大小是 %s MB"
#: libraries/advisory_rules.txt:450
#| msgid "Buffer pool size"
@ -13243,6 +13258,11 @@ msgid ""
"\"http://www.mysqlperformanceblog.com/2007/11/03/choosing-"
"innodb_buffer_pool_size/\">this article</a>"
msgstr ""
"InnoDB 緩衝池對 InnoDB 資料表的性能有重大影響,請將您剩餘的記憶體分配給此緩衝區。如果資料庫伺服器僅有 InnoDB "
"作為儲存引擎,並沒有運行的其他服務 (如網頁伺服器),您可以將高達 80%% 的可用記憶體分配給它。如果情況並非如此,您需要仔細評估其他服務和非 "
"InnoDB 資料表的記憶體消耗狀況,並相對應地設定此變數。如果將它設置得太高,您的系統將會開始記憶體和磁碟的切換,因而大大降低性能。請參見 <a "
"href=\"http://www.mysqlperformanceblog.com/2007/11/03/choosing-"
"innodb_buffer_pool_size/\">這篇文章</a>"
#: libraries/advisory_rules.txt:455
#, php-format
@ -13252,6 +13272,8 @@ msgid ""
"perfectly adequate for your system if you don't have much InnoDB tables or "
"other services running on the same machine."
msgstr ""
"您目前的 InnoDB 緩衝池已使用記憶體的 %s%%。如果您指派少於 60%% 將觸發此規則,然而也許因為沒有太多的 InnoDB "
"資料表或其他服務同時運行於此機器,所以這樣也許十分適用於您的系統。"
#: libraries/advisory_rules.txt:459
#| msgid "max. concurrent connections"
@ -13269,6 +13291,9 @@ msgid ""
"writers for a given table. See also <a href=\"http://dev.mysql.com/doc/"
"refman/5.5/en/concurrent-inserts.html\">MySQL Documentation</a>"
msgstr ""
"將 {concurrent_insert} 設為 1 可以減少在相同表上的讀取和寫入衝突,請參見 <a "
"href=\"http://dev.mysql.com/doc/refman/5.5/en/concurrent-inserts.html\">MySQL "
"文件</a>"
#: libraries/advisory_rules.txt:464
msgid "concurrent_insert is set to 0"