Translations by Roy Chan

Roy Chan has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

150 of 1285 results
~
Please enter a space-delimited list of virtual consoles you use. The usual Unix filename wildcards are allowed (*, ? and [...]).
2011-09-18
請輸入您使用的虛擬主控台清單 (以空格 " " 分隔) 。一般 Unix 檔案名稱萬用字亦可以使用 (*, ? 和 [...])。
~
The default value for the options of the keyboard layout is based on the currently defined language/region and the settings in /etc/X11/xorg.conf. This default value is ${XKBOPTIONS}, which is not supported by the configuration program.
2011-09-18
預設的鍵盤排列設置選項,是基於設定在 /etc/X11/xorg.conf 裏面已經定義好的當前 語言/國別。這個預設值是${XKBOPTIONS},設定程式並不支援這個。
~
To avoid problems it is strongly recommended to install the kernel into a partition which fits entirely within the first GB of the disk (by creating a small /boot partition in the beginning of the disk, for example). In the current partitioning scheme it is going to be installed onto the ${SILO_PART} partition which extends up to ${SILO_OFF} mark. Keeping this configuration may result in an unbootable system.
2008-05-12
為了避免這個問題,在此強烈建議您能將 Kernel 安裝在一個完全位於磁碟開頭 1GB 內的磁碟分割區上。(比如說,在磁碟的開頭建立一個小的 /boot 分割區)。在目前的磁碟分割設定裡,它將會被安裝在一個將延伸到 ${SILO_OFF} 標記的 ${SILO_PART} 分割區上。繼續使用這樣的設定可能會導致系統無法開機。
~
Install the SILO boot loader on a hard disk
2008-05-12
將 SILO 開機程式安裝至硬碟上
~
Unsupported partition table on the boot disk
2008-05-12
在開機磁碟上有著不被支援的磁碟分割表
~
SILO installation failed
2008-05-12
SILO 的安裝作業失敗了
~
It is strongly recommended that you go back to partitioning and correct this problem. Keeping the current configuration may result in an unbootable system.
2008-05-12
在此強烈建議您能返回重新切割磁碟並修正這個問題。繼續使用這樣的設定可能會導致系統無法開機。
~
Unsupported boot file system type
2008-05-12
開機檔案系統的格式不被支援
~
Boot partition may cause problems with SILO
2008-05-12
開機分割區可能無法和 SILO 搭配使用
~
Running "/sbin/silo" failed with error code "${ERRCODE}".
2008-05-12
在執行 "/sbin/silo" 時失敗了,錯誤代碼為 "${ERRCODE}"。
~
SILO installation failed. Continue anyway?
2008-05-12
SILO 的安裝作業失敗了。是否無論如何仍然繼續?
~
The 'silo' package failed to install into /target/. Installing SILO as a boot loader is a required step. The install problem might however be unrelated to SILO, so continuing the installation may be possible.
2008-05-12
無法將 silo 套件安裝至 /target/。安裝 SILO 以作為開機程式乃是不可或缺的步驟﹔然而,安裝失敗的原因可能並不是出在 SILO 身上,所以繼續進行安裝作業或許也是無妨的。
~
SILO installation successful
2008-05-12
SILO 的安裝作業完成
~
SILO (Sparc Linux Loader) can only boot the kernel off a disk with the "sun" partition table. In the current partitioning scheme the kernel is going to be installed on the ${SILO_PART} partition located on a disk with the partition table of type "${SILO_DISK}".
2008-05-12
SILO (Sparc Linux Loader) 只能啟動使用了 sun 分割表的磁碟上的 Kernel。在目前的磁碟分割設定裡,Kernel 將會被安裝在使用了 ${SILO_DISK} 格式分割表的磁碟裡的 ${SILO_PART} 分割區。
~
This machine is likely to suffer from a firmware bug, which makes it impossible for SILO (Sparc Linux Loader) to boot a kernel placed farther than 1 GB from the beginning of the disk.
2008-05-12
這個機器很可能會受到韌體上的一些問題所影響,使得它無法使用 SILO (Sparc Linux Loader) 來啟動位於磁碟開頭 1GB 以外的 Kernel。
~
The SILO boot loader has been successfully installed on your new boot partition, and your system should now be able to boot itself.
2008-05-12
SILO 開機程式已經順利安裝至新的啟動分割區,您的系統現在應該能夠自行開機了。
~
In order to be successfully loaded by SILO (Sparc Linux Loader), the kernel must reside on an ext2, ext3 or ufs formatted partition. In the current partitioning scheme the kernel is going to be installed on the ${SILO_PART} partition of type ${SILO_TYPE}.
2008-05-12
為了能順利被 SILO (Sparc Linux Loader) 呼叫,Kernel 必須位於 ext2、ext3 或 utf 格式的分割區內。而以目前的磁碟分割表狀態,Kernel 將會被安裝在 ${SILO_TYPE} 格式的 ${SILO_PART} 分割區。
~
You have chosen to install LILO on a partition that is not the active one. If this partition is not marked active, then LILO will not be loaded by the boot loader. This may cause you to be unable to boot into the system that is being installed.
2008-05-12
您已經選擇了將 LILO 安裝在一個非【啟動】的分割區上。如果分割區沒有設定為【啟動】,LILO 就無法由開機程式載入。這樣可能會導致無法開機進入剛才所安裝好的系統中。
~
The lilo package failed to install into /target/. Installing LILO as a boot loader is a required step. The install problem might however be unrelated to LILO, so continuing the installation may be possible.
2008-05-12
無法將 lilo 套件安裝至 /target/。安裝 LILO 以作為開機程式乃是不可或缺的步驟﹔然而,安裝失敗的原因可能並不是出在 LILO 身上,所以繼續進行安裝作業或許也是無妨的。
~
LILO installation failed. Continue anyway?
2008-05-12
LILO 的安裝作業失敗了。是否無論如何仍然繼續?
~
No mount point is assigned for the xfs file system in partition #${PARTITION} of ${DEVICE}.
2008-05-12
並沒有為 ${DEVICE} 裝置上第 ${PARTITION} 分割區的 xfs 檔案系統指派掛載點。
~
The test of the file system with type xfs in partition #${PARTITION} of ${DEVICE} found uncorrected errors.
2008-05-12
在 ${DEVICE} 裝置上的第 ${PARTITION} 分割區的 xfs 檔案系統所進行的測試中發現了未修正的錯誤。
~
The xfs file system creation in partition #${PARTITION} of ${DEVICE} failed.
2008-05-12
在建立 ${DEVICE} 裝置的第 ${PARTITION} 分割區上的 xfs 檔案系統時失敗了。
~
The jfs file system creation in partition #${PARTITION} of ${DEVICE} failed.
2008-05-12
在建立 ${DEVICE} 裝置的第 ${PARTITION} 分割區上的 jfs 檔案系統時失敗了。
~
Checking the jfs file system in partition #${PARTITION} of ${DEVICE}...
2008-05-12
正在檢驗 ${DEVICE} 裝置上第 ${PARTITION} 分割區的 jfs 檔案系統...
~
The test of the file system with type jfs in partition #${PARTITION} of ${DEVICE} found uncorrected errors.
2008-05-12
在 ${DEVICE} 裝置上的第 ${PARTITION} 分割區的 jfs 檔案系統所進行的測試中發現了未修正的錯誤。
~
No mount point is assigned for the ReiserFS file system in partition #${PARTITION} of ${DEVICE}.
2008-05-12
並沒有為 ${DEVICE} 裝置上第 ${PARTITION} 分割區的 ReiserFS 檔案系統指派掛載點。
~
The ReiserFS file system creation in partition #${PARTITION} of ${DEVICE} failed.
2008-05-12
在建立 ${DEVICE} 裝置的第 ${PARTITION} 分割區上的 ReiserFS 檔案系統時失敗了。
~
The test of the file system with type ReiserFS in partition #${PARTITION} of ${DEVICE} found uncorrected errors.
2008-05-12
在 ${DEVICE} 裝置上的第 ${PARTITION} 分割區的 ReiserFS 檔案系統所進行的測試中發現了未修正的錯誤。
~
Downloading the Release file...
2008-05-11
正在下載 Release 檔...
~
A valid hostname may contain only the numbers 0-9, the lowercase letters a-z, and the minus sign. It must be between 2 and 63 characters long, and may not begin or end with a minus sign.
2008-05-11
正確的主機名稱應當只包含了 數字 0-9、小寫字母 a-z 和 減號。它的長度必須在 2 至 63 個字元之間,且應當不能以減號開頭或結尾。
~
The automatic detection didn't find a CD-ROM drive. You can try to load a specific module if you have a unusual CD-ROM drive (that is neither IDE nor SCSI).
2008-05-11
自動偵測未能找到任何光碟機。如果您的光碟機十分罕見 (既非 IDE 也非 SCSI),請嘗試載入其特定的驅動模組。
~
Virtual consoles in use:
2008-05-11
使用中的虛擬主控台:
~
AltGr key replacement:
2008-05-11
取代 AltGr 鍵
~
Right Alt
2008-05-11
右 Alt
~
You may choose additional locales to be installed from this list.
2008-05-11
您可以從這份列表中選擇其它的語系來進行安裝。
~
Choose a country, territory or area:
2008-05-11
請選擇一個國家、領域或地區:
~
Based on your language, you are probably located in one of these countries or regions.
2008-05-11
根據您所使用的語言,您可能位於以下的國家或地區之一。
~
Choose a locale:
2008-05-11
選擇語系:
~
Choose other locales to be supported:
2007-03-12
請選擇其它希望能被支援的的語系(locale):
~
You may choose additional locales to be installed from this list.
2007-03-12
您可以從這份清單中選擇其它的區域資訊(locale)來進行安裝。
~
Based on your language and country choices, the following locale parameters are supported.
2007-03-12
根據您所選定的語言及國家,以下為已支援的語系參數。
8.
high
2007-03-10
高等
9.
medium
2007-03-10
中等
10.
low
2007-03-10
低等
12.
Packages that use debconf for configuration prioritize the questions they might ask you. Only questions with a certain priority or higher are actually shown to you; all less important questions are skipped.
2011-09-18
如果套件是使用 debconf 來進行設定時,指定在設定過程中將詢問您的問題等級。只有等於或高於這個優先等級的問題才會出現並要求您回答;其它不太重要的問題將會被略過。
14.
For example, this question is of medium priority, and if your priority were already 'high' or 'critical', you wouldn't see this question.
2008-05-11
例如,這個問題的優先等級是【中等】,而您所指定的優先等級卻是【高】或是【迫切】,那麼這個問題將會被直接略過。
2008-05-11
例如,這個問題的優先等級是【中等】,而您所指定的優先等級卻是【高】或是【迫切】,那麼這個問題將會被直接略過。
2008-05-11
例如,這個問題的優先等級是【中等】,而您所指定的優先等級卻是【高】或是【迫切】,那麼這個問題將會被直接略過。
25.
Screenshot
2008-05-11
螢幕快照