Update po|pot files after changings in en:

M    po/tl/preparing.po
M    po/ro/preparing.po
M    po/pt/preparing.po
M    po/pt/preseed.po
M    po/da/preparing.po
M    po/ru/preparing.po
M    po/sv/preparing.po
M    po/ja/preparing.po
M    po/zh_TW/preparing.po
M    po/fi/preparing.po
M    po/el/preparing.po
M    po/el/preseed.po
M    po/zh_CN/preparing.po
M    po/pot/preparing.pot
M    po/es/preparing.po
M    po/ko/preparing.po
M    po/nl/preparing.po
M    po/nn/preparing.po
M    po/hu/preparing.po
M    po/vi/preparing.po

1 files changed, 53 insertions, 53 deletions

diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot
index 4dd014c96..cfc941b1e 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: 2013-02-03 09:08+0000\n"
+"POT-Creation-Date: 2013-03-04 08:23+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"
@@ -839,13 +839,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:855
 #, no-c-format
-msgid "If you already have an operating system on your system <phrase arch=\"any-x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, &hellip;) </phrase> which uses the whole disk and you want to stick &debian; on the same disk, you will need to repartition it. &debian; requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Unix systems, but that's not covered here. At the very least you will need a dedicated partition for the &debian; root filesystem."
+msgid "If you already have an operating system on your system <phrase arch=\"any-x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, &hellip;) </phrase> which uses the whole disk and you want to stick &debian; on the same disk, you will need to repartition it. &debian; requires its own hard disk partitions. It cannot be installed on Windows or Mac OS X partitions. It may be able to share some partitions with other Unix systems, but that's not covered here. At the very least you will need a dedicated partition for the &debian; root filesystem."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:874
 #, no-c-format
-msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"any-x86\">, such as the integrated Disk Manager in Windows or fdisk in DOS</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes."
+msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"any-x86\">, such as the integrated Disk Manager in Windows or fdisk in DOS</phrase><phrase arch=\"powerpc\">, such as Disk Utility, Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes."
 msgstr ""
 
 #. Tag: para
@@ -893,7 +893,7 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:943
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-parttype; partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a &arch-parttype; placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the &debian; partition tools later during the actual install, and replace it with &arch-parttype; partitions."
+msgid "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-parttype; partitions should appear before all other partitions on the disk, especially Mac OS X boot partitions. This should be kept in mind when pre-partitioning; you should create a &arch-parttype; placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the &debian; partition tools later during the actual install, and replace it with &arch-parttype; partitions."
 msgstr ""
 
 #. Tag: title
@@ -929,119 +929,119 @@ msgstr ""
 #. Tag: title
 #: preparing.xml:1062
 #, no-c-format
-msgid "MacOS/OSX Partitioning"
+msgid "Mac OS X Partitioning"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1064
 #, no-c-format
-msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>."
+msgid "The <application>Disk Utility</application> application can be found under the <filename>Utilities</filename> menu in Mac OS X Installer. It will not adjust existing partitions; it is limited to partitioning the entire disk at once."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1071
+#: preparing.xml:1070
 #, no-c-format
 msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian-gnu; installer."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1077
+#: preparing.xml:1076
 #, no-c-format
-msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X."
+msgid "&debian; installer partition table editing tools are compatible with OS X, but not with MacOS 9. If you are planning to use both MacOS 9 and OS X, it is best to install OS X and &debian; on one hard drive, and put MacOS 9 on a separate hard drive. Separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1090
+#: preparing.xml:1086
 #, no-c-format
-msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux."
+msgid "GNU/Linux is unable to access information on UFS partitions, but can access HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the Mac OS X and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT file systems are supported by MacOS 9, Mac OS X and GNU/Linux."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1110
+#: preparing.xml:1106
 #, no-c-format
 msgid "Pre-Installation Hardware and Operating System Setup"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1111
+#: preparing.xml:1107
 #, no-c-format
 msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing &debian;. Generally, this involves checking and possibly changing BIOS/system firmware settings for your system. The <quote>BIOS</quote> or <quote>system firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up)."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1126
+#: preparing.xml:1122
 #, no-c-format
 msgid "Invoking the BIOS Set-Up Menu"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1128
+#: preparing.xml:1124
 #, no-c-format
 msgid "The BIOS provides the basic functions needed to boot your machine and to allow your operating system to access your hardware. Your system provides a BIOS setup menu, which is used to configure the BIOS. To enter the BIOS setup menu you have to press a key or key combination after turning on the computer. Often it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1142 preparing.xml:1294
+#: preparing.xml:1138 preparing.xml:1290
 #, no-c-format
 msgid "Boot Device Selection"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1144
+#: preparing.xml:1140
 #, no-c-format
 msgid "Within the BIOS setup menu, you can select which devices shall be checked in which sequence for a bootable operating system. Possible choices usually include the internal harddisks, the CD/DVD-ROM drive and USB mass storage devices such as USB sticks or external USB harddisks. On modern systems there is also often a possibility to enable network booting via PXE."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1152
+#: preparing.xml:1148
 #, no-c-format
 msgid "Depending on the installation media (CD/DVD ROM, USB stick, network boot) you have chosen you should enable the appropriate boot devices if they are not already enabled."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1158
+#: preparing.xml:1154
 #, no-c-format
 msgid "Most BIOS versions allow to call up a boot menu on system startup in which you select from which device the computer should start for the current session. If this option is available, the BIOS usually displays a short message like <quote>press <keycap>F12</keycap> for boot menu</quote> on system startup. The actual key used to select this menu varies from system to system; commonly used keys are <keycap>F12</keycap>, <keycap>F11</keycap> and <keycap>F8</keycap>. Choosing a device from this menu does not change the default boot order of the BIOS, i.e. you can start once from a USB stick while having configured the internal harddisk as the normal primary boot device."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1172
+#: preparing.xml:1168
 #, no-c-format
 msgid "If your BIOS does not provide you with a boot menu to do ad-hoc choices of the current boot device, you have to change your BIOS setup to make the device from which the &d-i; shall be booted the primary boot device."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1178
+#: preparing.xml:1174
 #, no-c-format
 msgid "Unfortunately some computers contain buggy BIOS versions. Booting &d-i; from a USB stick might not work even if there is an appropriate option in the BIOS setup menu and the stick is selected as the primary boot device. On some of these systems using a USB stick as boot medium is impossible; others can be tricked into booting from the stick by changing the device type in the BIOS setup from the default <quote>USB harddisk</quote> or <quote>USB stick</quote> to <quote>USB ZIP</quote> or <quote>USB CDROM</quote>. <phrase condition=\"isohybrid-supported\"> In particular if you use an isohybrid CD/DVD image on a USB stick (see <xref linkend=\"usb-copy-isohybrid\"/>), changing the device type to <quote>USB CDROM</quote> helps on some BIOSes which will not boot from a USB stick in USB harddisk mode.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1193
+#: preparing.xml:1189
 #, no-c-format
 msgid "If you cannot manipulate the BIOS to boot directly from a USB stick you still have the option of using an ISO copied to the stick. Boot &d-i; using <xref linkend=\"boot-drive-files\"/> and, after scanning the hard drives for an installer ISO image, select the USB device and choose an installation image."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1211
+#: preparing.xml:1207
 #, no-c-format
 msgid "Invoking OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1212
+#: preparing.xml:1208
 #, no-c-format
 msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1220
+#: preparing.xml:1216
 #, no-c-format
 msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command (cloverleaf/Apple)</keycap><keycap>Option</keycap><keycap>o</keycap><keycap>f</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1228
+#: preparing.xml:1224
 #, no-c-format
 msgid ""
       "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
@@ -1051,43 +1051,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1241
+#: preparing.xml:1237
 #, no-c-format
 msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save</guibutton> button to have the firmware patches installed to nvram."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1261
+#: preparing.xml:1257
 #, no-c-format
 msgid "Invoking OpenBoot"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1263
+#: preparing.xml:1259
 #, no-c-format
 msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1271
+#: preparing.xml:1267
 #, no-c-format
 msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>&gt;</userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1283
+#: preparing.xml:1279
 #, no-c-format
 msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1296
+#: preparing.xml:1292
 #, no-c-format
 msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1306
+#: preparing.xml:1302
 #, no-c-format
 msgid ""
       "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form: <informalexample> <screen>\n"
@@ -1098,7 +1098,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1329
+#: preparing.xml:1325
 #, no-c-format
 msgid ""
       "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n"
@@ -1107,115 +1107,115 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: preparing.xml:1348
+#: preparing.xml:1344
 #, no-c-format
 msgid "eeprom boot-device=disk1:1"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1358
+#: preparing.xml:1354
 #, no-c-format
 msgid "BIOS Setup"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1359
+#: preparing.xml:1355
 #, no-c-format
 msgid "In order to install &debian-gnu; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1371
+#: preparing.xml:1367
 #, no-c-format
 msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1381
+#: preparing.xml:1377
 #, no-c-format
 msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of &debian;-specific data is needed and where to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the &debian;-specific installation steps."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1398
+#: preparing.xml:1394
 #, no-c-format
 msgid "Native and LPAR installations"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1399
+#: preparing.xml:1395
 #, no-c-format
 msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1413
+#: preparing.xml:1409
 #, no-c-format
 msgid "Installation as a VM guest"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1415
+#: preparing.xml:1411
 #, no-c-format
 msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1425
+#: preparing.xml:1421
 #, no-c-format
 msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters (by specifying <userinput>BINARY</userinput> and <userinput>LOCSITE FIX 80</userinput> in your FTP client). <filename>parmfile.debian</filename> can be in either ASCII or EBCDIC format. A sample <filename>debian.exec</filename> script, which will punch the files in the proper order, is included with the images."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1442
+#: preparing.xml:1438
 #, no-c-format
 msgid "Setting up an installation server"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1444
+#: preparing.xml:1440
 #, no-c-format
 msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1452
+#: preparing.xml:1448
 #, no-c-format
 msgid "The installation server needs to copy the exact directory structure from any &debian-gnu; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree."
 msgstr ""
 
 #. Tag: emphasis
-#: preparing.xml:1461
+#: preparing.xml:1457
 #, no-c-format
 msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1468
+#: preparing.xml:1464
 #, no-c-format
 msgid "Hardware Issues to Watch Out For"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1471
+#: preparing.xml:1467
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1472
+#: preparing.xml:1468
 #, no-c-format
 msgid "If you have no PS/2-style keyboard, but only a USB model, on some very old PCs you may need to enable legacy keyboard emulation in your BIOS setup to be able to use your keyboard in the bootloader menu, but this is not an issue for modern systems. If your keyboard does not work in the bootloader menu, consult your mainboard manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1485
+#: preparing.xml:1481
 #, no-c-format
 msgid "Display-visibility on OldWorld Powermacs"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1487
+#: preparing.xml:1483
 #, no-c-format
 msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap 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 ""