[opensuse-translation-commit] r90541 - trunk/lcn/zh_TW/po
Author: keichwa Date: 2014-10-30 10:37:20 +0100 (Thu, 30 Oct 2014) New Revision: 90541 Modified: trunk/lcn/zh_TW/po/RELEASE-NOTES-openSUSE.zh_TW.po Log: mergedmerged Modified: trunk/lcn/zh_TW/po/RELEASE-NOTES-openSUSE.zh_TW.po =================================================================== --- trunk/lcn/zh_TW/po/RELEASE-NOTES-openSUSE.zh_TW.po 2014-10-30 09:37:17 UTC (rev 90540) +++ trunk/lcn/zh_TW/po/RELEASE-NOTES-openSUSE.zh_TW.po 2014-10-30 09:37:20 UTC (rev 90541) @@ -2,10 +2,11 @@ msgid "" msgstr "" "Project-Id-Version: RELEASE-NOTES\n" -"POT-Creation-Date: 2014-07-28 11:14+0200\n" +"POT-Creation-Date: 2014-10-30 10:31+0100\n" "PO-Revision-Date: 2014-10-19 22:47+0800\n" "Last-Translator: Ramax Lo <ramaxlo@gmail.com>\n" "Language-Team: Chinese Traditional <kde-i18n-doc@kde.org>\n" +"Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -26,286 +27,206 @@ msgid "13.2" msgstr "13.2" -#: xml/release-notes.xml:16(para) +#: xml/release-notes.xml:17(para) msgid "openSUSE is a free and Linux-based operating system for your PC, Laptop or Server. You can surf the web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!" msgstr "openSUSE 是一個自由的基於 Linux 的作業系統,可運作在您的桌上型電腦、筆記型電腦或是伺服器。您可以用它來瀏覽網頁、管理您的電子郵件與相片、進行生產力工作、播放影片或音樂。使用它讓您充滿樂趣。" #. Previous Release Notes -#: xml/release-notes.xml:49(para) +#: xml/release-notes.xml:51(para) msgid "If you upgrade from an older version to this openSUSE release, see previous release notes listed here: <ulink url=\"http://en.opensuse.org/openSUSE:Release_Notes\"/>" msgstr "如果您從較舊的 openSUSE 發行版本升級,請由此查看之前的發行紀事: <ulink url=\"http://en.opensuse.org/openSUSE:Release_Notes\"/>" -#: xml/release-notes.xml:86(title) +#: xml/release-notes.xml:90(title) msgid "Installation" msgstr "安裝" -#: xml/release-notes.xml:89(title) -msgid "For Detailed Installation Information" -msgstr "詳細安裝資訊" - -#: xml/release-notes.xml:91(para) -msgid "For detailed installation information, see <xref linkend=\"sec.123.documentation\"/>." -msgstr "欲了解細節的安裝資訊,請參考 <xref linkend=\"sec.123.documentation\"/>。" - -#: xml/release-notes.xml:97(title) +#: xml/release-notes.xml:103(title) msgid "General" msgstr "一般說明" -#: xml/release-notes.xml:101(title) -msgid "openSUSE Documentation" -msgstr "openSUSE 文件" - -#. <listitem> -#: xml/release-notes.xml:105(para) -msgid "In <emphasis>Start-Up</emphasis>, find step-by-step installation instructions, as well as introductions to the KDE and Gnome desktops and to the LibreOffice suite. Also covered are basic administration topics such as deployment and software management and an introduction to the bash shell." -msgstr "在 <emphasis>新手入門</emphasis> 中您可以找到安裝指南,以及 KDE 和 Gnome 桌面環境與 LibreOffice 辦公室套裝軟體的介紹。另外還包含了基本的系統管理議題,如佈署、軟體管理,以及 bash 的介紹。" - -#. <para> -#. Find the documentation in -#. <filename>/usr/share/doc/manual/opensuse-manuals_$LANG</filename> after -#. installing the package <systemitem>opensuse-manuals_$LANG</systemitem>, -#. or online on <ulink url="http://doc.opensuse.org"/>. -#. </para> -#: xml/release-notes.xml:146(para) -msgid "Find the documentation in <filename>/usr/share/doc/manual/opensuse-manuals_$LANG</filename> after installing the package <systemitem>opensuse-startup_$LANG</systemitem>, or online on <ulink url=\"http://doc.opensuse.org\"/>." -msgstr "您可以在安裝完 <systemitem>opensuse-startup_$LANG</systemitem> 套件後,在 <filename>/usr/share/doc/manual/opensuse-manuals_$LANG</filename> 找到文件,或是直接在線上瀏覽 <ulink url=\"http://doc.opensuse.org\"/>。" - -#: xml/release-notes.xml:160(title) +#: xml/release-notes.xml:172(title) msgid "UEFI—Unified Extensible Firmware Interface" msgstr "UEFI—統一可延伸韌體介面" -#: xml/release-notes.xml:161(para) xml/release-notes.xml:181(para) xml/release-notes.xml:200(para) xml/release-notes.xml:223(para) xml/release-notes.xml:261(para) xml/release-notes.xml:278(para) xml/release-notes.xml:288(para) xml/release-notes.xml:302(para) xml/release-notes.xml:315(para) xml/release-notes.xml:326(para) -msgid "CHECKIT:13.1" -msgstr "" - -#: xml/release-notes.xml:162(para) -msgid "Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI." +#: xml/release-notes.xml:173(para) +#, fuzzy +#| msgid "Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface) you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI." +msgid "Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface), you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installed Windows 8 is a strong indication that your system boots using UEFI." msgstr "在安裝 openSUSE 到使用 UEFI (統一可延伸韌體介面) 開機的系統之前,強烈建議您先詢問是否有硬體製造商所建議的韌體更新並加以安裝。若您的系統有預裝 Windows 8,通常就代表您的系統使用 UEFI 開機。" -#: xml/release-notes.xml:167(para) -msgid "<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much \"too much\" is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless it is recommended to install any firmware updates the hardware vendor recommends." +#: xml/release-notes.xml:181(para) +#, fuzzy +#| msgid "<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much \"too much\" is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless it is recommended to install any firmware updates the hardware vendor recommends." +msgid "<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. Nobody really knows how much \"too much\" is, though. openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux Kernel features that use the UEFI storage area for storing boot and crash information (<literal>pstore</literal>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends." msgstr "<emphasis>背景知識:</emphasis> 有些 UEFI 韌體有缺陷,導致當有太多資料被寫入 UEFI 儲存區域時,韌體會發生問題。但是沒人知道究竟寫入多少資料才算「太多」,故 openSUSE 藉由只寫入能夠啟動系統的最少需要的資料量,來降低這個風險。寫入的資料至少要能告訴 UEFI 韌體 openSUSE 啟動程式的位置。官方 Linux 核心提供使用 UEFI 儲存區來寫入開機及當機資訊的功能 (<literal>pstore</literal>),在此預設被停用。無論如何,建議安裝任何硬體製造商建議的韌體更新。" #. bnc#850056 -#: xml/release-notes.xml:180(title) +#: xml/release-notes.xml:198(title) msgid "UEFI, GPT, and MS-DOS Partitions" msgstr "UEFI,GPT 與 MS-DOS 磁碟分割區。" -#: xml/release-notes.xml:182(para) -msgid "Together with the EFI/UEFI specification a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types." +#: xml/release-notes.xml:199(para) +#, fuzzy +#| msgid "Together with the EFI/UEFI specification a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types." +msgid "Together with the EFI/UEFI specification, a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types." msgstr "在 EFI/UEFI 的規格書中提到一個新的分割磁碟的劃分方式:GPT(GUID Partition Table)。這個新的方式使用 GUID(128位元的值顯示在32個十六進制數字上)來識別裝置及劃分方式。" -#: xml/release-notes.xml:185(para) -msgid "Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB2) try to generate automatically a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consist of two different operation: removing the old entry and creating a new entry that replaces the first one." +#: xml/release-notes.xml:205(para) +#, fuzzy +#| msgid "Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB2) try to generate automatically a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consist of two different operation: removing the old entry and creating a new entry that replaces the first one." +msgid "Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consist of two different operation: removing the old entry and creating a new entry that replaces the first one." msgstr "此外,UEFI 規範是允許傳統的 MBR(MS-DOS)分割區。 Linux 引導加載器(ELILO 或 GRUB2)嘗試自動產生一個 GUID 針對那些傳統的分割區,並把它們寫進軔體。如此一來,一個 GUID 可以更換頻繁,導致軔體的重寫入。一次的重寫入包括兩種不同的操作:刪除舊的項目,以及創建一個新的項目以取代第一個項目。" -#: xml/release-notes.xml:190(para) +#: xml/release-notes.xml:214(para) msgid "Modern firmware has a garbage collector that collects deleted entries and frees the memory reserved for old entries. A problem arises when faulty firmware does not collect and free those entries; this may end up with a non-bootable system." msgstr "現代的軔體都有一個垃圾收集器(garbage collector),可以收集被刪除的進入點(entries),並且釋放記憶體保留給舊的進入點(entries)使用。當故障的軔體不能收集或是釋放這些進入點(entries)時,系統將會出現問題,最終將造成系統無法開機。" -#: xml/release-notes.xml:193(para) +#: xml/release-notes.xml:220(para) msgid "The workaround is simple: convert the legacy MBR partition to the new GPT to avoid this problem completely." msgstr "簡單的替代解決方案是:轉換傳統的 MBR 分割區成為新的 GPT 分割區以完整的避免此問題。" #. bnc#850052 -#: xml/release-notes.xml:199(title) +#: xml/release-notes.xml:228(title) msgid "Booting When in Secure Boot Mode" msgstr "啟動於 Secure Boot 模式下" -#: xml/release-notes.xml:201(para) +#: xml/release-notes.xml:229(para) msgid "This only affects machines in UEFI mode with secure boot enabled." msgstr "這個只會影響到啟用 UEFI Secure Boot 模式的機器。" -#: xml/release-notes.xml:202(para) -msgid "The new version of the shim loader allows more machines to boot with Secure Boot enabled than with openSUSE 12.3. Nevertheless, in case of trouble, first update the BIOS of your machine to the latest version. If the BIOS update does not help, report the model of your machine it the wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for the next release." +#: xml/release-notes.xml:232(para) +#, fuzzy +#| msgid "The new version of the shim loader allows more machines to boot with Secure Boot enabled than with openSUSE 12.3. Nevertheless, in case of trouble, first update the BIOS of your machine to the latest version. If the BIOS update does not help, report the model of your machine it the wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for the next release." +msgid "The new version of the shim loader allows more machines to boot with Secure Boot enabled than with openSUSE 13.1. Nevertheless, in case of trouble, first update the BIOS of your machine to the latest version. If the BIOS update does not help, report the model of your machine to the wiki (http://en.opensuse.org/openSUSE:UEFI). Then we can track it for the next release." msgstr "與 openSUSE 12.3 相比,新的 shim 載入器允許更多的機器能從 Secure Boot 模式下啟動。雖然,在某些棘手的情況下,您需要先更新您機器上的 BIOS 至最新的版本。假如更新後的 BIOS 並沒有解決您的問題,請提報您的機器型號到 openSUSE 維基 (http://en.opensuse.org/openSUSE:UEFI),以便我們能夠在下個發行版本追蹤它的支援狀態。" -#: xml/release-notes.xml:211(title) +#: xml/release-notes.xml:245(title) msgid "System Upgrade" msgstr "系統昇級" -#: xml/release-notes.xml:218(title) +#: xml/release-notes.xml:252(title) msgid "Technical" msgstr "技術議題" -#: xml/release-notes.xml:222(title) -msgid "Initializing Graphics with KMS (Kernel Mode Setting)" -msgstr "使用 KMS (Kernel Mode Setting) 初始化圖形顯示" - -#. 13.2: to be removed from the release notes: -#. https://bugzilla.novell.com/show_bug.cgi?id=849188 -#: xml/release-notes.xml:227(para) -msgid "With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding <literal>nomodeset</literal> to the kernel boot command line. To set this permanently using Grub 2, the default boot loader, add it to the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> kernel default load options line in your <filename>/etc/default/grub</filename> text file as root and running the terminal command" -msgstr "自 openSUSE 11.3 起,針對 Intel、ATI 及 NVIDIA 的圖形顯示,我們預設已改用 KMS (Kernel Mode Setting)。若您在 KMS 驅動程式支援 (intel,radeon,nouveau) 上遇到問題,您可以在核心開機參數中加入 <literal>nomodeset</literal> 來關閉 KMS。若要使用 Grub2 (預設的開機啟動程式) 來永久儲存該設定,請以 root 權限,將上述設定加入設定檔 <filename>/etc/default/grub</filename> 中的 <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> 核心預設啟動選項,並在終端機執行指令" - -#: xml/release-notes.xml:233(screen) -#, no-wrap -msgid "sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg" -msgstr "sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg" - -#: xml/release-notes.xml:234(para) -msgid "for the changes to take effect. Else, for Grub Legacy, add it to the kernel command line in <filename>/boot/grub/menu.lst</filename>, also done as root. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with <literal>modeset=0</literal> in <filename>initrd</filename>, i.e. KMS is disabled." -msgstr "來讓修改生效。若是使用舊版 Grub,將該設定加入設定檔 <filename>/boot/grub/menu.lst</filename> 中的核心開機參數行中,同樣也要以 root 權限進行。該選項可確保當在 <filename>initrd</filename> 載入適當的核心驅動程式 (intel,radeon,nouveau) 時,將 <literal>modeset=0</literal> 設定傳給驅動程式 (關閉 KMS)。" - -#: xml/release-notes.xml:239(para) -msgid "In the rare cases when loading the DRM module from <filename>initrd</filename> is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module in <filename>initrd</filename> completely. For this set the <literal>NO_KMS_IN_INITRD</literal> sysconfig variable to <literal>yes</literal> via YaST, which then recreates <filename>initrd</filename> afterwards. Reboot your machine." -msgstr "在極少數的情況之下,當從 <filename>initrd</filename> 載入 DRM 模組遇到問題且和 KMS 無關時,您也可以在 <filename>initrd</filename> 中完全停用 DRM 模組的載入。您可以透過 YaST 設定 sysconfig 變數 <literal>NO_KMS_IN_INITRD</literal>,將值設為 <literal>yes</literal>,然後重新產生 <filename>initrd</filename>。接著重新啟動您的電腦。" - -#: xml/release-notes.xml:245(para) -msgid "On Intel without KMS the Xserver falls back to the <literal>fbdev</literal> driver (the <literal>intel</literal> driver only supports KMS); alternatively, for legacy GPUs from Intel the \"intellegacy\" driver (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> package) is available, which still supports UMS (User Mode Setting). To use it, edit <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> and change the driver entry to <literal>intellegacy</literal>." -msgstr "對於未開啟 KMS 的 Intel 系統,X server 會退而求其次改用 <literal>fbdev</literal> 驅動程式 (<literal>intel</literal> 驅動程式只支援 KMS);或是,對於舊型的 Intel 晶片,\"intellegacy\" 驅動程式依然可以使用 (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> 套件),並支援 UMS (User Mode Setting)。要使用該驅動程式,請編輯 <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> 並修改 driver 欄位的內容為 <literal>intellegacy</literal>。" - -#: xml/release-notes.xml:252(para) -msgid "On ATI for current GPUs it falls back to <literal>radeonhd</literal>. On NVIDIA without KMS the <literal>nv</literal> driver is used (the <literal>nouveau</literal> driver supports only KMS). Note, newer ATI and NVIDIA GPUs are falling back to <literal>fbdev</literal>, if you specify the <literal>nomodeset</literal> kernel boot parameter." -msgstr "對於 ATI 目前的主流晶片,若未開啟 KMS,X server 會改用 <literal>radeonhd</literal>。對於 NVIDIA,則改用 <literal>nv</literal> (<literal>nouveau</literal> 驅動程式只支援 KMS)。請注意,對於未來更新的 ATI 與 NVIDIA 的顯示晶片,若您在核心開機參數加入 <literal>nomodeset</literal>,則會退回改用 <literal>fbdev</literal>。" - #. bnc#850053 -#: xml/release-notes.xml:260(title) +#: xml/release-notes.xml:256(title) msgid "Garbage on the Screen During Installation with the Nouveau Driver" msgstr "使用 Nouveau 圖形驅動時在安裝階段螢幕上出現殘影" -#: xml/release-notes.xml:262(para) +#: xml/release-notes.xml:257(para) msgid "On some systems with NVIDIA cards, the installer may show garbage on the top part of the screen due to problems with the default nouveau driver. If you are affected by this problem, you can disable the nouveau kernel module to run the installer and then enable it again once the system is installed or upgraded." msgstr "在某些使用 NVIDIA 圖形顯示卡的系統上,在安裝階段也許會有殘影出現在螢幕上,此為預設 nouveau 圖形驅動的問題。假如您遇見此問題,您可以在安裝階段關閉 nouveau 內核模組,然後在安裝完成之後或是升級完成之後重新啟動此模組。" -#: xml/release-notes.xml:266(para) +#: xml/release-notes.xml:261(para) msgid "To disable the kernel module, once you boot from the installation media, select the 'Installation' entry in grub and press 'e' to edit the parameters. Then go to the line starting with 'linux' (or 'linuxefi') and add <literal>brokenmodules=nouveau</literal> at the end. Now press F10 to continue booting with the new parameter. After the system is installed, you can re-enable the nouveau module by editing <filename>/etc/modprobe.d/50-blacklist.conf</filename> and removing the entry that blacklists nouveau." msgstr "要關閉內核模組,請在安裝媒體啟動時在 grub 畫面選擇“安裝”並按 'e' 來編輯參數。然後移動游標至 'Linux'(或 'linuxefi')為開頭的行,添加 <literal>brokenmodules=nouveau</literal> 至行尾末。接著按 F10 鍵以繼續啟動並採用新的參數。系統安裝完成後,可以重新啟用 nouveau 模組,前往編輯 <filename>/etc/modprobe.d/50-blacklist.conf</filename> 並從此黑名單中刪除 nouveau 項目。" -#. via mail: ddiss -#: xml/release-notes.xml:277(title) -msgid "Samba Version 4.1" -msgstr "Samba 4.1" +#. bnc#902947 +#: xml/release-notes.xml:271(title) +msgid "openSUSE pre-13.2 cifstab Migration" +msgstr "" +#: xml/release-notes.xml:273(para) +msgid "Mounting cifs shares at systems start via <filename>/etc/samba/cifstab</filename> has been discontinued and obsoleted. Now the generic <filename>/etc/fstab</filename> handles it." +msgstr "" + #: xml/release-notes.xml:279(para) -msgid "Samba version 4.1 shipped with openSUSE 13.1 does not include support to operate as an Active Directory style domain controller. This functionality is currently disabled, as it lacks integration with system-wide MIT Kerberos." -msgstr "openSUSE 13.1 所發行的 Samba 4.1 並未包含 Active Directory 網域主控站的運作支援。這個功能目前是關閉的,主要是因為它未與系統中的 MIT Kerberos 做整合。" +msgid "The migration process requires two steps:" +msgstr "" -#. bnc#848969 -#: xml/release-notes.xml:287(title) -msgid "KDE and Bluetooth" -msgstr "KDE 桌面環境與藍芽支援" +#: xml/release-notes.xml:284(para) +msgid "Append all your mount points from <filename>/etc/samba/cifstab.rpmsave</filename> to <filename>/etc/fstab</filename>." +msgstr "" -#: xml/release-notes.xml:289(para) -msgid "The Bluetooth stack is provided by Bluez 5 (a major, backwards-incompatbile version), a necessary upgrade for GNOME desktop and some other components of the base system. Unfortunately, the KDE workspace only supports Bluez version 4 in its currently-released versions." -msgstr "目前的藍芽軟體堆疊是由 Bluez 5 (主要且向前不相容的版本) 所提供。對於 GNOME 桌面環境以及基礎系統中的某些元件來說,它是必要的更新。然而不幸地,目前釋出版本的 KDE 工作空間只支援 Bluez 4。" +#: xml/release-notes.xml:291(para) +msgid "Add <literal>0 0</literal> to the end of each new cifs mount line in <filename>/etc/fstab</filename>." +msgstr "" -#: xml/release-notes.xml:292(para) -msgid "Therefore, the openSUSE KDE community team offers an unofficial Bluedevil package providing at least basic functionality such as device pairing or support for bluetooth mice; Some other features are known not to work jet, like file transfer." -msgstr "因此 openSUSE KDE 社群團隊提供了一個非官方的 Bluedevil 套件,來提供至少基本的功能如裝置配對,或是藍芽滑鼠的支援;其他的功能如檔案傳輸等,則尚未支援。" +#: xml/release-notes.xml:298(para) +msgid "For more information and examples, see <filename>/usr/share/doc/packages/cifs-utils/README.cifstab.migration</filename> in the installed system." +msgstr "" -#: xml/release-notes.xml:295(para) -msgid "For the moment, bugs should not be filed against Bluetooth support in KDE as the Bluez 5 port of Bluedevil is still ongoing." -msgstr "因為移植 Bluedevil 到 Bluez 5 的工作還在進行中,故現階段不應該回報有關 KDE 環境下的藍芽支援問題。" - #. bnc#850058 -#: xml/release-notes.xml:301(title) +#: xml/release-notes.xml:335(title) msgid "AppArmor and Permission Settings" msgstr "AppArmor 與權限設定" -#: xml/release-notes.xml:303(para) -msgid "AppArmor is enabled by default. This means more security, but might prevent services from working, if you run them in unexpected ways. If you encounter strange permission problems, try to switch the AppArmor profile for the affected service to complain mode with:" +#: xml/release-notes.xml:336(para) +#, fuzzy +#| msgid "AppArmor is enabled by default. This means more security, but might prevent services from working, if you run them in unexpected ways. If you encounter strange permission problems, try to switch the AppArmor profile for the affected service to complain mode with:" +msgid "AppArmor is enabled by default. This means more security, but might prevent services from working if you run them in unexpected ways. If you encounter strange permission problems, try to switch the AppArmor profile for the affected service to complain mode with:" msgstr "AppArmor 預設是被啟用的。這意味著系統會更加安全,但若您以非預期的方式執行某些服務,這些服務可能會無法正常運作。如果您遇到了異常的權限問題,可以嘗試將該受影響服務的 AppArmor 組態切換為 complain 模式:" -#: xml/release-notes.xml:306(screen) +#: xml/release-notes.xml:339(screen) #, no-wrap msgid "aa-complain /usr/bin/$your_service" msgstr "aa-complain /usr/bin/$your_service" -#: xml/release-notes.xml:307(para) +#: xml/release-notes.xml:340(para) msgid "Complain mode means: allow everything, and log things that the profile would not allow." msgstr "complain 模式意指允許所有操作,並且記錄那些原本不被允許的操作。" -#: xml/release-notes.xml:308(para) -msgid "Even if it helps report it as a bug! We want to fix AppArmor profiles to cover also corner cases." +#: xml/release-notes.xml:341(para) +#, fuzzy +#| msgid "Even if it helps report it as a bug! We want to fix AppArmor profiles to cover also corner cases." +msgid "Even if it helps, report it as a bug! We want to fix AppArmor profiles to also cover corner cases." msgstr "即使以上建議有助於解決您的問題,我們仍鼓勵您將您遇到的問題回報為臭蟲。我們想要修正 AppArmor 組態以儘可能涵蓋所有的極端情況。" -#. bnc#850057 -#: xml/release-notes.xml:314(title) -msgid "Skype" -msgstr "Skype" - -#: xml/release-notes.xml:316(para) -msgid "PulseAudio 4.0 exposes a bug in the current version of Skype for Linux (v4.2). Until Skype is fixed and updated, run <command>skype</command> from the command line:" -msgstr "使用 Skype 4.2 版(Linux 版本)於 PulseAudio 4.0 上有一個已知的問題,在 Skype 修復此問題前,請於命令列執行 <command>skype</command> :" - -#: xml/release-notes.xml:318(screen) -#, no-wrap -msgid "PULSE_LATENCY_MSEC=60 skype" -msgstr "PULSE_LATENCY_MSEC=60 skype" - -#: xml/release-notes.xml:319(para) -msgid "For more information about this bug, see <ulink url=\"http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/\"/>." -msgstr "針對此臭蟲的更多資訊請見 <ulink url=\"http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/\"/>。" - -#. bnc#851588 -#: xml/release-notes.xml:325(title) -msgid "AutoYaST" -msgstr "AutoYaST" - -#: xml/release-notes.xml:327(para) -msgid "If the autoyast profile contains entries in an <literal><add-on></literal> section there is a bug triggered that prevents information in the profile from being transferred from the first stage into the second stage. Therefore, in this case all second stage configuration steps are skipped, which normally leads to more or less completely unusable installations." -msgstr "若在 autoyast 組態中的 <literal><add-on></literal> 區段下含有設定欄位,則會觸發一個臭蟲,導致該組態中的資訊無法自安裝時期第一階段傳送至第二階段。因此第二階段的組態設定步驟會被忽略掉,這通常會使得安裝完的系統幾乎完全無法使用。" - -#: xml/release-notes.xml:331(para) -msgid "As a temporary workaround, avoid using <literal><add-on></literal> sections in profiles with AutoYaST in openSUSE 13.1." -msgstr "一個暫時性的解決方法,就是避免在 openSUSE 13.1 AutoYaST 組態中使用 <literal><add-on></literal> 區段。" - -#: xml/release-notes.xml:338(title) +#: xml/release-notes.xml:374(title) msgid "Miscellaneous" msgstr "雜項" -#: xml/release-notes.xml:339(para) +#: xml/release-notes.xml:375(para) msgid "N/A" msgstr "N/A" #. bnc#809347 -#: xml/release-notes.xml:345(title) +#: xml/release-notes.xml:381(title) msgid "More Information and Feedback" msgstr "更多資訊與反饋" -#: xml/release-notes.xml:349(para) +#: xml/release-notes.xml:385(para) msgid "Read the READMEs on the CDs." msgstr "閱讀安裝 CD 中的 README 檔案。" -#: xml/release-notes.xml:352(para) +#: xml/release-notes.xml:388(para) msgid "Get detailed changelog information about a particular package from the RPM:" msgstr "從 RPM 獲取某個套件詳細的變動歷史資訊:" -#: xml/release-notes.xml:353(screen) +#: xml/release-notes.xml:389(screen) #, no-wrap msgid "rpm --changelog -qp <FILENAME>.rpm" msgstr "rpm --changelog -qp <FILENAME>.rpm" -#: xml/release-notes.xml:354(para) +#: xml/release-notes.xml:390(para) msgid "<FILENAME>. is the name of the RPM." msgstr "<FILENAME> 是該套件的名稱。" -#: xml/release-notes.xml:357(para) +#: xml/release-notes.xml:393(para) msgid "Check the <filename>ChangeLog</filename> file in the top level of the DVD for a chronological log of all changes made to the updated packages." msgstr "請查看在安裝 DVD 最上層目錄下的 <filename>ChangeLog</filename> 檔案以了解所更新套件的變動歷史(按時間先後排序)" -#: xml/release-notes.xml:361(para) +#: xml/release-notes.xml:397(para) msgid "Find more information in the <filename>docu</filename> directory on the DVD." msgstr "在安裝 DVD 中的 <filename>docu</filename> 目錄可找到更多的資訊。" -#: xml/release-notes.xml:364(para) +#: xml/release-notes.xml:400(para) msgid "<ulink url=\"https://activedoc.opensuse.org/\"/> contains additional or updated documentation." msgstr "<ulink url=\"https://activedoc.opensuse.org/\"/> 包含了額外或是更新的文件。" -#: xml/release-notes.xml:369(para) +#: xml/release-notes.xml:405(para) msgid "Visit <ulink url=\"http://www.opensuse.org\"/> for the latest product news from openSUSE." msgstr "請造訪 <ulink url=\"http://www.opensuse.org\"/> 以了解 openSUSE 最新的產品訊息。" -#: xml/release-notes.xml:374(para) +#: xml/release-notes.xml:410(para) msgid "Copyright © 2014 SUSE LLC" msgstr "版權所有 © 2014 SUSE LLC" -#: xml/release-notes.xml:376(para) +#: xml/release-notes.xml:412(para) msgid "Thanks for using openSUSE." msgstr "感謝使用 openSUSE。" -#: xml/release-notes.xml:377(para) +#: xml/release-notes.xml:413(para) msgid "The openSUSE Team." msgstr "openSUSE 團隊" @@ -319,24 +240,89 @@ "Ray Chen <swyear@gmail.com>, 2007, 2008, 2009, 2010, 2011, 2012\n" "Ramax Lo <ramaxlo@gmail.com>, 2013, 2014" -#~ msgid "" -#~ "In case you encounter a \"Permission denied\" message, and want to speed " -#~ "up the access to the database file, consider to remove <filename>cron." -#~ "daily</filename> (do not do this if you run sensible tasks via the " -#~ "<filename>cron.daily</filename> mechanism):" -#~ msgstr "" -#~ "如果您遇到”拒絕存取(Permission denied)“訊息,以及想加速存取資料庫檔案," -#~ "請考慮移除 <filename>cron.daily</filename> (請不要移除它,假如你正在使用 " -#~ "<filename>cron.daily</filename> 處理敏感的任務的話):" +#~ msgid "For Detailed Installation Information" +#~ msgstr "詳細安裝資訊" +#~ msgid "For detailed installation information, see <xref linkend=\"sec.123.documentation\"/>." +#~ msgstr "欲了解細節的安裝資訊,請參考 <xref linkend=\"sec.123.documentation\"/>。" + +#~ msgid "openSUSE Documentation" +#~ msgstr "openSUSE 文件" + +#~ msgid "In <emphasis>Start-Up</emphasis>, find step-by-step installation instructions, as well as introductions to the KDE and Gnome desktops and to the LibreOffice suite. Also covered are basic administration topics such as deployment and software management and an introduction to the bash shell." +#~ msgstr "在 <emphasis>新手入門</emphasis> 中您可以找到安裝指南,以及 KDE 和 Gnome 桌面環境與 LibreOffice 辦公室套裝軟體的介紹。另外還包含了基本的系統管理議題,如佈署、軟體管理,以及 bash 的介紹。" + +#~ msgid "Find the documentation in <filename>/usr/share/doc/manual/opensuse-manuals_$LANG</filename> after installing the package <systemitem>opensuse-startup_$LANG</systemitem>, or online on <ulink url=\"http://doc.opensuse.org\"/>." +#~ msgstr "您可以在安裝完 <systemitem>opensuse-startup_$LANG</systemitem> 套件後,在 <filename>/usr/share/doc/manual/opensuse-manuals_$LANG</filename> 找到文件,或是直接在線上瀏覽 <ulink url=\"http://doc.opensuse.org\"/>。" + +#~ msgid "Initializing Graphics with KMS (Kernel Mode Setting)" +#~ msgstr "使用 KMS (Kernel Mode Setting) 初始化圖形顯示" + +#~ msgid "With openSUSE 11.3 we switched to KMS (Kernel Mode Setting) for Intel, ATI and NVIDIA graphics, which now is our default. If you encounter problems with the KMS driver support (intel, radeon, nouveau), disable KMS by adding <literal>nomodeset</literal> to the kernel boot command line. To set this permanently using Grub 2, the default boot loader, add it to the <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> kernel default load options line in your <filename>/etc/default/grub</filename> text file as root and running the terminal command" +#~ msgstr "自 openSUSE 11.3 起,針對 Intel、ATI 及 NVIDIA 的圖形顯示,我們預設已改用 KMS (Kernel Mode Setting)。若您在 KMS 驅動程式支援 (intel,radeon,nouveau) 上遇到問題,您可以在核心開機參數中加入 <literal>nomodeset</literal> 來關閉 KMS。若要使用 Grub2 (預設的開機啟動程式) 來永久儲存該設定,請以 root 權限,將上述設定加入設定檔 <filename>/etc/default/grub</filename> 中的 <literal>GRUB_CMDLINE_LINUX_DEFAULT</literal> 核心預設啟動選項,並在終端機執行指令" + +#~ msgid "sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg" +#~ msgstr "sudo /usr/sbin/grub2-mkconfig --output=/boot/grub2/grub.cfg" + +#~ msgid "for the changes to take effect. Else, for Grub Legacy, add it to the kernel command line in <filename>/boot/grub/menu.lst</filename>, also done as root. This option makes sure the appropriate kernel module (intel, radeon, nouveau) is loaded with <literal>modeset=0</literal> in <filename>initrd</filename>, i.e. KMS is disabled." +#~ msgstr "來讓修改生效。若是使用舊版 Grub,將該設定加入設定檔 <filename>/boot/grub/menu.lst</filename> 中的核心開機參數行中,同樣也要以 root 權限進行。該選項可確保當在 <filename>initrd</filename> 載入適當的核心驅動程式 (intel,radeon,nouveau) 時,將 <literal>modeset=0</literal> 設定傳給驅動程式 (關閉 KMS)。" + +#~ msgid "In the rare cases when loading the DRM module from <filename>initrd</filename> is a general problem and unrelated to KMS, it is even possible to disable loading of the DRM module in <filename>initrd</filename> completely. For this set the <literal>NO_KMS_IN_INITRD</literal> sysconfig variable to <literal>yes</literal> via YaST, which then recreates <filename>initrd</filename> afterwards. Reboot your machine." +#~ msgstr "在極少數的情況之下,當從 <filename>initrd</filename> 載入 DRM 模組遇到問題且和 KMS 無關時,您也可以在 <filename>initrd</filename> 中完全停用 DRM 模組的載入。您可以透過 YaST 設定 sysconfig 變數 <literal>NO_KMS_IN_INITRD</literal>,將值設為 <literal>yes</literal>,然後重新產生 <filename>initrd</filename>。接著重新啟動您的電腦。" + +#~ msgid "On Intel without KMS the Xserver falls back to the <literal>fbdev</literal> driver (the <literal>intel</literal> driver only supports KMS); alternatively, for legacy GPUs from Intel the \"intellegacy\" driver (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> package) is available, which still supports UMS (User Mode Setting). To use it, edit <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> and change the driver entry to <literal>intellegacy</literal>." +#~ msgstr "對於未開啟 KMS 的 Intel 系統,X server 會退而求其次改用 <literal>fbdev</literal> 驅動程式 (<literal>intel</literal> 驅動程式只支援 KMS);或是,對於舊型的 Intel 晶片,\"intellegacy\" 驅動程式依然可以使用 (<systemitem>xorg-x11-driver-video-intel-legacy</systemitem> 套件),並支援 UMS (User Mode Setting)。要使用該驅動程式,請編輯 <filename>/etc/X11/xorg.conf.d/50-device.conf</filename> 並修改 driver 欄位的內容為 <literal>intellegacy</literal>。" + +#~ msgid "On ATI for current GPUs it falls back to <literal>radeonhd</literal>. On NVIDIA without KMS the <literal>nv</literal> driver is used (the <literal>nouveau</literal> driver supports only KMS). Note, newer ATI and NVIDIA GPUs are falling back to <literal>fbdev</literal>, if you specify the <literal>nomodeset</literal> kernel boot parameter." +#~ msgstr "對於 ATI 目前的主流晶片,若未開啟 KMS,X server 會改用 <literal>radeonhd</literal>。對於 NVIDIA,則改用 <literal>nv</literal> (<literal>nouveau</literal> 驅動程式只支援 KMS)。請注意,對於未來更新的 ATI 與 NVIDIA 的顯示晶片,若您在核心開機參數加入 <literal>nomodeset</literal>,則會退回改用 <literal>fbdev</literal>。" + +#~ msgid "Samba Version 4.1" +#~ msgstr "Samba 4.1" + +#~ msgid "Samba version 4.1 shipped with openSUSE 13.1 does not include support to operate as an Active Directory style domain controller. This functionality is currently disabled, as it lacks integration with system-wide MIT Kerberos." +#~ msgstr "openSUSE 13.1 所發行的 Samba 4.1 並未包含 Active Directory 網域主控站的運作支援。這個功能目前是關閉的,主要是因為它未與系統中的 MIT Kerberos 做整合。" + +#~ msgid "KDE and Bluetooth" +#~ msgstr "KDE 桌面環境與藍芽支援" + +#~ msgid "The Bluetooth stack is provided by Bluez 5 (a major, backwards-incompatbile version), a necessary upgrade for GNOME desktop and some other components of the base system. Unfortunately, the KDE workspace only supports Bluez version 4 in its currently-released versions." +#~ msgstr "目前的藍芽軟體堆疊是由 Bluez 5 (主要且向前不相容的版本) 所提供。對於 GNOME 桌面環境以及基礎系統中的某些元件來說,它是必要的更新。然而不幸地,目前釋出版本的 KDE 工作空間只支援 Bluez 4。" + +#~ msgid "Therefore, the openSUSE KDE community team offers an unofficial Bluedevil package providing at least basic functionality such as device pairing or support for bluetooth mice; Some other features are known not to work jet, like file transfer." +#~ msgstr "因此 openSUSE KDE 社群團隊提供了一個非官方的 Bluedevil 套件,來提供至少基本的功能如裝置配對,或是藍芽滑鼠的支援;其他的功能如檔案傳輸等,則尚未支援。" + +#~ msgid "For the moment, bugs should not be filed against Bluetooth support in KDE as the Bluez 5 port of Bluedevil is still ongoing." +#~ msgstr "因為移植 Bluedevil 到 Bluez 5 的工作還在進行中,故現階段不應該回報有關 KDE 環境下的藍芽支援問題。" + +#~ msgid "Skype" +#~ msgstr "Skype" + +#~ msgid "PulseAudio 4.0 exposes a bug in the current version of Skype for Linux (v4.2). Until Skype is fixed and updated, run <command>skype</command> from the command line:" +#~ msgstr "使用 Skype 4.2 版(Linux 版本)於 PulseAudio 4.0 上有一個已知的問題,在 Skype 修復此問題前,請於命令列執行 <command>skype</command> :" + +#~ msgid "PULSE_LATENCY_MSEC=60 skype" +#~ msgstr "PULSE_LATENCY_MSEC=60 skype" + +#~ msgid "For more information about this bug, see <ulink url=\"http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/\"/>." +#~ msgstr "針對此臭蟲的更多資訊請見 <ulink url=\"http://arunraghavan.net/2013/08/pulseaudio-4-0-and-skype/\"/>。" + +#~ msgid "AutoYaST" +#~ msgstr "AutoYaST" + +#~ msgid "If the autoyast profile contains entries in an <literal><add-on></literal> section there is a bug triggered that prevents information in the profile from being transferred from the first stage into the second stage. Therefore, in this case all second stage configuration steps are skipped, which normally leads to more or less completely unusable installations." +#~ msgstr "若在 autoyast 組態中的 <literal><add-on></literal> 區段下含有設定欄位,則會觸發一個臭蟲,導致該組態中的資訊無法自安裝時期第一階段傳送至第二階段。因此第二階段的組態設定步驟會被忽略掉,這通常會使得安裝完的系統幾乎完全無法使用。" + +#~ msgid "As a temporary workaround, avoid using <literal><add-on></literal> sections in profiles with AutoYaST in openSUSE 13.1." +#~ msgstr "一個暫時性的解決方法,就是避免在 openSUSE 13.1 AutoYaST 組態中使用 <literal><add-on></literal> 區段。" + +#~ msgid "In case you encounter a \"Permission denied\" message, and want to speed up the access to the database file, consider to remove <filename>cron.daily</filename> (do not do this if you run sensible tasks via the <filename>cron.daily</filename> mechanism):" +#~ msgstr "如果您遇到”拒絕存取(Permission denied)“訊息,以及想加速存取資料庫檔案,請考慮移除 <filename>cron.daily</filename> (請不要移除它,假如你正在使用 <filename>cron.daily</filename> 處理敏感的任務的話):" + #~ msgid "rm /var/spool/cron/lastrun/cron.daily" #~ msgstr "rm /var/spool/cron/lastrun/cron.daily" -#~ msgid "" -#~ "Within the next 15 minutes the daily cron routine will start and build a " -#~ "proper mlocate file." -#~ msgstr "" -#~ "在接下來的15分鐘內,每日的 cron 服務將啟動,並建立適當的 mlocate 檔案。" +#~ msgid "Within the next 15 minutes the daily cron routine will start and build a proper mlocate file." +#~ msgstr "在接下來的15分鐘內,每日的 cron 服務將啟動,並建立適當的 mlocate 檔案。" #~ msgid "No Network after Installation" #~ msgstr "安裝完成後,沒有網路可用" @@ -344,72 +330,35 @@ #~ msgid "CHECKIT:12.3" #~ msgstr "CHECKIT:12.3" -#~ msgid "" -#~ "Directly after installation, NetworkManager is not started automatically " -#~ "and thus WiFi cannot be configured. To enable networking (WiFi), reboot " -#~ "the machine once manually." -#~ msgstr "" -#~ "當安裝完成後,NetworkManager 不會自動啟動,故無法設定 WiFi。要啟動網路 " -#~ "(WiFi),您需要手動重新啟動一次系統。" +#~ msgid "Directly after installation, NetworkManager is not started automatically and thus WiFi cannot be configured. To enable networking (WiFi), reboot the machine once manually." +#~ msgstr "當安裝完成後,NetworkManager 不會自動啟動,故無法設定 WiFi。要啟動網路 (WiFi),您需要手動重新啟動一次系統。" -#~ msgid "" -#~ "The proprietary NVIDIA driver requires users to have access to /dev/" -#~ "nvidia* devices" +#~ msgid "The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices" #~ msgstr "NVIDIA 封閉驅動程式需要使用者擁有能夠存取 /dev/nvidia* 裝置的權限 " -#~ msgid "" -#~ "Default and new users are no longer added to the <literal>video</literal> " -#~ "group automatically. But the proprietary NVIDIA driver requires users to " -#~ "have access to /dev/nvidia* devices." -#~ msgstr "" -#~ "預設及新增使用者將不會被自動加入 <literal>video</literal> 群組。然而 " -#~ "NVIDIA 封閉驅動程式需要使用者擁有存取 /dev/nvidia* 裝置的權限。" +#~ msgid "Default and new users are no longer added to the <literal>video</literal> group automatically. But the proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices." +#~ msgstr "預設及新增使用者將不會被自動加入 <literal>video</literal> 群組。然而 NVIDIA 封閉驅動程式需要使用者擁有存取 /dev/nvidia* 裝置的權限。" -#~ msgid "" -#~ "Because the NVIDIA driver does not use the usual kernel methods that " -#~ "allow to install ACLs on the device nodes, users have to be added " -#~ "manually to the <literal>video</literal> group; as <systemitem>root</" -#~ "systemitem> call (replace <literal>$USER</literal> with the actual " -#~ "username):" -#~ msgstr "" -#~ "由於 NVIDIA 驅動程式並未使用一般內核使用的方法 (該方法允許設定裝置檔案的 " -#~ "ACL),因此使用者需要手動加入 <literal>video</literal> 群組;要加入群組,請" -#~ "以 <systemitem>root</systemitem> 權限執行以下指令 (將指令中的 <literal>" -#~ "$USER</literal> 代換為實際的使用者名稱):" +#~ msgid "Because the NVIDIA driver does not use the usual kernel methods that allow to install ACLs on the device nodes, users have to be added manually to the <literal>video</literal> group; as <systemitem>root</systemitem> call (replace <literal>$USER</literal> with the actual username):" +#~ msgstr "由於 NVIDIA 驅動程式並未使用一般內核使用的方法 (該方法允許設定裝置檔案的 ACL),因此使用者需要手動加入 <literal>video</literal> 群組;要加入群組,請以 <systemitem>root</systemitem> 權限執行以下指令 (將指令中的 <literal>$USER</literal> 代換為實際的使用者名稱):" #~ msgid "usermod -a -G video $USER" #~ msgstr "usermod -a -G video $USER" -#~ msgid "" -#~ "Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode" +#~ msgid "Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode" #~ msgstr "在 Secure Boot 模式中,YaST 啟動 Secure Boot 選項預設未開啟" -#~ msgid "" -#~ "YaST does not automatically detect if the machine has secure boot enabled " -#~ "and will therefore install an unsigned bootloader by default. But the " -#~ "unsigned bootloader will not be accepted by the firmware. To have a " -#~ "signed bootloader installed the option \"Enable Secure Boot\" has to be " -#~ "manually enabled." -#~ msgstr "" -#~ "若機器啟用了 Secure Boot 模式,YaST 並不會自動偵測,因此預設會安裝一個未簽" -#~ "章的啟動程式,但是該程式將不會被韌體所接受。若要安裝簽章過的啟動程式,「啟" -#~ "用 Secure Boot」選項需要手動開啟。" +#~ msgid "YaST does not automatically detect if the machine has secure boot enabled and will therefore install an unsigned bootloader by default. But the unsigned bootloader will not be accepted by the firmware. To have a signed bootloader installed the option \"Enable Secure Boot\" has to be manually enabled." +#~ msgstr "若機器啟用了 Secure Boot 模式,YaST 並不會自動偵測,因此預設會安裝一個未簽章的啟動程式,但是該程式將不會被韌體所接受。若要安裝簽章過的啟動程式,「啟用 Secure Boot」選項需要手動開啟。" -#~ msgid "" -#~ "Wrong Bootloader When Installing from a Live Medium in a UEFI Environment" +#~ msgid "Wrong Bootloader When Installing from a Live Medium in a UEFI Environment" #~ msgstr "在 UEFI 環境中,使用 Live 媒體安裝了錯誤的啟動程式" #~ msgid "This only affects machines in UEFI mode." #~ msgstr "這個只會影響到使用 UEFI 模式的機器。" -#~ msgid "" -#~ "When using the installer on the live medium, YaST does not detect UEFI " -#~ "mode and therefore installs the legacy bootloader. This results in a not " -#~ "bootable system. The bootloader has to be switched from grub2 to grub2-" -#~ "efi manually." -#~ msgstr "" -#~ "當執行 Live 媒體上的安裝程式時,YaST 並不會偵測 UEFI 模式,因此會安裝到舊" -#~ "的啟動程式,系統將無法開機。因此啟動程式必須手動從 grub2 改用 grub2-efi。" +#~ msgid "When using the installer on the live medium, YaST does not detect UEFI mode and therefore installs the legacy bootloader. This results in a not bootable system. The bootloader has to be switched from grub2 to grub2-efi manually." +#~ msgstr "當執行 Live 媒體上的安裝程式時,YaST 並不會偵測 UEFI 模式,因此會安裝到舊的啟動程式,系統將無法開機。因此啟動程式必須手動從 grub2 改用 grub2-efi。" #~ msgid "Crypted LVM in UEFI Mode Needs /boot Partition" #~ msgstr "UEFI 模式中加密的 LVM 需要 /boot 分割區" @@ -417,53 +366,23 @@ #~ msgid "This only affects installations in UEFI mode." #~ msgstr "這個只會影響在 UEFI 模式下進行的安裝程序。" -#~ msgid "" -#~ "In the partitioning proposal when checking the option to use LVM (which " -#~ "is required for full disk encryption) YaST does not create a separate " -#~ "<filename>/boot</filename> partition. That means kernel and initrd end up " -#~ "in the (potentially encrypted) LVM container, inaccessible to the boot " -#~ "loader. To get full disk encryption when using UEFI, partitioning has to " -#~ "be done manually." -#~ msgstr "" -#~ "在磁碟分割建議中勾選使用 LVM 時 (這是使用全磁碟加密時的必要功能),YaST 並" -#~ "不會建立另一個獨立的 <filename>/boot</filename> 分割區。這表示核心與 " -#~ "initrd 將會被安裝到 LVM 容器中 (很可能是被加密過的),因此啟動程式將無法存" -#~ "取。要在 UEFI 模式下使用全磁碟加密,請手動建立分割區。" +#~ msgid "In the partitioning proposal when checking the option to use LVM (which is required for full disk encryption) YaST does not create a separate <filename>/boot</filename> partition. That means kernel and initrd end up in the (potentially encrypted) LVM container, inaccessible to the boot loader. To get full disk encryption when using UEFI, partitioning has to be done manually." +#~ msgstr "在磁碟分割建議中勾選使用 LVM 時 (這是使用全磁碟加密時的必要功能),YaST 並不會建立另一個獨立的 <filename>/boot</filename> 分割區。這表示核心與 initrd 將會被安裝到 LVM 容器中 (很可能是被加密過的),因此啟動程式將無法存取。要在 UEFI 模式下使用全磁碟加密,請手動建立分割區。" #~ msgid "systemd: Activating NetworkManager with a network.service Alias Link" #~ msgstr "systemd: 使用 network.service 別名鏈結來啟動 NetworkManager" -#~ msgid "" -#~ "By default, you use the YaST Network Settings dialog (<command>yast2 " -#~ "network</command>) to activate NetworkManager. If you want to activate " -#~ "NetworkManager, proceed as follows." -#~ msgstr "" -#~ "預設您應使用 YaST 網路設定對話框 (<command>yast2 network</command>) 來啟" -#~ "動 NetworkManager。若您想要手動啟動 NetworkManager,請參考以下的步驟。" +#~ msgid "By default, you use the YaST Network Settings dialog (<command>yast2 network</command>) to activate NetworkManager. If you want to activate NetworkManager, proceed as follows." +#~ msgstr "預設您應使用 YaST 網路設定對話框 (<command>yast2 network</command>) 來啟動 NetworkManager。若您想要手動啟動 NetworkManager,請參考以下的步驟。" -#~ msgid "" -#~ "The <literal>NETWORKMANAGER</literal> sysconfig variable in <filename>/" -#~ "etc/sysconfig/network/config</filename> to activate NetworkManager has " -#~ "been replaced with a systemd <literal>network.service</literal> alias " -#~ "link, which will be created with the" -#~ msgstr "" -#~ "原來在設定檔 <filename>/etc/sysconfig/network/config</filename> 中,用來啟" -#~ "動 NetworkManager 的 sysconfg 變數 <literal>NETWORKMANAGER</literal>,已經" -#~ "被 systemd 的 <literal>network.service</literal> 別名鏈結所取代,該鏈結可" -#~ "以由" +#~ msgid "The <literal>NETWORKMANAGER</literal> sysconfig variable in <filename>/etc/sysconfig/network/config</filename> to activate NetworkManager has been replaced with a systemd <literal>network.service</literal> alias link, which will be created with the" +#~ msgstr "原來在設定檔 <filename>/etc/sysconfig/network/config</filename> 中,用來啟動 NetworkManager 的 sysconfg 變數 <literal>NETWORKMANAGER</literal>,已經被 systemd 的 <literal>network.service</literal> 別名鏈結所取代,該鏈結可以由" #~ msgid "systemctl enable NetworkManager.service" #~ msgstr "systemctl enable NetworkManager.service" -#~ msgid "" -#~ "command. It causes the creation of a <literal>network.service</literal> " -#~ "alias link pointing to the <literal>NetworkManager.service</literal>, and " -#~ "thus deactivates the <filename>/etc/init.d/network</filename> script. The " -#~ "command" -#~ msgstr "" -#~ "指令建立。該指令建立一個 <literal>network.service</literal> 別名鏈結,指" -#~ "向 <literal>NetworkManager.service</literal>,因此也停用 <filename>/etc/" -#~ "init.d/network</filename> 腳本。以下指令" +#~ msgid "command. It causes the creation of a <literal>network.service</literal> alias link pointing to the <literal>NetworkManager.service</literal>, and thus deactivates the <filename>/etc/init.d/network</filename> script. The command" +#~ msgstr "指令建立。該指令建立一個 <literal>network.service</literal> 別名鏈結,指向 <literal>NetworkManager.service</literal>,因此也停用 <filename>/etc/init.d/network</filename> 腳本。以下指令" #~ msgid "systemctl -p Id show network.service" #~ msgstr "systemctl -p Id show network.service" @@ -515,12 +434,8 @@ #~ msgid "systemctl disable NetworkManager.service" #~ msgstr "systemctl disable NetworkManager.service" -#~ msgid "" -#~ "Start the <command>/etc/init.d/network</command> service: " -#~ "<screen>systemctl start network.service</screen>" -#~ msgstr "" -#~ "啟動 <command>/etc/init.d/network</command> 服務:<screen>systemctl " -#~ "start network.service</screen>" +#~ msgid "Start the <command>/etc/init.d/network</command> service: <screen>systemctl start network.service</screen>" +#~ msgstr "啟動 <command>/etc/init.d/network</command> 服務:<screen>systemctl start network.service</screen>" #~ msgid "To query the currently selected service, use:" #~ msgstr "要查詢目前所選擇的服務,請使用:" @@ -528,49 +443,23 @@ #~ msgid "systemctl -p Id show network.service" #~ msgstr "systemctl -p Id show network.service" -#~ msgid "" -#~ "It returns \"<literal>Id=NetworkManager.service</literal>\" if the " -#~ "NetworkManager service is enabled, otherwise \"<literal>Id=network." -#~ "service</literal>\" and <command>/etc/init.d/network</command> is acting " -#~ "as the network service." -#~ msgstr "" -#~ "若啟用了 NetworkManager 服務,它將回應 \"<literal>Id=NetworkManager." -#~ "service</literal>\",否則將回應 \"<literal>Id=network.service</literal>" -#~ "\",表示 <command>/etc/init.d/network</command> 被選擇為網路服務。" +#~ msgid "It returns \"<literal>Id=NetworkManager.service</literal>\" if the NetworkManager service is enabled, otherwise \"<literal>Id=network.service</literal>\" and <command>/etc/init.d/network</command> is acting as the network service." +#~ msgstr "若啟用了 NetworkManager 服務,它將回應 \"<literal>Id=NetworkManager.service</literal>\",否則將回應 \"<literal>Id=network.service</literal>\",表示 <command>/etc/init.d/network</command> 被選擇為網路服務。" -#~ msgid "" -#~ "GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input " -#~ "Source Selection" -#~ msgstr "" -#~ "GNOME:將 Shift 或 Ctrl+Shift 設定為輸入來源選擇快捷鍵的暫時解決方法" +#~ msgid "GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection" +#~ msgstr "GNOME:將 Shift 或 Ctrl+Shift 設定為輸入來源選擇快捷鍵的暫時解決方法" -#~ msgid "" -#~ "In Gnome 3.6 use the following workaround to set Shift or Ctrl+Shift as " -#~ "shortcut keys for input source selection:" -#~ msgstr "" -#~ "在 Gnome 3.6,使用以下的暫時解決方法來設定 Shift 或 Ctrl+Shift 做為選擇輸" -#~ "入來源的快捷鍵:" +#~ msgid "In Gnome 3.6 use the following workaround to set Shift or Ctrl+Shift as shortcut keys for input source selection:" +#~ msgstr "在 Gnome 3.6,使用以下的暫時解決方法來設定 Shift 或 Ctrl+Shift 做為選擇輸入來源的快捷鍵:" #~ msgid "Install gnome-tweak-tool." #~ msgstr "安裝 gnome-tweak-tool。" -#~ msgid "" -#~ "Start gnome-tweak-tool (<menuchoice><guimenu>'Activities'</" -#~ "guimenu><guimenu>'advanced settings'</guimenu></menuchoice>)." -#~ msgstr "" -#~ "啟動 gnome-tweak-tool (<menuchoice><guimenu>'活動'</guimenu><guimenu>'進階" -#~ "設定'</guimenu></menuchoice>)。" +#~ msgid "Start gnome-tweak-tool (<menuchoice><guimenu>'Activities'</guimenu><guimenu>'advanced settings'</guimenu></menuchoice>)." +#~ msgstr "啟動 gnome-tweak-tool (<menuchoice><guimenu>'活動'</guimenu><guimenu>'進階設定'</guimenu></menuchoice>)。" -#~ msgid "" -#~ "Via the left menu, select <menuchoice><guimenu>'Typing'</guimenu></" -#~ "menuchoice>, in the right window, change the settings." -#~ msgstr "" -#~ "在左邊的選單,選擇 <menuchoice><guimenu>'輸入'</guimenu></menuchoice>,接" -#~ "著在右邊的視窗修改設定。" +#~ msgid "Via the left menu, select <menuchoice><guimenu>'Typing'</guimenu></menuchoice>, in the right window, change the settings." +#~ msgstr "在左邊的選單,選擇 <menuchoice><guimenu>'輸入'</guimenu></menuchoice>,接著在右邊的視窗修改設定。" -#~ msgid "" -#~ "This is also being tracked in the upstream bug report <ulink url=" -#~ "\"https://bugzilla.gnome.org/show_bug.cgi?id=689839\"/>." -#~ msgstr "" -#~ "這個問題也由上游錯誤報告 <ulink url=\"https://bugzilla.gnome.org/show_bug." -#~ "cgi?id=689839\"/> 所追蹤。" +#~ msgid "This is also being tracked in the upstream bug report <ulink url=\"https://bugzilla.gnome.org/show_bug.cgi?id=689839\"/>." +#~ msgstr "這個問題也由上游錯誤報告 <ulink url=\"https://bugzilla.gnome.org/show_bug.cgi?id=689839\"/> 所追蹤。" -- To unsubscribe, e-mail: opensuse-translation-commit+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation-commit+owner@opensuse.org
participants (1)
-
keichwa@svn2.opensuse.org