Release Notes for openSUSE/Leap_15.5 — Chinese (Taiwan) (zh_TW) @ openSUSE Weblate: Make sure to also review the following sections of this …

Translation

Source change

English (itstool) path: sect1/para

Chinese (Taiwan) (zh_TW)

Needs editing

Skip

	English	Chinese (Taiwan) (zh_TW)	Actions
	systemctl disable --now transactional-update.timer rebootmgr.service	systemctl disable --now transactional-update.timer rebootmgr.service
	For more information about transactional updates, see the openSUSE Kubic blog posts <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> and <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>.	要了解更多關於交易型更新的細節，請見 openSUSE Kubic 部落格文章 <link xlink:href="https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/"/> 以及 <link xlink:href="https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/"/>。
	Installing on Hard Disks With Less Than 12 GB of Capacity	安裝在空間少於 12 GB 的硬碟
	The installer will only propose a partitioning scheme if the available hard disk size is larger than 12 GB. If you want to set up, for example, very small virtual machines images, use the guided partitioner to tune partitioning parameters manually.	只有當硬碟空間大於 12 GB 時，安裝程式才會建議磁碟分割規劃。若您想要設定空間非常小的虛擬機器映象檔，請使用引導式磁碟分割程式來自行調整分割參數。
	UEFI—Unified Extensible Firmware Interface	UEFI - 統一可延伸韌體介面
	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-installation of Windows 8 or later is a strong indication that your system boots using UEFI.	在安裝 openSUSE 到使用 UEFI (統一可延伸韌體介面) 開機的系統之前，強烈建議您先詢問是否有硬體製造商所建議的韌體更新並加以安裝。若您的系統有預裝 Windows 8 或更新的版本，通常就代表您的系統使用 UEFI 開機。
	<emphasis>Background:</emphasis> Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. However, there is no clear data of how much is <quote>too much</quote>.	<emphasis>背景知識：</emphasis> 有些 UEFI 韌體有缺陷，導致當有太多資料被寫入 UEFI 儲存區域時，韌體會發生問題。但是沒人知道究竟寫入多少資料才算<quote>太多</quote>。
	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.	openSUSE 藉由只寫入能夠啟動系統的最少需要的資料量，來降低這個風險。寫入的資料至少要能告訴 UEFI 韌體 openSUSE 啟動程式的位置。官方 Linux 核心提供使用 UEFI 儲存區來寫入開機及當機資訊的功能 (<literal>pstore</literal>)，在此預設被停用。無論如何，建議安裝任何硬體製造商建議的韌體更新。
	UEFI, GPT, and MS-DOS Partitions	UEFI，GPT 與 MS-DOS 磁碟分割區
	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.	在 EFI/UEFI 的規格書中提到一個新的分割磁碟的劃分方式：GPT（GUID Partition Table）。這個新的方式使用 GUID（128位元的值顯示在32個十六進制數字上）來識別裝置及分割區類型。
	Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB 2) 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 consists of two different operations: Removing the old entry and creating a new entry that replaces the first one.	此外，UEFI 規範是允許傳統的 MBR（MS-DOS）分割區。 Linux 引導加載器（ELILO 或 GRUB2）嘗試針對那些傳統的分割區自動產生一個 GUID ，並把它們寫進韌體。像這樣的一個 GUID 可以頻繁變更，導致韌體的重寫入。一次的重寫入包括兩種不同的操作：刪除舊的項目，以及創建一個新的項目以取代第一個項目。
	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 can result in a non-bootable system.	現代的韌體都有一個垃圾收集器（garbage collector），可以收集被刪除的進入點（entries），並且釋放原來保留給舊進入點（entries）的記憶體。當故障的韌體不能收集或是釋放這些進入點（entries）時，系統將會出現問題，最終將造成系統無法開機。
	To work around this problem, convert the legacy MBR partition to GPT.	簡單的替代解決方案是：轉換傳統的 MBR 分割區成為新的 GPT 分割區以完整的避免此問題。
	System Upgrade	系統升級
	This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:	這個小節列出了與系統升級有關的注意事項。欲了解支援的升級場景以及詳細的升級步驟，請見：
	Make sure to also review the following sections of this documentation:	請務必檢閱 <xref linkend="sec.driver"/>。
	Repository Path Updates
	<emphasis role="strong">Repository Location Changes:</emphasis> Starting with Leap 15.5, the ppc64le and aarch64 versions are no longer stored under <literal>ports</literal> (see below). The amv7hl architecture remains unchanged.
	<emphasis role="strong">For Upgrading Users:</emphasis> If you're moving from Leap 15.3 or earlier, switch to the new repository locations. Old paths are obsolete. New path details are available <link xlink:href="https://en.opensuse.org/SDB:System_upgrade#Note_about_ports_(non_intel_architectures)">here</link>.
	<emphasis role="strong">Easy Upgrade Tip:</emphasis> Download and install the <literal>openSUSE-repos-Leap</literal> package for automatic path updates. Get it <link xlink:href="https://software.opensuse.org/package/openSUSE-repos-Leap">here</link>.
	Packaging Changes	套件變動
	Deprecated Packages	不建議的套件
	Deprecated packages are still shipped as part of the distribution but are scheduled to be removed the next version of openSUSE Leap. These packages exist to aid migration, but their use is discouraged and they may not receive updates.	不建議的套件還是會收錄為發行版的一部分，並且在下一版 openSUSE Leap 中會被移除。這些套件存在的原因是為了幫助版本遷移，但不建議使用，而且它們不會再有更新。
	To check whether installed packages are no longer maintained, make sure that the <package>lifecycle-data-openSUSE</package> package is installed, then use the command:	要檢查已安裝的套件是否已不再維護，請先確認是否已安裝 <package>lifecycle-data-openSUSE</package> 套件，接著使用以下指令：
	zypper lifecycle	zypper lifecycle
	Removed Packages	移除的套件
	Removed packages are not shipped as part of the distribution anymore.	移除的套件將不再隨發行版一起發布。
	<package>cuneiform</package>: Package no longer builds and lacks active maintainer. See <link xlink:href="https://bugzilla.suse.com/show_bug.cgi?id=1217234"/>.	<package>chessx</package>：由於啟動問題以及上游專案的問題而被移除。詳情請見 <link xlink:href="https://bugzilla.opensuse.org/show_bug.cgi?id=1192907"/>。
	The following packages were all superseded by <link xlink:href="https://en.opensuse.org/SDB:NVIDIA_SUSE_Prime">NVIDIA SUSE Prime</link>. Also see <xref linkend="drivers-hardware-bumblebee"/>	要了解更多資訊，請參閱 <link xlink:href="https://en.opensuse.org/SDB:NVIDIA_drivers"/>。
	<package>bbswitch</package>	<package>uClibc</package>：已不再維護。
	<package>bumblebee</package>	<package>uClibc</package>：已不再維護。

Loading…

None

Source string changed

English 37 characters edited

5 months ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Chinese (Taiwan) (zh_TW)
No related strings found in the glossary.

String information

Source string description

(itstool) path: sect1/para

Source string location

xml/release-notes.xml:311

String age

5 months ago

Last updated

3 weeks ago

Source string age

5 months ago

Translation file

po/zh_TW.po, string 58