Update of POT and PO files for the manual

1 files changed, 15 insertions, 21 deletions

diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot
index 6b44895a8..7232e9aa4 100644
--- a/po/pot/preparing.pot
+++ b/po/pot/preparing.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-10-26 16:20+0000\n"
+"POT-Creation-Date: 2006-12-25 20:11+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1823,95 +1823,89 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:2079
 #, no-c-format
-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 they tell you about the bad RAM. Still, it's better to be told you have bad memory than to have it silently insert errors in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend=\"Parity-RAM\"/>."
-msgstr ""
-
-#. Tag: para
-#: preparing.xml:2090
-#, 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 ""
 
 #. Tag: title
-#: preparing.xml:2098
+#: preparing.xml:2087
 #, no-c-format
 msgid "The Turbo Switch"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2099
+#: 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 ""
 
 #. Tag: title
-#: preparing.xml:2112
+#: preparing.xml:2101
 #, no-c-format
 msgid "Cyrix CPUs and Floppy Disk Errors"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2113
+#: 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 ""
 
 #. Tag: para
-#: preparing.xml:2121
+#: 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 ""
 
 #. Tag: title
-#: preparing.xml:2131
+#: preparing.xml:2120
 #, no-c-format
 msgid "Peripheral Hardware Settings"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2132
+#: 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:2139
+#: 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 ""
 
 #. Tag: title
-#: preparing.xml:2150
+#: preparing.xml:2139
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2151
+#: preparing.xml:2140
 #, no-c-format
 msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:2164
+#: preparing.xml:2153
 #, no-c-format
 msgid "More than 64 MB RAM"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2165
+#: 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 ""
 
 #. Tag: title
-#: preparing.xml:2174
+#: preparing.xml:2163
 #, no-c-format
 msgid "Display visibility on OldWorld Powermacs"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2175
+#: preparing.xml:2164
 #, no-c-format
 msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver but possibly others as well, may not produce a colormap with reliably results in visible output under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>."
 msgstr ""