Author: keichwa
Date: 2014-10-07 18:00:49 +0200 (Tue, 07 Oct 2014)
New Revision: 89802
Modified:
trunk/yast/zh_TW/po/add-on-creator.zh_TW.po
trunk/yast/zh_TW/po/add-on.zh_TW.po
trunk/yast/zh_TW/po/audit-laf.zh_TW.po
trunk/yast/zh_TW/po/auth-client.zh_TW.po
trunk/yast/zh_TW/po/auth-server.zh_TW.po
trunk/yast/zh_TW/po/autoinst.zh_TW.po
trunk/yast/zh_TW/po/base.zh_TW.po
trunk/yast/zh_TW/po/bootloader.zh_TW.po
trunk/yast/zh_TW/po/ca-management.zh_TW.po
trunk/yast/zh_TW/po/cio.zh_TW.po
trunk/yast/zh_TW/po/cluster.zh_TW.po
trunk/yast/zh_TW/po/control-center.zh_TW.po
trunk/yast/zh_TW/po/control.zh_TW.po
trunk/yast/zh_TW/po/country.zh_TW.po
trunk/yast/zh_TW/po/crowbar.zh_TW.po
trunk/yast/zh_TW/po/dhcp-server.zh_TW.po
trunk/yast/zh_TW/po/dns-server.zh_TW.po
trunk/yast/zh_TW/po/drbd.zh_TW.po
trunk/yast/zh_TW/po/fcoe-client.zh_TW.po
trunk/yast/zh_TW/po/firewall-services.zh_TW.po
trunk/yast/zh_TW/po/firewall.zh_TW.po
trunk/yast/zh_TW/po/firstboot.zh_TW.po
trunk/yast/zh_TW/po/ftp-server.zh_TW.po
trunk/yast/zh_TW/po/geo-cluster.zh_TW.po
trunk/yast/zh_TW/po/gtk.zh_TW.po
trunk/yast/zh_TW/po/http-server.zh_TW.po
trunk/yast/zh_TW/po/inetd.zh_TW.po
trunk/yast/zh_TW/po/installation.zh_TW.po
trunk/yast/zh_TW/po/instserver.zh_TW.po
trunk/yast/zh_TW/po/iplb.zh_TW.po
trunk/yast/zh_TW/po/iscsi-client.zh_TW.po
trunk/yast/zh_TW/po/iscsi-lio-server.zh_TW.po
trunk/yast/zh_TW/po/iscsi-server.zh_TW.po
trunk/yast/zh_TW/po/isns.zh_TW.po
trunk/yast/zh_TW/po/kdump.zh_TW.po
trunk/yast/zh_TW/po/kerberos-server.zh_TW.po
trunk/yast/zh_TW/po/kerberos.zh_TW.po
trunk/yast/zh_TW/po/languages_db.zh_TW.po
trunk/yast/zh_TW/po/ldap-client.zh_TW.po
trunk/yast/zh_TW/po/ldap-server.zh_TW.po
trunk/yast/zh_TW/po/ldap.zh_TW.po
trunk/yast/zh_TW/po/live-installer.zh_TW.po
trunk/yast/zh_TW/po/lxc.zh_TW.po
trunk/yast/zh_TW/po/mail.zh_TW.po
trunk/yast/zh_TW/po/multipath.zh_TW.po
trunk/yast/zh_TW/po/ncurses-pkg.zh_TW.po
trunk/yast/zh_TW/po/ncurses.zh_TW.po
trunk/yast/zh_TW/po/network.zh_TW.po
trunk/yast/zh_TW/po/nfs.zh_TW.po
trunk/yast/zh_TW/po/nfs_server.zh_TW.po
trunk/yast/zh_TW/po/nis.zh_TW.po
trunk/yast/zh_TW/po/nis_server.zh_TW.po
trunk/yast/zh_TW/po/ntp-client.zh_TW.po
trunk/yast/zh_TW/po/oneclickinstall.zh_TW.po
trunk/yast/zh_TW/po/online-update-configuration.zh_TW.po
trunk/yast/zh_TW/po/online-update.zh_TW.po
trunk/yast/zh_TW/po/opensuse_mirror.zh_TW.po
trunk/yast/zh_TW/po/packager.zh_TW.po
trunk/yast/zh_TW/po/pam.zh_TW.po
trunk/yast/zh_TW/po/pkg-bindings.zh_TW.po
trunk/yast/zh_TW/po/printer.zh_TW.po
trunk/yast/zh_TW/po/product-creator.zh_TW.po
trunk/yast/zh_TW/po/proxy.zh_TW.po
trunk/yast/zh_TW/po/qt-pkg.zh_TW.po
trunk/yast/zh_TW/po/qt.zh_TW.po
trunk/yast/zh_TW/po/rdp.zh_TW.po
trunk/yast/zh_TW/po/rear.zh_TW.po
trunk/yast/zh_TW/po/registration.zh_TW.po
trunk/yast/zh_TW/po/reipl.zh_TW.po
trunk/yast/zh_TW/po/relocation-server.zh_TW.po
trunk/yast/zh_TW/po/s390.zh_TW.po
trunk/yast/zh_TW/po/samba-client.zh_TW.po
trunk/yast/zh_TW/po/samba-server.zh_TW.po
trunk/yast/zh_TW/po/samba-users.zh_TW.po
trunk/yast/zh_TW/po/scanner.zh_TW.po
trunk/yast/zh_TW/po/security.zh_TW.po
trunk/yast/zh_TW/po/services-manager.zh_TW.po
trunk/yast/zh_TW/po/slp-server.zh_TW.po
trunk/yast/zh_TW/po/snapper.zh_TW.po
trunk/yast/zh_TW/po/sound.zh_TW.po
trunk/yast/zh_TW/po/squid.zh_TW.po
trunk/yast/zh_TW/po/sshd.zh_TW.po
trunk/yast/zh_TW/po/storage.zh_TW.po
trunk/yast/zh_TW/po/sudo.zh_TW.po
trunk/yast/zh_TW/po/support.zh_TW.po
trunk/yast/zh_TW/po/sysconfig.zh_TW.po
trunk/yast/zh_TW/po/tftp-server.zh_TW.po
trunk/yast/zh_TW/po/timezone_db.zh_TW.po
trunk/yast/zh_TW/po/tune.zh_TW.po
trunk/yast/zh_TW/po/update.zh_TW.po
trunk/yast/zh_TW/po/users.zh_TW.po
trunk/yast/zh_TW/po/vm.zh_TW.po
trunk/yast/zh_TW/po/wagon.zh_TW.po
trunk/yast/zh_TW/po/wol.zh_TW.po
trunk/yast/zh_TW/po/xpram.zh_TW.po
trunk/yast/zh_TW/po/yast2-apparmor.zh_TW.po
Log:
merged
Modified: trunk/yast/zh_TW/po/add-on-creator.zh_TW.po
===================================================================
--- trunk/yast/zh_TW/po/add-on-creator.zh_TW.po 2014-10-07 15:59:55 UTC (rev 89801)
+++ trunk/yast/zh_TW/po/add-on-creator.zh_TW.po 2014-10-07 16:00:49 UTC (rev 89802)
@@ -8,7 +8,7 @@
msgstr ""
"Project-Id-Version: add-on-creator\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-23 15:41+0200\n"
+"POT-Creation-Date: 2014-07-04 15:51+0200\n"
"PO-Revision-Date: 2012-05-21 08:17+0800\n"
"Last-Translator: Ray Chen Process ID number is a number that uniquely identifies one specific process or running program (this number is valid only during the lifetime of that process).<br><br> <b>Severity Level:</b> Select the lowest severity level for security events that you would like to be included in the report. The selected severity level, and above, will be included in the reports.<br><br> <b>Detail:</b> A source to which the profile has denied access. This includes capabilities and files. You can use this field to report the resources are not allowed to be accessed by profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile grants to the program or process to which it is applied. The options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type describes what is actually happening with the security event. The options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated values) or ht
ml file. The CSV file separates pieces of data in the log entries with commas using a standard data format for importing into table-oriented applications. You can enter a pathname for your exported report by typing in the full pathname in the field provided.</p>"
+#~ msgstr "「報告組態」對話方塊可讓您過濾在前一畫面選取的已歸檔報告。 根據<b>日期範圍</b>過濾:<br><br> <ol> <li>按一下<b>根據日期範圍過濾</b>。 相關欄位會變成作用中狀態。 <li>請輸入定義報告範圍的開始與結束日期。 <li>輸入其他要過濾的參數。 請參閱以下參數的定義。 </ol>以下定義可協助您在「報告組態」對話方塊輸入過濾參數: <br><br> <b>程式名稱模式:</b> 當您輸入符合欲過濾的二進位執行檔名稱的程式名稱或模式後,報告將會顯示特定程式已發生的安全事件。<br><br> <b>設定檔名稱模式: </b>當您輸入設定檔的名稱,報告將會顯示特定設定檔所產生的安全事件。 您可以使用此報告內容來檢視已被特定設定檔限制的項目。<br><br> <b>PID 號碼:</b> 程序 ID 號碼是獨特的號碼,可用來識別某一特定程序或執行中的程式 (此號碼只有在程序的�
��命期間才是有效的)。<br><br> <b>嚴重性層級: </b> 選取您要納入報告中的最低等級安全事件嚴重性。 所選取的嚴重性及以上的層級會納入報告中。<br><br> <b>詳細資料: </b> 設定檔已拒絕存取的來源。 其中包涵功能與檔案。 您可以使用此欄位來報告被設定檔拒絕存取的來源。<br><br> <b>模式: </b>模式是設定檔授予所適用之程式或程序的許可。 選項為: r (讀取) w (寫入) l (連結) x (執行)<br><br> <b>存取類型:</b> 存取類型說明在安全事件中實際發生的情況。 選項為: PERMITTING (許可)、REJECTING (拒絕)或 AUDITING (稽核)。<br><br> <b>CSV 或 HTML: </b> 可讓您輸出 CSV (逗點分隔,comma separated values) 或 HTML 檔案。 CSV 檔案會使用標準資料格式,以逗號分隔記錄項目中的各筆資料,以便輸入表格導向的應用程式。 您可以在提供的欄位中鍵入完整的路徑名稱,以輸入�
��所輸出的報告的路徑。" #, fuzzy
-#~ msgid ""
-#~ "<p>The AppArmor On-Demand Report screen displays an instantly generated "
-#~ "version of one of the following reports. <b>Executive Security Summary:"
-#~ "b> A combined report, consisting of one or more Security incident reports "
-#~ "from one or more machines. This report provides a single view of "
-#~ "security events on multiple machines.<br><br> <b>Applications Audit "
-#~ "Report:</b> An auditing tool that reports which application servers are "
-#~ "running and whether the applications are confined by AppArmor. "
-#~ "Application servers are applications that accept incoming network "
-#~ "connections. <br><br> <b>Security Incident Report:</b> A report that "
-#~ "displays application security for a single host. It reports policy "
-#~ "violations for locally confined applications during a specific time "
-#~ "period. You can edit and customize this report, or add new versions.</p>"
-#~ msgstr ""
-#~ "AppArmor On-Demand 報告畫面會以即時產生的方式顯示下列報告之一。 <b>執行安"
-#~ "全摘要:</b>一種綜合報告,包含來自一或多部電腦的一或多個安全事件報告。 此"
-#~ "報告提供單一檢視畫面,讓您檢視多台電腦上的安全事件。<b>應用程式稽核報告:"
-#~ "</b>一種稽核工具,報告有哪些應用程式伺服器正在執行,以及有哪些應用程式受"
-#~ "到 AppArmor 的限制。應用程式伺服器是可接受外來網路連線的應用程式。"
-#~ "<br><br> <b>安全事件報告:</b>一種報告,顯示單一主機的應用程式安全性。 它"
-#~ "會顯示特定期間內違反本機應用程式限制政策的情形。您可以編輯及自訂此報告或新"
-#~ "增新的版本。"
+#~ msgid "<p>The AppArmor On-Demand Report screen displays an instantly generated version of one of the following reports. <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally confined applications during a specific time period. You can edit and customize this report, or add new versions.</p>"
+#~ msgstr "AppArmor On-Demand 報告畫面會以即時產生的方式顯示下列報告之一。 <b>執行安全摘要:</b>一種綜合報告,包含來自一或多部電腦的一或多個安全事件報告。 此報告提供單一檢視畫面,讓您檢視多台電腦上的安全事件。<b>應用程式稽核報告:</b>一種稽核工具,報告有哪些應用程式伺服器正在執行,以及有哪些應用程式受到 AppArmor 的限制。應用程式伺服器是可接受外來網路連線的應用程式。<br><br> <b>安全事件報告:</b>一種報告,顯示單一主機的應用程式安全性。 它會顯示特定期間內違反本機應用程式限制政策的情形。您可以編輯及自訂此報告或新增新的版本。"
#, fuzzy
-#~ msgid ""
-#~ "<p>The Report Configuration dialog enables you to filter the report "
-#~ "selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
-#~ "<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
-#~ "<li>Enter the start and end dates that delineate the scope of the "
-#~ "report. <li>Enter other filtering parameters. See below for definitions "
-#~ "of parameters. </ol> The following definitions help you to enter the "
-#~ "filtering parameters in the Report Configuration Dialog: <b>Program Name "
-#~ "Pattern:</b> When you enter a program name or pattern that matches the "
-#~ "name of the executable process of interest, the report will display "
-#~ "security events that have occurred for a specific program.<br><br> "
-#~ "<b>Profile Name Pattern:</b> When you enter the name of the security "
-#~ "profile that is applied to the process, the report will display the "
-#~ "security events that are generated for the specified profile. You can use "
-#~ "this to see what is being confined by a specific profile.<br><br> <b>PID "
-#~ "Number:</b> Process ID number is a number that uniquely identifies one "
-#~ "specific process or running program (this number is valid only during the "
-#~ "lifetime of that process).<br><br> <b>Severity Level:</b> Select the "
-#~ "lowest severity level for security events that you would like to be "
-#~ "included in the report. The selected severity level, and above, will be "
-#~ "included in the reports.<br><br> <b>Detail:</b> A source to which the "
-#~ "profile has denied access. This includes capabilities and files. You can "
-#~ "use this field to report the resources are not allowed to be accessed by "
-#~ "profiles.<br><br> <b>Mode:</b> The Mode is the permission that the "
-#~ "profile grants to the program or process to which it is applied. The "
-#~ "options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access "
-#~ "Type:</b> The access type describes what is actually happening with the "
-#~ "security event. The options are: PERMITTING, REJECTING, or AUDITING."
-#~ "<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated "
-#~ "values) or HTML file. The CSV file separates pieces of data in the log "
-#~ "entries with commas using a standard data format for importing into table-"
-#~ "oriented applications. You can enter a pathname for your exported report "
-#~ "by typing in the full pathname in the field provided.</p>"
-#~ msgstr ""
-#~ "「報告組態」對話方塊可讓您過濾在前一畫面選取的報告。根據<b>日期範圍</b>過"
-#~ "濾:<br><br> <ol> <li>按一下<b>根據日期範圍過濾</b>。相關欄位會變成作用中"
-#~ "狀態。 <li>請輸入定義報告範圍的開始與結束日期。 <li>輸入其他要過濾的參數。"
-#~ "請參閱以下參數的定義。 </ol>以下定義可協助您在「報告組態」對話方塊輸入過濾"
-#~ "參數: <b>程式名稱模式:</b> 當您輸入符合欲過濾的執行程序名稱的程式名稱或"
-#~ "模式後,報告將會顯示特定程式已發生的安全事件。<br><br> <b>設定檔名稱模式:"
-#~ "</b>當您輸入套用到程序的安全設定檔名稱後,報告將會顯示特定設定檔所產生的安"
-#~ "全事件。您可以使用此報告內容來檢視已被特定設定檔限制的項目。<br><br> "
-#~ "<b>PID 號碼:</b> 程序 ID 號碼是獨特的號碼,可用來識別某一特定程序或執行中"
-#~ "的程式 (此號碼只有在程序的生命期間才是有效的)。<br><br> <b>嚴重性層級:"
-#~ "b> 選取您要納入報告中的最低等級安全事件嚴重性。所選取的嚴重性及以上的層級"
-#~ "會納入報告中。<br><br> <b>詳細資料:</b> 設定檔已拒絕存取的來源。 其中包"
-#~ "涵功能與檔案。您可以使用此欄位來報告被設定檔拒絕存取的來源。<br><br> <b>模"
-#~ "式:</b>模式是設定檔授與所適用之程式或程序的許可。選項為: r (讀取) w (寫"
-#~ "入) l (連結) x (執行)<br><br> <b>存取類型:</b> 存取類型說明在安全事件中實"
-#~ "際發生的情況。選項為: PERMITTING (許可)、REJECTING (拒絕)或 AUDITING (稽"
-#~ "核)。<br><br> <b>CSV 或 HTML:</b> 可讓您輸出 CSV (逗點分隔,comma "
-#~ "separated values) 或 HTML 檔案。CSV 檔案會使用標準資料格式,以逗號分隔記錄"
-#~ "項目中的各筆資料,以便輸入表格導向的應用程式。您可以在提供的欄位中鍵入完整"
-#~ "的路徑名稱,以輸入您所輸出的報告的路徑。<br><br>"
+#~ msgid "<p>The Report Configuration dialog enables you to filter the report selected in the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become active. <li>Enter the start and end dates that delineate the scope of the report. <li>Enter other filtering parameters. See below for definitions of parameters. </ol> The following definitions help you to enter the filtering parameters in the Report Configuration Dialog: <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the executable process of interest, the report will display security events that have occurred for a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the name of the security profile that is applied to the process, the report will display the security events that are generated for the specified profile. You can use this to see what is being confined by a specific profile.<br><br> <b>PID Num
ber:</b> Process ID number is a number that uniquely identifies one specific process or running program (this number is valid only during the lifetime of that process).<br><br> <b>Severity Level:</b> Select the lowest severity level for security events that you would like to be included in the report. The selected severity level, and above, will be included in the reports.<br><br> <b>Detail:</b> A source to which the profile has denied access. This includes capabilities and files. You can use this field to report the resources are not allowed to be accessed by profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile grants to the program or process to which it is applied. The options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type describes what is actually happening with the security event. The options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated values
) or HTML file. The CSV file separates pieces of data in the log entries with commas using a standard data format for importing into table-oriented applications. You can enter a pathname for your exported report by typing in the full pathname in the field provided.</p>"
+#~ msgstr "「報告組態」對話方塊可讓您過濾在前一畫面選取的報告。根據<b>日期範圍</b>過濾:<br><br> <ol> <li>按一下<b>根據日期範圍過濾</b>。相關欄位會變成作用中狀態。 <li>請輸入定義報告範圍的開始與結束日期。 <li>輸入其他要過濾的參數。請參閱以下參數的定義。 </ol>以下定義可協助您在「報告組態」對話方塊輸入過濾參數: <b>程式名稱模式:</b> 當您輸入符合欲過濾的執行程序名稱的程式名稱或模式後,報告將會顯示特定程式已發生的安全事件。<br><br> <b>設定檔名稱模式:</b>當您輸入套用到程序的安全設定檔名稱後,報告將會顯示特定設定檔所產生的安全事件。您可以使用此報告內容來檢視已被特定設定檔限制的項目。<br><br> <b>PID 號碼:</b> 程序 ID 號碼是獨特的號碼,可用來識別某一特定程序或執行中的程式 (此號碼只有在程序的生命期�
��才是有效的)。<br><br> <b>嚴重性層級:</b> 選取您要納入報告中的最低等級安全事件嚴重性。所選取的嚴重性及以上的層級會納入報告中。<br><br> <b>詳細資料:</b> 設定檔已拒絕存取的來源。 其中包涵功能與檔案。您可以使用此欄位來報告被設定檔拒絕存取的來源。<br><br> <b>模式:</b>模式是設定檔授與所適用之程式或程序的許可。選項為: r (讀取) w (寫入) l (連結) x (執行)<br><br> <b>存取類型:</b> 存取類型說明在安全事件中實際發生的情況。選項為: PERMITTING (許可)、REJECTING (拒絕)或 AUDITING (稽核)。<br><br> <b>CSV 或 HTML:</b> 可讓您輸出 CSV (逗點分隔,comma separated values) 或 HTML 檔案。CSV 檔案會使用標準資料格式,以逗號分隔記錄項目中的各筆資料,以便輸入表格導向的應用程式。您可以在提供的欄位中鍵入完整的路徑名稱,以輸入您所輸出的報告
的路徑。<br><br>"
#, fuzzy
-#~ msgid ""
-#~ "<p>The summary of scheduled reports page shows us when reports are "
-#~ "scheduled to run. Reports can be set to run monthly, weekly, daily, or "
-#~ "hourly. The default settings are daily at midnight. The reports can also "
-#~ "be emailed, upon completion, to up to three email recipients.<br><br> In "
-#~ "the Set Schedule section, you can schedule the following three types of "
-#~ "security reports:<br><br> <b>Executive Security Summary:</b> A combined "
-#~ "report, consisting of one or more Security incident reports from one or "
-#~ "more machines. This report provides a single view of security events on "
-#~ "multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing "
-#~ "tool that reports which application servers are running and whether the "
-#~ "applications are confined by AppArmor. Application servers are "
-#~ "applications that accept incoming network connections. <br><br> "
-#~ "<b>Security Incident Report:</b> A report that displays application "
-#~ "security for a single host. It reports policy violations for locally "
-#~ "confined applications during a specific time period. You can edit and "
-#~ "customize this report, or add new versions.</p>"
-#~ msgstr ""
-#~ "已排程報告頁面的摘要會顯示排程,告訴您何時執行報告。您可設定每月、每週、每"
-#~ "日或每小時執行一次報告。預設值是設定於每天午夜。報告完成之後亦可透過電子郵"
-#~ "件傳送,最多可傳送給三位收件者。<br><br> 在「設定排程」區段,您可以排程下"
-#~ "列三種類型的安全報告:<br><br> <b>執行安全摘要:</b>一種綜合報告,包含來自"
-#~ "一或多部電腦的一或多個安全事件報告。 此報告提供單一檢視畫面,讓您檢視多台"
-#~ "電腦上的安全事件。<b>應用程式稽核報告:</b>一種稽核工具,報告有哪些應用程"
-#~ "式伺服器正在執行,以及有哪些應用程式受到 AppArmor 的限制。應用程式伺服器是"
-#~ "可接受外來網路連線的應用程式。<br><br> <b>安全事件報告:</b>一種報告,顯示"
-#~ "單一主機的應用程式安全性。 它會顯示特定期間內違反本機應用程式限制政策的情"
-#~ "形。您可以編輯及自訂此報告或新增新的版本。"
+#~ msgid "<p>The summary of scheduled reports page shows us when reports are scheduled to run. Reports can be set to run monthly, weekly, daily, or hourly. The default settings are daily at midnight. The reports can also be emailed, upon completion, to up to three email recipients.<br><br> In the Set Schedule section, you can schedule the following three types of security reports:<br><br> <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally conf
ined applications during a specific time period. You can edit and customize this report, or add new versions.</p>"
+#~ msgstr "已排程報告頁面的摘要會顯示排程,告訴您何時執行報告。您可設定每月、每週、每日或每小時執行一次報告。預設值是設定於每天午夜。報告完成之後亦可透過電子郵件傳送,最多可傳送給三位收件者。<br><br> 在「設定排程」區段,您可以排程下列三種類型的安全報告:<br><br> <b>執行安全摘要:</b>一種綜合報告,包含來自一或多部電腦的一或多個安全事件報告。 此報告提供單一檢視畫面,讓您檢視多台電腦上的安全事件。<b>應用程式稽核報告:</b>一種稽核工具,報告有哪些應用程式伺服器正在執行,以及有哪些應用程式受到 AppArmor 的限制。應用程式伺服器是可接受外來網路連線的應用程式。<br><br> <b>安全事件報告:</b>一種報告,顯示單一主機的應用程式安全性。 它會顯示特定期間內違反本機應用程式限制政策的情形。您可以編輯�
�自訂此報告或新增新的版本。"
-#~ msgid ""
-#~ "<p><b>AppArmor Status</b><br>This reports whether the AppArmor policy "
-#~ "enforcement module is loaded and functioning.</p> <p><b>Security Event "
-#~ "Notification</b><br>Configure this tool if you want to be notified by "
-#~ "email when access violations have occurred.</p> <p><b>Profile Modes"
-#~ "b><br>Use this tool to change the way that AppArmor uses individual "
-#~ "profiles.</p>"
-#~ msgstr ""
-#~ "<p><b>AppArmor 狀態</b><br>報告 AppArmor 政策執行模組是否已經載入並且在執"
-#~ "行中。</p> <p><b>安全事件通知</b><br>如果您希望在發生存取違規時收到電子郵"
-#~ "件通知,請設定此工具。</p> <p><b>設定檔模式</b><br>請使用此工具來改變 "
-#~ "AppArmor 對個別設定檔的使用方式。</p>"
+#~ msgid "<p><b>AppArmor Status</b><br>This reports whether the AppArmor policy enforcement module is loaded and functioning.</p> <p><b>Security Event Notification</b><br>Configure this tool if you want to be notified by email when access violations have occurred.</p> <p><b>Profile Modes</b><br>Use this tool to change the way that AppArmor uses individual profiles.</p>"
+#~ msgstr "<p><b>AppArmor 狀態</b><br>報告 AppArmor 政策執行模組是否已經載入並且在執行中。</p> <p><b>安全事件通知</b><br>如果您希望在發生存取違規時收到電子郵件通知,請設定此工具。</p> <p><b>設定檔模式</b><br>請使用此工具來改變 AppArmor 對個別設定檔的使用方式。</p>"
#~ msgid "Email address is too long. Please enter another address."
#~ msgstr "電子郵件地址太長。請輸入其他地址。"
--
To unsubscribe, e-mail: opensuse-translation-commit+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-translation-commit+owner@opensuse.org\n"
"<dt>* Virtual server port is 21: ftp\n"
@@ -432,9 +324,7 @@
"\n"
"\n"
"</dt><dt><b><big>check command</big> = \"</b><i>path to script</i><b>\"</b>\n"
-"<p>This setting is used if checktype is external and is the command to be "
-"run to check the status of a real server. It should exit with status 0 if "
-"everything\n"
+"<p>This setting is used if checktype is external and is the command to be run to check the status of a real server. It should exit with status 0 if everything\n"
"is ok, or non-zero otherwise.\n"
"</p><p>Four parameters are passed to the script:\n"
"</p></dt><dt>* virtual server ip/firewall mark\n"
@@ -445,105 +335,68 @@
"\n"
"\n"
"<p><b><big>check port</big> =</b> <i>n</i>\n"
-"</p><p>Number of port to monitor. Sometimes check port differs from service "
-"port.\n"
+"</p><p>Number of port to monitor. Sometimes check port differs from service port.\n"
"</p><p>Default: port specified for each real server\n"
"\n"
"\n"
-"</p><p><b><big>request</big> = \"</b><i>uri to requested object</i><b>\""
-"b>\n"
-"</p><p>This object will be requested each checkinterval seconds on each real "
-"server. The string must be inside quotes. Note that this string may be "
-"overridden by\n"
+"</p><p><b><big>request</big> = \"</b><i>uri to requested object</i><b>\"</b>\n"
+"</p><p>This object will be requested each checkinterval seconds on each real server. The string must be inside quotes. Note that this string may be overridden by\n"
"an optional per real-server based request-string.\n"
-"</p><p>For a <small>DNS</small> check this should the name of an A record, "
-"or the address of a <small>PTR</small> record to look up.\n"
-"</p><p>For a MySQL, Oracle or PostgeSQL check, this should be an <small>SQL"
-"small> query. The data returned is not checked, only that the answer is one "
-"or more\n"
+"</p><p>For a <small>DNS</small> check this should the name of an A record, or the address of a <small>PTR</small> record to look up.\n"
+"</p><p>For a MySQL, Oracle or PostgeSQL check, this should be an <small>SQL</small> query. The data returned is not checked, only that the answer is one or more\n"
"rows. This is a required setting.\n"
-"</p><p>For a simpletcp check, this string is sent verbatim except any "
-"occurances of \n"
+"</p><p>For a simpletcp check, this string is sent verbatim except any occurances of \n"
" are replaced with a new line character.\n"
"\n"
"\n"
"</p><p><b><big>receive</big> = \"</b><i>regexp to compare</i><b>\"</b>\n"
-"</p><p>If the requested result contains this <i>regexp to compare</i>, the "
-"real server is declared alive. The regexp must be inside quotes. Keep in "
-"mind that\n"
-"regexps are not plain strings and that you need to escape the special "
-"characters if they should as literals. Note that this regexp may be "
-"overridden by an\n"
+"</p><p>If the requested result contains this <i>regexp to compare</i>, the real server is declared alive. The regexp must be inside quotes. Keep in mind that\n"
+"regexps are not plain strings and that you need to escape the special characters if they should as literals. Note that this regexp may be overridden by an\n"
"optional per real-server based receive regexp.\n"
-"</p><p>For a <small>DNS</small> check this should be any one the A record's "
-"addresses or any one of the <small>PTR</small> record's names.\n"
+"</p><p>For a <small>DNS</small> check this should be any one the A record's addresses or any one of the <small>PTR</small> record's names.\n"
"</p><p>For a MySQL check, the receive setting is not used.\n"
"\n"
"\n"
-"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD"
-"small></b>\n"
-"</p><p>Sets the <small>HTTP</small> method which should be used to fetch the "
-"<small>URI</small> specified in the request-string. <small>GET</small> is "
-"the\n"
-"method used by default if the parameter is not set. If <small>HEAD</small> "
-"is used, the receive-string should be unset.\n"
+"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD</small></b>\n"
+"</p><p>Sets the <small>HTTP</small> method which should be used to fetch the <small>URI</small> specified in the request-string. <small>GET</small> is the\n"
+"method used by default if the parameter is not set. If <small>HEAD</small> is used, the receive-string should be unset.\n"
"</p><p>Default: <small>GET</small>\n"
"\n"
"\n"
"</p><p><b><big>virtual host</big> = \"</b><i>hostname</i><b>\"</b>\n"
-"</p><p>Used when using a negotiate check with <small>HTTP</small> or "
-"<small>HTTPS</small> . Sets the host header used in the <small>HTTP</small> "
-"request. In the\n"
-"case of <small>HTTPS</small> this generally needs to match the common name "
-"of the <small>SSL</small> certificate. If not set then the host header will "
-"be\n"
-"derived from the request url for the real server if present. As a last "
-"resort the <small>IP</small> address of the real server will be used.\n"
+"</p><p>Used when using a negotiate check with <small>HTTP</small> or <small>HTTPS</small> . Sets the host header used in the <small>HTTP</small> request. In the\n"
+"case of <small>HTTPS</small> this generally needs to match the common name of the <small>SSL</small> certificate. If not set then the host header will be\n"
+"derived from the request url for the real server if present. As a last resort the <small>IP</small> address of the real server will be used.\n"
"\n"
"\n"
"</p><p><b><big>login</big> = \"</b><i>username</i><b>\"</b>\n"
-"</p><p>For <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , "
-"MySQL, Oracle, <small>POP</small> and PostgreSQL, the username used to log "
-"in.\n"
+"</p><p>For <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , MySQL, Oracle, <small>POP</small> and PostgreSQL, the username used to log in.\n"
"</p><p>For Radius the passwd is used for the attribute User-Name.\n"
-"</p><p>For <small>SIP</small> , the username is used as both the to and from "
-"address for an <small>OPTIONS</small> query.\n"
+"</p><p>For <small>SIP</small> , the username is used as both the to and from address for an <small>OPTIONS</small> query.\n"
"</p><p>Default:\n"
"</p></dt><dt>* <small>FTP:</small> Anonymous\n"
-"</dt><dt>* MySQL Oracle, and PostgreSQL: Must be specified in the "
-"configuration\n"
-"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>, hostname is "
-"derived as per the passwd option below.\n"
-"</dt><dt>* Otherwise: empty string, which denotes that case authentication "
-"will not be attempted.\n"
+"</dt><dt>* MySQL Oracle, and PostgreSQL: Must be specified in the configuration\n"
+"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>, hostname is derived as per the passwd option below.\n"
+"</dt><dt>* Otherwise: empty string, which denotes that case authentication will not be attempted.\n"
"\n"
"\n"
"</dt><dt><b><big>password</big> = \"</b><i>password</i><b>\"</b>\n"
-"<p>Password to use to login to <small>FTP</small> , <small>IMAP</small> , "
-"<small>LDAP</small> , MySQL, Oracle, <small>POP</small> , PostgreSQL and\n"
+"<p>Password to use to login to <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , MySQL, Oracle, <small>POP</small> , PostgreSQL and\n"
"<small>SIP</small> servers.\n"
"</p><p>For Radius the passwd is used for the attribute User-Password.\n"
"</p><p>Default:\n"
-"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>, where "
-"hostname is the environment variable <small>HOSTNAME</small> evaluated at "
-"run time, or sourced\n"
+"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>, where hostname is the environment variable <small>HOSTNAME</small> evaluated at run time, or sourced\n"
"from uname if unset.\n"
-"</dt><dt>* Otherwise: empty string. In the case of <small>LDAP</small> , "
-"MySQL, Oracle, and PostgreSQL this means that authentication will not be "
-"performed.\n"
+"</dt><dt>* Otherwise: empty string. In the case of <small>LDAP</small> , MySQL, Oracle, and PostgreSQL this means that authentication will not be performed.\n"
"\n"
"\n"
"</dt><dt><b><big>database name</big> = \"</b><i>databasename</i><b>\"</b>\n"
-"<p>Database to use for MySQL, Oracle and PostgreSQL servers, this is the "
-"database that the query (set by <b>receive</b> above) will be performed "
-"against. This\n"
+"<p>Database to use for MySQL, Oracle and PostgreSQL servers, this is the database that the query (set by <b>receive</b> above) will be performed against. This\n"
"is a required setting.\n"
"\n"
"\n"
"</p><p><b><big>radius secret</big> = \"</b><i>radiussecret</i><b>\"</b>\n"
-"</p><p>Secret to use for Radius servers, this is the secret used to perform "
-"an Access-Request with the username (set by <b>login</b> above) and passwd "
-"(set by\n"
+"</p><p>Secret to use for Radius servers, this is the secret used to perform an Access-Request with the username (set by <b>login</b> above) and passwd (set by\n"
"<b>passwd</b> above).\n"
"</p><p>Default: empty string\n"
"\n"
@@ -557,120 +410,73 @@
"\n"
"\n"
"</p><p><b><big>scheduler</big> =</b> <i>scheduler_name</i>\n"
-"</p><p>Scheduler to be used by <small>LVS</small> for loadbalancing. For an "
-"information on the available sehedulers please see the <b>ipvsadm</a></b>(8) man page.\n"
+"</p><p>Scheduler to be used by <small>LVS</small> for loadbalancing. For an information on the available sehedulers please see the <b>ipvsadm</a></b>(8) man page.\n"
"</p><p>Default: \"wrr\"\n"
"\n"
"\n"
"</p><p><b><big>protocol</big> = tcp</b>|<b>udp</b>|<b>fwm</b>\n"
-"</p><p>Protocol to be used. If the virtual is specified as an <small>IP"
-"small> address and port then it must be one of tcp or udp. If a firewall "
-"mark then the\n"
+"</p><p>Protocol to be used. If the virtual is specified as an <small>IP</small> address and port then it must be one of tcp or udp. If a firewall mark then the\n"
"protocol must be fwm.\n"
"</p><p>Default:\n"
-"</p></dt><dt>* Virtual is an <small>IP</small> address and port, and the "
-"port is not 53: tcp\n"
-"</dt><dt>* Virtual is an <small>IP</small> address and port, and the port is "
-"53: udp\n"
+"</p></dt><dt>* Virtual is an <small>IP</small> address and port, and the port is not 53: tcp\n"
+"</dt><dt>* Virtual is an <small>IP</small> address and port, and the port is 53: udp\n"
"</dt><dt>* Virtual is a firewall mark: fwm\n"
"</dt></dl>\n"
"\n"
"\n"
"</p><p><b><big>check timeout</big> =</b> <i>n</i>\n"
-"</p><p>Timeout in seconds for connect, external and ping checks. If the "
-"timeout is exceeded then the real server is declared dead.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
-"</p><p>If undefined then the value of negotiatetimeout is used. "
-"negotiatetimeout is also a global value that may be overriden by a per-"
-"virtual setting.\n"
-"</p><p>If both checktimeout and negotiatetimeout are unset, the default is "
-"used.\n"
+"</p><p>Timeout in seconds for connect, external and ping checks. If the timeout is exceeded then the real server is declared dead.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
+"</p><p>If undefined then the value of negotiatetimeout is used. negotiatetimeout is also a global value that may be overriden by a per-virtual setting.\n"
+"</p><p>If both checktimeout and negotiatetimeout are unset, the default is used.\n"
"</p><p>Default: 5 seconds\n"
"\n"
"</p><p><b><big>negotiate timeout</big> =</b> <i>n</i>\n"
"</p><p>Timeout in seconds for negotiate checks.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
-"</p><p>If undefined then the value of connecttimeout is used. connecttimeout "
-"is also a global value that may be overriden by a per-virtual setting.\n"
-"</p><p>If both negotiatetimeout and connecttimeout are unset, the default is "
-"used.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
+"</p><p>If undefined then the value of connecttimeout is used. connecttimeout is also a global value that may be overriden by a per-virtual setting.\n"
+"</p><p>If both negotiatetimeout and connecttimeout are unset, the default is used.\n"
"</p><p>Default: 30 seconds\n"
"\n"
"</p><p><b><big>failure count</big> =</b> <i>n</i>\n"
-"</p><p>The number of consecutive times a failure will have to be reported by "
-"a check before the realserver is considered to have failed. A value of 1 "
-"will have the realserver considered failed on the first failure. A "
-"successful check will reset the failure counter to 0.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>The number of consecutive times a failure will have to be reported by a check before the realserver is considered to have failed. A value of 1 will have the realserver considered failed on the first failure. A successful check will reset the failure counter to 0.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: 1\n"
"\n"
"</p><p><b><big>email alert</big> = \"</b><i>emailaddress</i><b>\"</b>\n"
-"</p><p>A valid email address for sending alerts about the changed connection "
-"status to any real server defined in the virtual service. This option "
-"requires perl\n"
-"module MailTools to be installed. Automatically tries to send email using "
-"any of the built-in methods. See perldoc Mail::Mailer for more info on "
-"methods.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>A valid email address for sending alerts about the changed connection status to any real server defined in the virtual service. This option requires perl\n"
+"module MailTools to be installed. Automatically tries to send email using any of the built-in methods. See perldoc Mail::Mailer for more info on methods.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"\n"
"</p><p><b><big>email alert freq</big> =</b> <i>n</i>\n"
-"</p><p>Delay in seconds between repeating email alerts while any given real "
-"server in the virtual service remains inaccessible. A setting of zero "
-"seconds will\n"
-"inhibit the repeating alerts. The email timing accuracy of this setting is "
-"dependent on the number of seconds defined in the checkinterval "
-"configuration\n"
+"</p><p>Delay in seconds between repeating email alerts while any given real server in the virtual service remains inaccessible. A setting of zero seconds will\n"
+"inhibit the repeating alerts. The email timing accuracy of this setting is dependent on the number of seconds defined in the checkinterval configuration\n"
"option.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: 0\n"
"\n"
-"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting"
-"b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
-"</p><p>Comma delimited list of server states in which email alerts should be "
-"sent. <b>all</b> is a short-hand for\n"
-"\"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading</b>\". If "
-"<b>none</b> is specified, no other option may be specified, otherwise "
-"options are ORed\n"
+"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting</b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
+"</p><p>Comma delimited list of server states in which email alerts should be sent. <b>all</b> is a short-hand for\n"
+"\"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading</b>\". If <b>none</b> is specified, no other option may be specified, otherwise options are ORed\n"
"with each other.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: all\n"
"\n"
-"</p><p><b><big>fallback</big> =</b> <i>ip_address|hostname[:portnumber|"
-"sercvicename]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
-"</p><p>the server onto which a webservice is redirected if all real servers "
-"are down. Typically this would be 127.0.0.1 with an emergency page.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p><b><big>fallback</big> =</b> <i>ip_address|hostname[:portnumber|sercvicename]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
+"</p><p>the server onto which a webservice is redirected if all real servers are down. Typically this would be 127.0.0.1 with an emergency page.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"\n"
"</p><p><b><big>quiescent</big> = yes</b>|<b>no</b>\n"
-"</p><p>If <i>yes</i>, then when real or failback servers are determined to "
-"be down, they are not actually removed from the kernel's <small>LVS</small> "
-"table.\n"
-"Rather, their weight is set to zero which means that no new connections will "
-"be accepted.\n"
-"</p><p>This has the side effect, that if the real server has persistent "
-"connections, new connections from any existing clients will continue to be "
-"routed to the\n"
-"real server, until the persistant timeout can expire. See ipvsadm for more "
-"information on persistant connections.\n"
+"</p><p>If <i>yes</i>, then when real or failback servers are determined to be down, they are not actually removed from the kernel's <small>LVS</small> table.\n"
+"Rather, their weight is set to zero which means that no new connections will be accepted.\n"
+"</p><p>This has the side effect, that if the real server has persistent connections, new connections from any existing clients will continue to be routed to the\n"
+"real server, until the persistant timeout can expire. See ipvsadm for more information on persistant connections.\n"
"</p><p>This side-effect can be avoided by running the following:\n"
"</p><p>echo 1 > /proc/sys/net/ipv4/vs/expire_quiescent_template\n"
-"</p><p>If the proc file isn't present this probably means that the kernel "
-"doesn't have lvs support, <small>LVS</small> support isn't loaded, or the "
-"kernel is too\n"
-"old to have the proc file. Running ipvsadm as root should load <small>LVS"
-"small> into the kernel if it is possible.\n"
-"</p><p>If <i>no</i>, then the real or failback servers will be removed from "
-"the kernel's <small>LVS</small> table. The default is <i>yes</i>.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If the proc file isn't present this probably means that the kernel doesn't have lvs support, <small>LVS</small> support isn't loaded, or the kernel is too\n"
+"old to have the proc file. Running ipvsadm as root should load <small>LVS</small> into the kernel if it is possible.\n"
+"</p><p>If <i>no</i>, then the real or failback servers will be removed from the kernel's <small>LVS</small> table. The default is <i>yes</i>.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: <i>yes</i>\n"
"\n"
"\n"
@@ -688,7 +494,7 @@
#: src/include/iplb/vserver_conf.rb:151
msgid "Service"
-msgstr ""
+msgstr "服務"
#: src/include/iplb/vserver_conf.rb:152
msgid "Check Command"
@@ -700,7 +506,7 @@
#: src/include/iplb/vserver_conf.rb:160
msgid "Request"
-msgstr ""
+msgstr "要求"
#: src/include/iplb/vserver_conf.rb:162
msgid "Receive"
@@ -712,11 +518,11 @@
#: src/include/iplb/vserver_conf.rb:177
msgid "Login"
-msgstr ""
+msgstr "登入"
#: src/include/iplb/vserver_conf.rb:178
msgid "Password"
-msgstr ""
+msgstr "密碼"
#: src/include/iplb/vserver_conf.rb:180
msgid "Database Name"
@@ -732,7 +538,7 @@
#: src/include/iplb/vserver_conf.rb:200
msgid "Netmask"
-msgstr ""
+msgstr "網路遮罩"
#: src/include/iplb/vserver_conf.rb:202
msgid "Scheduler"
@@ -740,7 +546,7 @@
#: src/include/iplb/vserver_conf.rb:211
msgid "Protocol"
-msgstr ""
+msgstr "協定"
#: src/include/iplb/vserver_conf.rb:231
msgid "Virtual Servers"
@@ -748,15 +554,15 @@
#: src/include/iplb/vserver_conf.rb:234 src/include/iplb/vserver_conf.rb:301
msgid "Add"
-msgstr ""
+msgstr "新增"
#: src/include/iplb/vserver_conf.rb:235 src/include/iplb/vserver_conf.rb:303
msgid "Edit"
-msgstr ""
+msgstr "編輯"
#: src/include/iplb/vserver_conf.rb:236 src/include/iplb/vserver_conf.rb:302
msgid "Delete"
-msgstr ""
+msgstr "刪除"
#. disable the delete & edit button if vserver box is empty
#: src/include/iplb/vserver_conf.rb:296
@@ -782,11 +588,11 @@
#. return `cacel or a string
#: src/include/iplb/vserver_conf.rb:342 src/include/iplb/vserver_conf.rb:427
msgid "OK"
-msgstr ""
+msgstr "確定"
#: src/include/iplb/vserver_conf.rb:343 src/include/iplb/vserver_conf.rb:428
msgid "Cancel"
-msgstr ""
+msgstr "取消"
#. split the real server ip value;
#: src/include/iplb/vserver_conf.rb:411
@@ -824,7 +630,7 @@
#. Initialization dialog contents
#: src/include/iplb/wizards.rb:142
msgid "Initializing..."
-msgstr ""
+msgstr "正在啟始化..."
#. Read all iplb settings
#. @return true on success
@@ -851,7 +657,7 @@
#: src/modules/Iplb.rb:225 src/modules/Iplb.rb:330
msgid "Finished"
-msgstr ""
+msgstr "已完成"
#. Write all iplb settings
#. @return true on success
@@ -861,19 +667,19 @@
#: src/modules/Iplb.rb:326
msgid "Write the settings"
-msgstr ""
+msgstr "寫入設定"
#: src/modules/Iplb.rb:326
msgid "Run SuSEconfig"
-msgstr ""
+msgstr "執行 SuSEconfig"
#: src/modules/Iplb.rb:328
msgid "Writing the settings..."
-msgstr ""
+msgstr "正在寫入設定..."
#: src/modules/Iplb.rb:329
msgid "Running SuSEconfig..."
-msgstr ""
+msgstr "正在執行 SuSEconfig..."
#. write global conf
#. check for ipv6 address to decide whether to add "6=" or "="
@@ -883,10 +689,10 @@
#. to check whether it is an ipv6 address;
#: src/modules/Iplb.rb:355 src/modules/Iplb.rb:392 src/modules/Iplb.rb:405
msgid "Cannot write settings."
-msgstr ""
+msgstr "無法寫入設定。"
#. TODO FIXME: your code here...
#. Configuration summary text for autoyast
#: src/modules/Iplb.rb:441
msgid "Configuration summary..."
-msgstr ""
+msgstr "組態摘要..."
Modified: trunk/yast/zh_TW/po/iscsi-client.zh_TW.po
===================================================================
--- trunk/yast/zh_TW/po/iscsi-client.zh_TW.po 2014-10-07 15:59:55 UTC (rev 89801)
+++ trunk/yast/zh_TW/po/iscsi-client.zh_TW.po 2014-10-07 16:00:49 UTC (rev 89802)
@@ -11,7 +11,7 @@
msgstr ""
"Project-Id-Version: iscsi-client\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-23 15:42+0200\n"
+"POT-Creation-Date: 2014-07-04 15:52+0200\n"
"PO-Revision-Date: 2012-05-18 13:36+0800\n"
"Last-Translator: Ray Chen
<li>Select <b>Include unknown security events</b> if you would like "
-#~ "to include events that are not rated with a severity number.</li> </ol>"
-#~ msgstr ""
-#~ "「安全性事件通知」畫面可以用來設定安全性事件的電子郵件警示。請依照下面步驟"
-#~ "執行,指定警示的發出頻率、哪些人員要接收警示,以及在哪種安全性事件嚴重程度"
-#~ "時必須發出警示。<br><br><b>通知類型</b><br> <b>精簡通知:</b>精簡通知僅摘"
-#~ "要報告系統事件的總數,且不提供詳細資訊。<br>範例:<br> dhcp-101.up.wirex."
-#~ "com has had 10 security events since Tue Oct 12 11:10:00 2004<br><br> <b>"
-#~ "摘要通知:</b>摘要通知會顯示已記錄的 安全性事件,並列出個別的發生次數,包"
-#~ "含最後一次發生的日期。<br>範例:<br> SubDomain: PERMITTING access to "
-#~ "capability 'setgid' (httpd2-prefork(6347) profile /usr/sbin/httpd2-"
-#~ "prefork active /usr/sbin/httpd2-prefork) 2 times, the latest at Sat Oct "
-#~ "9 16:05:54 2004.<br><br> <b>詳細通知:</b>詳細通知會顯示尚未修改的已記錄 "
-#~ "Novell AppArmor 安全性事件。每次發生事件時都會通知您,並在詳細記錄中寫入新"
-#~ "行。這些安全性事件包含事件發生的日期和時間、應用程式設定檔允許和拒絕存取的"
-#~ "時間,以及允許或拒絕的檔案存取許可權類型。詳細通知也會報告 logprof 工具用"
-#~ "來解譯設定檔的數種訊息。<br>範例:<br> Oct 9 15:40:31 SubDomain: "
-#~ "PERMITTING r access to /etc/apache2/httpd.conf (httpd2-prefork(6068) "
-#~ "profile /usr/sbin/httpd2-prefork active /usr/sbin/httpd2-prefork)
<br><br> <li>選取應該要發出通知的最低「<b>嚴重性</b>」。當發生的事件等"
-#~ "於或大於選擇的嚴重程度時,系統會按照指定的時間間隔來記錄安全性事件並傳送通"
-#~ "知。如果間隔為 1 天,當發生安全性事件實,每天都會傳送一則通知。<br><br> "
-#~ "<b>嚴重性:</b>這些事件會以 0 到 10 來編號,10 代表最嚴重的安全性事件。"
-#~ "<b>severity.db</b> 檔案會定義潛在安全性事件的嚴重程度。嚴重程度是根據不同"
-#~ "安全性事件的威脅或重要性來決定,例如某些存取的資源或拒絕的服務。</li> <li>"
-#~ "若要在事件報告中包含未提供嚴重性評等數字的事件,請選取「<b>包含未知嚴重程"
-#~ "度事件</b>」。</li> </ol>"
+#~ msgid "The Security Event Notification screen enables you to setup email alerts for security events. In the following steps, specify how often alerts are sent, who receives the alert, and how severe the security event must be to send an alert. <br><br><b>Notification Types</b><br> <b>Terse Notification:</b> Terse notification summarizes the total number of system events without providing details. <br>For example:<br> dhcp-101.up.wirex.com has had 10 security events since Tue Oct 12 11:10:00 2004<br><br> <b>Summary Notification:</b> The Summary notification displays the logged AppArmor security events, and lists the number of individual occurrences, including the date of the last occurrence. <br>For example:<br> SubDomain: PERMITTING access to capability 'setgid' (httpd2-prefork(6347) profile /usr/sbin/httpd2-prefork active /usr/sbin/httpd2-prefork) 2 times, the latest at Sat Oct 9 16:05:54 2004.<br><br> <b>Verbose Notification:</b> The Verbose notification displays unmodified
, logged AppArmor security events. It tells you every time an event occurs and writes a new line in the Verbose log. These security events include the date and time the event occurred, when the application profile permits access as well as rejects access, and the type of file permission access that is permitted or rejected. Verbose Notification also reports several messages that the logprof tool uses to interpret profiles. <br>For example:<br> Oct 9 15:40:31 SubDomain: PERMITTING r access to /etc/apache2/httpd.conf (httpd2-prefork(6068) profile /usr/sbin/httpd2-prefork active /usr/sbin/httpd2-prefork)
<br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become "
-#~ "active. <li>Enter the start and end dates that delineate the scope of "
-#~ "the report. <li>Enter other filtering parameters. See below for "
-#~ "definitions of parameters. </ol> The following definitions help you to "
-#~ "enter the filtering parameters in the Report Configuration Dialog: "
-#~ "<br><br> <b>Program Name Pattern:</b> When you enter a program name or "
-#~ "pattern that matches the name of the binary executable of the program of "
-#~ "interest, the report will display security events that have occurred for "
-#~ "a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter "
-#~ "the name of the profile, the report will display the security events that "
-#~ "are generated for the specified profile. You can use this to see what is "
-#~ "being confined by a specific profile.<br><br> <b>PID Number:</b> Process "
-#~ "ID number is a number that uniquely identifies one specific process or "
-#~ "running program (this number is valid only during the lifetime of that "
-#~ "process).<br><br> <b>Severity Level:</b> Select the lowest severity "
-#~ "level for security events that you would like to be included in the "
-#~ "report. The selected severity level, and above, will be included in the "
-#~ "reports.<br><br> <b>Detail:</b> A source to which the profile has denied "
-#~ "access. This includes capabilities and files. You can use this field to "
-#~ "report the resources are not allowed to be accessed by profiles.<br><br> "
-#~ "<b>Mode:</b> The Mode is the permission that the profile grants to the "
-#~ "program or process to which it is applied. The options are: r (read) w "
-#~ "(write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type "
-#~ "describes what is actually happening with the security event. The options "
-#~ "are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
-#~ "Enables you to export a CSV (comma separated values) or html file. The "
-#~ "CSV file separates pieces of data in the log entries with commas using a "
-#~ "standard data format for importing into table-oriented applications. You "
-#~ "can enter a pathname for your exported report by typing in the full "
-#~ "pathname in the field provided.</p>"
-#~ msgstr ""
-#~ "「報告組態」對話方塊可讓您過濾在前一畫面選取的已歸檔報告。 根據<b>日期範圍"
-#~ "</b>過濾:<br><br> <ol> <li>按一下<b>根據日期範圍過濾</b>。 相關欄位會變成"
-#~ "作用中狀態。 <li>請輸入定義報告範圍的開始與結束日期。 <li>輸入其他要過濾"
-#~ "的參數。 請參閱以下參數的定義。 </ol>以下定義可協助您在「報告組態」對話方"
-#~ "塊輸入過濾參數: <br><br> <b>程式名稱模式:</b> 當您輸入符合欲過濾的二進位"
-#~ "執行檔名稱的程式名稱或模式後,報告將會顯示特定程式已發生的安全事件。"
-#~ "<br><br> <b>設定檔名稱模式: </b>當您輸入設定檔的名稱,報告將會顯示特定設"
-#~ "定檔所產生的安全事件。 您可以使用此報告內容來檢視已被特定設定檔限制的項"
-#~ "目。<br><br> <b>PID 號碼:</b> 程序 ID 號碼是獨特的號碼,可用來識別某一特"
-#~ "定程序或執行中的程式 (此號碼只有在程序的生命期間才是有效的)。<br><br> <b>"
-#~ "嚴重性層級: </b> 選取您要納入報告中的最低等級安全事件嚴重性。 所選取的嚴"
-#~ "重性及以上的層級會納入報告中。<br><br> <b>詳細資料: </b> 設定檔已拒絕存"
-#~ "取的來源。 其中包涵功能與檔案。 您可以使用此欄位來報告被設定檔拒絕存取的"
-#~ "來源。<br><br> <b>模式: </b>模式是設定檔授予所適用之程式或程序的許可。 選"
-#~ "項為: r (讀取) w (寫入) l (連結) x (執行)<br><br> <b>存取類型:</b> 存取"
-#~ "類型說明在安全事件中實際發生的情況。 選項為: PERMITTING (許可)、"
-#~ "REJECTING (拒絕)或 AUDITING (稽核)。<br><br> <b>CSV 或 HTML: </b> 可讓您"
-#~ "輸出 CSV (逗點分隔,comma separated values) 或 HTML 檔案。 CSV 檔案會使用"
-#~ "標準資料格式,以逗號分隔記錄項目中的各筆資料,以便輸入表格導向的應用程"
-#~ "式。 您可以在提供的欄位中鍵入完整的路徑名稱,以輸入您所輸出的報告的路徑。"
+#~ msgid "<p>The Report Configuration dialog enables you to filter the archived report selected in the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become active. <li>Enter the start and end dates that delineate the scope of the report. <li>Enter other filtering parameters. See below for definitions of parameters. </ol> The following definitions help you to enter the filtering parameters in the Report Configuration Dialog: <br><br> <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the binary executable of the program of interest, the report will display security events that have occurred for a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the name of the profile, the report will display the security events that are generated for the specified profile. You can use this to see what is being confined by a specific profile.<br><br> <b>PID Number: