summaryrefslogtreecommitdiff
path: root/po/zh_CN/preparing.po
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-12-31 03:18:14 +0000
committerFrans Pop <elendil@planet.nl>2006-12-31 03:18:14 +0000
commit14f198834aea7f3d4c0c196eb076521c24ea398b (patch)
tree1d3f5b9134b5dfa49b203d0999786889f18f2550 /po/zh_CN/preparing.po
parent7420a30685122aa6ef6b44768d95b8f05a32c0f8 (diff)
downloadinstallation-guide-14f198834aea7f3d4c0c196eb076521c24ea398b.zip
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/zh_CN/preparing.po')
-rw-r--r--po/zh_CN/preparing.po277
1 files changed, 119 insertions, 158 deletions
diff --git a/po/zh_CN/preparing.po b/po/zh_CN/preparing.po
index c3f5004d4..1e0f6adb5 100644
--- a/po/zh_CN/preparing.po
+++ b/po/zh_CN/preparing.po
@@ -3,7 +3,7 @@ msgid ""
msgstr ""
"Project-Id-Version: d-i-manual\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-12-29 19:35+0000\n"
+"POT-Creation-Date: 2006-12-31 03:15+0000\n"
"PO-Revision-Date: 2006-10-31 21:30+0800\n"
"Last-Translator: Ji YongGang<jungle@soforge.com>\n"
"Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n"
@@ -3031,48 +3031,13 @@ msgid "FIXME: more information needed &mdash; from a Redbook?"
msgstr "FIXME: more information needed &mdash; from a Redbook?"
#. Tag: title
-#: preparing.xml:2046
+#: preparing.xml:2047
#, no-c-format
msgid "Hardware Issues to Watch Out For"
msgstr "需要留心的硬件问题"
#. Tag: para
-#: preparing.xml:2047
-#, no-c-format
-msgid ""
-"Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It "
-"sometimes works, but is sensitive to temperature and other factors and can "
-"actually damage your system. One of the authors of this document over-"
-"clocked his own system for a year, and then the system started aborting the "
-"<command>gcc</command> program with an unexpected signal while it was "
-"compiling the operating system kernel. Turning the CPU speed back down to "
-"its rated value solved the problem."
-msgstr ""
-"有很多人曾试过把他们的 90 MHz 的 CPU 超频到 100 MHz 使用,以及其他诸如此类的"
-"做法。这有时可行,但是它有赖于外界的温度和其他因素,而且超频可能会损毁您的系"
-"统。本文的作者之一曾把他的系统超频使用了有一年,从那以后他的系统在编译操作系"
-"统的内核时,总是发现 <command>gcc</command> 的运行被意外的信号中止了。后来,"
-"当把 CPU 的频率调回它的标称速度后,问题迎刃而解。"
-
-#. Tag: para
-#: preparing.xml:2057
-#, no-c-format
-msgid ""
-"The <command>gcc</command> compiler is often the first thing to die from bad "
-"memory modules (or other hardware problems that change data unpredictably) "
-"because it builds huge data structures that it traverses repeatedly. An "
-"error in these data structures will cause it to execute an illegal "
-"instruction or access a non-existent address. The symptom of this will be "
-"<command>gcc</command> dying from an unexpected signal."
-msgstr ""
-"如果内存模块有故障的话(或者出现其他会使数据发生异变的硬件故障),"
-"<command>gcc</command> 编译器经常是第一个停止工作的程序。因为它会生成庞大的数"
-"据结构,并把它们在内存中频繁移动。一旦这些 数据结构中有错,就会导致程序执行非"
-"法指令或者访问不存在的地址空间。表现出症状就是<command>gcc</command> 被一个意"
-"外的信号中止运行。"
-
-#. Tag: para
-#: preparing.xml:2067
+#: preparing.xml:2049
#, no-c-format
msgid ""
"Atari TT RAM boards are notorious for RAM problems under Linux; if you "
@@ -3086,114 +3051,14 @@ msgstr ""
"来排除部分内存。<phrase condition=\"FIXME\"><emphasis> FIXME: more "
"description of this needed. </emphasis></phrase>"
-#. Tag: para
-#: preparing.xml:2079
-#, no-c-format
-msgid ""
-"If you do have true-parity RAM and your motherboard can handle it, be sure "
-"to enable any BIOS settings that cause the motherboard to interrupt on "
-"memory parity errors."
-msgstr ""
-"如果您配备有实奇偶校验的内存,而且您的主板也支持这种内存,那么请一定要 在 "
-"BIOS 的设置里开启相应的选项,好让主板在发现奇偶校验错时发生中断。"
-
-#. Tag: title
-#: preparing.xml:2087
-#, no-c-format
-msgid "The Turbo Switch"
-msgstr "加速(Turbo)开关"
-
-#. Tag: para
-#: preparing.xml:2088
-#, no-c-format
-msgid ""
-"Many systems have a <emphasis>turbo</emphasis> switch that controls the "
-"speed of the CPU. Select the high-speed setting. If your BIOS allows you to "
-"disable software control of the turbo switch (or software control of CPU "
-"speed), do so and lock the system in high-speed mode. We have one report "
-"that on a particular system, while Linux is auto-probing (looking for "
-"hardware devices) it can accidentally touch the software control for the "
-"turbo switch."
-msgstr ""
-"有许多系统带有一个 <emphasis>turbo</emphasis> 开关,通过这个开关可以控制 CPU "
-"的运行速度。请把它调节到“高速”。如果您的 BIOS 能让您禁用对加速开关的软件控制"
-"(或者对 CPU 速度的软件控制),那么就请禁用它,这会将系统锁定为高速运行模式。我"
-"们曾受到过报告称,在某台特别的系统上,当 Linux 在自动检测(搜寻硬件设备)时,会"
-"无意中触动加速开关的软件控制。"
-
-#. Tag: title
-#: preparing.xml:2101
-#, no-c-format
-msgid "Cyrix CPUs and Floppy Disk Errors"
-msgstr "Cyrix 出品的 CPU 和软盘错误"
-
-#. Tag: para
-#: preparing.xml:2102
-#, no-c-format
-msgid ""
-"Many users of Cyrix CPUs have had to disable the cache in their systems "
-"during installation, because the floppy disk has errors if they do not. If "
-"you have to do this, be sure to re-enable your cache when you are finished "
-"with installation, as the system runs <emphasis>much</emphasis> slower with "
-"the cache disabled."
-msgstr ""
-"许多 Cyrix CPU 的用户在安装时,必须禁用系统的高速缓存(cache)。如果不这样的"
-"话,就会发生软盘错误。如果您禁用了高速缓存,请在安装完成后重新开启它。因为如"
-"果您继续禁用的话,系统会变慢 <emphasis>很多</emphasis>。"
-
-#. Tag: para
-#: preparing.xml:2110
-#, no-c-format
-msgid ""
-"We don't think this is necessarily the fault of the Cyrix CPU. It may be "
-"something that Linux can work around. We'll continue to look into the "
-"problem. For the technically curious, we suspect a problem with the cache "
-"being invalid after a switch from 16-bit to 32-bit code."
-msgstr ""
-"我们并不认为这一定是 Cyrix CPU 的过错。Linux 或许能想办法避免它。我们将继续 "
-"关注这个问题。基于技术上的好奇,我们猜测这可能是系统从 16 位切换到 32 位模式"
-"时,导致高速缓存失效造成的。"
-
-#. Tag: title
-#: preparing.xml:2120
-#, no-c-format
-msgid "Peripheral Hardware Settings"
-msgstr "外设硬件的设置"
-
-#. Tag: para
-#: preparing.xml:2121
-#, no-c-format
-msgid ""
-"You may have to change some settings or jumpers on your computer's "
-"peripheral cards. Some cards have setup menus, while others rely on jumpers. "
-"This document cannot hope to provide complete information on every hardware "
-"device; what it hopes to provide is useful tips."
-msgstr ""
-"您也许必须得修改您计算机外设板卡上的一些设置或者跳线。有的板卡有设置菜单,而"
-"另一些则使用 跳线。本文档无意为您提供所有硬件设备的全面信息,只不过希望能提供"
-"一些有用的提示。"
-
-#. Tag: para
-#: preparing.xml:2128
-#, no-c-format
-msgid ""
-"If any cards provide <quote>mapped memory</quote>, the memory should be "
-"mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 "
-"megabyte) or at an address at least 1 megabyte greater than the total amount "
-"of RAM in your system."
-msgstr ""
-"如果有板卡提供了<quote>内存映射(mapped memory)</quote>,那么这块内存应该被映"
-"射到介于 0xA0000 和 0xFFFFF (从 640K 到正好 1M)的某块地方,也可以映射到您系统"
-"中总内存容量后 1 MB 以上的地址。"
-
#. Tag: title
-#: preparing.xml:2139
+#: preparing.xml:2064
#, no-c-format
msgid "USB BIOS support and keyboards"
msgstr "USB BIOS 支持与键盘"
#. Tag: para
-#: preparing.xml:2140
+#: preparing.xml:2065
#, no-c-format
msgid ""
"If you have no AT-style keyboard and only a USB model, you may need to "
@@ -3211,29 +3076,13 @@ msgstr ""
"keyboard support</quote>选项。"
#. Tag: title
-#: preparing.xml:2153
-#, no-c-format
-msgid "More than 64 MB RAM"
-msgstr "大于 64 MB 内存"
-
-#. Tag: para
-#: preparing.xml:2154
-#, no-c-format
-msgid ""
-"The Linux Kernel cannot always detect what amount of RAM you have. If this "
-"is the case please look at <xref linkend=\"boot-parms\"/>."
-msgstr ""
-"Linux 内核有时不能检测出您系统中的内存大小。如果这正符合您的情况,请参阅一下"
-"<xref linkend=\"boot-parms\"/>。"
-
-#. Tag: title
-#: preparing.xml:2163
+#: preparing.xml:2079
#, fuzzy, no-c-format
msgid "Display-visibility on OldWorld Powermacs"
msgstr "在 OldWorld Powermacs 上正常显示"
#. Tag: para
-#: preparing.xml:2164
+#: preparing.xml:2081
#, fuzzy, no-c-format
msgid ""
"Some OldWorld Powermacs, most notably those with the <quote>control</quote> "
@@ -3252,6 +3101,118 @@ msgstr ""
"为 256 色,替代 <quote>thousands</quote> 或 <quote>millions</quote>。"
#~ msgid ""
+#~ "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It "
+#~ "sometimes works, but is sensitive to temperature and other factors and "
+#~ "can actually damage your system. One of the authors of this document over-"
+#~ "clocked his own system for a year, and then the system started aborting "
+#~ "the <command>gcc</command> program with an unexpected signal while it was "
+#~ "compiling the operating system kernel. Turning the CPU speed back down to "
+#~ "its rated value solved the problem."
+#~ msgstr ""
+#~ "有很多人曾试过把他们的 90 MHz 的 CPU 超频到 100 MHz 使用,以及其他诸如此类"
+#~ "的做法。这有时可行,但是它有赖于外界的温度和其他因素,而且超频可能会损毁您"
+#~ "的系统。本文的作者之一曾把他的系统超频使用了有一年,从那以后他的系统在编译"
+#~ "操作系统的内核时,总是发现 <command>gcc</command> 的运行被意外的信号中止"
+#~ "了。后来,当把 CPU 的频率调回它的标称速度后,问题迎刃而解。"
+
+#~ msgid ""
+#~ "The <command>gcc</command> compiler is often the first thing to die from "
+#~ "bad memory modules (or other hardware problems that change data "
+#~ "unpredictably) because it builds huge data structures that it traverses "
+#~ "repeatedly. An error in these data structures will cause it to execute an "
+#~ "illegal instruction or access a non-existent address. The symptom of this "
+#~ "will be <command>gcc</command> dying from an unexpected signal."
+#~ msgstr ""
+#~ "如果内存模块有故障的话(或者出现其他会使数据发生异变的硬件故障),"
+#~ "<command>gcc</command> 编译器经常是第一个停止工作的程序。因为它会生成庞大"
+#~ "的数据结构,并把它们在内存中频繁移动。一旦这些 数据结构中有错,就会导致程"
+#~ "序执行非法指令或者访问不存在的地址空间。表现出症状就是<command>gcc</"
+#~ "command> 被一个意外的信号中止运行。"
+
+#~ msgid ""
+#~ "If you do have true-parity RAM and your motherboard can handle it, be "
+#~ "sure to enable any BIOS settings that cause the motherboard to interrupt "
+#~ "on memory parity errors."
+#~ msgstr ""
+#~ "如果您配备有实奇偶校验的内存,而且您的主板也支持这种内存,那么请一定要 在 "
+#~ "BIOS 的设置里开启相应的选项,好让主板在发现奇偶校验错时发生中断。"
+
+#~ msgid "The Turbo Switch"
+#~ msgstr "加速(Turbo)开关"
+
+#~ msgid ""
+#~ "Many systems have a <emphasis>turbo</emphasis> switch that controls the "
+#~ "speed of the CPU. Select the high-speed setting. If your BIOS allows you "
+#~ "to disable software control of the turbo switch (or software control of "
+#~ "CPU speed), do so and lock the system in high-speed mode. We have one "
+#~ "report that on a particular system, while Linux is auto-probing (looking "
+#~ "for hardware devices) it can accidentally touch the software control for "
+#~ "the turbo switch."
+#~ msgstr ""
+#~ "有许多系统带有一个 <emphasis>turbo</emphasis> 开关,通过这个开关可以控制 "
+#~ "CPU 的运行速度。请把它调节到“高速”。如果您的 BIOS 能让您禁用对加速开关的软"
+#~ "件控制(或者对 CPU 速度的软件控制),那么就请禁用它,这会将系统锁定为高速运"
+#~ "行模式。我们曾受到过报告称,在某台特别的系统上,当 Linux 在自动检测(搜寻硬"
+#~ "件设备)时,会无意中触动加速开关的软件控制。"
+
+#~ msgid "Cyrix CPUs and Floppy Disk Errors"
+#~ msgstr "Cyrix 出品的 CPU 和软盘错误"
+
+#~ msgid ""
+#~ "Many users of Cyrix CPUs have had to disable the cache in their systems "
+#~ "during installation, because the floppy disk has errors if they do not. "
+#~ "If you have to do this, be sure to re-enable your cache when you are "
+#~ "finished with installation, as the system runs <emphasis>much</emphasis> "
+#~ "slower with the cache disabled."
+#~ msgstr ""
+#~ "许多 Cyrix CPU 的用户在安装时,必须禁用系统的高速缓存(cache)。如果不这样的"
+#~ "话,就会发生软盘错误。如果您禁用了高速缓存,请在安装完成后重新开启它。因为"
+#~ "如果您继续禁用的话,系统会变慢 <emphasis>很多</emphasis>。"
+
+#~ msgid ""
+#~ "We don't think this is necessarily the fault of the Cyrix CPU. It may be "
+#~ "something that Linux can work around. We'll continue to look into the "
+#~ "problem. For the technically curious, we suspect a problem with the cache "
+#~ "being invalid after a switch from 16-bit to 32-bit code."
+#~ msgstr ""
+#~ "我们并不认为这一定是 Cyrix CPU 的过错。Linux 或许能想办法避免它。我们将继"
+#~ "续 关注这个问题。基于技术上的好奇,我们猜测这可能是系统从 16 位切换到 32 "
+#~ "位模式时,导致高速缓存失效造成的。"
+
+#~ msgid "Peripheral Hardware Settings"
+#~ msgstr "外设硬件的设置"
+
+#~ msgid ""
+#~ "You may have to change some settings or jumpers on your computer's "
+#~ "peripheral cards. Some cards have setup menus, while others rely on "
+#~ "jumpers. This document cannot hope to provide complete information on "
+#~ "every hardware device; what it hopes to provide is useful tips."
+#~ msgstr ""
+#~ "您也许必须得修改您计算机外设板卡上的一些设置或者跳线。有的板卡有设置菜单,"
+#~ "而另一些则使用 跳线。本文档无意为您提供所有硬件设备的全面信息,只不过希望"
+#~ "能提供一些有用的提示。"
+
+#~ msgid ""
+#~ "If any cards provide <quote>mapped memory</quote>, the memory should be "
+#~ "mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 "
+#~ "megabyte) or at an address at least 1 megabyte greater than the total "
+#~ "amount of RAM in your system."
+#~ msgstr ""
+#~ "如果有板卡提供了<quote>内存映射(mapped memory)</quote>,那么这块内存应该被"
+#~ "映射到介于 0xA0000 和 0xFFFFF (从 640K 到正好 1M)的某块地方,也可以映射到"
+#~ "您系统中总内存容量后 1 MB 以上的地址。"
+
+#~ msgid "More than 64 MB RAM"
+#~ msgstr "大于 64 MB 内存"
+
+#~ msgid ""
+#~ "The Linux Kernel cannot always detect what amount of RAM you have. If "
+#~ "this is the case please look at <xref linkend=\"boot-parms\"/>."
+#~ msgstr ""
+#~ "Linux 内核有时不能检测出您系统中的内存大小。如果这正符合您的情况,请参阅一"
+#~ "下<xref linkend=\"boot-parms\"/>。"
+
+#~ msgid ""
#~ "The very best motherboards support parity RAM and will actually tell you "
#~ "if your system has a single-bit error in RAM. Unfortunately, they don't "
#~ "have a way to fix the error, thus they generally crash immediately after "