90 files changed, 50806 insertions, 20270 deletions

diff --git a/po/da/boot-installer.po b/po/da/boot-installer.po
index eaddc80d4..5dad9a659 100644
--- a/po/da/boot-installer.po
+++ b/po/da/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-11-14 13:40+0100\n"
 "Last-Translator: Joe Hansen <joedalton2@yahoo.dk>\n"
 "Language-Team: Danish <debian-l10n-danish@lists.debian.org>\n"
@@ -63,8 +63,8 @@ msgid "Booting from TFTP"
 msgstr "Opstart fra TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -74,8 +74,8 @@ msgstr ""
 "netværksopstartsserver (DHCP, RARP eller BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -85,8 +85,8 @@ msgstr ""
 "BOOTP-server."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -102,8 +102,8 @@ msgid "Booting from CD-ROM"
 msgstr "Opstart fra cd-rom"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -119,8 +119,8 @@ msgstr ""
 "indsæt din cd, genstart og fortsæt til næste kapitel."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -136,8 +136,8 @@ msgstr ""
 "som måske vil fungere for dig."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -153,8 +153,8 @@ msgstr ""
 "installationssystemet til cd-rom-drevet."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -399,8 +399,8 @@ msgid "The installer will now start as usual."
 msgstr "Installationsprogrammet vil nu starte som normalt."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Opstart fra en cd-rom"
@@ -419,17 +419,23 @@ msgstr "For at starte installationsprogrammet fra Windows kan du enten"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "hente et installationsmedie for cd-rom/dvd-rom eller USB-drev som beskrevet "
 "i <xref linkend=\"official-cdrom\"/> og <xref linkend=\"boot-usb-files\"/>, "
 "eller"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -439,7 +445,7 @@ msgstr ""
 "win32-loader/stable/win32-loader.exe på &debian;-spejlene,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -455,7 +461,7 @@ msgstr ""
 "<command>setup.exe</command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -467,13 +473,13 @@ msgstr ""
 "installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Opstart fra DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -483,7 +489,7 @@ msgstr ""
 "op fra en gendannelses- eller diagonostikdisk."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -501,7 +507,7 @@ msgstr ""
 "ændre det aktuelle drev, hvis det er krævet."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -524,7 +530,7 @@ msgstr ""
 "Kernen vil indlæse og igangsætte installationssystemet."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -532,7 +538,7 @@ msgstr ""
 "Opstart fra Linux med <command>LILO</command> eller <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -543,7 +549,7 @@ msgstr ""
 "files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -561,7 +567,7 @@ msgstr ""
 "installationsprogrammet op fra, om selvom du bør gøre dette med forsigtighed."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -572,14 +578,14 @@ msgid ""
 "without needing the network."
 msgstr ""
 "Alternativt, hvis du forventer at bevare en eksisterende partition på "
-"harddisken uændret under installationen, så kan du hente filen "
-"<filename>hd-media/initrd.gz</filename> og dens kerne, samt kopiere en cd-iso "
-"(eller dvd-iso) til drevet (sikr dig at filens navn ender med "
-"<literal>.iso</literal>). Installationsprogrammet kan så starte op fra drevet "
-"og installere fra cd/dvd-aftrykket, uden at kræve netværket."
+"harddisken uændret under installationen, så kan du hente filen <filename>hd-"
+"media/initrd.gz</filename> og dens kerne, samt kopiere en cd-iso (eller dvd-"
+"iso) til drevet (sikr dig at filens navn ender med <literal>.iso</literal>). "
+"Installationsprogrammet kan så starte op fra drevet og installere fra cd/dvd-"
+"aftrykket, uden at kræve netværket."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -590,15 +596,15 @@ msgid ""
 "a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 "For <command>LILO</command> skal du konfigurere to essentielle ting i "
-"<filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> for "
-"at indlæse installationsprogrammet <filename>initrd.gz</filename> ved "
+"<filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> for at "
+"indlæse installationsprogrammet <filename>initrd.gz</filename> ved "
 "opstartstidspunktet; </para></listitem> <listitem><para> lad "
 "<filename>vmlinuz</filename>-kernen bruge en RAM-disk som sin rodpartition. "
-"</para></listitem> </itemizedlist> Her er et "
-"<filename>/etc/lilo.conf</filename>-eksempel:"
+"</para></listitem> </itemizedlist> Her er et <filename>/etc/lilo.conf</"
+"filename>-eksempel:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -610,7 +616,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -626,7 +632,7 @@ msgstr ""
 "<userinput>lilo</userinput> og genstart."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -642,7 +648,7 @@ msgstr ""
 "filename> er på den første partition på den første disk i systemet):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -656,7 +662,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -668,7 +674,7 @@ msgstr ""
 "post for installationsprogrammet ville for eksempel være:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -688,7 +694,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -698,13 +704,13 @@ msgstr ""
 "<command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Opstart fra USB-drev"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
 "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -722,13 +728,13 @@ msgstr ""
 "indtaste valgfrie opstartsargumenter, eller bare trykke på &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Opstart fra disketter"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -738,7 +744,7 @@ msgstr ""
 "aftrykkene i <xref linkend=\"create-floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -748,7 +754,7 @@ msgstr ""
 "diskettedrev, luk systemet ned som normalt, og tænd det så igen."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -767,7 +773,7 @@ msgstr ""
 "opstartsprompten."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -783,7 +789,7 @@ msgstr ""
 "en valgmulighed. Ellers udfør en hård genstart ved opstart."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -793,7 +799,7 @@ msgstr ""
 "opstartsdisketten og slutter med prompten <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -810,7 +816,7 @@ msgstr ""
 "findes nedenfor i <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -824,26 +830,26 @@ msgstr ""
 "automatisk."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Opstart med TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Der er forskellige måder at udføre en TFTP-opstart på i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "NIC eller bundkort som understøtter PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -857,13 +863,13 @@ msgstr ""
 "konfigurere din BIOS til at starte op fra netværket."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "NIC med netværks-BootROM"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -871,7 +877,7 @@ msgid ""
 msgstr "Det kan være at dit netværkskort tilbyder TFTP-opstartfunktionalitet."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -881,13 +887,13 @@ msgstr ""
 "håndterede det. Henvis til dette dokument."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -897,13 +903,13 @@ msgstr ""
 "opstartsdisketter og endda bootrom'er som udfører en TFTPboot."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Opstartsskærmen"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -940,7 +946,7 @@ msgstr ""
 "fordobler antallet af muligheder."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -956,7 +962,7 @@ msgstr ""
 "&mdash; og tryk på &enterkey; for at opstarte installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -968,7 +974,7 @@ msgstr ""
 "tilstanden ekspert, i redningstilstand og for automatiserede installationer."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -988,7 +994,7 @@ msgstr ""
 "foretaget."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
 "Choosing the <quote>Help</quote> entry will result in the first help screen "
@@ -1007,9 +1013,9 @@ msgid ""
 msgstr ""
 "Valg af punktet <quote>Hjælp</quote> vil resultere i at den første "
 "hjælpeskærm bliver vist, hvilket giver et overblik over alle tilgængelige "
-"hjælpeskærme. For at returnere til opstartsmenuen efter at hjælpeskærmene "
-"er blevet vist, så tast »menu« ved opstartsprompten og tryk på &enterkey;. "
-"Alle hjælpeskærme har en opstartsprompt hvor opstartskommandoen kan indtastes: "
+"hjælpeskærme. For at returnere til opstartsmenuen efter at hjælpeskærmene er "
+"blevet vist, så tast »menu« ved opstartsprompten og tryk på &enterkey;. Alle "
+"hjælpeskærme har en opstartsprompt hvor opstartskommandoen kan indtastes: "
 "<informalexample><screen>\n"
 "Tryk F1 for hjælpeindeks, eller RETUR for at starte op:\n"
 "</screen></informalexample> Ved denne opstartsprompt kan du enten bare "
@@ -1023,7 +1029,7 @@ msgstr ""
 "userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1041,7 +1047,7 @@ msgstr ""
 "reference til at finde de korrekte taster."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1061,7 +1067,7 @@ msgstr ""
 "quote> (iLO) og HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1082,13 +1088,13 @@ msgstr ""
 "beskrevet i hjælpeteksten."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Cd-indhold"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1113,7 +1119,7 @@ msgstr ""
 "uden at kræve adgang til netværket."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1139,7 +1145,7 @@ msgstr ""
 "opstartsblok for mere konventionelle systemer."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1156,7 +1162,7 @@ msgstr ""
 "læsbare fra EFI-skallen som beskrevet nedenfor."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1179,7 +1185,7 @@ msgstr ""
 "stede før installationen får lov til at fortsætte."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1203,13 +1209,13 @@ msgstr ""
 "eller anden grund ikke starter med den, så brug den anden indstilling."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "VIGTIGT"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1229,13 +1235,13 @@ msgstr ""
 "skalprompten."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Valg 1: Opstart fra vedligeholdelsesmenuen for opstartsindstillinger"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1247,7 +1253,7 @@ msgstr ""
 "systeminitialisering."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1257,7 +1263,7 @@ msgstr ""
 "piletasterne og tryk på <command>RETUR</command>. Dette vil vise en ny menu."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1275,7 +1281,7 @@ msgstr ""
 "bemærke at enheds- og controllerinformationen bør være ens."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1293,7 +1299,7 @@ msgstr ""
 "hvor det bliver krævet at du fortsætter til næste (yderligere) trin."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1302,14 +1308,14 @@ msgid ""
 "line with the arrow keys and press <command>ENTER</command>. This will start "
 "the boot load sequence."
 msgstr ""
-"Du skal kun bruge dette trin, hvis du vælger <command>Debian Inst [Acpi ..."
-"</command>. Mappevisningen vil også vise <command>[Treat like Removable Media "
+"Du skal kun bruge dette trin, hvis du vælger <command>Debian Inst [Acpi ...</"
+"command>. Mappevisningen vil også vise <command>[Treat like Removable Media "
 "Boot]</command> på den næste til den sidste linje. Vælg denne linje med "
 "piletasterne og tryk på <command>RETUR</command>. Dette vil igangsætte "
 "opstartssekvensen."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1321,13 +1327,13 @@ msgstr ""
 "opstartskernen og indstillinger."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Indstilling 2: Opstart fra EFI-skallen"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1336,24 +1342,24 @@ msgid ""
 "the following steps:"
 msgstr ""
 "Hvis, af en eller anden årsag, indstilling 1 ikke lykkes, så genstart "
-"maskinen og når skærmen for EFI-opstartshåndteringen vises, bør der være "
-"en indstilling kaldt <command>EFI Shell [Built-in]</command>. Start "
-"&debian;-installations-cd'en med de følgende trin:"
+"maskinen og når skærmen for EFI-opstartshåndteringen vises, bør der være en "
+"indstilling kaldt <command>EFI Shell [Built-in]</command>. Start &debian;-"
+"installations-cd'en med de følgende trin:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
 "display the EFI Boot Manager page and menu after it completes system "
 "initialization."
 msgstr ""
-"Indsæt cd'en i dvd/cd-drevet og genstart maskinen. Firmwaren vil vise "
-"siden og menuen for EFI-opstartshåndteringen efter, at den er færdig med "
+"Indsæt cd'en i dvd/cd-drevet og genstart maskinen. Firmwaren vil vise siden "
+"og menuen for EFI-opstartshåndteringen efter, at den er færdig med "
 "systeminitialiseringen."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1370,13 +1376,12 @@ msgstr ""
 "startes op fra, og vise dem for konsollen før den viser sin kommandoprompt."
 "De genkendte opstartspartitioner på enheder vi vise et enhedsnavn på "
 "<filename>fs<replaceable>n</replaceable>:</filename>. Alle andre genkendte "
-"partitioner vil blive navngivet <filename>blk<replaceable>n</"
-"replaceable>:</filename>. Hvis du indsættede cd'en lige før du indtastede "
-"skallen, så kan dette tage nogle få ekstra sekunder, da den initialiserer "
-"c-drevet."
+"partitioner vil blive navngivet <filename>blk<replaceable>n</replaceable>:</"
+"filename>. Hvis du indsættede cd'en lige før du indtastede skallen, så kan "
+"dette tage nogle få ekstra sekunder, da den initialiserer c-drevet."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1390,7 +1395,7 @@ msgstr ""
 "replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1400,11 +1405,11 @@ msgid ""
 msgstr ""
 "Indtast <command>fs<replaceable>n</replaceable>:</command> og tryk "
 "<command>RETUR</command> for at vælge den enhed hvor <replaceable>n</"
-"replaceable> er partitionsnummeret for cd'rommen. Skallen vil nu "
-"vise partitionsnummeret som sin prompt."
+"replaceable> er partitionsnummeret for cd'rommen. Skallen vil nu vise "
+"partitionsnummeret som sin prompt."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1414,7 +1419,7 @@ msgstr ""
 "igangsætte opstartssekvensen."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1424,19 +1429,19 @@ msgid ""
 "and options."
 msgstr ""
 "Som ved indstilling 1, igangsætter disse trin &debian;-opstartsindlæseren, "
-"som vil vise en menuside, hvor du kan vælge en opstartskerne og indstillinger. "
-"Du kan også indtaste den kortere kommando <command>fs<replaceable>n</replaceable>"
-":elilo</command> på skalprompten. Fortsæt for at vælge opstartskernen og "
-"indstillinger."
+"som vil vise en menuside, hvor du kan vælge en opstartskerne og "
+"indstillinger. Du kan også indtaste den kortere kommando "
+"<command>fs<replaceable>n</replaceable>:elilo</command> på skalprompten. "
+"Fortsæt for at vælge opstartskernen og indstillinger."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Installation med en seriel konsol"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1447,16 +1452,17 @@ msgid ""
 "serial console. Menu items for the most typical baud rate settings on the "
 "ttyS0 device are preconfigured."
 msgstr ""
-"Du kan vælge at udføre en installation med en skærm og tastatur eller "
-"med brug af en seriel forbindelse. For at bruge en opsætning for skærm/tastatur, "
-"så vælg en indstilling, der indeholder strengen [VGA console]. For at installere "
-"over en seriel forbindelse, så vælg en instilling der indeholder strengen "
-"[<replaceable>BAUD</replaceable> baud serial console], hvor <replaceable>BAUD"
-"</replaceable> er hastigheden for din serielle konsol. Menupunkter for de "
-"typiske indstillinger for baudhastigheder på ttyS0-enheden er prækonfigurerede."
+"Du kan vælge at udføre en installation med en skærm og tastatur eller med "
+"brug af en seriel forbindelse. For at bruge en opsætning for skærm/tastatur, "
+"så vælg en indstilling, der indeholder strengen [VGA console]. For at "
+"installere over en seriel forbindelse, så vælg en instilling der indeholder "
+"strengen [<replaceable>BAUD</replaceable> baud serial console], hvor "
+"<replaceable>BAUD</replaceable> er hastigheden for din serielle konsol. "
+"Menupunkter for de typiske indstillinger for baudhastigheder på ttyS0-"
+"enheden er prækonfigurerede."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1466,11 +1472,11 @@ msgid ""
 msgstr ""
 "I de fleste tilfælde vil du ønske at installationsprogrammet skal bruge den "
 "samme baudhastighed som din forbindelse til EFI-konsollen. Hvis du ikke er "
-"sikker på hvad denne indstilling er sat til, så kan du indhente denne oplysning "
-"med kommandoen <command>baud</command> via EFI-skallen."
+"sikker på hvad denne indstilling er sat til, så kan du indhente denne "
+"oplysning med kommandoen <command>baud</command> via EFI-skallen."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1487,7 +1493,7 @@ msgstr ""
 "classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1506,7 +1512,7 @@ msgstr ""
 "installationsprogrammet i teksttilstand."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1520,13 +1526,13 @@ msgstr ""
 "installationen."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Valg af opstartskernen og indstillinger"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1546,7 +1552,7 @@ msgstr ""
 "gængse indstillinger for kommandolinjen."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1570,7 +1576,7 @@ msgstr ""
 "installationen:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1580,7 +1586,7 @@ msgstr ""
 "med piletasterne."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1592,7 +1598,7 @@ msgstr ""
 "for seriel konsol) specificeres."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1604,7 +1610,7 @@ msgstr ""
 "for &debian;-installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1614,7 +1620,7 @@ msgstr ""
 "opsætte sprogområdet, netværk og diskpartitioner."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1634,7 +1640,7 @@ msgstr ""
 "cd-drevet."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1649,13 +1655,13 @@ msgstr ""
 "netværk."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Konfiguration af serveren"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1679,7 +1685,7 @@ msgstr ""
 "command> til at køre på klienten."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1695,7 +1701,7 @@ msgstr ""
 "opstartsfilerne for et IA-64-system."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1713,7 +1719,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1735,13 +1741,13 @@ msgstr ""
 "pakken <classname>elilo</classname> for detaljer."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Konfiguration af klienten"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1772,7 +1778,7 @@ msgstr ""
 "<filename>elilo.efi</filename> fra serveren."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1788,13 +1794,13 @@ msgstr ""
 "netværket, vil den starte &debian;-installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI TFTP-opstart"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1808,21 +1814,21 @@ msgid ""
 msgstr ""
 "Efter indtastning så bruger kommandoovervågningen <informalexample><screen>\n"
 "bootp():\n"
-"</screen></informalexample> på SGI-maskiner til at starte Linux op og "
-"til at begynde installationen af &debian;-programmet. For at dette skal virke, "
-"så skal du måske ændre indstilling på miljøvariablen <envar>netaddr</envar>. "
+"</screen></informalexample> på SGI-maskiner til at starte Linux op og til at "
+"begynde installationen af &debian;-programmet. For at dette skal virke, så "
+"skal du måske ændre indstilling på miljøvariablen <envar>netaddr</envar>. "
 "Tast <informalexample><screen>\n"
 "unsetenv netaddr\n"
 "</screen></informalexample> i kommandoovervågningen for dette."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Opstartsparametre"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1832,7 +1838,7 @@ msgstr ""
 "<command>bootp():</command> i kommandoskærmen."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1843,26 +1849,26 @@ msgid ""
 "<command>append</command>:"
 msgstr ""
 "Efter kommandoen <command>bootp():</command> kan du angive stien og navnet "
-"på filen der skal igangsættes, hvis du ikke angav et eksplicit navn via din bootp/"
-"dhcp-server. Eksempel: <informalexample><screen>\n"
+"på filen der skal igangsættes, hvis du ikke angav et eksplicit navn via din "
+"bootp/dhcp-server. Eksempel: <informalexample><screen>\n"
 "bootp():/boot/tftpboot.img\n"
 "</screen></informalexample> Yderligere kerneparametre kan sendes via "
 "<command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Cobalt TFTP-opstart"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1872,15 +1878,15 @@ msgid ""
 "network from NFS. It will then display several options on the display. There "
 "are the following two installation methods:"
 msgstr ""
-"Rent faktisk så bruger Cobalt ikke TFTP men NFS til at igangsætte. Du "
-"skal installere en NFS-server og placere installationsfilerne i "
-"<filename>/nfsroot</filename>. Når du igangsætter din Cobalt, så skal "
-"du trykke på venstre og højre musetast på samme tid og maskinen vil så "
-"starte via netværket fra NFS. Den vil så vise flere indstillinger på "
-"skærmen. Der er de følgende to installationsmetoder:"
+"Rent faktisk så bruger Cobalt ikke TFTP men NFS til at igangsætte. Du skal "
+"installere en NFS-server og placere installationsfilerne i <filename>/"
+"nfsroot</filename>. Når du igangsætter din Cobalt, så skal du trykke på "
+"venstre og højre musetast på samme tid og maskinen vil så starte via "
+"netværket fra NFS. Den vil så vise flere indstillinger på skærmen. Der er de "
+"følgende to installationsmetoder:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1889,26 +1895,26 @@ msgid ""
 "connect to the machine with an SSH client you can start with the "
 "installation."
 msgstr ""
-"Via SSH (standard): I dette tilfælde, vil installationsprogrammet konfigurere "
-"netværket via DHCP og starte en SSH-server. Den vil så vise en vilkårlig "
-"adgangskode og andre informationer for logind (såsom IP-adressen) på Cobalt LCD. "
-"Når du forbinder til maskinen med en SSH-klient, så kan du påbegynde "
-"installationen."
+"Via SSH (standard): I dette tilfælde, vil installationsprogrammet "
+"konfigurere netværket via DHCP og starte en SSH-server. Den vil så vise en "
+"vilkårlig adgangskode og andre informationer for logind (såsom IP-adressen) "
+"på Cobalt LCD. Når du forbinder til maskinen med en SSH-klient, så kan du "
+"påbegynde installationen."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
 "port of your Cobalt machine (using 115200 bps) and perform the installation "
 "this way."
 msgstr ""
-"Via seriel konsol: Med brug af et nullmodemkabel, så kan du forbinde til "
-"den serielle port på din Cobaltmaskine (med brug af 115200 bps) og udføre "
+"Via seriel konsol: Med brug af et nullmodemkabel, så kan du forbinde til den "
+"serielle port på din Cobaltmaskine (med brug af 115200 bps) og udføre "
 "installationen på denne måde."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1916,17 +1922,17 @@ msgid ""
 "your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 "Du kan ikke sende eventuelle parametre direkte. I stedet for skal du "
-"redigere filen <filename>/nfsroot/default.colo</filename> på NFS-serveren "
-"og tilføje dine parametre til variablen <replaceable>args</replaceable>."
+"redigere filen <filename>/nfsroot/default.colo</filename> på NFS-serveren og "
+"tilføje dine parametre til variablen <replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390-begrænsninger"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1936,7 +1942,7 @@ msgstr ""
 "session krævet på S/390."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1944,31 +1950,31 @@ msgid ""
 "by starting an ssh session which will launch the standard installation "
 "system."
 msgstr ""
-"Opstartsprocessen starter med en netværksopsætning, som anmoder dig om "
-"flere netværksparametre. Hvis opsætningen er succesfuld, vil du logge "
-"ind på systemet ved at starte en ssh-session, som vil igangsætte "
+"Opstartsprocessen starter med en netværksopsætning, som anmoder dig om flere "
+"netværksparametre. Hvis opsætningen er succesfuld, vil du logge ind på "
+"systemet ved at starte en ssh-session, som vil igangsætte "
 "standardinstallationssystemet."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390-opstartsparametre"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
 "either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
 "debian</filename> is provided with the installation images."
 msgstr ""
-"På S/390 kan du tilføje opstartsparametre i parm-filen. Denne fil kan "
-"enten være i ASCII- eller EBCDIC-format. Et eksempel på en sådan parm-fil "
+"På S/390 kan du tilføje opstartsparametre i parm-filen. Denne fil kan enten "
+"være i ASCII- eller EBCDIC-format. Et eksempel på en sådan parm-fil "
 "<filename>parmfile.debian</filename> følger med installationsaftrykket."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1978,15 +1984,15 @@ msgid ""
 "and <keycap>Delete</keycap> keys together while booting to boot from the "
 "factory default CD/DVD drive."
 msgstr ""
-"Aktuelt er de eneste &arch-title;-underarkitekturer, som understøtter "
-"cd-rom-opstart, PReP/CHRP (dog ikke alle systemer) og New World PowerMacs. "
-"På PowerMacs, hold tasten <keycap>c</keycap>, eller kombinationen af "
+"Aktuelt er de eneste &arch-title;-underarkitekturer, som understøtter cd-rom-"
+"opstart, PReP/CHRP (dog ikke alle systemer) og New World PowerMacs. På "
+"PowerMacs, hold tasten <keycap>c</keycap>, eller kombinationen af "
 "<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Skift</keycap>, "
-"og <keycap>slet</keycap> nede samtidig under opstarten for at starte op "
-"fra fabriksstandardens cd/dvd-drev."
+"og <keycap>slet</keycap> nede samtidig under opstarten for at starte op fra "
+"fabriksstandardens cd/dvd-drev."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -1996,21 +2002,21 @@ msgid ""
 "</screen></informalexample> for an alternative way to boot from the internal "
 "factory default CD/DVD drive type"
 msgstr ""
-"For at starte fra en PowerMac fra et eksternt Firewire cd/dvd-drev "
-"så igangsæt først Open Firmware-prompten (se <xref "
-"linkend=\"invoking-openfirmware\"/>), tast så <informalexample><screen>\n"
+"For at starte fra en PowerMac fra et eksternt Firewire cd/dvd-drev så "
+"igangsæt først Open Firmware-prompten (se <xref linkend=\"invoking-"
+"openfirmware\"/>), tast så <informalexample><screen>\n"
 "0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
-"</screen></informalexample> for en alternativ måde at starte op på fra "
-"den interne fabriksstandards cd/dvd-drevtype"
+"</screen></informalexample> for en alternativ måde at starte op på fra den "
+"interne fabriksstandards cd/dvd-drevtype"
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2019,14 +2025,15 @@ msgid ""
 "floppy drives, so use the floppy drive to launch the installer, and then "
 "point the installer to the CD for the needed files."
 msgstr ""
-"OldWorld PowerMacs vil ikke starte op med en &debian;-cd, da OldWorld-computere "
-"afhang af at en Mac OS ROM CD-opstartsdriver var til stede på cd'en, og en "
-"fri programversion af denne driver er ikke tilgængelig. Alle OldWorld-systemer "
-"har diskettedrev, så brug diskettedrevet til at igangsætte installationsprogrammet, "
-"og peg så installationsprogrammet til cd'en for de krævede filer."
+"OldWorld PowerMacs vil ikke starte op med en &debian;-cd, da OldWorld-"
+"computere afhang af at en Mac OS ROM CD-opstartsdriver var til stede på "
+"cd'en, og en fri programversion af denne driver er ikke tilgængelig. Alle "
+"OldWorld-systemer har diskettedrev, så brug diskettedrevet til at igangsætte "
+"installationsprogrammet, og peg så installationsprogrammet til cd'en for de "
+"krævede filer."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2034,23 +2041,23 @@ msgid ""
 "appears, type"
 msgstr ""
 "For at starte &debian;-cd eller -dvd på Pegasos II-maskiner, så hold tasten "
-"<keycap>Esc</keycap> nede umiddelbart efter at du har trykket på tændknappen, "
-"når SmartFirmware-prompten fremkommer, så tast"
+"<keycap>Esc</keycap> nede umiddelbart efter at du har trykket på "
+"tændknappen, når SmartFirmware-prompten fremkommer, så tast"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Opstart fra harddisk"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2060,25 +2067,25 @@ msgstr ""
 "nogle systemer er det den eneste understøttede installationsmetode."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
 "downloading and placing the needed files as described in <xref linkend="
 "\"boot-drive-files\"/>."
 msgstr ""
-"For at starte installationsprogrammet op fra harddisken, så skal du "
-"allerede have hentet og placeret de krævede filer som beskrevet i "
-"<xref linkend=\"boot-drive-files\"/>."
+"For at starte installationsprogrammet op fra harddisken, så skal du allerede "
+"have hentet og placeret de krævede filer som beskrevet i <xref linkend="
+"\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Opstart af OldWorld PowerMacs fra MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2092,21 +2099,21 @@ msgid ""
 msgstr ""
 "Hvis du opsætter BootX i <xref linkend=\"files-oldworld\"/>, så kan du bruge "
 "den til at starte op i installationssystemet. Dobbeltklik på programikonet "
-"<guiicon>BootX</guiicon>. Klik på knappen <guibutton>Options</guibutton> "
-"og vælg <guilabel>Use Specified RAM Disk</guilabel>. Dette vil give dig "
+"<guiicon>BootX</guiicon>. Klik på knappen <guibutton>Options</guibutton> og "
+"vælg <guilabel>Use Specified RAM Disk</guilabel>. Dette vil give dig "
 "mulighed for at vælge filen <filename>ramdisk.image.gz</filename>. Du skal "
 "måske vælge afkrydsningsboksen <guilabel>No Video Driver</guilabel>, "
-"afhængig af dit udstyr. Klik så på knappen <guibutton>Linux</guibutton> "
-"for at lukke MacOS ned og igangsæt installationsprogrammet."
+"afhængig af dit udstyr. Klik så på knappen <guibutton>Linux</guibutton> for "
+"at lukke MacOS ned og igangsæt installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Opstart af NewWorld Macs fra OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2130,9 +2137,9 @@ msgid ""
 msgstr ""
 "Du har allerede placeret filerne <filename>vmlinux</filename>, "
 "<filename>initrd.gz</filename>, <filename>yaboot</filename> og "
-"<filename>yaboot.conf</filename> på rodniveauet på din HFS-partition i "
-"<xref linkend=\"files-newworld\"/>. Du skal nu starte op i OpenFirmware (se "
-"<xref linkend=\"invoking-openfirmware\"/>). I prompten taster du "
+"<filename>yaboot.conf</filename> på rodniveauet på din HFS-partition i <xref "
+"linkend=\"files-newworld\"/>. Du skal nu starte op i OpenFirmware (se <xref "
+"linkend=\"invoking-openfirmware\"/>). I prompten taster du "
 "<informalexample><screen>\n"
 "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
 "</screen></informalexample> hvor du erstatter <replaceable>x</replaceable> "
@@ -2142,27 +2149,27 @@ msgstr ""
 "Efter nogle få yderligere sekunder vil du se en yaboot-prompt "
 "<informalexample><screen>\n"
 "boot:\n"
-"</screen></informalexample> Ved yaboots <prompt>boot:</prompt>-prompt, "
-"så tast enten <userinput>install</userinput> eller <userinput>install "
+"</screen></informalexample> Ved yaboots <prompt>boot:</prompt>-prompt, så "
+"tast enten <userinput>install</userinput> eller <userinput>install "
 "video=ofonly</userinput> efterfulgt af &enterkey;. Argumentet "
-"<userinput>video=ofonly</userinput> er for maksimal kompatibilitet; du "
-"kan prøve dette hvis <userinput>install</userinput> ikke fungerer. "
-"&debian;-installationsprogrammet bør starte."
+"<userinput>video=ofonly</userinput> er for maksimal kompatibilitet; du kan "
+"prøve dette hvis <userinput>install</userinput> ikke fungerer. &debian;-"
+"installationsprogrammet bør starte."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Opstart fra USB-hukommelsesdrev"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr "Aktuelt kan NewWorld PowerMac-systemer understøtte USB-opstart."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2170,14 +2177,14 @@ msgid ""
 "Open Firmware prompt, since Open Firmware does not search USB storage "
 "devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
-"Sikr dig at du har forberedt alt fra <xref linkend=\"boot-usb-files\"/"
-">. For at starte et Macintosh-system op fra et USB-drev, så skal du bruge "
-"Open Firmware-prompten, da Open Firmware ikke søger på USB-lagerenheder "
-"som standard. Se <xref linkend=\"invoking-openfirmware\"/>."
+"Sikr dig at du har forberedt alt fra <xref linkend=\"boot-usb-files\"/>. For "
+"at starte et Macintosh-system op fra et USB-drev, så skal du bruge Open "
+"Firmware-prompten, da Open Firmware ikke søger på USB-lagerenheder som "
+"standard. Se <xref linkend=\"invoking-openfirmware\"/>."
 
 # # engelsk fejl?
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2191,15 +2198,15 @@ msgid ""
 msgstr ""
 "Du skal undersøge hvor USB-lagerenheden fremgår af enhedstræet, da "
 "<command>ofpath</command> i øjeblikket ikke kan udregne dette automatisk. "
-"Tast <userinput>dev / ls</userinput> og <userinput>devalias</"
-"userinput> i Open Firmware-prompten for at få en liste over alle kendte "
-"enheder og enhedsaliasser. På forfatterens system med forskellige "
-"typer af USB-drev, ser stierne således ud <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
-"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename> og "
+"Tast <userinput>dev / ls</userinput> og <userinput>devalias</userinput> i "
+"Open Firmware-prompten for at få en liste over alle kendte enheder og "
+"enhedsaliasser. På forfatterens system med forskellige typer af USB-drev, "
+"ser stierne således ud <filename>usb0/disk</filename>, <filename>usb0/hub/"
+"disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename> og "
 "<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2217,15 +2224,15 @@ msgstr ""
 "installationsprogrammet op: <informalexample><screen>\n"
 "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
 "tbxi\n"
-"</screen></informalexample> <replaceable>2</replaceable> matcher "
-"partitionen Apple_HFS eller Apple_Bootstrap hvortil du tidligere kopierede "
-"opstartsaftrykket og delen <userinput>,\\\\:tbxi</userinput> instruerer "
-"Open Firmware i at opstarte fra filen med en HFS-filtype »tbxi« (dvs. "
-"<command>yaboot</command>) i mappen tidligere velsignet med "
-"<command>hattrib -b</command>."
+"</screen></informalexample> <replaceable>2</replaceable> matcher partitionen "
+"Apple_HFS eller Apple_Bootstrap hvortil du tidligere kopierede "
+"opstartsaftrykket og delen <userinput>,\\\\:tbxi</userinput> instruerer Open "
+"Firmware i at opstarte fra filen med en HFS-filtype »tbxi« (dvs. "
+"<command>yaboot</command>) i mappen tidligere velsignet med <command>hattrib "
+"-b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2237,7 +2244,7 @@ msgstr ""
 "eller bare trykke på &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2249,13 +2256,13 @@ msgstr ""
 "installationsrapport, som forklaret i <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr "Aktuelt understøtter PReP- og New World PowerMac-systemer netopstart."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2274,24 +2281,24 @@ msgid ""
 "machines) the command <userinput>help boot</userinput> may give a "
 "description of syntax and available options."
 msgstr ""
-"På maskiner med Open Firmware, såsom NewWorld Power Macs, går du i "
-"boot-monitoren (se <xref linkend=\"invoking-openfirmware\"/>) og brug "
-"kommandoen <informalexample><screen>\n"
+"På maskiner med Open Firmware, såsom NewWorld Power Macs, går du i boot-"
+"monitoren (se <xref linkend=\"invoking-openfirmware\"/>) og brug kommandoen "
+"<informalexample><screen>\n"
 "0 &gt; boot enet:0\n"
-"</screen></informalexample> Hvis dette ikke virker, så skal du måske "
-"tilføje filnavnet således: <informalexample><screen>\n"
+"</screen></informalexample> Hvis dette ikke virker, så skal du måske tilføje "
+"filnavnet således: <informalexample><screen>\n"
 "0 &gt; boot enet:0,yaboot\n"
-"</screen></informalexample> PReP- og CHRP-bokse kan have forskellige "
-"måder at adressere netværket på. På en PReP-maskine, kan du prøve "
+"</screen></informalexample> PReP- og CHRP-bokse kan have forskellige måder "
+"at adressere netværket på. På en PReP-maskine, kan du prøve "
 "<informalexample><screen>\n"
 "boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
 "replaceable>,<replaceable>client_ipaddr</replaceable>\n"
-"</screen></informalexample> På nogle PReP-systemer (f.eks. Motorola PowerStack-"
-"maskiner) kan kommandoen <userinput>help boot</userinput> levere en "
-"beskrivelse af syntaks og tilgængelige indstillinger."
+"</screen></informalexample> På nogle PReP-systemer (f.eks. Motorola "
+"PowerStack-maskiner) kan kommandoen <userinput>help boot</userinput> levere "
+"en beskrivelse af syntaks og tilgængelige indstillinger."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2299,25 +2306,25 @@ msgid ""
 "equipped with floppy drives, and attached USB floppy drives are not "
 "supported for booting."
 msgstr ""
-"Opstart fra diskettedrev er understøttet for &arch-title;, selvom "
-"det generelt kun er gældende for OldWorld-systemer. NewWorld-systemer "
-"er ikke udstyret med diskettedrev, og tilsluttede USB-drev er ikke "
-"understøttet for opstart."
+"Opstart fra diskettedrev er understøttet for &arch-title;, selvom det "
+"generelt kun er gældende for OldWorld-systemer. NewWorld-systemer er ikke "
+"udstyret med diskettedrev, og tilsluttede USB-drev er ikke understøttet for "
+"opstart."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
 "in floppy drive after shutting the system down, and before pressing the "
 "power-on button."
 msgstr ""
-"For at starte op fra disketten <filename>boot-floppy-hfs.img</filename>, "
-"så placer den i diskettedrevet efter at systemet er lukket ned, og før "
-"du trykker på tændknappen."
+"For at starte op fra disketten <filename>boot-floppy-hfs.img</filename>, så "
+"placer den i diskettedrevet efter at systemet er lukket ned, og før du "
+"trykker på tændknappen."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2325,13 +2332,13 @@ msgid ""
 "from. A floppy without a valid boot system will be ejected, and the machine "
 "will then check for bootable hard disk partitions."
 msgstr ""
-"For dem der ikke er bekendt med Macintosh-diskettedrevhandlinger: En diskette "
-"placeret i maskinen før opstart vil få første prioritet som opstart. En "
-"diskette uden et gyldigt opstartssystem vil blive skubbte ud, og maskinen "
-"vil så kigge efter harddiskpartitioner, der kan startes op fra."
+"For dem der ikke er bekendt med Macintosh-diskettedrevhandlinger: En "
+"diskette placeret i maskinen før opstart vil få første prioritet som "
+"opstart. En diskette uden et gyldigt opstartssystem vil blive skubbte ud, og "
+"maskinen vil så kigge efter harddiskpartitioner, der kan startes op fra."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2343,13 +2350,13 @@ msgstr ""
 "automatisk efter at rodsystemet er blevet indlæst i hukommelsen."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC-opstartsparametre"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2358,15 +2365,14 @@ msgid ""
 "most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
 "<userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
-"Mange ældre Appleskærme brugte en 640x480 67 Hz-tilstand. Hvis dit "
-"billede fremstår forskudt på en ældre Appleskærm, så prøv at tilføje "
-"opstartsparameteren <userinput>video=atyfb:vmode:6</userinput>, som "
-"vil vælge den tilstand for det meste Mach64- og Rage-videoudstyr. For "
-"Rage 128-udstyr bliver det "
-"<userinput>video=aty128fb:vmode:6</userinput> ."
+"Mange ældre Appleskærme brugte en 640x480 67 Hz-tilstand. Hvis dit billede "
+"fremstår forskudt på en ældre Appleskærm, så prøv at tilføje "
+"opstartsparameteren <userinput>video=atyfb:vmode:6</userinput>, som vil "
+"vælge den tilstand for det meste Mach64- og Rage-videoudstyr. For Rage 128-"
+"udstyr bliver det <userinput>video=aty128fb:vmode:6</userinput> ."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2380,31 +2386,31 @@ msgstr ""
 "På maskiner med OpenBoot, så indtast opstartsskærmen for maskinen som der "
 "installeres på (se <xref linkend=\"invoking-openboot\"/>). brug kommandoen "
 "<userinput>boot net</userinput> til at starte op med fra en TFTP- og RARP-"
-"server, eller prøv <userinput>boot net:bootp</userinput> eller <userinput>boot net:"
-"dhcp</userinput> til at starte op fra en TFTP- og BOOTP- eller DHCP-server. "
-"Du kan sende ekstra opstartsparametre til &d-i; i slutningen af kommandoen "
-"<userinput>boot</userinput>."
+"server, eller prøv <userinput>boot net:bootp</userinput> eller "
+"<userinput>boot net:dhcp</userinput> til at starte op fra en TFTP- og BOOTP- "
+"eller DHCP-server. Du kan sende ekstra opstartsparametre til &d-i; i "
+"slutningen af kommandoen <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
 "which is simply an alias to boot from the SCSI device on ID 6 (or the "
 "secondary master for IDE based systems)."
 msgstr ""
-"De fleste OpenBoot-versioner understøtter kommandoen <userinput>boot cdrom"
-"</userinput>, hvilket kun er et alias for at starte fra SCSI-enheden på ID 6 "
+"De fleste OpenBoot-versioner understøtter kommandoen <userinput>boot cdrom</"
+"userinput>, hvilket kun er et alias for at starte fra SCSI-enheden på ID 6 "
 "(eller den sekundære master for IDE-baserede systemer)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM-beskeder"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2414,19 +2420,18 @@ msgid ""
 "information."
 msgstr ""
 "Hvis du ikke kan starte op fordi du får beskeder om et problem med "
-"<quote>IDPROM</quote>, så er det muligt at dit NVRAM-batteri, som "
-"indeholder konfigurationsinformation for din firmware er løbet tør. "
-"se <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM OSS</ulink> for "
-"yderligere information."
+"<quote>IDPROM</quote>, så er det muligt at dit NVRAM-batteri, som indeholder "
+"konfigurationsinformation for din firmware er løbet tør. se <ulink url="
+"\"&url-sun-nvram-faq;\">Sun NVRAM OSS</ulink> for yderligere information."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Tilgængelighed"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2444,24 +2449,23 @@ msgstr ""
 "Nogle brugere kan have brug for specifik understøtelse, f.eks. på grund af "
 "en synshæmmelse. <phrase arch=\"ia64;powerpc;x86\">USB-brailleskærme "
 "detekteres automatisk (ikke serielle skærme forbundet via en seriel-til-USB-"
-"konvertering), men de fleste andre</phrase> "
-"<phrase arch=\"arm;hppa;mips;mipsel;sparc\"> "
-"De fleste</phrase> funktioner for tilgængelighed skal aktiveres manuelt. "
-"<phrase arch=\"x86\">På maskiner som understøtter det, så afgiver opstartsmenuen "
-"en biplyd når den er klar til at modtage tastaturtryk.</phrase> Nogle "
-"opstartsparametre kan <phrase arch=\"x86\">så</phrase> tilføjes for at aktivere "
-"tilgængelighedsfunktioner<phrase arch=\"x86\"> (se også "
-"<xref linkend=\"boot-screen\"/>)</phrase>. Bemærk at på de fleste arkitekturer "
-"fortolker opstartsindlæseren dit tastatur som et QERTY-tastatur."
+"konvertering), men de fleste andre</phrase> <phrase arch=\"arm;hppa;mips;"
+"mipsel;sparc\"> De fleste</phrase> funktioner for tilgængelighed skal "
+"aktiveres manuelt. <phrase arch=\"x86\">På maskiner som understøtter det, så "
+"afgiver opstartsmenuen en biplyd når den er klar til at modtage tastaturtryk."
+"</phrase> Nogle opstartsparametre kan <phrase arch=\"x86\">så</phrase> "
+"tilføjes for at aktivere tilgængelighedsfunktioner<phrase arch=\"x86\"> (se "
+"også <xref linkend=\"boot-screen\"/>)</phrase>. Bemærk at på de fleste "
+"arkitekturer fortolker opstartsindlæseren dit tastatur som et QERTY-tastatur."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB-brailleskærme"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2475,21 +2479,21 @@ msgid ""
 msgstr ""
 "USB-brailleskærme bør detekteres automatisk. En tekstversion af "
 "installationsprogrammet vil så blive valgt automatisk og understøttelse for "
-"brailleskærmen vil automatisk blive installeret på målsystemet. Du kan "
-"så bare trykke på &enterkey; ved opstartsmenuen. Når <classname>brltty</"
+"brailleskærmen vil automatisk blive installeret på målsystemet. Du kan så "
+"bare trykke på &enterkey; ved opstartsmenuen. Når <classname>brltty</"
 "classname> er startet, så kan du vælge en brailletabel ved at indtaste "
 "præferencemenuen. Dokumentation for genvejstaster til brailleenheder er "
 "tilgængelige på <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
 "classname> hjemmesiden</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Serielle brailleskærme"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2510,32 +2514,32 @@ msgid ""
 "devices is available on the <ulink url=\"&url-brltty-driver-help;"
 "\"><classname>brltty</classname> website</ulink>."
 msgstr ""
-"Serielle brailleskærme kan ikke detekteres på en sikker måde automatisk "
-"(da det kan ødelægge nogle af dem). Du skal derfor tilføje opstartsparameteren "
+"Serielle brailleskærme kan ikke detekteres på en sikker måde automatisk (da "
+"det kan ødelægge nogle af dem). Du skal derfor tilføje opstartsparameteren "
 "<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
 "replaceable>,<replaceable>table</replaceable></userinput> for at fortælle "
 "<classname>brltty</classname> hvilken driver den skal bruge. "
-"<replaceable>driver</replaceable> skal erstattes af driverkoden i to bogstaver "
-"for din terminal (se <ulink url=\"&url-brltty-manual;\">BRLTTY-manualen</ulink>). "
-"<replaceable>port</replaceable> skal erstattes af navnet for den serielle port "
-"skærmen er forbundet til, <userinput>ttyS0</userinput> er standarden, "
-"<userinput>ttyUSB0</userinput> kan typisk bruges når der bruges et seriel-til-"
-"USB-konverteringsprogram. <replaceable>table</replaceable> er navnet "
-"for brailletabellen, der skal bruges (se <ulink url=\"&url-brltty-manual;\">"
-"BRLTTY-manualen</ulink>); den engelske tabel er standarden. Bemærk at tabellen "
-"kan ændres senere ved at indtaste præferencemenuen. Dokumentation vedrørende "
-"genvejstaster for brailleenheder er tilgængelig på "
-"<ulink url=\"&url-brltty-driver-help;"
-"\"><classname>brltty</classname> hjemmesiden</ulink>."
+"<replaceable>driver</replaceable> skal erstattes af driverkoden i to "
+"bogstaver for din terminal (se <ulink url=\"&url-brltty-manual;\">BRLTTY-"
+"manualen</ulink>). <replaceable>port</replaceable> skal erstattes af navnet "
+"for den serielle port skærmen er forbundet til, <userinput>ttyS0</userinput> "
+"er standarden, <userinput>ttyUSB0</userinput> kan typisk bruges når der "
+"bruges et seriel-til-USB-konverteringsprogram. <replaceable>table</"
+"replaceable> er navnet for brailletabellen, der skal bruges (se <ulink url="
+"\"&url-brltty-manual;\">BRLTTY-manualen</ulink>); den engelske tabel er "
+"standarden. Bemærk at tabellen kan ændres senere ved at indtaste "
+"præferencemenuen. Dokumentation vedrørende genvejstaster for brailleenheder "
+"er tilgængelig på <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
+"classname> hjemmesiden</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "Understøttelse af talesyntese via programmer"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2550,13 +2554,13 @@ msgstr ""
 "sprog (hvis tilgængelig i <classname>espeak</classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Understøttelse af talesyntese via udstyr"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2564,11 +2568,11 @@ msgid ""
 "install</quote> entry in the boot menu."
 msgstr ""
 "Understøttelse for talesyntese via udstyrsenheder er kun tilgængelig sammen "
-"med understøttelse for et grafisk installationsprogram. Du skal derfor "
-"vælge et punkt med <quote>Grafisk installation</quote> i opstartsmenuen."
+"med understøttelse for et grafisk installationsprogram. Du skal derfor vælge "
+"et punkt med <quote>Grafisk installation</quote> i opstartsmenuen."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2581,23 +2585,23 @@ msgid ""
 "speech synthesis device will be automatically installed on the target system."
 msgstr ""
 "Enheder for udstyrstalesyntese kan ikke automatisk detekteres. Du skal "
-"derfor tilføje opstartsparameteren <userinput>speakup.synth=<replaceable>driver</"
-"replaceable></userinput> for at fortælle <classname>speakup</classname> "
-"hvilken driver den skal bruge. <replaceable>driver</replaceable> "
-"skal erstattes af driverkoden for din enhed (se <ulink url=\"&url-"
-"speakup-driver-codes;\">driverkodelisten</ulink>). Den tekstmæssige "
-"udgave af installationsprogramemt vil så automatisk blive valgt, og "
-"understøttelse for talesynteseenheden vil automatisk blive installeret "
-"på målsystemet."
+"derfor tilføje opstartsparameteren <userinput>speakup."
+"synth=<replaceable>driver</replaceable></userinput> for at fortælle "
+"<classname>speakup</classname> hvilken driver den skal bruge. "
+"<replaceable>driver</replaceable> skal erstattes af driverkoden for din "
+"enhed (se <ulink url=\"&url-speakup-driver-codes;\">driverkodelisten</"
+"ulink>). Den tekstmæssige udgave af installationsprogramemt vil så "
+"automatisk blive valgt, og understøttelse for talesynteseenheden vil "
+"automatisk blive installeret på målsystemet."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Bundkortenheder"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2607,31 +2611,31 @@ msgid ""
 "parameter. This will however reduce the number of available languages."
 msgstr ""
 "Nogle tilgængelighedsenheder er fysiske bundkort som er indsat i selve "
-"maskinen og som læser tekst direkte fra videohukommelsen. For at få dem "
-"til at virke skal understøttelse af framebuffer være deaktiveret ved "
-"at bruge opstartsparameteren <userinput arch="
-"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Dette "
-"vil dog reducere antallet af tilgængelige sprog."
+"maskinen og som læser tekst direkte fra videohukommelsen. For at få dem til "
+"at virke skal understøttelse af framebuffer være deaktiveret ved at bruge "
+"opstartsparameteren <userinput arch=\"x86\">vga=normal</userinput> "
+"<userinput>fb=false</userinput>. Dette vil dog reducere antallet af "
+"tilgængelige sprog."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
 "adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
-"Hvis det ønskes kan en tekstversion af opstartsindlæseren aktiveres "
-"før tilføjelse af opstartsparameteren ved at indtaste <userinput>h</userinput> "
+"Hvis det ønskes kan en tekstversion af opstartsindlæseren aktiveres før "
+"tilføjelse af opstartsparameteren ved at indtaste <userinput>h</userinput> "
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Tema med høj kontrast"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2643,24 +2647,24 @@ msgstr ""
 "<userinput>theme=dark</userinput> til opstartsparameteren."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Forhåndsindstilling"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
 "preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-"Alternativt kan &debian; installeres fuldstændig automatisk med brugen "
-"af forhåndsindstillinger. Dette er dokumenteret i "
-"<xref linkend=\"appendix-preseed\"/>."
+"Alternativt kan &debian; installeres fuldstændig automatisk med brugen af "
+"forhåndsindstillinger. Dette er dokumenteret i <xref linkend=\"appendix-"
+"preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2668,13 +2672,13 @@ msgid ""
 "can auto-detect information about your peripherals. However, in some cases "
 "you'll have to help the kernel a bit."
 msgstr ""
-"Opstartsparametre er parametre for Linuxkernen, som generelt bruges til "
-"at sikre at perifære enheder håndteres korrekt. I de fleste tilfælde kan "
-"kernen automatisk detektere information om dine perifære enheder. Dog skal "
-"du i nogle tilfælde hjælpe kernen lidt."
+"Opstartsparametre er parametre for Linuxkernen, som generelt bruges til at "
+"sikre at perifære enheder håndteres korrekt. I de fleste tilfælde kan kernen "
+"automatisk detektere information om dine perifære enheder. Dog skal du i "
+"nogle tilfælde hjælpe kernen lidt."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2682,13 +2686,14 @@ msgid ""
 "correctly. It probably will. If not, you can reboot later and look for any "
 "special parameters that inform the system about your hardware."
 msgstr ""
-"Hvis dette er den første gang du starter systemet op, så prøv standardparametrene "
-"for opstart (dvs. prøv uden at angive parametre) og se om det virker korrekt. "
-"Det vil det sikkert. Hvis ikke så kan du genstarte senere og kigge efter "
-"eventuelle specielle parametre som informerer dit system om dit udstyr."
+"Hvis dette er den første gang du starter systemet op, så prøv "
+"standardparametrene for opstart (dvs. prøv uden at angive parametre) og se "
+"om det virker korrekt. Det vil det sikkert. Hvis ikke så kan du genstarte "
+"senere og kigge efter eventuelle specielle parametre som informerer dit "
+"system om dit udstyr."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2697,14 +2702,14 @@ msgid ""
 "the most salient parameters. Some common gotchas are included below in <xref "
 "linkend=\"boot-troubleshooting\"/>."
 msgstr ""
-"Information om mange opstartsparametre kan findes i <ulink url=\"http://"
-"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
-"inklusive fif for sjældent udstyr. Dette afsnit indeholder kun en skitse "
-"med de mest indlysende parametre. Nogle gængse problemstillinger er "
-"inkluderet nedenfor i <xref linkend=\"boot-troubleshooting\"/>."
+"Information om mange opstartsparametre kan findes i <ulink url=\"http://www."
+"tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
+"inklusive fif for sjældent udstyr. Dette afsnit indeholder kun en skitse med "
+"de mest indlysende parametre. Nogle gængse problemstillinger er inkluderet "
+"nedenfor i <xref linkend=\"boot-troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
 msgid ""
 "If you are booting with a serial console, generally the kernel will "
@@ -2715,16 +2720,16 @@ msgid ""
 "is your serial device, which is usually something like <filename>ttyS0</"
 "filename>."
 msgstr ""
-"Hvis du starter op med en seriel konsol, vil kernen generelt detektere "
-"dette automatisk. Hvis du har et videokort (framebuffer) og et tastatur "
-"der også er tilsluttet computeren, som du ønsker at starte op via seriel "
-"konsol, så skal du måske sende argumentet <userinput>console=<replaceable>"
-"device</replaceable></userinput> til kernen, hvor <replaceable>device</replaceable> "
+"Hvis du starter op med en seriel konsol, vil kernen generelt detektere dette "
+"automatisk. Hvis du har et videokort (framebuffer) og et tastatur der også "
+"er tilsluttet computeren, som du ønsker at starte op via seriel konsol, så "
+"skal du måske sende argumentet <userinput>console=<replaceable>device</"
+"replaceable></userinput> til kernen, hvor <replaceable>device</replaceable> "
 "er din seriel enhed, hvilket normalt ligner noget ala <filename>ttyS0</"
 "filename>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
 msgid ""
 "In order to ensure the terminal type used by the installer matches your "
@@ -2739,20 +2744,20 @@ msgid ""
 "indeed perform translation into the <literal>screen</literal> terminal type, "
 "which is very close to <literal>vt102</literal>."
 msgstr ""
-"For at sikre at terminaltypen brugt af installationsprogrammet matcher "
-"din terminalemulator kan parameteren  <userinput>TERM=<replaceable>type</"
-"replaceable></userinput> tilføjes. Bemærk at installationsprogrammet "
-"kun understøtter de følgende terminaltyper: <literal>linux</literal>, <literal>bterm</"
-"literal>, <literal>ansi</literal>, <literal>vt102</literal> og "
-"<literal>dumb</literal>. Standarden for seriel konsol i &d-i; er "
+"For at sikre at terminaltypen brugt af installationsprogrammet matcher din "
+"terminalemulator kan parameteren  <userinput>TERM=<replaceable>type</"
+"replaceable></userinput> tilføjes. Bemærk at installationsprogrammet kun "
+"understøtter de følgende terminaltyper: <literal>linux</literal>, "
+"<literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> "
+"og <literal>dumb</literal>. Standarden for seriel konsol i &d-i; er "
 "<userinput>vt102</userinput>. Hvis du bruger et virtualiseringsværktøj, som "
 "ikke selv tilbyder konvertering til sådanne terminaltyper, f.eks. QEMU/KVM, "
-"så kan du starte den inden i en <command>screen</command>-session. Den "
-"vil udføre oversættelse til <literal>screen</literal>-terminaltypen, "
-"som er meget tæt på <literal>vt102</literal>."
+"så kan du starte den inden i en <command>screen</command>-session. Den vil "
+"udføre oversættelse til <literal>screen</literal>-terminaltypen, som er "
+"meget tæt på <literal>vt102</literal>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2766,13 +2771,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Parametre for &debian;-installationsprogrammet"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2780,14 +2785,14 @@ msgid ""
 "use 32 command line options and 32 environment options. If these numbers are "
 "exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
-"Installationssystemet genkender nogle få yderligere opstartsparametre"
-"<footnote> <para> med aktuelle kerner (2.6.9 eller nyere) kan du bruge "
-"32 kommandolinjeindstillinger og 32 miljøindstillinger. Hvis disse tal "
-"overskrides går kernen i panik. </para> </footnote> hvilket kan være "
-"nyttigt."
+"Installationssystemet genkender nogle få yderligere "
+"opstartsparametre<footnote> <para> med aktuelle kerner (2.6.9 eller nyere) "
+"kan du bruge 32 kommandolinjeindstillinger og 32 miljøindstillinger. Hvis "
+"disse tal overskrides går kernen i panik. </para> </footnote> hvilket kan "
+"være nyttigt."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2796,27 +2801,28 @@ msgid ""
 "brackets behind the (normal) long form. Examples in this manual will "
 "normally use the short form too."
 msgstr ""
-"Et antal parametre har en <quote>kort form</quote> som hjælper med at "
-"undgå begrænsningerne i kernens indstillinger for kommandolinjen og "
-"gør indtastning af parametre nemmere. Hvis en parameter har en kort form, "
-"så vil den blive vist i parenteser bag den (normale) lange form. Eksempler "
-"i denne manual vil normalt også bruge den korte form."
+"Et antal parametre har en <quote>kort form</quote> som hjælper med at undgå "
+"begrænsningerne i kernens indstillinger for kommandolinjen og gør "
+"indtastning af parametre nemmere. Hvis en parameter har en kort form, så vil "
+"den blive vist i parenteser bag den (normale) lange form. Eksempler i denne "
+"manual vil normalt også bruge den korte form."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (prioritet)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
-"Denne parameter angiver den laveste prioritet beskeder kan have for at blive vist."
+"Denne parameter angiver den laveste prioritet beskeder kan have for at blive "
+"vist."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2830,7 +2836,7 @@ msgstr ""
 "justerer installationsprogrammet prioriteten efter behov."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2841,22 +2847,22 @@ msgid ""
 "system will display only critical messages and try to do the right thing "
 "without fuss."
 msgstr ""
-"Hvis du tilføjer <userinput>priority=medium</userinput> som opstartsparameter, "
-"vil du få vist installationsmenuen og opnå yderligere kontrol over installationen. "
-"Når <userinput>priority=low</userinput> bruges, vises alle beskeder (dette "
-"svarer til opstartsmetoden <emphasis>expert</emphasis>. Med "
-"<userinput>priority=critical</userinput> vil installationssystemet kun vise "
-"kritiske beskeder og forsøge at udføre tingene korrekt uden hensyn til "
-"unødvendige detaljer."
+"Hvis du tilføjer <userinput>priority=medium</userinput> som "
+"opstartsparameter, vil du få vist installationsmenuen og opnå yderligere "
+"kontrol over installationen. Når <userinput>priority=low</userinput> bruges, "
+"vises alle beskeder (dette svarer til opstartsmetoden <emphasis>expert</"
+"emphasis>. Med <userinput>priority=critical</userinput> vil "
+"installationssystemet kun vise kritiske beskeder og forsøge at udføre "
+"tingene korrekt uden hensyn til unødvendige detaljer."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2877,29 +2883,29 @@ msgid ""
 msgstr ""
 "Denne opstartsparameter kontroller typen af brugergrænseflade brugt af "
 "installationsprogrammet. De aktuelt mulige parameterindstillinger er: "
-"<itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
-"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
+"<itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</"
 "userinput></para> </listitem><listitem> "
-"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
-"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
-"</listitem> </itemizedlist> Standardbrugerfladen er "
+"<para><userinput>DEBIAN_FRONTEND=text</userinput></para> </"
+"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> "
+"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></"
+"para> </listitem> </itemizedlist> Standardbrugerfladen er "
 "<userinput>DEBIAN_FRONTEND=newt</userinput>. "
 "<userinput>DEBIAN_FRONTEND=text</userinput> kan foretrækkes for serielle "
 "konsolinstallationer. Nogle specialiserede typer af installationsmedier "
 "tilbyder måske kun et begrærset udvalg af brugerflader, men brugerfladerne "
 "<userinput>newt</userinput> og <userinput>text</userinput> er tilgængelige "
 "på de fleste gængse installationsmedier. På arkitekturer som understøtter "
-"det, bruger det grafiske installationsprogram brugerfladen "
-"<userinput>gtk</userinput>."
+"det, bruger det grafiske installationsprogram brugerfladen <userinput>gtk</"
+"userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2907,55 +2913,56 @@ msgid ""
 "strategic points in the boot process. (Exit the shells to continue the boot "
 "process.)"
 msgstr ""
-"Angivelse af denne opstartsparameter til 2 vil medføre at installationsprogrammets "
-"opstartsprogram bliver udførligt logget. Indstilligen 3 vil gøre fejlsøgningsskaller "
-"tilgængelige på strategiske steder i opstartsprocessen. (Afslut skallerne for at "
-"fortsætte opstartsprocessen)."
+"Angivelse af denne opstartsparameter til 2 vil medføre at "
+"installationsprogrammets opstartsprogram bliver udførligt logget. "
+"Indstilligen 3 vil gøre fejlsøgningsskaller tilgængelige på strategiske "
+"steder i opstartsprocessen. (Afslut skallerne for at fortsætte "
+"opstartsprocessen)."
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Dette er standarden."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Mere uddybende end normalt."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Masser af fejlsøgningsinformation."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2965,48 +2972,48 @@ msgstr ""
 "detaljeret fejlsøgning. Afslut skallen for at fortsætte opstarten."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
 "installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
 "userinput>"
 msgstr ""
-"Værdien på denne parameter er stien til enehden hvor &debian;-installationsprogrammet "
-"skal indlæses fra. For eksempel, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
-"userinput>"
+"Værdien på denne parameter er stien til enehden hvor &debian;-"
+"installationsprogrammet skal indlæses fra. For eksempel, "
+"<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
 "floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
-"Opstartsdisketten, som normalt skanner alle diskettedrev den kan for at finde "
-"roddisketten, kan overskrives med denne parameter til kun at kigge efter en "
-"enhed."
+"Opstartsdisketten, som normalt skanner alle diskettedrev den kan for at "
+"finde roddisketten, kan overskrives med denne parameter til kun at kigge "
+"efter en enhed."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3018,13 +3025,13 @@ msgstr ""
 "angivet, er portstandarden systemloggens standardport 514."
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3036,30 +3043,30 @@ msgstr ""
 "hukommelse. Mulige værdier er 1 og 2. Se også <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
 "Useful for unattended installations where physical security is limited."
 msgstr ""
-"Forhindrer installationsprogrammet i at tilbyder interaktive skaller på "
-"tty2 og tty3. Nyttig for installationer der ikke overvåges og hvor "
-"fysisk sikkerhed er begrænset."
+"Forhindrer installationsprogrammet i at tilbyder interaktive skaller på tty2 "
+"og tty3. Nyttig for installationer der ikke overvåges og hvor fysisk "
+"sikkerhed er begrænset."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3069,21 +3076,21 @@ msgid ""
 "messages about bterm or bogl, a blank screen, or a freeze within a few "
 "minutes after starting the install."
 msgstr ""
-"Nogle arkitekturer bruger kerneframebufferen til at tilbyder installation "
-"i et antal sprog. Hvis framebuffer medfører et problem på dit system, så "
-"kan du deaktivere funktionen med parameteren <userinput arch=\"x86\">vga=normal</"
+"Nogle arkitekturer bruger kerneframebufferen til at tilbyder installation i "
+"et antal sprog. Hvis framebuffer medfører et problem på dit system, så kan "
+"du deaktivere funktionen med parameteren <userinput arch=\"x86\">vga=normal</"
 "userinput> <userinput>fb=false</userinput>. Symptomer på problemer er "
-"fejlbeskeder om bterm eller bogl, en blank skærm eller at installationen fryser "
-"efter et par minutter."
+"fejlbeskeder om bterm eller bogl, en blank skærm eller at installationen "
+"fryser efter et par minutter."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Disse problemer er blevet indrapporteret på hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3096,19 +3103,19 @@ msgstr ""
 "På grund af visningsproblemer på nogle systemer, så er understøttelse af "
 "framebuffer <emphasis>deaktiveret som standard</emphasis> for &arch-title;. "
 "Dette kan medføre visninger, der ikke er så kønne, på systemer som ikke "
-"korrekt understøtter framebufferen, såsom med ATI-grafikkort. Hvis du "
-"ser problemer i installationsprogrammet, så kan du prøve at starte med "
-"parameteren <userinput>debian-installer/framebuffer=true</userinput> "
-"eller <userinput>fb=true</userinput> i kort form."
+"korrekt understøtter framebufferen, såsom med ATI-grafikkort. Hvis du ser "
+"problemer i installationsprogrammet, så kan du prøve at starte med "
+"parameteren <userinput>debian-installer/framebuffer=true</userinput> eller "
+"<userinput>fb=true</userinput> i kort form."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (tema)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3117,21 +3124,21 @@ msgid ""
 "designed for visually impaired users. Set the theme by booting with "
 "<userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
-"Et tema bestemmer hvordan brugergrænsefladen for installationsprogrammet "
-"ser ud (farver, ikoner etc.). Hvilke temaer der er tilgængelige afviger "
-"per brugerflade. Aktuelt har både newt- og gtk-brugerfladerne kun et "
+"Et tema bestemmer hvordan brugergrænsefladen for installationsprogrammet ser "
+"ud (farver, ikoner etc.). Hvilke temaer der er tilgængelige afviger per "
+"brugerflade. Aktuelt har både newt- og gtk-brugerfladerne kun et "
 "<quote>dark</quote>-tema, som blev designet for de visuelt synshæmmede "
-"brugere. Angiv temaet ved at starte med "
-"<userinput>theme=<replaceable>dark</replaceable></userinput>."
+"brugere. Angiv temaet ved at starte med <userinput>theme=<replaceable>dark</"
+"replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3139,13 +3146,13 @@ msgid ""
 "the obtained settings. You can get to the manual network setup only in case "
 "the DHCP probe fails."
 msgstr ""
-"Som standard vil &d-i; automatisk søge efter netværkskonfiguration via "
-"DHCP. Hvis søgningen lykkes, vil du ikke få mulighed for at gennemse "
-"eller ændre de indhentede indstillinger. Du kan kun komme til manuel "
-"netværksopsætning hvis DHCP-søgningen mislykkes."
+"Som standard vil &d-i; automatisk søge efter netværkskonfiguration via DHCP. "
+"Hvis søgningen lykkes, vil du ikke få mulighed for at gennemse eller ændre "
+"de indhentede indstillinger. Du kan kun komme til manuel netværksopsætning "
+"hvis DHCP-søgningen mislykkes."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3153,36 +3160,36 @@ msgid ""
 "<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
 "network with DHCP and to enter the information manually."
 msgstr ""
-"Hvis du har en DHCP-server på dit lokale netværk, men ønsker at undgå "
-"den fordi den f.eks. giver forkerte svar, så kan du bruge parameteren "
+"Hvis du har en DHCP-server på dit lokale netværk, men ønsker at undgå den "
+"fordi den f.eks. giver forkerte svar, så kan du bruge parameteren "
 "<userinput>netcfg/disable_dhcp=true</userinput> til at forhindre "
 "konfiguration af netværket med DHCP og indtaste informationen manuelt."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
 "that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
-"Sæt til <userinput>false</userinput> for at forhindre opstart af "
-"PCMCIA-tjenester, hvis dette medfører problemer. Nogle bærbare "
-"er kendt for denne opførsel."
+"Sæt til <userinput>false</userinput> for at forhindre opstart af PCMCIA-"
+"tjenester, hvis dette medfører problemer. Nogle bærbare er kendt for denne "
+"opførsel."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3190,36 +3197,36 @@ msgid ""
 "that this support is currently experimental. Additional information can be "
 "found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
-"Sæt til <userinput>true</userinput> for aktivere understøttelse for "
-"Serial ATA RAID-diske (også kaldt ATA RAID, BIOS RAID eller falsk RAID) "
-"i installationsprogrammet. Bemærk at denne understøttelse kun er eksperimentel. "
-"Yderligere information kan findes på <ulink url=\"&url-d-i-wiki;\">"
-"&debian;-installationsprogrammets wiki</ulink>."
+"Sæt til <userinput>true</userinput> for aktivere understøttelse for Serial "
+"ATA RAID-diske (også kaldt ATA RAID, BIOS RAID eller falsk RAID) i "
+"installationsprogrammet. Bemærk at denne understøttelse kun er "
+"eksperimentel. Yderligere information kan findes på <ulink url=\"&url-d-i-"
+"wiki;\">&debian;-installationsprogrammets wiki</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (adresse)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
 "automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
-"Angiv adressen for en prækonfigurationsfil for at hente og bruge "
-"den for automatisering af installationen. Se <xref linkend=\"automatic-install\"/>."
+"Angiv adressen for en prækonfigurationsfil for at hente og bruge den for "
+"automatisering af installationen. Se <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (fil)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3229,13 +3236,13 @@ msgstr ""
 "automatisering af installationen. Se <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3244,39 +3251,38 @@ msgid ""
 "boot parameters, but for those a special syntax can be used. See <xref "
 "linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
-"Sæt til <userinput>true</userinput> for at vise spørgsmål selv hvis de "
-"er blevet forudfyldt. Kan være nyttig for test eller fejlsøgning af en "
-"forhåndskonfigureret fil. Bemærk at dette ikke vil have effekt på "
-"parametre som sendes som opstartsparametre, men for disse kan en "
-"speciel syntaks bruges. Se  <xref linkend=\"preseed-seenflag\"/> "
-"for detaljer."
+"Sæt til <userinput>true</userinput> for at vise spørgsmål selv hvis de er "
+"blevet forudfyldt. Kan være nyttig for test eller fejlsøgning af en "
+"forhåndskonfigureret fil. Bemærk at dette ikke vil have effekt på parametre "
+"som sendes som opstartsparametre, men for disse kan en speciel syntaks "
+"bruges. Se  <xref linkend=\"preseed-seenflag\"/> for detaljer."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
 "after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
 "details about using this to automate installs."
 msgstr ""
-"Forsink spørgsmål som der normalt stilles før forudfyldning er muligt "
-"indtil efter at netværket er konfigureret. Se <xref linkend=\"preseed-auto\"/> "
-"for detaljer om brugen af denne til automatisering af installationer."
+"Forsink spørgsmål som der normalt stilles før forudfyldning er muligt indtil "
+"efter at netværket er konfigureret. Se <xref linkend=\"preseed-auto\"/> for "
+"detaljer om brugen af denne til automatisering af installationer."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3284,17 +3290,18 @@ msgid ""
 "filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 "Under installationer fra seriel eller håndteringskonsol er de regulære "
-"virtuelle konsoller (VT1 til VT6) normalt deaktiveret i <filename>/etc/inittab</"
-"filename>. Sæt til <userinput>true</userinput> for at forhindre dette."
+"virtuelle konsoller (VT1 til VT6) normalt deaktiveret i <filename>/etc/"
+"inittab</filename>. Sæt til <userinput>true</userinput> for at forhindre "
+"dette."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3308,12 +3315,12 @@ msgstr ""
 "ud, som blev brugt under installationen. Dette kan være unødvendigt, hvis "
 "systemet ikke automatisk starter op fra cd'en. I nogle tilfælde kan det "
 "endda være uønsket, for eksempel hvis det optiske drev ikke kan genindsætte "
-"mediet selv og hvis brugeren ikke er der til at gøre det manuelt. Mange "
-"slot-indlæsende og tynde drev samt drev i caddy-stil kan ikke genindlæse "
-"mediet automatisk."
+"mediet selv og hvis brugeren ikke er der til at gøre det manuelt. Mange slot-"
+"indlæsende og tynde drev samt drev i caddy-stil kan ikke genindlæse mediet "
+"automatisk."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3321,17 +3328,17 @@ msgid ""
 "boot from the optical drive after the initial installation."
 msgstr ""
 "Sæt til <userinput>false</userinput> for at deaktivere automatisk skub ud, "
-"og vær opmærksom på at du skal sikre at systemet ikke automtatisk starter "
-"op fra det optiske drev efter den oprindelige installation."
+"og vær opmærksom på at du skal sikre at systemet ikke automtatisk starter op "
+"fra det optiske drev efter den oprindelige installation."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (anbefalinger)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3339,14 +3346,14 @@ msgid ""
 "<quote>Recommends</quote>, both during the installation and for the "
 "installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
-"Ved at angive denne indstilling til <userinput>false</userinput>, "
-"vil pakkehåndteringssystemet blive konfigureret til ikke automatisk "
-"at installere <quote>Recommends (anbefalinger)</quote>, både under "
-"installationen og for det installerede system. Se også "
-"<xref linkend=\"di-install-base\"/>."
+"Ved at angive denne indstilling til <userinput>false</userinput>, vil "
+"pakkehåndteringssystemet blive konfigureret til ikke automatisk at "
+"installere <quote>Recommends (anbefalinger)</quote>, både under "
+"installationen og for det installerede system. Se også <xref linkend=\"di-"
+"install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3355,20 +3362,20 @@ msgid ""
 "full functionality you want. This option should therefore only be used by "
 "very experienced users."
 msgstr ""
-"Bemærk at denne indstilling giver et mindre omfattende system, men kan "
-"også resultere i at funktioner mangler, som du ellers normalt ville "
-"forvente var tilgængelige. Du skal måske installere nogle af de anbefalede "
-"pakker for at få den fulde funktionalitet. Denne indstilling bør derfor "
-"kun bruges af meget erfarne brugere."
+"Bemærk at denne indstilling giver et mindre omfattende system, men kan også "
+"resultere i at funktioner mangler, som du ellers normalt ville forvente var "
+"tilgængelige. Du skal måske installere nogle af de anbefalede pakker for at "
+"få den fulde funktionalitet. Denne indstilling bør derfor kun bruges af "
+"meget erfarne brugere."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3376,19 +3383,19 @@ msgid ""
 "authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
 "emphasis>"
 msgstr ""
-"Som standard kræver installationsprogrammet at arkiver godkendes med en kendt "
-"gpg-nøgle. Angiv som <userinput>true (sand)</userinput> for at deaktivere den "
-"godkendelse. <emphasis role=\"bold\">Advarsel: usikker, kan ikke anbefales.</"
-"emphasis>"
+"Som standard kræver installationsprogrammet at arkiver godkendes med en "
+"kendt gpg-nøgle. Angiv som <userinput>true (sand)</userinput> for at "
+"deaktivere den godkendelse. <emphasis role=\"bold\">Advarsel: usikker, kan "
+"ikke anbefales.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3396,34 +3403,33 @@ msgid ""
 "be loaded completely. The value is in kB."
 msgstr ""
 "Denne parameter bør allerede være angivet til en korrekt værdi hvor krævet; "
-"angiv den kun hvis du ser fejl under opstarten som indikerer at ramdisk "
-"ikke kunne indlæses fuldt ud. Værdien er i kB."
+"angiv den kun hvis du ser fejl under opstarten som indikerer at ramdisk ikke "
+"kunne indlæses fuldt ud. Værdien er i kB."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
 "performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
-"Angiv til <userinput>true (sand)</userinput> for at gå i "
-"redningstilstand fremfor at udføre en normal installation. Se "
-"<xref linkend=\"rescue\"/>."
+"Angiv til <userinput>true (sand)</userinput> for at gå i redningstilstand "
+"fremfor at udføre en normal installation. Se <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Brug af opstartsparametre til at besvare spørgsmål"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3432,31 +3438,31 @@ msgid ""
 "\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 "Med nogle undtagelser, kan en værdi angives ved opstartsprompten for "
-"spørgsmål stillet under installationen, dog er dette kun virkelig nyttigt "
-"i specifikke tilfælde. Generelle instruktioner om hvordan dette udføres "
-"kan findes i <xref linkend=\"preseed-bootparms\"/>. Nogle specifikke "
-"eksempler vises nedenfor."
+"spørgsmål stillet under installationen, dog er dette kun virkelig nyttigt i "
+"specifikke tilfælde. Generelle instruktioner om hvordan dette udføres kan "
+"findes i <xref linkend=\"preseed-bootparms\"/>. Nogle specifikke eksempler "
+"vises nedenfor."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (sprog)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (land)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (sted)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3466,7 +3472,7 @@ msgstr ""
 "installationen og det installerede system."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3480,13 +3486,12 @@ msgstr ""
 "Den første og nemmeste måde er kun at sende parameteren <literal>locale</"
 "literal>. Sprog og land vil så blive udledt fra dens værdi. Du kan for "
 "eksempel bruge <userinput>locale=de_CH</userinput> til at vælge tysk som "
-"sprog og Schweitz som land (<literal>de_CH.UTF-8</literal> vil blive "
-"angivet som standardsted for det installerede system). Begrænsningen er "
-"at ikke alle mulige kombinationer af sprog, land og sted kan opnås på "
-"denne måde."
+"sprog og Schweitz som land (<literal>de_CH.UTF-8</literal> vil blive angivet "
+"som standardsted for det installerede system). Begrænsningen er at ikke alle "
+"mulige kombinationer af sprog, land og sted kan opnås på denne måde."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3502,13 +3507,13 @@ msgstr ""
 "locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (moduler)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3524,7 +3529,7 @@ msgstr ""
 "<classname>ppp-udeb</classname> (se <xref linkend=\"pppoe\"/>)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3534,13 +3539,13 @@ msgstr ""
 "DHCP og i stedet for fremtvinger statisk netværkskonfiguration."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protokol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3550,39 +3555,39 @@ msgid ""
 "instead. Note that you cannot select an ftp mirror from a list, you have to "
 "enter the hostname manually."
 msgstr ""
-"Som standard vil installationsprogrammet bruge http-protokollen til "
-"at hente filer fra &debian;-spejle og ændring af dette til ftp er ikke "
-"muligt under installationer med normal prioritet. Ved at angive denne "
-"parameter til <userinput>ftp</userinput>, så kan du tvinge installationsprogrammet "
-"til at bruge den protokol i stedet for. Bemærk at du ikke kan vælge et "
-"ftp-spejl fra en liste, du skal indtaste værtsnavnet manuelt."
+"Som standard vil installationsprogrammet bruge http-protokollen til at hente "
+"filer fra &debian;-spejle og ændring af dette til ftp er ikke muligt under "
+"installationer med normal prioritet. Ved at angive denne parameter til "
+"<userinput>ftp</userinput>, så kan du tvinge installationsprogrammet til at "
+"bruge den protokol i stedet for. Bemærk at du ikke kan vælge et ftp-spejl "
+"fra en liste, du skal indtaste værtsnavnet manuelt."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (opgaver)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
 "list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
 "\"pkgsel\"/> for additional information."
 msgstr ""
-"Kan bruges til at vælge opgaver, som ikke er tilgængelige fra den interaktive "
-"opgaveliste, såsom opgaven <literal>kde-desktop</literal>. Se <xref linkend="
-"\"pkgsel\"/> for yderligere information."
+"Kan bruges til at vælge opgaver, som ikke er tilgængelige fra den "
+"interaktive opgaveliste, såsom opgaven <literal>kde-desktop</literal>. Se "
+"<xref linkend=\"pkgsel\"/> for yderligere information."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Sende parametre til kernemoduler"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3600,13 +3605,13 @@ msgstr ""
 "parametre til moduler, som du normalt ville gøre, hvis drivere er kompileret "
 "som moduler og fordi kernemoduler indlæses en smule anderledes under "
 "installation end under opstart fra et installeret system. I stedet skal du "
-"bruge en speciel syntaks der genkendes af installationsprogrammet, som så vil "
-"sikre at parametrene er gemt i de korrekte konfigurationsfiler og vil "
+"bruge en speciel syntaks der genkendes af installationsprogrammet, som så "
+"vil sikre at parametrene er gemt i de korrekte konfigurationsfiler og vil "
 "derfor blive brugt når modulerne rent faktisk indlæses. Parametrene vil også "
 "automatisk blive videregivet til konfigurationen for det installerede system."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3614,13 +3619,13 @@ msgid ""
 "system and set good defaults that way. However, in some situations it may "
 "still be needed to set parameters manually."
 msgstr ""
-"Bemærk at det er ret sjældent at parametere skal sendes til moduler. "
-"I de fleste tilfælde vil kernen kunne finde frem til udstyret i et system og "
+"Bemærk at det er ret sjældent at parametere skal sendes til moduler. I de "
+"fleste tilfælde vil kernen kunne finde frem til udstyret i et system og "
 "angive gode standarder via denne metode. I nogle situationer kan det dog "
 "være nødvendigt at angive parametre manuelt."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3632,29 +3637,28 @@ msgid ""
 "network interface card to use the BNC (coax) connector and IRQ 10, you would "
 "pass:"
 msgstr ""
-"Syntaksen for brug af modulparametre er: "
-"<informalexample><screen>\n"
+"Syntaksen for brug af modulparametre er: <informalexample><screen>\n"
 "<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
 "replaceable>=<replaceable>value</replaceable>\n"
 "</screen></informalexample> Hvis du skal sende flere parametre til den samme "
-"eller forskellige moduler, så gentag bare dette. For eksmepel, for at angive at "
-"et gammelt 3Com-netværksgrænsefladekort skal bruge BNC-forbindelsen (coax) og "
-"IRQ 10, skal du skrive:"
+"eller forskellige moduler, så gentag bare dette. For eksmepel, for at angive "
+"at et gammelt 3Com-netværksgrænsefladekort skal bruge BNC-forbindelsen "
+"(coax) og IRQ 10, skal du skrive:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Sortliste kernemoduler"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3667,12 +3671,12 @@ msgstr ""
 "Undertiden kan det være nødvendigt at sortliste et modul for at forhindre "
 "det i at blive indlæst automatisk af kernen og udev. En årsag kunne være at "
 "et specifik modul medfører problemer med dit udstyr. Kernen viser også "
-"undertiden to forskellige drivere for den samme enhed. Dette kan medføre "
-"at enheden ikke fungerer korrekt, hvis driverne er i konflikt eller hvis "
-"den forkerte driver indlæses først."
+"undertiden to forskellige drivere for den samme enhed. Dette kan medføre at "
+"enheden ikke fungerer korrekt, hvis driverne er i konflikt eller hvis den "
+"forkerte driver indlæses først."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3688,7 +3692,7 @@ msgstr ""
 "system."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3698,23 +3702,23 @@ msgid ""
 msgstr ""
 "Bemærk at et modul stadig kan blive indlæst af selve installationssystemet. "
 "Du kan forhindre dette i at ske ved at køre installationen i eksperttilstand "
-"og fravælge modulet fra listen over moduler vist under detektionsfaserne "
-"for udstyret."
+"og fravælge modulet fra listen over moduler vist under detektionsfaserne for "
+"udstyret."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Fejlsøgning af installationsprocessen"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Cd-rom-troværdighed"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3723,40 +3727,40 @@ msgid ""
 "errors while reading from it during the installation."
 msgstr ""
 "Undertiden, specielt med ældre cd-rom-drev, vil installationsprogrammet "
-"fejle i at starte op fra en cd-rom. Installationsprogrammet kan også "
-"&mdash; selv efter opstart fra cd-rom &mdash; mislykkes i at genkende "
-"cd-rommen eller returnere fejl under læsning fra den under installationen."
+"fejle i at starte op fra en cd-rom. Installationsprogrammet kan også &mdash; "
+"selv efter opstart fra cd-rom &mdash; mislykkes i at genkende cd-rommen "
+"eller returnere fejl under læsning fra den under installationen."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
 "list some common issues and provide general suggestions on how to deal with "
 "them. The rest is up to you."
 msgstr ""
-"Der er mangle forskellige mulige årsager for disse problemer. Vi kan "
-"kun vise nogle gængse problemstillinger og tilbyde generelle forslag til "
-"hvordan du håndterer dem. Resten er op til dig."
+"Der er mangle forskellige mulige årsager for disse problemer. Vi kan kun "
+"vise nogle gængse problemstillinger og tilbyde generelle forslag til hvordan "
+"du håndterer dem. Resten er op til dig."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Der er to meget simple metoder, du bør prøve først."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
 "it is not dirty."
 msgstr ""
-"Hvis cd-rommen ikke starter op, så kontroller at disken er korrekt indsat "
-"og at den ikke er ridset eller beskidt."
+"Hvis cd-rommen ikke starter op, så kontroller at disken er korrekt indsat og "
+"at den ikke er ridset eller beskidt."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid ""
 "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3765,24 +3769,24 @@ msgid ""
 "drives are known to be resolved in this way."
 msgstr ""
 "Hvis installationsprogrammet ikke kan genkende en cd-rom, så prøv at køre "
-"indstillingen <menuchoice> <guimenuitem>Detekter og monter cd-rom</guimenuitem> "
-"</menuchoice> endnu en gang. Nogle DMA-relaterede problemstillinger med meget "
-"gamle cd-rom-drev kan løses på denne måde."
+"indstillingen <menuchoice> <guimenuitem>Detekter og monter cd-rom</"
+"guimenuitem> </menuchoice> endnu en gang. Nogle DMA-relaterede "
+"problemstillinger med meget gamle cd-rom-drev kan løses på denne måde."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
 "Most, but not all, suggestions discussed there are valid for both CD-ROM and "
 "DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
-"Hvis dette ikke virker, så prøv forslagene i underafsnittene nedenfor. "
-"De fleste - men ikke alle - forslag diskuteret her er gyldige for både cd-rom "
+"Hvis dette ikke virker, så prøv forslagene i underafsnittene nedenfor. De "
+"fleste - men ikke alle - forslag diskuteret her er gyldige for både cd-rom "
 "og dvd, men vi bruger alene udtrykket cd-rom."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3792,13 +3796,13 @@ msgstr ""
 "andre tilgængelige installationsmetoder."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Gængse problemstillinger"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3808,7 +3812,7 @@ msgstr ""
 "med høje hastigheder via et moderne cd-rom-drev."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid ""
 "Some very old CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3818,30 +3822,31 @@ msgstr ""
 "access</quote> (DMA) er aktiveret for dem."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Hvordan kan der undersøges og måske løses problemstillinger"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
-msgstr "Hvis cd-rom'en ikke starter op, så prøv anbefalingerne på listen nedenfor."
+msgstr ""
+"Hvis cd-rom'en ikke starter op, så prøv anbefalingerne på listen nedenfor."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid ""
 "Check that your BIOS actually supports booting from CD-ROM (only an issue "
 "for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
-"Kontroller at din BIOS rent faktisk understøtter opstart fra cd-rom (kun "
-"en problemstilling for meget gamle systemer) og at cd-opstart er aktiveret "
-"i BIOS'en."
+"Kontroller at din BIOS rent faktisk understøtter opstart fra cd-rom (kun en "
+"problemstilling for meget gamle systemer) og at cd-opstart er aktiveret i "
+"BIOS'en."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3856,8 +3861,8 @@ msgid ""
 "image to read the correct number of bytes from the CD-ROM."
 msgstr ""
 "Hvis du hentede et iso-aftryk, så kontroller at md5summen for det aftryk "
-"matcher det viste aftryk i filen <filename>MD5SUMS</filename>, som "
-"bør befinde sig samme sted, som du hentede aftrykket fra. "
+"matcher det viste aftryk i filen <filename>MD5SUMS</filename>, som bør "
+"befinde sig samme sted, som du hentede aftrykket fra. "
 "<informalexample><screen>\n"
 "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
 "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
@@ -3867,7 +3872,7 @@ msgstr ""
 "størrelsen for aftrykket til at læse det korrekte antal byte fra cd-rommen."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3888,7 +3893,7 @@ msgstr ""
 "134486016 byte (134 MB) kopieret, 97,474 sekunder, 1,4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3904,13 +3909,12 @@ msgstr ""
 "ikke detekteres, så kan det bare at prøve igen nogle gange løse problemet. "
 "Hvis du har mere end et cd-rom-drev, så prøv at indsætte disken i det andet "
 "drev. Hvis det ikke virker eller hvis diske genkendes men har fejl under "
-"læsning, så prøv forslagene nedenfor. Lidt grundlæggende viden om "
-"&arch-kernel; er krævet for dette. For at køre disse kommandoer, så skal du "
-"først skifte til den anden virtuelle konsol (VT2) og aktivere skallen "
-"der."
+"læsning, så prøv forslagene nedenfor. Lidt grundlæggende viden om &arch-"
+"kernel; er krævet for dette. For at køre disse kommandoer, så skal du først "
+"skifte til den anden virtuelle konsol (VT2) og aktivere skallen der."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3919,11 +3923,11 @@ msgid ""
 msgstr ""
 "Skift til VT4 eller vis indholdet af <filename>/var/log/syslog</filename> "
 "(brug <command>nano</command> som redigeringsprogram) til at kontrollere "
-"efter specifikke fejlbeskeder. Derefter kontrolleres også resultatet "
-"af <command>dmesg</command>."
+"efter specifikke fejlbeskeder. Derefter kontrolleres også resultatet af "
+"<command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3939,22 +3943,22 @@ msgid ""
 "not supported at all. If you know what driver is needed for the controller, "
 "you can try loading it manually using <command>modprobe</command>."
 msgstr ""
-"Kontroller i resultatet fra <command>dmesg</command> om dit cd-rom-drev "
-"blev genkendt. Du bør se noget ala (linjerne skal ikke nødvendigvis "
-"være fortløbende): <informalexample><screen>\n"
+"Kontroller i resultatet fra <command>dmesg</command> om dit cd-rom-drev blev "
+"genkendt. Du bør se noget ala (linjerne skal ikke nødvendigvis være "
+"fortløbende): <informalexample><screen>\n"
 "Probing IDE interface ide1...\n"
 "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
 "ide1 at 0x170-0x177,0x376 on irq 15\n"
 "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
 "Uniform CD-ROM driver Revision: 3.20\n"
-"</screen></informalexample> Hvis du ikke ser noget der ligner eksemplet, "
-"er der en risiko for, at controlleren som dit cd-rom-drev er forbundet "
-"med ikke blev genkendt eller slet ikke er understøttet. Hvis du ved hvilken "
-"driver, der er krævet for controlleren, så kan du forsøge at indlæse den "
-"manuelt med <command>modprobe</command>."
+"</screen></informalexample> Hvis du ikke ser noget der ligner eksemplet, er "
+"der en risiko for, at controlleren som dit cd-rom-drev er forbundet med ikke "
+"blev genkendt eller slet ikke er understøttet. Hvis du ved hvilken driver, "
+"der er krævet for controlleren, så kan du forsøge at indlæse den manuelt med "
+"<command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3966,7 +3970,7 @@ msgstr ""
 "filename>. Der skal også være et <filename>/dev/cdrom</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -3983,7 +3987,7 @@ msgstr ""
 "den kommando."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4002,14 +4006,14 @@ msgstr ""
 "$ grep using_dma settings\n"
 "using_dma      1       0       1       rw\n"
 "</screen></informalexample> Et <quote>1</quote> i den første kolonne efter "
-"<literal>using_dma</literal> betyder at den er aktiveret. Hvis den er, "
-"så prøv at deaktivere den: <informalexample><screen>\n"
+"<literal>using_dma</literal> betyder at den er aktiveret. Hvis den er, så "
+"prøv at deaktivere den: <informalexample><screen>\n"
 "$ echo -n \"using_dma:0\" >settings\n"
 "</screen></informalexample> Sikr dig at du er i mappen for enheden som "
 "svarer til dit cd-rom-drev."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4018,28 +4022,28 @@ msgid ""
 "be read reliably."
 msgstr ""
 "Hvis der er problemer under installationen, så prøv at kontrollere "
-"integriteten for cd-rommen med indstillingen nær bunden af installationsprogrammets "
-"hovedmenu. Denne indstilling kan også bruges som en generel test af, "
-"om cd-rommen kan læses troværdigt."
+"integriteten for cd-rommen med indstillingen nær bunden af "
+"installationsprogrammets hovedmenu. Denne indstilling kan også bruges som en "
+"generel test af, om cd-rommen kan læses troværdigt."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Troværdighed for disketter"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
 "to be floppy disk reliability."
 msgstr ""
-"Det største problem for folk der bruger disketter til at installere "
-"&debian; ser ud til at være disketternes troværdighed."
+"Det største problem for folk der bruger disketter til at installere &debian; "
+"ser ud til at være disketternes troværdighed."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4051,13 +4055,13 @@ msgid ""
 msgstr ""
 "Opstartsdisketten er disketten med de største problemer, da den læses af "
 "udstyret direkte, før Linux starter op. Ofte læser udstyret ikke lige så "
-"troværdigt som diskettedriveren for Linux, og kan bare stoppe uden at "
-"vise en fejlbesked, hvis den læser ukorrekte data. Der kan også være "
-"fejl i driverdisketterne, hvor de fleste fejl viser sig som en stor mængde "
-"af I/O-fejl."
+"troværdigt som diskettedriveren for Linux, og kan bare stoppe uden at vise "
+"en fejlbesked, hvis den læser ukorrekte data. Der kan også være fejl i "
+"driverdisketterne, hvor de fleste fejl viser sig som en stor mængde af I/O-"
+"fejl."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4067,15 +4071,15 @@ msgid ""
 "reformatted and written with no errors. It is sometimes useful to try "
 "writing the floppy on a different system."
 msgstr ""
-"Hvis installationen stopper med en specifik diskette, er den første "
-"ting du skal gøre at skrive aftrykket til en <emphasis>anden</emphasis> "
-"diskette og se om dette løser problemet. En formatering af den gamle "
-"diskette er måske ikke nok, også selv om det ser ud til at disketten "
-"blev formateret og skrevet uden fejl. Det er undertiden nyttigt at "
-"prøve at skrive disketten på et andet system."
+"Hvis installationen stopper med en specifik diskette, er den første ting du "
+"skal gøre at skrive aftrykket til en <emphasis>anden</emphasis> diskette og "
+"se om dette løser problemet. En formatering af den gamle diskette er måske "
+"ikke nok, også selv om det ser ud til at disketten blev formateret og "
+"skrevet uden fejl. Det er undertiden nyttigt at prøve at skrive disketten på "
+"et andet system."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4083,11 +4087,11 @@ msgid ""
 "third floppy."
 msgstr ""
 "En bruger indrapporterede at han skulle skrive aftrykket til disketten "
-"<emphasis>tre</emphasis> gange før der var en der virkede, og så var "
-"alt okay med den tredje diskette."
+"<emphasis>tre</emphasis> gange før der var en der virkede, og så var alt "
+"okay med den tredje diskette."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4099,25 +4103,25 @@ msgstr ""
 "korrekt ved at verificere deres md5summer."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
 "floppy in the floppy drive can lead to a successful boot. This is all due to "
 "buggy hardware or firmware floppy drivers."
 msgstr ""
-"Andre brugere har indrapporteret at simple genstarter over et par gange "
-"med den samme diskette i drevet kan føre til en succesfuld opstart. Dette "
+"Andre brugere har indrapporteret at simple genstarter over et par gange med "
+"den samme diskette i drevet kan føre til en succesfuld opstart. Dette "
 "skyldes fejlramt udstyr eller firmware i diskettedrevene."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Opstartskonfiguration"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4125,13 +4129,13 @@ msgid ""
 "properly, the first thing to check is the boot parameters, as discussed in "
 "<xref linkend=\"boot-parms\"/>."
 msgstr ""
-"Hvis du har problemer og kernen hænger under opstartsprocessen, ikke genkender "
-"perifære enheder du rent faktisk har, eller driverne ikke bliver genkendt "
-"korrekt, så er den første ting du skal gøre er at kontrollere opstartsparametrene, "
-"som omtalt i <xref linkend=\"boot-parms\"/>."
+"Hvis du har problemer og kernen hænger under opstartsprocessen, ikke "
+"genkender perifære enheder du rent faktisk har, eller driverne ikke bliver "
+"genkendt korrekt, så er den første ting du skal gøre er at kontrollere "
+"opstartsparametrene, som omtalt i <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4139,11 +4143,11 @@ msgid ""
 ">)."
 msgstr ""
 "I nogle tilfælde kan fejlsituationer opstå på grund af manglende firmware "
-"for udstyr (se <xref linkend=\"hardware-firmware\"/> og "
-"<xref linkend=\"loading-firmware\"/>)."
+"for udstyr (se <xref linkend=\"hardware-firmware\"/> og <xref linkend="
+"\"loading-firmware\"/>)."
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4154,45 +4158,45 @@ msgid ""
 "a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 "Hvis talesyntese for programmer ikke virker, så er der sandsynligvis et "
-"problem med dit lydkort, normalt på grund af at enten drivere for den "
-"ikke er inkluderet i installationsprogrammet, eller fordi den har et "
-"unormalt navn for mikserniveauet som er sat til slukket som standard. "
-"Du skal derfor indsende en fejlraport som inkluderer resultatet fra "
-"de følgende kommandoer, kørt på den samme maskine fra et Linuxsystem "
-"som vides at have lyd virkende (dvs. en live-cd)."
+"problem med dit lydkort, normalt på grund af at enten drivere for den ikke "
+"er inkluderet i installationsprogrammet, eller fordi den har et unormalt "
+"navn for mikserniveauet som er sat til slukket som standard. Du skal derfor "
+"indsende en fejlraport som inkluderer resultatet fra de følgende kommandoer, "
+"kørt på den samme maskine fra et Linuxsystem som vides at have lyd virkende "
+"(dvs. en live-cd)."
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Gængse &arch-title;-installationsproblemer"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4202,7 +4206,7 @@ msgstr ""
 "at sende bestemte opstartsparametre til installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4213,23 +4217,23 @@ msgid ""
 "languages will be available during the installation due to limited console "
 "features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
-"Hvis din skærm begynder at vise et underligt billede når kernen starter "
-"op, f.eks. ren hvid, ren sort eller usammenhængende farvede billedpunkter, "
-"så kan dit system indeholde et problematisk videokort, som ikke skifter "
-"til tilstanden for framebuffer korrekt. Så kan du bruge opstartsparameteren "
-"<userinput>fb=false</userinput> til at deaktivere framebuffer-konsollen. "
-"Kun et reduceret sæt af sprog vil være tilgængelige under installationen "
-"på grund af begrænsede konsolfunktioner. Se <xref linkend=\"boot-parms\"/> "
-"for detaljer."
+"Hvis din skærm begynder at vise et underligt billede når kernen starter op, "
+"f.eks. ren hvid, ren sort eller usammenhængende farvede billedpunkter, så "
+"kan dit system indeholde et problematisk videokort, som ikke skifter til "
+"tilstanden for framebuffer korrekt. Så kan du bruge opstartsparameteren "
+"<userinput>fb=false</userinput> til at deaktivere framebuffer-konsollen. Kun "
+"et reduceret sæt af sprog vil være tilgængelige under installationen på "
+"grund af begrænsede konsolfunktioner. Se <xref linkend=\"boot-parms\"/> for "
+"detaljer."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Systemfrysning under PCMCIA-konfigurationsfasen"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
 msgid ""
 "Some very old laptop models produced by Dell are known to crash when PCMCIA "
@@ -4244,12 +4248,13 @@ msgstr ""
 "når PCMCIA-enhedsdetektering forsøger at tilgå udvalgte udstyrsadresser. "
 "Andre bærbare kan have lignende problemer. Hvis du oplever et sådant problem "
 "har du ikke brug for PCMCIA-understøttelse under installationen, så kan du "
-"deaktivere PCMCIA via opstartsparameteren <userinput>hw-detect/start_pcmcia=false"
-"</userinput>. Du kan så konfigurere PCMCIA efter at installationen er "
-"færdig og ekskludere ressourceintervallet, der medfører problemerne."
+"deaktivere PCMCIA via opstartsparameteren <userinput>hw-detect/"
+"start_pcmcia=false</userinput>. Du kan så konfigurere PCMCIA efter at "
+"installationen er færdig og ekskludere ressourceintervallet, der medfører "
+"problemerne."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4266,24 +4271,23 @@ msgstr ""
 "kræver. For eksempel, hvis du har en af Dells bærbare nævnt ovenfor, skal du "
 "indtaste <userinput>exclude port 0x800-0x8ff</userinput>. Der er også en "
 "liste over nogle gængse intervalindstillinger for ressourcer i afsnittet for "
-"<ulink url=\"http://pcmcia-cs."
-"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">Systemressourceindstillinger "
-"for PCMCIA - hjælp</ulink>."
+"<ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1."
+"html#ss1.12\">Systemressourceindstillinger for PCMCIA - hjælp</ulink>."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "Der er nogle gængse installationsproblemer som det er værd at nævne."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Fejlramt videoresultat"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4297,20 +4301,19 @@ msgid ""
 "phase using a kernel parameter. For example, to disable an ATI card, you "
 "should boot the installer with <userinput>video=atyfb:off</userinput>."
 msgstr ""
-"Det er ret ofte at &arch-title; har to videokort i en maskine, for "
-"eksempel et ATI-kort og et Sun Creator 3D. I nogle tilfælde, kan dette "
-"resultere i at videoresultatet bliver fejlramt efter at systemet starter op. "
-"i typiske tilfælde vil skærmen kun vise: <informalexample><screen>\n"
+"Det er ret ofte at &arch-title; har to videokort i en maskine, for eksempel "
+"et ATI-kort og et Sun Creator 3D. I nogle tilfælde, kan dette resultere i at "
+"videoresultatet bliver fejlramt efter at systemet starter op. i typiske "
+"tilfælde vil skærmen kun vise: <informalexample><screen>\n"
 "Remapping the kernel... done\n"
 "Booting Linux...\n"
-"</screen></informalexample> For at omgå dete kan du enten fjerne et "
-"af videokortene eller deaktivere et af dem under OpenProm-opstartsfasen "
-"med en kerneparameter. For eksempel, for at deaktivere et ATI-kort, "
-"skal du starter installationsprogrammet op med <userinput>video=atyfb:off"
-"</userinput>."
+"</screen></informalexample> For at omgå dete kan du enten fjerne et af "
+"videokortene eller deaktivere et af dem under OpenProm-opstartsfasen med en "
+"kerneparameter. For eksempel, for at deaktivere et ATI-kort, skal du starter "
+"installationsprogrammet op med <userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4318,19 +4321,19 @@ msgid ""
 "rebooting) and, if you installed X11, modify the video driver in <filename>/"
 "etc/X11/xorg.conf</filename>."
 msgstr ""
-"Bemærk at du måske også manuelt skal tilføje denne paramter til "
-"silo-konfigurationen (rediger <filename>/target/etc/silo.conf</filename> "
-"før genstart) og, hvis du installerede X11, så ændr videodriveren i <filename>/"
+"Bemærk at du måske også manuelt skal tilføje denne paramter til silo-"
+"konfigurationen (rediger <filename>/target/etc/silo.conf</filename> før "
+"genstart) og, hvis du installerede X11, så ændr videodriveren i <filename>/"
 "etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Fejl ved opstart eller installation fra cd-rom"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4338,11 +4341,11 @@ msgid ""
 "Most problems have been reported with SunBlade systems."
 msgstr ""
 "Nogle Sparc-systemer er notorisk svære at starte fra cd-rom og selv om de "
-"starter op, kan der være fejl der ikke kan forklare under installationen. "
-"De fleste problemer er blevet indrapporteret med SunBlade-systemer."
+"starter op, kan der være fejl der ikke kan forklare under installationen. De "
+"fleste problemer er blevet indrapporteret med SunBlade-systemer."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4350,13 +4353,13 @@ msgstr ""
 "installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Fortolker kernens opstartsbeskeder"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4394,13 +4397,13 @@ msgstr ""
 "linkend=\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Rapportering af installationsproblemer"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4420,7 +4423,7 @@ msgstr ""
 "du vedhæfte denne information til fejlrapporten."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4432,13 +4435,13 @@ msgstr ""
 "efter at computeren er blevet startet op i det installerede system."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Indsendelse af installationsrapporter"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4452,7 +4455,7 @@ msgstr ""
 "største antal udstyrskonfigurationer."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4464,7 +4467,7 @@ msgstr ""
 "at du bruger en e-post-adresse, som du ikke har problemer med er offentlig."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4484,7 +4487,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/da/gpl.po b/po/da/gpl.po
index 3582cbd8a..5f7616aa6 100644
--- a/po/da/gpl.po
+++ b/po/da/gpl.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,35 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:6
 #, no-c-format
-msgid "[[This note, consisting of two paragraphs, should only be included in your translation if you translate the GPL in this appendix. See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English name of your language. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[This note, consisting of two paragraphs, should only be included in your "
+"translation if you translate the GPL in this appendix. See build/lang-"
+"options/README on how to enable this paragraph and for additional "
+"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH "
+"IN ENGLISH! Only replace {language} with the English name of your language. "
+"Do not change the link to the GPL!]] This is an unofficial translation of "
+"the GNU General Public License into {language}. It was not published by the "
+"Free Software Foundation, and does not legally state the distribution terms "
+"for software that uses the GNU GPL &mdash; only the original <ulink url="
+"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. "
+"However, we hope that this translation will help {language} speakers to "
+"better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:22
 #, no-c-format
-msgid "[[See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of your language before translating. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[See build/lang-options/README on how to enable this paragraph and for "
+"additional information. Its condition is \"gpl-unofficial\".]] [[THIS "
+"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of "
+"your language before translating. Do not change the link to the GPL!]] This "
+"is an unofficial translation of the GNU General Public License into "
+"{language}. It was not published by the Free Software Foundation, and does "
+"not legally state the distribution terms for software that uses the GNU GPL "
+"&mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</"
+"ulink> of the GNU GPL does that. However, we hope that this translation will "
+"help {language} speakers to better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
@@ -41,11 +64,11 @@ msgstr ""
 #: gpl.xml:41
 #, no-c-format
 msgid ""
-      "Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
-      "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
-      "\n"
-      "Everyone is permitted to copy and distribute verbatim copies\n"
-      "of this license document, but changing it is not allowed."
+"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
+"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
+"\n"
+"Everyone is permitted to copy and distribute verbatim copies\n"
+"of this license document, but changing it is not allowed."
 msgstr ""
 
 #. Tag: title
@@ -57,49 +80,87 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:46
 #, no-c-format
-msgid "The licenses for most software are designed to take away your freedom to share and change it. By contrast, the gnu General Public License is intended to guarantee your freedom to share and change free software &mdash; to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the gnu Library General Public License instead.) You can apply it to your programs, too."
+msgid ""
+"The licenses for most software are designed to take away your freedom to "
+"share and change it. By contrast, the gnu General Public License is intended "
+"to guarantee your freedom to share and change free software &mdash; to make "
+"sure the software is free for all its users. This General Public License "
+"applies to most of the Free Software Foundation's software and to any other "
+"program whose authors commit to using it. (Some other Free Software "
+"Foundation software is covered by the gnu Library General Public License "
+"instead.) You can apply it to your programs, too."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:58
 #, no-c-format
-msgid "When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+msgid ""
+"When we speak of free software, we are referring to freedom, not price. Our "
+"General Public Licenses are designed to make sure that you have the freedom "
+"to distribute copies of free software (and charge for this service if you "
+"wish), that you receive source code or can get it if you want it, that you "
+"can change the software or use pieces of it in new free programs; and that "
+"you know you can do these things."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:68
 #, no-c-format
-msgid "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it."
+msgid ""
+"To protect your rights, we need to make restrictions that forbid anyone to "
+"deny you these rights or to ask you to surrender the rights. These "
+"restrictions translate to certain responsibilities for you if you distribute "
+"copies of the software, or if you modify it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:75
 #, no-c-format
-msgid "For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
+msgid ""
+"For example, if you distribute copies of such a program, whether gratis or "
+"for a fee, you must give the recipients all the rights that you have. You "
+"must make sure that they, too, receive or can get the source code. And you "
+"must show them these terms so they know their rights."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:83
 #, no-c-format
-msgid "We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
+msgid ""
+"We protect your rights with two steps: (1) copyright the software, and (2) "
+"offer you this license which gives you legal permission to copy, distribute "
+"and/or modify the software."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:89
 #, no-c-format
-msgid "Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations."
+msgid ""
+"Also, for each author's protection and ours, we want to make certain that "
+"everyone understands that there is no warranty for this free software. If "
+"the software is modified by someone else and passed on, we want its "
+"recipients to know that what they have is not the original, so that any "
+"problems introduced by others will not reflect on the original authors' "
+"reputations."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:98
 #, no-c-format
-msgid "Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."
+msgid ""
+"Finally, any free program is threatened constantly by software patents. We "
+"wish to avoid the danger that redistributors of a free program will "
+"individually obtain patent licenses, in effect making the program "
+"proprietary. To prevent this, we have made it clear that any patent must be "
+"licensed for everyone's free use or not licensed at all."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:107
 #, no-c-format
-msgid "The precise terms and conditions for copying, distribution and modification follow."
+msgid ""
+"The precise terms and conditions for copying, distribution and modification "
+"follow."
 msgstr ""
 
 #. Tag: title
@@ -117,163 +178,327 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:121
 #, no-c-format
-msgid "<emphasis role=\"bold\">0.</emphasis> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \"Program\", below, refers to any such program or work, and a \"work based on the Program\" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \"modification\".) Each licensee is addressed as \"you\"."
+msgid ""
+"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or "
+"other work which contains a notice placed by the copyright holder saying it "
+"may be distributed under the terms of this General Public License. The "
+"\"Program\", below, refers to any such program or work, and a \"work based "
+"on the Program\" means either the Program or any derivative work under "
+"copyright law: that is to say, a work containing the Program or a portion of "
+"it, either verbatim or with modifications and/or translated into another "
+"language. (Hereinafter, translation is included without limitation in the "
+"term \"modification\".) Each licensee is addressed as \"you\"."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:134
 #, no-c-format
-msgid "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
+msgid ""
+"Activities other than copying, distribution and modification are not covered "
+"by this License; they are outside its scope. The act of running the Program "
+"is not restricted, and the output from the Program is covered only if its "
+"contents constitute a work based on the Program (independent of having been "
+"made by running the Program). Whether that is true depends on what the "
+"Program does."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:143
 #, no-c-format
-msgid "<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program."
+msgid ""
+"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim "
+"copies of the Program's source code as you receive it, in any medium, "
+"provided that you conspicuously and appropriately publish on each copy an "
+"appropriate copyright notice and disclaimer of warranty; keep intact all the "
+"notices that refer to this License and to the absence of any warranty; and "
+"give any other recipients of the Program a copy of this License along with "
+"the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:154
 #, no-c-format
-msgid "You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
+msgid ""
+"You may charge a fee for the physical act of transferring a copy, and you "
+"may at your option offer warranty protection in exchange for a fee."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:160
 #, no-c-format
-msgid "<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:"
+msgid ""
+"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of "
+"the Program or any portion of it, thus forming a work based on the Program, "
+"and copy and distribute such modifications or work under the terms of "
+"Section 1 above, provided that you also meet all of these conditions:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:169
 #, no-c-format
-msgid "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."
+msgid ""
+"You must cause the modified files to carry prominent notices stating that "
+"you changed the files and the date of any change."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:175
 #, no-c-format
-msgid "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License."
+msgid ""
+"You must cause any work that you distribute or publish, that in whole or in "
+"part contains or is derived from the Program or any part thereof, to be "
+"licensed as a whole at no charge to all third parties under the terms of "
+"this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:183
 #, no-c-format
-msgid "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
+msgid ""
+"If the modified program normally reads commands interactively when run, you "
+"must cause it, when started running for such interactive use in the most "
+"ordinary way, to print or display an announcement including an appropriate "
+"copyright notice and a notice that there is no warranty (or else, saying "
+"that you provide a warranty) and that users may redistribute the program "
+"under these conditions, and telling the user how to view a copy of this "
+"License. (Exception: if the Program itself is interactive but does not "
+"normally print such an announcement, your work based on the Program is not "
+"required to print an announcement.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:197
 #, no-c-format
-msgid "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
+msgid ""
+"These requirements apply to the modified work as a whole. If identifiable "
+"sections of that work are not derived from the Program, and can be "
+"reasonably considered independent and separate works in themselves, then "
+"this License, and its terms, do not apply to those sections when you "
+"distribute them as separate works. But when you distribute the same sections "
+"as part of a whole which is a work based on the Program, the distribution of "
+"the whole must be on the terms of this License, whose permissions for other "
+"licensees extend to the entire whole, and thus to each and every part "
+"regardless of who wrote it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:210
 #, no-c-format
-msgid "Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program."
+msgid ""
+"Thus, it is not the intent of this section to claim rights or contest your "
+"rights to work written entirely by you; rather, the intent is to exercise "
+"the right to control the distribution of derivative or collective works "
+"based on the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:217
 #, no-c-format
-msgid "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
+msgid ""
+"In addition, mere aggregation of another work not based on the Program with "
+"the Program (or with a work based on the Program) on a volume of a storage "
+"or distribution medium does not bring the other work under the scope of this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:224
 #, no-c-format
-msgid "<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:"
+msgid ""
+"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the "
+"Program (or a work based on it, under Section 2) in object code or "
+"executable form under the terms of Sections 1 and 2 above provided that you "
+"also do one of the following:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:233
 #, no-c-format
-msgid "Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with the complete corresponding machine-readable source code, "
+"which must be distributed under the terms of Sections 1 and 2 above on a "
+"medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:241
 #, no-c-format
-msgid "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with a written offer, valid for at least three years, to give "
+"any third party, for a charge no more than your cost of physically "
+"performing source distribution, a complete machine-readable copy of the "
+"corresponding source code, to be distributed under the terms of Sections 1 "
+"and 2 above on a medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:251
 #, no-c-format
-msgid "Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)"
+msgid ""
+"Accompany it with the information you received as to the offer to distribute "
+"corresponding source code. (This alternative is allowed only for "
+"noncommercial distribution and only if you received the program in object "
+"code or executable form with such an offer, in accord with Subsection b "
+"above.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:260
 #, no-c-format
-msgid "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."
+msgid ""
+"The source code for a work means the preferred form of the work for making "
+"modifications to it. For an executable work, complete source code means all "
+"the source code for all modules it contains, plus any associated interface "
+"definition files, plus the scripts used to control compilation and "
+"installation of the executable. However, as a special exception, the source "
+"code distributed need not include anything that is normally distributed (in "
+"either source or binary form) with the major components (compiler, kernel, "
+"and so on) of the operating system on which the executable runs, unless that "
+"component itself accompanies the executable."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:273
 #, no-c-format
-msgid "If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code."
+msgid ""
+"If distribution of executable or object code is made by offering access to "
+"copy from a designated place, then offering equivalent access to copy the "
+"source code from the same place counts as distribution of the source code, "
+"even though third parties are not compelled to copy the source along with "
+"the object code."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:281
 #, no-c-format
-msgid "<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."
+msgid ""
+"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, "
+"or distribute the Program except as expressly provided under this License. "
+"Any attempt otherwise to copy, modify, sublicense or distribute the Program "
+"is void, and will automatically terminate your rights under this License. "
+"However, parties who have received copies, or rights, from you under this "
+"License will not have their licenses terminated so long as such parties "
+"remain in full compliance."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:292
 #, no-c-format
-msgid "<emphasis role=\"bold\">5.</emphasis> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
+msgid ""
+"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this "
+"License, since you have not signed it. However, nothing else grants you "
+"permission to modify or distribute the Program or its derivative works. "
+"These actions are prohibited by law if you do not accept this License. "
+"Therefore, by modifying or distributing the Program (or any work based on "
+"the Program), you indicate your acceptance of this License to do so, and all "
+"its terms and conditions for copying, distributing or modifying the Program "
+"or works based on it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:304
 #, no-c-format
-msgid "<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."
+msgid ""
+"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program "
+"(or any work based on the Program), the recipient automatically receives a "
+"license from the original licensor to copy, distribute or modify the Program "
+"subject to these terms and conditions. You may not impose any further "
+"restrictions on the recipients' exercise of the rights granted herein. You "
+"are not responsible for enforcing compliance by third parties to this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:315
 #, no-c-format
-msgid "<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
+msgid ""
+"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court "
+"judgment or allegation of patent infringement or for any other reason (not "
+"limited to patent issues), conditions are imposed on you (whether by court "
+"order, agreement or otherwise) that contradict the conditions of this "
+"License, they do not excuse you from the conditions of this License. If you "
+"cannot distribute so as to satisfy simultaneously your obligations under "
+"this License and any other pertinent obligations, then as a consequence you "
+"may not distribute the Program at all. For example, if a patent license "
+"would not permit royalty-free redistribution of the Program by all those who "
+"receive copies directly or indirectly through you, then the only way you "
+"could satisfy both it and this License would be to refrain entirely from "
+"distribution of the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:332
 #, no-c-format
-msgid "If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances."
+msgid ""
+"If any portion of this section is held invalid or unenforceable under any "
+"particular circumstance, the balance of the section is intended to apply and "
+"the section as a whole is intended to apply in other circumstances."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:339
 #, no-c-format
-msgid "It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
+msgid ""
+"It is not the purpose of this section to induce you to infringe any patents "
+"or other property right claims or to contest validity of any such claims; "
+"this section has the sole purpose of protecting the integrity of the free "
+"software distribution system, which is implemented by public license "
+"practices. Many people have made generous contributions to the wide range of "
+"software distributed through that system in reliance on consistent "
+"application of that system; it is up to the author/donor to decide if he or "
+"she is willing to distribute software through any other system and a "
+"licensee cannot impose that choice."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:352
 #, no-c-format
-msgid "This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License."
+msgid ""
+"This section is intended to make thoroughly clear what is believed to be a "
+"consequence of the rest of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:357
 #, no-c-format
-msgid "<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License."
+msgid ""
+"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the "
+"Program is restricted in certain countries either by patents or by "
+"copyrighted interfaces, the original copyright holder who places the Program "
+"under this License may add an explicit geographical distribution limitation "
+"excluding those countries, so that distribution is permitted only in or "
+"among countries not thus excluded. In such case, this License incorporates "
+"the limitation as if written in the body of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:368
 #, no-c-format
-msgid "<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \"any later version\", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
+msgid ""
+"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may "
+"publish revised and/or new versions of the General Public License from time "
+"to time. Such new versions will be similar in spirit to the present version, "
+"but may differ in detail to address new problems or concerns. Each version "
+"is given a distinguishing version number. If the Program specifies a version "
+"number of this License which applies to it and \"any later version\", you "
+"have the option of following the terms and conditions either of that version "
+"or of any later version published by the Free Software Foundation. If the "
+"Program does not specify a version number of this License, you may choose "
+"any version ever published by the Free Software Foundation."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:383
 #, no-c-format
-msgid "<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally."
+msgid ""
+"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of "
+"the Program into other free programs whose distribution conditions are "
+"different, write to the author to ask for permission. For software which is "
+"copyrighted by the Free Software Foundation, write to the Free Software "
+"Foundation; we sometimes make exceptions for this. Our decision will be "
+"guided by the two goals of preserving the free status of all derivatives of "
+"our free software and of promoting the sharing and reuse of software "
+"generally."
 msgstr ""
 
 #. Tag: emphasis
@@ -285,13 +510,31 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:399
 #, no-c-format
-msgid "<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION."
+msgid ""
+"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE "
+"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY "
+"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT "
+"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY "
+"OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE "
+"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. "
+"THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH "
+"YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL "
+"NECESSARY SERVICING, REPAIR OR CORRECTION."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:412
 #, no-c-format
-msgid "<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgid ""
+"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY "
+"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY "
+"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED "
+"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, "
+"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO "
+"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING "
+"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE "
+"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR "
+"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
 msgstr ""
 
 #. Tag: emphasis
@@ -309,87 +552,111 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:434
 #, no-c-format
-msgid "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."
+msgid ""
+"If you develop a new program, and you want it to be of the greatest possible "
+"use to the public, the best way to achieve this is to make it free software "
+"which everyone can redistribute and change under these terms."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:441
 #, no-c-format
-msgid "To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \"copyright\" line and a pointer to where the full notice is found."
+msgid ""
+"To do so, attach the following notices to the program. It is safest to "
+"attach them to the start of each source file to most effectively convey the "
+"exclusion of warranty; and each file should have at least the \"copyright\" "
+"line and a pointer to where the full notice is found."
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:448
 #, no-c-format
 msgid ""
-      "<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable>\n"
-      "Copyright (C) <replaceable>year  name of author</replaceable>\n"
-      "\n"
-      "This program is free software; you can redistribute it and/or\n"
-      "modify it under the terms of the GNU General Public License\n"
-      "as published by the Free Software Foundation; either version 2\n"
-      "of the License, or (at your option) any later version.\n"
-      "\n"
-      "This program is distributed in the hope that it will be useful,\n"
-      "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
-      "MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
-      "GNU General Public License for more details.\n"
-      "\n"
-      "You should have received a copy of the GNU General Public License\n"
-      "along with this program; if not, write to the Free Software\n"
-      "Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA."
+"<replaceable>one line to give the program's name and a brief idea of what it "
+"does.</replaceable>\n"
+"Copyright (C) <replaceable>year  name of author</replaceable>\n"
+"\n"
+"This program is free software; you can redistribute it and/or\n"
+"modify it under the terms of the GNU General Public License\n"
+"as published by the Free Software Foundation; either version 2\n"
+"of the License, or (at your option) any later version.\n"
+"\n"
+"This program is distributed in the hope that it will be useful,\n"
+"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
+"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
+"GNU General Public License for more details.\n"
+"\n"
+"You should have received a copy of the GNU General Public License\n"
+"along with this program; if not, write to the Free Software\n"
+"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, "
+"USA."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:450
 #, no-c-format
-msgid "Also add information on how to contact you by electronic and paper mail."
+msgid ""
+"Also add information on how to contact you by electronic and paper mail."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:455
 #, no-c-format
-msgid "If the program is interactive, make it output a short notice like this when it starts in an interactive mode:"
+msgid ""
+"If the program is interactive, make it output a short notice like this when "
+"it starts in an interactive mode:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:460
 #, no-c-format
 msgid ""
-      "Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable>\n"
-      "Gnomovision comes with absolutely no warranty; for details\n"
-      "type `show w'. This is free software, and you are welcome\n"
-      "to redistribute it under certain conditions; type `show c'\n"
-      "for details."
+"Gnomovision version 69, Copyright (C) <replaceable>year name of author</"
+"replaceable>\n"
+"Gnomovision comes with absolutely no warranty; for details\n"
+"type `show w'. This is free software, and you are welcome\n"
+"to redistribute it under certain conditions; type `show c'\n"
+"for details."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:462
 #, no-c-format
-msgid "The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items &mdash; whatever suits your program."
+msgid ""
+"The hypothetical commands `show w' and `show c' should show the appropriate "
+"parts of the General Public License. Of course, the commands you use may be "
+"called something other than `show w' and `show c'; they could even be mouse-"
+"clicks or menu items &mdash; whatever suits your program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:470
 #, no-c-format
-msgid "You should also get your employer (if you work as a programmer) or your school, if any, to sign a \"copyright disclaimer\" for the program, if necessary. Here is a sample; alter the names:"
+msgid ""
+"You should also get your employer (if you work as a programmer) or your "
+"school, if any, to sign a \"copyright disclaimer\" for the program, if "
+"necessary. Here is a sample; alter the names:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:476
 #, no-c-format
 msgid ""
-      "Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
-      "program `Gnomovision' (which makes passes at compilers) written\n"
-      "by James Hacker.\n"
-      "\n"
-      "<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
-      "Ty Coon, President of Vice"
+"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
+"program `Gnomovision' (which makes passes at compilers) written\n"
+"by James Hacker.\n"
+"\n"
+"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
+"Ty Coon, President of Vice"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:478
 #, no-c-format
-msgid "This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
+msgid ""
+"This General Public License does not permit incorporating your program into "
+"proprietary programs. If your program is a subroutine library, you may "
+"consider it more useful to permit linking proprietary applications with the "
+"library. If this is what you want to do, use the GNU Lesser General Public "
+"License instead of this License."
 msgstr ""
-
diff --git a/po/da/hardware.po b/po/da/hardware.po
index c3e0c1251..96af36f01 100644
--- a/po/da/hardware.po
+++ b/po/da/hardware.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:7
 #, no-c-format
-msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;."
+msgid ""
+"This section contains information about what hardware you need to get "
+"started with &debian;. You will also find links to further information about "
+"hardware supported by GNU and &arch-kernel;."
 msgstr ""
 
 #. Tag: title
@@ -34,13 +38,23 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;."
+msgid ""
+"&debian; does not impose hardware requirements beyond the requirements of "
+"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
+"architecture or platform to which the Linux or kFreeBSD kernel, libc, "
+"<command>gcc</command>, etc. have been ported, and for which a &debian; port "
+"exists, can run &debian;. Please refer to the Ports pages at <ulink url="
+"\"&url-ports;\"></ulink> for more details on &arch-title; architecture "
+"systems which have been tested with &debian-gnu;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:32
 #, no-c-format
-msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found."
+msgid ""
+"Rather than attempting to describe all the different hardware configurations "
+"which are supported for &arch-title;, this section contains general "
+"information and pointers to where additional information can be found."
 msgstr ""
 
 #. Tag: title
@@ -52,7 +66,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid ""
+"&debian; GNU/Linux &release; supports eleven major architectures and several "
+"variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -430,19 +446,38 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:203
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are "
+"looking for information on any of the other &debian;-supported architectures "
+"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-"
+"Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
+msgid ""
+"The &arch-title; architecture only supports Intel Itanium processors and not "
+"the much more common 64-bit processors from the Intel 64 family (including e."
+"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
+"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
+"userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:223
 #, no-c-format
-msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
+msgid ""
+"This is the first official release of &debian-gnu; for the &arch-title; "
+"architecture. We feel that it has proven itself sufficiently to be released. "
+"However, because it has not had the exposure (and hence testing by users) "
+"that some other architectures have had, you may encounter a few bugs. Use "
+"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any "
+"problems; make sure to mention the fact that the bug is on the &arch-title; "
+"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
+"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
@@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
+#: hardware.xml:522 hardware.xml:575
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -466,13 +502,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:273
 #, no-c-format
-msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
+msgid ""
+"Each distinct ARM architecture requires its own kernel. Because of this the "
+"standard &debian; distribution only supports installation on a number of the "
+"most common platforms. The &debian; userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:282
 #, no-c-format
-msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
+msgid ""
+"Most ARM CPUs may be run in either endian mode (big or little). However, the "
+"majority of current system implementation uses little-endian mode. &debian; "
+"currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
@@ -490,7 +533,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:298
 #, no-c-format
-msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
+msgid ""
+"Intel's I/O Processor (IOP) line is found in a number of products related to "
+"data storage and processing. &debian; currently supports the IOP32x "
+"platform, featuring the IOP 80219 and 32x chips commonly found in Network "
+"Attached Storage (NAS) devices. &debian; explicitly supports two such "
+"devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from "
+"IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -502,7 +551,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:312
 #, no-c-format
-msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
+msgid ""
+"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
+"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
+"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
+"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
+"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
+"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
+"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
+"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
@@ -514,7 +571,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:329
 #, no-c-format
-msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
+msgid ""
+"Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, "
+"Ethernet, SATA, USB, and other functionality in one chip. There are many "
+"Network Attached Storage (NAS) devices on the market that are based on an "
+"Orion chip. We currently support the following Orion based devices: <ulink "
+"url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url="
+"\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
+"cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -526,19 +590,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:344
 #, no-c-format
-msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
+msgid ""
+"The Versatile platform is emulated by QEMU and is therefore a nice way to "
+"test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:363
 #, no-c-format
-msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
+msgid ""
+"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-"
+"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit "
+"processors whereas the 2.0 architecture is targeted to the 64-bit "
+"processors. Some systems are able to run either kernel. In both cases, the "
+"userland is 32-bit. There is the possibility of a 64-bit userland in the "
+"future."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:382
 #, no-c-format
-msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
+msgid ""
+"Complete information concerning supported peripherals can be found at <ulink "
+"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. "
+"This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
@@ -550,19 +625,43 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:391
 #, no-c-format
-msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
+msgid ""
+"Nearly all x86-based (IA-32) processors still in use in personal computers "
+"are supported, including all varieties of Intel's \"Pentium\" series. This "
+"also includes 32-bit AMD and VIA (former Cyrix) processors, and processors "
+"like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:398
 #, no-c-format
-msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
+msgid ""
+"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run "
+"on 386 or earlier processors. Despite the architecture name \"i386\", "
+"support for actual 80386 processors (and their clones) was dropped with the "
+"Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to "
+"avoid this, but in the end it was necessary due a unfortunate series of "
+"issues with the compiler and the kernel, starting with an bug in the C++ ABI "
+"provided by GCC. You should still be able to run &debian; GNU/Linux on "
+"actual 80386 processors if you compile your own kernel and compile all "
+"packages from source, but that is beyond the scope of this manual. </para> </"
+"footnote>. (No version of Linux has ever supported the 286 or earlier chips "
+"in the series.) All i486 and later processors are still supported<footnote> "
+"<para> Many &debian; packages will actually run slightly faster on modern "
+"computers as a positive side effect of dropping support for these old chips. "
+"The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) "
+"which the i386, introduced in 1986, did not have. Previously, these could "
+"not be easily used by most &debian; packages; now they can. </para> </"
+"footnote>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+msgid ""
+"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
+"you will probably want to use the installer for the amd64 architecture "
+"instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
@@ -574,31 +673,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:441
 #, no-c-format
-msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
+msgid ""
+"The system bus is the part of the motherboard which allows the CPU to "
+"communicate with peripherals such as storage devices. Your computer must use "
+"the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called "
+"the VL bus). Essentially all personal computers sold in recent years use one "
+"of these."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:465
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, "
+"Indigo 2 and Challenge S. Since these machines are very similar, whenever "
+"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant "
+"as well. </para></listitem> <listitem><para> SGI IP32: this platform is "
+"generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: "
+"this platform is emulated by QEMU and is therefore a nice way to test and "
+"run &debian; on MIPS if you don't have the hardware. </para></listitem> </"
+"itemizedlist> Complete information regarding supported mips/mipsel machines "
+"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</"
+"ulink>. In the following, only the systems supported by the &debian; "
+"installer will be covered. If you are looking for support for other "
+"subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> "
+"debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
+msgid ""
+"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and "
+"R5000 processors are supported by the &debian; installation system on big "
+"endian MIPS. On SGI IP32, currently only systems based on the R5000 are "
+"supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
+msgid ""
+"Some MIPS machines can be operated in both big and little endian mode. For "
+"little endian MIPS, please read the documentation for the mipsel "
+"architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:523
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are "
+"covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway "
+"Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform "
+"is emulated by QEMU and is therefore a nice way to test and run &debian; on "
+"MIPS if you don't have the hardware. </para></listitem> </itemizedlist> "
+"Complete information regarding supported mips/mipsel machines can be found "
+"at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the "
+"following, only the systems supported by the &debian; installer will be "
+"covered. If you are looking for support for other subarchitectures, please "
+"contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; "
+"mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -610,7 +747,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:553
 #, no-c-format
-msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
+msgid ""
+"All MIPS based Cobalt machines are supported with the exception of the Qube "
+"2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
@@ -628,7 +767,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:576
 #, no-c-format
-msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
+msgid ""
+"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
+"PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +781,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:599
 #, no-c-format
-msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
+msgid ""
+"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -652,7 +795,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:607
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid ""
+"Most systems use this kernel flavour, which supports the PowerPC 601, 603, "
+"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and "
+"including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
@@ -670,19 +816,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:622
 #, no-c-format
-msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
+msgid ""
+"The POWER3 processor is used in older IBM 64-bit server systems: known "
+"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, "
+"and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:628
 #, no-c-format
-msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
+msgid ""
+"The POWER4 processor is used in more recent IBM 64-bit server systems: known "
+"models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:633
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid ""
+"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
+"architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
@@ -694,25 +847,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:669
 #, no-c-format
-msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
+msgid ""
+"Apple (and briefly a few other manufacturers &mdash; Power Computing, for "
+"example) made a series of Macintosh computers based on the PowerPC "
+"processor. For purposes of architecture support, they are categorized as "
+"NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:676
 #, no-c-format
-msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
+msgid ""
+"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI "
+"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld "
+"machines. Those pre-iMac PowerPC models from Apple use a four digit naming "
+"scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:684
 #, no-c-format
-msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
+msgid ""
+"The so called NewWorld PowerMacs are any PowerMacs in translucent colored "
+"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, "
+"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. "
+"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</"
+"quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:692
 #, no-c-format
-msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
+msgid ""
+"Specifications for Apple hardware are available at <ulink url=\"http://www."
+"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older "
+"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/"
+"index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
@@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
+#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
+#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
+#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
+#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
+#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
+#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
+#: hardware.xml:825
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -1084,7 +1261,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:933
 #, no-c-format
-msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
+msgid ""
+"NuBus systems are not currently supported by &debian;/powerpc. The "
+"monolithic Linux/PPC kernel architecture does not have support for these "
+"machines; instead, one must use the MkLinux Mach microkernel, which &debian; "
+"does not yet support. These include the following: <itemizedlist> "
+"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> "
+"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> "
+"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> "
+"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </"
+"itemizedlist> A linux kernel for these machines and limited support is "
+"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1096,19 +1283,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:972
 #, no-c-format
-msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
+msgid ""
+"Macintosh computers using the 680x0 series of processors are <emphasis>not</"
+"emphasis> in the PowerPC family but are instead m68k machines. Those models "
+"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> "
+"family, then the Centris series, and culminate in the Quadras and Performas. "
+"These models usually have a Roman numeral or 3-digit model number such as "
+"Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:981
 #, no-c-format
-msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
+msgid ""
+"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, "
+"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, "
+"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra "
+"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the "
+"Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:989
 #, no-c-format
-msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
+msgid ""
+"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs "
+"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, "
+"please see the section above)."
 msgstr ""
 
 #. Tag: title
@@ -1120,7 +1321,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1006
 #, no-c-format
-msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
+msgid ""
+"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
+"Your machine needs to support the z/Architecture, 64-bit support is "
+"mandatory. The userland of the s390 port is still compiled for ESA/390, "
+"though. All zSeries and System z hardware is fully supported. &arch-title; "
+"support software is included from the kernel 3.1 development stream. The "
+"most current information about IBM's Linux support can be found at the "
+"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
+"development_technical.html\"> Linux on <trademark class=\"registered"
+"\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1132,7 +1342,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1024
 #, no-c-format
-msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
+msgid ""
+"PAV and HyperPAV are supported transparently, multipathing is not needed to "
+"take advantage of these storage system features. Be sure to configure the "
+"devices during DASD device selection. The alias devices will not be offered "
+"neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
@@ -1144,7 +1358,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1041
 #, no-c-format
-msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
+msgid ""
+"Sparc-based hardware is divided into a number of different subarchitectures, "
+"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u "
+"or sun4v. The following list describes what machines they include and what "
+"level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
@@ -1156,13 +1374,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1054
 #, no-c-format
-msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
+msgid ""
+"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a "
+"complete list of machines belonging to these subarchitectures, please "
+"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation"
+"\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1061
 #, no-c-format
-msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
+msgid ""
+"The last &debian; release to support sparc32 was Etch, but even then only "
+"for sun4m systems. Support for the other 32-bits subarchitectures had "
+"already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
@@ -1174,7 +1399,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1073
 #, no-c-format
-msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
+msgid ""
+"This subarchitecture includes all 64-bit machines (sparc64) based on the "
+"UltraSparc processor and its clones. Most of the machines are well "
+"supported, even though for some you may experience problems booting from CD "
+"due to firmware or bootloader bugs (this problem may be worked around by "
+"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP "
+"configurations respectively."
 msgstr ""
 
 #. Tag: term
@@ -1186,13 +1417,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1088
 #, no-c-format
-msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
+msgid ""
+"This is the newest addition to the Sparc family, which includes machines "
+"based on the Niagara multi-core CPUs. At the moment such CPUs are only "
+"available in T1000 and T2000 servers by Sun, and are well supported. Use the "
+"sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1099
 #, no-c-format
-msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
+msgid ""
+"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
+"not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
@@ -1204,7 +1441,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1109
 #, no-c-format
-msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
+msgid ""
+"From a technical point of view, laptops are normal PCs, so all information "
+"regarding PC systems applies to laptops as well. Installations on laptops "
+"nowadays usually work out of the box, including things like automatically "
+"suspending the system on closing the lid and laptop specfic hardware buttons "
+"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
+"Nonetheless sometimes the hardware vendors use specialized or proprietary "
+"hardware for some laptop-specific functions which might not be supported. To "
+"see if your particular laptop works well with GNU/Linux, see for example the "
+"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1216,61 +1462,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1127
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. Having multiple "
+"processors in a computer was originally only an issue for high-end server "
+"systems but has become quite common in recent years even for rather low-end "
+"desktop computers and laptops with the introduction of so called "
+"<quote>multi-core</quote> processors. These contain two or more processor "
+"units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1137
 #, no-c-format
-msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
+msgid ""
+"The standard &debian; &release; kernel image has been compiled with SMP "
+"support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1148
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. The standard "
+"&debian; &release; kernel image has been compiled with <firstterm>SMP-"
+"alternatives</firstterm> support. This means that the kernel will detect the "
+"number of processors (or processor cores) and will automatically deactivate "
+"SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1157
 #, no-c-format
-msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Having multiple processors in a computer was originally only an issue for "
+"high-end server systems but has become quite common in recent years even for "
+"rather low-end desktop computers and laptops with the introduction of so "
+"called <quote>multi-core</quote> processors. These contain two or more "
+"processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1165
 #, no-c-format
-msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
+msgid ""
+"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
+"not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1175
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. However, the "
+"standard &debian; &release; kernel image does not support SMP. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1184
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a "
+"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this "
+"time (kernel version &kernelversion;) the way you enable SMP is to select "
+"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</"
+"quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1198
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture, and is supported "
+"by a precompiled &debian; kernel image. Depending on your install media, "
+"this SMP-capable kernel may or may not be installed by default. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1208
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
+msgid ""
+"In order to take advantage of multiple processors, you should check to see "
+"if a kernel package that supports SMP is installed, and if not, choose an "
+"appropriate kernel package."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1214
 #, no-c-format
-msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"You can also build your own customized kernel to support SMP.<phrase arch="
+"\"linux-any\"> You can find a discussion of how to do this in <xref linkend="
+"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way "
+"you enable SMP is to select <quote>&smp-config-option;</quote> in the "
+"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1282,13 +1575,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1226
 #, no-c-format
-msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
+msgid ""
+"&debian;'s support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. On modern PCs, having a graphical "
+"display usually works out of the box. Whether advanced graphics card "
+"features such as 3D-hardware acceleration or hardware-accelerated video are "
+"available, depends on the actual graphics hardware used in the system and in "
+"some cases on the installation of additional <quote>firmware</quote> images "
+"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
+"been reports about hardware on which installation of additional graphics "
+"card firmware was required even for basic graphics support, but these have "
+"been rare exceptions."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1239
 #, no-c-format
-msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
+msgid ""
+"Details on supported graphics cards and pointing devices can be found at "
+"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
+"version &x11ver;."
 msgstr ""
 
 #. Tag: para
@@ -1300,13 +1606,31 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1249
 #, no-c-format
-msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
+msgid ""
+"Most graphics options commonly found on Sparc-based machines are supported. "
+"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, "
+"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), "
+"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards "
+"(glint driver). To use an Elite3D card with X.org you additionally need to "
+"install the <classname>afbinit</classname> package, and read the "
+"documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1259
 #, no-c-format
-msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
+msgid ""
+"It is not uncommon for a Sparc machine to have two graphics cards in a "
+"default configuration. In such a case there is a possibility that the Linux "
+"kernel will not direct its output to the card initially used by the "
+"firmware. The lack of output on the graphical console may then be mistaken "
+"for a hang (usually the last message seen on console is 'Booting Linux...'). "
+"One possible solution is to physically remove one of the video cards; "
+"another option is to disable one of the cards using a kernel boot parameter. "
+"Also, if graphical output is not required or desired, serial console may be "
+"used as an alternative. On some systems use of serial console can be "
+"activated automatically by disconnecting the keyboard before booting the "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -1318,13 +1642,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1282
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
+msgid ""
+"Almost any network interface card (NIC) supported by the &arch-kernel; "
+"kernel should also be supported by the installation system; drivers should "
+"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
+"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
+"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1292
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+msgid ""
+"This includes a lot of generic PCI cards (for systems that have PCI) and the "
+"following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
@@ -1384,7 +1715,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1349
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
+msgid ""
+"On &arch-title;, most built-in Ethernet devices are supported and modules "
+"for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
@@ -1402,31 +1735,52 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1362
 #, no-c-format
-msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
+msgid ""
+"Wireless networking is in general supported as well and a growing number of "
+"wireless adapters are supported by the official &arch-kernel; kernel, "
+"although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1369
 #, no-c-format
-msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
+msgid ""
+"If firmware is needed, the installer will prompt you to load firmware. See "
+"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
+"firmware during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1374
 #, no-c-format
-msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
+msgid ""
+"Wireless NICs that are not supported by the official &arch-kernel; kernel "
+"can generally be made to work under &debian-gnu;, but are not supported "
+"during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1379
 #, no-c-format
-msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
+msgid ""
+"If there is a problem with wireless and there is no other NIC you can use "
+"during the installation, it is still possible to install &debian-gnu; using "
+"a full CD-ROM or DVD image. Select the option to not configure a network and "
+"install using only the packages available from the CD/DVD. You can then "
+"install the driver and firmware you need after the installation is completed "
+"(after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1389
 #, no-c-format
-msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
+msgid ""
+"In some cases the driver you need may not be available as a &debian; "
+"package. You will then have to look if there is source code available in the "
+"internet and compile the driver yourself. How to do this is outside the "
+"scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, "
+"your last resort is to use the <classname>ndiswrapper</classname> package, "
+"which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1438,7 +1792,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1404
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid ""
+"There are a couple of issues with specific network cards that are worth "
+"mentioning here."
 msgstr ""
 
 #. Tag: title
@@ -1450,19 +1806,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1413
 #, no-c-format
-msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
+msgid ""
+"There are various PCI network cards that have the same PCI identification, "
+"but are supported by related, but different drivers. Some cards work with "
+"the <literal>tulip</literal> driver, others with the <literal>dfme</literal> "
+"driver. Because they have the same identification, the kernel cannot "
+"distinguish between them and it is not certain which driver will be loaded. "
+"If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1423
 #, no-c-format
-msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
+msgid ""
+"This is a common problem on Netra systems with a Davicom (DEC-Tulip "
+"compatible) NIC. In that case the <literal>tulip</literal> driver is "
+"probably the correct one. You can prevent this issue by blacklisting the "
+"wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1431
 #, no-c-format
-msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
+msgid ""
+"An alternative solution during the installation is to switch to a shell and "
+"unload the wrong driver module using <userinput>modprobe -r "
+"<replaceable>module</replaceable></userinput> (or both, if they are both "
+"loaded). After that you can load the correct module using "
+"<userinput>modprobe <replaceable>module</replaceable></userinput>. Note that "
+"the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
@@ -1474,7 +1846,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1446
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid ""
+"The <literal>cassini</literal> network driver does not work with Sun B100 "
+"blade systems."
 msgstr ""
 
 #. Tag: title
@@ -1486,7 +1860,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1462
 #, no-c-format
-msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
+msgid ""
+"Support for braille displays is determined by the underlying support found "
+"in <classname>brltty</classname>. Most displays work under "
+"<classname>brltty</classname>, connected via either a serial port, USB or "
+"bluetooth. Details on supported braille devices can be found on the <ulink "
+"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
+"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
@@ -1498,7 +1878,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1477
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
+msgid ""
+"Support for hardware speech synthesis devices is determined by the "
+"underlying support found in <classname>speakup</classname>. "
+"<classname>speakup</classname> only supports integrated boards and external "
+"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
+"are supported). Details on supported hardware speech synthesis devices can "
+"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
+"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
+"classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
@@ -1510,25 +1898,37 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1498
 #, no-c-format
-msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
+msgid ""
+"&arch-kernel; supports a large variety of hardware devices such as mice, "
+"printers, scanners, PCMCIA and USB devices. However, most of these devices "
+"are not required while installing the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1504
 #, no-c-format
-msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
+msgid ""
+"USB hardware generally works fine. On some very old PC systems some USB "
+"keyboards may require additional configuration (see <xref linkend=\"hardware-"
+"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
+"any specific configuration."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1513
 #, no-c-format
-msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
+msgid ""
+"Package installations from XPRAM and tape are not supported by this system. "
+"All packages that you want to install need to be available on a DASD or over "
+"the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1519
 #, no-c-format
-msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Cobalt RaQ has no support for additional devices but the Qube has one "
+"PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -1540,31 +1940,63 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1532
 #, no-c-format
-msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
+msgid ""
+"Besides the availability of a device driver, some hardware also requires so-"
+"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> "
+"to be loaded into the device before it can become operational. This is most "
+"common for network interface cards (especially wireless NICs), but for "
+"example some USB devices and even some hard disk controllers also require "
+"firmware. With many graphics cards, basic functionality is available without "
+"additional firmware, but the use of advanced features requires an "
+"appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1543
 #, no-c-format
-msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
+msgid ""
+"On many older devices which require firmware to work, the firmware file was "
+"permanently placed in an EEPROM/Flash chip on the device itself by the "
+"manufacturer. Nowadays most new devices do not have the firmware embedded "
+"this way anymore, so the firmware file must be uploaded into the device by "
+"the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1551
 #, no-c-format
-msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
+msgid ""
+"In most cases firmware is non-free according to the criteria used by the "
+"&debian-gnu; project and thus cannot be included in the main distribution or "
+"in the installation system. If the device driver itself is included in the "
+"distribution and if &debian-gnu; legally can distribute the firmware, it "
+"will often be available as a separate package from the non-free section of "
+"the archive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1560
 #, no-c-format
-msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
+msgid ""
+"However, this does not mean that such hardware cannot be used during an "
+"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
+"firmware files or packages containing firmware from a removable medium, such "
+"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
+"information on how to load firmware files or packages during the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1569
 #, no-c-format
-msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
+msgid ""
+"If the &d-i; prompts for a firmware file and you do not have this firmware "
+"file available or do not want to install a non-free firmware file on your "
+"system, you can try to proceed without loading the firmware. There are "
+"several cases where a driver prompts for additional firmware because it may "
+"be needed under certain circumstances, but the device does work without it "
+"on most systems (this e.g. happens with certain network cards using the tg3 "
+"driver)."
 msgstr ""
 
 #. Tag: title
@@ -1576,19 +2008,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1588
 #, no-c-format
-msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
+msgid ""
+"There are several vendors, who ship systems with &debian; or other "
+"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</"
+"ulink>. You might pay more for the privilege, but it does buy a level of "
+"peace of mind, since you can be sure that the hardware is well-supported by "
+"GNU/Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1596
 #, no-c-format
-msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
+msgid ""
+"If you do have to buy a machine with Windows bundled, carefully read the "
+"software license that comes with Windows; you may be able to reject the "
+"license and obtain a rebate from your vendor. Searching the Internet for "
+"<quote>windows refund</quote> may get you some useful information to help "
+"with that."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1604
 #, no-c-format
-msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
+"even a used system, it is still important to check that your hardware is "
+"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
+"the references found above. Let your salesperson (if any) know that you're "
+"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
+"vendors."
 msgstr ""
 
 #. Tag: title
@@ -1600,31 +2048,67 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1616
 #, no-c-format
-msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
+msgid ""
+"Some hardware manufacturers simply won't tell us how to write drivers for "
+"their hardware. Others won't allow us access to the documentation without a "
+"non-disclosure agreement that would prevent us from releasing the driver's "
+"source code, which is one of the central elements of free software. Since we "
+"haven't been granted access to usable documentation on these devices, they "
+"simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1626
 #, no-c-format
-msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
+msgid ""
+"In many cases there are standards (or at least some de-facto standards) "
+"describing how an operating system and its device drivers communicate with a "
+"certain class of devices. All devices which comply to such a (de-facto-)"
+"standard can be used with a single generic device driver and no device-"
+"specific drivers are required. With some kinds of hardware (e.g. USB "
+"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
+"mass storage devices like USB flash disks and memory card readers) this "
+"works very well and practically every device sold in the market is standards-"
+"compliant."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1638
 #, no-c-format
-msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
+msgid ""
+"In other fields, among them e.g. printers, this is unfortunately not the "
+"case. While there are many printers which can be addressed via a small set "
+"of (de-facto-)standard control languages and therefore can be made to work "
+"without problems in any operating system, there are quite a few models which "
+"only understand proprietary control commands for which no usable "
+"documentation is available and therefore either cannot be used at all on "
+"free operating systems or can only be used with a vendor-supplied closed-"
+"source driver."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1649
 #, no-c-format
-msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
+msgid ""
+"Even if there is a vendor-provided closed-source driver for such hardware "
+"when purchasing the device, the practical lifespan of the device is limited "
+"by driver availability. Nowadays product cycles have become short and it is "
+"not uncommon that a short time after a consumer device has ceased "
+"production, no driver updates get made available any more by the "
+"manufacturer. If the old closed-source driver does not work anymore after a "
+"system update, an otherwise perfectly working device becomes unusable due to "
+"lacking driver support and there is nothing that can be done in this case. "
+"You should therefore avoid buying closed hardware in the first place, "
+"regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1662
 #, no-c-format
-msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
+msgid ""
+"You can help improve this situation by encouraging manufacturers of closed "
+"hardware to release the documentation and other resources necessary for us "
+"to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
@@ -1636,7 +2120,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1679
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
+msgid ""
+"This section will help you determine which different media types you can use "
+"to install &debian;. There is a whole chapter devoted to media, <xref "
+"linkend=\"install-methods\"/>, which lists the advantages and disadvantages "
+"of each media type. You may want to refer back to this page once you reach "
+"that section."
 msgstr ""
 
 #. Tag: title
@@ -1648,7 +2137,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
+msgid ""
+"In some cases, you'll have to do your first boot from floppy disks. "
+"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch "
+"floppy drive."
 msgstr ""
 
 #. Tag: para
@@ -1666,7 +2158,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1705
 #, no-c-format
-msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
+msgid ""
+"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-"
+"ROMs and DVD-ROMs, because both technologies are really the same from the "
+"operating system's point of view."
 msgstr ""
 
 #. Tag: para
@@ -1684,7 +2179,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1719
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid ""
+"USB CD-ROM drives are also supported, as are FireWire devices that are "
+"supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
@@ -1696,7 +2193,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1728
 #, no-c-format
-msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
+msgid ""
+"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of "
+"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM "
+"drives sold on the PC market do not have this capability. If your CD-ROM "
+"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</"
+"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. "
+"To start the install, simply choose the <quote>System installation</quote> "
+"entry in the firmware."
 msgstr ""
 
 #. Tag: title
@@ -1708,7 +2212,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1744
 #, no-c-format
-msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
+msgid ""
+"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
+"cheap storage device. Most modern computer systems also allow booting the &d-"
+"i; from such a stick. Many modern computer systems, in particular netbooks "
+"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
+"from USB media ist the standard way of installing a new operating system on "
+"them."
 msgstr ""
 
 #. Tag: title
@@ -1720,19 +2230,36 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1758
 #, no-c-format
-msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
+msgid ""
+"The network can be used during the installation to retrieve files needed for "
+"the installation. Whether the network is used or not depends on the "
+"installation method you choose and your answers to certain questions that "
+"will be asked during the installation. The installation system supports most "
+"types of network connections (including PPPoE, but not ISDN or PPP), via "
+"either HTTP or FTP. After the installation is completed, you can also "
+"configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1768
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> the installation system over the "
+"network without needing any local media like CDs/DVDs or USB sticks. If you "
+"already have a netboot-infrastructure available (i.e. you are already "
+"running DHCP and TFTP services in your network), this allows an easy and "
+"fast deployment of a large number of machines. Setting up the necessary "
+"infrastructure requires a certain level of technical experience, so this is "
+"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the "
+"preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1781
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+msgid ""
+"Diskless installation, using network booting from a local area network and "
+"NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
@@ -1744,13 +2271,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1792
 #, no-c-format
-msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
+msgid ""
+"Booting the installation system directly from a hard disk is another option "
+"for many architectures. This will require some other operating system to "
+"load the installer onto the hard disk. This method is only recommended for "
+"special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1799
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid ""
+"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
+"can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
@@ -1762,7 +2295,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1810
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian-gnu; without using the &d-i; described in the rest of this manual. "
+"This kind of install may be useful for users with otherwise unsupported "
+"hardware or on hosts which can't afford downtime. If you are interested in "
+"this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This "
+"installation method is only recommended for advanced users when no other "
+"installation method is available."
 msgstr ""
 
 #. Tag: title
@@ -1774,43 +2314,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1825
 #, no-c-format
-msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
+msgid ""
+"The &debian; installer contains a kernel which is built to maximize the "
+"number of systems it runs on."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1829
 #, no-c-format
-msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+msgid ""
+"Generally, the &debian; installation system includes support for IDE (also "
+"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
+"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
+"(VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1846
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. The following SCSI drivers are supported in the default kernel: "
+"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> "
+"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec "
+"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></"
+"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also "
+"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC "
+"Processors FAQ</ulink> for more information on SPARC hardware supported by "
+"the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1879
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support floppies on "
+"CHRP systems at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support the floppy "
+"drive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1891
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1896
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This means that FBA and ECKD DASDs are supported with the old "
+"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
@@ -1822,12 +2388,22 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1915
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space to perform a normal installation. Note that these are fairly "
+"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-"
+"hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1922
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgid ""
+"Installation on systems with less memory<footnote condition=\"gtk\"> <para> "
+"Installation images that support the graphical installer require more memory "
+"than images that support only the textual installer and should not be used "
+"on systems with less than &minimum-memory; of memory. If there is a choice "
+"between booting the regular and the graphical installer, the former should "
+"be selected. </para> </footnote> or disk space available may be possible but "
+"is only advised for experienced users."
 msgstr ""
-
diff --git a/po/da/install-methods.po b/po/da/install-methods.po
index c164d8428..6f56f6790 100644
--- a/po/da/install-methods.po
+++ b/po/da/install-methods.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,1149 +29,1719 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian-gnu; is from an Official &debian; CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/DVD-ROM images from a &debian; mirror and make your own set, if you have a fast network connection and a CD/DVD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, which is the case on all modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/>. Much effort has been expended to ensure the most-used files are on the first CDs and DVDs, so that a basic desktop installation can be done with only the first DVD or - to a limited extent - even with only the first CD."
+msgid ""
+"By far the easiest way to install &debian-gnu; is from an Official &debian; "
+"CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-"
+"debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/"
+"DVD-ROM images from a &debian; mirror and make your own set, if you have a "
+"fast network connection and a CD/DVD burner (see the <ulink url=\"&url-"
+"debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;"
+"\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; "
+"CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, "
+"which is the case on all modern PCs</phrase>, you can skip right to <xref "
+"linkend=\"boot-installer\"/>. Much effort has been expended to ensure the "
+"most-used files are on the first CDs and DVDs, so that a basic desktop "
+"installation can be done with only the first DVD or - to a limited extent - "
+"even with only the first CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid ""
+"As CDs have a rather limited capacity by today's standards, not all "
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid ""
+"If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
+"relevant on very old PC systems)</phrase>, but you do have a CD set, you can "
+"use an alternative strategy such as <phrase condition=\"supports-floppy-boot"
+"\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition="
+"\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net "
+"boot,</phrase> or manually loading the kernel from the CD to initially boot "
+"the system installer. The files you need for booting by another means are "
+"also on the CD; the &debian; network archive and CD folder organization are "
+"identical. So when archive file paths are given below for particular files "
+"you need for booting, look for those files in the same directories and "
+"subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
-msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a &debian; mirror using FTP, be sure to download "
+"the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
-msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each &debian; mirror in the directory "
+"<ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
-msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
+msgid ""
+"A firmware image is provided for the Thecus N2100 which will automatically "
+"boot <classname>debian-installer</classname>. This image can be installed "
+"using the Thecus firmware upgrade process. This firmware image can be "
+"obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
-msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
+msgid ""
+"The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
+"on which you intend to install &debian;. These images can be obtained from "
+"&glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
-msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
+msgid ""
+"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
+"disk on which you intend to install &debian;. These images can be obtained "
+"from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
-msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
+msgid ""
+"A firmware image is provided for the HP mv2120 which will automatically boot "
+"<classname>debian-installer</classname>. This image can be installed with "
+"uphpmvault on Linux and other systems and with the HP Media Vault Firmware "
+"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-"
+"firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
-msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
+msgid ""
+"The installation files for the QNAP Turbo Station consist of a kernel and "
+"ramdisk as well as a script to write these images to flash. You can obtain "
+"the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
+"kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
-msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
+msgid ""
+"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
+"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
+"obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
-msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
+msgid ""
+"The installation files for LaCie NASes (Network Space v2, Network Space Max "
+"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
+"consist of a kernel and initrd for U-Boot. You can obtain these files from "
+"&lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
-msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
+msgid ""
+"Bootable floppy disks are generally used as a last resort to boot the "
+"installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
-msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
+msgid ""
+"Booting the installer from floppy disk reportedly fails on Mac USB floppy "
+"drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images. This "
+"section describes how to create floppies from disk images on different "
+"platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
-msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
+msgid ""
+"Before you can create the floppies, you will first need to download them "
+"from one of the &debian; mirrors, as explained in <xref linkend="
+"\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an "
+"installation CD-ROM or DVD, the floppy images may also be included on the CD/"
+"DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
-msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
+msgid ""
+"No matter which method you use to create your floppies, you should remember "
+"to flip the write-protect tab on the floppies once you have written them, to "
+"ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
-      "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
-      "$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-      "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> (on Solaris, use <command>eject</command>, see the manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:337
+"To write the floppy disk image files to the floppy disks, you will probably "
+"need root access to the system. Place a good, blank floppy in the floppy "
+"drive. Next, use the command <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly "
+"used name of the floppy disk device, it may be different on your "
+"workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</"
+"filename>)</phrase>. The command may return to the prompt before Unix has "
+"finished writing the floppy disk, so look for the disk-in-use light on the "
+"floppy drive and be sure that the light is out and the disk has stopped "
+"revolving before you remove it from the drive. On some systems, you'll have "
+"to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> "
+"(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:336
 #, no-c-format
-msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+msgid ""
+"Some systems attempt to automatically mount a floppy disk when you place it "
+"in the drive. You might have to disable this feature before the workstation "
+"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
+"management to get raw access to the floppy. First, make sure that the floppy "
+"is auto-mounted (using <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
-msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 or amd64 machine, you can use one of the "
+"following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> programs can "
+"be used under MS-DOS. To use these programs, first make sure that you are "
+"booted into DOS. Trying to use these programs from within a DOS box in "
+"Windows, or double-clicking on these programs from the Windows Explorer is "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
-msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
+msgid ""
+"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
+"ME, XP and probably later versions. To use it you will need to unpack diskio."
+"dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
-msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official &debian; CD-ROMs under the "
+"<filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
-msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
+msgid ""
+"An AppleScript, <application>Make &debian; Floppy</application>, is "
+"available for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on "
+"your desktop, and then drag any floppy image file to it. You must have "
+"Applescript installed and enabled in your extensions manager. Disk Copy will "
+"ask you to confirm that you wish to erase the floppy and proceed to write "
+"the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> file is an example of a floppy image. Use one of the following "
+"methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian-gnu; CD, then the Type and Creator are already set "
+"correctly. The following <command>Creator-Changer</command> steps are only "
+"necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> image file from the "
+"resulting dialog. It will ask you to insert a floppy, then ask if you really "
+"want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
-msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
+msgid ""
+"To prepare the USB stick, you will need a system where GNU/Linux is already "
+"running and where USB is supported. With current GNU/Linux systems the USB "
+"stick should be automatically recognized when you insert it. If it is not "
+"you should check that the usb-storage kernel module is loaded. When the USB "
+"stick is inserted, it will be mapped to a device named <filename>/dev/sdX</"
+"filename>, where the <quote>X</quote> is a letter in the range a-z. You "
+"should be able to see to which device the USB stick was mapped by running "
+"the command <command>dmesg</command> after inserting it. To write to your "
+"stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
-msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
+msgid ""
+"The procedures described in this section will destroy anything already on "
+"the device! Make very sure that you use the correct device name for your USB "
+"stick. If you use the wrong device the result could be that all information "
+"on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
-msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
+msgid ""
+"Debian CD and DVD images can now be written directly a USB stick, which is a "
+"very easy way to make a bootable USB stick. Simply choose a CD or DVD image "
+"that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to "
+"get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
-msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
+msgid ""
+"Alternatively, for very small USB sticks, only a few megabytes in size, you "
+"can download the <filename>mini.iso</filename> image from the "
+"<filename>netboot</filename> directory (at the location mentioned in <xref "
+"linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
-msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
+msgid ""
+"A special method can be used to add firmware to the <filename>mini.iso</"
+"filename>. First, write the <filename>mini.iso</filename> to the USB stick. "
+"Next obtain the necessary firmware files. See <xref linkend=\"loading-"
+"firmware\"/> for more information about firmware. Now unplug and replug the "
+"USB stick, and two partitions should now be visible on it. You should mount "
+"the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
-      "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
-      "# cd /mnt\n"
-      "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
-      "# cd /\n"
-      "# umount"
+"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
+"# cd /mnt\n"
+"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
+"# cd /\n"
+"# umount"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
-msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
+msgid ""
+"The CD or DVD image you choose should be written directly to the USB stick, "
+"overwriting its current contents. For example, when using an existing GNU/"
+"Linux system, the CD or DVD image file can be written to a USB stick as "
+"follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
-      "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
-      "<prompt>#</prompt> <userinput>sync</userinput>"
+"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
+"<replaceable>sdX</replaceable></userinput>\n"
+"<prompt>#</prompt> <userinput>sync</userinput>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
-msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
+msgid ""
+"Simply writing the CD or DVD image to USB like this should work fine for "
+"most users. The other options below are more complex, mainly for people with "
+"specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
-msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"An alternative way to set up your USB stick is to manually copy the "
+"installer files, and also a CD image to it. Note that the USB stick should "
+"be at least 1 GB in size (smaller setups are possible if you follow <xref "
+"linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
-msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
+msgid ""
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) <phrase arch="
+"\"x86\">as well as <classname>syslinux</classname> and its configuration "
+"file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</"
+"classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
-msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
+msgid ""
+"Note that, although convenient, this method does have one major "
+"disadvantage: the logical size of the device will be limited to 1 GB, even "
+"if the capacity of the USB stick is larger. You will need to repartition the "
+"USB stick and create new file systems to get its full capacity back if you "
+"ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
-msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
+msgid ""
+"Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
+"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract "
+"the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
-msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"After that, mount the USB memory stick <phrase arch=\"x86\">"
+"(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</"
+"phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</"
+"replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch="
+"\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS "
+"filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
+"CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
+"are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
-msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
+msgid ""
+"If you like more flexibility or just want to know what's going on, you "
+"should use the following method to put the files on your stick. One "
+"advantage of using this method is that &mdash; if the capacity of your USB "
+"stick is large enough &mdash; you have the option of copying a full CD ISO "
+"image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
-msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to set up the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
-      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
-      "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
+"Since most USB sticks come pre-configured with a single FAT16 partition, you "
+"probably won't have to repartition or reformat the stick. If you have to do "
+"that anyway, use <command>cfdisk</command> or any other partitioning tool to "
+"create a FAT16 partition<footnote> <para> Don't forget to set the "
+"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR "
+"using: <informalexample><screen>\n"
+"# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+"</screen></informalexample> The <command>install-mbr</command> command is "
+"contained in the <classname>mbr</classname> &debian; package. Then create "
+"the filesystem using: <informalexample><screen>\n"
+"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. Although any boot loader (e.g. <classname>lilo</"
+"classname>) should work, it's convenient to use <classname>syslinux</"
+"classname>, since it uses a FAT16 partition and can be reconfigured by just "
+"editing a text file. Any operating system which supports the FAT file system "
+"can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
-      "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
-      "# syslinux /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>syslinux</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"To put <classname>syslinux</classname> on the FAT16 partition on your USB "
+"stick, install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
+"# syslinux /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>syslinux</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick: "
+"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or "
+"<filename>linux</filename> (kernel binary) </para></listitem> "
+"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </"
+"para></listitem> </itemizedlist> You can choose between either the regular "
+"version or the graphical version of the installer. The latter can be found "
+"in the <filename>gtk</filename> subdirectory. If you want to rename the "
+"files, please note that <classname>syslinux</classname> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
-      "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
-      "default vmlinuz\n"
-      "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
+"Next you should create a <filename>syslinux.cfg</filename> configuration "
+"file, which at a bare minimum should contain the following two lines (change "
+"the name of the kernel binary to <quote><filename>linux</filename></quote> "
+"if you used a <filename>netboot</filename> image): "
+"<informalexample><screen>\n"
+"default vmlinuz\n"
+"append initrd=initrd.gz\n"
+"</screen></informalexample> For the graphical installer you should add "
+"<userinput>vga=788</userinput> to the second line. Other parameters can be "
+"appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
-msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgid ""
+"To enable the boot prompt to permit further parameter appending, add a "
+"<userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
-msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
+msgid ""
+"If you used an <filename>hd-media</filename> image, you should now copy the "
+"ISO file of a &debian; ISO image<footnote> <para> You can use either a "
+"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure "
+"to select one that fits. Note that the <quote>netboot <filename>mini.iso</"
+"filename></quote> image is not usable for this purpose. </para> </footnote> "
+"onto the stick. When you are done, unmount the USB memory stick "
+"(<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
-      "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
-      "$ hformat /dev/<replaceable>sdX2</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> &debian; package."
+"Most USB sticks do not come pre-configured in such a way that Open Firmware "
+"can boot from them, so you will need to repartition the stick. On Mac "
+"systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></"
+"userinput>, initialise a new partition map using the <userinput>i</"
+"userinput> command, and create a new partition of type Apple_Bootstrap using "
+"the <userinput>C</userinput> command. (Note that the first \"partition\" "
+"will always be the partition map itself.) Then type "
+"<informalexample><screen>\n"
+"$ hformat /dev/<replaceable>sdX2</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> boot loader can be "
+"installed on an HFS filesystem and can be reconfigured by just editing a "
+"text file. Any operating system which supports the HFS file system can be "
+"used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
-      "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
-      "$ hmount /dev/<replaceable>sdX2</replaceable>\n"
-      "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
-      "$ hattrib -c UNIX -t tbxi :yaboot\n"
-      "$ hattrib -b :\n"
-      "$ humount\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:857
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
+"$ hmount /dev/<replaceable>sdX2</replaceable>\n"
+"$ hcopy -r /usr/lib/yaboot/yaboot :\n"
+"$ hattrib -c UNIX -t tbxi :yaboot\n"
+"$ hattrib -b :\n"
+"$ humount\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be otherwise mounted during this procedure. "
+"This procedure writes the boot loader to the partition, and uses the HFS "
+"utilities to mark it in such a way that Open Firmware will boot it. Having "
+"done this, the rest of the USB stick may be prepared using the normal Unix "
+"utilities."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:856
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
-      "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
-      "default=install\n"
-      "root=/dev/ram\n"
-      "\n"
-      "message=/boot.msg\n"
-      "\n"
-      "image=/vmlinux\n"
-      "        label=install\n"
-      "        initrd=/initrd.gz\n"
-      "        initrd-size=10000\n"
-      "        read-only\n"
-      "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
+"default=install\n"
+"root=/dev/ram\n"
+"\n"
+"message=/boot.msg\n"
+"\n"
+"image=/vmlinux\n"
+"        label=install\n"
+"        initrd=/initrd.gz\n"
+"        initrd-size=10000\n"
+"        read-only\n"
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
-msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
+msgid ""
+"The installer may be booted using boot files placed on an existing hard "
+"drive partition, either launched from another operating system or by "
+"invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
-msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+msgid ""
+"The installer cannot boot from files on an HFS+ file system. MacOS System "
+"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To "
+"determine whether your existing file system is HFS+, select <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
-msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
+msgid ""
+"At boot time, both bootloaders support loading in memory not only the "
+"kernel, but also a disk image. This RAM disk can be used as the root file-"
+"system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
-msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the &debian; archives to a convenient location "
+"on your hard drive (note that LILO can not boot from files on an NTFS file "
+"system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
-msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
+msgid ""
+"This section explains how to prepare your hard drive for booting the "
+"installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
-msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
+msgid ""
+"Copy the following directories from a &debian; CD image to <filename>c:\\</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
-msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
+msgid ""
+"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your &debian; installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on &debian; http/ftp mirrors and official &debian; CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
-msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+msgid ""
+"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
+"well as loading ELF binaries directly from the hard disk. These machines "
+"will boot Linux directly via <command>yaboot</command>, which supports "
+"loading a kernel and RAMdisk directly from an ext2 partition, as well as "
+"dual-booting with MacOS. Hard disk booting of the installer is particularly "
+"appropriate for newer machines without floppy drives. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (not move) the following four files which you "
+"downloaded earlier from the &debian; archives, onto the root level of your "
+"hard drive (this can be accomplished by <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the <command>L</command> command to check for the partition number. You "
+"will need this partition number for the command you type at the Open "
+"Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
-msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
+msgid ""
+"If your machine is connected to a local area network, you may be able to "
+"boot it over the network from another machine, using TFTP. If you intend to "
+"boot the installation system from another machine, the boot files will need "
+"to be placed in specific locations on that machine, and the machine "
+"configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
-msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
+msgid ""
+"You need to set up a TFTP server, and for many machines a DHCP server<phrase "
+"condition=\"supports-rarp\">, or RARP server</phrase><phrase condition="
+"\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol.</phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image.</phrase> The DHCP "
+"(Dynamic Host Configuration Protocol) is a more flexible, backwards-"
+"compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
-msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
+msgid ""
+"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
+"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
+"boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
-msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
+msgid ""
+"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
+"the client. Theoretically, any server, on any platform, which implements "
+"these protocols, may be used. In the examples in this section, we shall "
+"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
-msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
+msgid ""
+"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
+"It's written by the same author as the <classname>syslinux</classname> "
+"bootloader and is therefore least likely to cause issues. A good alternative "
+"is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
-msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
+msgid ""
+"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>ip addr show dev eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
+msgid ""
+"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
+"you use the <command>rarpd</command> program. You need to ensure that the "
+"Ethernet hardware address for the client is listed in the <quote>ethers</"
+"quote> database (either in the <filename>/etc/ethers</filename> file, or via "
+"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start "
+"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</"
+"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/"
+"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/"
+"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
+"gnu;, the <classname>dhcp3-server</classname> package is recommended. Here "
+"is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</"
+"filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
-      "option domain-name \"example.com\";\n"
-      "option domain-name-servers ns1.example.com;\n"
-      "option subnet-mask 255.255.255.0;\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "server-name \"servername\";\n"
-      "\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option routers 192.168.1.1;\n"
-      "}\n"
-      "\n"
-      "host clientname {\n"
-      "  filename \"/tftpboot.img\";\n"
-      "  server-name \"servername\";\n"
-      "  next-server servername;\n"
-      "  hardware ethernet 01:23:45:67:89:AB;\n"
-      "  fixed-address 192.168.1.90;\n"
-      "}"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1237
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+"  filename \"/tftpboot.img\";\n"
+"  server-name \"servername\";\n"
+"  next-server servername;\n"
+"  hardware ethernet 01:23:45:67:89:AB;\n"
+"  fixed-address 192.168.1.90;\n"
+"}"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1236
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
-#, no-c-format
-msgid ""
-      "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
-      "option domain-name \"example.com\";\n"
-      "\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "\n"
-      "allow booting;\n"
-      "allow bootp;\n"
-      "\n"
-      "# The next paragraph needs to be modified to fit your case\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option broadcast-address 192.168.1.255;\n"
-      "# the gateway address which can be different\n"
-      "# (access to the internet for instance)\n"
-      "  option routers 192.168.1.1;\n"
-      "# indicate the dns you want to use\n"
-      "  option domain-name-servers 192.168.1.3;\n"
-      "}\n"
-      "\n"
-      "group {\n"
-      "  next-server 192.168.1.3;\n"
-      "  host tftpclient {\n"
-      "# tftp client hardware address\n"
-      "  hardware ethernet  00:10:DC:27:6C:15;\n"
-      "  filename \"pxelinux.0\";\n"
-      " }\n"
-      "}\n"
-      "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+#: install-methods.xml:1255
+#, no-c-format
+msgid ""
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different\n"
+"# (access to the internet for instance)\n"
+"  option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+"  option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"group {\n"
+"  next-server 192.168.1.3;\n"
+"  host tftpclient {\n"
+"# tftp client hardware address\n"
+"  hardware ethernet  00:10:DC:27:6C:15;\n"
+"  filename \"pxelinux.0\";\n"
+" }\n"
+"}\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux. The first is CMU "
+"<command>bootpd</command>. The other is actually a DHCP server: ISC "
+"<command>dhcpd</command>. In &debian-gnu; these are contained in the "
+"<classname>bootp</classname> and <classname>dhcp3-server</classname> "
+"packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
-      "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
-      "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-      "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
-      "client:\\\n"
-      "  hd=/tftpboot:\\\n"
-      "  bf=tftpboot.img:\\\n"
-      "  ip=192.168.1.90:\\\n"
-      "  sm=255.255.255.0:\\\n"
-      "  sa=192.168.1.1:\\\n"
-      "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1318
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you "
+"can run <userinput>update-inetd --enable bootps</userinput>, then "
+"<userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your "
+"BOOTP server does not run &debian;, the line in question should look like: "
+"<informalexample><screen>\n"
+"bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
+"client:\\\n"
+"  hd=/tftpboot:\\\n"
+"  bf=tftpboot.img:\\\n"
+"  ip=192.168.1.90:\\\n"
+"  sm=255.255.255.0:\\\n"
+"  sa=192.168.1.1:\\\n"
+"  ha=0123456789AB:\n"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI machines you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1317
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd."
+"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/"
+"init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
-msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
+msgid ""
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
-msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
+msgid ""
+"In the case of <classname>tftpd-hpa</classname> there are two ways the "
+"service can be run. It can be started on demand by the system's "
+"<classname>inetd</classname> daemon, or it can be set up to run as an "
+"independent daemon. Which of these methods is used is selected when the "
+"package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
-msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
+msgid ""
+"Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
+"to serve images from. However, &debian-gnu; packages may use other "
+"directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by "
+"default uses <filename>/srv/tftp</filename>. You may have to adjust the "
+"configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
-msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
+msgid ""
+"All <command>in.tftpd</command> alternatives available in &debian; should "
+"log TFTP requests to the system logs by default. Some of them support a "
+"<userinput>-v</userinput> argument to increase verbosity. It is recommended "
+"to check these log messages in case of boot problems as they are a good "
+"starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
-      "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
-      "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
-      "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-      "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"If you intend to install &debian; on an SGI machine and your TFTP server is "
+"a GNU/Linux box running Linux 2.4, you'll need to set the following on your "
+"server: <informalexample><screen>\n"
+"# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets "
+"are sent from a source port no greater than 32767, or the download will "
+"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
+"the PROM, and you can avoid it by setting <informalexample><screen>\n"
+"# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. You may "
+"have to make a link from that file to the file which <command>tftpd</"
+"command> will use for booting a particular client. Unfortunately, the file "
+"name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. You will need to download the following files from the "
+"<filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
-      "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-      "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
-      "</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"Some SPARC architectures add the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your "
+"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename "
+"would be <filename>C0A80103.SUN4C</filename>. However, there are also "
+"subarchitectures where the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. An easy way to determine the "
+"hexadecimal code for the IP address is to enter the following command in a "
+"shell (assuming the machine's intended IP is 10.0.0.4). "
+"<informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> To get to the correct filename, you will need to "
+"change all letters to uppercase and if necessary append the subarchitecture "
+"name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
-msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
+msgid ""
+"If you've done all this correctly, giving the command <userinput>boot net</"
+"userinput> from the OpenPROM should load the image. If the image cannot be "
+"found, try checking the logs on your tftp server to see which image name is "
+"being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
-msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+msgid ""
+"You can also force some sparc systems to look for a specific file name by "
+"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
-msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI machines you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. &debian; packages intended for this include <classname>fai-"
+"quickstart</classname> (which can use an install server) and the &debian; "
+"Installer itself. Have a look at the <ulink url=\"http://fai-project.org"
+"\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
-msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
+msgid ""
+"The &debian; Installer supports automating installs via preconfiguration "
+"files. A preconfiguration file can be loaded from the network or from "
+"removable media, and used to fill in answers to questions asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
-msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Full documentation on preseeding including a working example that you can "
+"edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-
diff --git a/po/da/installation-howto.po b/po/da/installation-howto.po
index 6b8f358e5..369f718c1 100644
--- a/po/da/installation-howto.po
+++ b/po/da/installation-howto.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:7
 #, no-c-format
-msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document."
+msgid ""
+"This document describes how to install &debian-gnu; &releasename; for the "
+"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a "
+"quick walkthrough of the installation process which should contain all the "
+"information you will need for most installs. When more information can be "
+"useful, we will link to more detailed explanations in other parts of this "
+"document."
 msgstr ""
 
 #. Tag: title
@@ -34,7 +41,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:20
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)."
+msgid ""
+"<phrase condition=\"unofficial-build\"> The debian-installer is still in a "
+"beta state. </phrase> If you encounter bugs during your install, please "
+"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report "
+"them. If you have questions which cannot be answered by this document, "
+"please direct them to the debian-boot mailing list (&email-debian-boot-"
+"list;) or ask on IRC (#debian-boot on the OFTC network)."
 msgstr ""
 
 #. Tag: title
@@ -46,19 +59,30 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:37
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>."
+msgid ""
+"<phrase condition=\"unofficial-build\"> For some quick links to CD images, "
+"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> "
+"The debian-cd team provides builds of CD images using &d-i; on the <ulink "
+"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on "
+"where to get CDs, see <xref linkend=\"official-cdrom\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:47
 #, no-c-format
-msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on &debian; mirrors."
+msgid ""
+"Some installation methods require other images than CD images. <phrase "
+"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home "
+"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files"
+"\"/> explains how to find images on &debian; mirrors."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:57
 #, no-c-format
-msgid "The subsections below will give the details about which images you should get for each possible means of installation."
+msgid ""
+"The subsections below will give the details about which images you should "
+"get for each possible means of installation."
 msgstr ""
 
 #. Tag: title
@@ -70,13 +94,26 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:67
 #, no-c-format
-msgid "The netinst CD image is a popular image which can be used to install &releasename; with the &d-i;. This image is intended to boot from CD and install additional packages over a network; hence the name 'netinst'. The image has the software components needed to run the installer and the base packages to provide a minimal &releasename; system. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set."
+msgid ""
+"The netinst CD image is a popular image which can be used to install "
+"&releasename; with the &d-i;. This image is intended to boot from CD and "
+"install additional packages over a network; hence the name 'netinst'. The "
+"image has the software components needed to run the installer and the base "
+"packages to provide a minimal &releasename; system. If you'd rather, you can "
+"get a full size CD image which will not need the network to install. You "
+"only need the first CD of the set."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:77
 #, no-c-format
-msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>"
+msgid ""
+"Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-"
+"x86\">To boot the CD, you may need to change your BIOS configuration, as "
+"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc"
+"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while "
+"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -88,31 +125,50 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:92
 #, no-c-format
-msgid "If you can't boot from CD, you can download floppy images to install &debian;. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks."
+msgid ""
+"If you can't boot from CD, you can download floppy images to install "
+"&debian;. You need the <filename>floppy/boot.img</filename>, the "
+"<filename>floppy/root.img</filename> and one or more of the driver disks."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:98
 #, no-c-format
-msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy &mdash; use the one with <filename>root.img</filename> on it."
+msgid ""
+"The boot floppy is the one with <filename>boot.img</filename> on it. This "
+"floppy, when booted, will prompt you to insert a second floppy &mdash; use "
+"the one with <filename>root.img</filename> on it."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:104
 #, no-c-format
-msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>."
+msgid ""
+"If you're planning to install over the network, you will usually need the "
+"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, "
+"and some less common network cards, you will also need a second driver "
+"floppy, <filename>floppy/net-drivers-2.img</filename>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:111
 #, no-c-format
-msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD."
+msgid ""
+"If you have a CD, but cannot boot from it, then boot from floppies and use "
+"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the "
+"install using the CD."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:117
 #, no-c-format
-msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them."
+msgid ""
+"Floppy disks are one of the least reliable media around, so be prepared for "
+"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each "
+"<filename>.img</filename> file you downloaded goes on a single floppy; you "
+"can use the dd command to write it to /dev/fd0 or some other means (see "
+"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than "
+"one floppy, it's a good idea to label them."
 msgstr ""
 
 #. Tag: title
@@ -124,37 +180,62 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:131
 #, no-c-format
-msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy &debian; install medium that you can take with you anywhere."
+msgid ""
+"It's also possible to install from removable USB storage devices. For "
+"example a USB keychain can make a handy &debian; install medium that you can "
+"take with you anywhere."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:137
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download any Debian "
+"CD or DVD image that will fit on it, and write the CD image directly to the "
+"memory stick. Of course this will destroy anything already on the memory "
+"stick. This works because Debian CD images are \"isohybrid\" images that can "
+"boot both from CD and from USB drives."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:145
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from that file. Write this image directly to your memory stick, which must be at least 1 GB in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download <filename>hd-"
+"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from "
+"that file. Write this image directly to your memory stick, which must be at "
+"least 1 GB in size. Of course this will destroy anything already on the "
+"memory stick. Then mount the memory stick, which will now have a FAT "
+"filesystem on it. Next, download a &debian; netinst CD image, and copy that "
+"file to the memory stick; any filename is ok as long as it ends in <literal>."
+"iso</literal>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:156
 #, no-c-format
-msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
+msgid ""
+"There are other, more flexible ways to set up a memory stick to use the "
+"debian-installer, and it's possible to get it to work with smaller memory "
+"sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:162
 #, no-c-format
-msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Some BIOSes can boot USB storage directly, and some cannot. You may need to "
+"configure your BIOS to boot from a <quote>removable drive</quote> or even a "
+"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful "
+"hints and details, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:169
 #, no-c-format
-msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Booting Macintosh systems from USB storage devices involves manual use of "
+"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: title
@@ -166,13 +247,22 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:179
 #, no-c-format
-msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;."
+msgid ""
+"It's also possible to boot &d-i; completely from the net. The various "
+"methods to netboot depend on your architecture and netboot setup. The files "
+"in <filename>netboot/</filename> can be used to netboot &d-i;."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:185
 #, no-c-format
-msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The easiest thing to set up is probably PXE netbooting. Untar the file "
+"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</"
+"filename> or wherever is appropriate for your tftp server. Set up your DHCP "
+"server to pass filename <filename>pxelinux.0</filename> to clients, and with "
+"luck everything will just work. For detailed instructions, see <xref linkend="
+"\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -184,7 +274,15 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:200
 #, no-c-format
-msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>"
+msgid ""
+"It's possible to boot the installer using no removable media, but just an "
+"existing hard disk, which can have a different OS on it. Download "
+"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</"
+"filename>, and a &debian; CD image to the top-level directory of the hard "
+"disk. Make sure that the CD image has a filename ending in <literal>.iso</"
+"literal>. Now it's just a matter of booting linux with the initrd. <phrase "
+"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -196,91 +294,156 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:218
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
+msgid ""
+"Once the installer starts, you will be greeted with an initial screen. Press "
+"&enterkey; to boot, or read the instructions for other boot methods and "
+"parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:224
 #, no-c-format
-msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
+msgid ""
+"After a while you will be asked to select your language. Use the arrow keys "
+"to pick a language and press &enterkey; to continue. Next you'll be asked to "
+"select your country, with the choices including countries where your "
+"language is spoken. If it's not on the short list, a list of all the "
+"countries in the world is available."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:232
 #, no-c-format
-msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
+msgid ""
+"You may be asked to confirm your keyboard layout. Choose the default unless "
+"you know better."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:237
 #, no-c-format
-msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
+msgid ""
+"Now sit back while debian-installer detects some of your hardware, and loads "
+"the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:242
 #, no-c-format
-msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
+msgid ""
+"Next the installer will try to detect your network hardware and set up "
+"networking by DHCP. If you are not on a network or do not have DHCP, you "
+"will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:248
 #, no-c-format
-msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones."
+msgid ""
+"The next step is setting up your clock and time zone. The installer will try "
+"to contact a time server on the Internet to ensure the clock is set "
+"correctly. The time zone is based on the country selected earlier and the "
+"installer will only ask to select one if a country has multiple zones."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:255
 #, no-c-format
-msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"Now it is time to partition your disks. First you will be given the "
+"opportunity to automatically partition either an entire drive, or available "
+"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is "
+"recommended for new users or anyone in a hurry. If you do not want to "
+"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:263
 #, no-c-format
-msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size."
+msgid ""
+"If you have an existing DOS or Windows partition that you want to preserve, "
+"be very careful with automatic partitioning. If you choose manual "
+"partitioning, you can use the installer to resize existing FAT or NTFS "
+"partitions to create room for the &debian; install: simply select the "
+"partition and specify its new size."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:270
 #, no-c-format
-msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning."
+msgid ""
+"On the next screen you will see your partition table, how the partitions "
+"will be formatted, and where they will be mounted. Select a partition to "
+"modify or delete it. If you did automatic partitioning, you should just be "
+"able to choose <guimenuitem>Finish partitioning and write changes to disk</"
+"guimenuitem> from the menu to use what it set up. Remember to assign at "
+"least one partition for swap space and to mount a partition on <filename>/</"
+"filename>. For more detailed information on how to use the partitioner, "
+"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend="
+"\"partitioning\"/> has more general information about partitioning."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:283
 #, no-c-format
-msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
+msgid ""
+"Now &d-i; formats your partitions and starts to install the base system, "
+"which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:288
 #, no-c-format
-msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step."
+msgid ""
+"The base system that was installed earlier is a working, but very minimal "
+"installation. To make the system more functional the next step allows you to "
+"install additional packages by selecting tasks. Before packages can be "
+"installed <classname>apt</classname> needs to be configured as that defines "
+"from where the packages will be retrieved. The <quote>Standard system</"
+"quote> task will be selected by default and should normally be installed. "
+"Select the <quote>Desktop environment</quote> task if you would like to have "
+"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> "
+"for additional information about this step."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:300
 #, no-c-format
-msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account."
+msgid ""
+"Installation of the base system is followed by setting up user accounts. By "
+"default you will need to provide a password for the <quote>root</quote> "
+"(administrator) account and information necessary to create one regular user "
+"account."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:307
 #, no-c-format
-msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
+msgid ""
+"The last step is to install a boot loader. If the installer detects other "
+"operating systems on your computer, it will add them to the boot menu and "
+"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to "
+"the master boot record of the first harddrive, which is generally a good "
+"choice. You'll be given the opportunity to override that choice and install "
+"it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:317
 #, no-c-format
-msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>."
+msgid ""
+"&d-i; will now tell you that the installation has finished. Remove the cdrom "
+"or other boot media and hit &enterkey; to reboot your machine. It should "
+"boot up into the newly installed system and allow you to log in. This is "
+"explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:324
 #, no-c-format
-msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
+msgid ""
+"If you need more information on the install process, see <xref linkend=\"d-i-"
+"intro\"/>."
 msgstr ""
 
 #. Tag: title
@@ -292,13 +455,23 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:334
 #, no-c-format
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>."
+msgid ""
+"If you successfully managed an installation with &d-i;, please take time to "
+"provide us with a report. The simplest way to do so is to install the "
+"reportbug package (<command>aptitude install reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:344
 #, no-c-format
-msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
+msgid ""
+"If you did not complete the install, you probably found a bug in debian-"
+"installer. To improve the installer it is necessary that we know about them, "
+"so please take the time to report them. You can use an installation report "
+"to report problems; if the install completely fails, see <xref linkend="
+"\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
@@ -310,6 +483,7 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:357
 #, no-c-format
-msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read <xref linkend=\"post-install\"/>."
+msgid ""
+"We hope that your &debian; installation is pleasant and that you find "
+"&debian; useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
-
diff --git a/po/da/partitioning.po b/po/da/partitioning.po
index 5cab7d795..2be4d60bf 100644
--- a/po/da/partitioning.po
+++ b/po/da/partitioning.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,57 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
+msgid ""
+"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can "
+"have a single partition containing the entire operating system, "
+"applications, and your personal files. Most people feel that a separate swap "
+"partition is also a necessity, although it's not strictly true. <quote>Swap</"
+"quote> is scratch space for an operating system, which allows the system to "
+"use disk storage as <quote>virtual memory</quote>. By putting swap on a "
+"separate partition, &arch-kernel; can make much more efficient use of it. It "
+"is possible to force &arch-kernel; to use a regular file as swap, but it is "
+"not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid ""
+"Most people choose to give GNU/&arch-kernel; more than the minimum number of "
+"partitions, however. There are two reasons you might want to break up the "
+"file system into a number of smaller partitions. The first is for safety. If "
+"something happens to corrupt the file system, generally only one partition "
+"is affected. Thus, you only have to replace (from the backups you've been "
+"carefully keeping) a portion of your system. At a bare minimum, you should "
+"consider creating what is commonly called a <quote>root partition</quote>. "
+"This contains the most essential components of the system. If any other "
+"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix "
+"the system. This can save you the trouble of having to reinstall the system "
+"from scratch."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:40
 #, no-c-format
-msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed."
+msgid ""
+"The second reason is generally more important in a business setting, but it "
+"really depends on your use of the machine. For example, a mail server "
+"getting spammed with e-mail can easily fill a partition. If you made "
+"<filename>/var/mail</filename> a separate partition on the mail server, most "
+"of the system will remain working even if you get spammed."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:48
 #, no-c-format
-msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?"
+msgid ""
+"The only real drawback to using more partitions is that it is often "
+"difficult to know in advance what your needs will be. If you make a "
+"partition too small then you will either have to reinstall the system or you "
+"will be constantly moving things around to make room in the undersized "
+"partition. On the other hand, if you make the partition too big, you will be "
+"wasting space that could be used elsewhere. Disk space is cheap nowadays, "
+"but why throw your money away?"
 msgstr ""
 
 #. Tag: title
@@ -58,7 +91,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:68
 #, no-c-format
-msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all &debian; systems include these directories:"
+msgid ""
+"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink> for directory and file naming. This standard "
+"allows users and software programs to predict the location of files and "
+"directories. The root level directory is represented simply by the slash "
+"<filename>/</filename>. At the root level, all &debian; systems include "
+"these directories:"
 msgstr ""
 
 #. Tag: entry
@@ -280,37 +319,77 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:142
 #, no-c-format
-msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
+msgid ""
+"The following is a list of important considerations regarding directories "
+"and partitions. Note that disk usage varies widely given system "
+"configuration and specific usage patterns. The recommendations here are "
+"general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
+msgid ""
+"The root partition <filename>/</filename> must always physically contain "
+"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</"
+"filename>, <filename>/lib</filename> and <filename>/dev</filename>, "
+"otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for "
+"the root partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
+msgid ""
+"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</"
+"filename>), libraries (<filename>/usr/lib</filename>), documentation "
+"(<filename>/usr/share/doc</filename>), etc. This is the part of the file "
+"system that generally takes up most space. You should provide at least 500MB "
+"of disk space. This amount should be increased depending on the number and "
+"type of packages you plan to install. A generous workstation or server "
+"installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid ""
+"<filename>/var</filename>: variable data like news articles, e-mails, web "
+"sites, databases, the packaging system cache, etc. will be placed under this "
+"directory. The size of this directory depends greatly on the usage of your "
+"system, but for most people will be dictated by the package management "
+"tool's overhead. If you are going to do a full installation of just about "
+"everything &debian; has to offer, all in one session, setting aside 2 or 3 "
+"GB of space for <filename>/var</filename> should be sufficient. If you are "
+"going to install in pieces (that is to say, install services and utilities, "
+"followed by text stuff, then X, ...), you can get away with 300&ndash;500 "
+"MB. If hard drive space is at a premium and you don't plan on doing major "
+"system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid ""
+"<filename>/tmp</filename>: temporary data created by programs will most "
+"likely go in this directory. 40&ndash;100MB should usually be enough. Some "
+"applications &mdash; including archive manipulators, CD/DVD authoring tools, "
+"and multimedia software &mdash; may use <filename>/tmp</filename> to "
+"temporarily store image files. If you plan to use such applications, you "
+"should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid ""
+"<filename>/home</filename>: every user will put his personal data into a "
+"subdirectory of this directory. Its size depends on how many users will be "
+"using the system and what files are to be stored in their directories. "
+"Depending on your planned usage you should reserve about 100MB for each "
+"user, but adapt this value to your needs. Reserve a lot more space if you "
+"plan to save a lot of multimedia files (pictures, MP3, movies) in your home "
+"directory."
 msgstr ""
 
 #. Tag: title
@@ -322,49 +401,91 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:223
 #, no-c-format
-msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
+msgid ""
+"For new users, personal &debian; boxes, home systems, and other single-user "
+"setups, a single <filename>/</filename> partition (plus swap) is probably "
+"the easiest, simplest way to go. However, if your partition is larger than "
+"around 6GB, choose ext3 as your partition type. Ext2 partitions need "
+"periodic file system integrity checking, and this can cause delays during "
+"booting when the partition is large."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:232
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid ""
+"For multi-user systems or systems with lots of disk space, it's best to put "
+"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</"
+"filename>, and <filename>/home</filename> each on their own partitions "
+"separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid ""
+"You might need a separate <filename>/usr/local</filename> partition if you "
+"plan to install many programs that are not part of the &debian; "
+"distribution. If your machine will be a mail server, you might need to make "
+"<filename>/var/mail</filename> a separate partition. Often, putting "
+"<filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, "
+"is a good idea. If you are setting up a server with lots of user accounts, "
+"it's generally good to have a separate, large <filename>/home</filename> "
+"partition. In general, the partitioning situation varies from computer to "
+"computer depending on its uses."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:252
 #, no-c-format
-msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
+msgid ""
+"For very complex systems, you should see the <ulink url=\"&url-multidisk-"
+"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, "
+"mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:259
 #, no-c-format
-msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
+msgid ""
+"With respect to the issue of swap partition size, there are many views. One "
+"rule of thumb which works well is to use as much swap as you have system "
+"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, "
+"there are exceptions to these rules. If you are trying to solve 10000 "
+"simultaneous equations on a machine with 256MB of memory, you may need a "
+"gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:268
 #, no-c-format
-msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
+msgid ""
+"On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap "
+"partition is 2GB. That should be enough for nearly any installation. "
+"However, if your swap requirements are this high, you should probably try to "
+"spread the swap across different disks (also called <quote>spindles</quote>) "
+"and, if possible, different SCSI or IDE channels. The kernel will balance "
+"swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:278
 #, no-c-format
-msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
+msgid ""
+"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE "
+"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for "
+"another operating system on <filename>/dev/hda1</filename>, a 32MB swap "
+"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/"
+"dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:287
 #, no-c-format
-msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
+msgid ""
+"For an idea of the space taken by tasks you might be interested in adding "
+"after your system installation is complete, check <xref linkend=\"tasksel-"
+"size-list\"/>."
 msgstr ""
 
 #. Tag: title
@@ -376,7 +497,10 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:304
 #, no-c-format
-msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
+msgid ""
+"Linux disks and partition names may be different from other operating "
+"systems. You need to know the names that Linux uses when you create and "
+"mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
@@ -394,37 +518,51 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:322
 #, no-c-format
-msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
+msgid ""
+"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:328
 #, no-c-format
-msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
+msgid ""
+"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, "
+"and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:334
 #, no-c-format
-msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
+msgid ""
+"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as "
+"<filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:340
 #, no-c-format
-msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
+msgid ""
+"The master disk on IDE primary controller is named <filename>/dev/hda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:346
 #, no-c-format
-msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
+msgid ""
+"The slave disk on IDE primary controller is named <filename>/dev/hdb</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:352
 #, no-c-format
-msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
+msgid ""
+"The master and slave disks of the secondary controller can be called "
+"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, "
+"respectively. Newer IDE controllers can actually have two channels, "
+"effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
@@ -436,43 +574,74 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:369
 #, no-c-format
-msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
+msgid ""
+"The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:377
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>sda1</filename> and <filename>sda2</filename> "
+"represent the first and second partitions of the first SCSI disk drive in "
+"your system."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:384
 #, no-c-format
-msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
+msgid ""
+"Here is a real-life example. Let's assume you have a system with 2 SCSI "
+"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk "
+"(at address 2) is then named <filename>sda</filename>, and the second "
+"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 "
+"partitions on it, these will be named <filename>sda1</filename>, "
+"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies "
+"to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:395
 #, no-c-format
-msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
+msgid ""
+"Note that if you have two SCSI host bus adapters (i.e., controllers), the "
+"order of the drives can get confusing. The best solution in this case is to "
+"watch the boot messages, assuming you know the drive models and/or "
+"capacities."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:402
 #, no-c-format
-msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
+msgid ""
+"Linux represents the primary partitions as the drive name, plus the numbers "
+"1 through 4. For example, the first primary partition on the first IDE drive "
+"is <filename>/dev/hda1</filename>. The logical partitions are numbered "
+"starting at 5, so the first logical partition on that same drive is "
+"<filename>/dev/hda5</filename>. Remember that the extended partition, that "
+"is, the primary partition holding the logical partitions, is not usable by "
+"itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:413
 #, no-c-format
-msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
+msgid ""
+"Sun disk partitions allow for 8 separate partitions (or slices). The third "
+"partition is usually (and is preferred to have) the <quote>Whole Disk</"
+"quote> partition. This partition references all of the sectors of the disk, "
+"and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:420
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> "
+"represent the first and second partitions of the first DASD device in your "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -484,7 +653,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:436
 #, no-c-format
-msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
+msgid ""
+"Several varieties of partitioning programs have been adapted by &debian; "
+"developers to work on various types of hard disks and computer "
+"architectures. Following is a list of the program(s) applicable for your "
+"architecture."
 msgstr ""
 
 #. Tag: command
@@ -496,7 +669,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:449
 #, no-c-format
-msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
+msgid ""
+"Recommended partitioning tool in &debian;. This Swiss army knife can also "
+"resize partitions, create filesystems <phrase arch=\"any-x86\"> "
+"(<quote>format</quote> in Windows speak)</phrase> and assign them to the "
+"mountpoints."
 msgstr ""
 
 #. Tag: command
@@ -514,7 +691,12 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:465
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
+msgid ""
+"Be careful if you have existing FreeBSD partitions on your machine. The "
+"installation kernels include support for these partitions, but the way that "
+"<command>fdisk</command> represents them (or not) can make the device names "
+"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</"
+"ulink>."
 msgstr ""
 
 #. Tag: command
@@ -532,7 +714,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:482
 #, no-c-format
-msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
+msgid ""
+"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at "
+"all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
@@ -580,7 +764,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:519
 #, no-c-format
-msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
+msgid ""
+"PowerMac-aware version of <command>fdisk</command>, also used by BVM and "
+"Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
@@ -592,13 +778,21 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:529
 #, no-c-format
-msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
+msgid ""
+"&arch-title; version of <command>fdisk</command>; Please read the fdasd "
+"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/"
+"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and "
+"Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:540
 #, no-c-format
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
+msgid ""
+"One of these programs will be run by default when you select "
+"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible "
+"to use a different partitioning tool from the command line on VT2, but this "
+"is not recommended."
 msgstr ""
 
 #. Tag: para
@@ -610,11 +804,18 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:550
 #, no-c-format
-msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
+msgid ""
+"One key point when partitioning for Mac type disks is that the swap "
+"partition is identified by its name; it must be named <quote>swap</quote>. "
+"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. "
+"Please read the fine manual. We also suggest reading the <ulink url=\"&url-"
+"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you "
+"should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686
+#: partitioning.xml:800 partitioning.xml:877
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
@@ -622,61 +823,138 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:567
 #, no-c-format
-msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
+msgid ""
+"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> "
+"somewhere in the first 2GB. This is where the boot loader and an optional "
+"kernel and RAMdisk will be stored, so make it big enough for that &mdash; at "
+"least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware "
+"is that the Linux kernel must reside within the first 2GB of the disk. This "
+"is typically achieved by making the root ext2 partition fit entirely within "
+"the first 2GB of the disk. Alternatively you can create a small ext2 "
+"partition near the start of the disk and mount that on <filename>/boot</"
+"filename>, since that is the directory where the Linux kernel(s) will be "
+"stored. <filename>/boot</filename> needs to be big enough to hold whatever "
+"kernels (and backups) you might wish to load; 25&ndash;50MB is generally "
+"sufficient."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:591
 #, no-c-format
-msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
+msgid ""
+"If you have an existing other operating system such as DOS or Windows and "
+"you want to preserve that operating system while installing &debian;, you "
+"may need to resize its partition to free up space for the &debian; "
+"installation. The installer supports resizing of both FAT and NTFS "
+"filesystems; when you get to the installer's partitioning step, select the "
+"option <guimenuitem>Manual</guimenuitem> and then simply select an existing "
+"partition and change its size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:601
 #, no-c-format
-msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
+msgid ""
+"The PC BIOS generally adds additional constraints for disk partitioning. "
+"There is a limit to how many <quote>primary</quote> and <quote>logical</"
+"quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 "
+"BIOSes, there are limits to where on the drive the BIOS can boot from. More "
+"information can be found in the <ulink url=\"&url-partition-howto;\">Linux "
+"Partition HOWTO</ulink>, but this section will include a brief overview to "
+"help you plan most situations."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:611
 #, no-c-format
-msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
+msgid ""
+"<quote>Primary</quote> partitions are the original partitioning scheme for "
+"PC disks. However, there can only be four of them. To get past this "
+"limitation, <quote>extended</quote> and <quote>logical</quote> partitions "
+"were invented. By setting one of your primary partitions as an extended "
+"partition, you can subdivide all the space allocated to that partition into "
+"logical partitions. You can create up to 60 logical partitions per extended "
+"partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:622
 #, no-c-format
-msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
+msgid ""
+"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 "
+"usable primary partitions, 252 logical partitions), and 63 partitions on an "
+"IDE drive (3 usable primary partitions, 60 logical partitions). However the "
+"normal &debian-gnu; system provides only 20 devices for partitions, so you "
+"may not install on partitions higher than 20 unless you first manually "
+"create devices for those partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:632
 #, no-c-format
-msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
+msgid ""
+"If you have a large IDE disk, and are using neither LBA addressing, nor "
+"overlay drivers (sometimes provided by hard disk manufacturers), then the "
+"boot partition (the partition containing your kernel image) must be placed "
+"within the first 1024 cylinders of your hard drive (usually around 524 "
+"megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:640
 #, no-c-format
-msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
+msgid ""
+"This restriction doesn't apply if you have a BIOS newer than around "
+"1995&ndash;98 (depending on the manufacturer) that supports the "
+"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the "
+"Linux loader, and &debian;'s alternative <command>mbr</command> must use the "
+"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large "
+"disk access extensions are found to be present, they will be utilized. "
+"Otherwise, the legacy disk access interface is used as a fall-back, and it "
+"cannot be used to address any location on the disk higher than the 1023rd "
+"cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer "
+"has, these restrictions no longer apply, since &arch-kernel; does not use "
+"the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:654
 #, no-c-format
-msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
+msgid ""
+"If you have a large disk, you might have to use cylinder translation "
+"techniques, which you can set from your BIOS setup program, such as LBA "
+"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). "
+"More information about issues with large disks can be found in the <ulink "
+"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a "
+"cylinder translation scheme, and the BIOS does not support the large disk "
+"access extensions, then your boot partition has to fit within the "
+"<emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:666
 #, no-c-format
-msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
+msgid ""
+"The recommended way of accomplishing this is to create a small "
+"(25&ndash;50MB should suffice) partition at the beginning of the disk to be "
+"used as the boot partition, and then create whatever other partitions you "
+"wish to have, in the remaining area. This boot partition <emphasis>must</"
+"emphasis> be mounted on <filename>/boot</filename>, since that is the "
+"directory where the &arch-kernel; kernel(s) will be stored. This "
+"configuration will work on any system, regardless of whether LBA or large "
+"disk CHS translation is used, and regardless of whether your BIOS supports "
+"the large disk access extensions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:687
 #, no-c-format
-msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
+msgid ""
+"The <command>partman</command> disk partitioner is the default partitioning "
+"tool for the installer. It manages the set of partitions and their mount "
+"points to ensure that the disks and filesystems are properly configured for "
+"a successful installation. It actually uses <command>parted</command> to do "
+"the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
@@ -688,28 +966,52 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:700
 #, no-c-format
-msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+msgid ""
+"The IA-64 EFI firmware supports two partition table (or disk label) formats, "
+"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer "
+"recommended for IA-64 systems. Although the installer also provides "
+"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> "
+"<command>parted</command></ulink> because only it can manage both GPT and MS-"
+"DOS tables correctly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:712
 #, no-c-format
-msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
+msgid ""
+"The automatic partitioning recipes for <command>partman</command> allocate "
+"an EFI partition as the first partition on the disk. You can also set up the "
+"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the "
+"main menu in a manner similar to setting up a <emphasis>swap</emphasis> "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:720
 #, no-c-format
 msgid ""
-      "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
-      "      mklabel gpt\n"
-      "      mkpartfs primary fat 0 50\n"
-      "      mkpartfs primary linux-swap 51 1000\n"
-      "      mkpartfs primary ext2 1001 3000\n"
-      "      set 1 boot on\n"
-      "      print\n"
-      "      quit\n"
-      "</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks."
+"The <command>partman</command> partitioner will handle most disk layouts. "
+"For those rare cases where it is necessary to manually set up a disk, you "
+"can use the shell as described above and run the <command>parted</command> "
+"utility directly using its command line interface. Assuming that you want to "
+"erase your whole disk and create a GPT table and some partitions, then "
+"something similar to the following command sequence could be used: "
+"<informalexample><screen>\n"
+"      mklabel gpt\n"
+"      mkpartfs primary fat 0 50\n"
+"      mkpartfs primary linux-swap 51 1000\n"
+"      mkpartfs primary ext2 1001 3000\n"
+"      set 1 boot on\n"
+"      print\n"
+"      quit\n"
+"</screen></informalexample> This creates a new partition table, and three "
+"partitions to be used as an EFI boot partition, swap space, and a root file "
+"system. Finally it sets the boot flag on the EFI partition. Partitions are "
+"specified in Megabytes, with start and end offsets from the beginning of the "
+"disk. So, for example, above we created a 1999MB ext2 file system starting "
+"at offset 1001MB from the start of the disk. Note that formatting swap space "
+"with <command>parted</command> can take a few minutes to complete, as it "
+"scans the partition for bad blocks."
 msgstr ""
 
 #. Tag: title
@@ -721,19 +1023,36 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:746
 #, no-c-format
-msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
+msgid ""
+"ELILO, the IA-64 boot loader, requires a partition containing a FAT file "
+"system with the <userinput>boot</userinput> flag set. The partition must be "
+"big enough to hold the boot loader and any kernels or RAMdisks you may wish "
+"to boot. A minimum size would be about 20MB, but if you expect to run with "
+"multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:755
 #, no-c-format
-msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
+msgid ""
+"The EFI Boot Manager and the EFI Shell fully support the GPT table so the "
+"boot partition does not necessarily have to be the first partition or even "
+"on the same disk. This is convenient if you should forget to allocate the "
+"partition and only find out after you have formatted the other partitions on "
+"your disk(s). The <command>partman</command> partitioner checks for an EFI "
+"partition at the same time it checks for a properly set up <emphasis>root</"
+"emphasis> partition. This gives you an opportunity to correct the disk "
+"layout before the package install begins. The easiest way to correct this "
+"omission is to shrink the last partition of the disk to make enough free "
+"space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:770
 #, no-c-format
-msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
+msgid ""
+"It is strongly recommended that you allocate the EFI boot partition on the "
+"same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -745,13 +1064,27 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:779
 #, no-c-format
-msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
+msgid ""
+"The EFI firmware is significantly more sophisticated than the usual BIOS "
+"seen on most x86 PCs. Some system vendors take advantage of the ability of "
+"the EFI to access files and run programs from a hard disk filesystem to "
+"store diagnostics and EFI based system management utilities on the hard "
+"disk. This is a separate FAT format filesystem on the system disk. Consult "
+"the system documentation and accessories that come with the system for "
+"details. The easiest time to set up a diagnostics partition is at the same "
+"time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:801
 #, no-c-format
-msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
+msgid ""
+"SGI machines require an SGI disk label in order to make the system bootable "
+"from hard disk. It can be created in the fdisk expert menu. The thereby "
+"created volume header (partition number 9) should be at least 3MB large. If "
+"the volume header created is too small, you can simply delete partition "
+"number 9 and re-add it with a different size. Note that the volume header "
+"must start at sector 0."
 msgstr ""
 
 #. Tag: title
@@ -763,48 +1096,94 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:819
 #, no-c-format
-msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
+msgid ""
+"If you are installing onto a NewWorld PowerMac you must create a special "
+"bootstrap partition to hold the boot loader. The size of this partition must "
+"have at least 819200 bytes and its partition type must be "
+"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not "
+"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine "
+"cannot be made bootable from the hard disk. This partition can easily be "
+"created by creating a new partition in <command>partman</command> and "
+"telling it to use it as a <quote>NewWorld boot partition</quote>, or in "
+"<command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:832
 #, no-c-format
-msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
+msgid ""
+"The special partition type Apple_Bootstrap is required to prevent MacOS from "
+"mounting and damaging the bootstrap partition, as there are special "
+"modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:839
 #, no-c-format
-msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
+msgid ""
+"Note that the bootstrap partition is only meant to hold 3 very small files: "
+"the <command>yaboot</command> binary, its configuration <filename>yaboot."
+"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</"
+"command>. It need not and must not be mounted on your file system nor have "
+"kernels or anything else copied to it. The <command>ybin</command> and "
+"<command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:849
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
+msgid ""
+"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap "
+"partition should appear before other boot partitions on the disk, especially "
+"MacOS boot partitions. The bootstrap partition should be the first one you "
+"create. However, if you add a bootstrap partition later, you can use "
+"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder "
+"the partition map so the bootstrap partition comes right after the map "
+"(which is always partition 1). It's the logical map order, not the physical "
+"address order, that counts."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:861
 #, no-c-format
-msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
+msgid ""
+"Apple disks normally have several small driver partitions. If you intend to "
+"dual boot your machine with MacOSX, you should retain these partitions and a "
+"small HFS partition (800k is the minimum size). That is because MacOSX, on "
+"every boot, offers to initialize any disks which do not have active MacOS "
+"partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:878
 #, no-c-format
-msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
+msgid ""
+"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This "
+"is the only kind of partition scheme that the OpenBoot PROM understands, and "
+"so it's the only scheme from which you can boot. The <keycap>s</keycap> key "
+"is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:886
 #, no-c-format
-msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
+msgid ""
+"Furthermore, on &arch-title; disks, make sure your first partition on your "
+"boot disk starts at cylinder 0. While this is required, it also means that "
+"the first partition will contain the partition table and the boot block, "
+"which are the first two sectors of the disk. You must <emphasis>not</"
+"emphasis> put swap on the first partition of the boot drive, since swap "
+"partitions do not preserve the first few sectors of the partition. You can "
+"put Ext2 or UFS partitions there; these will leave the partition table and "
+"the boot block alone."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:897
 #, no-c-format
-msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
+msgid ""
+"It is also advised that the third partition should be of type <quote>Whole "
+"disk</quote> (type 5), and contain the entire disk (from the first cylinder "
+"to the last). This is simply a convention of Sun disk labels, and helps the "
+"<command>SILO</command> boot loader keep its bearings."
 msgstr ""
-
diff --git a/po/da/post-install.po b/po/da/post-install.po
index 8367ac28c..e22aac91d 100644
--- a/po/da/post-install.po
+++ b/po/da/post-install.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,27 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:15
 #, no-c-format
-msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system."
+msgid ""
+"To shut down a running &debian-gnu; system, you must not reboot with the "
+"reset switch on the front or back of your computer, or just turn off the "
+"computer. &debian-gnu; should be shut down in a controlled manner, otherwise "
+"files might get lost and/or disk damage might occur. If you run a desktop "
+"environment, there is usually an option to <quote>log out</quote> available "
+"from the application menu that allows you to shutdown (or reboot) the system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:25
 #, no-c-format
-msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system."
+msgid ""
+"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</"
+"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch="
+"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> "
+"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last "
+"option is to log in as root and type one of the commands <command>poweroff</"
+"command>, <command>halt</command> or <command>shutdown -h now</command> if "
+"either of the key combinations do not work or you prefer to type commands; "
+"use <command>reboot</command> to reboot the system."
 msgstr ""
 
 #. Tag: title
@@ -46,13 +61,26 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:47
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:55
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as &debian; packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as &debian; "
+"packages."
 msgstr ""
 
 #. Tag: title
@@ -64,7 +92,13 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:77
 #, no-c-format
-msgid "&debian; is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about &debian; to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use &debian;, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"&debian; is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about &debian; to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use &debian;, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -76,13 +110,32 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:89
 #, no-c-format
-msgid "The most important concept to grasp is the &debian; packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the &debian; packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:130
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
@@ -94,7 +147,12 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:142
 #, no-c-format
-msgid "There are official and unofficial software repositories that are not enabled in the default &debian; install. These contain software which many find important and expect to have. Information on these additional repositories can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-software;\">The Software Available for &debian;'s Stable Release</ulink>."
+msgid ""
+"There are official and unofficial software repositories that are not enabled "
+"in the default &debian; install. These contain software which many find "
+"important and expect to have. Information on these additional repositories "
+"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-"
+"software;\">The Software Available for &debian;'s Stable Release</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,7 +164,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:155
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
@@ -118,19 +179,34 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:166
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:175
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user account under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:184
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -142,25 +218,50 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:200
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:206
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about &debian;-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about &debian;-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:217
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about &debian;. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more &debian; documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The &debian; community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on &debian;."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about &debian;. In particular, see the "
+"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> "
+"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference"
+"\">Debian Reference</ulink>. An index of more &debian; documentation is "
+"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian "
+"Documentation Project</ulink>. The &debian; community is self-supporting; to "
+"subscribe to one or more of the Debian mailing lists, see the <ulink url="
+"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</"
+"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/"
+"\">Debian Mailing List Archives</ulink> contain a wealth of information on "
+"&debian;."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:235
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
@@ -172,31 +273,59 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:252
 #, no-c-format
-msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some &debian; utilities, we will try to cover the basics in this section."
+msgid ""
+"Today, email is an important part of many people's life. As there are many "
+"options as to how to set it up, and as having it set up correctly is "
+"important for some &debian; utilities, we will try to cover the basics in "
+"this section."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:259
 #, no-c-format
-msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox."
+msgid ""
+"There are three main functions that make up an e-mail system. First there is "
+"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user "
+"actually uses to compose and read mails. Then there is the <firstterm>Mail "
+"Transfer Agent</firstterm> (MTA) that takes care of transferring messages "
+"from one computer to another. And last there is the <firstterm>Mail Delivery "
+"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the "
+"user's inbox."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:269
 #, no-c-format
-msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail."
+msgid ""
+"These three functions can be performed by separate programs, but they can "
+"also be combined in one or two programs. It is also possible to have "
+"different programs handle these functions for different types of mail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:275
 #, no-c-format
-msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA."
+msgid ""
+"On Linux and Unix systems <command>mutt</command> is historically a very "
+"popular MUA. Like most traditional Linux programs it is text based. It is "
+"often used in combination with <command>exim</command> or <command>sendmail</"
+"command> as MTA and <command>procmail</command> as MDA."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:282
 #, no-c-format
-msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in &debian; available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in &debian; has to do with licensing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can &mdash; and often are &mdash; also be used in combination with the traditional Linux tools."
+msgid ""
+"With the increasing popularity of graphical desktop systems, the use of "
+"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's "
+"<command>kmail</command> or Mozilla's <command>thunderbird</command> (in "
+"&debian; available as <command>icedove</command><footnote> <para> The reason "
+"that <command>thunderbird</command> has been renamed to <command>icedove</"
+"command> in &debian; has to do with licensing issues. Details are outside "
+"the scope of this manual. </para> </footnote>) is becoming more popular. "
+"These programs combine the function of a MUA, MTA and MDA, but can &mdash; "
+"and often are &mdash; also be used in combination with the traditional Linux "
+"tools."
 msgstr ""
 
 #. Tag: title
@@ -208,19 +337,40 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:303
 #, no-c-format
-msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, &hellip; </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes."
+msgid ""
+"Even if you are planning to use a graphical mail program, it is important "
+"that a traditional MTA/MDA is also installed and correctly set up on your "
+"&debian-gnu; system. Reason is that various utilities running on the "
+"system<footnote> <para> Examples are: <command>cron</command>, "
+"<command>quota</command>, <command>logcheck</command>, <command>aide</"
+"command>, &hellip; </para> </footnote> can send important notices by e-mail "
+"to inform the system administrator of (potential) problems or changes."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:318
 #, no-c-format
-msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>."
+msgid ""
+"For this reason the packages <classname>exim4</classname> and "
+"<classname>mutt</classname> will be installed by default (provided you did "
+"not unselect the <quote>standard</quote> task during the installation). "
+"<classname>exim4</classname> is a combination MTA/MDA that is relatively "
+"small but very flexible. By default it will be configured to only handle e-"
+"mail local to the system itself and e-mails addressed to the system "
+"administrator (root account) will be delivered to the regular user account "
+"created during the installation<footnote> <para> The forwarding of mail for "
+"root to the regular user account is configured in <filename>/etc/aliases</"
+"filename>. If no regular user account was created, the mail will of course "
+"be delivered to the root account itself. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:337
 #, no-c-format
-msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>."
+msgid ""
+"When system e-mails are delivered they are added to a file in <filename>/var/"
+"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be "
+"read using <command>mutt</command>."
 msgstr ""
 
 #. Tag: title
@@ -232,31 +382,51 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:348
 #, no-c-format
-msgid "As mentioned earlier, the installed &debian; system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others."
+msgid ""
+"As mentioned earlier, the installed &debian; system is only set up to handle "
+"e-mail local to the system, not for sending mail to others nor for receiving "
+"mail from others."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:354
 #, no-c-format
-msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly."
+msgid ""
+"If you would like <classname>exim4</classname> to handle external e-mail, "
+"please refer to the next subsection for the basic available configuration "
+"options. Make sure to test that mail can be sent and received correctly."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:360
 #, no-c-format
-msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)."
+msgid ""
+"If you intend to use a graphical mail program and use a mail server of your "
+"Internet Service Provider (ISP) or your company, there is not really any "
+"need to configure <classname>exim4</classname> for handling external e-mail. "
+"Just configure your favorite graphical mail program to use the correct "
+"servers to send and receive e-mail (how is outside the scope of this manual)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:369
 #, no-c-format
-msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against &debian; packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports."
+msgid ""
+"However, in that case you may need to configure individual utilities to "
+"correctly send e-mails. One such utility is <command>reportbug</command>, a "
+"program that facilitates submitting bug reports against &debian; packages. "
+"By default it expects to be able to use <classname>exim4</classname> to "
+"submit bug reports."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:377
 #, no-c-format
-msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports."
+msgid ""
+"To correctly set up <command>reportbug</command> to use an external mail "
+"server, please run the command <command>reportbug --configure</command> and "
+"answer <quote>no</quote> to the question if an MTA is available. You will "
+"then be asked for the SMTP server to be used for submitting bug reports."
 msgstr ""
 
 #. Tag: title
@@ -268,7 +438,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:389
 #, no-c-format
-msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:"
+msgid ""
+"If you would like your system to also handle external e-mail, you will need "
+"to reconfigure the <classname>exim4</classname> package<footnote> <para> You "
+"can of course also remove <classname>exim4</classname> and replace it with "
+"an alternative MTA/MDA. </para> </footnote>:"
 msgstr ""
 
 #. Tag: screen
@@ -280,13 +454,18 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:403
 #, no-c-format
-msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option."
+msgid ""
+"After entering that command (as root), you will be asked if you want split "
+"the configuration into small files. If you are unsure, select the default "
+"option."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:409
 #, no-c-format
-msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs."
+msgid ""
+"Next you will be presented with several common mail scenarios. Choose the "
+"one that most closely resembles your needs."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +477,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:419
 #, no-c-format
-msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
+msgid ""
+"Your system is connected to a network and your mail is sent and received "
+"directly using SMTP. On the following screens you will be asked a few basic "
+"questions, like your machine's mail name, or a list of domains for which you "
+"accept or relay mail."
 msgstr ""
 
 #. Tag: term
@@ -310,13 +493,22 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:431
 #, no-c-format
-msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which takes care of sending the message on to its destination. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail."
+msgid ""
+"In this scenario your outgoing mail is forwarded to another machine, called "
+"a <quote>smarthost</quote>, which takes care of sending the message on to "
+"its destination. The smarthost also usually stores incoming mail addressed "
+"to your computer, so you don't need to be permanently online. That also "
+"means you have to download your mail from the smarthost via programs like "
+"fetchmail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:441
 #, no-c-format
-msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network."
+msgid ""
+"In a lot of cases the smarthost will be your ISP's mail server, which makes "
+"this option very suitable for dial-up users. It can also be a company mail "
+"server, or even another system on your own network."
 msgstr ""
 
 #. Tag: term
@@ -328,7 +520,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:452
 #, no-c-format
-msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled."
+msgid ""
+"This option is basically the same as the previous one except that the system "
+"will not be set up to handle mail for a local e-mail domain. Mail on the "
+"system itself (e.g. for the system administrator) will still be handled."
 msgstr ""
 
 #. Tag: term
@@ -352,19 +547,37 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:473
 #, no-c-format
-msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
+msgid ""
+"Choose this if you are absolutely convinced you know what you are doing. "
+"This will leave you with an unconfigured mail system &mdash; until you "
+"configure it, you won't be able to send or receive any mail and you may miss "
+"some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:484
 #, no-c-format
-msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has further details about configuring <classname>exim4</classname> and explains where to find additional documentation."
+msgid ""
+"If none of these scenarios suits your needs, or if you need a finer grained "
+"setup, you will need to edit configuration files under the <filename>/etc/"
+"exim4</filename> directory after the installation is complete. More "
+"information about <classname>exim4</classname> may be found under <filename>/"
+"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</"
+"filename> has further details about configuring <classname>exim4</classname> "
+"and explains where to find additional documentation."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:495
 #, no-c-format
-msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>."
+msgid ""
+"Note that sending mail directly to the Internet when you don't have an "
+"official domain name, can result in your mail being rejected because of anti-"
+"spam measures on receiving servers. Using your ISP's mail server is "
+"preferred. If you still do want to send out mail directly, you may want to "
+"use a different e-mail address than is generated by default. If you use "
+"<classname>exim4</classname> as your MTA, this is possible by adding an "
+"entry in <filename>/etc/email-addresses</filename>."
 msgstr ""
 
 #. Tag: title
@@ -376,19 +589,29 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:514
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with &debian; handles most configurations. Also, &debian; often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with &debian; handles most configurations. "
+"Also, &debian; often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:524
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:530
 #, no-c-format
-msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
@@ -430,67 +653,135 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:565
 #, no-c-format
-msgid "To compile a kernel the &debian; way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the &debian; way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<classname>linux-source-2.6</classname> and a few others which are probably "
+"already installed (see <filename>/usr/share/doc/kernel-package/README.gz</"
+"filename> for the complete list)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:574
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:582
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>&debian; way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>&debian; way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <classname>linux-source-2.6</"
+"classname>, yet still use the <classname>kernel-package</classname> "
+"compilation method."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:591
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:598
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/"
+"linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory "
+"<filename>linux-source-&kernelversion;</filename> that will have been "
+"created."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:618
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your &debian; installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your &debian; installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:633
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:638
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --"
+"revision=custom.1.0 kernel_image</userinput>. The version number of "
+"<quote>1.0</quote> can be changed at will; this is just a version number "
+"that you will use to track your kernel builds. Likewise, you can put any "
+"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel "
+"compilation may take quite a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:648
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well."
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../&kernelpackage;-"
+"&kernelversion;-<replaceable>subarchitecture</"
+"replaceable>_custom.1.0_&architecture;.deb</userinput>. The "
+"<replaceable>subarchitecture</replaceable> part is an optional sub-"
+"architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> "
+"depending on what kernel options you set. <userinput>dpkg -i</userinput> "
+"will install the kernel, along with some other nice supporting files. For "
+"instance, the <filename>System.map</filename> will be properly installed "
+"(helpful for debugging kernel problems), and <filename>/boot/config-"
+"&kernelversion;</filename> will be installed, containing your current "
+"configuration set. Your new kernel package is also clever enough to "
+"automatically update your boot loader to use the new kernel. If you have "
+"created a modules package, you'll need to install that package as well."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:668
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:673
 #, no-c-format
-msgid "For more information on &debian; kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"For more information on &debian; kernels and kernel compilation, see the "
+"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. "
+"For more information on <classname>kernel-package</classname>, read the fine "
+"documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
@@ -502,31 +793,63 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:690
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:700
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:715
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:723
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:735
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
@@ -538,6 +861,8 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:748
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/da/preparing.po b/po/da/preparing.po
index 9378d6304..86a142b74 100644
--- a/po/da/preparing.po
+++ b/po/da/preparing.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:6
 #, no-c-format
-msgid "This chapter deals with the preparation for installing &debian; before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information."
+msgid ""
+"This chapter deals with the preparation for installing &debian; before you "
+"even boot the installer. This includes backing up your data, gathering "
+"information about your hardware, and locating any necessary information."
 msgstr ""
 
 #. Tag: title
@@ -34,37 +38,59 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:20
 #, no-c-format
-msgid "First, just a note about re-installations. With &debian;, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case."
+msgid ""
+"First, just a note about re-installations. With &debian;, a circumstance "
+"that will require a complete re-installation of your system is very rare; "
+"perhaps mechanical failure of the hard disk would be the most common case."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:27
 #, no-c-format
-msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS."
+msgid ""
+"Many common operating systems may require a complete installation to be "
+"performed when critical failures take place or for upgrades to new OS "
+"versions. Even if a completely new installation isn't required, often the "
+"programs you use must be re-installed to operate properly in the new OS."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:35
 #, no-c-format
-msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the &debian; packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system."
+msgid ""
+"Under &debian-gnu;, it is much more likely that your OS can be repaired "
+"rather than replaced if things go wrong. Upgrades never require a wholesale "
+"installation; you can always upgrade in-place. And the programs are almost "
+"always compatible with successive OS releases. If a new program version "
+"requires newer supporting software, the &debian; packaging system ensures "
+"that all the necessary software is automatically identified and installed. "
+"The point is, much effort has been put into avoiding the need for re-"
+"installation, so think of it as your very last option. The installer is "
+"<emphasis>not</emphasis> designed to re-install over an existing system."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:48
 #, no-c-format
-msgid "Here's a road map for the steps you will take during the installation process."
+msgid ""
+"Here's a road map for the steps you will take during the installation "
+"process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:56
 #, no-c-format
-msgid "Back up any existing data or documents on the hard disk where you plan to install."
+msgid ""
+"Back up any existing data or documents on the hard disk where you plan to "
+"install."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:62
 #, no-c-format
-msgid "Gather information about your computer and any needed documentation, before starting the installation."
+msgid ""
+"Gather information about your computer and any needed documentation, before "
+"starting the installation."
 msgstr ""
 
 #. Tag: para
@@ -76,13 +102,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-msgid "Locate and/or download the installer software and any specialized driver or firmware files your machine requires."
+msgid ""
+"Locate and/or download the installer software and any specialized driver or "
+"firmware files your machine requires."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:79
 #, no-c-format
-msgid "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot infrastructure from which the installer can be booted."
+msgid ""
+"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
+"infrastructure from which the installer can be booted."
 msgstr ""
 
 #. Tag: para
@@ -124,7 +154,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:117
 #, no-c-format
-msgid "If necessary, resize existing partitions on your target harddisk to make space for the installation."
+msgid ""
+"If necessary, resize existing partitions on your target harddisk to make "
+"space for the installation."
 msgstr ""
 
 #. Tag: para
@@ -136,13 +168,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:127
 #, no-c-format
-msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>."
+msgid ""
+"Watch the automatic download/install/setup of the <firstterm>base system</"
+"firstterm>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:133
 #, no-c-format
-msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system."
+msgid ""
+"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
+"and/or your existing system."
 msgstr ""
 
 #. Tag: para
@@ -154,37 +190,68 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
+"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
+"of the installation system. For more information about this graphical "
+"installer, see <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:154
 #, no-c-format
-msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
+msgid ""
+"If you have problems during the installation, it helps to know which "
+"packages are involved in which steps. Introducing the leading software "
+"actors in this installation drama:"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:160
 #, no-c-format
-msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
+msgid ""
+"The installer software, <classname>debian-installer</classname>, is the "
+"primary concern of this manual. It detects hardware and loads appropriate "
+"drivers, uses <classname>dhcp-client</classname> to set up the network "
+"connection, runs <classname>debootstrap</classname> to install the base "
+"system packages, and runs <classname>tasksel</classname> to allow you to "
+"install certain additional software. Many more actors play smaller parts in "
+"this process, but <classname>debian-installer</classname> has completed its "
+"task when you load the new system for the first time."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:172
 #, no-c-format
-msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
+msgid ""
+"To tune the system to your needs, <classname>tasksel</classname> allows you "
+"to choose to install various predefined bundles of software like a Web "
+"server or a Desktop environment."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because in relation to a text-mode-only system it requires a comparatively large amount of disk space and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid ""
+"One important option during the installation is whether or not to install a "
+"graphical desktop environment, consisting of the X Window System and one of "
+"the available graphical desktop environments. If you choose not to select "
+"the <quote>Desktop environment</quote> task, you will only have a relatively "
+"basic, command line driven system. Installing the Desktop environment task "
+"is optional because in relation to a text-mode-only system it requires a "
+"comparatively large amount of disk space and because many &debian-gnu; "
+"systems are servers which don't really have any need for a graphical user "
+"interface to do their job."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Troubleshooting of the X Window System is not within the scope of this manual."
+msgid ""
+"Just be aware that the X Window System is completely separate from "
+"<classname>debian-installer</classname>, and in fact is much more "
+"complicated. Troubleshooting of the X Window System is not within the scope "
+"of this manual."
 msgstr ""
 
 #. Tag: title
@@ -196,13 +263,29 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system is going to be installed on your computer, it is quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in the installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
+msgid ""
+"Before you start, make sure to back up every file that is now on your "
+"system. If this is the first time a non-native operating system is going to "
+"be installed on your computer, it is quite likely you will need to re-"
+"partition your disk to make room for &debian-gnu;. Anytime you partition "
+"your disk, you run a risk of losing everything on the disk, no matter what "
+"program you use to do it. The programs used in the installation are quite "
+"reliable and most have seen years of use; but they are also quite powerful "
+"and a false move can cost you. Even after backing up, be careful and think "
+"about your answers and actions. Two minutes of thinking can save hours of "
+"unnecessary work."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Even though this is normally not necessary, there might be situations in which you could be required to reinstall your operating system's boot loader to make the system boot or in a worst case even have to reinstall the complete operating system and restore your previously made backup."
+msgid ""
+"If you are creating a multi-boot system, make sure that you have the "
+"distribution media of any other present operating systems on hand. Even "
+"though this is normally not necessary, there might be situations in which "
+"you could be required to reinstall your operating system's boot loader to "
+"make the system boot or in a worst case even have to reinstall the complete "
+"operating system and restore your previously made backup."
 msgstr ""
 
 #. Tag: title
@@ -238,13 +321,20 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:259
 #, no-c-format
-msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of &debian;; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is the official version of the "
+"Installation Guide for the &releasename; release of &debian;; available in "
+"<ulink url=\"&url-release-area;/installmanual\">various formats and "
+"translations</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:268
 #, no-c-format
-msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of &debian;; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is a development version of the "
+"Installation Guide for the next release of &debian;; available in <ulink url="
+"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -256,7 +346,8 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:281
 #, no-c-format
-msgid "Often contains useful information on configuring or using your hardware."
+msgid ""
+"Often contains useful information on configuring or using your hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -286,7 +377,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:314
 #, no-c-format
-msgid "Documentation of &arch-title;-specific boot sequence, commands and device drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
+msgid ""
+"Documentation of &arch-title;-specific boot sequence, commands and device "
+"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
 msgstr ""
 
 #. Tag: ulink
@@ -298,7 +391,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:330
 #, no-c-format
-msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
+msgid ""
+"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
+"&arch-title; hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -310,7 +405,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:346
 #, no-c-format
-msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about &debian; but the basic installation concepts are the same across all &arch-title; distributions."
+msgid ""
+"IBM Redbook describing the Linux distributions available for the mainframe. "
+"It has no chapter about &debian; but the basic installation concepts are the "
+"same across all &arch-title; distributions."
 msgstr ""
 
 #. Tag: ulink
@@ -328,7 +426,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:368
 #, no-c-format
-msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
+msgid ""
+"In many cases, the installer will be able to automatically detect your "
+"hardware. But to be prepared, we do recommend familiarizing yourself with "
+"your hardware before the install."
 msgstr ""
 
 #. Tag: para
@@ -346,7 +447,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys or key combinations. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
+msgid ""
+"The BIOS setup screens of your computer. You can view these screens when you "
+"start your computer by pressing a combination of keys. Check your manual for "
+"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
+"keycap> key, but some manufacturers use other keys or key combinations. "
+"Usually upon starting the computer there will be a message stating which key "
+"to press to enter the setup screen."
 msgstr ""
 
 #. Tag: para
@@ -364,13 +471,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:408
 #, no-c-format
-msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
+msgid ""
+"System commands or tools in another operating system, including file manager "
+"displays. This source is especially useful for information about RAM and "
+"hard drive memory."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:415
 #, no-c-format
-msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
+msgid ""
+"Your system administrator or Internet Service Provider. These sources can "
+"tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
 #. Tag: title
@@ -514,61 +626,115 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-msgid "Many products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems."
+msgid ""
+"Many products work without trouble on &arch-kernel;. Moreover, hardware "
+"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
+"does not run as many different types of hardware as some operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:516
 #, no-c-format
-msgid "Drivers in &arch-kernel; in most cases are not written for a certain <quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names."
+msgid ""
+"Drivers in &arch-kernel; in most cases are not written for a certain "
+"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
+"but for a certain hardware/chipset. Many seemingly different products/brands "
+"are based on the same hardware design; it is not uncommon that chip "
+"manufacturers provide so-called <quote>reference designs</quote> for "
+"products based on their chips which are then used by several different "
+"device manufacturers and sold under lots of different product or brand names."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:527
 #, no-c-format
-msgid "This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them."
+msgid ""
+"This has advantages and disadvantages. An advantage is that a driver for one "
+"chipset works with lots of different products from different manufacturers, "
+"as long as their product is based on the same chipset. The disadvantage is "
+"that it is not always easy to see which actual chipset is used in a certain "
+"product/brand. Unfortunately sometimes device manufacturers change the "
+"hardware base of their product without changing the product name or at least "
+"the product version number, so that when having two items of the same brand/"
+"product name bought at different times, they can sometimes be based on two "
+"different chipsets and therefore use two different drivers or there might be "
+"no driver at all for one of them."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:540
 #, no-c-format
-msgid "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and <quote>product</quote> IDs, and the combination of these two is usually the same for any product based on the same chipset."
+msgid ""
+"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
+"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
+"Express/ExpressCard devices have so called <quote>vendor</quote> and "
+"<quote>product</quote> IDs, and the combination of these two is usually the "
+"same for any product based on the same chipset."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:548
 #, no-c-format
-msgid "On Linux systems, these IDs can be read with the <command>lsusb</command> command for USB devices and with the <command>lspci -nn</command> command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as <quote>1d6b:0001</quote>."
+msgid ""
+"On Linux systems, these IDs can be read with the <command>lsusb</command> "
+"command for USB devices and with the <command>lspci -nn</command> command "
+"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
+"usually given in the form of two hexadecimal numbers, seperated by a colon, "
+"such as <quote>1d6b:0001</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:556
 #, no-c-format
-msgid "An example for the output of <command>lsusb</command>: <quote>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the vendor ID and 0002 is the product ID."
+msgid ""
+"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
+"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
+"vendor ID and 0002 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:562
 #, no-c-format
-msgid "An example for the output of <command>lspci -nn</command> for an Ethernet card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID."
+msgid ""
+"An example for the output of <command>lspci -nn</command> for an Ethernet "
+"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
+"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
+"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
+"here 10ec is the vendor- and 8168 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:570
 #, no-c-format
-msgid "As another example, a graphics card could give the following output: <quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
+msgid ""
+"As another example, a graphics card could give the following output: "
+"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
+"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:576
 #, no-c-format
-msgid "On Windows systems, the IDs for a device can be found in the Windows device manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the device manager's details tab to actually see the IDs, as they are not displayed by default."
+msgid ""
+"On Windows systems, the IDs for a device can be found in the Windows device "
+"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
+"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
+"you have to select the property <quote>Hardware IDs</quote> in the device "
+"manager's details tab to actually see the IDs, as they are not displayed by "
+"default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:586
 #, no-c-format
-msgid "Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and <quote>driver</quote> as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the graphics card example), can help."
+msgid ""
+"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
+"quote> and <quote>driver</quote> as the search terms often results in "
+"information regarding the driver support status for a certain chipset. If a "
+"search for the vendor/product ID does not yield usable results, a search for "
+"the chip code names, which are also often provided by lsusb and lspci "
+"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
+"and <quote>RV710</quote> in the graphics card example), can help."
 msgstr ""
 
 #. Tag: title
@@ -580,19 +746,42 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:601
 #, no-c-format
-msgid "&debian-gnu; is also available as a so-called <quote>live system</quote> for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by &debian-gnu;, the easiest way is to run a &debian; live system on it and try it out."
+msgid ""
+"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
+"certain architectures. A live system is a preconfigured ready-to-use system "
+"in a compressed format that can be booted and used from a read-only medium "
+"like a CD or DVD. Using it by default does not create any permanent changes "
+"on your computer. You can change user settings and install additional "
+"programs from within the live system, but all this only happens in the "
+"computer's RAM, i.e. if you turn off the computer and boot the live system "
+"again, everything is reset to its defaults. If you want to see whether your "
+"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
+"live system on it and try it out."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:614
 #, no-c-format
-msgid "There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official &debian-gnu; live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the &d-i;, so installation of non-free components must be done manually if needed."
+msgid ""
+"There are a few limitations in using a live system. The first is that as all "
+"changes you do within the live system must be held in your computer's RAM, "
+"this only works on systems with enough RAM to do that, so installing "
+"additional large software packages may fail due to memory constraints. "
+"Another limitation with regards to hardware compatibility testing is that "
+"the official &debian-gnu; live system contains only free components, i.e. "
+"there are no non-free firmware files included in it. Such non-free packages "
+"can of course be installed manually within the system, but there is no "
+"automatic detection of required firmware files like in the &d-i;, so "
+"installation of non-free components must be done manually if needed."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:627
 #, no-c-format
-msgid "Information about the available variants of the &debian; live images can be found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</ulink>."
+msgid ""
+"Information about the available variants of the &debian; live images can be "
+"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
+"ulink>."
 msgstr ""
 
 #. Tag: title
@@ -604,7 +793,11 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-msgid "If your computer is connected to a fixed network (i.e. an Ethernet or equivalent connection &mdash; not a dialup/PPP connection) which is administered by somebody else, you should ask your network's system administrator for this information:"
+msgid ""
+"If your computer is connected to a fixed network (i.e. an Ethernet or "
+"equivalent connection &mdash; not a dialup/PPP connection) which is "
+"administered by somebody else, you should ask your network's system "
+"administrator for this information:"
 msgstr ""
 
 #. Tag: para
@@ -634,31 +827,47 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:671
 #, no-c-format
-msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
+msgid ""
+"The IP address of the default gateway system you should route to, if your "
+"network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:677
 #, no-c-format
-msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
+msgid ""
+"The system on your network that you should use as a DNS (Domain Name "
+"Service) server."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-msgid "If the network you are connected to uses DHCP (Dynamic Host Configuration Protocol) for configuring network settings, you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
+msgid ""
+"If the network you are connected to uses DHCP (Dynamic Host Configuration "
+"Protocol) for configuring network settings, you don't need this information "
+"because the DHCP server will provide it directly to your computer during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:692
 #, no-c-format
-msgid "If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default."
+msgid ""
+"If you have internet access via DSL or cable modem (i.e. over a cable tv "
+"network) and have a router (often provided preconfigured by your phone or "
+"catv provider) which handles your network connectivity, DHCP is usually "
+"available by default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:700
 #, no-c-format
-msgid "As a rule of thumb: if you run a Windows system in your home network and did not have to manually perform any network settings there to achieve Internet access, network connectivity in &debian-gnu; will also be configured automatically."
+msgid ""
+"As a rule of thumb: if you run a Windows system in your home network and did "
+"not have to manually perform any network settings there to achieve Internet "
+"access, network connectivity in &debian-gnu; will also be configured "
+"automatically."
 msgstr ""
 
 #. Tag: para
@@ -688,19 +897,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:735
 #, no-c-format
-msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
+msgid ""
+"Once you have gathered information about your computer's hardware, check "
+"that your hardware will let you do the type of installation that you want to "
+"do."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:741
 #, no-c-format
-msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
+msgid ""
+"Depending on your needs, you might manage with less than some of the "
+"recommended hardware listed in the table below. However, most users risk "
+"being frustrated if they ignore these suggestions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:747
 #, no-c-format
-msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
+msgid ""
+"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
 msgstr ""
 
 #. Tag: para
@@ -790,31 +1006,58 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:785
 #, no-c-format
-msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
+msgid ""
+"The actual minimum memory requirements are a lot less then the numbers "
+"listed in this table. Depending on the architecture, it is possible to "
+"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
+"same goes for the disk space requirements, especially if you pick and choose "
+"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
+"additional information on disk space requirements."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:795
 #, no-c-format
-msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
+msgid ""
+"It is possible to run a graphical desktop environment on older or low-end "
+"systems, but in that case it is recommended to install a window manager that "
+"is less resource-hungry than those of the GNOME or KDE desktop environments; "
+"alternatives include <classname>xfce4</classname>, <classname>icewm</"
+"classname> and <classname>wmaker</classname>, but there are others to choose "
+"from."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:804
 #, no-c-format
-msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
+msgid ""
+"It is practically impossible to give general memory or disk space "
+"requirements for server installations as those very much depend on what the "
+"server is to be used for."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:810
 #, no-c-format
-msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
+msgid ""
+"Remember that these sizes don't include all the other materials which are "
+"usually to be found, such as user files, mail, and data. It is always best "
+"to be generous when considering the space for your own files and data."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:817
 #, no-c-format
-msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to &debian; in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
+msgid ""
+"Disk space required for the smooth operation of the &debian-gnu; system "
+"itself is taken into account in these recommended system requirements. "
+"Notably, the <filename>/var</filename> partition contains a lot of state "
+"information specific to &debian; in addition to its regular contents, like "
+"logfiles. The <command>dpkg</command> files (with information on all "
+"installed packages) can easily consume 40MB. Also, <command>apt-get</"
+"command> puts downloaded packages here before they are installed. You should "
+"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
+"more if you install a graphical desktop environment."
 msgstr ""
 
 #. Tag: title
@@ -826,43 +1069,83 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:842
 #, no-c-format
-msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
+msgid ""
+"Partitioning your disk simply refers to the act of breaking up your disk "
+"into sections. Each section is then independent of the others. It's roughly "
+"equivalent to putting up walls inside a house; if you add furniture to one "
+"room it doesn't affect any other room."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:849
 #, no-c-format
-msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
+msgid ""
+"Whenever this section talks about <quote>disks</quote> you should translate "
+"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
+"means an LPAR or VM guest in this case."
 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 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."
 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 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
 #: preparing.xml:884
 #, no-c-format
-msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
+msgid ""
+"In general, changing a partition with a file system already on it will "
+"destroy any information there. Thus you should always make backups before "
+"doing any repartitioning. Using the analogy of the house, you would probably "
+"want to move all the furniture out of the way before moving a wall or you "
+"risk destroying it."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:892
 #, no-c-format
-msgid "Several modern operating systems offer the ability to move and resize certain existing partitions without destroying their contents. This allows making space for additional partitions without losing existing data. Even though this works quite well in most cases, making changes to the partitioning of a disk is an inherently dangerous action and should only be done after having made a full backup of all data. <phrase arch=\"any-x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, the ability to move and resize them losslessly is provided both by &d-i; as well as by the integrated Disk Manager of Windows 7. </phrase>"
+msgid ""
+"Several modern operating systems offer the ability to move and resize "
+"certain existing partitions without destroying their contents. This allows "
+"making space for additional partitions without losing existing data. Even "
+"though this works quite well in most cases, making changes to the "
+"partitioning of a disk is an inherently dangerous action and should only be "
+"done after having made a full backup of all data. <phrase arch=\"any-"
+"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
+"the ability to move and resize them losslessly is provided both by &d-i; as "
+"well as by the integrated Disk Manager of Windows 7. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:907
 #, no-c-format
-msgid "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size."
+msgid ""
+"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
+"to the partitioning step, select the option for manual partitioning, select "
+"the partition to resize, and simply specify its new size."
 msgstr ""
 
 #. Tag: emphasis
@@ -874,25 +1157,50 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:917
 #, no-c-format
-msgid "Creating and deleting partitions can be done from within &d-i; as well as from an existing operating system. As a rule of thumb, partitions should be created by the system for which they are to be used, i.e. partitions to be used by &debian-gnu; should be created from within &d-i; and partitions to be used from another operating system should be created from there. &d-i; is capable of creating non-&arch-kernel; partitions, and partitions created this way usually work without problems when used in other operating systems, but there are a few rare corner cases in which this could cause problems, so if you want to be sure, use the native partitioning tools to create partitions for use by other operating systems."
+msgid ""
+"Creating and deleting partitions can be done from within &d-i; as well as "
+"from an existing operating system. As a rule of thumb, partitions should be "
+"created by the system for which they are to be used, i.e. partitions to be "
+"used by &debian-gnu; should be created from within &d-i; and partitions to "
+"be used from another operating system should be created from there. &d-i; is "
+"capable of creating non-&arch-kernel; partitions, and partitions created "
+"this way usually work without problems when used in other operating systems, "
+"but there are a few rare corner cases in which this could cause problems, so "
+"if you want to be sure, use the native partitioning tools to create "
+"partitions for use by other operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with the &debian; installation. Windows and other OS installations may destroy your ability to start &debian;, or encourage you to reformat non-native partitions."
+msgid ""
+"If you are going to install more than one operating system on the same "
+"machine, you should install all other system(s) before proceeding with the "
+"&debian; installation. Windows and other OS installations may destroy your "
+"ability to start &debian;, or encourage you to reformat non-native "
+"partitions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:938
 #, no-c-format
-msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
+msgid ""
+"You can recover from these actions or avoid them, but installing the native "
+"system first saves you trouble."
 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 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."
 msgstr ""
 
 #. Tag: title
@@ -904,7 +1212,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1021
 #, no-c-format
-msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and &debian; on the same machine, it is recommended that you partition using SunOS prior to installing &debian;. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
+msgid ""
+"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
+"both SunOS and &debian; on the same machine, it is recommended that you "
+"partition using SunOS prior to installing &debian;. The Linux kernel "
+"understands Sun disk labels, so there are no problems there. SILO supports "
+"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
+"iso9660 (CDROM) partitions."
 msgstr ""
 
 #. Tag: title
@@ -916,13 +1230,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1035
 #, no-c-format
-msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
+msgid ""
+"Whatever system you are using to partition, make sure you create a "
+"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
+"partition scheme that the OpenBoot PROM understands, and so it's the only "
+"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
+"keycap> key is used to create Sun disk labels. You only need to do this on "
+"drives that do not already have a Sun disk label. If you are using a drive "
+"that was previously formatted using a PC (or other architecture) you must "
+"create a new disk label, or problems with the disk geometry will most likely "
+"occur."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1047
 #, no-c-format
-msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
+msgid ""
+"You will probably be using <command>SILO</command> as your boot loader (the "
+"small program which runs the operating system kernel). <command>SILO</"
+"command> has certain requirements for partition sizes and location; see "
+"<xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: title
@@ -934,25 +1261,49 @@ 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>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>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1071
 #, 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."
+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
 #, 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 ""
+"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."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1090
 #, 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 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."
 msgstr ""
 
 #. Tag: title
@@ -964,7 +1315,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1111
 #, 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)."
+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
@@ -976,7 +1333,15 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1128
 #, 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."
+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
@@ -988,31 +1353,63 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1144
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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>"
+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: title
@@ -1024,29 +1421,53 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1204
 #, 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."
+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:1212
 #, 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."
+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:1220
 #, no-c-format
 msgid ""
-      "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
-      "ok\n"
-      "0 &gt;\n"
-      "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
+"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
+"ok\n"
+"0 &gt;\n"
+"</screen></informalexample> Note that on older model &arch-title; Macs, the "
+"default and sometimes hardwired I/O for OpenFirmware user interaction is "
+"through the serial (modem) port. If you invoke OpenFirmware on one of these "
+"machines, you will just see a black screen. In that case, a terminal program "
+"running on another computer, connected to the modem port, is needed to "
+"interact with OpenFirmware."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1233
 #, 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."
+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
@@ -1058,45 +1479,90 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1255
 #, 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."
+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:1263
 #, 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."
+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:1275
 #, 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."
+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:1288
 #, 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>."
+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:1298
 #, 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"
-      "<replaceable>driver-name</replaceable>@\n"
-      "<replaceable>unit-address</replaceable>:\n"
-      "<replaceable>device-arguments</replaceable>\n"
-      "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
+"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"
+"<replaceable>driver-name</replaceable>@\n"
+"<replaceable>unit-address</replaceable>:\n"
+"<replaceable>device-arguments</replaceable>\n"
+"</screen></informalexample> In older revisions of OpenBoot, device naming is "
+"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
+"disk devices are of the form <quote>sd(<replaceable>controller</"
+"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
+"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
+"newer OpenBoot revisions is useful for viewing the currently configured "
+"devices. For full information, whatever your revision, see the <ulink url="
+"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1321
 #, 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"
-      "# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
-      "</screen></informalexample> and under Solaris:"
+"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"
+"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
+"</screen></informalexample> and under Solaris:"
 msgstr ""
 
 #. Tag: screen
@@ -1114,19 +1580,45 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1351
 #, 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."
+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:1363
 #, 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."
+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:1373
 #, 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."
+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
@@ -1138,7 +1630,12 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1391
 #, 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."
+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
@@ -1150,13 +1647,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1407
 #, 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."
+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:1417
 #, 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."
+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
@@ -1168,13 +1678,21 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1436
 #, 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."
+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:1444
 #, 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."
+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
@@ -1198,7 +1716,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1464
 #, 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."
+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
@@ -1210,6 +1734,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1479
 #, 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>."
+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 ""
-
diff --git a/po/da/preseed.po b/po/da/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/da/preseed.po
+++ b/po/da/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-
diff --git a/po/da/random-bits.po b/po/da/random-bits.po
index ff94f432b..26dbb7c32 100644
--- a/po/da/random-bits.po
+++ b/po/da/random-bits.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,7 +29,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:12
 #, no-c-format
-msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below."
+msgid ""
+"In Linux various special files can be found under the directory <filename>/"
+"dev</filename>. These files are called device files and behave unlike "
+"ordinary files. The most common types of device files are for block devices "
+"and character devices. These files are an interface to the actual driver "
+"(part of the Linux kernel) which in turn accesses the hardware. Another, "
+"less common, type of device file is the named <firstterm>pipe</firstterm>. "
+"The most important device files are listed in the tables below."
 msgstr ""
 
 #. Tag: filename
@@ -316,33 +324,62 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:126
 #, no-c-format
-msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. Normally, this is a simple matter of installing <filename>gpm</"
+"filename> and the X server itself. Both should be configured to use "
+"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse "
+"protocol is named <userinput>exps2</userinput> in gpm, and "
+"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files "
+"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:137
 #, no-c-format
-msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>."
+msgid ""
+"Certain kernel modules must be loaded in order for your mouse to work. In "
+"most cases the correct modules are autodetected, but not always for old-"
+"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole "
+"D-shaped connector; bus mice have an 8-pin round connector, not to be "
+"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round "
+"connector of an ADB mouse. </para> </footnote>, which are quite rare except "
+"on very old computers. Summary of Linux kernel modules needed for different "
+"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</"
+"entry> <entry>Description</entry> </row> </thead><tbody> <row> "
+"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </"
+"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</"
+"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> "
+"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech "
+"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse "
+"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></"
+"informaltable> To load a mouse driver module, you can use the "
+"<command>modconf</command> command (from the package with the same name) and "
+"look in the category <userinput>kernel/drivers/input/mouse</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:184
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:191
 #, no-c-format
 msgid ""
-      "# 3-button mouse emulation\n"
-      "# turn on emulation\n"
-      "/dev/mac_hid/mouse_button_emulation = 1\n"
-      "# Send middle mouse button signal with the F11 key\n"
-      "/dev/mac_hid/mouse_button2_keycode = 87\n"
-      "# Send right mouse button signal with the F12 key\n"
-      "/dev/mac_hid/mouse_button3_keycode = 88\n"
-      "# For different keys, use showkey to tell you what the code is."
+"# 3-button mouse emulation\n"
+"# turn on emulation\n"
+"/dev/mac_hid/mouse_button_emulation = 1\n"
+"# Send middle mouse button signal with the F11 key\n"
+"/dev/mac_hid/mouse_button2_keycode = 87\n"
+"# Send right mouse button signal with the F12 key\n"
+"/dev/mac_hid/mouse_button3_keycode = 88\n"
+"# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
 #. Tag: title
@@ -354,31 +391,54 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "A standard installation for the amd64 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB."
+msgid ""
+"A standard installation for the amd64 architecture, including all standard "
+"packages and using the default 2.6 kernel, takes up &std-system-size;MB of "
+"disk space. A minimal base installation, without the <quote>Standard system</"
+"quote> task selected, will take &base-system-size;MB."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:207
 #, no-c-format
-msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use."
+msgid ""
+"In both cases this is the actual disk space used <emphasis>after</emphasis> "
+"the installation is finished and any temporary files deleted. It also does "
+"not take into account overhead used by the file system, for example for "
+"journal files. This means that significantly more disk space is needed both "
+"<emphasis>during</emphasis> the installation and for normal system use."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:216
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:223
 #, no-c-format
-msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)."
+msgid ""
+"By default the installer will install the GNOME desktop environment, but "
+"alternative desktop environments can be selected either by using one of the "
+"special CD images, or by specifying the desired desktop environment when the "
+"installer is booted (see <xref linkend=\"pkgsel\"/>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:230
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the standard installation when determining the size of partitions. Most of "
+"the size listed as <quote>Installed size</quote> will end up in <filename>/"
+"usr</filename> and in <filename>/lib</filename>; the size listed as "
+"<quote>Download size</quote> is (temporarily) required in <filename>/var</"
+"filename>."
 msgstr ""
 
 #. Tag: entry
@@ -522,7 +582,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid ""
+"There is some overlap of the Laptop task with the Desktop environment task. "
+"If you install both, the Laptop task will only require a few MB additional "
+"disk space."
 msgstr ""
 
 #. Tag: entry
@@ -714,7 +777,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:350
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -726,19 +793,40 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:367
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
+msgid ""
+"This section explains how to install &debian-gnu; from an existing Unix or "
+"Linux system, without using the menu-driven installer as explained in the "
+"rest of the manual. This <quote>cross-install</quote> HOWTO has been "
+"requested by users switching to &debian-gnu; from Red Hat, Mandriva, and "
+"SUSE. In this section some familiarity with entering *nix commands and "
+"navigating the file system is assumed. In this section, <prompt>$</prompt> "
+"symbolizes a command to be entered in the user's current system, while "
+"<prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:379
 #, no-c-format
-msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new &debian; system configured to your preference, you "
+"can migrate your existing user data (if any) to it, and keep on rolling. "
+"This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's "
+"also a clever way for dealing with hardware that otherwise doesn't play "
+"friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:390
 #, no-c-format
-msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
+msgid ""
+"As this is a mostly manual procedure, you should bear in mind that you will "
+"need to do a lot of basic configuration of the system yourself, which will "
+"also require more knowledge of &debian; and of &arch-kernel; in general than "
+"performing a regular installation. You cannot expect this procedure to "
+"result in a system that is identical to a system from a regular "
+"installation. You should also keep in mind that this procedure only gives "
+"the basic steps to set up a system. Additional installation and/or "
+"configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
@@ -750,41 +838,56 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:405
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need around &base-"
+"system-size;MB of space available for a console only install, or about &task-"
+"desktop-lxde-inst;MB if you plan to install X (more if you intend to install "
+"desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:413
 #, no-c-format
 msgid ""
-      "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
-      "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
-      "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"Next, create file systems on the partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
+"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:423
 #, no-c-format
 msgid ""
-      "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
-      "# mkswap /dev/<replaceable>hda5</replaceable>\n"
-      "# sync; sync; sync\n"
-      "# swapon /dev/<replaceable>hda5</replaceable>\n"
-      "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"Initialize and activate swap (substitute the partition number for your "
+"intended &debian; swap partition): <informalexample><screen>\n"
+"# mkswap /dev/<replaceable>hda5</replaceable>\n"
+"# sync; sync; sync\n"
+"# swapon /dev/<replaceable>hda5</replaceable>\n"
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:435
 #, no-c-format
 msgid ""
-      "# mkdir /mnt/debinst\n"
-      "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
+"# mkdir /mnt/debinst\n"
+"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:438
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
@@ -796,26 +899,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:449
 #, no-c-format
-msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The utility used by the &debian; installer, and recognized as the official "
+"way to install a &debian; base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname> and basic Unix/Linux "
+"tools<footnote> <para> These include the GNU core utilities and commands "
+"like <command>sed</command>, <command>grep</command>, <command>tar</command> "
+"and <command>gzip</command>. </para> </footnote>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:479
 #, no-c-format
 msgid ""
-      "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
-      "# mkdir work\n"
-      "# cd work\n"
-      "</screen></informalexample> The <command>debootstrap</command> binary is located in the &debian; archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files."
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
+"# mkdir work\n"
+"# cd work\n"
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the &debian; archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the files from it. "
+"You will need to have root privileges to install the files."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:494
 #, no-c-format
 msgid ""
-      "# ar -x debootstrap_0.X.X_all.deb\n"
-      "# cd /\n"
-      "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
+"# ar -x debootstrap_0.X.X_all.deb\n"
+"# cd /\n"
+"# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
 #. Tag: title
@@ -827,27 +945,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any &debian; archive mirror "
+"for <userinput>&archive-mirror;/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:510
 #, no-c-format
-msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>amd64</userinput>, "
+"<userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, "
+"<userinput>mipsel</userinput>, <userinput>powerpc</userinput>, "
+"<userinput>s390</userinput>, <userinput>s390x</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:533
 #, no-c-format
 msgid ""
-      "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
-      "     /mnt/debinst http://ftp.us.debian.org/debian"
+"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
+"     /mnt/debinst http://ftp.us.debian.org/debian"
 msgstr ""
 
 #. Tag: title
@@ -860,9 +993,11 @@ msgstr ""
 #: random-bits.xml:540
 #, no-c-format
 msgid ""
-      "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
-      "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
-      "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:"
+"Now you've got a real &debian; system, though rather lean, on disk. "
+"<command>chroot</command> into it: <informalexample><screen>\n"
+"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
+"</screen></informalexample> After chrooting you may need to set the terminal "
+"definition to be compatible with the &debian; base system, for example:"
 msgstr ""
 
 #. Tag: screen
@@ -880,7 +1015,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:556
 #, no-c-format
-msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
+msgid ""
+"At this point <filename>/dev/</filename> only contains very basic device "
+"files. For the next steps of the installation additional device files may be "
+"needed. There are different ways to go about this and which method you "
+"should use depends on the host system you are using for the installation, on "
+"whether you intend to use a modular kernel or not, and on whether you intend "
+"to use dynamic (e.g. using <classname>udev</classname>) or static device "
+"files for the new system."
 msgstr ""
 
 #. Tag: para
@@ -892,28 +1034,34 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:571
 #, no-c-format
-msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
+msgid ""
+"install the makedev package, and create a default set of static device files "
+"using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:575
 #, no-c-format
 msgid ""
-      "# apt-get install makedev\n"
-      "# cd /dev\n"
-      "# MAKEDEV generic"
+"# apt-get install makedev\n"
+"# cd /dev\n"
+"# MAKEDEV generic"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:578
 #, no-c-format
-msgid "manually create only specific device files using <command>MAKEDEV</command>"
+msgid ""
+"manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:583
 #, no-c-format
-msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
+msgid ""
+"bind mount /dev from your host system on top of /dev in the target system; "
+"note that the postinst scripts of some packages may try to create device "
+"files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
@@ -926,34 +1074,44 @@ msgstr ""
 #: random-bits.xml:597
 #, no-c-format
 msgid ""
-      "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
-      "# editor /etc/fstab\n"
-      "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
-      "# /etc/fstab: static file system information.\n"
-      "#\n"
-      "# file system    mount point   type    options                  dump pass\n"
-      "/dev/XXX         /             ext3    defaults                 0    1\n"
-      "/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
-      "\n"
-      "/dev/XXX         none          swap    sw                       0    0\n"
-      "proc             /proc         proc    defaults                 0    0\n"
-      "\n"
-      "/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
-      "/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
-      "\n"
-      "/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
-      "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-      "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n"
-      "# mount /path   # e.g.: mount /usr\n"
-      "</screen></informalexample> Current &debian; systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n"
-      "# cd /media\n"
-      "# mkdir cdrom0\n"
-      "# ln -s cdrom0 cdrom\n"
-      "# cd /\n"
-      "# ln -s media/cdrom\n"
-      "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
+"# editor /etc/fstab\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
+"# /etc/fstab: static file system information.\n"
+"#\n"
+"# file system    mount point   type    options                  dump pass\n"
+"/dev/XXX         /             ext3    defaults                 0    1\n"
+"/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
+"\n"
+"/dev/XXX         none          swap    sw                       0    0\n"
+"proc             /proc         proc    defaults                 0    0\n"
+"\n"
+"/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
+"/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
+"\n"
+"/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
+"/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or, to mount file systems individually, use: <informalexample><screen>\n"
+"# mount /path   # e.g.: mount /usr\n"
+"</screen></informalexample> Current &debian; systems have mountpoints for "
+"removable media under <filename>/media</filename>, but keep compatibility "
+"symlinks in <filename>/</filename>. Create these as as needed, for example: "
+"<informalexample><screen>\n"
+"# cd /media\n"
+"# mkdir cdrom0\n"
+"# ln -s cdrom0 cdrom\n"
+"# cd /\n"
+"# ln -s media/cdrom\n"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -965,7 +1123,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:625
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -983,15 +1144,19 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:638
 #, no-c-format
-msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
+msgid ""
+"An option in the file <filename>/etc/default/rcS</filename> determines "
+"whether the system will interpret the hardware clock as being set to UTC or "
+"local time. The following command allows you to set that and choose your "
+"timezone."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:645
 #, no-c-format
 msgid ""
-      "# editor /etc/default/rcS\n"
-      "# dpkg-reconfigure tzdata"
+"# editor /etc/default/rcS\n"
+"# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
@@ -1004,54 +1169,64 @@ msgstr ""
 #: random-bits.xml:652
 #, no-c-format
 msgid ""
-      "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
-      "# editor /etc/network/interfaces\n"
-      "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
-      "######################################################################\n"
-      "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
-      "# See the interfaces(5) manpage for information on what options are\n"
-      "# available.\n"
-      "######################################################################\n"
-      "\n"
-      "# We always want the loopback interface.\n"
-      "#\n"
-      "auto lo\n"
-      "iface lo inet loopback\n"
-      "\n"
-      "# To use dhcp:\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet dhcp\n"
-      "\n"
-      "# An example static IP setup: (broadcast and gateway are optional)\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet static\n"
-      "#     address 192.168.0.42\n"
-      "#     network 192.168.0.0\n"
-      "#     netmask 255.255.255.0\n"
-      "#     broadcast 192.168.0.255\n"
-      "#     gateway 192.168.0.1\n"
-      "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "# editor /etc/resolv.conf\n"
-      "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "search hqdom.local\n"
-      "nameserver 10.1.1.36\n"
-      "nameserver 192.168.9.100\n"
-      "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
-      "# echo DebianHostName &gt; /etc/hostname\n"
-      "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n"
-      "127.0.0.1 localhost\n"
-      "127.0.1.1 DebianHostName\n"
-      "\n"
-      "# The following lines are desirable for IPv6 capable hosts\n"
-      "::1     ip6-localhost ip6-loopback\n"
-      "fe00::0 ip6-localnet\n"
-      "ff00::0 ip6-mcastprefix\n"
-      "ff02::1 ip6-allnodes\n"
-      "ff02::2 ip6-allrouters\n"
-      "ff02::3 ip6-allhosts\n"
-      "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> "
+"and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
+"# editor /etc/network/interfaces\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"######################################################################\n"
+"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
+"# See the interfaces(5) manpage for information on what options are\n"
+"# available.\n"
+"######################################################################\n"
+"\n"
+"# We always want the loopback interface.\n"
+"#\n"
+"auto lo\n"
+"iface lo inet loopback\n"
+"\n"
+"# To use dhcp:\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet dhcp\n"
+"\n"
+"# An example static IP setup: (broadcast and gateway are optional)\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet static\n"
+"#     address 192.168.0.42\n"
+"#     network 192.168.0.0\n"
+"#     netmask 255.255.255.0\n"
+"#     broadcast 192.168.0.255\n"
+"#     gateway 192.168.0.1\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"# editor /etc/resolv.conf\n"
+"</screen></informalexample> A simple example <filename>/etc/resolv.conf</"
+"filename>: <informalexample><screen>\n"
+"search hqdom.local\n"
+"nameserver 10.1.1.36\n"
+"nameserver 192.168.9.100\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
+"# echo DebianHostName &gt; /etc/hostname\n"
+"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with "
+"IPv6 support: <informalexample><screen>\n"
+"127.0.0.1 localhost\n"
+"127.0.1.1 DebianHostName\n"
+"\n"
+"# The following lines are desirable for IPv6 capable hosts\n"
+"::1     ip6-localhost ip6-loopback\n"
+"fe00::0 ip6-localnet\n"
+"ff00::0 ip6-mcastprefix\n"
+"ff02::1 ip6-allnodes\n"
+"ff02::2 ip6-allrouters\n"
+"ff02::3 ip6-allhosts\n"
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1064,12 +1239,16 @@ msgstr ""
 #: random-bits.xml:694
 #, no-c-format
 msgid ""
-      "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
-      "deb-src http://ftp.us.debian.org/debian &releasename; main\n"
-      "\n"
-      "deb http://security.debian.org/ &releasename;/updates main\n"
-      "deb-src http://security.debian.org/ &releasename;/updates main\n"
-      "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list."
+"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</"
+"filename> that will allow installing additional packages. However, you may "
+"want to add some additional sources, for example for source packages and "
+"security updates: <informalexample><screen>\n"
+"deb-src http://ftp.us.debian.org/debian &releasename; main\n"
+"\n"
+"deb http://security.debian.org/ &releasename;/updates main\n"
+"deb-src http://security.debian.org/ &releasename;/updates main\n"
+"</screen></informalexample> Make sure to run <userinput>aptitude update</"
+"userinput> after you have made changes to the sources list."
 msgstr ""
 
 #. Tag: title
@@ -1082,24 +1261,29 @@ msgstr ""
 #: random-bits.xml:711
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
-      "# aptitude install locales\n"
-      "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> To configure your keyboard (if needed):"
+"To configure your locale settings to use a language other than English, "
+"install the <classname>locales</classname> support package and configure it. "
+"Currently the use of UTF-8 locales is recommended. "
+"<informalexample><screen>\n"
+"# aptitude install locales\n"
+"# dpkg-reconfigure locales\n"
+"</screen></informalexample> To configure your keyboard (if needed):"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:721
 #, no-c-format
 msgid ""
-      "# aptitude install console-setup\n"
-      "# dpkg-reconfigure keyboard-configuration"
+"# aptitude install console-setup\n"
+"# dpkg-reconfigure keyboard-configuration"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:723
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1111,7 +1295,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:734
 #, no-c-format
-msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
+msgid ""
+"If you intend to boot this system, you probably want a &arch-kernel; kernel "
+"and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
@@ -1129,7 +1315,9 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:745
 #, no-c-format
-msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid ""
+"# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</"
+"replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1141,30 +1329,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:752
 #, no-c-format
-msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
+msgid ""
+"To make your &debian-gnu; system bootable, set up your boot loader to load "
+"the installed kernel with your new root partition. Note that "
+"<command>debootstrap</command> does not install a boot loader, though you "
+"can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:759
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
+msgid ""
+"Check <userinput>info grub</userinput> <phrase arch=\"x86\">or "
+"<userinput>man lilo.conf</userinput></phrase> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing grub2 "
+"<filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</"
+"filename>. For <filename>lilo.conf</filename>, you could also copy it to the "
+"new system and edit it there. After you are done editing, call "
+"<command>lilo</command> (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:771
 #, no-c-format
 msgid ""
-      "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
-      "# aptitude install grub-pc\n"
-      "# grub-install /dev/<replaceable>hda</replaceable>\n"
-      "# update-grub\n"
-      "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>."
+"Installing and setting up <classname>grub2</classname> is as easy as: "
+"<informalexample><screen>\n"
+"# aptitude install grub-pc\n"
+"# grub-install /dev/<replaceable>hda</replaceable>\n"
+"# update-grub\n"
+"</screen></informalexample> The second command will install <command>grub2</"
+"command> (in this case in the MBR of <literal>hda</literal>). The last "
+"command will create a sane and working <filename>/boot/grub/grub.cfg</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:781
 #, no-c-format
-msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
+msgid ""
+"Note that this assumes that a <filename>/dev/hda</filename> device file has "
+"been created. There are alternative methods to install <command>grub2</"
+"command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
@@ -1177,36 +1385,44 @@ msgstr ""
 #: random-bits.xml:791
 #, no-c-format
 msgid ""
-      "boot=/dev/<replaceable>hda6</replaceable>\n"
-      "root=/dev/<replaceable>hda6</replaceable>\n"
-      "install=menu\n"
-      "delay=20\n"
-      "lba32\n"
-      "image=/vmlinuz\n"
-      "initrd=/initrd.img\n"
-      "label=Debian"
+"boot=/dev/<replaceable>hda6</replaceable>\n"
+"root=/dev/<replaceable>hda6</replaceable>\n"
+"install=menu\n"
+"delay=20\n"
+"lba32\n"
+"image=/vmlinuz\n"
+"initrd=/initrd.img\n"
+"label=Debian"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:793
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:803
 #, no-c-format
 msgid ""
-      "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
-      "boot=/dev/hda2\n"
-      "device=hd:\n"
-      "partition=6\n"
-      "root=/dev/hda6\n"
-      "magicboot=/usr/lib/yaboot/ofboot\n"
-      "timeout=50\n"
-      "image=/vmlinux\n"
-      "label=Debian\n"
-      "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
+"boot=/dev/hda2\n"
+"device=hd:\n"
+"partition=6\n"
+"root=/dev/hda6\n"
+"magicboot=/usr/lib/yaboot/ofboot\n"
+"timeout=50\n"
+"image=/vmlinux\n"
+"label=Debian\n"
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1218,15 +1434,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:817
 #, no-c-format
-msgid "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set a password for root:"
+msgid ""
+"In case you can login to the system via console, you can skip this section. "
+"If the system should be accessible via the network later on, you need to "
+"install SSH and set a password for root:"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:823
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+"# aptitude install ssh\n"
+"# passwd"
 msgstr ""
 
 #. Tag: title
@@ -1239,15 +1458,22 @@ msgstr ""
 #: random-bits.xml:829
 #, no-c-format
 msgid ""
-      "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
-      "# tasksel install standard\n"
-      "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually."
+"As mentioned earlier, the installed system will be very basic. If you would "
+"like to make the system a bit more mature, there is an easy method to "
+"install all packages with <quote>standard</quote> priority: "
+"<informalexample><screen>\n"
+"# tasksel install standard\n"
+"</screen></informalexample> Of course, you can also just use "
+"<command>aptitude</command> to install packages individually."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:840
 #, no-c-format
-msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
+msgid ""
+"After the installation there will be a lot of downloaded packages in "
+"<filename>/var/cache/apt/archives/</filename>. You can free up some "
+"diskspace by running:"
 msgstr ""
 
 #. Tag: screen
@@ -1265,25 +1491,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:859
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian-gnu; on a computer without an "
+"Ethernet card, but with just a remote gateway computer attached via a Null-"
+"Modem cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a &debian; mirror on it (e.g. to the "
+"Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:867
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:875
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:880
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1295,7 +1538,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:893
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where &debian; will "
+"be installed."
 msgstr ""
 
 #. Tag: para
@@ -1307,13 +1552,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:904
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:910
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
@@ -1325,28 +1575,33 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:923
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:928
 #, no-c-format
 msgid ""
-      "#!/bin/sh\n"
-      "\n"
-      "# We remove running modules from kernel to avoid conflicts and to\n"
-      "# reconfigure them manually.\n"
-      "modprobe -r lp parport_pc\n"
-      "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
-      "modprobe plip\n"
-      "\n"
-      "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-      "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
-      "\n"
-      "# Configure gateway\n"
-      "modprobe iptable_nat\n"
-      "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
-      "echo 1 > /proc/sys/net/ipv4/ip_forward"
+"#!/bin/sh\n"
+"\n"
+"# We remove running modules from kernel to avoid conflicts and to\n"
+"# reconfigure them manually.\n"
+"modprobe -r lp parport_pc\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
+"modprobe plip\n"
+"\n"
+"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"\n"
+"# Configure gateway\n"
+"modprobe iptable_nat\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
+"echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
 #. Tag: title
@@ -1359,9 +1614,16 @@ msgstr ""
 #: random-bits.xml:935
 #, no-c-format
 msgid ""
-      "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
-      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
-      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to "
+"set parameters for kernel modules, you also need to do this at the boot "
+"prompt. For example, to boot the installer and set values for the <quote>io</"
+"quote> and <quote>irq</quote> options for the parport_pc module, enter the "
+"following at the boot prompt: <informalexample><screen>\n"
+"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc."
+"irq=<replaceable>7</replaceable>\n"
+"</screen></informalexample> Below are the answers that should be given "
+"during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1373,7 +1635,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:956
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1385,13 +1649,20 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:969
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:978
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1409,19 +1680,24 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:998
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1003
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1009
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
@@ -1433,67 +1709,112 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1030
 #, no-c-format
-msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
+msgid ""
+"In some countries PPP over Ethernet (PPPoE) is a common protocol for "
+"broadband (ADSL or cable) connections to an Internet Service Provider. "
+"Setting up a network connection using PPPoE is not supported by default in "
+"the installer, but can be made to work very simply. This section explains "
+"how."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1038
 #, no-c-format
-msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PPPoE connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1043
 #, no-c-format
-msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
+msgid ""
+"To have the option of setting up and using PPPoE during the installation, "
+"you will need to install using one of the CD-ROM/DVD images that are "
+"available. It is not supported for other installation methods (e.g. "
+"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1050
 #, no-c-format
-msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
+msgid ""
+"Installing over PPPoE is mostly the same as any other installation. The "
+"following steps explain the differences."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1058
 #, no-c-format
-msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
+msgid ""
+"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</"
+"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> "
+"for information on how to add a boot parameter. </para> </footnote>. This "
+"will ensure the component responsible for the setup of PPPoE (<classname>ppp-"
+"udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1073
 #, no-c-format
-msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
+msgid ""
+"Follow the regular initial steps of the installation (language, country and "
+"keyboard selection; the loading of additional installer components<footnote> "
+"<para> The <classname>ppp-udeb</classname> component is loaded as one of the "
+"additional components in this step. If you want to install at medium or low "
+"priority (expert mode), you can also manually select the <classname>ppp-"
+"udeb</classname> instead of entering the <quote>modules</quote> parameter at "
+"the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1092
 #, no-c-format
-msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
+msgid ""
+"The next step is the detection of network hardware, in order to identify any "
+"Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1098
 #, no-c-format
-msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
+msgid ""
+"After this the actual setup of PPPoE is started. The installer will probe "
+"all the detected Ethernet interfaces in an attempt to find a PPPoE "
+"concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1104
 #, no-c-format
-msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
+msgid ""
+"It is possible that the concentrator will not to be found at the first "
+"attempt. This can happen occasionally on slow or loaded networks or with "
+"faulty servers. In most cases a second attempt to detect the concentrator "
+"will be successful; to retry, select <guimenuitem>Configure and start a "
+"PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1113
 #, no-c-format
-msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
+msgid ""
+"After a concentrator is found, the user will be prompted to type the login "
+"information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1119
 #, no-c-format
-msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
+msgid ""
+"At this point the installer will use the provided information to establish "
+"the PPPoE connection. If the correct information was provided, the PPPoE "
+"connection should be configured and the installer should be able to use it "
+"to connect to the Internet and retrieve packages over it (if needed). If the "
+"login information is not correct or some error appears, the installer will "
+"stop, but the configuration can be attempted again by selecting the menu "
+"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
@@ -1505,49 +1826,89 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1140
 #, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
+msgid ""
+"The graphical version of the installer is only available for a limited "
+"number of architectures, including &arch-title;. The functionality of the "
+"graphical installer is essentially the same as that of the regular installer "
+"as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1148
 #, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
+msgid ""
+"Although the functionality is identical, the graphical installer still has a "
+"few significant advantages. The main advantage is that it supports more "
+"languages, namely those that use a character set that cannot be displayed "
+"with the regular <quote>newt</quote> frontend. It also has a few usability "
+"advantages such as the option to use a mouse, and in some cases several "
+"questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1157
 #, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
+msgid ""
+"The graphical installer is available with all CD images and with the hd-"
+"media installation method. To boot the graphical installer simply select the "
+"relevant option from the boot menu. Expert and rescue mode for the graphical "
+"installer can be selected from the <quote>Advanced options</quote> menu. The "
+"previously used boot methods <userinput>installgui</userinput>, "
+"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
+"still be used from the boot prompt which is shown after selecting the "
+"<quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1168
 #, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
+msgid ""
+"There is also a graphical installer image that can be netbooted. And there "
+"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> "
+"<para> The mini ISO image can be downloaded from a &debian; mirror as "
+"described in <xref linkend=\"downloading-files\"/>. Look for "
+"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
+"mainly useful for testing."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1181
 #, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
+msgid ""
+"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
+"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image "
+"can be downloaded from a &debian; mirror as described in <xref linkend="
+"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
+"</para> </footnote>. It should work on almost all PowerPC systems that have "
+"an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1195
 #, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
+msgid ""
+"Just as with the regular installer it is possible to add boot parameters "
+"when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1201
 #, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
+msgid ""
+"The graphical installer requires significantly more memory to run than the "
+"regular installer: &minimum-memory-gtk;. If insufficient memory is "
+"available, it will automatically fall back to the regular <quote>newt</"
+"quote> frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1208
 #, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
+msgid ""
+"If the amount of memory in your system is below &minimum-memory;, the "
+"graphical installer may fail to boot at all while booting the regular "
+"installer would still work. Using the regular installer is recommended for "
+"systems with little available memory."
 msgstr ""
 
 #. Tag: title
@@ -1559,24 +1920,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1219
 #, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
+msgid ""
+"As already mentioned, the graphical installer basically works the same as "
+"the regular installer and thus the rest of this manual can be used to guide "
+"you through the installation process."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1225
 #, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgid ""
+"If you prefer using the keyboard over the mouse, there are two things you "
+"need to know. To expand a collapsed list (used for example for the selection "
+"of countries within continents), you can use the <keycap>+</keycap> and "
+"<keycap>-</keycap> keys. For questions where more than one item can be "
+"selected (e.g. task selection), you first need to tab to the &BTN-CONT; "
+"button after making your selections; hitting enter will toggle a selection, "
+"not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1235
 #, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgid ""
+"If a dialog offers additional help information, a <guibutton>Help</"
+"guibutton> button will be displayed. The help information can be accessed "
+"either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1241
 #, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgid ""
+"To switch to another console, you will also need to use the <keycap>Ctrl</"
+"keycap> key, just as with the X Window System. For example, to switch to VT2 "
+"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> "
+"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical "
+"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</"
+"keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""
-
diff --git a/po/da/using-d-i.po b/po/da/using-d-i.po
index bbba423e4..85197cce6 100644
--- a/po/da/using-d-i.po
+++ b/po/da/using-d-i.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,79 +29,147 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:8
 #, no-c-format
-msgid "The &debian; Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started."
+msgid ""
+"The &debian; Installer consists of a number of special-purpose components to "
+"perform each installation task. Each component performs its task, asking the "
+"user questions as necessary to do its job. The questions themselves are "
+"given priorities, and the priority of questions to be asked is set when the "
+"installer is started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:16
 #, no-c-format
-msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked."
+msgid ""
+"When a default installation is performed, only essential (high priority) "
+"questions will be asked. This results in a highly automated installation "
+"process with little user interaction. Components are automatically run in "
+"sequence; which components are run depends mainly on the installation method "
+"you use and on your hardware. The installer will use default values for "
+"questions that are not asked."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:25
 #, no-c-format
-msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified."
+msgid ""
+"If there is a problem, the user will see an error screen, and the installer "
+"menu may be shown in order to select some alternative action. If there are "
+"no problems, the user will never see the installer menu, but will simply "
+"answer questions for each component in turn. Serious error notifications are "
+"set to priority <quote>critical</quote> so the user will always be notified."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:34
 #, no-c-format
-msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
+msgid ""
+"Some of the defaults that the installer uses can be influenced by passing "
+"boot arguments when &d-i; is started. If, for example, you wish to force "
+"static network configuration (DHCP is used by default if available), you "
+"could add the boot parameter <userinput>netcfg/disable_dhcp=true</"
+"userinput>. See <xref linkend=\"installer-args\"/> for available options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:42
 #, no-c-format
-msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>."
+msgid ""
+"Power users may be more comfortable with a menu-driven interface, where each "
+"step is controlled by the user rather than the installer performing each "
+"step automatically in sequence. To use the installer in a manual, menu-"
+"driven way, add the boot argument <userinput>priority=medium</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:50
 #, no-c-format
-msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;."
+msgid ""
+"If your hardware requires you to pass options to kernel modules as they are "
+"installed, you will need to start the installer in <quote>expert</quote> "
+"mode. This can be done by either using the <command>expert</command> command "
+"to start the installer or by adding the boot argument "
+"<userinput>priority=low</userinput>. Expert mode gives you full control over "
+"&d-i;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:59
 #, no-c-format
-msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgid ""
+"For this architecture the &d-i; supports two different user interfaces: a "
+"character-based one and a graphical one. The character-based interface is "
+"used by default unless you selected the <quote>Graphical install</quote> "
+"option in the initial boot menu. For more information about the graphical "
+"installer, please refer to <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:67
 #, no-c-format
-msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
+msgid ""
+"For this architecture the installer uses a character-based user interface. A "
+"graphical user interface is currently not available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:72
 #, no-c-format
-msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
+msgid ""
+"In the character-based environment the use of a mouse is not supported. Here "
+"are the keys you can use to navigate within the various dialogs. The "
+"<keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move "
+"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> "
+"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move "
+"<quote>backward</quote> between displayed buttons and selections. The "
+"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items "
+"within a scrollable list, and also scroll the list itself. In addition, in "
+"long lists, you can type a letter to cause the list to scroll directly to "
+"the section with items starting with the letter you typed and use <keycap>Pg-"
+"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The "
+"<keycap>space bar</keycap> selects an item such as a checkbox. Use "
+"&enterkey; to activate choices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:89
 #, no-c-format
-msgid "Some dialogs may offer additional help information. If help is available this will be indicated on the bottom line of the screen by displaying that help information can be accessed by pressing the <keycap>F1</keycap> key."
+msgid ""
+"Some dialogs may offer additional help information. If help is available "
+"this will be indicated on the bottom line of the screen by displaying that "
+"help information can be accessed by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:95
 #, no-c-format
-msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
+msgid ""
+"S/390 does not support virtual consoles. You may open a second and third ssh "
+"session to view the logs described below."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:100
 #, no-c-format
-msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"Error messages and logs are redirected to the fourth console. You can access "
+"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</"
+"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing "
+"the <keycap>F4</keycap> function key); get back to the main installer "
+"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></"
+"keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:110
 #, no-c-format
-msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"These messages can also be found in <filename>/var/log/syslog</filename>. "
+"After installation, this log is copied to <filename>/var/log/installer/"
+"syslog</filename> on your new system. Other installation messages may be "
+"found in <filename>/var/log/</filename> during the installation, and "
+"<filename>/var/log/installer/</filename> after the computer has been booted "
+"into the installed system."
 msgstr ""
 
 #. Tag: title
@@ -112,7 +181,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:125
 #, no-c-format
-msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
+msgid ""
+"Here is a list of installer components with a brief description of each "
+"component's purpose. Details you might need to know about using a particular "
+"component are in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: term
@@ -124,13 +196,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:136
 #, no-c-format
-msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
+msgid ""
+"Shows the list of components to the user during installer operation, and "
+"starts a component when it is selected. Main-menu's questions are set to "
+"priority medium, so if your priority is set to high or critical (high is the "
+"default), you will not see the menu. On the other hand, if there is an error "
+"which requires your intervention, the question priority may be downgraded "
+"temporarily to allow you to resolve the problem, and in that case the menu "
+"may appear."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:146
 #, no-c-format
-msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
+msgid ""
+"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly "
+"to back all the way out of the currently running component."
 msgstr ""
 
 #. Tag: term
@@ -142,7 +223,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:155
 #, no-c-format
-msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
+msgid ""
+"Allows the user to select localization options for the installation and the "
+"installed system: language, country and locales. The installer will display "
+"messages in the selected language, unless the translation for that language "
+"is not complete in which case some messages may be shown in English."
 msgstr ""
 
 #. Tag: term
@@ -154,7 +239,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:167
 #, no-c-format
-msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
+msgid ""
+"Shows a list of keyboards, from which the user chooses the model which "
+"matches his own."
 msgstr ""
 
 #. Tag: term
@@ -166,7 +253,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:176
 #, no-c-format
-msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
+msgid ""
+"Automatically detects most of the system's hardware, including network "
+"cards, disk drives, and PCMCIA."
 msgstr ""
 
 #. Tag: term
@@ -190,7 +279,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:193
 #, no-c-format
-msgid "Configures the computer's network connections so it can communicate over the internet."
+msgid ""
+"Configures the computer's network connections so it can communicate over the "
+"internet."
 msgstr ""
 
 #. Tag: term
@@ -202,7 +293,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:202
 #, no-c-format
-msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
+msgid ""
+"Searches for ISO images (<filename>.iso</filename> files) on hard drives."
 msgstr ""
 
 #. Tag: term
@@ -214,7 +306,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:210
 #, no-c-format
-msgid "Presents a list of &debian; archive mirrors. The user may choose the source of his installation packages."
+msgid ""
+"Presents a list of &debian; archive mirrors. The user may choose the source "
+"of his installation packages."
 msgstr ""
 
 #. Tag: term
@@ -226,7 +320,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:219
 #, no-c-format
-msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
+msgid ""
+"Checks integrity of a CD-ROM. This way, the user may assure him/herself that "
+"the installation CD-ROM was not corrupted."
 msgstr ""
 
 #. Tag: term
@@ -238,7 +334,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:228
 #, no-c-format
-msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
+msgid ""
+"Lowmem tries to detect systems with low memory and then does various tricks "
+"to remove unnecessary parts of &d-i; from the memory (at the cost of some "
+"features)."
 msgstr ""
 
 #. Tag: term
@@ -250,7 +349,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:238
 #, no-c-format
-msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
+msgid ""
+"Anna's Not Nearly APT. Installs packages which have been retrieved from the "
+"chosen mirror or CD."
 msgstr ""
 
 #. Tag: term
@@ -274,7 +375,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:255
 #, no-c-format
-msgid "Updates the system clock and determines whether the clock is set to UTC or not."
+msgid ""
+"Updates the system clock and determines whether the clock is set to UTC or "
+"not."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +401,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:272
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
+msgid ""
+"Allows the user to partition disks attached to the system, create file "
+"systems on the selected partitions, and attach them to the mountpoints. "
+"Included are also interesting features like a fully automatic mode or LVM "
+"support. This is the preferred partitioning tool in &debian;."
 msgstr ""
 
 #. Tag: term
@@ -310,7 +417,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:284
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
+msgid ""
+"Allows the user to partition disks attached to the system. A partitioning "
+"program appropriate to your computer's architecture is chosen."
 msgstr ""
 
 #. Tag: term
@@ -322,7 +431,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:294
 #, no-c-format
-msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
+msgid ""
+"Displays a list of partitions, and creates file systems on the selected "
+"partitions according to user instructions."
 msgstr ""
 
 #. Tag: term
@@ -334,7 +445,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:303
 #, no-c-format
-msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
+msgid ""
+"Helps the user with the configuration of the <firstterm>LVM</firstterm> "
+"(Logical Volume Manager)."
 msgstr ""
 
 #. Tag: term
@@ -346,7 +459,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:312
 #, no-c-format
-msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
+msgid ""
+"Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant "
+"Array of Inexpensive Disks). This Software RAID is usually superior to the "
+"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
 #. Tag: term
@@ -358,7 +474,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:323
 #, no-c-format
-msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
+msgid ""
+"Installs the most basic set of packages which would allow the computer to "
+"operate under &debian-gnu; when rebooted."
 msgstr ""
 
 #. Tag: term
@@ -370,7 +488,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:332
 #, no-c-format
-msgid "Configures apt, mostly automatically, based on what media the installer is running from."
+msgid ""
+"Configures apt, mostly automatically, based on what media the installer is "
+"running from."
 msgstr ""
 
 #. Tag: term
@@ -382,7 +502,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:341
 #, no-c-format
-msgid "Uses <classname>tasksel</classname> to select and install additional software."
+msgid ""
+"Uses <classname>tasksel</classname> to select and install additional "
+"software."
 msgstr ""
 
 #. Tag: term
@@ -394,7 +516,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:349
 #, no-c-format
-msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
+msgid ""
+"Detects currently installed operating systems on the computer and passes "
+"this information to the bootloader-installer, which may offer you an ability "
+"to add discovered operating systems to the bootloader's start menu. This way "
+"the user could easily choose at the boot time which operating system to "
+"start."
 msgstr ""
 
 #. Tag: term
@@ -406,7 +533,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:361
 #, no-c-format
-msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
+msgid ""
+"The various bootloader installers each install a boot loader program on the "
+"hard disk, which is necessary for the computer to start up using &arch-"
+"kernel; without using a floppy or CD-ROM. Many boot loaders allow the user "
+"to choose an alternate operating system each time the computer boots."
 msgstr ""
 
 #. Tag: term
@@ -418,7 +549,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:372
 #, no-c-format
-msgid "Allows the user to execute a shell from the menu, or in the second console."
+msgid ""
+"Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
 #. Tag: term
@@ -430,7 +562,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:381
 #, no-c-format
-msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to &debian; developers later."
+msgid ""
+"Provides a way for the user to record information on a floppy disk, network, "
+"hard disk, or other media when trouble is encountered, in order to "
+"accurately report installer software problems to &debian; developers later."
 msgstr ""
 
 #. Tag: title
@@ -442,7 +577,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:400
 #, no-c-format
-msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
+msgid ""
+"In this section we will describe each installer component in detail. The "
+"components have been grouped into stages that should be recognizable for "
+"users. They are presented in the order they appear during the install. Note "
+"that not all modules will be used for every installation; which modules are "
+"actually used depends on the installation method you use and on your "
+"hardware."
 msgstr ""
 
 #. Tag: title
@@ -454,19 +595,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:413
 #, no-c-format
-msgid "Let's assume the &debian; Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
+msgid ""
+"Let's assume the &debian; Installer has booted and you are facing its first "
+"screen. At this time, the capabilities of &d-i; are still quite limited. It "
+"doesn't know much about your hardware, preferred language, or even the task "
+"it should perform. Don't worry. Because &d-i; is quite clever, it can "
+"automatically probe your hardware, locate the rest of its components and "
+"upgrade itself to a capable installation system. However, you still need to "
+"help &d-i; with some information it can't determine automatically (like "
+"selecting your preferred language, keyboard layout or desired network "
+"mirror)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:426
 #, no-c-format
-msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
+msgid ""
+"You will notice that &d-i; performs <firstterm>hardware detection</"
+"firstterm> several times during this stage. The first time is targeted "
+"specifically at the hardware needed to load installer components (e.g. your "
+"CD-ROM or network card). As not all drivers may be available during this "
+"first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:434
 #, no-c-format
-msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
+msgid ""
+"During hardware detection &d-i; checks if any of the drivers for the "
+"hardware devices in your system require firmware to be loaded. If any "
+"firmware is requested but unavailable, a dialog will be displayed that "
+"allows the missing firmware to be loaded from a removable medium. See <xref "
+"linkend=\"loading-firmware\"/> for further details."
 msgstr ""
 
 #. Tag: title
@@ -478,43 +638,75 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:451
 #, no-c-format
-msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system."
+msgid ""
+"One of the first things &d-i; does, is to check available memory. If the "
+"available memory is limited, this component will make some changes in the "
+"installation process which hopefully will allow you to install &debian-gnu; "
+"on your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:458
 #, no-c-format
-msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
+msgid ""
+"The first measure taken to reduce memory consumption by the installer is to "
+"disable translations, which means that the installation can only be done in "
+"English. Of course, you can still localize the installed system after the "
+"installation has completed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:465
 #, no-c-format
-msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
+msgid ""
+"If that is not sufficient, the installer will further reduce memory "
+"consumption by loading only those components essential to complete a basic "
+"installation. This reduces the functionality of the installation system. You "
+"will be given the opportunity to load additional components manually, but "
+"you should be aware that each component you select will use additional "
+"memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:474
 #, no-c-format
-msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
+msgid ""
+"If the installer runs in low memory mode, it is recommended to create a "
+"relatively large swap partition (64&ndash;128MB). The swap partition will be "
+"used as virtual memory and thus increases the amount of memory available to "
+"the system. The installer will activate the swap partition as early as "
+"possible in the installation process. Note that heavy use of swap will "
+"reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:484
 #, no-c-format
-msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
+msgid ""
+"Despite these measures, it is still possible that your system freezes, that "
+"unexpected errors occur or that processes are killed by the kernel because "
+"the system runs out of memory (which will result in <quote>Out of memory</"
+"quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:491
 #, no-c-format
-msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
+msgid ""
+"For example, it has been reported that creating a big ext3 file system fails "
+"in low memory mode when there is insufficient swap space. If a larger swap "
+"doesn't help, try creating the file system as ext2 (which is an essential "
+"component of the installer) instead. It is possible to change an ext2 "
+"partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:499
 #, no-c-format
-msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
+msgid ""
+"It is possible to force the installer to use a higher lowmem level than the "
+"one based on available memory by using the boot parameter <quote>lowmem</"
+"quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
@@ -526,61 +718,116 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:516
 #, no-c-format
-msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, location and locales."
+msgid ""
+"In most cases the first questions you will be asked concern the selection of "
+"localization options to be used both for the installation and for the "
+"installed system. The localization options consist of language, location and "
+"locales."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:523
 #, no-c-format
-msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
+msgid ""
+"The language you choose will be used for the rest of the installation "
+"process, provided a translation of the different dialogs is available. If no "
+"valid translation is available for the selected language, the installer will "
+"default to English."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:530
 #, no-c-format
-msgid "The selected geographic location (in most cases a country) will be used later in the installation process to select the correct time zone and a &debian; mirror appropriate for that country. Language and country together will help determine the default locale for your system and select the correct keyboard layout."
+msgid ""
+"The selected geographic location (in most cases a country) will be used "
+"later in the installation process to select the correct time zone and a "
+"&debian; mirror appropriate for that country. Language and country together "
+"will help determine the default locale for your system and select the "
+"correct keyboard layout."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:538
 #, no-c-format
-msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
+msgid ""
+"You will first be asked to select your preferred language. The language "
+"names are listed both in English (left side) and in the language itself "
+"(right side); the names on the right side are also shown in the proper "
+"script for the language. The list is sorted on the English names. At the top "
+"of the list is an extra option that allows you to select the <quote>C</"
+"quote> locale instead of a language. Choosing the <quote>C</quote> locale "
+"will result in the installation proceding in English; the installed system "
+"will have no localization support as the <classname>locales</classname> "
+"package will not be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:550
 #, no-c-format
-msgid "Next you will be asked to select your geographic location. If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
+msgid ""
+"Next you will be asked to select your geographic location. If you selected a "
+"language that is recognized as an official language for more than one "
+"country<footnote> <para> In technical terms: where multiple locales exist "
+"for that language with differing country codes. </para> </footnote>, you "
+"will be shown a list of only those countries. To select a country that is "
+"not in that list, choose <guimenuitem>other</guimenuitem> (the last option). "
+"You will then be presented with a list of continents; selecting a continent "
+"will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:567
 #, no-c-format
-msgid "If the language has only one country associated with it, a list of countries will be displayed for the continent or region the country belongs to, with that country selected as the default. Use the <guibutton>Go Back</guibutton> option to select countries on a different continent."
+msgid ""
+"If the language has only one country associated with it, a list of countries "
+"will be displayed for the continent or region the country belongs to, with "
+"that country selected as the default. Use the <guibutton>Go Back</guibutton> "
+"option to select countries on a different continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:574
 #, no-c-format
-msgid "It is important to select the country where you live or where you are located as it determines the time zone that will be configured for the installed system."
+msgid ""
+"It is important to select the country where you live or where you are "
+"located as it determines the time zone that will be configured for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:580
 #, no-c-format
-msgid "If you selected a combination of language and country for which no locale is defined and there exist multiple locales for the language, then the installer will allow you to choose which of those locales you prefer as the default locale for the installed system<footnote> <para> At medium and low priority you can always select your preferred locale from those available for the selected language (if there's more than one). </para> </footnote>. In all other cases a default locale will be selected based on the selected language and country."
+msgid ""
+"If you selected a combination of language and country for which no locale is "
+"defined and there exist multiple locales for the language, then the "
+"installer will allow you to choose which of those locales you prefer as the "
+"default locale for the installed system<footnote> <para> At medium and low "
+"priority you can always select your preferred locale from those available "
+"for the selected language (if there's more than one). </para> </footnote>. "
+"In all other cases a default locale will be selected based on the selected "
+"language and country."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:595
 #, no-c-format
-msgid "Any default locale selected as described in the previous paragraph will use <firstterm>UTF-8</firstterm> as character encoding."
+msgid ""
+"Any default locale selected as described in the previous paragraph will use "
+"<firstterm>UTF-8</firstterm> as character encoding."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:600
 #, no-c-format
-msgid "If you are installing at low priority, you will have the option of selecting additional locales, including so-called <quote>legacy</quote> locales<footnote> <para> Legacy locales are locales which do not use UTF-8, but one of the older standards for character encoding such as ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by Japanese). </para> </footnote>, to be generated for the installed system; if you do, you will be asked which of the selected locales should be the default for the installed system."
+msgid ""
+"If you are installing at low priority, you will have the option of selecting "
+"additional locales, including so-called <quote>legacy</quote> "
+"locales<footnote> <para> Legacy locales are locales which do not use UTF-8, "
+"but one of the older standards for character encoding such as "
+"ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by "
+"Japanese). </para> </footnote>, to be generated for the installed system; if "
+"you do, you will be asked which of the selected locales should be the "
+"default for the installed system."
 msgstr ""
 
 #. Tag: title
@@ -592,13 +839,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:626
 #, no-c-format
-msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>dpkg-reconfigure keyboard-configuration</command> as root after you have completed the installation)."
+msgid ""
+"Keyboards are often tailored to the characters used in a language. Select a "
+"layout that conforms to the keyboard you are using, or select something "
+"close if the keyboard layout you want isn't represented. Once the system "
+"installation is complete, you'll be able to select a keyboard layout from a "
+"wider range of choices (run <command>dpkg-reconfigure keyboard-"
+"configuration</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:636
 #, no-c-format
-msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration."
+msgid ""
+"Move the highlight to the keyboard selection you desire and press "
+"&enterkey;. Use the arrow keys to move the highlight &mdash; they are in the "
+"same place in all national language keyboard layouts, so they are "
+"independent of the keyboard configuration."
 msgstr ""
 
 #. Tag: title
@@ -610,25 +867,51 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:664
 #, no-c-format
-msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the &debian; Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
+msgid ""
+"When installing via the <emphasis>hd-media</emphasis> method, there will be "
+"a moment where you need to find and mount the &debian; Installer iso image "
+"in order to get the rest of the installation files. The component "
+"<command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:671
 #, no-c-format
-msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid &debian; iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
+msgid ""
+"At first, <command>iso-scan</command> automatically mounts all block devices "
+"(e.g. partitions) which have some known filesystem on them and sequentially "
+"searches for filenames ending with <filename>.iso</filename> (or <filename>."
+"ISO</filename> for that matter). Beware that the first attempt scans only "
+"files in the root directory and in the first level of subdirectories (i.e. "
+"it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, "
+"<filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not "
+"<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). "
+"After an iso image has been found, <command>iso-scan</command> checks its "
+"content to determine if the image is a valid &debian; iso image or not. In "
+"the former case we are done, in the latter <command>iso-scan</command> seeks "
+"for another image."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:688
 #, no-c-format
-msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
+msgid ""
+"In case the previous attempt to find an installer iso image fails, "
+"<command>iso-scan</command> will ask you whether you would like to perform a "
+"more thorough search. This pass doesn't just look into the topmost "
+"directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:695
 #, no-c-format
-msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
+msgid ""
+"If <command>iso-scan</command> does not discover your installer iso image, "
+"reboot back to your original operating system and check if the image is "
+"named correctly (ending in <filename>.iso</filename>), if it is placed on a "
+"filesystem recognizable by &d-i;, and if it is not corrupted (verify the "
+"checksum). Experienced Unix users could do this without rebooting on the "
+"second console."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +923,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:718
 #, no-c-format
-msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
+msgid ""
+"As you enter this step, if the system detects that you have more than one "
+"network device, you'll be asked to choose which device will be your "
+"<emphasis>primary</emphasis> network interface, i.e. the one which you want "
+"to use for installation. The other interfaces won't be configured at this "
+"time. You may configure additional interfaces after installation is "
+"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> "
+"<manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: title
@@ -652,7 +942,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:733
 #, no-c-format
-msgid "By default, &d-i; tries to configure your computer's network automatically as far as possible. If the automatic configuration fails, that may be caused by many factors ranging from an unplugged network cable to missing infrastructure for automatic configuration. For further explanation in case of errors, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. Sometimes the network services used for autoconfiguration can be slow in their responses, so if you are sure everything is in place, simply start the autoconfiguration attempt again. If autoconfiguration fails repeatedly, you can instead choose the manual network setup."
+msgid ""
+"By default, &d-i; tries to configure your computer's network automatically "
+"as far as possible. If the automatic configuration fails, that may be caused "
+"by many factors ranging from an unplugged network cable to missing "
+"infrastructure for automatic configuration. For further explanation in case "
+"of errors, check the error messages on the fourth console. In any case, you "
+"will be asked if you want to retry, or if you want to perform a manual "
+"setup. Sometimes the network services used for autoconfiguration can be slow "
+"in their responses, so if you are sure everything is in place, simply start "
+"the autoconfiguration attempt again. If autoconfiguration fails repeatedly, "
+"you can instead choose the manual network setup."
 msgstr ""
 
 #. Tag: title
@@ -664,13 +964,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:753
 #, no-c-format
-msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network name</quote>) and a <computeroutput>WEP key</computeroutput> or <computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
+msgid ""
+"The manual network setup in turn asks you a number of questions about your "
+"network, notably <computeroutput>IP address</computeroutput>, "
+"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</"
+"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and "
+"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a "
+"wireless network interface, you will be asked to provide your "
+"<computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network "
+"name</quote>) and a <computeroutput>WEP key</computeroutput> or "
+"<computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers "
+"from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:769
 #, no-c-format
-msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
+msgid ""
+"Some technical details you might, or might not, find handy: the program "
+"assumes the network IP address is the bitwise-AND of your system's IP "
+"address and your netmask. The default broadcast address is calculated as the "
+"bitwise OR of your system's IP address with the bitwise negation of the "
+"netmask. It will also guess your gateway. If you can't find any of these "
+"answers, use the offered defaults &mdash; if necessary, you can change them "
+"by editing <filename>/etc/network/interfaces</filename> once the system has "
+"been installed."
 msgstr ""
 
 #. Tag: title
@@ -682,13 +1000,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:785
 #, no-c-format
-msgid "From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
+msgid ""
+"From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 "
+"as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and "
+"IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:791
 #, no-c-format
-msgid "Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration using NDP (Neighbor Discovery Protocol, including recursive DNS server (RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed stateless/stateful autoconfiguration (address configuration via NDP, additional parameters via DHCPv6)."
+msgid ""
+"Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration "
+"Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration "
+"using NDP (Neighbor Discovery Protocol, including recursive DNS server "
+"(RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed "
+"stateless/stateful autoconfiguration (address configuration via NDP, "
+"additional parameters via DHCPv6)."
 msgstr ""
 
 #. Tag: title
@@ -700,7 +1027,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:839
 #, no-c-format
-msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
+msgid ""
+"The installer will first attempt to connect to a time server on the Internet "
+"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set "
+"the system time. If this does not succeed, the installer will assume the "
+"time and date obtained from the system clock when the installation system "
+"was booted are correct. It is not possible to manually set the system time "
+"during the installation process."
 msgstr ""
 
 #. Tag: para
@@ -712,25 +1045,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:861
 #, no-c-format
-msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone."
+msgid ""
+"Depending on the location selected earlier in the installation process, you "
+"may be shown a list of time zones relevant for that location. If your "
+"location has only one time zone and you are doing a default installation, "
+"you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:869
 #, no-c-format
-msgid "In expert mode or when installing at medium priority, you will have the additional option to select <quote>Coordinated Universal Time</quote> (UTC) as time zone."
+msgid ""
+"In expert mode or when installing at medium priority, you will have the "
+"additional option to select <quote>Coordinated Universal Time</quote> (UTC) "
+"as time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:875
 #, no-c-format
-msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
+msgid ""
+"If for some reason you wish to set a time zone for the installed system that "
+"does <emphasis>not</emphasis> match the selected location, there are two "
+"options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:886
 #, no-c-format
-msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:"
+msgid ""
+"The simplest option is to just select a different time zone after the "
+"installation has been completed and you've booted into the new system. The "
+"command to do this is:"
 msgstr ""
 
 #. Tag: screen
@@ -742,13 +1088,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:898
 #, no-c-format
-msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
+msgid ""
+"Alternatively, the time zone can be set at the very start of the "
+"installation by passing the parameter <userinput>time/"
+"zone=<replaceable>value</replaceable></userinput> when you boot the "
+"installation system. The value should of course be a valid time zone, for "
+"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:912
 #, no-c-format
-msgid "For automated installations the time zone can be set to any desired value using preseeding."
+msgid ""
+"For automated installations the time zone can be set to any desired value "
+"using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -760,7 +1113,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:927
 #, no-c-format
-msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
+msgid ""
+"Just before configuring the clock, the installer will allow you to set up "
+"the <quote>root</quote> account and/or an account for the first user. Other "
+"user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
@@ -772,19 +1128,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:945
 #, no-c-format
-msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
+msgid ""
+"The <emphasis>root</emphasis> account is also called the <emphasis>super-"
+"user</emphasis>; it is a login that bypasses all security protection on your "
+"system. The root account should only be used to perform system "
+"administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:953
 #, no-c-format
-msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
+msgid ""
+"Any password you create should contain at least 6 characters, and should "
+"contain both upper- and lower-case characters, as well as punctuation "
+"characters. Take extra care when setting your root password, since it is "
+"such a powerful account. Avoid dictionary words or use of any personal "
+"information which could be guessed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:961
 #, no-c-format
-msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
+msgid ""
+"If anyone ever tells you they need your root password, be extremely wary. "
+"You should normally never give your root password out, unless you are "
+"administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
@@ -796,25 +1164,42 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:973
 #, no-c-format
-msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
+msgid ""
+"The system will ask you whether you wish to create an ordinary user account "
+"at this point. This account should be your main personal log-in. You should "
+"<emphasis>not</emphasis> use the root account for daily use or as your "
+"personal login."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:982
 #, no-c-format
-msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
+msgid ""
+"Why not? Well, one reason to avoid using root's privileges is that it is "
+"very easy to do irreparable damage as root. Another reason is that you might "
+"be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; "
+"that is a program that takes advantage of your super-user powers to "
+"compromise the security of your system behind your back. Any good book on "
+"Unix system administration will cover this topic in more detail &mdash; "
+"consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:992
 #, no-c-format
-msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
+msgid ""
+"You will first be prompted for the user's full name. Then you'll be asked "
+"for a name for the user account; generally your first name or something "
+"similar will suffice and indeed will be the default. Finally, you will be "
+"prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:999
 #, no-c-format
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgid ""
+"If at any point after installation you would like to create another account, "
+"use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
@@ -826,28 +1211,45 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1011
 #, no-c-format
-msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
+msgid ""
+"At this time, after hardware detection has been executed a final time, &d-i; "
+"should be at its full strength, customized for the user's needs and ready to "
+"do some real work. As the title of this section indicates, the main task of "
+"the next few components lies in partitioning your disks, creating "
+"filesystems, assigning mountpoints and optionally configuring closely "
+"related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1032
 #, no-c-format
-msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
+msgid ""
+"If you are uncomfortable with partitioning, or just want to know more "
+"details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1038
 #, no-c-format
 msgid ""
-      "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
-      "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n"
-      "</screen></informalexample> Note that this will make any existing data on that disk inaccessible."
+"If a hard disk has previously used under Solaris, the partitioner may not "
+"detect the size of the drive correctly. Creating a new partition table does "
+"not fix this issue. What does help, is to <quote>zero</quote> the first few "
+"sectors of the drive: <informalexample><screen>\n"
+"# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; "
+"sync\n"
+"</screen></informalexample> Note that this will make any existing data on "
+"that disk inaccessible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1051
 #, no-c-format
-msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"First you will be given the opportunity to automatically partition either an "
+"entire drive, or available free space on a drive. This is also called "
+"<quote>guided</quote> partitioning. If you do not want to autopartition, "
+"choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
@@ -859,19 +1261,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1062
 #, no-c-format
-msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
+msgid ""
+"The partitioner used in &d-i; is fairly versatile. It allows to create many "
+"different partitioning schemes, using various partition tables, file systems "
+"and advanced block devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1068
 #, no-c-format
-msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
+msgid ""
+"Exactly which options are available depends mainly on the architecture, but "
+"also on other factors. For example, on systems with limited internal memory "
+"some options may not be available. Defaults may vary as well. The type of "
+"partition table used by default can for example be different for large "
+"capacity hard disks than for smaller hard disks. Some options can only be "
+"changed when installing at medium or low debconf priority; at higher "
+"priorities sensible defaults will be used."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1079
 #, no-c-format
-msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
+msgid ""
+"The installer supports various forms of advanced partitioning and use of "
+"storage devices, which in many cases can be used in combination."
 msgstr ""
 
 #. Tag: emphasis
@@ -901,13 +1315,18 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1096
 #, no-c-format
-msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
+msgid ""
+"<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1098
 #, no-c-format
-msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
+msgid ""
+"Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support "
+"for Serial ATA RAID is currently only available if enabled when the "
+"installer is booted. Further information is available on <ulink url=\"&url-d-"
+"i-sataraid;\">our Wiki</ulink>."
 msgstr ""
 
 #. Tag: para
@@ -919,7 +1338,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1106
 #, no-c-format
-msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
+msgid ""
+"See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. "
+"Support for multipath is currently only available if enabled when the "
+"installer is booted."
 msgstr ""
 
 #. Tag: para
@@ -931,13 +1353,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1118
 #, no-c-format
-msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></phrase>"
+msgid ""
+"<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> "
+"<emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</"
+"emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></"
+"phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1123
 #, no-c-format
-msgid "The default file system selected in most cases is ext3; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
+msgid ""
+"The default file system selected in most cases is ext3; for <filename>/boot</"
+"filename> partitions ext2 will be selected by default when guided "
+"partitioning is used."
 msgstr ""
 
 #. Tag: para
@@ -973,37 +1402,59 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1141
 #, no-c-format
-msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:"
+msgid ""
+"As ZFS support in the installer is still in development, only a basic subset "
+"of ZFS features are supported. Some of them can be enabled manually after "
+"the initial install, but there are some caveats:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1146
 #, no-c-format
-msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the <quote>zfs create</quote> command."
+msgid ""
+"Each ZFS pool will host only one filesystem. After install is finished, more "
+"filesystems can be created on this pool by using the <quote>zfs create</"
+"quote> command."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1151
 #, no-c-format
-msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the <quote>zpool add</quote> command, or into a mirrored pool by using the <quote>zpool attach</quote> command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system."
+msgid ""
+"Each ZFS pool will be composed of exactly one partition. After install is "
+"finished, a single-device ZFS pool can be converted into a multi-device pool "
+"by using the <quote>zpool add</quote> command, or into a mirrored pool by "
+"using the <quote>zpool attach</quote> command. However, you shouldn't do "
+"this on the pool that hosts root filesystem, as it would prevent GRUB from "
+"booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1159
 #, no-c-format
-msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the <quote>compression</quote> property via the <quote>zfs set</quote> command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system."
+msgid ""
+"Compression is not currently supported. After the install is finished, "
+"compression can be enabled by setting the <quote>compression</quote> "
+"property via the <quote>zfs set</quote> command. However, if a compression "
+"algorithm other than the default (lzjb) is used on the pool that hosts your "
+"root filesystem, this may prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1168
 #, no-c-format
-msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
+msgid ""
+"<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1170
 #, no-c-format
-msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
+msgid ""
+"Support for the Reiser file system is no longer available by default. When "
+"the installer is running at medium or low debconf priority it can be enabled "
+"by selecting the <classname>partman-reiserfs</classname> component. Only "
+"version 3 of the file system is supported."
 msgstr ""
 
 #. Tag: emphasis
@@ -1015,7 +1466,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1178
 #, no-c-format
-msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
+msgid ""
+"Used on some systems to read flash memory. It is not possible to create new "
+"jffs2 partitions."
 msgstr ""
 
 #. Tag: emphasis
@@ -1027,7 +1480,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1184
 #, no-c-format
-msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
+msgid ""
+"Existing partitions will be recognized and it is possible to assign mount "
+"points for them. It is not possible to create new qnx4 partitions."
 msgstr ""
 
 #. Tag: para
@@ -1045,7 +1500,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1193
 #, no-c-format
-msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
+msgid ""
+"Existing NTFS partitions can be resized and it is possible to assign mount "
+"points for them. It is not possible to create new NTFS partitions."
 msgstr ""
 
 #. Tag: title
@@ -1057,49 +1514,89 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1204
 #, no-c-format
-msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
+msgid ""
+"If you choose guided partitioning, you may have three options: to create "
+"partitions directly on the hard disk (classic method), or to create them "
+"using Logical Volume Management (LVM), or to create them using encrypted "
+"LVM<footnote> <para> The installer will encrypt the LVM volume group using a "
+"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> "
+"support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1219
 #, no-c-format
-msgid "The option to use (encrypted) LVM may not be available on all architectures."
+msgid ""
+"The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1224
 #, no-c-format
-msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
+msgid ""
+"When using LVM or encrypted LVM, the installer will create most partitions "
+"inside one big partition; the advantage of this method is that partitions "
+"inside this big partition can be resized relatively easily later. In the "
+"case of encrypted LVM the big partition will not be readable without knowing "
+"a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1233
 #, no-c-format
-msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
+msgid ""
+"When using encrypted LVM, the installer will also automatically erase the "
+"disk by writing random data to it. This further improves security (as it "
+"makes it impossible to tell which parts of the disk are in use and also "
+"makes sure that any traces of previous installations are erased), but may "
+"take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1242
 #, no-c-format
-msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
+msgid ""
+"If you choose guided partitioning using LVM or encrypted LVM, some changes "
+"in the partition table will need to be written to the selected disk while "
+"LVM is being set up. These changes effectively erase all data that is "
+"currently on the selected hard disk and you will not be able to undo them "
+"later. However, the installer will ask you to confirm these changes before "
+"they are written to disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1252
 #, no-c-format
-msgid "If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
+msgid ""
+"If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic "
+"or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked "
+"to select the disk you want to use. Check that all your disks are listed "
+"and, if you have several disks, make sure you select the correct one. The "
+"order they are listed in may differ from what you are used to. The size of "
+"the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1261
 #, no-c-format
-msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. <phrase arch=\"linux-any\"> If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. </phrase>"
+msgid ""
+"Any data on the disk you select will eventually be lost, but you will always "
+"be asked to confirm any changes before they are written to the disk. <phrase "
+"arch=\"linux-any\"> If you have selected the classic method of partitioning, "
+"you will be able to undo any changes right until the end; when using "
+"(encrypted) LVM this is not possible. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1271
 #, no-c-format
-msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
+msgid ""
+"Next, you will be able to choose from the schemes listed in the table below. "
+"All schemes have their pros and cons, some of which are discussed in <xref "
+"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in "
+"mind that guided partitioning needs a certain minimal amount of free space "
+"to operate with. If you don't give it at least about 1GB of space (depends "
+"on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
@@ -1171,54 +1668,79 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1307
 #, no-c-format
-msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
+msgid ""
+"<filename>/</filename>, <filename>/home</filename>, <filename>/usr</"
+"filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1316
 #, no-c-format
-msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
+msgid ""
+"If you choose guided partitioning using (encrypted) LVM, the installer will "
+"also create a separate <filename>/boot</filename> partition. The other "
+"partitions, including the swap partition, will be created inside the LVM "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1322
 #, no-c-format
-msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
+msgid ""
+"If you choose guided partitioning for your IA-64 system, there will be an "
+"additional partition, formatted as a FAT16 bootable filesystem, for the EFI "
+"boot loader. There is also an additional menu item in the formatting menu to "
+"manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1330
 #, no-c-format
-msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
+msgid ""
+"After selecting a scheme, the next screen will show your new partition "
+"table, including information on whether and how partitions will be formatted "
+"and where they will be mounted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1336
 #, no-c-format
 msgid ""
-      "The list of partitions might look like this: <informalexample><screen>\n"
-      "  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
-      "        #1 primary   16.4 MB  B f ext2       /boot\n"
-      "        #2 primary  551.0 MB      swap       swap\n"
-      "        #3 primary    5.8 GB      ntfs\n"
-      "           pri/log    8.2 MB      FREE SPACE\n"
-      "\n"
-      "  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
-      "        #1 primary   15.9 MB      ext3\n"
-      "        #2 primary  996.0 MB      fat16\n"
-      "        #3 primary    3.9 GB      xfs        /home\n"
-      "        #5 logical    6.0 GB    f ext3       /\n"
-      "        #6 logical    1.0 GB    f ext3       /var\n"
-      "        #7 logical  498.8 MB      ext3\n"
-      "        #8 logical  551.5 MB      swap       swap\n"
-      "        #9 logical   65.8 GB      ext2\n"
-      "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning."
+"The list of partitions might look like this: <informalexample><screen>\n"
+"  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
+"        #1 primary   16.4 MB  B f ext2       /boot\n"
+"        #2 primary  551.0 MB      swap       swap\n"
+"        #3 primary    5.8 GB      ntfs\n"
+"           pri/log    8.2 MB      FREE SPACE\n"
+"\n"
+"  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
+"        #1 primary   15.9 MB      ext3\n"
+"        #2 primary  996.0 MB      fat16\n"
+"        #3 primary    3.9 GB      xfs        /home\n"
+"        #5 logical    6.0 GB    f ext3       /\n"
+"        #6 logical    1.0 GB    f ext3       /var\n"
+"        #7 logical  498.8 MB      ext3\n"
+"        #8 logical  551.5 MB      swap       swap\n"
+"        #9 logical   65.8 GB      ext2\n"
+"</screen></informalexample> This example shows two IDE harddrives divided "
+"into several partitions; the first disk has some free space. Each partition "
+"line consists of the partition number, its type, size, optional flags, file "
+"system, and mountpoint (if any). Note: this particular setup cannot be "
+"created using guided partitioning but it does show possible variation that "
+"can be achieved using manual partitioning."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1349
 #, no-c-format
-msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
+msgid ""
+"This concludes the guided partitioning. If you are satisfied with the "
+"generated partition table, you can choose <guimenuitem>Finish partitioning "
+"and write changes to disk</guimenuitem> from the menu to implement the new "
+"partition table (as described at the end of this section). If you are not "
+"happy, you can choose to <guimenuitem>Undo changes to partitions</"
+"guimenuitem> and run guided partitioning again, or modify the proposed "
+"changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
@@ -1230,49 +1752,101 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1364
 #, no-c-format
-msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
+msgid ""
+"A similar screen to the one shown just above will be displayed if you choose "
+"manual partitioning except that your existing partition table will be shown "
+"and without the mount points. How to manually set up your partition table "
+"and the usage of partitions by your new &debian; system will be covered in "
+"the remainder of this section."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1372
 #, no-c-format
-msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
+msgid ""
+"If you select a pristine disk which has neither partitions nor free space on "
+"it, you will be asked if a new partition table should be created (this is "
+"needed so you can create new partitions). After this, a new line entitled "
+"<quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1380
 #, no-c-format
-msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file system,</phrase> or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap,<phrase arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
+msgid ""
+"If you select some free space, you will have the opportunity to create a new "
+"partition. You will have to answer a quick series of questions about its "
+"size, type (primary or logical), and location (beginning or end of the free "
+"space). After this, you will be presented with a detailed overview of your "
+"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which "
+"determines if the partition will have a file system on it, or be used for "
+"swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file "
+"system,</phrase> or not be used at all. Other settings include mountpoint, "
+"mount options, and bootable flag; which settings are shown depends on how "
+"the partition is to be used. If you don't like the preselected defaults, "
+"feel free to change them to your liking. E.g. by selecting the option "
+"<guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem "
+"for this partition, including options to use the partition for swap,<phrase "
+"arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. "
+"Another nice feature is the ability to copy data from an existing partition "
+"onto this one. When you are satisfied with your new partition, select "
+"<guimenuitem>Done setting up the partition</guimenuitem> and you will return "
+"to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1402
 #, no-c-format
-msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
+msgid ""
+"If you decide you want to change something about your partition, simply "
+"select the partition, which will bring you to the partition configuration "
+"menu. This is the same screen as is used when creating a new partition, so "
+"you can change the same settings. One thing that may not be very obvious at "
+"a first glance is that you can resize the partition by selecting the item "
+"displaying the size of the partition. Filesystems known to work are at least "
+"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1413
 #, no-c-format
-msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
+msgid ""
+"Be sure to create at least two partitions: one for the <emphasis>root</"
+"emphasis> filesystem (which must be mounted as <filename>/</filename>) and "
+"one for <emphasis>swap</emphasis>. If you forget to mount the root "
+"filesystem, <command>partman</command> won't let you continue until you "
+"correct this issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1421
 #, no-c-format
-msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
+msgid ""
+"If you forget to select and format an EFI boot partition, <command>partman</"
+"command> will detect this and will not let you continue until you allocate "
+"one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1427
 #, no-c-format
-msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
+msgid ""
+"Capabilities of <command>partman</command> can be extended with installer "
+"modules, but are dependent on your system's architecture. So if you can't "
+"see all promised goodies, check if you have loaded all required modules (e."
+"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or "
+"<filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1435
 #, no-c-format
-msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
+msgid ""
+"After you are satisfied with partitioning, select <guimenuitem>Finish "
+"partitioning and write changes to disk</guimenuitem> from the partitioning "
+"menu. You will be presented with a summary of changes made to the disks and "
+"asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
@@ -1284,19 +1858,82 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1464
 #, no-c-format
-msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
+msgid ""
+"If you have more than one harddrive<footnote><para> To be honest, you can "
+"construct an MD device even from partitions residing on single physical "
+"drive, but that won't give any benefits. </para></footnote> in your "
+"computer, you can use <command>mdcfg</command> to set up your drives for "
+"increased performance and/or better reliability of your data. The result is "
+"called <firstterm>Multidisk Device</firstterm> (or after its most famous "
+"variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1477
 #, no-c-format
-msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
+msgid ""
+"MD is basically a bunch of partitions located on different disks and "
+"combined together to form a <emphasis>logical</emphasis> device. This device "
+"can then be used like an ordinary partition (i.e. in <command>partman</"
+"command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1485
 #, no-c-format
-msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
+msgid ""
+"What benefits this brings depends on the type of MD device you are creating. "
+"Currently supported are: <variablelist> <varlistentry> <term>RAID0</"
+"term><listitem><para> Is mainly aimed at performance. RAID0 splits all "
+"incoming data into <firstterm>stripes</firstterm> and distributes them "
+"equally over each disk in the array. This can increase the speed of read/"
+"write operations, but when one of the disks fails, you will lose "
+"<emphasis>everything</emphasis> (part of the information is still on the "
+"healthy disk(s), the other part <emphasis>was</emphasis> on the failed "
+"disk). </para><para> The typical use for RAID0 is a partition for video "
+"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</"
+"term><listitem><para> Is suitable for setups where reliability is the first "
+"concern. It consists of several (usually two) equally-sized partitions where "
+"every partition contains exactly the same data. This essentially means three "
+"things. First, if one of your disks fails, you still have the data mirrored "
+"on the remaining disks. Second, you can use only a fraction of the available "
+"capacity (more precisely, it is the size of the smallest partition in the "
+"RAID). Third, file-reads are load-balanced among the disks, which can "
+"improve performance on a server, such as a file server, that tends to be "
+"loaded with more disk reads than writes. </para><para> Optionally you can "
+"have a spare disk in the array which will take the place of the failed disk "
+"in the case of failure. </para></listitem> </varlistentry> <varlistentry> "
+"<term>RAID5</term><listitem><para> Is a good compromise between speed, "
+"reliability and data redundancy. RAID5 splits all incoming data into stripes "
+"and distributes them equally on all but one disk (similar to RAID0). Unlike "
+"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which "
+"gets written on the remaining disk. The parity disk is not static (that "
+"would be called RAID4), but is changing periodically, so the parity "
+"information is distributed equally on all disks. When one of the disks "
+"fails, the missing part of information can be computed from remaining data "
+"and its parity. RAID5 must consist of at least three active partitions. "
+"Optionally you can have a spare disk in the array which will take the place "
+"of the failed disk in the case of failure. </para><para> As you can see, "
+"RAID5 has a similar degree of reliability to RAID1 while achieving less "
+"redundancy. On the other hand, it might be a bit slower on write operations "
+"than RAID0 due to computation of parity information. </para></listitem> </"
+"varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar "
+"to RAID5 except that it uses two parity devices instead of one. </"
+"para><para> A RAID6 array can survive up to two disk failures. </para></"
+"listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> "
+"RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It "
+"creates <replaceable>n</replaceable> copies of incoming data and distributes "
+"them across the partitions so that none of the copies of the same data are "
+"on the same device. The default value of <replaceable>n</replaceable> is 2, "
+"but it can be set to something else in expert mode. The number of partitions "
+"used must be at least <replaceable>n</replaceable>. RAID10 has different "
+"layouts for distributing the copies. The default is near copies. Near copies "
+"have all of the copies at about the same offset on all of the disks. Far "
+"copies have the copies at different offsets on the disks. Offset copies copy "
+"the stripe, not the individual copies. </para><para> RAID10 can be used to "
+"achieve reliability and redundancy without the drawback of having to "
+"calculate parity. </para></listitem> </varlistentry> </variablelist> To sum "
+"it up:"
 msgstr ""
 
 #. Tag: entry
@@ -1392,7 +2029,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1629
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus one)"
 msgstr ""
 
 #. Tag: entry
@@ -1410,7 +2049,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1640
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus two)"
 msgstr ""
 
 #. Tag: entry
@@ -1422,79 +2063,140 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1651
 #, no-c-format
-msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
+msgid ""
+"Total of all partitions divided by the number of chunk copies (defaults to "
+"two)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1658
 #, no-c-format
-msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
+msgid ""
+"If you want to know more about Software RAID, have a look at <ulink url="
+"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1663
 #, no-c-format
-msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
+msgid ""
+"To create an MD device, you need to have the desired partitions it should "
+"consist of marked for use in a RAID. (This is done in <command>partman</"
+"command> in the <guimenu>Partition settings</guimenu> menu where you should "
+"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume "
+"for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1672
 #, no-c-format
-msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
+msgid ""
+"Make sure that the system can be booted with the partitioning scheme you are "
+"planning. In general it will be necessary to create a separate file system "
+"for <filename>/boot</filename> when using RAID for the root (<filename>/</"
+"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including "
+"lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using "
+"for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</"
+"filename> can be an option."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1684
 #, no-c-format
-msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
+msgid ""
+"Support for MD is a relatively new addition to the installer. You may "
+"experience problems for some RAID levels and in combination with some "
+"bootloaders if you try to use MD for the root (<filename>/</filename>) file "
+"system. For experienced users, it may be possible to work around some of "
+"these problems by executing some configuration or installation steps "
+"manually from a shell."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1693
 #, no-c-format
-msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
+msgid ""
+"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> "
+"from the main <command>partman</command> menu. (The menu will only appear "
+"after you mark at least one partition for use as <guimenuitem>physical "
+"volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</"
+"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will "
+"be presented with a list of supported types of MD devices, from which you "
+"should choose one (e.g. RAID1). What follows depends on the type of MD you "
+"selected."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1706
 #, no-c-format
-msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
+msgid ""
+"RAID0 is simple &mdash; you will be issued with the list of available RAID "
+"partitions and your only task is to select the partitions which will form "
+"the MD."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1713
 #, no-c-format
-msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
+msgid ""
+"RAID1 is a bit more tricky. First, you will be asked to enter the number of "
+"active devices and the number of spare devices which will form the MD. Next, "
+"you need to select from the list of available RAID partitions those that "
+"will be active and then those that will be spare. The count of selected "
+"partitions must be equal to the number provided earlier. Don't worry. If you "
+"make a mistake and select a different number of partitions, &d-i; won't let "
+"you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1725
 #, no-c-format
-msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+msgid ""
+"RAID5 has a setup procedure similar to RAID1 with the exception that you "
+"need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1731
 #, no-c-format
-msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
+msgid ""
+"RAID6 also has a setup procedure similar to RAID1 except that at least "
+"<emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1737
 #, no-c-format
-msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
+msgid ""
+"RAID10 again has a setup procedure similar to RAID1 except in expert mode. "
+"In expert mode, &d-i; will ask you for the layout. The layout has two parts. "
+"The first part is the layout type. It is either <literal>n</literal> (for "
+"near copies), <literal>f</literal> (for far copies), or <literal>o</literal> "
+"(for offset copies). The second part is the number of copies to make of the "
+"data. There must be at least that many active devices so that all of the "
+"copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1751
 #, no-c-format
-msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
+msgid ""
+"It is perfectly possible to have several types of MD at once. For example, "
+"if you have three 200 GB hard drives dedicated to MD, each containing two "
+"100 GB partitions, you can combine the first partitions on all three disks "
+"into the RAID0 (fast 300 GB video editing partition) and use the other three "
+"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition "
+"for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1760
 #, no-c-format
-msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
+msgid ""
+"After you set up MD devices to your liking, you can <guimenuitem>Finish</"
+"guimenuitem> <command>mdcfg</command> to return back to the "
+"<command>partman</command> to create filesystems on your new MD devices and "
+"assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
@@ -1506,37 +2208,70 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1776
 #, no-c-format
-msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
+msgid ""
+"If you are working with computers at the level of system administrator or "
+"<quote>advanced</quote> user, you have surely seen the situation where some "
+"disk partition (usually the most important one) was short on space, while "
+"some other partition was grossly underused and you had to manage this "
+"situation by moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1784
 #, no-c-format
-msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
+msgid ""
+"To avoid the described situation you can use Logical Volume Manager (LVM). "
+"Simply said, with LVM you can combine your partitions (<firstterm>physical "
+"volumes</firstterm> in LVM lingo) to form a virtual disk (so called "
+"<firstterm>volume group</firstterm>), which can then be divided into virtual "
+"partitions (<firstterm>logical volumes</firstterm>). The point is that "
+"logical volumes (and of course underlying volume groups) can span across "
+"several physical disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1794
 #, no-c-format
-msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
+msgid ""
+"Now when you realize you need more space for your old 160GB <filename>/home</"
+"filename> partition, you can simply add a new 300GB disk to the computer, "
+"join it with your existing volume group and then resize the logical volume "
+"which holds your <filename>/home</filename> filesystem and voila &mdash; "
+"your users have some room again on their renewed 460GB partition. This "
+"example is of course a bit oversimplified. If you haven't read it yet, you "
+"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1805
 #, no-c-format
-msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
+msgid ""
+"LVM setup in &d-i; is quite simple and completely supported inside "
+"<command>partman</command>. First, you have to mark the partition(s) to be "
+"used as physical volumes for LVM. This is done in the <guimenu>Partition "
+"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:"
+"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1814
 #, no-c-format
-msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
+msgid ""
+"When you return to the main <command>partman</command> screen, you will see "
+"a new option <guimenuitem>Configure the Logical Volume Manager</"
+"guimenuitem>. When you select that, you will first be asked to confirm "
+"pending changes to the partition table (if any) and after that the LVM "
+"configuration menu will be shown. Above the menu a summary of the LVM "
+"configuration is shown. The menu itself is context sensitive and only shows "
+"valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1825
 #, no-c-format
-msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
+msgid ""
+"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device "
+"structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1578,19 +2313,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1847
 #, no-c-format
-msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
+msgid ""
+"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</"
+"command> screen"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1853
 #, no-c-format
-msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
+msgid ""
+"Use the options in that menu to first create a volume group and then create "
+"your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1858
 #, no-c-format
-msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
+msgid ""
+"After you return to the main <command>partman</command> screen, any created "
+"logical volumes will be displayed in the same way as ordinary partitions "
+"(and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
@@ -1602,37 +2344,76 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1873
 #, no-c-format
-msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
+msgid ""
+"&d-i; allows you to set up encrypted partitions. Every file you write to "
+"such a partition is immediately saved to the device in encrypted form. "
+"Access to the encrypted data is granted only after entering the "
+"<firstterm>passphrase</firstterm> used when the encrypted partition was "
+"originally created. This feature is useful to protect sensitive data in case "
+"your laptop or hard drive gets stolen. The thief might get physical access "
+"to the hard drive, but without knowing the right passphrase, the data on the "
+"hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1885
 #, no-c-format
-msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+msgid ""
+"The two most important partitions to encrypt are: the home partition, where "
+"your private data resides, and the swap partition, where sensitive data "
+"might be stored temporarily during operation. Of course, nothing prevents "
+"you from encrypting any other partitions that might be of interest. For "
+"example <filename>/var</filename> where database servers, mail servers or "
+"print servers store their data, or <filename>/tmp</filename> which is used "
+"by various programs to store potentially interesting temporary files. Some "
+"people may even want to encrypt their whole system. The only exception is "
+"the <filename>/boot</filename> partition which must remain unencrypted, "
+"because currently there is no way to load the kernel from an encrypted "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1900
 #, no-c-format
-msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
+msgid ""
+"Please note that the performance of encrypted partitions will be less than "
+"that of unencrypted ones because the data needs to be decrypted or encrypted "
+"for every read or write. The performance impact depends on your CPU speed, "
+"chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1907
 #, no-c-format
-msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
+msgid ""
+"To use encryption, you have to create a new partition by selecting some free "
+"space in the main partitioning menu. Another option is to choose an existing "
+"partition (e.g. a regular partition, an LVM logical volume or a RAID "
+"volume). In the <guimenu>Partition settings</guimenu> menu, you need to "
+"select <guimenuitem>physical volume for encryption</guimenuitem> at the "
+"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will "
+"then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1918
 #, no-c-format
-msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+msgid ""
+"&d-i; supports several encryption methods. The default method is "
+"<firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to "
+"host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> "
+"(older, maintained separately from the Linux kernel tree). Unless you have "
+"compelling reasons to do otherwise, it is recommended to use the default."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1930
 #, no-c-format
-msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid ""
+"First, let's have a look at the options available when you select "
+"<userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As "
+"always: when in doubt, use the defaults, because they have been carefully "
+"chosen with security in mind."
 msgstr ""
 
 #. Tag: term
@@ -1644,7 +2425,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1942
 #, no-c-format
-msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
+msgid ""
+"This option lets you select the encryption algorithm (<firstterm>cipher</"
+"firstterm>) which will be used to encrypt the data on the partition. &d-i; "
+"currently supports the following block ciphers: <firstterm>aes</firstterm>, "
+"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and "
+"<firstterm>twofish</firstterm>. It is beyond the scope of this document to "
+"discuss the qualities of these different algorithms, however, it might help "
+"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by "
+"the American National Institute of Standards and Technology as the standard "
+"encryption algorithm for protecting sensitive information in the 21st "
+"century."
 msgstr ""
 
 #. Tag: term
@@ -1656,7 +2447,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1962
 #, no-c-format
-msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
+msgid ""
+"Here you can specify the length of the encryption key. With a larger key "
+"size, the strength of the encryption is generally improved. On the other "
+"hand, increasing the length of the key usually has a negative impact on "
+"performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
@@ -1668,13 +2463,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1976
 #, no-c-format
-msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
+msgid ""
+"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</"
+"firstterm> algorithm is used in cryptography to ensure that applying the "
+"cipher on the same <firstterm>clear text</firstterm> data with the same key "
+"always produces a unique <firstterm>cipher text</firstterm>. The idea is to "
+"prevent the attacker from deducing information from repeated patterns in the "
+"encrypted data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1986
 #, no-c-format
-msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
+msgid ""
+"From the provided alternatives, the default <userinput>cbc-essiv:sha256</"
+"userinput> is currently the least vulnerable to known attacks. Use the other "
+"alternatives only when you need to ensure compatibility with some previously "
+"installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
@@ -1698,7 +2503,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2007
 #, no-c-format
-msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
+msgid ""
+"The encryption key will be computed<footnote> <para> Using a passphrase as "
+"the key currently means that the partition will be set up using <ulink url="
+"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase "
+"which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
@@ -1710,13 +2519,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2023
 #, no-c-format
-msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
+msgid ""
+"A new encryption key will be generated from random data each time you try to "
+"bring up the encrypted partition. In other words: on every shutdown the "
+"content of the partition will be lost as the key is deleted from memory. (Of "
+"course, you could try to guess the key with a brute force attack, but unless "
+"there is an unknown weakness in the cipher algorithm, it is not achievable "
+"in our lifetime.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2032
 #, no-c-format
-msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
+msgid ""
+"Random keys are useful for swap partitions because you do not need to bother "
+"yourself with remembering the passphrase or wiping sensitive information "
+"from the swap partition before shutting down your computer. However, it also "
+"means that you will <emphasis>not</emphasis> be able to use the "
+"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels "
+"as it will be impossible (during a subsequent boot) to recover the suspended "
+"data written to the swap partition."
 msgstr ""
 
 #. Tag: term
@@ -1728,13 +2550,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2053
 #, no-c-format
-msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
+msgid ""
+"Determines whether the content of this partition should be overwritten with "
+"random data before setting up the encryption. This is recommended because it "
+"might otherwise be possible for an attacker to discern which parts of the "
+"partition are in use and which are not. In addition, this will make it "
+"harder to recover any leftover data from previous "
+"installations<footnote><para> It is believed that the guys from three-letter "
+"agencies can restore the data even after several rewrites of the "
+"magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2073
 #, no-c-format
-msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
+msgid ""
+"If you select <menuchoice> <guimenu>Encryption method:</guimenu> "
+"<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu "
+"changes to provide the following options:"
 msgstr ""
 
 #. Tag: term
@@ -1746,7 +2579,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2084
 #, no-c-format
-msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
+msgid ""
+"For loop-AES, unlike dm-crypt, the options for cipher and key size are "
+"combined, so you can select both at the same time. Please see the above "
+"sections on ciphers and key sizes for further information."
 msgstr ""
 
 #. Tag: term
@@ -1770,7 +2606,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2103
 #, no-c-format
-msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
+msgid ""
+"The encryption key will be generated from random data during the "
+"installation. Moreover this key will be encrypted with <application>GnuPG</"
+"application>, so to use it, you will need to enter the proper passphrase "
+"(you will be asked to provide one later in the process)."
 msgstr ""
 
 #. Tag: para
@@ -1788,50 +2628,93 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2139
 #, no-c-format
-msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
+msgid ""
+"After you have selected the desired parameters for your encrypted "
+"partitions, return back to the main partitioning menu. There should now be a "
+"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After "
+"you select it, you will be asked to confirm the deletion of data on "
+"partitions marked to be erased and possibly other actions such as writing a "
+"new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2149
 #, no-c-format
-msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
+msgid ""
+"Next you will be asked to enter a passphrase for partitions configured to "
+"use one. Good passphrases should be longer than 8 characters, should be a "
+"mixture of letters, numbers and other characters and should not contain "
+"common dictionary words or information easily associable with you (such as "
+"birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2158
 #, no-c-format
-msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
+msgid ""
+"Before you input any passphrases, you should have made sure that your "
+"keyboard is configured correctly and generates the expected characters. If "
+"you are unsure, you can switch to the second virtual console and type some "
+"text at the prompt. This ensures that you won't be surprised later, e.g. by "
+"trying to input a passphrase using a qwerty keyboard layout when you used an "
+"azerty layout during the installation. This situation can have several "
+"causes. Maybe you switched to another keyboard layout during the "
+"installation, or the selected keyboard layout might not have been set up yet "
+"when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2171
 #, no-c-format
-msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
+msgid ""
+"If you selected to use methods other than a passphrase to create encryption "
+"keys, they will be generated now. Because the kernel may not have gathered a "
+"sufficient amount of entropy at this early stage of the installation, the "
+"process may take a long time. You can help speed up the process by "
+"generating entropy: e.g. by pressing random keys, or by switching to the "
+"shell on the second virtual console and generating some network and disk "
+"traffic (downloading some files, feeding big files into <filename>/dev/null</"
+"filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2187
 #, no-c-format
 msgid ""
-      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
-      "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
-      "     #1 115.1 GB  F ext3\n"
-      "\n"
-      "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-      "     #1 515.2 MB  F ext3\n"
-      "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you."
+"After returning to the main partitioning menu, you will see all encrypted "
+"volumes as additional partitions which can be configured in the same way as "
+"ordinary partitions. The following example shows two different volumes. The "
+"first one is encrypted via dm-crypt, the second one via loop-AES. "
+"<informalexample><screen>\n"
+"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux "
+"device-mapper\n"
+"     #1 115.1 GB  F ext3\n"
+"\n"
+"Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
+"     #1 515.2 MB  F ext3\n"
+"</screen></informalexample> Now is the time to assign mount points to the "
+"volumes and optionally change the file system types if the defaults do not "
+"suit you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2200
 #, no-c-format
-msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+msgid ""
+"Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</"
+"replaceable> and <replaceable>loop0</replaceable> in this case) and the "
+"mount points you assigned to each encrypted volume. You will need this "
+"information later when booting the new system. The differences between the "
+"ordinary boot process and the boot process with encryption involved will be "
+"covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2210
 #, no-c-format
-msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
+msgid ""
+"Once you are satisfied with the partitioning scheme, continue with the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -1843,37 +2726,63 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2222
 #, no-c-format
-msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
+msgid ""
+"Although this stage is the least problematic, it consumes a significant "
+"fraction of the install because it downloads, verifies and unpacks the whole "
+"base system. If you have a slow computer or network connection, this could "
+"take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2235
 #, no-c-format
-msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"During installation of the base system, package unpacking and setup messages "
+"are redirected to <userinput>tty4</userinput>. You can access this terminal "
+"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></"
+"keycombo>; get back to the main installer process with "
+"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2244
 #, no-c-format
-msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
+msgid ""
+"The unpack/setup messages generated during this phase are also saved in "
+"<filename>/var/log/syslog</filename>. You can check them there if the "
+"installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2250
 #, no-c-format
-msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
+msgid ""
+"As part of the installation, a &arch-kernel; kernel will be installed. At "
+"the default priority, the installer will choose one for you that best "
+"matches your hardware. In lower priority modes, you will be able to choose "
+"from a list of available kernels."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2257
 #, no-c-format
-msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
+msgid ""
+"When packages are installed using the package management system, it will by "
+"default also install packages that are recommended by those packages. "
+"Recommended packages are not strictly required for the core functionality of "
+"the selected software, but they do enhance that software and should, in the "
+"view of the package maintainers, normally be installed together with that "
+"software."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2267
 #, no-c-format
-msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
+msgid ""
+"For technical reasons packages installed during the installation of the base "
+"system are installed without their <quote>Recommends</quote>. The rule "
+"described above only takes effect after this point in the installation "
+"process."
 msgstr ""
 
 #. Tag: title
@@ -1885,7 +2794,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2280
 #, no-c-format
-msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
+msgid ""
+"At this point you have a usable but limited system. Most users will want to "
+"install additional software on the system to tune it to their needs, and the "
+"installer allows you do so. This step can take even longer than installing "
+"the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
@@ -1897,25 +2810,55 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2297
 #, no-c-format
-msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
+msgid ""
+"One of the tools used to install packages on a &debian-gnu; system is a "
+"program called <command>apt-get</command>, from the <classname>apt</"
+"classname> package<footnote> <para> Note that the program which actually "
+"installs the packages is called <command>dpkg</command>. However, this "
+"program is more of a low-level tool. <command>apt-get</command> is a higher-"
+"level tool, which will invoke <command>dpkg</command> as appropriate. It "
+"knows how to retrieve packages from your CD, the network, or wherever. It is "
+"also able to automatically install other packages which are required to make "
+"the package you're trying to install work correctly. </para> </footnote>. "
+"Other front-ends for package management, like <command>aptitude</command> "
+"and <command>synaptic</command>, are also in use. These front-ends are "
+"recommended for new users, since they integrate some additional features "
+"(package searching and status checks) in a nice user interface. In fact, "
+"<command>aptitude</command> is now the recommended utility for package "
+"management."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2321
 #, no-c-format
-msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
+msgid ""
+"<command>apt</command> must be configured so that it knows from where to "
+"retrieve packages. The results of this configuration are written to the file "
+"<filename>/etc/apt/sources.list</filename>. You can examine and edit this "
+"file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2328
 #, no-c-format
-msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
+msgid ""
+"If you are installing at default priority, the installer will largely take "
+"care of the configuration automatically, based on the installation method "
+"you are using and possibly using choices made earlier in the installation. "
+"In most cases the installer will automatically add a security mirror and, if "
+"you are installing the stable distribution, a mirror for the "
+"<quote>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2337
 #, no-c-format
-msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
+msgid ""
+"If you are installing at a lower priority (e.g. in expert mode), you will be "
+"able to make more decisions yourself. You can choose whether or not to use "
+"the security and/or volatile update services, and you can choose to add "
+"packages from the <quote>contrib</quote> and <quote>non-free</quote> "
+"sections of the archive."
 msgstr ""
 
 #. Tag: title
@@ -1927,37 +2870,64 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2350
 #, no-c-format
-msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
+msgid ""
+"If you are installing from a CD or a DVD that is part of a larger set, the "
+"installer will ask if you want to scan additional CDs or DVDs. If you have "
+"additional CDs or DVDs available, you probably want to do this so the "
+"installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2357
 #, no-c-format
-msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
+msgid ""
+"If you do not have any additional CDs or DVDs, that is no problem: using "
+"them is not required. If you also do not use a network mirror (as explained "
+"in the next section), it can mean that not all packages belonging to the "
+"tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2365
 #, no-c-format
-msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
+msgid ""
+"Packages are included on CDs (and DVDs) in the order of their popularity. "
+"This means that for most uses only the first CDs in a set are needed and "
+"that only very few people actually use any of the packages included on the "
+"last CDs in a set."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2372
 #, no-c-format
-msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
+msgid ""
+"It also means that buying or downloading and burning a full CD set is just a "
+"waste of money as you'll never use most of them. In most cases you are "
+"better off getting only the first 3 to 8 CDs and installing any additional "
+"packages you may need from the Internet by using a mirror. The same goes for "
+"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2381
 #, no-c-format
-msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
+msgid ""
+"A good rule of thumb is that for a regular desktop installation (using the "
+"GNOME desktop environment) only the first three CDs are needed. For the "
+"alternative desktop environments (KDE or Xfce), additional CDs are needed. "
+"The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2389
 #, no-c-format
-msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
+msgid ""
+"If you do scan multiple CDs or DVDs, the installer will prompt you to "
+"exchange them when it needs packages from another CD/DVD than the one "
+"currently in the drive. Note that only CDs or DVDs that belong to the same "
+"set should be scanned. The order in which they are scanned does not really "
+"matter, but scanning them in ascending order will reduce the chance of "
+"mistakes."
 msgstr ""
 
 #. Tag: title
@@ -1969,37 +2939,67 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2404
 #, no-c-format
-msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
+msgid ""
+"One question that will be asked during most installs is whether or not to "
+"use a network mirror as a source for packages. In most cases the default "
+"answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2410
 #, no-c-format
-msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
+msgid ""
+"If you are <emphasis>not</emphasis> installing from a full CD or DVD or "
+"using a full CD/DVD image, you really should use a network mirror as "
+"otherwise you will end up with only a very minimal system. However, if you "
+"have a limited Internet connection it is best <emphasis>not</emphasis> to "
+"select the <literal>desktop</literal> task in the next step of the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2419
 #, no-c-format
-msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
+msgid ""
+"If you are installing from a single full CD or using a full CD image, using "
+"a network mirror is not required, but is still strongly recommended because "
+"a single CD contains only a fairly limited number of packages. If you have a "
+"limited Internet connection it may still be best to <emphasis>not</emphasis> "
+"select a network mirror here, but to finish the installation using only "
+"what's available on the CD and selectively install additional packages after "
+"the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2430
 #, no-c-format
-msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
+msgid ""
+"If you are installing from a DVD or using a DVD image, any packages needed "
+"during the installation should be present on the first DVD. The same is true "
+"if you have scanned multiple CDs as explained in the previous section. Use "
+"of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2437
 #, no-c-format
-msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
+msgid ""
+"One advantage of adding a network mirror is that updates that have occurred "
+"since the CD/DVD set was created and have been included in a point release, "
+"will become available for installation, thus extending the life of your CD/"
+"DVD set without compromising the security or stability of the installed "
+"system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2444
 #, no-c-format
-msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
+msgid ""
+"In summary: selecting a network mirror is generally a good idea, except if "
+"you do not have a good Internet connection. If the current version of a "
+"package is available from CD/DVD, the installer will always use that. The "
+"amount of data that will be downloaded if you do select a mirror thus "
+"depends on"
 msgstr ""
 
 #. Tag: para
@@ -2017,19 +3017,27 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2463
 #, no-c-format
-msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
+msgid ""
+"which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2468
 #, no-c-format
-msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
+msgid ""
+"whether any updated versions of packages included on the CDs or DVDs are "
+"available from a mirror (either a regular package mirror, or a mirror for "
+"security or volatile updates)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2477
 #, no-c-format
-msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
+msgid ""
+"Note that the last point means that, even if you choose not to use a network "
+"mirror, some packages may still be downloaded from the Internet if there is "
+"a security or volatile update available for them and those services have "
+"been configured."
 msgstr ""
 
 #. Tag: title
@@ -2041,19 +3049,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2489
 #, no-c-format
-msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine."
+msgid ""
+"If you have selected to use a network mirror during the installation "
+"(optional for CD/DVD installs, required for netboot images), you will be "
+"presented with a list of geographically nearby (and therefore hopefully "
+"fast) network mirrors, based upon your country selection earlier in the "
+"installation process. Choosing the offered default is usually fine."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2497
 #, no-c-format
-msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one."
+msgid ""
+"If your computer is on an IPv6-only network (which is probably not the case "
+"for the vast majority of users), using the default mirror for your country "
+"might not work. All the mirrors in the list are reachable via IPv4, but only "
+"some of them can be used via IPv6. As connectivity of individual mirrors can "
+"change over time, this information is not available in the installer. If "
+"there is no IPv6 connectivity for the default mirror for your country, you "
+"can either try some of the other mirrors offered to you or choose the "
+"<quote>enter information manually</quote> option. You can then specify "
+"<quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for "
+"a mirror available via IPv6, although it will probably not be the fastest "
+"possible one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2511
 #, no-c-format
-msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
+msgid ""
+"Another option when choosing to specify the mirror manually is to use "
+"<quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</"
+"quote> is not a physical mirror but a mirror redirection service, i.e. it "
+"automatically refers your system to a real mirror near you in terms of "
+"network topology. It takes into account by which protocol you connect to it, "
+"i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
 msgstr ""
 
 #. Tag: title
@@ -2065,85 +3095,165 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2532
 #, no-c-format
-msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
+msgid ""
+"During the installation process, you are given the opportunity to select "
+"additional software to install. Rather than picking individual software "
+"packages from the &num-of-distrib-pkgs; available packages, this stage of "
+"the installation process focuses on selecting and installing predefined "
+"collections of software to quickly set up your computer to perform various "
+"tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2541
 #, no-c-format
-msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
+msgid ""
+"So, you have the ability to choose <emphasis>tasks</emphasis> first, and "
+"then add on more individual packages later. These tasks loosely represent a "
+"number of different jobs or things you want to do with your computer, such "
+"as <quote>Desktop environment</quote>, <quote>Web server</quote>, or "
+"<quote>Print server</quote><footnote> <para> You should know that to present "
+"this list, the installer is merely invoking the <command>tasksel</command> "
+"program. It can be run at any time after installation to install more "
+"packages (or remove them), or you can use a more fine-grained tool such as "
+"<command>aptitude</command>. If you are looking for a specific single "
+"package, after installation is complete, simply run <userinput>aptitude "
+"install <replaceable>package</replaceable></userinput>, where "
+"<replaceable>package</replaceable> is the name of the package you are "
+"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> "
+"lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2568
 #, no-c-format
-msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
+msgid ""
+"Some tasks may be pre-selected based on the characteristics of the computer "
+"you are installing. If you disagree with these selections you can deselect "
+"them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2575
 #, no-c-format
-msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+msgid ""
+"In the standard user interface of the installer, you can use the space bar "
+"to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2581
 #, no-c-format
-msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
+msgid ""
+"Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop "
+"environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2586
 #, no-c-format
-msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using <literal>desktop=xfce</literal> or <literal>desktop=lxde</literal>."
+msgid ""
+"It is not possible to interactively select a different desktop during the "
+"installation. However, it <emphasis>is</emphasis> possible to get &d-i; to "
+"install a KDE desktop environment instead of GNOME by using preseeding (see "
+"<xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter "
+"<literal>desktop=kde</literal> at the boot prompt when starting the "
+"installer. Alternatively the more lightweight Xfce and LXDE desktop "
+"environments can be selected by using <literal>desktop=xfce</literal> or "
+"<literal>desktop=lxde</literal>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2597
 #, no-c-format
-msgid "Some CD images (netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>."
+msgid ""
+"Some CD images (netinst and DVD) also allow selection of the desired desktop "
+"environment from the graphical boot menu. Select the <quote>Advanced "
+"options</quote> option in the main menu and look for <quote>Alternative "
+"desktop environments</quote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2604
 #, no-c-format
-msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method."
+msgid ""
+"Note that this will only work if the packages needed for the desired desktop "
+"environment are actually available. If you are installing using a single "
+"full CD image, they will need to be downloaded from a mirror as most needed "
+"packages are only included on later CDs; installing KDE, Xfce or LXDE this "
+"way should work fine if you are using a DVD image or any other installation "
+"method."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2614
 #, no-c-format
-msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
+msgid ""
+"The various server tasks will install software roughly as follows. DNS "
+"server: <classname>bind9</classname>; File server: <classname>samba</"
+"classname>, <classname>nfs</classname>; Mail server: <classname>exim4</"
+"classname>, <classname>spamassassin</classname>, <classname>uw-imap</"
+"classname>; Print server: <classname>cups</classname>; SQL database: "
+"<classname>postgresql</classname>; Web server: <classname>apache2</"
+"classname>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2625
 #, no-c-format
-msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system."
+msgid ""
+"The <quote>Standard system</quote> task will install any package that has a "
+"priority <quote>standard</quote>. This includes a lot of common utilities "
+"that are normally available on any Linux or Unix system. You should leave "
+"this task selected unless you know what you are doing and want a really "
+"minimal system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2633
 #, no-c-format
-msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)."
+msgid ""
+"If during language selection a default locale other than the <quote>C</"
+"quote> locale was selected, <command>tasksel</command> will check if any "
+"localization tasks are defined for that locale and will automatically try to "
+"install relevant localization packages. This includes for example packages "
+"containing word lists or special fonts for your language. If a desktop "
+"environment was selected, it will also install appropriate localization "
+"packages for that (if available)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2643
 #, no-c-format
-msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
+msgid ""
+"Once you've selected your tasks, select &BTN-CONT;. At this point, "
+"<command>aptitude</command> will install the packages that are part of the "
+"selected tasks. If a particular program needs more information from the "
+"user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2650
 #, no-c-format
-msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
+msgid ""
+"You should be aware that especially the Desktop task is very large. "
+"Especially when installing from a normal CD-ROM in combination with a mirror "
+"for packages not on the CD-ROM, the installer may want to retrieve a lot of "
+"packages over the network. If you have a relatively slow Internet "
+"connection, this can take a long time. There is no option to cancel the "
+"installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2659
 #, no-c-format
-msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
+msgid ""
+"Even when packages are included on the CD-ROM, the installer may still "
+"retrieve them from the mirror if the version available on the mirror is more "
+"recent than the one included on the CD-ROM. If you are installing the stable "
+"distribution, this can happen after a point release (an update of the "
+"original stable release); if you are installing the testing distribution "
+"this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: title
@@ -2155,7 +3265,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2676
 #, no-c-format
-msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
+msgid ""
+"If you are installing a diskless workstation, obviously, booting off the "
+"local disk isn't a meaningful option, and this step will be skipped. <phrase "
+"arch=\"sparc\">You may wish to set OpenBoot to boot from the network by "
+"default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -2167,13 +3281,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2693
 #, no-c-format
-msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;."
+msgid ""
+"Before a boot loader is installed, the installer will attempt to probe for "
+"other operating systems which are installed on the machine. If it finds a "
+"supported operating system, you will be informed of this during the boot "
+"loader installation step, and the computer will be configured to boot this "
+"other operating system in addition to &debian;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2701
 #, no-c-format
-msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
+msgid ""
+"Note that multiple operating systems booting on a single machine is still "
+"something of a black art. The automatic support for detecting and setting up "
+"boot loaders to boot other operating systems varies by architecture and even "
+"by subarchitecture. If it does not work you should consult your boot "
+"manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
@@ -2185,7 +3309,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2720
 #, no-c-format
-msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
+msgid ""
+"The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is "
+"similar in configuration and usage to <command>LILO</command>, with a few "
+"exceptions. First of all, <command>PALO</command> allows you to boot any "
+"kernel image on your boot partition. This is because <command>PALO</command> "
+"can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
@@ -2203,19 +3332,28 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2743
 #, no-c-format
-msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
+msgid ""
+"The main &architecture; boot loader is called <quote>grub</quote>. Grub is a "
+"flexible and robust boot loader and a good default choice for new users and "
+"old hands alike."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2749
 #, no-c-format
-msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
+msgid ""
+"By default, grub will be installed into the Master Boot Record (MBR), where "
+"it will take over complete control of the boot process. If you prefer, you "
+"can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2755
 #, no-c-format
-msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
+msgid ""
+"If you do not want to install grub, use the &BTN-GOBACK; button to get to "
+"the main menu, and from there select whatever bootloader you would like to "
+"use."
 msgstr ""
 
 #. Tag: title
@@ -2227,19 +3365,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2770
 #, no-c-format
-msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
+msgid ""
+"The second &architecture; boot loader is called <quote>LILO</quote>. It is "
+"an old complex program which offers lots of functionality, including DOS, "
+"Windows, and OS/2 boot management. Please carefully read the instructions in "
+"the directory <filename>/usr/share/doc/lilo/</filename> if you have special "
+"needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2780
 #, no-c-format
-msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
+msgid ""
+"Currently the LILO installation will only create menu entries for other "
+"operating systems if these can be <firstterm>chainloaded</firstterm>. This "
+"means you may have to manually add a menu entry for operating systems like "
+"GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2788
 #, no-c-format
-msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
+msgid ""
+"&d-i; offers you three choices on where to install the <command>LILO</"
+"command> boot loader:"
 msgstr ""
 
 #. Tag: term
@@ -2251,7 +3400,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2795
 #, no-c-format
-msgid "This way the <command>LILO</command> will take complete control of the boot process."
+msgid ""
+"This way the <command>LILO</command> will take complete control of the boot "
+"process."
 msgstr ""
 
 #. Tag: term
@@ -2263,7 +3414,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2802
 #, no-c-format
-msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader."
+msgid ""
+"Choose this if you want to use another boot manager. <command>LILO</command> "
+"will install itself at the beginning of the new &debian; partition and it "
+"will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
@@ -2275,13 +3429,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2811
 #, no-c-format
-msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+msgid ""
+"Useful for advanced users who want to install <command>LILO</command> "
+"somewhere else. In this case you will be asked for desired location. You can "
+"use traditional device names such as <filename>/dev/hda</filename> or "
+"<filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2821
 #, no-c-format
-msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into &debian;!"
+msgid ""
+"If you can no longer boot into Windows 9x (or DOS) after this step, you'll "
+"need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /"
+"mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; "
+"however, this means that you'll need to use some other way to get back into "
+"&debian;!"
 msgstr ""
 
 #. Tag: title
@@ -2293,13 +3456,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2839
 #, no-c-format
-msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
+msgid ""
+"The &architecture; boot loader is called <quote>elilo</quote>. It is modeled "
+"on the <quote>lilo</quote> boot loader for the x86 architecture and uses a "
+"similar configuration file. However, instead of writing an MBR or partition "
+"boot record to the disk, it copies the necessary files to a separate FAT "
+"formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</"
+"guimenuitem> menu in the firmware to point to the files in the EFI "
+"partition. The <command>elilo</command> boot loader is really in two parts. "
+"The <filename>/usr/sbin/elilo</filename> command manages the partition and "
+"copies files into it. The <filename>elilo.efi</filename> program is copied "
+"into the EFI partition and then run by the <quote>EFI Boot Manager</quote> "
+"to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2855
 #, no-c-format
-msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
+msgid ""
+"The <quote>elilo</quote> configuration and installation is done as the last "
+"step of installing the packages of the base installation. &d-i; will present "
+"you with a list of potential disk partitions that it has found suitable for "
+"an EFI partition. Select the partition you set up earlier in the "
+"installation, typically a partition on the same disk that contains your "
+"<emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2311,7 +3491,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2869
 #, no-c-format
-msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
+msgid ""
+"The criterion for selecting a partition is that it must be a FAT format "
+"filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show "
+"multiple choices depending on what it finds from scanning all of the disks "
+"of the system including EFI partitions of other system disks and EFI "
+"diagnostic partitions. Remember, <command>elilo</command> may format the "
+"partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
@@ -2323,7 +3509,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2886
 #, no-c-format
-msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
+msgid ""
+"The EFI partition is a FAT filesystem format partition on one of the hard "
+"disks of the system, usually the same disk that contains the <emphasis>root</"
+"emphasis> filesystem. It is normally not mounted on a running system as it "
+"is only needed by the <quote>EFI Boot Manager</quote> to load the system and "
+"the installer part of the <command>elilo</command> writes to the filesystem "
+"directly. The <command>/usr/sbin/elilo</command> utility writes the "
+"following files into the <filename>efi/debian</filename> directory of the "
+"EFI partition during the installation. Note that the <quote>EFI Boot "
+"Manager</quote> would find these files using the path "
+"<filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may "
+"be other files in this filesystem as well over time as the system is updated "
+"or re-configured."
 msgstr ""
 
 #. Tag: filename
@@ -2335,7 +3533,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2909
 #, no-c-format
-msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
+msgid ""
+"This is the configuration file read by the boot loader when it starts. It is "
+"a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-"
+"written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
@@ -2347,7 +3548,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2919
 #, no-c-format
-msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
+msgid ""
+"This is the boot loader program that the <quote>EFI Boot Manager</quote> "
+"runs to boot the system. It is the program behind the <guimenuitem>&debian; "
+"GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> "
+"command menu."
 msgstr ""
 
 #. Tag: filename
@@ -2359,7 +3564,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2930
 #, no-c-format
-msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
+msgid ""
+"This is the initial root filesystem used to boot the kernel. It is a copy of "
+"the file referenced in the <filename>/etc/elilo.conf</filename>. In a "
+"standard &debian; installation it would be the file in <filename>/boot</"
+"filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
@@ -2371,7 +3580,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2943
 #, no-c-format
-msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
+msgid ""
+"This is a small text file warning you that the contents of the directory are "
+"managed by the <command>elilo</command> and that any local changes would be "
+"lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
@@ -2383,7 +3595,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2954
 #, no-c-format
-msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
+msgid ""
+"This is the compressed kernel itself. It is a copy of the file referenced in "
+"the <filename>/etc/elilo.conf</filename>. In a standard &debian; "
+"installation it would be the file in <filename>/boot</filename> pointed to "
+"by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
@@ -2396,13 +3612,25 @@ msgstr ""
 #: using-d-i.xml:2975
 #, no-c-format
 msgid ""
-      "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
-      "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
-      "<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n"
-      "<userinput> setenv OSLoader arcboot</userinput>\n"
-      "<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n"
-      "<userinput> setenv AutoLoad yes</userinput>\n"
-      "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
+"The boot loader on SGI machines is <command>arcboot</command>. It has to be "
+"installed on the same hard disk as the kernel (this is done automatically by "
+"the installer). Arcboot supports different configurations which are set up "
+"in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique "
+"name, the default setup as created by the installer is <quote>linux</quote>. "
+"After arcboot has been installed, the system can be booted from hard disk by "
+"setting some firmware environment variables entering "
+"<informalexample><screen>\n"
+"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
+"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</"
+"replaceable>)</userinput>\n"
+"<userinput> setenv OSLoader arcboot</userinput>\n"
+"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></"
+"userinput>\n"
+"<userinput> setenv AutoLoad yes</userinput>\n"
+"</screen></informalexample> on the firmware prompt, and then typing "
+"<command>boot</command>."
 msgstr ""
 
 #. Tag: replaceable
@@ -2414,7 +3642,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2995
 #, no-c-format
-msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
+msgid ""
+"is the SCSI bus to be booted from, this is <userinput>0</userinput> for the "
+"onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
@@ -2426,7 +3656,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3004
 #, no-c-format
-msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
+msgid ""
+"is the SCSI ID of the hard disk on which <command>arcboot</command> is "
+"installed"
 msgstr ""
 
 #. Tag: replaceable
@@ -2438,7 +3670,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3013
 #, no-c-format
-msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
+msgid ""
+"is the number of the partition on which <filename>/etc/arcboot.conf</"
+"filename> resides"
 msgstr ""
 
 #. Tag: replaceable
@@ -2450,7 +3684,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3022
 #, no-c-format
-msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
+msgid ""
+"is the name of the configuration entry in <filename>/etc/arcboot.conf</"
+"filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
@@ -2462,7 +3698,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3044
 #, no-c-format
-msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;."
+msgid ""
+"Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their "
+"boot loader. The installer will set up <command>yaboot</command> "
+"automatically, so all you need is a small 820k partition named "
+"<quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> "
+"created back in the partitioning component. If this step completes "
+"successfully then your disk should now be bootable and OpenFirmware will be "
+"set to boot &debian-gnu;."
 msgstr ""
 
 #. Tag: title
@@ -2474,7 +3717,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3063
 #, no-c-format
-msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
+msgid ""
+"The boot loader for OldWorld Power Macintosh machines is <command>quik</"
+"command>. You can also use it on CHRP. The installer will attempt to set up "
+"<command>quik</command> automatically. The setup has been known to work on "
+"7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
@@ -2486,7 +3733,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3080
 #, no-c-format
-msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
+msgid ""
+"The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. Please take a look at <quote>LINUX for &arch-title; "
+"Device Drivers and Installation Commands</quote> from IBM's developerWorks "
+"web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
@@ -2498,7 +3750,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3099
 #, no-c-format
-msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
+msgid ""
+"The standard &architecture; boot loader is called <quote>silo</quote>. It is "
+"documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. First of all, <command>SILO</command> allows you to "
+"boot any kernel image on your drive, even if it is not listed in <filename>/"
+"etc/silo.conf</filename>. This is because <command>SILO</command> can "
+"actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is "
+"read at boot time, so there is no need to rerun <command>silo</command> "
+"after installing a new kernel like you would with <command>LILO</command>. "
+"<command>SILO</command> can also read UFS partitions, which means it can "
+"boot SunOS/Solaris partitions as well. This is useful if you want to install "
+"GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
@@ -2510,13 +3774,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3126
 #, no-c-format
-msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)."
+msgid ""
+"This option can be used to complete the installation even when no boot "
+"loader is to be installed, either because the arch/subarch doesn't provide "
+"one, or because none is desired (e.g. you will use existing boot loader)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3133
 #, no-c-format
-msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
+msgid ""
+"If you plan to manually configure your bootloader, you should check the name "
+"of the installed kernel in <filename>/target/boot</filename>. You should "
+"also check that directory for the presence of an <firstterm>initrd</"
+"firstterm>; if one is present, you will probably have to instruct your "
+"bootloader to use it. Other information you will need are the disk and "
+"partition you selected for your <filename>/</filename> filesystem and, if "
+"you chose to install <filename>/boot</filename> on a separate partition, "
+"also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2528,7 +3803,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3151
 #, no-c-format
-msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
+msgid ""
+"This is the last step in the &debian; installation process during which the "
+"installer will do any last minute tasks. It mostly consists of tidying up "
+"after the &d-i;."
 msgstr ""
 
 #. Tag: title
@@ -2540,19 +3818,32 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3166
 #, no-c-format
-msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
+msgid ""
+"The installer may ask you if the computer's clock is set to UTC. Normally "
+"this question is avoided if possible and the installer tries to work out "
+"whether the clock is set to UTC based on things like what other operating "
+"systems are installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3173
 #, no-c-format
-msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
+msgid ""
+"In expert mode you will always be able to choose whether or not the clock is "
+"set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally "
+"set to local time. If you want to dual-boot, select local time instead of "
+"UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or "
+"Windows are normally set to local time. If you want to dual-boot, select "
+"local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3184
 #, no-c-format
-msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
+msgid ""
+"At this point &d-i; will also attempt to save the current time to the "
+"system's hardware clock. This will be done either in UTC or local time, "
+"depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
@@ -2564,13 +3855,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3201
 #, no-c-format
-msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system."
+msgid ""
+"You will be prompted to remove the boot media (CD, floppy, etc) that you "
+"used to boot the installer. After that the system will be rebooted into your "
+"new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3207
 #, no-c-format
-msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation."
+msgid ""
+"After a final prompt the system will be halted because rebooting is not "
+"supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD "
+"which you selected for the root filesystem during the first steps of the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2582,7 +3880,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3221
 #, no-c-format
-msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
+msgid ""
+"The components listed in this section are usually not involved in the "
+"installation process, but are waiting in the background to help the user in "
+"case something goes wrong."
 msgstr ""
 
 #. Tag: title
@@ -2594,13 +3895,21 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3236
 #, no-c-format
-msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system."
+msgid ""
+"If the installation is successful, the logfiles created during the "
+"installation process will be automatically saved to <filename>/var/log/"
+"installer/</filename> on your new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3243
 #, no-c-format
-msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
+msgid ""
+"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu "
+"allows you to save the log files to a floppy disk, network, hard disk, or "
+"other media. This can be useful if you encounter fatal problems during the "
+"installation and wish to study the logs on another system or attach them to "
+"an installation report."
 msgstr ""
 
 #. Tag: title
@@ -2612,7 +3921,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3265
 #, no-c-format
-msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
+msgid ""
+"There are several methods you can use to get a shell while running an "
+"installation. On most systems, and if you are not installing over serial "
+"console, the easiest method is to switch to the second <emphasis>virtual "
+"console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> "
+"<keycap>F2</keycap></keycombo><footnote> <para> That is: press the "
+"<keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</"
+"keycap> and the <keycap>F2</keycap> function key at the same time. </para> </"
+"footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</"
+"keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</"
+"keycap></keycombo> to switch back to the installer itself."
 msgstr ""
 
 #. Tag: para
@@ -2624,31 +3943,52 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3287
 #, no-c-format
-msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
+msgid ""
+"If you cannot switch consoles, there is also an <guimenuitem>Execute a "
+"Shell</guimenuitem> item on the main menu that can be used to start a shell. "
+"You can get to the main menu from most dialogs by using the &BTN-GOBACK; "
+"button one or more times. Type <userinput>exit</userinput> to close the "
+"shell and return to the installer."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3295
 #, no-c-format
-msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
+msgid ""
+"At this point you are booted from the RAM disk, and there is a limited set "
+"of Unix utilities available for your use. You can see what programs are "
+"available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</"
+"command> and by typing <command>help</command>. The shell is a Bourne shell "
+"clone called <command>ash</command> and has some nice features like "
+"autocompletion and history."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3304
 #, no-c-format
-msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
+msgid ""
+"To edit and view files, use the text editor <command>nano</command>. Log "
+"files for the installation system can be found in the <filename>/var/log</"
+"filename> directory."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3311
 #, no-c-format
-msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
+msgid ""
+"Although you can do basically anything in a shell that the available "
+"commands allow you to do, the option to use a shell is really only there in "
+"case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3317
 #, no-c-format
-msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
+msgid ""
+"Doing things manually from the shell may interfere with the installation "
+"process and result in errors or an incomplete installation. In particular, "
+"you should always use let the installer activate your swap partition and not "
+"do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
@@ -2660,70 +4000,146 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3335
 #, no-c-format
-msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
+msgid ""
+"One of the more interesting components is <firstterm>network-console</"
+"firstterm>. It allows you to do a large part of the installation over the "
+"network via SSH. The use of the network implies you will have to perform the "
+"first steps of the installation from the console, at least to the point of "
+"setting up the networking. (Although you can automate that part with <xref "
+"linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3345
 #, no-c-format
-msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
+msgid ""
+"This component is not loaded into the main installation menu by default, so "
+"you have to explicitly ask for it. If you are installing from CD, you need "
+"to boot with medium priority or otherwise invoke the main installation menu "
+"and choose <guimenuitem>Load installer components from CD</guimenuitem> and "
+"from the list of additional components select <guimenuitem>network-console: "
+"Continue installation remotely using SSH</guimenuitem>. Successful load is "
+"indicated by a new menu entry called <guimenuitem>Continue installation "
+"remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3358
 #, no-c-format
-msgid "For installations on &arch-title;, this is the default method after setting up the network."
+msgid ""
+"For installations on &arch-title;, this is the default method after setting "
+"up the network."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3363
 #, no-c-format
-msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely."
+msgid ""
+"<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> "
+"<phrase arch=\"s390\">You</phrase> will be asked for a new password to be "
+"used for connecting to the installation system and for its confirmation. "
+"That's all. Now you should see a screen which instructs you to login "
+"remotely as the user <emphasis>installer</emphasis> with the password you "
+"just provided. Another important detail to notice on this screen is the "
+"fingerprint of this system. You need to transfer the fingerprint securely to "
+"the person who will continue the installation remotely."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3375
 #, no-c-format
-msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
+msgid ""
+"Should you decide to continue with the installation locally, you can always "
+"press &enterkey;, which will bring you back to the main menu, where you can "
+"select another component."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3381
 #, no-c-format
 msgid ""
-      "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
-      "<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n"
-      "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct."
+"Now let's switch to the other side of the wire. As a prerequisite, you need "
+"to configure your terminal for UTF-8 encoding, because that is what the "
+"installation system uses. If you do not, remote installation will be still "
+"possible, but you may encounter strange display artefacts like destroyed "
+"dialog borders or unreadable non-ascii characters. Establishing a connection "
+"with the installation system is as simple as typing: "
+"<informalexample><screen>\n"
+"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</"
+"replaceable></userinput>\n"
+"</screen></informalexample> Where <replaceable>install_host</replaceable> is "
+"either the name or IP address of the computer being installed. Before the "
+"actual login the fingerprint of the remote system will be displayed and you "
+"will have to confirm that it is correct."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3398
 #, no-c-format
-msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
+msgid ""
+"The <command>ssh</command> server in the installer uses a default "
+"configuration that does not send keep-alive packets. In principle, a "
+"connection to the system being installed should be kept open indefinitely. "
+"However, in some situations &mdash; depending on your local network setup "
+"&mdash; the connection may be lost after some period of inactivity. One "
+"common case where this can happen is when there is some form of Network "
+"Address Translation (NAT) somewhere between the client and the system being "
+"installed. Depending on at which point of the installation the connection "
+"was lost, you may or may not be able to resume the installation after "
+"reconnecting."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3411
 #, no-c-format
-msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
+msgid ""
+"You may be able to avoid the connection being dropped by adding the option "
+"<userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></"
+"userinput> when starting the <command>ssh</command> connection, or by adding "
+"that option in your <command>ssh</command> configuration file. Note however "
+"that in some cases adding this option may also <emphasis>cause</emphasis> a "
+"connection to be dropped (for example if keep-alive packets are sent during "
+"a brief network outage, from which <command>ssh</command> would otherwise "
+"have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3424
 #, no-c-format
-msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
+msgid ""
+"If you install several computers in turn and they happen to have the same IP "
+"address or hostname, <command>ssh</command> will refuse to connect to such "
+"host. The reason is that it will have different fingerprint, which is "
+"usually a sign of a spoofing attack. If you are sure this is not the case, "
+"you will need to delete the relevant line from <filename>~/.ssh/known_hosts</"
+"filename><footnote> <para> The following command will remove an existing "
+"entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</"
+"replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </"
+"para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3440
 #, no-c-format
-msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
+msgid ""
+"After the login you will be presented with an initial screen where you have "
+"two possibilities called <guimenuitem>Start menu</guimenuitem> and "
+"<guimenuitem>Start shell</guimenuitem>. The former brings you to the main "
+"installer menu, where you can continue with the installation as usual. The "
+"latter starts a shell from which you can examine and possibly fix the remote "
+"system. You should only start one SSH session for the installation menu, but "
+"may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3450
 #, no-c-format
-msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
+msgid ""
+"After you have started the installation remotely over SSH, you should not go "
+"back to the installation session running on the local console. Doing so may "
+"corrupt the database that holds the configuration of the new system. This in "
+"turn may result in a failed installation or problems with the installed "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -2735,25 +4151,44 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3470
 #, no-c-format
-msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
+msgid ""
+"As described in <xref linkend=\"hardware-firmware\"/>, some devices require "
+"firmware to be loaded. In most cases the device will not work at all if the "
+"firmware is not available; sometimes basic functionality is not impaired if "
+"it is missing and the firmware is only needed to enable additional features."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3478
 #, no-c-format
-msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
+msgid ""
+"If a device driver requests firmware that is not available, &d-i; will "
+"display a dialog offering to load the missing firmware. If this option is "
+"selected, &d-i; will scan available devices for either loose firmware files "
+"or packages containing firmware. If found, the firmware will be copied to "
+"the correct location (<filename>/lib/firmware</filename>) and the driver "
+"module will be reloaded."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3488
 #, no-c-format
-msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
+msgid ""
+"Which devices are scanned and which file systems are supported depends on "
+"the architecture, the installation method and the stage of the installation. "
+"Especially during the early stages of the installation, loading the firmware "
+"is most likely to succeed from a FAT-formatted floppy disk or USB stick. "
+"<phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an "
+"MMC or SD card.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3498
 #, no-c-format
-msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
+msgid ""
+"Note that it is possible to skip loading the firmware if you know the device "
+"will also function without it, or if the device is not needed during the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2765,25 +4200,47 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3507
 #, no-c-format
-msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
+msgid ""
+"Official CD images do not include non-free firmware. The most common method "
+"to load such firmware is from some removable medium such as a USB stick. "
+"Alternatively, unofficial CD builds containing non-free firmware can be "
+"found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick "
+"(or other medium like a hard drive partition, or floppy disk), the firmware "
+"files or packages must be placed in either the root directory or a directory "
+"named <filename>/firmware</filename> of the file system on the medium. The "
+"recommended file system to use is FAT as that is most certain to be "
+"supported during the early stages of the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3520
 #, no-c-format
-msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
+msgid ""
+"Tarballs and zip files containing current packages for the most common "
+"firmware are available from: <itemizedlist> <listitem><para> <ulink url="
+"\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just "
+"download the tarball or zip file for the correct release and unpack it to "
+"the file system on the medium."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3534
 #, no-c-format
-msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
+msgid ""
+"If the firmware you need is not included in the tarball, you can also "
+"download specific firmware packages from the (non-free section of the) "
+"archive. The following overview should list most available firmware packages "
+"but is not guaranteed to be complete and may also contain non-firmware "
+"packages:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3548
 #, no-c-format
-msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
+msgid ""
+"It is also possible to copy individual firmware files to the medium. Loose "
+"firmware could be obtained for example from an already installed system or "
+"from a hardware vendor."
 msgstr ""
 
 #. Tag: title
@@ -2795,24 +4252,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3558
 #, no-c-format
-msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
+msgid ""
+"Any firmware loaded during the installation will be copied automatically to "
+"the installed system. In most cases this will ensure that the device that "
+"requires the firmware will also work correctly after the system is rebooted "
+"into the installed system. However, if the installed system runs a different "
+"kernel version from the installer there is a slight chance that the firmware "
+"cannot be loaded due to version skew."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3567
 #, no-c-format
-msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
+msgid ""
+"If the firmware was loaded from a firmware package, &d-i; will also install "
+"this package for the installed system and will automatically add the non-"
+"free section of the package archive in APT's <filename>sources.list</"
+"filename>. This has the advantage that the firmware should be updated "
+"automatically if a new version becomes available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3575
 #, no-c-format
-msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
+msgid ""
+"If loading the firmware was skipped during the installation, the relevant "
+"device will probably not work with the installed system until the firmware "
+"(package) is installed manually."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3582
 #, no-c-format
-msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
+msgid ""
+"If the firmware was loaded from loose firmware files, the firmware copied to "
+"the installed system will <emphasis>not</emphasis> be automatically updated "
+"unless the corresponding firmware package (if available) is installed after "
+"the installation is completed."
 msgstr ""
-
diff --git a/po/el/boot-installer.po b/po/el/boot-installer.po
index d3c9d4ac3..acadd4de9 100644
--- a/po/el/boot-installer.po
+++ b/po/el/boot-installer.po
@@ -15,7 +15,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-08-15 12:43+0300\n"
 "Last-Translator: galaxico <galaxico@quad-nrg.net>\n"
 "Language-Team: American English <debian-l10n-greek@lists.debian.org>\n"
@@ -77,8 +77,8 @@ msgid "Booting from TFTP"
 msgstr "Εκκίνηση από TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -88,8 +88,8 @@ msgstr ""
 "έναν δικτυακό TFTP server εκκίνησης (DHCP, RARP, ή BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -99,8 +99,8 @@ msgstr ""
 "RBOOT αντί ενός  BOOTP."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -116,8 +116,8 @@ msgid "Booting from CD-ROM"
 msgstr "Εκκίνηση από CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -135,8 +135,8 @@ msgstr ""
 "κεφάλαιο."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -153,8 +153,8 @@ msgstr ""
 "περίπτωσή σας."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -171,8 +171,8 @@ msgstr ""
 "στο σύστημα εγκατάστασης να χρησιμοποιήσει τον οδηγό του CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -423,8 +423,8 @@ msgid "The installer will now start as usual."
 msgstr "Ο εγκαταστάτης θα ξεκινήσει τώρα ως συνήθως."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Εκκίνηση από CD-ROM"
@@ -443,17 +443,23 @@ msgstr "Για να ξεκινήσετε τον εγκαταστάτη από τ
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "αποκτήστε ένα μέσο εγκατάστασης είτε σε CD-ROM/DVD-ROM είτε σε κλειδί μνήμης "
 "USB όπως περιγράφεται στις ενότητες <xref linkend=\"official-cdrom\"/> και "
 "<xref linkend=\"boot-usb-files\"/>, ή"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -464,7 +470,7 @@ msgstr ""
 "&debian;,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -481,7 +487,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -493,13 +499,13 @@ msgstr ""
 "του &debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Εκκίνηση από το DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -509,7 +515,7 @@ msgstr ""
 "παράδειγμα από έναν δίσκο ανάκτησης  ή διαγνωστικών."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -528,7 +534,7 @@ msgstr ""
 "δίσκου αν είναι απαραίτητο."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -551,7 +557,7 @@ msgstr ""
 "command>. Ο πυρήνας θα φορτωθεί και θα ξεκινήσει το σύστημα εγκατάστασης."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -559,7 +565,7 @@ msgstr ""
 "Ξεκινώντας από το Linux με <command>LILO</command> ή <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -570,7 +576,7 @@ msgstr ""
 "ενότητα <xref linkend=\"boot-drive-files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -589,7 +595,7 @@ msgstr ""
 "και θα πρέπει να κάνετε κάτι τέτοιο με προσοχή."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -608,7 +614,7 @@ msgstr ""
 "του CD/DVD χωρίς την ανάγκη πρόσβασης στο δίκτυο."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -628,7 +634,7 @@ msgstr ""
 "lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -640,7 +646,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz "
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -656,7 +662,7 @@ msgstr ""
 "userinput> και επανεκκινήστε."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -673,7 +679,7 @@ msgstr ""
 "κατάτμηση του πρώτου δίσκου του συστήματος):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -687,7 +693,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -700,7 +706,7 @@ msgstr ""
 "για παράδειγμα:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -720,7 +726,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -730,13 +736,13 @@ msgstr ""
 "<command>GRUB</command> και του <command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Εκκίνηση από USB stick μνήμης "
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -761,13 +767,13 @@ msgstr ""
 "εισάγετε προαιρετικά ορίσματα για την εκκίνηση ή απλά να πατήσετε &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Εκκίνηση από Δισκέττες"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -778,7 +784,7 @@ msgstr ""
 "floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -789,7 +795,7 @@ msgstr ""
 "συνηθισμένο τρόπο, και μετά ξανανοίξτε το."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -808,7 +814,7 @@ msgstr ""
 "<userinput>linux root=/dev/hdc</userinput> στο προτρεπτικό εκκίνησης."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -826,7 +832,7 @@ msgstr ""
 "κατά τη διαδικασία της εκκίνησης."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -836,7 +842,7 @@ msgstr ""
 "εισάγει τη δισκέττα και τελειώνει με την προτροπή <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -854,7 +860,7 @@ msgstr ""
 "στο  <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -868,14 +874,14 @@ msgstr ""
 "<command>debian-installer</command> ξεκινά αυτόματα."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Εκκίνηση μέσω TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
@@ -883,13 +889,13 @@ msgstr ""
 "αρχιτεκτονική i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "Κάρτα δικτύου ή μητρική που υποστηρίζουν PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -904,13 +910,13 @@ msgstr ""
 "ώστε να εκκινεί από το δίκτυο."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "Κάρτα δικτύου (NIC) με δικτυακή bootROM "
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -920,7 +926,7 @@ msgstr ""
 "εκκίνησης με TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -930,13 +936,13 @@ msgstr ""
 "τα καταφέρατε. Παρακαλούμε αναφερθείτε στο κείμενο αυτό."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot "
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -947,13 +953,13 @@ msgstr ""
 "μια εκκίνηση με TFTPboot."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Η οθόνη εκκίνησης"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -991,7 +997,7 @@ msgstr ""
 "κάτω, διπλασιάζοντας σχεδόν έτσι τον αριθμό των επιλογών."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -1008,7 +1014,7 @@ msgstr ""
 "εγκαταστάτη."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -1020,7 +1026,7 @@ msgstr ""
 "\", σε κατάσταση \"διάσωσης\" και σε αυτοματοποιημένες εγκαταστάσεις."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1040,7 +1046,7 @@ msgstr ""
 "αναιρέσετε όποιες αλλαγές έχετε κάνει."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1091,7 +1097,7 @@ msgstr ""
 "βοήθειας. Αν όντως προσθέσετε οποιεσδήποτε \t"
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1112,7 +1118,7 @@ msgstr ""
 "χρησιμοποιηθούν."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1134,7 +1140,7 @@ msgstr ""
 "HP."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1156,13 +1162,13 @@ msgstr ""
 "προτρεπτικό εκκίνησης, όπως περιγράφεται στο κείμενο βοήθειας."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Περιεχόμενα CD"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1187,7 +1193,7 @@ msgstr ""
 "χωρίς την ανάγκη πρόσβασης στο δίκτυο."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1214,7 +1220,7 @@ msgstr ""
 "απλού MBR ή του μπλοκ εκκίνησης στα περισσότερα συμβατικά συστήματα."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1231,7 +1237,7 @@ msgstr ""
 "το κέλυφος EFI όπως περιγράφεται στη συνέχεια."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1254,7 +1260,7 @@ msgstr ""
 "EFI όντως υπάρχει πριν επιτρέψει την συνέχιση της εγκατάστασης."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1278,13 +1284,13 @@ msgstr ""
 "για κάποιο λόγο δεν εκκινεί με αυτήν, χρησιμοποιείστε την δεύτερη."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "ΣΗΜΑΝΤΙΚΟ"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1306,13 +1312,13 @@ msgstr ""
 "του κελύφους."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Επιλογή 1: Εκκίνηση από το Μενού Συντήρησης Επιλογής Εκκίνησης"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1324,7 +1330,7 @@ msgstr ""
 "ολοκληρώσει την αρχικοποίηση του συστήματος."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1335,7 +1341,7 @@ msgstr ""
 "εμφανίσει ένα καινούριο μενού."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1354,7 +1360,7 @@ msgstr ""
 "συσκευή και τον ελεγκτή θα πρέπει να είναι η ίδια."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1373,7 +1379,7 @@ msgstr ""
 "προχωρήσετε στο επόμενο (επιπρόσθετο) βήμα."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1389,7 +1395,7 @@ msgstr ""
 "command>. Αυτό θα ξεκινήσει την ακολουθία της εκκίνησης."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1401,13 +1407,13 @@ msgstr ""
 "και να δώσετε άλλες επιλογές. Προχωρήστε στις επιλογές αυτές."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Επιλογή 2: Εκκίνηση από το κέλυφος του EFI"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1421,7 +1427,7 @@ msgstr ""
 "command>. Εκκινήστε το CD του εγκαταστάτη του &debian; με τα ακόλουθα βήματα:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1433,7 +1439,7 @@ msgstr ""
 "μετά από αυτό ολοκληρώνει την αρχικοποίηση του συστήματος."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1456,7 +1462,7 @@ msgstr ""
 "επιπλέον καθώς γίνεται η εκκίνηση της συσκευής του."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1470,7 +1476,7 @@ msgstr ""
 "σαν<filename>fs<emphasis>n</emphasis></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1484,7 +1490,7 @@ msgstr ""
 "εμφανίσει τώρα τοναριθμό της διαμέρισης σαν την προτροπή του."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1494,7 +1500,7 @@ msgstr ""
 "θα ξεκινήσει την ακολουθία της εκκίνησης."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1511,13 +1517,13 @@ msgstr ""
 "δυνατοτήτων."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Εγκατάσταση μέσω Σειριακής Κονσόλας"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1539,7 +1545,7 @@ msgstr ""
 "συσκευή ttyS0."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1553,7 +1559,7 @@ msgstr ""
 "χρησιμοποιώντας την εντολή<command>baud</command> στο κέλυφος  EFI."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1570,7 +1576,7 @@ msgstr ""
 "στο παράθυρο κειμένου <classname>Boot:</classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1590,7 +1596,7 @@ msgstr ""
 "εγκαταστάτη σε \"Κατάσταση Κειμένου\"."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1604,13 +1610,13 @@ msgstr ""
 "συστήματος για να μπορέσει να ξεκινήσει η εγκατάσταση."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Επιλογή του πυρήνα εκκίνησης και των άλλων επιλογών"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1631,7 +1637,7 @@ msgstr ""
 "τις πιο κοινές επιλογές για τη γραμμή εντολών."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1657,7 +1663,7 @@ msgstr ""
 "εγκατάσταση:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1667,7 +1673,7 @@ msgstr ""
 "ταιριάζειπερισσότερο στις ανάγκες σας με τα βελάκια του πληκτρολογίου."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1679,7 +1685,7 @@ msgstr ""
 "πυρήνα (όπως για παράδειγμα οι ρυθμίσεις της σειριακής κονσόλας)."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1691,7 +1697,7 @@ msgstr ""
 "ακολουθούμενα από την πρώτη οθόνη του εγκαταστάτη."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1702,7 +1708,7 @@ msgstr ""
 "του δίσκου."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1723,7 +1729,7 @@ msgstr ""
 "από το CD."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1739,13 +1745,13 @@ msgstr ""
 "την φόρτωση από το δίκτυο."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Ρύθμιση του Server"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1769,7 +1775,7 @@ msgstr ""
 "εκτέλεση του <command>elilo.efi</command> στην πλευρά του πελάτη."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1786,7 +1792,7 @@ msgstr ""
 "ένα σύστημα IA-64."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1804,7 +1810,7 @@ msgstr ""
 "[...] "
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1827,13 +1833,13 @@ msgstr ""
 "πακέτο <classname>elilo</classname> για λεπτομέρειες."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Ρύθμιση του πελάτη"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1866,7 +1872,7 @@ msgstr ""
 "<filename>elilo.efi</filename> από τον διακομιστή."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1883,13 +1889,13 @@ msgstr ""
 "&debian;."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Εκκίνηση SGI Indy με TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1912,13 +1918,13 @@ msgstr ""
 "</screen></informalexample> στην οθόνη εντολών για να το κάνετε."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Παράμετροι εκκίνησης"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1928,7 +1934,7 @@ msgstr ""
 "<command>bootp():</command> στην οθόνη εντολών."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1947,19 +1953,19 @@ msgstr ""
 "μέσω της εντολής <command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\" "
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Εκκίνηση Cobalt με TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1978,7 +1984,7 @@ msgstr ""
 "Υπάρχουν οι ακόλουθες δύο μέθοδοι εγκατάστασης:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1994,7 +2000,7 @@ msgstr ""
 "πελάτη SSH μπορείτε να ξεκινήσετε με την εγκατάσταση."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -2007,7 +2013,7 @@ msgstr ""
 "τον τρόπο."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -2020,13 +2026,13 @@ msgstr ""
 "μεταβλητή <replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Περιορισμοί των υπολογιστικών συστημάτων s390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -2036,7 +2042,7 @@ msgstr ""
 "ρυθμισμένοδίκτυο και δυνατότητα για ssh σύνδεση."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -2050,13 +2056,13 @@ msgstr ""
 "εκκίνηση τοκανονικό σύστημα εγκατάστασης ."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Παράμετροι Εκκίνησης για s390 "
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -2069,7 +2075,7 @@ msgstr ""
 "δίνεται με τις εικόνες της εγκατάστασης."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2088,7 +2094,7 @@ msgstr ""
 "ξεκινήσετε από την προκαθορισμένη από τον κατασκευαστή συσκευή CD/DVD."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2107,13 +2113,13 @@ msgstr ""
 "εσωτερική προκαθορισμένη συσκευή  CD/DVD πληκτρολογήστε"
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot "
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2131,7 +2137,7 @@ msgstr ""
 "αρχείων."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2144,19 +2150,19 @@ msgstr ""
 "του SmartFirmware πληκτρολογήστε"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Εκκίνηση από τον σκληρό δίσκο"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2167,7 +2173,7 @@ msgstr ""
 "εγκατάστασης."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2179,13 +2185,13 @@ msgstr ""
 "περιγράφεται στο <xref linkend=\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Εκκίνηση OldWorld PowerMac από το MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2209,13 +2215,13 @@ msgstr ""
 "εγκαταστάτη."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Εκκίνηση ενός NewWorld Mac από το OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2261,13 +2267,13 @@ msgstr ""
 "τότε να ξεκινήσει."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Εκκίνηση από USB κλειδί μνήμης"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2275,7 +2281,7 @@ msgstr ""
 "υποστηρίζουν εκκίνηση μέσω USB."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2291,7 +2297,7 @@ msgstr ""
 "openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2315,7 +2321,7 @@ msgstr ""
 "pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2341,7 +2347,7 @@ msgstr ""
 "προσδιορισμένο με ακρίβεια μέσω της <command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2353,7 +2359,7 @@ msgstr ""
 "προαιρετικά ορίσματα εκκίνησης ή απλώς να πατήσετε το &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2366,7 +2372,7 @@ msgstr ""
 "εξηγείται στο <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2374,7 +2380,7 @@ msgstr ""
 "εκκίνηση από το δίκτυο."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2409,7 +2415,7 @@ msgstr ""
 "της σύνταξης και των διαθέσιμων επιλογών."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2423,7 +2429,7 @@ msgstr ""
 "εκκίνηση προσαρτώμενες USB συσκευές δισκέττας."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2435,7 +2441,7 @@ msgstr ""
 "πριν πατήσετε τον διακόπτη για την επανεκκίνηση."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2450,7 +2456,7 @@ msgstr ""
 "ελέγξει για εκκινήσιμες διαμερίσεις στον σκληρό δίσκο."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2463,13 +2469,13 @@ msgstr ""
 "συστήματος στη μνήμη."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "Παράμετροι Εκκίνησης για PowerPC"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2486,7 +2492,7 @@ msgstr ""
 "<userinput>video=aty128fb:vmode:6</userinput> ."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2507,7 +2513,7 @@ msgstr ""
 "εντολής <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2520,13 +2526,13 @@ msgstr ""
 "δεύτερο καλώδιο για συστήματα IDE)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "Μηνύματα IDPROM"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2542,13 +2548,13 @@ msgstr ""
 "NVRAM FAQ</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Προσβασιμότητα"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2578,13 +2584,13 @@ msgstr ""
 "το πληκτρολόγιό σας ως πληκτρολόγιο QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "Οθόνες Braille USB"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2607,13 +2613,13 @@ msgstr ""
 "ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Σειριακές Οθόνες Braille"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2656,13 +2662,13 @@ msgstr ""
 "\"><classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "Σύνθεση Ομιλίας με Λογισμικό"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2678,13 +2684,13 @@ msgstr ""
 "στο <classname>espeak</classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Σύνθεση Ομιλίας από το Hardware"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2696,7 +2702,7 @@ msgstr ""
 "<quote>Γραφική εγκατάσταση</quote> από το μενού εκκίνησης."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2720,13 +2726,13 @@ msgstr ""
 "εγκατάσταση σύστημα."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Συσκευές Καρτών"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2744,7 +2750,7 @@ msgstr ""
 "διαθέσιμων γλωσσών για την εγκατάσταση."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2755,13 +2761,13 @@ msgstr ""
 "userinput> &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Θέμα Υψηλής Αντίθεσης"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2774,13 +2780,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Προρύθμιση"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2791,7 +2797,7 @@ msgstr ""
 "τεκμηρίωση στην ενότητα <xref linkend=\"appendix-preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2806,7 +2812,7 @@ msgstr ""
 "κάποιες φορές θα πρέπει να του δώσετε μια μικρή βοήθεια."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2822,7 +2828,7 @@ msgstr ""
 "hardware σας."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2839,7 +2845,7 @@ msgstr ""
 "περιλαμβάνονταιπαρακάτω στο <xref linkend=\"boot-troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2877,7 +2883,7 @@ msgstr ""
 "προσθέσετε  "
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2919,7 +2925,7 @@ msgstr ""
 "προσθέσετε  "
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2933,13 +2939,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Παράμετροι του Εγκαταστάτη του &debian;"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2955,7 +2961,7 @@ msgstr ""
 "χρήσιμες."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2972,13 +2978,13 @@ msgstr ""
 "την σύντομη μορφή."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority) "
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
@@ -2986,7 +2992,7 @@ msgstr ""
 "θα εμφανίζονται."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -3001,7 +3007,7 @@ msgstr ""
 "προτεραιότητα όπως χρειάζεται."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -3022,13 +3028,13 @@ msgstr ""
 "κάνει το \"σωστό\" χωρίς μεγάλη \"φασαρία\"."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND "
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -3065,13 +3071,13 @@ msgstr ""
 "την επιλογή <userinput>gtk</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG "
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -3086,49 +3092,49 @@ msgstr ""
 "συνεχίσετε την διαδικασία εκκίνησης)."
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0 "
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Αυτή είναι η προκαθορισμένη επιλογή."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1 "
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Πιο αναλυτική από το συνηθισμένο."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2 "
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Άφθονη πληροφορία αποσφαλμάτωσης."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3 "
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -3139,13 +3145,13 @@ msgstr ""
 "συνεχίσετε κανονικάτην εκκίνηση."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV "
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3157,7 +3163,7 @@ msgstr ""
 "dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3168,19 +3174,19 @@ msgstr ""
 "με την παράμετρο αυτή ώστε να \"κοιτάξει\" μια μόνο συσκευή."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3193,13 +3199,13 @@ msgstr ""
 "προκαθορισμένη για το syslog θύρα 514. "
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3212,13 +3218,13 @@ msgstr ""
 "οι 1 και 2. Δείτε επίσης  <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3229,13 +3235,13 @@ msgstr ""
 "και όπου η φυσική ασφάλεια είναι περιορισμένη."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb) "
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3255,13 +3261,13 @@ msgstr ""
 "εγκατάστασης."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Τέτοια προβλήματα έχουν αναφερθεί σε hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3281,13 +3287,13 @@ msgstr ""
 "userinput>  ή σε συντομία <userinput>fb=true</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (θέμα)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3304,13 +3310,13 @@ msgstr ""
 "<userinput>theme=<replaceable>dark</replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp "
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3325,7 +3331,7 @@ msgstr ""
 "αποτύχει."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3340,13 +3346,13 @@ msgstr ""
 "που θέλετε χειροκίνητα."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia "
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3357,13 +3363,13 @@ msgstr ""
 "είναι αρκετάγνωστοί για αυτή την κακή συμπεριφορά."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3378,13 +3384,13 @@ msgstr ""
 "url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url) "
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3395,13 +3401,13 @@ msgstr ""
 "Δείτε το <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file) "
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3412,13 +3418,13 @@ msgstr ""
 "\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3435,13 +3441,13 @@ msgstr ""
 "\"preseed-seenflag\"/> για λεπτομέρειες."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "αυτόματη-εγκατάσταση/ενεργοποιημένη (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3455,13 +3461,13 @@ msgstr ""
 "εγκαταστάσεων."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3474,13 +3480,13 @@ msgstr ""
 "userinput> για να αποτρέψετε κάτι τέτοιο."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "ανίχνευση/αποβολή cdrom"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3500,7 +3506,7 @@ msgstr ""
 "αυτόματα."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3513,13 +3519,13 @@ msgstr ""
 "εγκατάσταση."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3534,7 +3540,7 @@ msgstr ""
 "\"di-install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3551,13 +3557,13 @@ msgstr ""
 "λοιπόν να χρησιμοποιηθεί μόνο από πολύ έμπειρους χρήστες."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3571,13 +3577,13 @@ msgstr ""
 "\">Προειδοποίηση: δεν είναι ασφαλής, μη συνιστώμενη.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size "
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3590,13 +3596,13 @@ msgstr ""
 "φορτωθεί πλήρως. Η τιμή είναι σε kB."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "διάσωση/ενεργοποίηση"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3606,13 +3612,13 @@ msgstr ""
 "διάσωσης αντί της διαδικασίας της κανονικής εγκατάστασης."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Χρήση παραμέτρων εκκίνησης για την απάντηση ερωτήσεων"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3628,25 +3634,25 @@ msgstr ""
 "παραδείγματα παραθέτονται στη συνέχεια."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (γλώσσα)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (χώρα)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale) "
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3657,7 +3663,7 @@ msgstr ""
 "εγκατεστημμένο σύστημα."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3679,7 +3685,7 @@ msgstr ""
 "τοπικοποίησης."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3696,13 +3702,13 @@ msgstr ""
 "<userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules) "
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3719,7 +3725,7 @@ msgstr ""
 "classname> (δείτε και το <xref linkend=\"pppoe\"/>)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3729,13 +3735,13 @@ msgstr ""
 "χρήση DHCP και να χρησιμοποιήσετε υποχρεωτικά μια στατική ρύθμιση δικτύου."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol) "
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3755,13 +3761,13 @@ msgstr ""
 "χέρι."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks) "
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3774,13 +3780,13 @@ msgstr ""
 "πληροφορίες."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Πέρασμα παραμέτρων στα αρθρώματα του πυρήνα"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3806,7 +3812,7 @@ msgstr ""
 "αυτόματα στις ρυθμίσεις του εγκατεστημμένου συστήματος."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3822,7 +3828,7 @@ msgstr ""
 "το χέρι."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3836,19 +3842,19 @@ msgid ""
 msgstr "Η σύνταξη που πρέπει να χρησιμοποιηθεί "
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10 "
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Αποκλεισμός (blacklisting) αρθρωμάτων του πυρήνα"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3867,7 +3873,7 @@ msgstr ""
 "των οδηγών ή αν φορτωθεί πρώτα ο λάθος οδηγός."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3883,7 +3889,7 @@ msgstr ""
 "διάρκεια της εγκατάστασης όσο και για το εγκατεστημένο σύστημα."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3898,19 +3904,19 @@ msgstr ""
 "του υλικού."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Ανίχνευση λαθών της Διαδικασίας Εγκατάστασης "
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Αξιοπιστία των δίσκων CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3925,7 +3931,7 @@ msgstr ""
 "κατά την ανάγνωσή του στη διάρκεια της εγκατάστασης."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3938,14 +3944,14 @@ msgstr ""
 "από σας."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 "Υπάρχουν δυο πολύ απλά πράγματα που θα μπορούσατε καταρχήν να δοκιμάσετε."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3955,7 +3961,7 @@ msgstr ""
 "είναι καθαρό."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3975,7 +3981,7 @@ msgstr ""
 "αντιμετωπίζονται με τον τρόπο αυτό."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3988,7 +3994,7 @@ msgstr ""
 "χρησιμοποιήσουμε τον όρο CD-ROM για απλούστευση."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3998,13 +4004,13 @@ msgstr ""
 "μια από τις άλλες μεθόδους εγκατάστασης που είναι διαθέσιμες."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Συνηθισμένα προβλήματα"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -4015,7 +4021,7 @@ msgstr ""
 "εγγραφείς CD."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -4028,13 +4034,13 @@ msgstr ""
 "ενεργοποιημένη η επιλογή  <quote>direct memory access</quote> (DMA)."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Πώς να διερευνήσετε και πιθανόν να επιλύσετε μερικά προβλήματα"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
@@ -4042,7 +4048,7 @@ msgstr ""
 "προτείνονται παρακάτω."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -4057,7 +4063,7 @@ msgstr ""
 "υποστηρίζει τα μέσα που χρησιμοποιείτε."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -4084,7 +4090,7 @@ msgstr ""
 "τον σωστό αριθμό των byte από το CD-ROM."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -4106,7 +4112,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s "
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -4128,7 +4134,7 @@ msgstr ""
 "εικονική κονσόλα (VT2) και να ενεργοποιήσετε το κέλυφος σ' αυτήν."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -4141,7 +4147,7 @@ msgstr ""
 "Στη συνέχεια, ελέγξτε επίσης την έξοδο της εντολής <command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -4172,7 +4178,7 @@ msgstr ""
 "το χέρι χρησιμοποιοώντας την εντολή  <command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -4185,7 +4191,7 @@ msgstr ""
 "ένας κόμβος <filename>/dev/cdrom</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4202,7 +4208,7 @@ msgstr ""
 "σφάλματος μετά την εκτέλεση της εντολής αυτής."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4229,7 +4235,7 @@ msgstr ""
 "όνομα που αντιστοιχεί στη συσκευή CD-ROM σας."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4244,13 +4250,13 @@ msgstr ""
 "αναγνωστεί αξιόπιστα."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Αξιοπιστία των δισκετών"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4260,7 +4266,7 @@ msgstr ""
 "φαίνεται να είναι η αξιοπιστία των δισκετών."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4280,7 +4286,7 @@ msgstr ""
 "εισόδου/εξόοδου (Ι/Ο) της δισκέττας."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4299,7 +4305,7 @@ msgstr ""
 "το να προσπαθήσετε να γράψετε την δισκέττα σε ένα διαφορετικό σύστημα."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4311,7 +4317,7 @@ msgstr ""
 "επειτα ολα προχωρησαν κανονικα με την τριτη δισκετα."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4323,7 +4329,7 @@ msgstr ""
 "των δισκεττών έχουν κατέβει σωστά επαληθεύοντας τις υπογραφές τους md5sums."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4335,13 +4341,13 @@ msgstr ""
 "αυτά οφείλονται σε ένα προβληματικό υλικό ή στο firmware του οδηγού δισκέτας."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Ρύθμιση της εκκίνησης"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4356,7 +4362,7 @@ msgstr ""
 "parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4365,7 +4371,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4385,37 +4391,37 @@ msgstr ""
 "έχει λειτουργικό ήχο (πχ. ένα σύστημα live CD). "
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Συνηθισμένα προβλήματα εγκατάστασης στην αρχιτεκτονική &arch-title; "
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4425,7 +4431,7 @@ msgstr ""
 "αποφευχθούν περνώντας συγκεκριμένες παραμέτρους εκκίνησης στον εγκαταστάτη."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4447,13 +4453,13 @@ msgstr ""
 "\"boot-parms\"/> για λεπτομέρειες."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Πάγωμα του συστήματος κατά το στάδιο ρύθμισης του PCMCIA "
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4482,7 +4488,7 @@ msgstr ""
 "την περιοχή των πόρων εκείνων που προκαλούν τα προβλήματα."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4506,20 +4512,20 @@ msgstr ""
 "εισάγετε αυτή την τιμή στον εγκαταστάτη."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 "Υπάρχουν μερικά συνηθισμένα προβλήματα εγκατάστασης που αξίζει να αναφερθούν."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Λάθος κατευθυνόμενη έξοδος εικόνας"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4549,7 +4555,7 @@ msgstr ""
 "userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4564,13 +4570,13 @@ msgstr ""
 "conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Αποτυχία Εκκίνησης ή Εγκατάστασης από το CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4583,7 +4589,7 @@ msgstr ""
 "συστήματα SunBlade."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4591,13 +4597,13 @@ msgstr ""
 "εγκαταστάτη από το δίκτυο."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Ερμηνεία των μηνυμάτων έναρξης πυρήνα! "
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4637,13 +4643,13 @@ msgstr ""
 "\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Αναφορά Προβλημάτων της Εγκατάστασης"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4665,7 +4671,7 @@ msgstr ""
 "επισυνάψετε αυτές τις πληροφορίες σ'αυτήν."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4678,13 +4684,13 @@ msgstr ""
 "σας στο εγκατεστημένο σύστημα."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Διαδικασία υποβολής Αναφοράς Εγκατάστασης"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4699,7 +4705,7 @@ msgstr ""
 "διαμορφώσεων υλικού."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4713,7 +4719,7 @@ msgstr ""
 "δημοσιοποιηθεί."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4733,7 +4739,7 @@ msgstr ""
 "και να τρέξετε την εντολή <command>reportbug installation-reports</command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/el/install-methods.po b/po/el/install-methods.po
index ecb5b4af3..8e41af44b 100644
--- a/po/el/install-methods.po
+++ b/po/el/install-methods.po
@@ -13,7 +13,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-08-15 19:26+0300\n"
 "Last-Translator: galaxico <galaxico@quad-nrg.net>\n"
 "Language-Team: American English <debian-l10n-greek@lists.debian.org>\n"
@@ -90,15 +90,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -141,7 +140,7 @@ msgstr ""
 "ίδιους καταλόγους και υποκαταλόγους στο CD σας."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -151,7 +150,7 @@ msgstr ""
 "υπόλοιπα απαραίτητα για τον εγκαταστάτη αρχεία από το CD."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -171,13 +170,13 @@ msgstr ""
 "του εγκαταστάτη."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Λήψη Αρχείων από τους Κατοπτριστές αρχείων του &debian;"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -188,7 +187,7 @@ msgstr ""
 "κατοπτριστών αρχείων του Debian</ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -200,13 +199,13 @@ msgstr ""
 "κατάσταση κειμένου."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Πού να βρείτε Είδωλα της Εγκατάστασης"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -222,13 +221,13 @@ msgstr ""
 "ulink> καταγράφει κάθε είδωλο και τον ρόλο της."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Αρχεία εγκατάστασης του Thecus N2100"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -242,13 +241,13 @@ msgstr ""
 "firmware του Thecus και να ληφθεί από το &n2100-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Αρχεία εγκατάστασης GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -260,13 +259,13 @@ msgstr ""
 "εικόνες μπορούν να ληφθούν από το &glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Αρχεία εγκατάστασης Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -279,13 +278,13 @@ msgstr ""
 "img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Αρχεία εγκατάστασης HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -301,13 +300,13 @@ msgstr ""
 "μπορεί να ληφθεί από το &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Αρχεία εγκατάστασης QNAP Turbo Station"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -322,13 +321,13 @@ msgstr ""
 "&qnap-kirkwood-firmware-img;.  "
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Αρχεία Εγκατάστασης Plug Computer και OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -344,14 +343,14 @@ msgstr ""
 "Μπορείτε να πάρετε τα αρχεία αυτά από το &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "NSLU2 Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "Αρχεία εγκατάστασης NSLU2"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -368,13 +367,13 @@ msgstr ""
 "Μπορείτε να πάρετε τα αρχεία αυτά από το &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Δημιουργία μιας κασέτας IPL"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -397,13 +396,13 @@ msgstr ""
 "filename>, δείτε το <xref linkend=\"where-files\"/>,"
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Γράφοντας Δισκέτες από Είδωλα Δισκετών"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -414,7 +413,7 @@ msgstr ""
 "CD ή από άλλο μέσο."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -424,7 +423,7 @@ msgstr ""
 "δισκεττών USB σε Mac."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -446,7 +445,7 @@ msgstr ""
 "δισκέττα."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -458,7 +457,7 @@ msgstr ""
 "είδωλα δισκεττών σε διαφορετικές πλατφόρμες."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -474,7 +473,7 @@ msgstr ""
 "συμπεριλαμβάνονται ήδη στο CD/DVD.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -487,13 +486,13 @@ msgstr ""
 "καταστραφούν από αμέλεια."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Γράφοντας Είδωλα Δισκεττών από ένα σύστημα Linux ή Unix"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -533,7 +532,7 @@ msgstr ""
 "σελίδα οδηγιών χρήσης της) </phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -569,7 +568,7 @@ msgstr ""
 "συστήματα ρωτήστε τον διαχειριστή του συστήματός σας. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -581,13 +580,13 @@ msgstr ""
 "θα είναι να το εγκαταστήσετε."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Γράφοντας είδωλα δισκεττών σε DOS, Windows, ή OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -597,7 +596,7 @@ msgstr ""
 "ένα από τα παρακάτω προγράμματα για να αντιγράψετε τις εικόνες σε δισκέττες."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -614,7 +613,7 @@ msgstr ""
 "αναμένεται να δουλέψει."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -626,7 +625,7 @@ msgstr ""
 "πρέπει να αποσυμπιέσετε την βιβλιοθήκη diskio.dll στον ίδιο κατάλογο."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -636,13 +635,13 @@ msgstr ""
 "από τον κατάλογο <filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Εγγραφή ειδώλων δισκέττας από το MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -666,7 +665,7 @@ msgstr ""
 "προχωρήσετε στην εγγραφή του αρχείου εικόνας σε αυτήν."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -681,13 +680,13 @@ msgstr ""
 "δημιουργία μιας δισκέττας από μια εικόνα δισκέττας με αυτά τα εργαλεία."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Εγγραφή Ειδώλων Δίσκων με το <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -702,7 +701,7 @@ msgstr ""
 "του &debian;."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -713,7 +712,7 @@ msgstr ""
 "filename>file."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -725,7 +724,7 @@ msgstr ""
 "Προσέξτε ότι στα πεδία υπάρχει διάκριση κεφαλαίων-πεζών."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -741,7 +740,7 @@ msgstr ""
 "εκκίνησης σε περίπτωση που το είδωλο προσαρτηθεί κατά τύχη."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -753,7 +752,7 @@ msgstr ""
 "<ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -770,13 +769,13 @@ msgstr ""
 "θέλετε πραγματικά να τη διαγράψετε. Όταν τελειώσετε θα αποβάλλει τη δισκέττα."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Εγγραφή Ειδώλων Δίσκων με το <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -790,7 +789,7 @@ msgstr ""
 "<userinput>Special</userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -799,7 +798,7 @@ msgstr ""
 "(ξεκινώντας από τον τομέα 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -808,7 +807,7 @@ msgstr ""
 "αρχείου."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -822,7 +821,7 @@ msgstr ""
 "δισκέττας, απλά δοκιμάστε με μια άλλη."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -834,13 +833,13 @@ msgstr ""
 "MacOS, το MacOS θα την καταστρέψει."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Προετοιμασία Αρχείων για Εκκίνηση από ένα USB Stick μνήμης"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -865,7 +864,7 @@ msgstr ""
 "προστασία εγγραφής του."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -880,7 +879,7 @@ msgstr ""
 "για παράδειγμα."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
@@ -888,7 +887,7 @@ msgstr ""
 "CD ή DVD"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -903,7 +902,7 @@ msgstr ""
 "\"/> για το πώς να αποκτήσετε μια εικόνα CD ή DVD."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -917,7 +916,7 @@ msgstr ""
 "ενότητα <xref linkend=\"where-files\"/>)."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -937,7 +936,7 @@ msgstr ""
 "να αποσυμπιέσετε εκεί τα αρχεία με το firmware."
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -953,7 +952,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -968,7 +967,7 @@ msgstr ""
 "βεβαιωθεί ότι το κλειδί έχει αποπροσαρτηθεί:"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -980,7 +979,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -993,13 +992,13 @@ msgstr ""
 "εξειδικευμένες ανάγκες."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "Αντιγραφή αρχείων στο κλειδί USB με το χέρι"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -1014,7 +1013,7 @@ msgstr ""
 "ενότητα <xref linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -1030,7 +1029,7 @@ msgstr ""
 "<classname>yaboot</classname> και το αρχείο των ρυθμίσεών του</phrase>."
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -1047,7 +1046,7 @@ msgstr ""
 "χρησιμοποιήσετε για κάποιο άλλο σκοπό."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
@@ -1055,13 +1054,13 @@ msgstr ""
 "USB:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1073,13 +1072,13 @@ msgstr ""
 "<command>mac-fdisk</command> και εξάγετε την εικόνα κατευθείαν στο κλειδί:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1110,13 +1109,13 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>) και έχετε τελειώσει."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Αντιγραφή αρχείων στο κλειδί USB με το χέρι &mdash; ο ευέλικτος τρόπος"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1132,13 +1131,13 @@ msgstr ""
 "τη δυνατότητα να αντιγράψετε μια ολόκληρη εικόνα ISO CD σ' αυτό."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Διαμέριση του κλειδιού USB"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1148,7 +1147,7 @@ msgstr ""
 "το πρώτο τμήμα αντί ολόκληρης της συσκευής."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1192,7 +1191,7 @@ msgstr ""
 "περιέχεται στο πακέτο <classname>dosfstools</classname> του &debian;."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1212,7 +1211,7 @@ msgstr ""
 "φορτωτή εκκίνησης."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1238,13 +1237,13 @@ msgstr ""
 "εκκίνησης."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Προσθήκη της εικόνας του εγκαταστάτη"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1271,7 +1270,7 @@ msgstr ""
 "(8.3) του DOS."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1306,7 +1305,7 @@ msgstr ""
 "προσθέσετε τις παραμέτρους <userinput>vga=788</userinput> στη δεύτερη γραμμή."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1314,7 +1313,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy "
@@ -1344,7 +1343,7 @@ msgstr ""
 "userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1375,7 +1374,7 @@ msgstr ""
 "στο πακέτο του &debian; <classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1392,7 +1391,7 @@ msgstr ""
 "χρησιμοποιηθεί για να γίνουν αλλαγές στην ρύθμιση του φορτωτή εκκίνησης."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1430,7 +1429,7 @@ msgstr ""
 "μπορεί να προετοιμαστεί χρησιμοποιώντας τα συνηθισμένα εργαλεία του Unix."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1441,31 +1440,31 @@ msgstr ""
 "εγκαταστάτη στο κλειδί:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (εκετελέσιμο αρχείο πυρήνα)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (εικόνα αρχικού δίσκου μνήμης ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (αρχείο ρυθμίσεων του yaboot)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (προαιρετικό μήνυμα εκκίνησης)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1502,13 +1501,13 @@ msgstr ""
 "το μέγεθος της εικόνα ramdisk που χρησιμοποιείτε για την εκκίνηση."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Προετοιμασία των αρχείων για Εκκίνηση από Σκληρό Δίσκο"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1521,7 +1520,7 @@ msgstr ""
 "εκκίνησης (boot loader) κατευθείαν από το BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1535,7 +1534,7 @@ msgstr ""
 "με πολυάριθμες και αναξιόπιστες δισκέττες."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1558,7 +1557,7 @@ msgstr ""
 "MacOS και του Linux, και συγκεκριμένα τα αρχεία που κατεβάζετε."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1570,7 +1569,7 @@ msgstr ""
 "εγκατάσταση από το σκληρό δίσκο."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1580,7 +1579,7 @@ msgstr ""
 "command> ή <command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1591,7 +1590,7 @@ msgstr ""
 "command> ή το <command>GRUB</command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1604,7 +1603,7 @@ msgstr ""
 "αρχείων από τον πυρήνα."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1617,19 +1616,19 @@ msgstr ""
 "<filename>/boot/newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (αρχείο πυρήνα)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (είδωλο δίσκου μνήμης)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1639,7 +1638,7 @@ msgstr ""
 "linkend=\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
@@ -1647,7 +1646,7 @@ msgstr ""
 "command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1658,7 +1657,7 @@ msgstr ""
 "<command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1668,7 +1667,7 @@ msgstr ""
 "&debian; CD στομ <filename>c:\\</filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1677,19 +1676,19 @@ msgstr ""
 "εικόνα δίσκου μνήμης, ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (εργαλείο loadlin)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Εκκίνηση του Εγκαταστάτη από το σκληρό δίσκο για OldWorld Macs"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1714,7 +1713,7 @@ msgstr ""
 "απαραίτητο γι αυτό το μοντέλο."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1742,13 +1741,13 @@ msgstr ""
 "στο ενεργό System Folder."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Εκκίνηση του Εγκαταστάτη από το σκληρό δίσκο για NewWorld Macs"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1769,7 +1768,7 @@ msgstr ""
 "χρησιμοποιείται σε NewWorld PowerMac συστήματα."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1783,31 +1782,31 @@ msgstr ""
 "dragging κάθε αρχείου στο εικονίδιο του σκληρού δίσκου)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1824,7 +1823,7 @@ msgstr ""
 "εκκίνηση του εγκαταστάτη."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1832,13 +1831,13 @@ msgstr ""
 "\"boot-newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Προετοιμασία Αρχείων για δικτυακή εκκίνηση με TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1856,7 +1855,7 @@ msgstr ""
 "συγκεκριμένου μηχανήματός σας."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1869,7 +1868,7 @@ msgstr ""
 "εξυπηρετητή BOOTP</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1891,7 +1890,7 @@ msgstr ""
 "συστήματα μπορούν να ρυθμιστούν μόνο μέσω του πρωτοκόλλου αυτού."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1904,7 +1903,7 @@ msgstr ""
 "BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1915,7 +1914,7 @@ msgstr ""
 "classname> "
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1930,7 +1929,7 @@ msgstr ""
 "SunOS 4.x, SunOS 5.x (δηλ. το Solaris), και GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1945,13 +1944,13 @@ msgstr ""
 "<classname>atftpd</classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Ρυθμίζοντας έναν εξυπηρετητή RARP"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1972,7 +1971,7 @@ msgstr ""
 "εντολή <userinput>ip addr show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1997,13 +1996,13 @@ msgstr ""
 "rarpd -a</userinput> στο σύστημα SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Ρυθμίζοντας έναν εξυπηρετητή DHCP"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -2017,7 +2016,7 @@ msgstr ""
 "ρυθμίσεων γι' αυτόν (δείτε το <filename>/etc/dhcp3/dhcpd.conf</filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -2061,7 +2060,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -2080,7 +2079,7 @@ msgstr ""
 "TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -2091,13 +2090,13 @@ msgstr ""
 "restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Ενεργοποίηση Εκκίνησης με τη μέθοδο PXE στη ρύθμιση του DHCP"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2170,13 +2169,13 @@ msgstr ""
 "\"tftp-images\"/> στη συνέχεια)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Ρύθμιση ενός εξυπηρετητή BOOTP"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2192,7 +2191,7 @@ msgstr ""
 "classname> και <classname>dhcp3-server</classname> αντίστοιχα."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2258,7 +2257,7 @@ msgstr ""
 "userinput> είναι η διεύθυνση MAC του μηχανήματος.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2283,13 +2282,13 @@ msgstr ""
 "την εντολή <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Ενεργοποίηση του εξυπηρετητή TFTP"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2299,7 +2298,7 @@ msgstr ""
 "είναι ενεργοποιημένος ο <command>tftpd</command>"
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2316,7 +2315,7 @@ msgstr ""
 "μπορεί να αλλάξει με την επαναρύθμιση του πακέτου."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2336,7 +2335,7 @@ msgstr ""
 "παραδείγματα ρυθμίσεων στην παρούσα ενότητα ανάλογα."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2354,7 +2353,7 @@ msgstr ""
 "αφετηρίας για την διάγνωση της αιτίας τέτοιων σφαλμάτων."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2387,13 +2386,13 @@ msgstr ""
 "χρησιμοποιεί ο TFTP server στο Linux."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Μεταφορά των ειδώλων TFTP στη θέση τους"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2411,7 +2410,7 @@ msgstr ""
 "αυτό σταθερά πρότυπα."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2427,13 +2426,13 @@ msgstr ""
 "παρακάτω αρχεία από τον κατάλογο <filename>netboot/</filename>:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2450,7 +2449,7 @@ msgstr ""
 "αρχείου για εκκίνηση."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2467,13 +2466,13 @@ msgstr ""
 "το όνομα του αρχείου εκκίνησης."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Εκκίνηση με TFTP για SPARC"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2506,7 +2505,7 @@ msgstr ""
 "προσθέσετε στο τέλος το όνομα της υποαρχιτεκτονικής."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2520,7 +2519,7 @@ msgstr ""
 "εξυπηρετητή tftp για να δείτε ποιο όνομα εικόνας ζητείται."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2535,13 +2534,13 @@ msgstr ""
 "ψάχνει ο server TFTP."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Εκκίνηση TFTP για SGI"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2556,13 +2555,13 @@ msgstr ""
 "userinput> στο αρχείο <filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Αυτόματη Εγκατάσταση"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2580,13 +2579,13 @@ msgstr ""
 "για αναλυτικότερες πληροφορίες."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Αυτόματη εγκατάσταση με χρήση του &debian; Installer "
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2601,7 +2600,7 @@ msgstr ""
 "εγκατάστασης."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/es/boot-installer.po b/po/es/boot-installer.po
index 225c7b25a..cca84665e 100644
--- a/po/es/boot-installer.po
+++ b/po/es/boot-installer.po
@@ -37,7 +37,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-08-01 18:36+0200\n"
 "Last-Translator: Javier Fernández-Sanguino <jfs@debian.org>\n"
 "Language-Team: Debian l10n Spanish <debian-l10n-spanish@lists.debian.org>\n"
@@ -96,8 +96,8 @@ msgid "Booting from TFTP"
 msgstr "Arrancar desde TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -107,8 +107,8 @@ msgstr ""
 "servidor de arranque TFTP (DHCP, RARP o BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -118,8 +118,8 @@ msgstr ""
 "RBOOT en lugar de uno BOOTP."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -135,8 +135,8 @@ msgid "Booting from CD-ROM"
 msgstr "Arrancar desde CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -153,8 +153,8 @@ msgstr ""
 "próximo capítulo."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -170,8 +170,8 @@ msgstr ""
 "que podrían funcionar en su caso."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -187,8 +187,8 @@ msgstr ""
 "adicionales, haga que el sistema de instalación use la unidad de CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -434,8 +434,8 @@ msgid "The installer will now start as usual."
 msgstr "El instalador arrancará de la forma habitual."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Arranque desde un CD-ROM"
@@ -454,17 +454,23 @@ msgstr "Para iniciar el instalador desde Windows, puede"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "obtener primero un medio de instalación en CD-ROM/DVD-ROM o una memoria USB "
 "como se describe en <xref linkend=\"official-cdrom\"/> y <xref linkend="
 "\"boot-usb-files\"/>, o bien"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -475,7 +481,7 @@ msgstr ""
 "de &debian;,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -491,7 +497,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -503,13 +509,13 @@ msgstr ""
 "&debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Arranque desde DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -519,7 +525,7 @@ msgstr ""
 "disco de restauración o diagnóstico."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -537,7 +543,7 @@ msgstr ""
 "actual si es necesario."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -559,7 +565,7 @@ msgstr ""
 "command>. El núcleo se cargará y arrancará el sistema del instalador."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -567,7 +573,7 @@ msgstr ""
 "Arranque desde Linux usando <command>LILO</command> o <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -578,7 +584,7 @@ msgstr ""
 "\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -596,7 +602,7 @@ msgstr ""
 "aunque debe hacerlo con cuidado."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -615,7 +621,7 @@ msgstr ""
 "CD/DVD, sin necesitar la red."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -633,7 +639,7 @@ msgstr ""
 "un ejemplo de <filename>/etc/lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -645,7 +651,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -661,7 +667,7 @@ msgstr ""
 "<userinput>lilo</userinput> y reinicie."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -678,7 +684,7 @@ msgstr ""
 "el sistema):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -692,7 +698,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -704,7 +710,7 @@ msgstr ""
 "filename>. La entrada para el instalador podría ser, por ejemplo:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -724,7 +730,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -734,13 +740,13 @@ msgstr ""
 "command> o <command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Arranque desde un dispositivo de memoria USB"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -765,13 +771,13 @@ msgstr ""
 "adicionales o simplemente presionar &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Arranque desde disquetes"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -781,7 +787,7 @@ msgstr ""
 "disquetes desde éstas como se explica en <xref linkend=\"create-floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -792,7 +798,7 @@ msgstr ""
 "enciéndalo nuevamente."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -811,7 +817,7 @@ msgstr ""
 "<userinput>install root=/dev/hdc</userinput> en el cursor de arranque."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -828,7 +834,7 @@ msgstr ""
 "en forma <quote>forzada</quote> o total cuando arranque."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -838,7 +844,7 @@ msgstr ""
 "de arranque y finalice mostrando el cursor <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -855,7 +861,7 @@ msgstr ""
 "de arranque en <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -869,26 +875,26 @@ msgstr ""
 "installer</command> se cargará automáticamente."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Arranque con TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Existen varias formas de realizar un arranque con TFTP en i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "Tarjetas de red o placas base que aceptan PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -902,13 +908,13 @@ msgstr ""
 "posibilidad de configurar su BIOS para arrancar desde la red."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "Tarjeta de red con bootROM"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -918,7 +924,7 @@ msgstr ""
 "usando TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -928,13 +934,13 @@ msgstr ""
 "favor, haga referencia a este documento."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -945,13 +951,13 @@ msgstr ""
 "arranque usando TFTP."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "La pantalla de arranque"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -988,7 +994,7 @@ msgstr ""
 "práctica casi dobla el número de opciones."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -1004,7 +1010,7 @@ msgstr ""
 "presione &enterkey; para iniciar el instalador."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -1016,7 +1022,7 @@ msgstr ""
 "instalaciones automatizadas."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1035,7 +1041,7 @@ msgstr ""
 "arranque y deshará cualquier cambio que usted haya hecho."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1088,7 +1094,7 @@ msgstr ""
 "userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1107,7 +1113,7 @@ msgstr ""
 "referencia para encontrar las teclas correctas a usar."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1128,7 +1134,7 @@ msgstr ""
 "(IRA)."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1149,13 +1155,13 @@ msgstr ""
 "describe en el texto de ayuda."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Contenidos del CD"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1180,7 +1186,7 @@ msgstr ""
 "acceder a la red."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1207,7 +1213,7 @@ msgstr ""
 "bloque de arranque en sistemas más convencionales."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1224,7 +1230,7 @@ msgstr ""
 "intérprete de órdenes de EFI como se describe a continuación."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1247,7 +1253,7 @@ msgstr ""
 "la instalación prosiga."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1270,13 +1276,13 @@ msgstr ""
 "por alguna razón el CD no arranca con ésta, use la segunda opción."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "IMPORTANTE"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1297,14 +1303,14 @@ msgstr ""
 "órdenes."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 "Opción 1: Arrancar desde la opción de arranque de mantenimiento del menú"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1316,7 +1322,7 @@ msgstr ""
 "finalice la inicialización del sistema."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1327,7 +1333,7 @@ msgstr ""
 "menú."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1346,7 +1352,7 @@ msgstr ""
 "mismas."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1365,7 +1371,7 @@ msgstr ""
 "siguiente (y adicional)."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1381,7 +1387,7 @@ msgstr ""
 "command>. Esto iniciará la secuencia de arranque."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1393,13 +1399,13 @@ msgstr ""
 "elegirlas."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Opción 2: Arrancar desde el intérprete de órdenes de EFI"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1413,7 +1419,7 @@ msgstr ""
 "instalador de &debian; con los siguientes pasos:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1425,7 +1431,7 @@ msgstr ""
 "inicialización del sistema."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1449,7 +1455,7 @@ msgstr ""
 "la unidad de CD."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1463,7 +1469,7 @@ msgstr ""
 "serán mostrados como <filename>fs<replaceable>n</replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1477,7 +1483,7 @@ msgstr ""
 "como su cursor."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1487,7 +1493,7 @@ msgstr ""
 "iniciará la secuencia de arranque."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1503,13 +1509,13 @@ msgstr ""
 "a elegir el núcleo de arranque y las opciones."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Instalar usando una consola en el puerto serie"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1529,7 +1535,7 @@ msgstr ""
 "comunes de ttyS0."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1543,7 +1549,7 @@ msgstr ""
 "<command>baud</command> en el intérprete de órdenes de EFI."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1559,7 +1565,7 @@ msgstr ""
 "command> en la ventana de texto <classname>Boot:</classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1578,7 +1584,7 @@ msgstr ""
 "modo texto."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1592,13 +1598,13 @@ msgstr ""
 "instalación."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Elegir el núcleo de arranque y opciones"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1619,7 +1625,7 @@ msgstr ""
 "opciones comunes de línea de órdenes."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1644,7 +1650,7 @@ msgstr ""
 "instalación:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1654,7 +1660,7 @@ msgstr ""
 "necesidades con las teclas de desplazamiento."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1667,7 +1673,7 @@ msgstr ""
 "consola serie)."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1679,7 +1685,7 @@ msgstr ""
 "pantalla del instalador de &debian;."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1689,7 +1695,7 @@ msgstr ""
 "configurará su idioma, red y particiones de disco."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1709,7 +1715,7 @@ msgstr ""
 "red en lugar de la unidad de CD."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1724,13 +1730,13 @@ msgstr ""
 "carga a través de la red."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Configurar el servidor"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1754,7 +1760,7 @@ msgstr ""
 "command> se ejecute en el cliente."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1770,7 +1776,7 @@ msgstr ""
 "installer</filename> con los ficheros de arranque para un sistema IA-64."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1788,7 +1794,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1811,13 +1817,13 @@ msgstr ""
 "detalles."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Configurar el cliente"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1848,7 +1854,7 @@ msgstr ""
 "<filename>elilo.efi</filename> desde el servidor."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1864,13 +1870,13 @@ msgstr ""
 "instalarse a través de la red, se iniciará el instalador de &debian;."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Arranque TFTP en sistemas SGI"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1892,13 +1898,13 @@ msgstr ""
 "</screen></informalexample> en el monitor de órdenes para efectuarlo."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Parámetros de arranque"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1908,7 +1914,7 @@ msgstr ""
 "():</command> en el monitor de órdenes."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1926,19 +1932,19 @@ msgstr ""
 "pasar con <command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Arrancar Cobalt por TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1956,7 +1962,7 @@ msgstr ""
 "distintas opciones en su pantalla. Estos son los dos métodos de instalación:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1972,7 +1978,7 @@ msgstr ""
 "instalación cuando se conecte al equipo con un cliente SSH."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1984,7 +1990,7 @@ msgstr ""
 "instalación."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1997,13 +2003,13 @@ msgstr ""
 "<replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Limitaciones de s390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -2013,7 +2019,7 @@ msgstr ""
 "red y una sesión ssh que funcionen en S/390."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -2027,13 +2033,13 @@ msgstr ""
 "estándar."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Parámetros de arranque de s390"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -2046,7 +2052,7 @@ msgstr ""
 "<filename>parmfile.debian</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2064,7 +2070,7 @@ msgstr ""
 "el dispositivo de CD/DVD."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2083,13 +2089,13 @@ msgstr ""
 "desde el dispositivo CD/DVD predeterminado instalado en la fábrica."
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2106,7 +2112,7 @@ msgstr ""
 "indicar al instalador que busque los ficheros necesarios en el CD."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2118,19 +2124,19 @@ msgstr ""
 "encendido, y cuando aparezca la pantalla de SmartFirmware, escriba"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Arranque desde el disco duro"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2141,7 +2147,7 @@ msgstr ""
 "compatible."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2153,13 +2159,13 @@ msgstr ""
 "<xref linkend=\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Arrancar PowerMacs OldWorld desde MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2182,13 +2188,13 @@ msgstr ""
 "cargar el instalador."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Arrancar Macs NewWorld desde OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2231,13 +2237,13 @@ msgstr ""
 "funciona. Entonces se iniciará el programa de instalación de &debian;."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Arranque desde un dispositivo de memoria USB"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2245,7 +2251,7 @@ msgstr ""
 "USB."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2260,7 +2266,7 @@ msgstr ""
 "<xref linkend=\"invoking-openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2283,7 +2289,7 @@ msgstr ""
 "filename>, y <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2309,7 +2315,7 @@ msgstr ""
 "<command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2321,7 +2327,7 @@ msgstr ""
 "adicionales o sólo pulsar &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2334,7 +2340,7 @@ msgstr ""
 "linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2342,7 +2348,7 @@ msgstr ""
 "desde red."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2378,7 +2384,7 @@ msgstr ""
 "algunos sistemas PReP (como por ejemplo en los equipos Motorola PowerStack)."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2392,7 +2398,7 @@ msgstr ""
 "desde unidades de disquete conectadas a través de USB."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2404,7 +2410,7 @@ msgstr ""
 "de presionar el botón de encendido."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2419,7 +2425,7 @@ msgstr ""
 "en el disco duro."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2432,13 +2438,13 @@ msgstr ""
 "cargado en memoria."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "Parámetros de arranque de PowerPC"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2454,7 +2460,7 @@ msgstr ""
 "una tarjeta Rage 128, use <userinput>video=aty128fb:vmode:6</userinput> ."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2474,7 +2480,7 @@ msgstr ""
 "i; a continuación de la orden <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2487,13 +2493,13 @@ msgstr ""
 "IDE)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "Mensajes de IDPROM"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2509,13 +2515,13 @@ msgstr ""
 "ulink> para mayor información."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Accesibilidad"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2545,13 +2551,13 @@ msgstr ""
 "arranque asume que su teclado es de tipo QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "Dispositivos Braille USB"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2573,13 +2579,13 @@ msgstr ""
 "\">sitio web de <classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Dispositivos Braille Seriales"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2621,13 +2627,13 @@ msgstr ""
 "help;\">sitio web de <classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "Software de Síntesis de Voz"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2643,13 +2649,13 @@ msgstr ""
 "<classname>espeak</classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Dispositivos de Síntesis de Voz"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2661,7 +2667,7 @@ msgstr ""
 "opción <quote>Instalación Gráfica</quote> en el menú de arranque."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2685,13 +2691,13 @@ msgstr ""
 "destino."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Dispositivos de Tarjeta"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2708,7 +2714,7 @@ msgstr ""
 "esto reduce el número de idiomas disponibles."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2719,13 +2725,13 @@ msgstr ""
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Temas de Alto contraste"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2737,13 +2743,13 @@ msgstr ""
 "parámetro de arranque <userinput>theme=dark</userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Preconfiguración"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2754,7 +2760,7 @@ msgstr ""
 "documentado en <xref linkend=\"appendix-preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2769,7 +2775,7 @@ msgstr ""
 "su núcleo en algunos casos."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2785,7 +2791,7 @@ msgstr ""
 "informar a su sistema del hardware del que dispone."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2802,7 +2808,7 @@ msgstr ""
 "adelante en la <xref linkend=\"boot-troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2844,7 +2850,7 @@ msgstr ""
 "el &d-i; es <userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2890,7 +2896,7 @@ msgstr ""
 "el &d-i; es <userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2904,13 +2910,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Parámetros del instalador de &debian;"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2925,7 +2931,7 @@ msgstr ""
 "un fallo. </para> </footnote> pueden serle útiles."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2941,13 +2947,13 @@ msgstr ""
 "Los ejemplos en este manual generalmente utilizan la forma simplificada."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
@@ -2956,7 +2962,7 @@ msgstr ""
 "prioridad a la aquí definida."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2970,7 +2976,7 @@ msgstr ""
 "instalador, sin embargo, ajustará esta prioridad si se produce algún error."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2990,13 +2996,13 @@ msgstr ""
 "críticos e intentará hacer lo correcto sin formular muchas preguntas."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -3033,13 +3039,13 @@ msgstr ""
 "userinput> en las arquitecturas en las que es compatible."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -3053,49 +3059,49 @@ msgstr ""
 "arranque (salga del intérprete para continuar con el proceso de arranque)."
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Este es el valor predeterminado."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Más detallado de lo habitual."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Incluye mucha información de depuración."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -3106,13 +3112,13 @@ msgstr ""
 "órdenes para proseguir con el arranque."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3124,7 +3130,7 @@ msgstr ""
 "floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3135,19 +3141,19 @@ msgstr ""
 "este parámetro para que busque sólo en un dispositivo concreto."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3159,13 +3165,13 @@ msgstr ""
 "valor predeterminado para syslog es su valor estándar de puerto, 514."
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3177,13 +3183,13 @@ msgstr ""
 "valores posibles son 1 y 2, consulte <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3194,13 +3200,13 @@ msgstr ""
 "la seguridad física es limitada."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3220,13 +3226,13 @@ msgstr ""
 "congelado algunos minutos después de iniciarse la instalación."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Se han observado este tipo de problemas en hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3247,13 +3253,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3270,13 +3276,13 @@ msgstr ""
 "instalador con <userinput>theme=<replaceable>dark</replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3290,7 +3296,7 @@ msgstr ""
 "manual en el caso de que falle la solicitud DHCP."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3305,13 +3311,13 @@ msgstr ""
 "no proporciona valores correctos."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3323,13 +3329,13 @@ msgstr ""
 "deshabilitarlo."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3344,13 +3350,13 @@ msgstr ""
 "wiki;\">Wiki del Instalador de &debian;</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3361,13 +3367,13 @@ msgstr ""
 "\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3378,13 +3384,13 @@ msgstr ""
 "install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3401,13 +3407,13 @@ msgstr ""
 "éstos. Para más información consulte <xref linkend=\"preseed-seenflag\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3420,13 +3426,13 @@ msgstr ""
 "instalaciones automatizadas."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3439,13 +3445,13 @@ msgstr ""
 "evitarlo."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3464,7 +3470,7 @@ msgstr ""
 "pueden recargar el medio automáticamente."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3477,13 +3483,13 @@ msgstr ""
 "instalación inicial."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3498,7 +3504,7 @@ msgstr ""
 "install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3514,13 +3520,13 @@ msgstr ""
 "ello, sólo los usuarios muy experimentados deberían usar esta opción."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3534,13 +3540,13 @@ msgstr ""
 "\">Aviso: inseguro, no recomendado.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3552,13 +3558,13 @@ msgstr ""
 "que el disco de ram no se cargó por completo. El valor se debe dar en kB."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3569,13 +3575,13 @@ msgstr ""
 "consulte <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Utilizar parámetros de arranque para responder a preguntas"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3590,25 +3596,25 @@ msgstr ""
 "\"preseed-bootparms\"/>. A continuación se listan algunos ejemplos."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3618,7 +3624,7 @@ msgstr ""
 "de instalación y en el sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3638,7 +3644,7 @@ msgstr ""
 "idioma, país y locale."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3654,13 +3660,13 @@ msgstr ""
 "country=DE locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3677,7 +3683,7 @@ msgstr ""
 "configuración PPPoE)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3687,13 +3693,13 @@ msgstr ""
 "DHCP y forzar la configuración estática de la red."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3711,13 +3717,13 @@ msgstr ""
 "introducir el nombre del sistema donde está la réplica manualmente."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3729,13 +3735,13 @@ msgstr ""
 "literal>. Para más información consulte <xref linkend=\"pkgsel\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Pasar parámetros a módulos del núcleo"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3761,7 +3767,7 @@ msgstr ""
 "configuración utilizada en el sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3776,7 +3782,7 @@ msgstr ""
 "pasar parámetros manualmente."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3798,19 +3804,19 @@ msgstr ""
 "conector BNC (coaxial) y la interrupción (IRQ) 10 debería utiliza:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Poner módulos del núcleo en una lista negra"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3829,7 +3835,7 @@ msgstr ""
 "erróneo primero."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3845,7 +3851,7 @@ msgstr ""
 "en el sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3859,19 +3865,19 @@ msgstr ""
 "durante las fases de detección de hardware."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Resolución de problemas en el proceso de instalación"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Fiabilidad de la unidad de CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3886,7 +3892,7 @@ msgstr ""
 "instalación."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3898,13 +3904,13 @@ msgstr ""
 "demás depende de usted."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Hay dos cosas muy sencillas que debería intentar primero."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3914,7 +3920,7 @@ msgstr ""
 "está sucio."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3933,7 +3939,7 @@ msgstr ""
 "con DMA en unidades de CD-ROM antiguas se resuelven de esta forma."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3947,7 +3953,7 @@ msgstr ""
 "simplificar el texto."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3957,13 +3963,13 @@ msgstr ""
 "disponible si no consigue que la instalación funcione mediante CD-ROM."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Problemas habituales"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3973,7 +3979,7 @@ msgstr ""
 "altas velocidades con grabadores de CD modernos."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3986,13 +3992,13 @@ msgstr ""
 "la función <quote>direct memory access</quote> (DMA)."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Cómo investigar y, quizás, solucionar problemas"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
@@ -4000,7 +4006,7 @@ msgstr ""
 "continuación."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -4015,7 +4021,7 @@ msgstr ""
 "medio de almacenamiento que está usando."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -4042,7 +4048,7 @@ msgstr ""
 "el número de bytes correcto del CD-ROM."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -4064,7 +4070,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -4087,7 +4093,7 @@ msgstr ""
 "cualquiera de estas órdenes."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -4100,7 +4106,7 @@ msgstr ""
 "compruebe también la salida de ejecutar <command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -4131,7 +4137,7 @@ msgstr ""
 "<command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -4144,7 +4150,7 @@ msgstr ""
 "filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4161,7 +4167,7 @@ msgstr ""
 "después de ejecutar esta orden."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4187,7 +4193,7 @@ msgstr ""
 "dispositivo que corresponde a su unidad de CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4201,13 +4207,13 @@ msgstr ""
 "determinar si el CD-ROM se puede leer con fiabilidad."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Fiabilidad de los disquetes"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4217,7 +4223,7 @@ msgstr ""
 "instalar &debian; por primera vez suele ser la fiabilidad de los disquetes."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4236,7 +4242,7 @@ msgstr ""
 "gran cantidad de mensajes sobre errores E/S del disquete."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4254,7 +4260,7 @@ msgstr ""
 "puede ser útil intentar escribir en el disquete en un sistema diferente."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4266,7 +4272,7 @@ msgstr ""
 "correctamente con el tercer disquete."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4279,7 +4285,7 @@ msgstr ""
 "comprobación de sus sumas de control md5."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4292,13 +4298,13 @@ msgstr ""
 "defectuosos."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Configuración del arranque"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4312,7 +4318,7 @@ msgstr ""
 "de arranque, como se explica en <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4321,7 +4327,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4340,37 +4346,37 @@ msgstr ""
 "(por ejemplo, desde un Live CD)."
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Problemas comunes durante la instalación en &arch-title;"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4380,7 +4386,7 @@ msgstr ""
 "resolverse o evitarse pasando ciertos parámetros de arranque al instalador."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4402,13 +4408,13 @@ msgstr ""
 "<xref linkend=\"boot-parms\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Parada del sistema durante la fase de configuración de PCMCIA"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4437,7 +4443,7 @@ msgstr ""
 "recursos que causa el problema."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4460,7 +4466,7 @@ msgstr ""
 "hay, cuando introduzca este valor en el instalador."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
@@ -4468,13 +4474,13 @@ msgstr ""
 "mencionar."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Salida de vídeo mal dirigida"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4502,7 +4508,7 @@ msgstr ""
 "<userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4517,13 +4523,13 @@ msgstr ""
 "filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Fallo en el arranque o la instalación de CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4535,7 +4541,7 @@ msgstr ""
 "mayoría de los problemas de este tipo se han reportado en sistemas SunBlade."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4543,13 +4549,13 @@ msgstr ""
 "instalador."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Interpretar los mensajes de inicio del núcleo"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4587,13 +4593,13 @@ msgstr ""
 "piensa que el tiempo que tarda en arrancar el sistema es muy largo."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Informar de fallos"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4613,7 +4619,7 @@ msgstr ""
 "fallos."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4626,13 +4632,13 @@ msgstr ""
 "instalado."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Enviar los informes de la instalación"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4646,7 +4652,7 @@ msgstr ""
 "configuraciones de hardware."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4659,7 +4665,7 @@ msgstr ""
 "importa que se haga público."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4678,7 +4684,7 @@ msgstr ""
 "la orden <command>reportbug installation-reports</command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/es/install-methods.po b/po/es/install-methods.po
index 6124dc1a7..566e869fe 100644
--- a/po/es/install-methods.po
+++ b/po/es/install-methods.po
@@ -36,7 +36,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: debian-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-31 23:27+0200\n"
 "Last-Translator: Javier Fernández-Sanguino <jfs@debian.org>\n"
 "Language-Team: Debian l10n Spanish <debian-l10n-spanish@lists.debian.org>\n"
@@ -113,15 +113,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -163,7 +162,7 @@ msgstr ""
 "los mismos directorios y subdirectorios en su CD."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -173,7 +172,7 @@ msgstr ""
 "ficheros necesarios desde el CD."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -192,13 +191,13 @@ msgstr ""
 "puedan usarse para arrancar el instalador."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Descarga de ficheros desde réplicas de &debian;"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -208,7 +207,7 @@ msgstr ""
 "la <ulink url=\"&url-debian-mirrors;\">lista de réplicas de &debian;</ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -219,13 +218,13 @@ msgstr ""
 "en modo texto o automático."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Dónde encontrar las imágenes de instalación"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -241,13 +240,13 @@ msgstr ""
 "ulink> contiene una lista con cada imagen y su propósito."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Ficheros de instalación para Thecus N2100"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -261,13 +260,13 @@ msgstr ""
 "obtener esta imagen del firmware de &n2100-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Ficheros de instalación para GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -279,13 +278,13 @@ msgstr ""
 "&glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Ficheros de instalación para Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -297,13 +296,13 @@ msgstr ""
 "&kuroboxpro-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Ficheros de instalación para HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -319,13 +318,13 @@ msgstr ""
 "firmware de &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Ficheros de instalación para QNAP Turbo Station"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -339,13 +338,13 @@ msgstr ""
 "TS-21x y TS-41x desde &qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Ficheros de instalación para PC de enchufe y OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -362,14 +361,14 @@ msgstr ""
 "marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "GLAN Tank Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "Ficheros de instalación para GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -387,13 +386,13 @@ msgstr ""
 "marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Creación de una cinta IPL"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -416,13 +415,13 @@ msgstr ""
 "linkend=\"where-files\"/>."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Creación de disquetes desde imágenes de disco"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -433,7 +432,7 @@ msgstr ""
 "métodos."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -443,7 +442,7 @@ msgstr ""
 "unidades de disquete USB de Mac."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -464,7 +463,7 @@ msgstr ""
 "fichero en el disquete."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -476,7 +475,7 @@ msgstr ""
 "diferentes plataformas."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -492,7 +491,7 @@ msgstr ""
 "instalación en CD-ROM ó DVD. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -504,13 +503,13 @@ msgstr ""
 "escrito en ellos, para asegurarse de que no se dañen sin querer."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Escritura de las imágenes de disco desde un sistema Linux o Unix"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -548,7 +547,7 @@ msgstr ""
 "</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -583,7 +582,7 @@ msgstr ""
 "filename>). En otros sistemas, pregunte a su administrador </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -595,13 +594,13 @@ msgstr ""
 "instalarlo."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Escritura de imágenes de disco desde DOS, Windows u OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -611,7 +610,7 @@ msgstr ""
 "programas para copiar las imágenes a los disquetes."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -627,7 +626,7 @@ msgstr ""
 "de Windows <emphasis>no</emphasis> se espera que funcionen."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -639,7 +638,7 @@ msgstr ""
 "desempaquetar diskio.dll en el mismo directorio."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -649,13 +648,13 @@ msgstr ""
 "bajo el directorio <filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Escritura de imágenes de disco desde MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -678,7 +677,7 @@ msgstr ""
 "imagen en él."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -693,13 +692,13 @@ msgstr ""
 "disquete con estas herramientas."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Escritura de imágenes de disco con <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -714,7 +713,7 @@ msgstr ""
 "réplica de &debian;."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -724,7 +723,7 @@ msgstr ""
 "y úselo para abrir el fichero <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -736,7 +735,7 @@ msgstr ""
 "sensibles a las mayúsculas y minúsculas."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -752,7 +751,7 @@ msgstr ""
 "imagen es montada accidentalmente."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -764,7 +763,7 @@ msgstr ""
 "diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -781,13 +780,13 @@ msgstr ""
 "disquete."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Escritura de imágenes de disco con <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -801,7 +800,7 @@ msgstr ""
 "userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -810,7 +809,7 @@ msgstr ""
 "(inicia en el sector 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -819,7 +818,7 @@ msgstr ""
 "fichero."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -833,7 +832,7 @@ msgstr ""
 "deséchelo e inténtelo con otro."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -845,14 +844,14 @@ msgstr ""
 "accidentalmente, y éste lo estropearía."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 "Preparación de ficheros para el arranque desde un dispositivo de memoria USB"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -877,7 +876,7 @@ msgstr ""
 "seguro de protección contra escritura."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -891,14 +890,14 @@ msgstr ""
 "perdiendo toda la información de, por ejemplo, un disco duro."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 "Preparación de una memoria USB utilizando una imagen de CD o DVD híbrida"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -913,7 +912,7 @@ msgstr ""
 "información sobre cómo obtener una imagen de CD o DVD."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -926,7 +925,7 @@ msgstr ""
 "filename> (en la ubicación mencionada en <xref linkend=\"where-files\"/>)."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -946,7 +945,7 @@ msgstr ""
 "firmware."
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -962,7 +961,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -977,7 +976,7 @@ msgstr ""
 "desmontado el dispositivo USB:"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -989,7 +988,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -1001,13 +1000,13 @@ msgstr ""
 "más complejos, generalmente para personas con necesidades especiales."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "Copia manual de los ficheros a la memoria USB"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -1022,7 +1021,7 @@ msgstr ""
 "linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -1038,7 +1037,7 @@ msgstr ""
 "<classname>yaboot</classname> y su fichero de configuración</phrase>."
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -1054,7 +1053,7 @@ msgstr ""
 "reparticionarla y crear un nuevo sistema de ficheros"
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
@@ -1062,13 +1061,13 @@ msgstr ""
 "USB:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt;/dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1080,13 +1079,13 @@ msgstr ""
 "y extraiga la imagen directamente a éste:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt;/dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1117,14 +1116,14 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>) y habrá terminado."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 "Copia manual de los ficheros a la memoria USB &mdash; la forma flexible"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1140,13 +1139,13 @@ msgstr ""
 "completa de CD en ella."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Particionado de las memorias USB"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1156,7 +1155,7 @@ msgstr ""
 "partición en lugar de todo el dispositivo."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1199,7 +1198,7 @@ msgstr ""
 "encuentra en el paquete <classname>dosfstools</classname> de &debian;."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1218,7 +1217,7 @@ msgstr ""
 "cambios a la configuración del gestor de arranque."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1243,13 +1242,13 @@ msgstr ""
 "que contiene el código del gestor de arranque."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Añadir la imagen del instalador"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1274,7 +1273,7 @@ msgstr ""
 "nombres de ficheros estilo DOS (8.3)."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1309,7 +1308,7 @@ msgstr ""
 "adicionar <userinput>vga=788</userinput> a la segunda línea."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1317,7 +1316,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy "
@@ -1345,7 +1344,7 @@ msgstr ""
 "desmonte la memoria USB, (<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1375,7 +1374,7 @@ msgstr ""
 "command> en el paquete &debian; <classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1392,7 +1391,7 @@ msgstr ""
 "HFS para hacer cambios a la configuración del gestor de arranque."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1429,7 +1428,7 @@ msgstr ""
 "con las herramientas habituales de Unix."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1440,31 +1439,31 @@ msgstr ""
 "al dispositivo de memoria:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (binario del núcleo)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (imagen inicial de memoria ram)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (fichero de configuración de yaboot)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (mensaje de arranque opcional)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1500,13 +1499,13 @@ msgstr ""
 "a arrancar."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Preparación de los ficheros para arranque desde el disco duro"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1518,7 +1517,7 @@ msgstr ""
 "operativo o ejecutando directamente un gestor de arranque desde la BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1532,7 +1531,7 @@ msgstr ""
 "muchos, y poco fiables, disquetes."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1555,7 +1554,7 @@ msgstr ""
 "de instalación que descargue."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1567,7 +1566,7 @@ msgstr ""
 "quote> u <quote>OldWorld</quote>."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1577,7 +1576,7 @@ msgstr ""
 "command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1587,7 +1586,7 @@ msgstr ""
 "Linux existente usando <command>LILO</command> o <command>GRUB</command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1599,7 +1598,7 @@ msgstr ""
 "usar este disco RAM como sistema de ficheros raíz."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1612,19 +1611,19 @@ msgstr ""
 "boot/newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (binario del núcleo)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (imagen de disco RAM)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1634,14 +1633,14 @@ msgstr ""
 "\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 "Arranque del instalador desde el disco duro usando <command>loadlin</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1651,7 +1650,7 @@ msgstr ""
 "desde DOS usando <command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1661,7 +1660,7 @@ msgstr ""
 "<filename>c:\\</filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1670,19 +1669,19 @@ msgstr ""
 "RAM)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (herramienta loadlin)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Arranque del instalador desde el disco duro en Macs OldWorld"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1706,7 +1705,7 @@ msgstr ""
 "necesita <application>BootX</application> en ese modelo."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1734,13 +1733,13 @@ msgstr ""
 "Kernels</filename> en la carpeta «System» activa."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Arranque del instalador desde el disco duro en Macs NewWorld"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1761,7 +1760,7 @@ msgstr ""
 "no debe usarse en PowerMacs NewWorld."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1775,31 +1774,31 @@ msgstr ""
 "tecla <keycap>option</keycap>)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1815,21 +1814,21 @@ msgstr ""
 "de «Open Firmware» cuando arranque el instalador."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 "Para arrancar el instalador, continúe en <xref linkend=\"boot-newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 "Preparación de los ficheros para el arranque a través de red usando TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1845,7 +1844,7 @@ msgstr ""
 "esa máquina, y debe configurarla para permitir el arranque desde ella."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1858,7 +1857,7 @@ msgstr ""
 "BOOTP</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1880,7 +1879,7 @@ msgstr ""
 "través de DHCP."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1892,7 +1891,7 @@ msgstr ""
 "solamente pueden arrancar usando BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1903,7 +1902,7 @@ msgstr ""
 "&debian;."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1918,7 +1917,7 @@ msgstr ""
 "(conocido también como Solaris) y GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1932,13 +1931,13 @@ msgstr ""
 "problemas. Una buena alternativa es <classname>atftpd</classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Configuración del servidor RARP"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1958,7 +1957,7 @@ msgstr ""
 "addr show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1983,13 +1982,13 @@ msgstr ""
 "y en SunOS 4 (Solaris 1) utilice <userinput>/usr/etc/rarpd -a</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Configuración del servidor DHCP"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -2003,7 +2002,7 @@ msgstr ""
 "(consulte <filename>/etc/dhcpd3/dhcpd.conf</filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -2047,7 +2046,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -2065,7 +2064,7 @@ msgstr ""
 "que se recuperará a través de TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -2075,13 +2074,13 @@ msgstr ""
 "reinícielo con <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Habilitar el arranque PXE en la configuración DHCP"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2152,13 +2151,13 @@ msgstr ""
 "imagen de núcleo (vea <xref linkend=\"tftp-images\"/> a continuación)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Configuración del servidor BOOTP"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2174,7 +2173,7 @@ msgstr ""
 "respectivamente."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2240,7 +2239,7 @@ msgstr ""
 "phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2265,13 +2264,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Habilitar el servidor TFTP"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2281,7 +2280,7 @@ msgstr ""
 "<command>tftpd</command> está instalada."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2297,7 +2296,7 @@ msgstr ""
 "paquete, y se puede modificar reconfigurando el paquete."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2316,7 +2315,7 @@ msgstr ""
 "ejemplos de configuración en esta sección si la ubicación varía."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2333,7 +2332,7 @@ msgstr ""
 "buen punto de partida para diagnosticar la causa de los errores."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2364,13 +2363,13 @@ msgstr ""
 "el servidor TFTP."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Mover las imágenes TFTP a su ubicación"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2387,7 +2386,7 @@ msgstr ""
 "es determinado por el cliente TFTP, y no existe un estándar definido."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2403,13 +2402,13 @@ msgstr ""
 "filename> los siguientes ficheros:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2426,7 +2425,7 @@ msgstr ""
 "del fichero a arrancar."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2443,13 +2442,13 @@ msgstr ""
 "command> como el nombre del fichero a arrancar."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Arranque de TFTP en SPARC"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2480,7 +2479,7 @@ msgstr ""
 "si es necesario, el nombre de la subarquitectura."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2494,7 +2493,7 @@ msgstr ""
 "solicitando si el cargador no encuentra la imagen."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2508,13 +2507,13 @@ msgstr ""
 "el directorio en el que busca el servidor TFTP."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Arranque TFTP en SGI"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2529,13 +2528,13 @@ msgstr ""
 "filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Instalación automática"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2551,14 +2550,14 @@ msgstr ""
 "la <ulink url=\"http://fai-project.org\">página oficial de FAI</ulink>"
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 "Utilizar el instalador de &debian; para realizar una instalación automática"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2573,7 +2572,7 @@ msgstr ""
 "instalación."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/fi/boot-installer.po b/po/fi/boot-installer.po
index 4bbe1476b..cf4fb5c9f 100644
--- a/po/fi/boot-installer.po
+++ b/po/fi/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Debian Installation Guide boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2010-05-02 10:57+0300\n"
 "Last-Translator: Tapio Lehtonen <tale@debian.org>\n"
 "Language-Team: Finnish <debian-l10n-finnish@lists.debian.org>\n"
@@ -62,8 +62,8 @@ msgid "Booting from TFTP"
 msgstr "Käynnistäminen TFTP:llä"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -73,8 +73,8 @@ msgstr ""
 "käynnistyspalvelinta (DHCP, RARP, tai BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -84,8 +84,8 @@ msgstr ""
 "palvelinta BOOTP:n tilalla."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -101,8 +101,8 @@ msgid "Booting from CD-ROM"
 msgstr "Käynnistäminen CD-levyltä"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -119,8 +119,8 @@ msgstr ""
 "seuraavaan lukuun."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -136,8 +136,8 @@ msgstr ""
 "saattaisivat tässä tilanteessa toimia."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -153,8 +153,8 @@ msgstr ""
 "asennusjärjestelmä asentamaan ne CD-levyltä."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -392,8 +392,8 @@ msgid "The installer will now start as usual."
 msgstr "Asennin käynnistyy nyt tavanomaiseen tapaan."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Käynnistäminen CD-levyltä"
@@ -418,15 +418,17 @@ msgstr ""
 #| "or USB memory stick installation media as described in <xref linkend="
 #| "\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>."
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "Asentimen käynnistäminen Windowsista vaatii ensin asennustaltion noutamisen "
 "CD- tai DVD-levylle tai muistitikulle kohdassa <xref linkend=\"official-cdrom"
 "\"/> tai <xref linkend=\"boot-usb-files\"/> kuvatulla tavalla."
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -434,7 +436,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -450,7 +452,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After the program has been started, a few preliminary questions will be "
@@ -464,14 +466,14 @@ msgstr ""
 "ja järjestelmä valmistetaan käynnistämään &debian-gnu; asennin."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, fuzzy, no-c-format
 #| msgid "Booting from CD-ROM"
 msgid "Booting from DOS"
 msgstr "Käynnistäminen CD-levyltä"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -479,7 +481,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -491,7 +493,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -505,7 +507,7 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -514,7 +516,7 @@ msgstr ""
 "command>:lla"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -525,7 +527,7 @@ msgstr ""
 "drive-files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -543,7 +545,7 @@ msgstr ""
 "tämä olisi tehtävä huolella."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -561,7 +563,7 @@ msgstr ""
 "eikä verkkoa tarvita."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -580,7 +582,7 @@ msgstr ""
 "etc/lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -592,7 +594,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -608,7 +610,7 @@ msgstr ""
 "<userinput>lilo</userinput> ja käynnistä sitten tietokone uudelleen."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The procedure for <command>GRUB</command> is quite similar. Locate your "
@@ -630,7 +632,7 @@ msgstr ""
 "filename> olevan ensimmäisen levyn ensimmäisellä osiolla:"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -644,7 +646,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The procedure for <command>GRUB</command> is quite similar. Locate your "
@@ -664,7 +666,7 @@ msgstr ""
 "filename> olevan ensimmäisen levyn ensimmäisellä osiolla:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, fuzzy, no-c-format
 #| msgid ""
 #| "title  New Install\n"
@@ -686,7 +688,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -696,13 +698,13 @@ msgstr ""
 "<command>LILO</command>:n välillä."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Käynnistys USB-muistilta"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -727,13 +729,13 @@ msgstr ""
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Käynnistäminen levykkeiltä"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -743,7 +745,7 @@ msgstr ""
 "<xref linkend=\"create-floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -754,7 +756,7 @@ msgstr ""
 "virta takaisin."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -772,7 +774,7 @@ msgstr ""
 "käynnistyskehotteessa <userinput>linux root=/dev/hdc</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -789,7 +791,7 @@ msgstr ""
 "laitetta käynnistetään."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -799,7 +801,7 @@ msgstr ""
 "esitellään ja jonka alareunassa on kehote <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -816,7 +818,7 @@ msgstr ""
 "\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -830,26 +832,26 @@ msgstr ""
 "käynnistyy automaattisesti."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Käynnistys TFTP:llä"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "i386:lla on erilaisia tapoja käynnistää TFTP:llä"
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "NIC tai emolevy joka tukee PXE:tä"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -862,13 +864,13 @@ msgstr ""
 "Jos PXE löytyy, voi olla mahdollista asettaa BIOS käynnistämään verkosta."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "NIC jossa on BootROM verkosta käynnistämiseen"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -876,7 +878,7 @@ msgid ""
 msgstr "Verkkokortti osaa ehkä käynnistyä TFTP:llä."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -886,13 +888,13 @@ msgstr ""
 "Viittaa tähän ohjeeseen."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -903,13 +905,13 @@ msgstr ""
 "TFTPbootilla."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Käynnistysruutu"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, fuzzy, no-c-format
 #| msgid ""
 #| "When the installer boots, you should be presented with a friendly "
@@ -956,7 +958,7 @@ msgstr ""
 "<quote>Graphical install</quote>."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, fuzzy, no-c-format
 #| msgid ""
 #| "For a normal installation, select either the <quote>Install</quote> or "
@@ -976,7 +978,7 @@ msgstr ""
 "&mdash; ja käynnistä asennin painamalla &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -988,7 +990,7 @@ msgstr ""
 "automaattisia asennuksia varten."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1007,7 +1009,7 @@ msgstr ""
 "muutokset perutaan. "
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1059,7 +1061,7 @@ msgstr ""
 "(esim. <userinput>install fb=false</userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1076,7 +1078,7 @@ msgstr ""
 "näppäinasettelu</ulink> josta voidaan katsoa näppäimet joita kuuluu painaa."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1096,7 +1098,7 @@ msgstr ""
 "Assistant</quote> (IRA)."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1117,13 +1119,13 @@ msgstr ""
 "neuvontaruudussa lukee."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "CD-levyn sisältö"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1148,7 +1150,7 @@ msgstr ""
 "verkkoyhteyttä."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1175,7 +1177,7 @@ msgstr ""
 "tavanomaisemmissa järjestelmissä."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1191,7 +1193,7 @@ msgstr ""
 "luettavissa EFI:n komentotulkista kuten alla selitetään. "
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1213,7 +1215,7 @@ msgstr ""
 "osio löytyy ennen kuin se päästää asennuksen jatkumaan."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1236,13 +1238,13 @@ msgstr ""
 "toisesta käynnisty, käytä toista vaihtoehtoa."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "TÄRKEÄÄ"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1262,13 +1264,13 @@ msgstr ""
 "Shellin kehotteessa."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Valinta 1: Käynnistäminen Boot Option Maintenance -valikosta"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1279,7 +1281,7 @@ msgstr ""
 "EFI Boot Manager -sivun kun järjestelmän alkuasetukset ovat valmiit."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1289,7 +1291,7 @@ msgstr ""
 "&enterkey;. Tällöin näytetään uusi valikko."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1307,7 +1309,7 @@ msgstr ""
 "ohjaimen tietojen pitäisi olla samat."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1325,7 +1327,7 @@ msgstr ""
 "seuraavaan lisäkohtaan."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1340,7 +1342,7 @@ msgstr ""
 "nuolinäppäimillä ja painamalla &enterkey;. Tämä aloittaa käynnistyslatauksen."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1352,13 +1354,13 @@ msgstr ""
 "käynnistysydin ja valitsimia."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Valinta 2: Käynnistäminen EFI Shell:stä"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1371,7 +1373,7 @@ msgstr ""
 "[Built-in]</command>. Käynnistä &debian;in asennus-CD seuraavasti:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1382,7 +1384,7 @@ msgstr ""
 "EFI Boot Manager -sivun ja valikon kun järjestelmän alkuasetukset on tehty."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1404,7 +1406,7 @@ msgstr ""
 "ylimääräisen sekunnin kun asema käynnistyy."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1418,7 +1420,7 @@ msgstr ""
 "replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1431,7 +1433,7 @@ msgstr ""
 "osion numero. Komentotulkki näyttää nyt osion numeron kehotteena."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1441,7 +1443,7 @@ msgstr ""
 "käynnistää käynnistyslatauksen."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1457,13 +1459,13 @@ msgstr ""
 "ja asetukset."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Asentaminen sarjapäätteen avulla"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1482,7 +1484,7 @@ msgstr ""
 "valmiiksi yleisimmin käytetyt nopeusasetukset laitteelle ttyS0."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1495,7 +1497,7 @@ msgstr ""
 "katsoa komennolla <command>baud</command> EFI:n komentotulkissa."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1511,7 +1513,7 @@ msgstr ""
 "classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1528,7 +1530,7 @@ msgstr ""
 "asennin käynnistetään tekstitilassa."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1542,13 +1544,13 @@ msgstr ""
 "ennen kuin asennus voidaan alottaa."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Käynnistysytimen ja parametrien valinta"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1567,7 +1569,7 @@ msgstr ""
 "<classname>Params</classname> yleiset komentorivin parametrit."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1590,7 +1592,7 @@ msgstr ""
 "asennuksen:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1600,7 +1602,7 @@ msgstr ""
 "asennustapa."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1612,7 +1614,7 @@ msgstr ""
 "asetukset) kirjoitetaan."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1624,7 +1626,7 @@ msgstr ""
 "Installerin ensimmäisen ruutu."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1634,7 +1636,7 @@ msgstr ""
 "verkkoasetukset ja levyosiot."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1653,7 +1655,7 @@ msgstr ""
 "paketit asennetaan verkosta eikä CD-asemasta."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1668,13 +1670,13 @@ msgstr ""
 "asetus, jotta lataus verkosta on käytössä."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Palvelimen asetukset"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1698,7 +1700,7 @@ msgstr ""
 "<command>elilo.efi</command> käynnistettyä asiakaskoneella."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1714,7 +1716,7 @@ msgstr ""
 "järjestelmän käynnistystiedostot."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1732,7 +1734,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1755,13 +1757,13 @@ msgstr ""
 "classname> mukana tulevista ohjeista."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Asiakaskoneen asetukset"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1793,7 +1795,7 @@ msgstr ""
 "noutamiseen TFTP:Llä palvelimelta."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1808,13 +1810,13 @@ msgstr ""
 "ytimen lataus verkosta on valmis, se käynnistää &debian; Installerin."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI:n käynnistäminen TFTP:llä"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1836,13 +1838,13 @@ msgstr ""
 "</screen></informalexample>."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Käynnistysparametrit"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1852,7 +1854,7 @@ msgstr ""
 "<command>bootp():</command>-komennon loppuun."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1870,19 +1872,19 @@ msgstr ""
 "<command>append</command>:n avulla:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Cobaltin käynnistys TFTP:llä"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1900,7 +1902,7 @@ msgstr ""
 "kaksi:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1915,7 +1917,7 @@ msgstr ""
 "laitteeseen kirjaudutaan SSH:lla voidaan asennus aloittaa."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1926,7 +1928,7 @@ msgstr ""
 "115200 bittiä sekunnissa) ja tee asennus tällä tavoin."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1938,13 +1940,13 @@ msgstr ""
 "parametrit muuttujaan <replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390:n rajoitukset"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1954,7 +1956,7 @@ msgstr ""
 "verkkoasetukset ja ssh-istunto."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1967,13 +1969,13 @@ msgstr ""
 "käynnistämällä ssh-istunto, joka käynnistää tavanomaisen asennusjärjestelmän."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390:n käynnistysparametrit"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1985,7 +1987,7 @@ msgstr ""
 "<filename>parmfile.debian</filename> tulee asennusotosten mukana."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2010,7 +2012,7 @@ msgstr ""
 "levyltä."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2022,13 +2024,13 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2044,7 +2046,7 @@ msgstr ""
 "noutamaan tarvittavat tiedostot CD-levyltä."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2053,19 +2055,19 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Käynnistys kiintolevyltä"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2075,7 +2077,7 @@ msgstr ""
 "tapa; joillekin järjestelmille se on ainoa tuettu asennustapa."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2086,13 +2088,13 @@ msgstr ""
 "noutaa ja tallentaa kohdassa <xref linkend=\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "OldWorld PowerMacien käynnistäminen MacOS:stä"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2114,13 +2116,13 @@ msgstr ""
 "painikkeella <guibutton>Linux</guibutton>, se käynnistää asentimen."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "NewWorld Macien käynnistäminen OpenFirmwaresta"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2163,13 +2165,13 @@ msgstr ""
 "&debian;in asentimen pitäisi käynnistyä."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Käynnistys USB-muistilta"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2177,7 +2179,7 @@ msgstr ""
 "muistilta."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2191,7 +2193,7 @@ msgstr ""
 "muistilaitteita etsitä. Katso <xref linkend=\"invoking-openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2214,7 +2216,7 @@ msgstr ""
 "pci@f2000000/usb@1b,1/hub@1/disk@1</filename>"
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2240,7 +2242,7 @@ msgstr ""
 "<command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2252,7 +2254,7 @@ msgstr ""
 "painaa vaan &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2264,14 +2266,14 @@ msgstr ""
 "Asennusraportin teko selitetään kohdassa <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 "Tällä hetkellä PReP ja New World PowerMacit tukevat käynnistystä verkosta."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2312,7 +2314,7 @@ msgstr ""
 "komennoista ja käytettävissä olevista valitsimista."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2326,7 +2328,7 @@ msgstr ""
 "ole tuettu."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2338,7 +2340,7 @@ msgstr ""
 "virtanappulaa."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2352,7 +2354,7 @@ msgstr ""
 "poistetaan asemasta ja laite etsii käynnistyskelpoisia osioita kiintolevyltä."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2364,13 +2366,13 @@ msgstr ""
 "automaattisesti kun juuritiedostojärjestelmä on ladattu muistiin."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC:n käynnistysparametrit"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2386,7 +2388,7 @@ msgstr ""
 "käytä <userinput>video=aty128fb:vmode:6</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2406,7 +2408,7 @@ msgstr ""
 "lopussa."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2419,13 +2421,13 @@ msgstr ""
 "koneessa)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPRO:min viestit"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2440,13 +2442,13 @@ msgstr ""
 "\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Esteettömyys"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some users may need specific support because of e.g. some visual "
@@ -2483,13 +2485,13 @@ msgstr ""
 "laitealustoilla käynnistyslatain olettaa näppäinasettelun olevan QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB pistekirjoitusnäytöt"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2511,13 +2513,13 @@ msgstr ""
 "webbisivulta</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Sarjaportin pistekirjoitusnäytöt"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Serial braille displays cannot safely be automatically detected (since "
@@ -2572,14 +2574,14 @@ msgstr ""
 "\"><classname>brltty</classname>:n webbisivulta</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, fuzzy, no-c-format
 #| msgid "Hardware Speech Synthesis"
 msgid "Software Speech Synthesis"
 msgstr "Puhesyntetisaattorilaitteet"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2590,13 +2592,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Puhesyntetisaattorilaitteet"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Support for hardware speech synthesis devices is available only alongside "
@@ -2612,7 +2614,7 @@ msgstr ""
 "käynnistysvalikossa."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2634,13 +2636,13 @@ msgstr ""
 "puhesyntetisaattorilaitteelle."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Lisälaittekortit"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2657,7 +2659,7 @@ msgstr ""
 "olevien kielten määrää."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2668,13 +2670,13 @@ msgstr ""
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Suurikonstrastinen teema"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2686,13 +2688,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2700,7 +2702,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2714,7 +2716,7 @@ msgstr ""
 "kuitenkin hieman autettava."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2729,7 +2731,7 @@ msgstr ""
 "järjestelmälle laitteistosta."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2745,7 +2747,7 @@ msgstr ""
 "kohdassa <xref linkend=\"boot-troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2786,7 +2788,7 @@ msgstr ""
 "<userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2831,7 +2833,7 @@ msgstr ""
 "<userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2845,13 +2847,13 @@ msgstr ""
 "arvoksi <filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "&debian;in asentimen parametrit"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2866,7 +2868,7 @@ msgstr ""
 "hyödyllisiä."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2882,19 +2884,19 @@ msgstr ""
 "tavallisesti lyhyttä muotoa. "
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "Tämä parametri määrää, kuinka alhaisen prioriteetin viestit näytetään."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2908,7 +2910,7 @@ msgstr ""
 "tulee pulmia, asennin säätää prioriteettia tarpeen mukaan."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2927,13 +2929,13 @@ msgstr ""
 "kriittiset viestit ja yrittää tehdä oikeat valinnat kyselemättä turhia."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, fuzzy, no-c-format
 #| msgid ""
 #| "This boot parameter controls the type of user interface used for the "
@@ -2982,13 +2984,13 @@ msgstr ""
 "<userinput>gtk</userinput>-käyttöliittymää."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -3002,49 +3004,49 @@ msgstr ""
 "tärkeissä vaiheissa. (Käynnistystä jatketaan poistumalla komentotulkista.)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Tämä on oletusarvo"
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Tavallista yksityiskohtaisempi."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Paljon vianjäljitystietoa."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -3054,13 +3056,13 @@ msgstr ""
 "Jatka käynnistystä poistumalla komentotulkista."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3071,7 +3073,7 @@ msgstr ""
 "ladataan. Esimerkiksi <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3082,19 +3084,19 @@ msgstr ""
 "laitteeseen."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3103,13 +3105,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "vähämuisti"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3121,13 +3123,13 @@ msgstr ""
 "arvot ovat 1 ja 2. Katso myös <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3137,13 +3139,13 @@ msgstr ""
 "Hyödyllinen automaattisissa asennuksissa kun keskusmuistia on niukasti."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3161,13 +3163,13 @@ msgstr ""
 "jumittuminen muutaman minuutin sisällä asennuksen alusta."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Pulmista on ilmoitettu hppa:lla."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3186,13 +3188,13 @@ msgstr ""
 "<userinput>fb=true</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3208,13 +3210,13 @@ msgstr ""
 "<userinput>theme=<replaceable>dark</replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3227,7 +3229,7 @@ msgstr ""
 "Verkkoasetukset pääsee tekemään itse vain jos DHCP epäonnistuu."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3241,13 +3243,13 @@ msgstr ""
 "estää verkkoasetusten noutamisen DHCP:llä ja tiedot voi kirjoittaa itse."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3258,13 +3260,13 @@ msgstr ""
 "läppäreillä."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3278,13 +3280,13 @@ msgstr ""
 "<ulink url=\"&url-d-i-wiki;\">Debian-asennin wikistä</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3294,13 +3296,13 @@ msgstr ""
 "asennuksen automatisoimiseksi. Katso <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3310,13 +3312,13 @@ msgstr ""
 "automatisoimiseksi. Katso <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3333,13 +3335,13 @@ msgstr ""
 "\"preseed-seenflag\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3352,13 +3354,13 @@ msgstr ""
 "hyödyntämisestä asennuksen automatisoinnissa."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3371,13 +3373,13 @@ msgstr ""
 "<userinput>true</userinput> estää tämän."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3396,7 +3398,7 @@ msgstr ""
 "asemaan automaattisesti."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3409,13 +3411,13 @@ msgstr ""
 "jälkeen."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3429,7 +3431,7 @@ msgstr ""
 "Katso myös <xref linkend=\"di-install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3445,13 +3447,13 @@ msgstr ""
 "näin ollen vain hyvin kokeneiden käyttäjien käyttää. "
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3465,13 +3467,13 @@ msgstr ""
 "emphasis>."
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3483,13 +3485,13 @@ msgstr ""
 "muistilevyä voitu ladata kokonaan. Arvon yksikkö on kt."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3499,13 +3501,13 @@ msgstr ""
 "eikä tavallinen asennus. Katso <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Valmiita vastauksia käynnistysparametreilla"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3520,25 +3522,25 @@ msgstr ""
 "tapauksista on seuraavassa luettelossa."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3548,7 +3550,7 @@ msgstr ""
 "asennetussa järjestelmässä on kaksi tapaa."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3567,7 +3569,7 @@ msgstr ""
 "maa-asetuston yhdistelmiä ei voi tällä tavalla saada."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3583,13 +3585,13 @@ msgstr ""
 "country=DE locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3606,7 +3608,7 @@ msgstr ""
 "\"pppoe\"/>)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3616,13 +3618,13 @@ msgstr ""
 "ja pakotetaan kiinteät verkkoasetukset."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3640,13 +3642,13 @@ msgstr ""
 "konenimi on kirjoitettava itse."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3658,13 +3660,13 @@ msgstr ""
 "literal>. Katso lisätietoja kohdasta <xref linkend=\"pkgsel\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Parametrien välittäminen ytimen moduuleille"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3688,7 +3690,7 @@ msgstr ""
 "asennetun järjestelmän asetustiedostoihin."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3702,7 +3704,7 @@ msgstr ""
 "kuitenkin olla välttämätöntä asettaa parametrien arvo itse."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3723,19 +3725,19 @@ msgstr ""
 "seuraavasti:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Ytimen moduulien lisääminen kieltolistalle"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3752,7 +3754,7 @@ msgstr ""
 "oikein jos ajurit aiheuttavat ristiriidan tai jos väärä ajuri ladataan ensin."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3768,7 +3770,7 @@ msgstr ""
 "asennetussa järjestelmässä."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3782,19 +3784,19 @@ msgstr ""
 "luettelosta."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Asennusprosessin vianetsintä"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "CD-levyjen luotettavuus"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3807,7 +3809,7 @@ msgstr ""
 "levyltä, se ei tunnista levyä tai asennuksen aikana tulee lukuvirheitä."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3818,13 +3820,13 @@ msgstr ""
 "yleisiä tapauksia ja yleisiä toimintaohjeita. Lopusta saat huolehtia itse."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Ensiksi kannattaa kokeilla kahta hyvin yksinkertaista juttua."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3834,7 +3836,7 @@ msgstr ""
 "ettei se ole likainen."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3853,7 +3855,7 @@ msgstr ""
 "tunnetusti tällä tavalla."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3865,7 +3867,7 @@ msgstr ""
 "yksinkertaisuuden vuoksi termiä CD."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3875,13 +3877,13 @@ msgstr ""
 "asennustapoja."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Yleisiä pulmia"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3891,7 +3893,7 @@ msgstr ""
 "nopeuksilla kirjoitettujen levyjen lukemista."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3904,19 +3906,19 @@ msgstr ""
 "quote> (DMA) on käytössä."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Miten pulmia tutkitaan ja ehkä selvitetään"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr "Jos CD-levy ei käynnisty, kokeile alla lueteltuja ehdotuksia."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -3930,7 +3932,7 @@ msgstr ""
 "luultavasti eivät tue) ja että CD-asema tukee käytettyä taltiota."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3955,7 +3957,7 @@ msgstr ""
 "käyttää otoksen kokoa lukeakseen oikean määrän tavuja levyltä."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3977,7 +3979,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3998,7 +4000,7 @@ msgstr ""
 "komentotulkki."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -4011,7 +4013,7 @@ msgstr ""
 "tuloste."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -4041,7 +4043,7 @@ msgstr ""
 "lataamista itse komennolla <command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -4053,7 +4055,7 @@ msgstr ""
 "filename>. Pitäisi olla myös <filename>/dev/cdrom</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4069,7 +4071,7 @@ msgstr ""
 "virheilmoituksia."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4095,7 +4097,7 @@ msgstr ""
 "laitteen hakemistossa."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4109,13 +4111,13 @@ msgstr ""
 "luettua luotettavasti."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Levykkeen luotettavuus"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4125,7 +4127,7 @@ msgstr ""
 "levykkeiden luotettavuus."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4143,7 +4145,7 @@ msgstr ""
 "koskevien virheilmoitusten tulvana."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4160,7 +4162,7 @@ msgstr ""
 "virheittä. Joskus kannattaa levyke kirjoittaa toisella koneella."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4171,7 +4173,7 @@ msgstr ""
 "<emphasis>kolme</emphasis> kertaa ennen kuin yksi levyke vihdoin toimi."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4183,7 +4185,7 @@ msgstr ""
 "tarkistamalla niiden md5sum-tarkistussummat."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4195,13 +4197,13 @@ msgstr ""
 "viallisista laitteista tai laiteohjelmiston levykeajureista."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Käynnistysasetukset"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4215,7 +4217,7 @@ msgstr ""
 "kohdassa <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4224,7 +4226,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4236,37 +4238,37 @@ msgid ""
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Yleisiä suoritinperheen &arch-title; asennuspulmia"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4276,7 +4278,7 @@ msgstr ""
 "asentimelle sopivia käynnistysparametreja."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4296,13 +4298,13 @@ msgstr ""
 "kohdasta <xref linkend=\"boot-parms\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Järjestelmä jumittuu PCMCIA:n asetuksia tehtäessä"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4330,7 +4332,7 @@ msgstr ""
 "poistaa pulmia aiheuttavien osoitteiden arvoalue pois käytöstä."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4353,19 +4355,19 @@ msgstr ""
 "kirjoitetaan asentimelle."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "Muutamat yleiset asennuspulmat kannattaa mainita."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Videosignaali väärään paikkaan"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4393,7 +4395,7 @@ msgstr ""
 "<userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4407,13 +4409,13 @@ msgstr ""
 "tiedostossa <filename>/etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Käynnistys tai asennus CD-levyltä ei toimi"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4425,7 +4427,7 @@ msgstr ""
 "aikana. Useimmat viat on raportoitu SunBlade-järjestelmistä."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4433,13 +4435,13 @@ msgstr ""
 "verkosta."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Ytimen käynnistysviestien tulkinta"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4476,13 +4478,13 @@ msgstr ""
 "\"linux-any\">(katso <xref linkend=\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Asennuspulmista ilmoittaminen"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4501,7 +4503,7 @@ msgstr ""
 "vikailmoitukset, halunnet liittää nämä tiedot vikailmoitukseen."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4513,13 +4515,13 @@ msgstr ""
 "</filename> kun tietokone on käynnistynyt asennettuun järjestelmään."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Asennusraporttien lähettäminen"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4532,7 +4534,7 @@ msgstr ""
 "mahdollisimman paljon tietoa mahdollisimman monista laitteistokokoonpanoista."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4545,7 +4547,7 @@ msgstr ""
 "julkistamista et pane pahaksesi."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4565,7 +4567,7 @@ msgstr ""
 "<command>reportbug installation-reports</command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/fi/install-methods.po b/po/fi/install-methods.po
index a0a640681..7d760186a 100644
--- a/po/fi/install-methods.po
+++ b/po/fi/install-methods.po
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Debian Installation Guide install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2010-05-04 11:14+0300\n"
 "Last-Translator: Tapio Lehtonen <tale@debian.org>\n"
 "Language-Team: Finnish <debian-l10n-finnish@lists.debian.org>\n"
@@ -75,15 +75,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -125,7 +124,7 @@ msgstr ""
 "tiedostot samoista hakemistoista ja alihakemistoista rompulta."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -135,7 +134,7 @@ msgstr ""
 "tiedostot rompulta."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -154,13 +153,13 @@ msgstr ""
 "voidaan käynnistää niiltä."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Tiedostojen noutaminen &debian;in asennuspalvelimilta"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -171,7 +170,7 @@ msgstr ""
 "ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -182,13 +181,13 @@ msgstr ""
 "automaattimuodossa."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Mistä asennusotokset löytyvät?"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -204,13 +203,13 @@ msgstr ""
 "ulink> on kaikki otokset ja niiden käyttötarkoitus."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Thecus N2100:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -223,13 +222,13 @@ msgstr ""
 "otos saadaan tiedostosta &n2100-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "GLAN Tank:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -241,13 +240,13 @@ msgstr ""
 "&glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Kurobox Pro:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -259,13 +258,13 @@ msgstr ""
 "&kuroboxpro-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "HP mv2120:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -281,13 +280,13 @@ msgstr ""
 "tiedostosta &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "QNAP Turbo Station:in asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -308,14 +307,14 @@ msgstr ""
 "TS-219P osoitteesta &qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, fuzzy, no-c-format
 #| msgid "SheevaPlug and OpenRD Installation Files"
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "SheevaPlug:in ja OpenRD:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the Marvell SheevaPlug and OpenRD devices "
@@ -331,14 +330,14 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "NSLU2 Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "NSLU2:n asennustiedostot"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the Marvell SheevaPlug and OpenRD devices "
@@ -355,13 +354,13 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "IPL-nauhan luominen"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -383,13 +382,13 @@ msgstr ""
 "<filename>tape</filename>, katso kohdasta <xref linkend=\"where-files\"/>."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Levykkeiden luominen levyotoksista"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -400,7 +399,7 @@ msgstr ""
 "tavoin."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -410,7 +409,7 @@ msgstr ""
 "levykeasemilta."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -430,7 +429,7 @@ msgstr ""
 "kirjoitettava levykkeelle sektori kerrallaan."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -441,7 +440,7 @@ msgstr ""
 "kerrotaan miten levyotoksista tehdään levykkeitä eri laitealustoilla."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -456,7 +455,7 @@ msgstr ""
 "saattavat levykeotokset olla rompulla.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -468,13 +467,13 @@ msgstr ""
 "kirjoita vahingossa."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Levyotosten kirjoittaminen Linuxissa tai Unixissa"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -510,7 +509,7 @@ msgstr ""
 "käytetään komentoa <command>eject</command>, katso man-sivua)</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -545,7 +544,7 @@ msgstr ""
 "parasta kysyä järjestelmän ylläpitäjältä.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -557,13 +556,13 @@ msgstr ""
 "asennettava."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Levyotosten kirjoittaminen DOS:ssa, Windowsissa tai OS/2:ssa"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -573,7 +572,7 @@ msgstr ""
 "levykkeille seuraavilla ohjelmilla."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -589,7 +588,7 @@ msgstr ""
 "tiedostoselaimessa."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -601,7 +600,7 @@ msgstr ""
 "purettava samaan hakemistoon."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -611,13 +610,13 @@ msgstr ""
 "<filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Levykeotosten kirjoittaminen MacOS:ssä"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -639,7 +638,7 @@ msgstr ""
 "ja levykeotostiedoston kirjoittamiseen."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -653,14 +652,14 @@ msgstr ""
 "levykeotoksesta jollain seuraavista tavoista näillä apuohjelmilla."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 "Levykeotosten kirjoittaminen apuohjelmalla <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -674,7 +673,7 @@ msgstr ""
 "otostiedostot noudettiin &debian;in asennuspalvelimelta."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -684,7 +683,7 @@ msgstr ""
 "ja avaa sillä tiedosto <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -696,7 +695,7 @@ msgstr ""
 "kentät ovat aakkoslajit erottavia."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -711,7 +710,7 @@ msgstr ""
 "poistaa käynnistyslohkoja jos otos vahingossa liitetään."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -723,7 +722,7 @@ msgstr ""
 "etsi osoitteesta <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -739,13 +738,13 @@ msgstr ""
 "levykkeen pyyhkimiselle. Kun on valmista pitäisi sen työntää levyke ulos."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Levykeotosten kirjoittaminen komennolla <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -758,7 +757,7 @@ msgstr ""
 "<quote>Overwrite Sectors...</quote> valikosta <userinput>Special</userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -767,7 +766,7 @@ msgstr ""
 "sektorista  0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -776,7 +775,7 @@ msgstr ""
 "tiedostonavausvalintaikkunassa."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -790,7 +789,7 @@ msgstr ""
 "levykkeellä."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -802,13 +801,13 @@ msgstr ""
 "jos epähuomiossa liittää sen MacOS:ssä."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Tiedostojen valmistelu käynnistettäessä USB-muistilta"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -832,7 +831,7 @@ msgstr ""
 "on sen kirjoitussuoja ehkä otettava pois päältä."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -845,13 +844,13 @@ msgstr ""
 "laitenimeä, saatat tuhota kaiken tiedon esimerkiksi koneen kiintolevyltä."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -861,7 +860,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -871,7 +870,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -883,7 +882,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -894,7 +893,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -904,7 +903,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -913,7 +912,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -922,14 +921,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, fuzzy, no-c-format
 #| msgid "Booting the USB stick"
 msgid "Manually copying files to the USB stick"
 msgstr "Käynnistäminen USB-muistilta"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note that the USB stick should be at least 256 MB in size (smaller setups "
@@ -944,7 +943,7 @@ msgstr ""
 "koko riittää jos noudatat ohjetta <xref linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, fuzzy, no-c-format
 #| msgid ""
 #| "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> "
@@ -966,7 +965,7 @@ msgstr ""
 "asetustiedosto.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note that, although convenient, this method does have one major "
@@ -991,19 +990,19 @@ msgstr ""
 "romppuotosta, ainoastaan pienemmän businesscard- tai netinst-otoksen."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr "Jos käytät tätä otosta, riittää purkaa se sellaisenaan USB-muistille:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1015,13 +1014,13 @@ msgstr ""
 "otos suoraan siihen:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1052,14 +1051,14 @@ msgstr ""
 "userinput>) ja homma on valmis."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, fuzzy, no-c-format
 #| msgid "Copying the files &mdash; the flexible way"
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Tiedostojen kopiointi &mdash; joustava tapa"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1074,13 +1073,13 @@ msgstr ""
 "mahdollisuus kopioida kokonainen CD-levyn ISO-otos sille."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Osioiden teko USB-muistille"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1090,7 +1089,7 @@ msgstr ""
 "muistia."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1132,7 +1131,7 @@ msgstr ""
 "<classname>dosfstools</classname>."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1151,7 +1150,7 @@ msgstr ""
 "käynnistyslataimen asetustiedoston muuttamiseen."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1175,13 +1174,13 @@ msgstr ""
 "<filename>ldlinux.sys</filename>, jossa on käynnistyslataimen koodi."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Asentimen levyotoksen lisääminen"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1209,7 +1208,7 @@ msgstr ""
 "tiedostonimiä."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1246,7 +1245,7 @@ msgstr ""
 "lisättävä <userinput>vga=788</userinput>."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1254,7 +1253,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy a "
@@ -1282,7 +1281,7 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1312,7 +1311,7 @@ msgstr ""
 "<classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1329,7 +1328,7 @@ msgstr ""
 "muuttamiseen."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1364,7 +1363,7 @@ msgstr ""
 "valmistella tavallisilla Unixin työkaluilla."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1375,31 +1374,31 @@ msgstr ""
 "muistille:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (ytimen ohjelmatiedosto)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (käynnistysmuistilevyn levyotos)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yabootin asetustiedosto)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (valinnainen käynnistysviesti)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1434,13 +1433,13 @@ msgstr ""
 "userinput> arvoa voidaan joutua kasvattamaan asennettavan otoksen mukaan."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Tiedostojen valmistelu käynnistettäessä kiintolevyltä"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1452,7 +1451,7 @@ msgstr ""
 "käyttöjärjestelmästä tai käynnistämällä käynnistyslatain suoraan BIOS:sta."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1466,7 +1465,7 @@ msgstr ""
 "lukuisten ja epäluotettavien levykkeiden kanssa tappeleminen."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1489,7 +1488,7 @@ msgstr ""
 "erityisesti noudettavien asennustiedostojen kopioimiseen."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1501,7 +1500,7 @@ msgstr ""
 "käynnistämiseen."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1511,7 +1510,7 @@ msgstr ""
 "<command>LILO</command> tai <command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1522,7 +1521,7 @@ msgstr ""
 "<command>LILO</command> tai <command>GRUB</command>. "
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1534,7 +1533,7 @@ msgstr ""
 "juuritiedostojärjestelmänä."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Copy the following files from the Debian archives to a convenient "
@@ -1550,19 +1549,19 @@ msgstr ""
 "filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (ytimen ohjelmatiedosto)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (muistilevyn levyotos)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1572,7 +1571,7 @@ msgstr ""
 "\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Hard disk installer booting using <command>LILO</command> or "
@@ -1583,7 +1582,7 @@ msgstr ""
 "<command>LILO</command> tai <command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, fuzzy, no-c-format
 #| msgid ""
 #| "This section explains how to add to or even replace an existing linux "
@@ -1598,7 +1597,7 @@ msgstr ""
 "<command>LILO</command> tai <command>GRUB</command>. "
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Copy the following files from the Debian archives to a convenient "
@@ -1613,7 +1612,7 @@ msgstr ""
 "filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, fuzzy, no-c-format
 #| msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgid ""
@@ -1621,20 +1620,20 @@ msgid ""
 msgstr "<filename>initrd.gz</filename> (käynnistysmuistilevyn levyotos)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, fuzzy, no-c-format
 #| msgid "<filename>boot.msg</filename> (optional boot message)"
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>boot.msg</filename> (valinnainen käynnistysviesti)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Kiintolevylle tallennetun asentimen käynnistäminen OldWorld Maceilla"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1659,7 +1658,7 @@ msgstr ""
 "pakollinen tuolla mallilla."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1687,13 +1686,13 @@ msgstr ""
 "käytössä olevaan System-kansioon."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Kiintolevylle tallennetun asentimen käynnistäminen NewWorld Maceilla"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1714,7 +1713,7 @@ msgstr ""
 "PowerMaceilla."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1728,31 +1727,31 @@ msgstr ""
 "kiintolevyn kuvakkeeseen."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1767,20 +1766,20 @@ msgstr ""
 "tarvitaan Open Firmwaren komennossa kun asenninta käynnistetään."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 "Käynnistä asennin jatkamalla kohtaan <xref linkend=\"boot-newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Tiedostojen valmistelu verkosta käynnistämiseen TFTP:llä"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1796,7 +1795,7 @@ msgstr ""
 "tehtävä siten, että asennettavan koneen käynnistämistä tuetaan."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1808,7 +1807,7 @@ msgstr ""
 "phrase><phrase condition=\"supports-bootp\"> tai BOOTP-palvelin</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1828,7 +1827,7 @@ msgstr ""
 "järjestelmissä verkkoasetukset voidaan tehdä vain DHCP:llä."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1840,7 +1839,7 @@ msgstr ""
 "llä."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1850,7 +1849,7 @@ msgstr ""
 "&debian;issa on saatavilla paketti <classname>rbootd</classname>."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1865,7 +1864,7 @@ msgstr ""
 "Solaris) ja GNU/Linux käytettävät komennot."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1880,13 +1879,13 @@ msgstr ""
 "classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "RARP-palvelimen asetukset"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1906,7 +1905,7 @@ msgstr ""
 "userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1932,13 +1931,13 @@ msgstr ""
 "käyttöjärjestelmässä SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "DHCP-palvelimen asetukset"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1952,7 +1951,7 @@ msgstr ""
 "filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1996,7 +1995,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -2014,7 +2013,7 @@ msgstr ""
 "nimi."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -2024,13 +2023,13 @@ msgstr ""
 "uudestaan komennolla <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "PXE-käynnistyksen käyttöönotto DHCP-asetuksissa"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2101,13 +2100,13 @@ msgstr ""
 "ohjelmatiedosto (katso <xref linkend=\"tftp-images\"/> tuonnempana)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "BOOTP-palvelimen käyttöönotto"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2122,7 +2121,7 @@ msgstr ""
 "<classname>bootp</classname> ja <classname>dhcp3-server</classname>."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, fuzzy, no-c-format
 #| msgid ""
 #| "To use CMU <command>bootpd</command>, you must first uncomment (or add) "
@@ -2218,7 +2217,7 @@ msgstr ""
 "osoite. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2242,13 +2241,13 @@ msgstr ""
 "<userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "TFTP-palvelimen käyttöönotto"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2258,7 +2257,7 @@ msgstr ""
 "komennon <command>tftpd</command> olevan käytettävissä."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2274,7 +2273,7 @@ msgstr ""
 "asetukset uudestaan. "
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2293,7 +2292,7 @@ msgstr ""
 "asetusesimerkkejä vastaavasti."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2310,7 +2309,7 @@ msgstr ""
 "virheiden syytä etsittäessä."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2341,13 +2340,13 @@ msgstr ""
 "palvelimen valitsee käyttämänsä lähdeporttit."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Siirretään TFTP-otokset paikalleen"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2364,7 +2363,7 @@ msgstr ""
 "nimeämiskäytännölle ole kunnollisia standardeja."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2379,13 +2378,13 @@ msgstr ""
 "<filename>netboot</filename> on noudettava seuraavat tiedostot:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2402,7 +2401,7 @@ msgstr ""
 "filename>."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2419,13 +2418,13 @@ msgstr ""
 "ia64/elilo.efi</filename>."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "SPARC:n käynnistys TFTP:llä"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2456,7 +2455,7 @@ msgstr ""
 "nimen."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2469,7 +2468,7 @@ msgstr ""
 "yritä tarkistaa tftp-palvelimen lokeista mitä otoksen nimeä yritetään noutaa."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2483,13 +2482,13 @@ msgstr ""
 "hakemistossa josta TFTP-palvelin sitä etsii."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI:n käynnistys TFTP:llä"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2503,13 +2502,13 @@ msgstr ""
 "tiedostossa <filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Automaattinen asennus"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, fuzzy, no-c-format
 #| msgid ""
 #| "For installing on multiple computers it's possible to do fully automatic "
@@ -2531,13 +2530,13 @@ msgstr ""
 "classname>, ja &debian;in asennin itse."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Automaattinen asennus &debian;in asentimella"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2551,7 +2550,7 @@ msgstr ""
 "asennusprosessin aikana kysyttyihin kysymyksiin."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/ja/boot-installer.po b/po/ja/boot-installer.po
index cb78a1500..73f1b7d92 100644
--- a/po/ja/boot-installer.po
+++ b/po/ja/boot-installer.po
@@ -4,7 +4,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-20 23:24+0900\n"
 "Last-Translator: KURASAWA Nozomu <nabetaro@debian.or.jp>\n"
 "Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
@@ -62,8 +62,8 @@ msgid "Booting from TFTP"
 msgstr "TFTP からの起動"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -73,8 +73,8 @@ msgstr ""
 "(DHCP, RARP, BOOTP) が必要です。"
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -83,8 +83,8 @@ msgstr ""
 "715 のような古いシステムは、BOOTP サーバではなく RBOOT サーバが必要です。"
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -100,8 +100,8 @@ msgid "Booting from CD-ROM"
 msgstr "CD-ROM からの起動"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -117,8 +117,8 @@ msgstr ""
 "</phrase>CD-ROM をドライブに入れて再起動し、次の章に進んでください。"
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -133,8 +133,8 @@ msgstr ""
 "ついて読んでください。"
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -150,8 +150,8 @@ msgstr ""
 "ください。"
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -390,8 +390,8 @@ msgid "The installer will now start as usual."
 msgstr "今度は通常のように、インストーラが起動します。"
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "CD-ROM からの起動"
@@ -410,17 +410,23 @@ msgstr "Windows からインストーラを起動するには、"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "<xref linkend=\"official-cdrom\"/> や <xref linkend=\"boot-usb-files\"/> で記"
 "述しているような CD-ROM/DVD-ROM あるいは USB メモリスティックのインストールメ"
 "ディアを得るか、"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -430,7 +436,7 @@ msgstr ""
 "れだけで起動する Windows の実行ファイルをダウンロードします。"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -445,7 +451,7 @@ msgstr ""
 "きます。"
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -456,13 +462,13 @@ msgstr ""
 "gnu; インストーラを起動する準備が整います。"
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "DOS からの起動"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -472,7 +478,7 @@ msgstr ""
 "スクから起動します。"
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -490,7 +496,7 @@ msgstr ""
 "ブを変更します。"
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -512,7 +518,7 @@ msgstr ""
 "ください。カーネルが読み込まれインストーラシステムが起動します。"
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -520,7 +526,7 @@ msgstr ""
 "<command>LILO</command> や <command>GRUB</command> を用いた Linux からの起動"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -531,7 +537,7 @@ msgstr ""
 "なりません。"
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -549,7 +555,7 @@ msgstr ""
 "できます。(注意して行ってください)"
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -567,7 +573,7 @@ msgstr ""
 "ンストールできます。"
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -585,7 +591,7 @@ msgstr ""
 "itemizedlist> <filename>/etc/lilo.conf</filename> の例を示します。"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -597,7 +603,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -613,7 +619,7 @@ msgstr ""
 "ださい。"
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -629,7 +635,7 @@ msgstr ""
 "ティションにあると仮定します)。"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -644,7 +650,7 @@ msgstr ""
 
 # trans: for instance for example?
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -656,7 +662,7 @@ msgstr ""
 "インストーラのエントリは以下の例の様になります。"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -676,7 +682,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -686,13 +692,13 @@ msgstr ""
 "ん。"
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "USB メモリからの起動"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
 "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -710,13 +716,13 @@ msgstr ""
 "するか、単に &enterkey; を押してください。"
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "フロッピーからの起動"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -726,7 +732,7 @@ msgstr ""
 "既にダウンロードし、それらのイメージからフロッピーは作成済みかと思います。"
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -737,7 +743,7 @@ msgstr ""
 "れてください。"
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -755,7 +761,7 @@ msgstr ""
 "dev/hdc</userinput> と入力します。"
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -771,7 +777,7 @@ msgstr ""
 "トールを行うときは、ハードリブートを用いてください。"
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -781,7 +787,7 @@ msgstr ""
 "に <prompt>boot:</prompt> というプロンプトが表示されます。"
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -798,7 +804,7 @@ msgstr ""
 "\"kernel-msgs\"/> で説明します。"
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -812,26 +818,26 @@ msgstr ""
 "起動します。"
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "TFTP での起動"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "i386 での TFTP ブートはいろいろな方法があります。"
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "PXE をサポートする NIC・マザーボード"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -845,13 +851,13 @@ msgstr ""
 "BIOS を設定することができます。"
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "ネットワーク BootROM がある NIC"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -861,7 +867,7 @@ msgstr ""
 "せん。"
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -871,13 +877,13 @@ msgstr ""
 "ださい。この文書に参加をお願いします。"
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -887,13 +893,13 @@ msgstr ""
 "TFTP ブートを行うブートディスケットとブート ROM を提供しています。"
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "ブート画面"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -929,7 +935,7 @@ msgstr ""
 "ため、オプションの数は、ほぼ 2 倍になります。"
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -944,7 +950,7 @@ msgstr ""
 "択済み)、&enterkey; を押してインストーラを起動してください。"
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -956,7 +962,7 @@ msgstr ""
 "セスできます。"
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -974,7 +980,7 @@ msgstr ""
 "ニューに戻り、行った変更を取り消します。"
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1024,7 +1030,7 @@ msgstr ""
 "<userinput>install fb=false</userinput>)。"
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1042,7 +1048,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1062,7 +1068,7 @@ msgstr ""
 "Remote Assistant</quote> (IRA) のテキストコンソールを含みます。"
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1082,13 +1088,13 @@ msgstr ""
 "fb=false</userinput> を追加したくなるでしょう。"
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "CD の内容"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1112,7 +1118,7 @@ msgstr ""
 "をインストールできます。"
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1138,7 +1144,7 @@ msgstr ""
 "を意味します。"
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1154,7 +1160,7 @@ msgstr ""
 "のファイルは下に記述したように EFI シェルから読むことができます。"
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1177,7 +1183,7 @@ msgstr ""
 "確認します。"
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1200,13 +1206,13 @@ msgstr ""
 "ださい。"
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "重要"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1225,13 +1231,13 @@ msgstr ""
 "ジャに戻ることができます。"
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "オプション 1: 起動オプションメンテナンスメニューからの起動"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1242,7 +1248,7 @@ msgstr ""
 "と、ファームウェアが EFI ブートマネージャの画面やメニューを表示する。"
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1252,7 +1258,7 @@ msgstr ""
 "<command>ENTER</command> を押す。ここで新しいメニューを表示する。"
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1270,7 +1276,7 @@ msgstr ""
 "に気がつくだろう。"
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1287,7 +1293,7 @@ msgstr ""
 "移ることを要求し、CD の起動可能部分のディレクトリ一覧を表示するだろう。"
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1302,7 +1308,7 @@ msgstr ""
 "<command>ENTER</command> を押すと、ブートロードシーケンスを開始する。"
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1313,13 +1319,13 @@ msgstr ""
 "ブートローダを起動します。起動カーネルやオプションの選択に移行してください。"
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "オプション 2: EFI シェルからの起動"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1333,7 +1339,7 @@ msgstr ""
 "ください。"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1344,7 +1350,7 @@ msgstr ""
 "と、ファームウェアが EFI ブートマネージャの画面やメニューを表示する。"
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1366,7 +1372,7 @@ msgstr ""
 "化するのに数秒よけいにかかる可能性がある。"
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1379,7 +1385,7 @@ msgstr ""
 "filename> という、起動可能パーティションを持つ他のデバイスとして表される。"
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1393,7 +1399,7 @@ msgstr ""
 "される。"
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1403,7 +1409,7 @@ msgstr ""
 "ブートローダが起動される。"
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1418,13 +1424,13 @@ msgstr ""
 "ます。起動カーネルやオプションの選択に進んでください。"
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "シリアルコンソールを用いたインストール"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1445,7 +1451,7 @@ msgstr ""
 "定されています。"
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1458,7 +1464,7 @@ msgstr ""
 "<command>baud</command> コマンドを使って取得できます。"
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1474,7 +1480,7 @@ msgstr ""
 "力してください。"
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1492,7 +1498,7 @@ msgstr ""
 "ニューの説明をご覧ください。"
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1505,13 +1511,13 @@ msgstr ""
 "める前に、再起動する必要があるでしょう。"
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "起動カーネルやオプションの選択"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1531,7 +1537,7 @@ msgstr ""
 "明します。"
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1553,7 +1559,7 @@ msgstr ""
 "可能性があります。以下の手順で選択しインストールを開始してください。"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1562,7 +1568,7 @@ msgstr ""
 "カーネルのバージョンと目的に対して最も適切なモードを、矢印キーで選択する。"
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1574,7 +1580,7 @@ msgstr ""
 "定を行う。"
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1585,7 +1591,7 @@ msgstr ""
 "は &debian; インストーラの第 1 画面に通常の初期化メッセージを表示する。"
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1595,7 +1601,7 @@ msgstr ""
 "ンストールを続けるのには、次章に進んでください。"
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1614,7 +1620,7 @@ msgstr ""
 "トールと同じ手順で、システムのインストールを行うことになります。"
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1628,13 +1634,13 @@ msgstr ""
 "ロードができるよう EFI ブートマネージャに定義しなければなりません。"
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "サーバの設定"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1658,7 +1664,7 @@ msgstr ""
 "することが目的であることに注意してください。"
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1674,7 +1680,7 @@ msgstr ""
 "installer</filename> ディレクトリを作成します。"
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1692,7 +1698,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1713,13 +1719,13 @@ msgstr ""
 "classname> パッケージで提供されるドキュメントを参照してください。"
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "クライアントの設定"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1749,7 +1755,7 @@ msgstr ""
 "いるか、確認した方がいいでしょう。"
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1764,13 +1770,13 @@ msgstr ""
 "らカーネルの読み込みが完了すれば、&debian; インストーラを起動します。"
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI の TFTP での起動"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1792,13 +1798,13 @@ msgstr ""
 "</screen></informalexample> とします。"
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "ブートパラメータ"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1808,7 +1814,7 @@ msgstr ""
 "トパラメータを追加します。"
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1826,19 +1832,19 @@ msgstr ""
 "command> を通して渡せます:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Cobalt の TFTP での起動"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1856,7 +1862,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1871,7 +1877,7 @@ msgstr ""
 "トでマシンに接続すると、インストールが始まります。"
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1882,7 +1888,7 @@ msgstr ""
 "リアルポートに接続 (115200 bps) し、インストールを実行できます。"
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1894,13 +1900,13 @@ msgstr ""
 "<replaceable>args</replaceable> に追加する必要があります。"
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390 の制限"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1910,7 +1916,7 @@ msgstr ""
 "ssh セッションが使えることが必要となります。"
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1923,13 +1929,13 @@ msgstr ""
 "にログインします。すると標準のインストールシステムが起動されます。"
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390 ブートパラメータ"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1941,7 +1947,7 @@ msgstr ""
 "メージの <filename>parmfile.debian</filename> で提供しています。"
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1959,7 +1965,7 @@ msgstr ""
 "フォルト CD-ROM から起動できます。"
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -1977,13 +1983,13 @@ msgstr ""
 "</screen></informalexample>"
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -1999,7 +2005,7 @@ msgstr ""
 "ピードライブを使い、必要とされたファイルのために CD を指定してください。"
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2011,19 +2017,19 @@ msgstr ""
 "が表示されたら以下を入力してください。"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "ハードディスクからの起動"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2033,7 +2039,7 @@ msgstr ""
 "のシステムについては、インストールをサポートする唯一の方法です。"
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2045,13 +2051,13 @@ msgstr ""
 "があります。"
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "MacOS からの OldWorld PowerMac の起動"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2073,13 +2079,13 @@ msgstr ""
 "タンをクリックすると、MacOS がシャットダウンして、インストーラが起動します。"
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "OpenFirmware からの NewWorld Mac の起動"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2125,19 +2131,19 @@ msgstr ""
 "が開始されるはずです。"
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "USB メモリからの起動"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr "現在、NewWorld PowerMac は USB からの起動をサポートしています。"
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2152,7 +2158,7 @@ msgstr ""
 "覧ください。"
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2174,7 +2180,7 @@ msgstr ""
 "えています。"
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2200,7 +2206,7 @@ msgstr ""
 "Firmware に指示しています。"
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2211,7 +2217,7 @@ msgstr ""
 "加の起動引数を入力するか、単に &enterkey; を押してください。"
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2223,7 +2229,7 @@ msgstr ""
 "ンストールレポートを出してください。"
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2231,7 +2237,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2267,7 +2273,7 @@ msgstr ""
 "ションの説明が得られます。"
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2281,7 +2287,7 @@ msgstr ""
 "ん。"
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2293,7 +2299,7 @@ msgstr ""
 "てください。"
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2307,7 +2313,7 @@ msgstr ""
 "ションをチェックします。"
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2319,13 +2325,13 @@ msgstr ""
 "れると、インストーラプログラムが自動的に起動します。"
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC ブートパラメータ"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2341,7 +2347,7 @@ msgstr ""
 "userinput> に変えてください。"
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2361,7 +2367,7 @@ msgstr ""
 "パラメータを渡せます。"
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2373,13 +2379,13 @@ msgstr ""
 "システムならセカンダリのマスター) から起動せよ、という命令の別名です。"
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM メッセージ"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2394,13 +2400,13 @@ msgstr ""
 "\">Sun NVRAM FAQ</ulink> を見てください。"
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "アクセシビリティ"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2428,13 +2434,13 @@ msgstr ""
 "キーボードとして認識することに注意してください。"
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB 点字ディスプレイ"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2455,13 +2461,13 @@ msgstr ""
 "す。"
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "シリアル接続点字ディスプレイ"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2500,13 +2506,13 @@ msgstr ""
 "ブサイト</ulink> にドキュメントがあります。"
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "ソフトウェア音声合成"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2521,13 +2527,13 @@ msgstr ""
 "classname> が有効な場合)。"
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "ハードウェア音声合成"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2539,7 +2545,7 @@ msgstr ""
 "選択する必要があります。"
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2560,13 +2566,13 @@ msgstr ""
 "スのサポートをターゲットシステムに自動でインストールします。"
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "基板デバイス"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2582,7 +2588,7 @@ msgstr ""
 "これにより使用できる言語が減ってしまいます。"
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2592,13 +2598,13 @@ msgstr ""
 "<userinput>h</userinput> &enterkey; をタイプしてください。"
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "高コントラストテーマ"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2610,13 +2616,13 @@ msgstr ""
 "<userinput>theme=dark</userinput> を追加してください。"
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "preseed の利用"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2626,7 +2632,7 @@ msgstr ""
 "これは <xref linkend=\"appendix-preseed\"/> にドキュメントがあります。"
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2640,7 +2646,7 @@ msgstr ""
 "あるのです。"
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2654,7 +2660,7 @@ msgstr ""
 "ステムに伝えるためのパラメータを調べ、あとで再起動します。"
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2670,7 +2676,7 @@ msgstr ""
 "に含まれています。"
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2711,7 +2717,7 @@ msgstr ""
 "<userinput>vt102</userinput> です。</para> </footnote>。"
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2756,7 +2762,7 @@ msgstr ""
 "<userinput>vt102</userinput> です。</para> </footnote>。"
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2770,13 +2776,13 @@ msgstr ""
 "を設定しても結構です。"
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "&debian; Installer パラメータ"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2790,7 +2796,7 @@ msgstr ""
 "ニックしてしまいます。</para> </footnote>をいくつか認識します。"
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2805,20 +2811,20 @@ msgstr ""
 "ルの例は、通常、短縮形も使用しています。"
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 "このパラメータには、表示するメッセージのもっとも低い優先度を設定します。"
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2832,7 +2838,7 @@ msgstr ""
 "な優先度に調整します。"
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2851,13 +2857,13 @@ msgstr ""
 "なメッセージだけを表示し、大騒ぎせずに正しい設定をしようとします。"
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2893,13 +2899,13 @@ msgstr ""
 "エンドを使用します。"
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2912,49 +2918,49 @@ msgstr ""
 "できます。(シェルを終了すると起動プロセスを継続します)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "デフォルトです。"
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "通常よりも詳細です。"
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "デバッグ情報を大量に表示します。"
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2964,13 +2970,13 @@ msgstr ""
 "起動を続けるにはシェルから抜けてください。"
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -2982,7 +2988,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -2992,19 +2998,19 @@ msgstr ""
 "が、このパラメータで 1 つのデバイスを探すように上書きできます。"
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3016,13 +3022,13 @@ msgstr ""
 "ポートのデフォルト値を、標準 syslog ポートの 514 とします。"
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3034,13 +3040,13 @@ msgstr ""
 "す。<xref linkend=\"lowmem\"/> もご覧ください。"
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3050,13 +3056,13 @@ msgstr ""
 "リティが限られている、無人インストールの際に便利です。"
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3074,13 +3080,13 @@ msgstr ""
 "の兆候です。"
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "そのような問題が、hppa について報告されています。"
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3098,13 +3104,13 @@ msgstr ""
 "<userinput>fb=true</userinput> というパラメータを試してください。"
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3120,13 +3126,13 @@ msgstr ""
 "と指定してテーマを設定してください。"
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3139,7 +3145,7 @@ msgstr ""
 "敗する場合のみ、手動ネットワーク設定を行えます。"
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3152,13 +3158,13 @@ msgstr ""
 "<userinput>netcfg/disable_dhcp=true</userinput> パラメータを使用できます。"
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3169,13 +3175,13 @@ msgstr ""
 "ピュータには、そういう行儀悪さがあることが知られています。"
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3189,13 +3195,13 @@ msgstr ""
 "\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink> にあります。"
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3206,13 +3212,13 @@ msgstr ""
 "い。"
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3222,13 +3228,13 @@ msgstr ""
 "<xref linkend=\"automatic-install\"/> を参照してください。"
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3243,13 +3249,13 @@ msgstr ""
 "す。詳細は、<xref linkend=\"preseed-seenflag\"/> をご覧ください。"
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3261,13 +3267,13 @@ msgstr ""
 "auto\"/> をご覧ください。"
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3279,13 +3285,13 @@ msgstr ""
 "れを回避するには <userinput>true</userinput> をセットしてください。"
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3303,7 +3309,7 @@ msgstr ""
 "ムライン、キャディタイプのドライブは、自動的にメディアをリロードできません。"
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3315,13 +3321,13 @@ msgstr ""
 "要があります。"
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3335,7 +3341,7 @@ msgstr ""
 "base\"/> をご覧ください。"
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3350,13 +3356,13 @@ msgstr ""
 "ンは、経験豊富なユーザにしか有用ではないでしょう。"
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3369,13 +3375,13 @@ msgstr ""
 "い。<emphasis role=\"bold\">警告: 危険です。お勧めしません。</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3387,13 +3393,13 @@ msgstr ""
 "い。値は kB で指定してください。"
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3403,13 +3409,13 @@ msgstr ""
 "userinput> にセットしてください。<xref linkend=\"rescue\"/> をご覧ください。"
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "ブートパラメータで質問に答える"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3422,25 +3428,25 @@ msgstr ""
 "bootparms\"/> にあります。特殊な例を以下に示します。"
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3450,7 +3456,7 @@ msgstr ""
 "ふたつあります。"
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3469,7 +3475,7 @@ msgstr ""
 "ないということです。"
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3485,13 +3491,13 @@ msgstr ""
 "UTF-8</userinput>"
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3507,7 +3513,7 @@ msgstr ""
 "\"pppoe\"/> をご覧ください) </phrase>が便利です。"
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3517,13 +3523,13 @@ msgstr ""
 "userinput> と設定します。"
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3540,13 +3546,13 @@ msgstr ""
 "ホスト名を手入力しなければならないことに注意してください。"
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3558,13 +3564,13 @@ msgstr ""
 "ださい。"
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "カーネルモジュールへパラメータを渡す"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3587,7 +3593,7 @@ msgstr ""
 "ステムに伝播します。"
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3601,7 +3607,7 @@ msgstr ""
 "は、未だにパラメータを手で設定しなければなりません。"
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3622,19 +3628,19 @@ msgstr ""
 "スカードで BNC (coax) を使用し、IRQ 10 を設定する場合は、以下のようにします。"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "カーネルモジュールのブラックリスト化"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3652,7 +3658,7 @@ msgstr ""
 "因となります。"
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3668,7 +3674,7 @@ msgstr ""
 "が有効になります。"
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3682,19 +3688,19 @@ msgstr ""
 "げます。"
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "インストールプロセスのトラブルシューティング"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "CD-ROM の信頼性"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3708,7 +3714,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3719,13 +3725,13 @@ msgstr ""
 "法を提供することしかできません。後はあなた次第です。"
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "まずはじめに試すのは、以下の 2 点です。"
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3735,7 +3741,7 @@ msgstr ""
 "さい。"
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3753,7 +3759,7 @@ msgstr ""
 "ROM ドライブの DMA に関連する問題は、この方法で解決することが知られています。"
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3765,7 +3771,7 @@ msgstr ""
 "という用語を用いています。"
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3775,13 +3781,13 @@ msgstr ""
 "さい。"
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "共通の問題"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3791,7 +3797,7 @@ msgstr ""
 "ディスクからの読み込みをサポートしていない物があります。"
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3804,19 +3810,19 @@ msgstr ""
 "が有効だと、正しく動作しない物もあります。"
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "調査および問題解決の方法"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr "CD-ROM が起動に失敗したら、以下のことを試してください。"
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -3831,7 +3837,7 @@ msgstr ""
 "ください。"
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3856,7 +3862,7 @@ msgstr ""
 "み込むのにイメージのサイズを利用します。"
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3878,7 +3884,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3898,7 +3904,7 @@ msgstr ""
 "に切り替えて、シェルを有効にしてください。"
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3910,7 +3916,7 @@ msgstr ""
 "示してください。その後、<command>dmesg</command> の出力でもチェックできます。"
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3940,7 +3946,7 @@ msgstr ""
 "むのを試せます。"
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3952,7 +3958,7 @@ msgstr ""
 "<filename>/dev/cdrom</filename> にもあるかもしれません。"
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -3969,7 +3975,7 @@ msgstr ""
 "チェックしてください。"
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -3995,7 +4001,7 @@ msgstr ""
 "クトリで操作してください。"
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4008,13 +4014,13 @@ msgstr ""
 "ションを一般的なテストとして使用できます。"
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "フロッピーディスクの信頼性"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4024,7 +4030,7 @@ msgstr ""
 "は、フロッピーディスクの信頼性だと思います。"
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4042,7 +4048,7 @@ msgstr ""
 "ディスク I/O エラーに関するメッセージが大量に表示されます。"
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4059,7 +4065,7 @@ msgstr ""
 "ムで書き込んでみると、うまくいくこともあるようです。"
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4071,7 +4077,7 @@ msgstr ""
 "して確認するといいでしょう。"
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4083,7 +4089,7 @@ msgstr ""
 "フロッピーでは、何も問題なくいったそうです。"
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4095,13 +4101,13 @@ msgstr ""
 "ウェアのフロッピードライバのできが悪かったためでしょう。"
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "起動設定"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4114,7 +4120,7 @@ msgstr ""
 "\"/> の説明に従ってブートパラメータを確認してください。"
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4123,7 +4129,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4140,37 +4146,37 @@ msgstr ""
 "(Live CD など) で実行し、その結果をバグ報告してください。"
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "&arch-title; へのインストールに共通の問題"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4180,7 +4186,7 @@ msgstr ""
 "ラメータで解決したり、確実にバイパスして回避したりできます。"
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4200,13 +4206,13 @@ msgstr ""
 "ください。"
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "PCMCIA 設定中のシステムフリーズ"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4234,7 +4240,7 @@ msgstr ""
 "外することができます。"
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4256,19 +4262,19 @@ msgstr ""
 "あればカンマを省略しなければならないことに注意してください。"
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "以下、言及しておくべき、インストール時の一般的な問題があります。"
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "ビデオ出力先の間違い"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4294,7 +4300,7 @@ msgstr ""
 "userinput> をインストーラに与えて起動してください。"
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4308,13 +4314,13 @@ msgstr ""
 "filename> のビデオドライバを修正してください。"
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "起動に失敗ないし CD-ROM からインストール"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4326,20 +4332,20 @@ msgstr ""
 "システムで報告されています。"
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 "そのようなシステムでは、インストーラをネットから起動するのをお勧めします。"
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "カーネルの起動時メッセージの意味"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4377,13 +4383,13 @@ msgstr ""
 "baking\"/> 参照)</phrase>。"
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "インストールで発生した問題の報告"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4402,7 +4408,7 @@ msgstr ""
 "バグ報告を送る際に、バグ報告にこの情報を付けることができます。"
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4414,13 +4420,13 @@ msgstr ""
 "installer/</filename> にあるはずです。"
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "インストールレポートの送信"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4433,7 +4439,7 @@ msgstr ""
 "さんのハードウェア設定情報を手に入れることができます。"
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4445,7 +4451,7 @@ msgstr ""
 "ない e-mail アドレスを使用してください。"
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4464,7 +4470,7 @@ msgstr ""
 "て、<command>reportbug installation-reports</command> を実行してください。"
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/ja/install-methods.po b/po/ja/install-methods.po
index fb6d2e51c..0ece0357d 100644
--- a/po/ja/install-methods.po
+++ b/po/ja/install-methods.po
@@ -4,7 +4,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: \n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-20 23:36+0900\n"
 "Last-Translator: KURASAWA Nozomu <nabetaro@debian.or.jp>\n"
 "Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
@@ -77,15 +77,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -126,7 +125,7 @@ msgstr ""
 "ブディレクトリからファイルを探せます。"
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -136,7 +135,7 @@ msgstr ""
 "きます。"
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -155,13 +154,13 @@ msgstr ""
 "ます。"
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "&debian; ミラーサイトからのファイルのダウンロード"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -172,7 +171,7 @@ msgstr ""
 "さい。"
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -183,13 +182,13 @@ msgstr ""
 "さい。テキスト (text) モードや自動選択モードではだめです。"
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "どこでインストールイメージを探すか"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -205,13 +204,13 @@ msgstr ""
 "す。"
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Thecus N2100 のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -225,13 +224,13 @@ msgstr ""
 "&n2100-firmware-img; から得られます。"
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "GLAN Tank のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -243,13 +242,13 @@ msgstr ""
 "&glantank-firmware-img; から取得できます。"
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "玄箱 Pro のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -261,13 +260,13 @@ msgstr ""
 "&kuroboxpro-firmware-img; から取得できます。"
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "HP mv2120 のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -283,13 +282,13 @@ msgstr ""
 "ます。"
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "QNAP Turbo Station のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -304,13 +303,13 @@ msgstr ""
 "img; から取得できます。"
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "プラグコンピュータと OpenRD のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -326,14 +325,14 @@ msgstr ""
 "ファイルを &kirkwood-marvell-firmware-img; から取得できます。"
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "NSLU2 Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "NSLU2 のインストールファイル"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -350,13 +349,13 @@ msgstr ""
 "ファイルを &kirkwood-marvell-firmware-img; から取得できます。"
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "IPL テープの作成"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -378,13 +377,13 @@ msgstr ""
 "<xref linkend=\"where-files\"/> をご覧ください。"
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "ディスクイメージからのフロッピーの作成"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -394,7 +393,7 @@ msgstr ""
 "ンストーラを起動するのに起動可能なフロッピーディスクを用います。"
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -404,7 +403,7 @@ msgstr ""
 "ないそうです。"
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -424,7 +423,7 @@ msgstr ""
 "の <emphasis>セクタコピー</emphasis> が必要になります。"
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -436,7 +435,7 @@ msgstr ""
 "方法を説明します。"
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -451,7 +450,7 @@ msgstr ""
 "場合、 フロッピーイメージは CD/DVD に含まれているはずです。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -463,13 +462,13 @@ msgstr ""
 "いようにしましょう。"
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Linux や Unix システムでのディスクイメージの書き込み"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -508,7 +507,7 @@ msgstr ""
 "してください。 詳細はマニュアルページをご覧ください)</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -542,7 +541,7 @@ msgstr ""
 "のシステムでは、システム管理者にお尋ねください。 </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -554,13 +553,13 @@ msgstr ""
 "ルしなければならないでしょう。"
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "DOS, Windows, OS/2 でのディスクイメージの書き込み"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -570,7 +569,7 @@ msgstr ""
 "は以下のプログラムのどれかが使えます。"
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -586,7 +585,7 @@ msgstr ""
 "ない</emphasis>ことが予想されます。"
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -598,7 +597,7 @@ msgstr ""
 "ディレクトリに diskio.dll を展開する必要があります。"
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -608,13 +607,13 @@ msgstr ""
 "す。"
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "MacOS からのディスクイメージの書き込み"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -636,7 +635,7 @@ msgstr ""
 "良いかを Disk Copy から尋ねられます。"
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -651,13 +650,13 @@ msgstr ""
 "下にいくつか紹介します。"
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "<command>Disk Copy</command> を用いたディスクイメージの書き込み"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -671,7 +670,7 @@ msgstr ""
 "ドした場合でのみ必要となります。"
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -681,7 +680,7 @@ msgstr ""
 "し、これを用いて <filename>root.bin</filename> ファイルをオープンします。"
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -693,7 +692,7 @@ msgstr ""
 "らのフィールドでは大文字小文字が区別されますので注意してください。"
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -709,7 +708,7 @@ msgstr ""
 "消してしまわないようにしてください。"
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -721,7 +720,7 @@ msgstr ""
 "diskcopy;\"></ulink> を試してみてください。"
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -737,13 +736,13 @@ msgstr ""
 "うかを訊かれます。 書き込みが終わったらフロッピーはイジェクトされます。"
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "<command>suntar</command> を用いたディスクイメージの書き込み"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -757,7 +756,7 @@ msgstr ""
 "quote> を選びます。"
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -766,7 +765,7 @@ msgstr ""
 "0 から始めます)。"
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -775,7 +774,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -789,7 +788,7 @@ msgstr ""
 "い。"
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -801,13 +800,13 @@ msgstr ""
 "合、 MacOS がフロッピーを壊してしまいます。"
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "USB メモリでの起動用ファイルの準備"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -830,7 +829,7 @@ msgstr ""
 "イッチを切る必要があります。"
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -843,13 +842,13 @@ msgstr ""
 "例えばハードディスク内のすべてのデータを失うといったことが起こります。"
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "ハイブリッド CD/DVD イメージを使った USB メモリの準備"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -863,7 +862,7 @@ msgstr ""
 "照してください。"
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -877,7 +876,7 @@ msgstr ""
 "があります)。"
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -896,7 +895,7 @@ msgstr ""
 "ます。"
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -912,7 +911,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -926,7 +925,7 @@ msgstr ""
 "実にアンマウントしてください。"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -938,7 +937,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -950,13 +949,13 @@ msgstr ""
 "す。"
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "USB メモリへのファイルの手動コピー"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -970,7 +969,7 @@ msgstr ""
 "少ないサイズでもセットアップできます)。"
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -986,7 +985,7 @@ msgstr ""
 "あります。"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -1002,19 +1001,19 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr "このイメージを使用するには、単にUSB メモリに直接展開してください。"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1026,13 +1025,13 @@ msgstr ""
 "モリに直接展開してください。"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1062,13 +1061,13 @@ msgstr ""
 "モリをアンマウント (<userinput>umount /mnt</userinput>) すると完了です。"
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "USB メモリへのファイルの手動コピー &mdash; 柔軟な方法"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1083,13 +1082,13 @@ msgstr ""
 "ということです。"
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "USB メモリのパーティション分割"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1099,7 +1098,7 @@ msgstr ""
 "を示します。"
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
 "Since most USB sticks come pre-configured with a single FAT16 partition, you "
@@ -1134,7 +1133,7 @@ msgstr ""
 "&debian; パッケージに含まれています。"
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1152,7 +1151,7 @@ msgstr ""
 "のに利用できます。"
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1177,13 +1176,13 @@ msgstr ""
 "を作成します。"
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "インストーライメージの追加"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1208,7 +1207,7 @@ msgstr ""
 "DOS (8.3) のファイル名しか処理できないことに注意してください。"
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
 "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1233,7 +1232,7 @@ msgstr ""
 "みで付加できます。"
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1243,7 +1242,7 @@ msgstr ""
 "<userinput>prompt 1</userinput> の行を追加してください。"
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy "
@@ -1271,7 +1270,7 @@ msgstr ""
 "ウントしてください (<userinput>umount /mnt</userinput>)。"
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1300,7 +1299,7 @@ msgstr ""
 "classname> &debian; パッケージに含まれています。"
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1316,7 +1315,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1351,7 +1350,7 @@ msgstr ""
 "常の Unix ユーティリティを使う準備ができたことになります。"
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1362,31 +1361,31 @@ msgstr ""
 "リへコピーしてください。"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (カーネルバイナリ)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (初期 RAM ディスクイメージ)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yaboot 設定ファイル)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (追加起動メッセージ)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1421,13 +1420,13 @@ msgstr ""
 "size</userinput> パラメータを、 増やす必要があることに注意してください。"
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "ハードディスク起動ファイルの準備"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1439,7 +1438,7 @@ msgstr ""
 "ることもできます。"
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1453,7 +1452,7 @@ msgstr ""
 "事全てを避けることができます。"
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1475,7 +1474,7 @@ msgstr ""
 "たファイル) をやりとりするためには、HFS パーティションが必要です。"
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1487,7 +1486,7 @@ msgstr ""
 "別々のプログラムを使います。"
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1497,7 +1496,7 @@ msgstr ""
 "らのインストーラの起動"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1507,7 +1506,7 @@ msgstr ""
 "して、linux を追加したり、 既存の linux を交換する方法について説明します。"
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1519,7 +1518,7 @@ msgstr ""
 "イルシステムとして使うことができます。"
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1531,19 +1530,19 @@ msgstr ""
 "してください)。例えば <filename>/boot/newinstall/</filename> などです。"
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (カーネルバイナリ)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (RAM ディスクイメージ)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1553,14 +1552,14 @@ msgstr ""
 "ください。"
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 "<command>loadlin</command> を使用したハードディスクからのインストーラの起動"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1570,7 +1569,7 @@ msgstr ""
 "するようハードディスクを準備する方法を説明します。"
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1580,7 +1579,7 @@ msgstr ""
 "コピーしてください。"
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1589,19 +1588,19 @@ msgstr ""
 "メージ)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (loadlin ツール)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "OldWorld Mac におけるハードディスクからのインストーラの起動"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1625,7 +1624,7 @@ msgstr ""
 "ためこのモデルでは <application>BootX</application> が必要です。"
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1653,13 +1652,13 @@ msgstr ""
 "System Folder に置いてください。"
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "NewWorld Mac におけるハードディスクからのインストーラの起動"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1680,7 +1679,7 @@ msgstr ""
 "PowerMac をサポートしておらず、 使うべきではありません。"
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1694,31 +1693,31 @@ msgstr ""
 "ラッグします)。"
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1734,7 +1733,7 @@ msgstr ""
 "入力するコマンドで必要となります。"
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1742,13 +1741,13 @@ msgstr ""
 "トーラを起動させるには、 <xref linkend=\"boot-newworld\"/> に進んでください。"
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "TFTP ネットブート用ファイルの準備"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1764,7 +1763,7 @@ msgstr ""
 "せん。"
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1777,7 +1776,7 @@ msgstr ""
 "要です。"
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1798,7 +1797,7 @@ msgstr ""
 "DHCP でしか設定できないこともあります。"
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1810,7 +1809,7 @@ msgstr ""
 "あります。"
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1821,7 +1820,7 @@ msgstr ""
 "す。"
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1835,7 +1834,7 @@ msgstr ""
 "4.x, SunOS 5.x (Solaris), GNU/Linux での例を示します。"
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1849,13 +1848,13 @@ msgstr ""
 "です。"
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "RARP サーバの設定"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1874,7 +1873,7 @@ msgstr ""
 "て <userinput>ip addr show dev eth0</userinput> コマンドを使ってください。"
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1899,13 +1898,13 @@ msgstr ""
 "で) 実行してください。"
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "DHCP サーバの設定"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1919,7 +1918,7 @@ msgstr ""
 "dhcpd.conf</filename> を参照)"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1963,7 +1962,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1980,7 +1979,7 @@ msgstr ""
 "ションは TFTP 経由で取得するファイルの名前です。"
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1991,13 +1990,13 @@ msgstr ""
 "してください。"
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "DHCP 設定での PXE 起動の有効化"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2068,13 +2067,13 @@ msgstr ""
 "い)。"
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "BOOTP サーバの設定"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2090,7 +2089,7 @@ msgstr ""
 "ぞれ入っています。"
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2154,7 +2153,7 @@ msgstr ""
 "userinput> 変数がマシンの MAC アドレスです。 </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2178,13 +2177,13 @@ msgstr ""
 "<command>dhcpd</command> を再起動するだけです。"
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "TFTP サーバの立ち上げ"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2194,7 +2193,7 @@ msgstr ""
 "を確認してください。"
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2209,7 +2208,7 @@ msgstr ""
 "は、パッケージのインストール時や再設定時に選択できます。"
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2227,7 +2226,7 @@ msgstr ""
 "要に応じて、本節の設定例を調整してください。"
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2243,7 +2242,7 @@ msgstr ""
 "勧めします。"
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2273,13 +2272,13 @@ msgstr ""
 "調整してください。"
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "TFTP イメージを適切な場所に配置する"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2295,7 +2294,7 @@ msgstr ""
 "TFTP クライアントによって決まり、 強制力のある標準は存在しません。"
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2311,13 +2310,13 @@ msgstr ""
 "す。"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2334,7 +2333,7 @@ msgstr ""
 "てください。"
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2351,13 +2350,13 @@ msgstr ""
 "を確認してください。"
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "SPARC TFTP ブート"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2387,7 +2386,7 @@ msgstr ""
 "字に変更し、 (必要なら) サブアーキテクチャ名を追加しなければなりません。"
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2401,7 +2400,7 @@ msgstr ""
 "い。"
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2415,13 +2414,13 @@ msgstr ""
 "しても TFTP サーバが見るディレクトリの内部でなければいけません。"
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI の TFTP での起動"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2435,13 +2434,13 @@ msgstr ""
 "filename> の <userinput>filename=</userinput> オプションに指定します。"
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "自動インストール"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2456,13 +2455,13 @@ msgstr ""
 "<ulink url=\"http://fai-project.org\">FAI home page</ulink> をご覧ください。"
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "&debian; インストーラを用いた自動インストール"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2476,7 +2475,7 @@ msgstr ""
 "れます。"
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po
index 68336f927..229db4274 100644
--- a/po/ko/boot-installer.po
+++ b/po/ko/boot-installer.po
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer.xml\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-11-03 04:50+0900\n"
 "Last-Translator: Changwoo Ryu <cwryu@debian.org>\n"
 "Language-Team: Korean <debian-i10n-korean@lists.debian.org>\n"
@@ -66,8 +66,8 @@ msgid "Booting from TFTP"
 msgstr "TFTP에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -77,8 +77,8 @@ msgstr ""
 "서버가 (DHCP, RARP 혹은 BOOTP) 필요합니다."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -88,8 +88,8 @@ msgstr ""
 "수도 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -105,8 +105,8 @@ msgid "Booting from CD-ROM"
 msgstr "CD-ROM에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -122,8 +122,8 @@ msgstr ""
 "넣고 다시 시작하고 다음 장으로 넘어가십시오."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -138,8 +138,8 @@ msgstr ""
 "다른 커널 및 설치 방법을 읽어보십시오."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -154,8 +154,8 @@ msgstr ""
 "ROM 드라이브로 맞춰 놓으십시오."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -393,8 +393,8 @@ msgid "The installer will now start as usual."
 msgstr "설치 프로그램은 지금 평소와 같이 시작됩니다."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "CD-ROM에서 부팅하기"
@@ -414,16 +414,22 @@ msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "먼저 <xref linkend=\"official-cdrom\"/> 및 <xref linkend=\"boot-usb-files\"/>"
 "에서 설명한 CD-ROM/DVD-ROM이나 USB 메모리 설치 미디어를 가져옵니다."
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -433,7 +439,7 @@ msgstr ""
 "우 실행 파일을 다운로드합니다."
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -448,7 +454,7 @@ msgstr ""
 "수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -459,13 +465,13 @@ msgstr ""
 "시 시작하도록 준비합니다."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "DOS에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -475,7 +481,7 @@ msgstr ""
 "스턴스 부팅 하세요."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -493,7 +499,7 @@ msgstr ""
 "이브를 바꿉니다."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -515,7 +521,7 @@ msgstr ""
 "다. 커널은 설치 시스템을 로드하고 실행됩니다."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -523,7 +529,7 @@ msgstr ""
 "<command>LILO</command> 혹은 <command>GRUB</command>을 사용해 리눅스 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -533,7 +539,7 @@ msgstr ""
 "files\"/>에서 설명한 필요한 파일을 다운로드해 하드 디스크에 저장해야 합니다."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -550,7 +556,7 @@ msgstr ""
 "파티션할 수 있습니다. 단 주의를 기울여야 합니다."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -567,7 +573,7 @@ msgstr ""
 "다음 네트워크 없이 그 CD/DVD 이미지에서 설치할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -585,7 +591,7 @@ msgstr ""
 "기 예제 <filename>/etc/lilo.conf</filename> 파일이 있습니다:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -597,7 +603,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -612,7 +618,7 @@ msgstr ""
 "하십시오. 이제 <userinput>lilo</userinput>를 실행하고 다시 부팅하십시오."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -628,7 +634,7 @@ msgstr ""
 "크의 첫번째 파티션일 때):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -642,7 +648,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -654,7 +660,7 @@ msgstr ""
 "어 설치 프로그램을 시작하는 항목은 다음과 같습니다:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -674,7 +680,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -684,13 +690,13 @@ msgstr ""
 "이 없습니다."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "USB 메모리에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
 "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -699,16 +705,21 @@ msgid ""
 "should boot up, and unless you have used the flexible way to build the stick "
 "and not enabled it, you should be presented with the <prompt>boot:</prompt> "
 "prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
-msgstr "<xref linkend=\"boot-dev-select\"/> 및 <xref linkend=\"boot-usb-files\"/>의 모든 것을 준비했으면, USB 메모리를 빈 USB 단자에 꼽고 컴퓨터를 다시 부팅하십시오. \"유연한 방법\"으로 USB 메모리를 준비해서 사용하는 경우가 아니라면, 시스템이 부팅해서 <prompt>boot:</prompt> 프롬프트가 나와야 합니다. 거기에서 부팅 파라미터를 추가로 넣을 수도 있고, 그냥 &enterkey;를 누를 수도 있습니다."
+msgstr ""
+"<xref linkend=\"boot-dev-select\"/> 및 <xref linkend=\"boot-usb-files\"/>의 "
+"모든 것을 준비했으면, USB 메모리를 빈 USB 단자에 꼽고 컴퓨터를 다시 부팅하십"
+"시오. \"유연한 방법\"으로 USB 메모리를 준비해서 사용하는 경우가 아니라면, 시"
+"스템이 부팅해서 <prompt>boot:</prompt> 프롬프트가 나와야 합니다. 거기에서 부"
+"팅 파라미터를 추가로 넣을 수도 있고, 그냥 &enterkey;를 누를 수도 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "플로피에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -718,7 +729,7 @@ msgstr ""
 "명한 대로 이미지를 플로피로 만듭니다."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -728,7 +739,7 @@ msgstr ""
 "고, 평소에 하던 방법처럼 시스템을 끈 다음 다시 켜십시오."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -746,7 +757,7 @@ msgstr ""
 "고 입력합니다."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -762,7 +773,7 @@ msgstr ""
 "때 하드 리부팅을 하십시오."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -772,7 +783,7 @@ msgstr ""
 "오고 마지막에 <prompt>boot:</prompt> 프롬프트가 나옵니다."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -788,7 +799,7 @@ msgstr ""
 "대한 더 자세한 정보는 아래의 <xref linkend=\"kernel-msgs\"/>에 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -801,26 +812,26 @@ msgstr ""
 "다. 설치 프로그램 <command>debian-installer</command>를 자동으로 실행합니다."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "TFTP로 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "i386에서 TFTP 부팅을 하려면 여러 가지 방법이 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "PXE를 지원하는 NIC 혹은 마더보드"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -834,13 +845,13 @@ msgstr ""
 "을 것입니다."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "네트워크 부트롬이 들어 있는 NIC"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -848,7 +859,7 @@ msgid ""
 msgstr "네트워크 인터페이스 카드에서 TFTP 부팅 기능을 지원할 수도 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -858,13 +869,13 @@ msgstr ""
 "서를 언급해 주십시오."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -874,13 +885,13 @@ msgstr ""
 "TFTPboot를 할 수 있는 부팅 디스켓과 부트롬이 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "부팅 화면"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -916,7 +927,7 @@ msgstr ""
 "의 두 배가 됩니다."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -931,7 +942,7 @@ msgstr ""
 "&enterkey; 키를 누르면 설치 프로그램이 시작합니다."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -942,7 +953,7 @@ msgstr ""
 "동 설치 관련 메뉴가 나타납니다."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -960,7 +971,7 @@ msgstr ""
 "을 취소합니다."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
 "Choosing the <quote>Help</quote> entry will result in the first help screen "
@@ -977,12 +988,22 @@ msgid ""
 "method (the default is <userinput>install</userinput>) and a space before "
 "the first parameter (e.g., <userinput>install fb=false</userinput>)."
 msgstr ""
-"<quote>Help</quote> 항목을 선택하면 첫번째 도움말 화면이 나오고, 여기에는 전체 도움말 화면들에 대한 요약이 들어 있습니다. 도움말 화면이 나타난 다음 부팅 메뉴로 돌아가려면, 부팅 프롬프트에서 'menu'를 입력하고 &enterkey;를 누르십시오. 모든 도움말 화면에는 부팅 명령어를 입력할 수 있는 부팅 프롬프트가 들어 있습니다: <informalexample><screen>\n"
+"<quote>Help</quote> 항목을 선택하면 첫번째 도움말 화면이 나오고, 여기에는 전"
+"체 도움말 화면들에 대한 요약이 들어 있습니다. 도움말 화면이 나타난 다음 부팅 "
+"메뉴로 돌아가려면, 부팅 프롬프트에서 'menu'를 입력하고 &enterkey;를 누르십시"
+"오. 모든 도움말 화면에는 부팅 명령어를 입력할 수 있는 부팅 프롬프트가 들어 있"
+"습니다: <informalexample><screen>\n"
 "Press F1 for the help index, or ENTER to boot:\n"
-"</screen></informalexample> 이 부팅 프롬프트에서 &enterkey; 키를 눌러서 기본 옵션으로 설치 프로그램을 시작할 수도 있고, 아니면 특정 부팅 명령어와 특정 부팅 파라미터를 지정할 수도 있습니다. 부팅 명령어에 사용할 수 있는 유용한 여러가지 부팅 파라미터가 도움말 화면에 설명되어 있습니다. 부팅 명령어에 파라미터를 입력하려면, 먼저 부팅 방법을 입력하고 (기본값은 <userinput>install</userinput>입니다.) 첫 파라미터 앞에 공백을 입력하십시오. (예를 들어, <userinput>install fb=false</userinput>)"
+"</screen></informalexample> 이 부팅 프롬프트에서 &enterkey; 키를 눌러서 기본 "
+"옵션으로 설치 프로그램을 시작할 수도 있고, 아니면 특정 부팅 명령어와 특정 부"
+"팅 파라미터를 지정할 수도 있습니다. 부팅 명령어에 사용할 수 있는 유용한 여러"
+"가지 부팅 파라미터가 도움말 화면에 설명되어 있습니다. 부팅 명령어에 파라미터"
+"를 입력하려면, 먼저 부팅 방법을 입력하고 (기본값은 <userinput>install</"
+"userinput>입니다.) 첫 파라미터 앞에 공백을 입력하십시오. (예를 들어, "
+"<userinput>install fb=false</userinput>)"
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -999,7 +1020,7 @@ msgstr ""
 "ulink>이 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1018,7 +1039,7 @@ msgstr ""
 "<quote>integrated Remote Assistant</quote> (IRA) 따위가 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1038,13 +1059,13 @@ msgstr ""
 "할 것입니다 ."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "CD 내용"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1067,7 +1088,7 @@ msgstr ""
 "있습니다."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1092,7 +1113,7 @@ msgstr ""
 "크 파티션이 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1107,7 +1128,7 @@ msgstr ""
 "습니다. 이러한 파일은 아래에 기술한 방법으로 EFI Shell에서 읽을 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1127,7 +1148,7 @@ msgstr ""
 "를 계속하기 전에 파티션 작업에서 EFI 파티션이 있는 지 검사도 합니다."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1148,13 +1169,13 @@ msgstr ""
 "만, 그 옵션이 없거나 CD가 부팅하지 않는다면 두 번째 옵션을 사용하십시오."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "중요"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1172,13 +1193,13 @@ msgstr ""
 "command> 명령을 실행해 Boot Manager로 돌아오십시오."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "방법 1: Boot Option Maintenance Menu에서 부팅"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1189,7 +1210,7 @@ msgstr ""
 "화를 마치면 EFI Boot Manager 페이지와 메뉴를 표시합니다."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1199,7 +1220,7 @@ msgstr ""
 "<command>ENTER</command>를 누르십시오. 그러면 다른 메뉴가 나타납니다."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1216,7 +1237,7 @@ msgstr ""
 "뉴 항목의 나머지를 보면, 장치와 컨트롤러 정보가 같은 지 알 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1233,7 +1254,7 @@ msgstr ""
 "디렉터리의 내용을 표시하고, 다음 단계로 진행할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1248,7 +1269,7 @@ msgstr ""
 "command>를 누르십시오. 그러면 부팅 과정을 시작합니다."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1259,13 +1280,13 @@ msgstr ""
 "합니다. 부팅 커널과 옵션 선택으로 이동하십시오."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "방법 2: EFI Shell에서 부팅"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1278,7 +1299,7 @@ msgstr ""
 "음과 같이 &debian; 설치 CD를 부팅하십시오:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1289,7 +1310,7 @@ msgstr ""
 "화를 마치면 EFI Boot Manager 페이지와 메뉴가 나타납니다."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1310,7 +1331,7 @@ msgstr ""
 "서 몇 초가 더 걸릴 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1323,7 +1344,7 @@ msgstr ""
 "이브는 <filename>fs0:</filename>이라고 나올 것입니다."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1337,7 +1358,7 @@ msgstr ""
 "에 표시합니다."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1347,7 +1368,7 @@ msgstr ""
 "그러면 부팅 과정을 시작합니다."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1362,13 +1383,13 @@ msgstr ""
 "다. 부팅 커널과 옵션 선택으로 이동하십시오."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "시리얼 콘솔을 사용해 설치하기"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1387,7 +1408,7 @@ msgstr ""
 "정되어 있는 메뉴 항목이 이미 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1400,7 +1421,7 @@ msgstr ""
 "로 알아낼 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1415,7 +1436,7 @@ msgstr ""
 "<command>console=ttyS1,57600n8</command>이라고 입력하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1432,7 +1453,7 @@ msgstr ""
 "도움말 메뉴를 참고하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1445,13 +1466,13 @@ msgstr ""
 "설치를 할 수 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "부팅 커널과 옵션 선택하기"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1469,7 +1490,7 @@ msgstr ""
 "<classname>Params</classname> 화면은 일반적인 명령행 옵션에 대해 설명합니다."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1491,7 +1512,7 @@ msgstr ""
 "택하고 설치를 시작합니다:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1499,7 +1520,7 @@ msgid ""
 msgstr "화살표 키로 가장 적합한 커널 버전과 설치 모드를 선택하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1511,7 +1532,7 @@ msgstr ""
 "정)."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1522,7 +1543,7 @@ msgstr ""
 "커널은 &debian; 설치 첫번째 화면에서 초기화 메시지를 표시합니다."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1531,7 +1552,7 @@ msgstr ""
 "다음 장으로 가서 언어 로캘, 네트워크, 디스크 파티션 설정을 계속 하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1549,7 +1570,7 @@ msgstr ""
 "지를 CD 드라이브가 아니라 네트워크에서 가져온다는 점입니다."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1563,13 +1584,13 @@ msgstr ""
 "팅 옵션을 정의해야 합니다."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "서버 설정하기"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1593,7 +1614,7 @@ msgstr ""
 "에서 실행하는 것입니다."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1609,7 +1630,7 @@ msgstr ""
 "이 들어 있습니다."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1627,7 +1648,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1648,13 +1669,13 @@ msgstr ""
 "<classname>elilo</classname> 패키지에 들어 있는 문서를 참고하십시오."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "클라이언트 설정하기"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1683,7 +1704,7 @@ msgstr ""
 "<filename>elilo.efi</filename> 파일을 서버에서 가져옵니다."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1698,13 +1719,13 @@ msgstr ""
 "시작합니다."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI TFTP 부팅"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1726,13 +1747,13 @@ msgstr ""
 "</screen></informalexample>이것을 입력합니다.."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "부팅 파라미터"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1742,7 +1763,7 @@ msgstr ""
 "어 뒤에 붙일 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1760,19 +1781,19 @@ msgstr ""
 "를 통해 넘길 수 있습니다:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Cobalt TFTP 부팅"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1789,7 +1810,7 @@ msgstr ""
 "지 설치 방법이 있습니다:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1804,7 +1825,7 @@ msgstr ""
 "수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1815,7 +1836,7 @@ msgstr ""
 "(115200 bps 속도) 접속해 설치를 할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1827,13 +1848,13 @@ msgstr ""
 "replaceable>에 파라미터를 추가하면 됩니다."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390 한계"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1843,7 +1864,7 @@ msgstr ""
 "고 SSH 세션이 필요합니다."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1856,13 +1877,13 @@ msgstr ""
 "합니다."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390 부팅 파라미터"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1874,7 +1895,7 @@ msgstr ""
 "filename>이 들어 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1891,7 +1912,7 @@ msgstr ""
 "keycap>, <keycap>Delete</keycap> 키를 동시에 누르고 있으십시오."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -1909,13 +1930,13 @@ msgstr ""
 "른 종류의 드라이브에서 부팅합니다."
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -1931,7 +1952,7 @@ msgstr ""
 "여 필요한 파일을 위해 CD를 지정하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -1943,19 +1964,19 @@ msgstr ""
 "을 입력합니다."
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "하드 디스크에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -1965,7 +1986,7 @@ msgstr ""
 "는 이게 유일한 설치 방법입니다."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -1976,13 +1997,13 @@ msgstr ""
 "\"/>에서 설명한대로 이미 다운로드가 완료 배치되고있을 필요가 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "맥오에스에서 올드월드 파워맥 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2004,13 +2025,13 @@ msgstr ""
 "치 프로그램을 시작하십시오."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "OpenFirmware에서 뉴월드 맥 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2053,19 +2074,19 @@ msgstr ""
 "다."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "USB 메모리에서 부팅하기"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr "현재 뉴월드 파워맥 시스템은 USB 부팅을 지원한다고 알려져 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2079,7 +2100,7 @@ msgstr ""
 "openfirmware\"/> 부분을 참고하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2101,7 +2122,7 @@ msgstr ""
 "동작하고 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2127,7 +2148,7 @@ msgstr ""
 "다."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2138,7 +2159,7 @@ msgstr ""
 "부팅 파라미터가 필요하면 입력하고, 아니면 그냥 &enterkey;를 누르십시오."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2150,13 +2171,13 @@ msgstr ""
 "는 대로 제출해 주십시오."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr "현재 PReP 및 뉴월드 파워맥 시스템은 네트워크 부팅을 지원합니다."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2192,7 +2213,7 @@ msgstr ""
 "법 및 사용할 수 있는 옵션 설명이 나옵니다."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2205,7 +2226,7 @@ msgstr ""
 "플로피 드라이브만 붙어 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2216,7 +2237,7 @@ msgstr ""
 "고 전원 단추를 누르기 전에 플로피를 드라이브에 넣으십시오."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2229,7 +2250,7 @@ msgstr ""
 "고, 부팅 가능한 하드 디스크 파티션을 찾게 됩니다."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2241,13 +2262,13 @@ msgstr ""
 "을 자동으로 시작합니다."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC 부팅 파라미터"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2263,7 +2284,7 @@ msgstr ""
 "<userinput>video=aty128fb:videomode:6</userinput>이라고 하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2282,7 +2303,7 @@ msgstr ""
 "가로 입력할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2294,13 +2315,13 @@ msgstr ""
 "master에서) 부팅합니다."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM 메시지"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2315,13 +2336,13 @@ msgstr ""
 "십시오."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "접근성"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2347,13 +2368,13 @@ msgstr ""
 "의 아키텍처는 키보드를 QWERTY 키보드로 인식하니 주의하십시오."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB 점자 디스플레이"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2373,13 +2394,13 @@ msgstr ""
 "\"><classname>brltty</classname> 웹사이트</ulink>에 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "시리얼 점자 디스플레이"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2417,13 +2438,13 @@ msgstr ""
 "classname> 웹사이트</ulink>에 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "소프트웨어 음성 합성 장치"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2438,13 +2459,13 @@ msgstr ""
 "의 경우) 선택한 언어로 진행됩니다."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "하드웨어 음성 합성 장치"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2455,7 +2476,7 @@ msgstr ""
 "그러므로 부팅 메뉴의 <quote>그래픽 설치</quote> 항목을 이용하십시오."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2476,13 +2497,13 @@ msgstr ""
 "성 장치 기능을 자동으로 설치합니다."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "보드 장치"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2497,7 +2518,7 @@ msgstr ""
 "비활성화 해야합니다 . 그러나 이것은 사용 가능한 언어가 줄어 듭니다."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2507,13 +2528,13 @@ msgstr ""
 "boot paramete를 &enterkey; 추가하기 전에 활성화 할 수 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "고대비 테마"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2525,13 +2546,13 @@ msgstr ""
 "userinput> 파라미터를 붙입니다."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "미리 설정하기"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2542,7 +2563,7 @@ msgstr ""
 "니다."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2555,7 +2576,7 @@ msgstr ""
 "냅니다. 하지만 몇몇 경우에는 파라미터로 커널을 조금 도와줘야 합니다."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2569,7 +2590,7 @@ msgstr ""
 "한 파라미터가 있는 지 찾아 보십시오."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2585,7 +2606,7 @@ msgstr ""
 "troubleshooting\"/>에 들어 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
 msgid ""
 "If you are booting with a serial console, generally the kernel will "
@@ -2595,10 +2616,15 @@ msgid ""
 "userinput> argument to the kernel, where <replaceable>device</replaceable> "
 "is your serial device, which is usually something like <filename>ttyS0</"
 "filename>."
-msgstr "시리얼 콘솔로 부팅하는 경우, 보통 자동으로 찾아냅니다. 시리얼 콘솔로 부팅하려는 컴퓨터에 비디오 카드와 (프레임버퍼) 키보드가 붙어 있다면, <userinput>console=<replaceable>장치</replaceable></userinput> 파라미터를 커널에 넘겨야 할 수 있습니다. 여기서 <replaceable>장치</replaceable>는 시리얼 장치이고, <filename>ttyS0</filename>과 같이 씁니다."
+msgstr ""
+"시리얼 콘솔로 부팅하는 경우, 보통 자동으로 찾아냅니다. 시리얼 콘솔로 부팅하려"
+"는 컴퓨터에 비디오 카드와 (프레임버퍼) 키보드가 붙어 있다면, "
+"<userinput>console=<replaceable>장치</replaceable></userinput> 파라미터를 커"
+"널에 넘겨야 할 수 있습니다. 여기서 <replaceable>장치</replaceable>는 시리얼 "
+"장치이고, <filename>ttyS0</filename>과 같이 씁니다."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
 msgid ""
 "In order to ensure the terminal type used by the installer matches your "
@@ -2612,10 +2638,19 @@ msgid ""
 "you can start it inside a <command>screen</command> session. That will "
 "indeed perform translation into the <literal>screen</literal> terminal type, "
 "which is very close to <literal>vt102</literal>."
-msgstr "설치 프로그램이 사용하는 터미널 종류가 사용하고 있는 터미널 에뮬레이터에 맞도록 하려면, <userinput>TERM=<replaceable>종류</replaceable></userinput> 파라미터를 추가할 수 있습니다. 단 설치 프로그램은 다음 터미널 종류만 지원합니다: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal>, <literal>dumb</literal>. &d-i;의 시리얼 콘솔의 기본값은 <userinput>vt102</userinput>입니다. 이런 터미널 종류를 지원하지 않는 가상화 도구를 사용하고 있다면(예를 들어 QEMU/KVM), <command>screen</command> 세션 안에서 그 툴을 시작하면 됩니다. 그러면 <literal>screen</literal> 터미널 타입으로 동작하는데 <literal>vt102</literal> 터미널과 매우 가깝습니다."
+msgstr ""
+"설치 프로그램이 사용하는 터미널 종류가 사용하고 있는 터미널 에뮬레이터에 맞도"
+"록 하려면, <userinput>TERM=<replaceable>종류</replaceable></userinput> 파라미"
+"터를 추가할 수 있습니다. 단 설치 프로그램은 다음 터미널 종류만 지원합니다: "
+"<literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, "
+"<literal>vt102</literal>, <literal>dumb</literal>. &d-i;의 시리얼 콘솔의 기본"
+"값은 <userinput>vt102</userinput>입니다. 이런 터미널 종류를 지원하지 않는 가"
+"상화 도구를 사용하고 있다면(예를 들어 QEMU/KVM), <command>screen</command> 세"
+"션 안에서 그 툴을 시작하면 됩니다. 그러면 <literal>screen</literal> 터미널 타"
+"입으로 동작하는데 <literal>vt102</literal> 터미널과 매우 가깝습니다."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2629,13 +2664,13 @@ msgstr ""
 "맞출 수도 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "&debian; 설치프로그램 파라미터"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2649,7 +2684,7 @@ msgstr ""
 "para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2664,19 +2699,19 @@ msgstr ""
 "제에서도 짧은 형식을 사용합니다."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "이 파라미터는 표시할 메시지의 가장 낮은 우선순위를 설정합니다."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2690,7 +2725,7 @@ msgstr ""
 "라 조정합니다."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2708,13 +2743,13 @@ msgstr ""
 "의 경우, 필수 메시지만 표시하고 질문에 신경 쓰지 않고 설치를 진행합니다."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2748,13 +2783,13 @@ msgstr ""
 "그래픽 설치 프로그램은 <userinput>gtk</userinput> 프론트엔드를 사용합니다."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2767,49 +2802,49 @@ msgstr ""
 "동작합니다. (부팅을 계속하려면 이 쉘을 끝내십시오.)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "기본값입니다."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "보통때보다 많은 디버깅 정보."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "디버깅 정보 아주 많이."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2819,13 +2854,13 @@ msgstr ""
 "속하려면 쉘을 나가면 됩니다."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -2836,7 +2871,7 @@ msgstr ""
 "다. 예를 들어, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>입니다."
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -2846,19 +2881,19 @@ msgstr ""
 "합니다. 이 파라미터를 재지정해서 장치 한 개만 검색하도록 만들 수 있습니다."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -2870,13 +2905,13 @@ msgstr ""
 "인 514번을 기본값으로 사용합니다."
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -2888,13 +2923,13 @@ msgstr ""
 "linkend=\"lowmem\"/> 부분도 참고하십시오."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -2904,13 +2939,13 @@ msgstr ""
 "되지 않은 상태에서 설치하는 경우에 좋습니다."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -2927,13 +2962,13 @@ msgstr ""
 "는 설치를 시작하고 몇 분 후에 멈추는 것은 문제의 증상입니다."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "hppa에서 그러한 문제가 보고되었습니다."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -2951,13 +2986,13 @@ msgstr ""
 "<userinput>fb=true</userinput> 파라미터를 넣고 부팅해 보십시오."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -2973,13 +3008,13 @@ msgstr ""
 "replaceable></userinput>를 파라미터로 넘기면 됩니다."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -2992,7 +3027,7 @@ msgstr ""
 "네트워크 셋업을 할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3006,13 +3041,13 @@ msgstr ""
 "할 수 있습니다."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3022,13 +3057,13 @@ msgstr ""
 "시작하지 않습니다. 일부 노트북 컴퓨터에서 이와 관련해 문제가 발생합니다."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3042,13 +3077,13 @@ msgstr ""
 "\">&debian; Installer Wiki</ulink>에 있습니다."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3058,13 +3093,13 @@ msgstr ""
 "자동화합니다. <xref linkend=\"automatic-install\"/> 참고."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3074,13 +3109,13 @@ msgstr ""
 "를 합니다. <xref linkend=\"automatic-install\"/> 참고."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3096,13 +3131,13 @@ msgstr ""
 "\"preseed-seenflag\"/> 부분을 보십시오."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3114,13 +3149,13 @@ msgstr ""
 "분을 보십시오."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3132,13 +3167,13 @@ msgstr ""
 "콘솔을 막지 않습니다."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3156,7 +3191,7 @@ msgstr ""
 "롯 방식 드라이브는 미디어를 자동으로 다시 집어넣지 못합니다."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3167,13 +3202,13 @@ msgstr ""
 "단 설치한 후에 시스템이 광학 드라이브에서 자동으로 부팅하지 않도록 하십시오."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3186,7 +3221,7 @@ msgstr ""
 "다.  <xref linkend=\"di-install-base\"/>도 참조하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3201,13 +3236,13 @@ msgstr ""
 "니다. 이 옵션은 숙련된 사용자가 이용해야 합니다."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3221,13 +3256,13 @@ msgstr ""
 "하지 않습니다.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3239,13 +3274,13 @@ msgstr ""
 "설정하십시오. 단위는 kB입니다."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3255,13 +3290,13 @@ msgstr ""
 "로 설정하십시오. <xref linkend=\"rescue\"/> 부분을 참고하십시오."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "부팅 파라미터로 질문에 답하기"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3275,25 +3310,25 @@ msgstr ""
 "오. 몇 가지 예제가 아래에 있습니다."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3303,7 +3338,7 @@ msgstr ""
 "습니다."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3321,7 +3356,7 @@ msgstr ""
 "제한 언어는 국가 및 locale의 모든 가능한 조합 방법을 얻을 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3336,13 +3371,13 @@ msgstr ""
 "수 있습니다. 예: <userinput>언어=en 국가=DE locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3358,7 +3393,7 @@ msgstr ""
 "\"/> 참고)</phrase>이 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3368,13 +3403,13 @@ msgstr ""
 "설정하십시오."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3391,13 +3426,13 @@ msgstr ""
 "이름을 입력해야한다는 것에주의하십시오."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3408,13 +3443,13 @@ msgstr ""
 "를 선택할 때 사용합니다. 자세한 정보는 <xref linkend=\"pkgsel\"/> 참고."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "커널 모듈에 파라미터 넘기기"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3436,7 +3471,7 @@ msgstr ""
 "로 적용됩니다."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3449,7 +3484,7 @@ msgstr ""
 "일부 경우에는 파라미터를 수동으로 지정해야 할 수도 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3470,19 +3505,19 @@ msgstr ""
 "페이스 카드에서 BNC (동축) 커넥터와 IRQ 10을 지정하려면, 다음과 같이 합니다:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "커널 모듈 블랙리스트"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3499,7 +3534,7 @@ msgstr ""
 "해당 장치가 제대로 동작하지 않을 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3514,7 +3549,7 @@ msgstr ""
 "치 프로그램이나 설치한 시스템에 적용합니다."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3527,19 +3562,19 @@ msgstr ""
 "을 읽어들이지 않게 만들 수 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "설치 과정의 문제 해결"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "CD-ROM 신뢰성"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3552,7 +3587,7 @@ msgstr ""
 "나 설치 도중에 CD-ROM을 읽으면서 오류가 발생하는 경우도 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3563,13 +3598,13 @@ msgstr ""
 "문제 및 각각의 경우 대처하는 방법을 설명합니다. 나머지는 여러분에게 맡깁니다."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "제일 먼저 확인할 수 있는 간단한 일이 두 가지 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3579,17 +3614,21 @@ msgstr ""
 "이 깨끗한지 확인하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid ""
 "If the installer fails to recognize a CD-ROM, try just running the option "
 "<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
 "menuchoice> a second time. Some DMA related issues with very old CD-ROM "
 "drives are known to be resolved in this way."
-msgstr "설치 프로그램이 CD-ROM을 인식하지 못하면, <menuchoice> <guimenuitem>CD-ROM 찾기 및 마운트</guimenuitem> </menuchoice> 옵션을 다시 한 번 실행해 보십시오. 아주 오래 된 CD-ROM에서 발생하는 일부 DMA 관련 문제는 이런 식으로 해결된다고 알려져 있습니다."
+msgstr ""
+"설치 프로그램이 CD-ROM을 인식하지 못하면, <menuchoice> <guimenuitem>CD-ROM 찾"
+"기 및 마운트</guimenuitem> </menuchoice> 옵션을 다시 한 번 실행해 보십시오. "
+"아주 오래 된 CD-ROM에서 발생하는 일부 DMA 관련 문제는 이런 식으로 해결된다고 "
+"알려져 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3601,7 +3640,7 @@ msgstr ""
 "되지만, 간략하게 하기 위해 CD-ROM이라는 용어만 사용합니다."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3611,13 +3650,13 @@ msgstr ""
 "오."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "공통 사항"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3627,35 +3666,39 @@ msgstr ""
 "다."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid ""
 "Some very old CD-ROM drives do not work correctly if <quote>direct memory "
 "access</quote> (DMA) is enabled for them."
-msgstr "일부 아주 오래 된 CD-ROM 드라이브는 <quote>직접 메모리 접근</quote>(DMA) 기능을 사용할 경우 올바르게 동작하지 않습니다."
+msgstr ""
+"일부 아주 오래 된 CD-ROM 드라이브는 <quote>직접 메모리 접근</quote>(DMA) 기능"
+"을 사용할 경우 올바르게 동작하지 않습니다."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "문제점 파악 및 해결 방법"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr "CD-ROM 부팅이 실패하면, 아래에 나온 방법을 시도해 보십시오."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid ""
 "Check that your BIOS actually supports booting from CD-ROM (only an issue "
 "for very old systems) and that CD booting is enabled in the BIOS."
-msgstr "BIOS가 CD-ROM 부팅을 지원하는 지 확인하고(아주 오래 된 시스템이 경우에만 해당됩니다) CD-ROM 드라이브가 해당 미디어를 지원하는 지 확인하십시오."
+msgstr ""
+"BIOS가 CD-ROM 부팅을 지원하는 지 확인하고(아주 오래 된 시스템이 경우에만 해당"
+"됩니다) CD-ROM 드라이브가 해당 미디어를 지원하는 지 확인하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3680,7 +3723,7 @@ msgstr ""
 "트 수만큼 CD-ROM에서 읽어들입니다."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3702,7 +3745,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3721,7 +3764,7 @@ msgstr ""
 "행하려면 먼저 두 번째 가상 콘솔(VT2)로 전환해서 쉘을 활성화하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3733,7 +3776,7 @@ msgstr ""
 "시오. 그 다음에 <command>dmesg</command>의 출력도 확인해 보십시오."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3763,7 +3806,7 @@ msgstr ""
 "드라이버를 읽어들여 보십시오."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3775,7 +3818,7 @@ msgstr ""
 "<filename>/dev/cdrom</filename> 파일도 있어야 합니다."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -3792,7 +3835,7 @@ msgstr ""
 "하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -3818,7 +3861,7 @@ msgstr ""
 "터리 안에서 실행해야 하는 것에 유의하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -3831,13 +3874,13 @@ msgstr ""
 "을 수 있는 지 시험하는 목적으로도 사용합니다."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "플로피 디스크 신뢰성"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -3847,7 +3890,7 @@ msgstr ""
 "디스크 신뢰성 문제일 것입니다."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -3864,7 +3907,7 @@ msgstr ""
 "로피에서도 디스크 입출력 오류 메시지만 가득 나오는 문제가 발생하기도 합니다."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -3881,7 +3924,7 @@ msgstr ""
 "다."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -3892,7 +3935,7 @@ msgstr ""
 "emphasis> 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -3903,7 +3946,7 @@ msgstr ""
 "md5sum을 검사해서 이미지가 올바른 지 확인하는 게 좋습니다."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -3915,13 +3958,13 @@ msgstr ""
 "이버때문입니다."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "부팅 설정"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -3934,16 +3977,18 @@ msgstr ""
 "linkend=\"boot-parms\"/>에 쓰여 있는 것처럼 제대로 되었는 지 확인하십시오."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
 "<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
 ">)."
-msgstr "장치의 펌웨어가 없어서 문제가 발생할 수도 있습니다. (<xref linkend=\"hardware-firmware\"/> 및 <xref linkend=\"loading-firmware\"/> 참고.)"
+msgstr ""
+"장치의 펌웨어가 없어서 문제가 발생할 수도 있습니다. (<xref linkend="
+"\"hardware-firmware\"/> 및 <xref linkend=\"loading-firmware\"/> 참고.)"
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -3960,37 +4005,37 @@ msgstr ""
 "스 시스템과 같은 컴퓨터에서 (예를 들어 라이브 CD) 실행하십시오."
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "자주 발생하는 &arch-title; 설치 문제"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4000,7 +4045,7 @@ msgstr ""
 "법으로 해결할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4020,13 +4065,13 @@ msgstr ""
 "분을 참고하십시오."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "PCMCIA 설정 단계에서 시스템 멈춤"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
 msgid ""
 "Some very old laptop models produced by Dell are known to crash when PCMCIA "
@@ -4036,10 +4081,16 @@ msgid ""
 "the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
 "can then configure PCMCIA after the installation is completed and exclude "
 "the resource range causing the problems."
-msgstr "Dell에서 제조한 아주 오래 전 노트북 모델은 PCMCIA 장치를 찾을 때 특정 하드웨어 주소에 접근하는 순간 멈춰 버립니다. 그 외의 노트북 모델도 비슷한 현상이 나타날 수 있습니다. 만약 그러한 문제가 발생하고 설치할 때 PCMCIA 기능이 필요없다면, <userinput>hw-detect/start_pcmcia=false</userinput> 부팅 파라미터로 PCMCIA를 끌 수 있습니다. 설치를 마친 다음에 PCMCIA를 설정해서 문제가 발생하는 구간을 제외할 수 있습니다."
+msgstr ""
+"Dell에서 제조한 아주 오래 전 노트북 모델은 PCMCIA 장치를 찾을 때 특정 하드웨"
+"어 주소에 접근하는 순간 멈춰 버립니다. 그 외의 노트북 모델도 비슷한 현상이 나"
+"타날 수 있습니다. 만약 그러한 문제가 발생하고 설치할 때 PCMCIA 기능이 필요없"
+"다면, <userinput>hw-detect/start_pcmcia=false</userinput> 부팅 파라미터로 "
+"PCMCIA를 끌 수 있습니다. 설치를 마친 다음에 PCMCIA를 설정해서 문제가 발생하"
+"는 구간을 제외할 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4060,19 +4111,19 @@ msgstr ""
 "값을 입력할 때, 쉼표를 쓰지 않는다는 것에 유의하십시오."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "자주 발생하는 설치 문제 중에 몇 가지를 설명합니다."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "비디오 출력이 다른 곳으로 가는 경우"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4099,7 +4150,7 @@ msgstr ""
 "<userinput>video=atyfb:off</userinput> 파라미터로 설치 프로그램을 부팅합니다."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4112,13 +4163,13 @@ msgstr ""
 "xorg.conf</filename>의 비디오 드라이버도 바꿔야 합니다."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "부팅 실패 혹은 CD-ROM에서 설치 실패"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4130,20 +4181,20 @@ msgstr ""
 "SunBlade 시스템에서 보고되었습니다."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 "이러한 시스템에서는 설치 프로그램을 네트워크 부팅해서 설치하기를 권장합니다."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "커널 시작 메시지 해석하기"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4179,13 +4230,13 @@ msgstr ""
 "arch=\"linux-any\">(<xref linkend=\"kernel-baking\"/> 참고)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "설치 문제 보고하기"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4204,7 +4255,7 @@ msgstr ""
 "부해 주십시오."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4216,13 +4267,13 @@ msgstr ""
 "들어 있습니다."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "설치 보고 제출"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4235,7 +4286,7 @@ msgstr ""
 "사용하는 지에 대한 정보를 많이 얻을 수 있습니다."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4246,7 +4297,7 @@ msgstr ""
 "스트에도 전달됩니다. 공개해도 상관 없는 전자메일 주소를 사용하도록 하십시오."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4265,7 +4316,7 @@ msgstr ""
 "<command>reportbug installation-reports</command>를 실행하십시오."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/ko/install-methods.po b/po/ko/install-methods.po
index 52db058d6..2e133e63b 100644
--- a/po/ko/install-methods.po
+++ b/po/ko/install-methods.po
@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods.xml\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-11-08 12:26+0900\n"
 "Last-Translator: Changwoo Ryu <cwryu@debian.org>\n"
 "Language-Team: Korean <debian-l10n-korean@lists.debian.org>\n"
@@ -49,22 +49,45 @@ msgid ""
 "most-used files are on the first CDs and DVDs, so that a basic desktop "
 "installation can be done with only the first DVD or - to a limited extent - "
 "even with only the first CD."
-msgstr "현재 &debian-gnu;를 설치하는 가장 쉬운 방법은 공식 &debian; CD/DVD-ROM 세트로 설치하는 것입니다. 공급 업체에서 이 세트를 구입할 수 있습니다(<ulink url=\"&url-debian-cd-vendors;\">CD 벤더 페이지 </ulink> 참조). 고속 네트워크 연결과 CD/DVD 라이터가 있으면, &debian; 미러 사이트에서 CD/DVD-ROM 이미지를 다운로드해도 괜찮습니다(자세한 설명은 <ulink url=\"&url-debian-cd;\">데비안 CD 페이지</ulink> 및 <ulink url=\"&url-debian-cd-faq;\">데비안 CD FAQ</ulink> 참고). &debian; CD/DVD 세트를 가지고 있고, 시스템이 CD/DVD에서 부팅할 수 있으면<phrase arch=\"x86\">(최근 대부분의 PC에서는 부팅이 됩니다)</phrase>, <xref linkend=\"boot-installer\"/> 부분으로 넘어갈 수 있습니다. 많이 사용되는 파일이 첫번째 CD 또는 DVD에 들어가도록 많은 노력을 하고 있습니다. 그러므로 기본적인 데스크톱 설치는 첫번째 DVD 또는 (제한적이긴 하지만) 첫번째 CD로도 가능합니다."
+msgstr ""
+"현재 &debian-gnu;를 설치하는 가장 쉬운 방법은 공식 &debian; CD/DVD-ROM 세트"
+"로 설치하는 것입니다. 공급 업체에서 이 세트를 구입할 수 있습니다(<ulink url="
+"\"&url-debian-cd-vendors;\">CD 벤더 페이지 </ulink> 참조). 고속 네트워크 연결"
+"과 CD/DVD 라이터가 있으면, &debian; 미러 사이트에서 CD/DVD-ROM 이미지를 다운"
+"로드해도 괜찮습니다(자세한 설명은 <ulink url=\"&url-debian-cd;\">데비안 CD 페"
+"이지</ulink> 및 <ulink url=\"&url-debian-cd-faq;\">데비안 CD FAQ</ulink> 참"
+"고). &debian; CD/DVD 세트를 가지고 있고, 시스템이 CD/DVD에서 부팅할 수 있으면"
+"<phrase arch=\"x86\">(최근 대부분의 PC에서는 부팅이 됩니다)</phrase>, <xref "
+"linkend=\"boot-installer\"/> 부분으로 넘어갈 수 있습니다. 많이 사용되는 파일"
+"이 첫번째 CD 또는 DVD에 들어가도록 많은 노력을 하고 있습니다. 그러므로 기본적"
+"인 데스크톱 설치는 첫번째 DVD 또는 (제한적이긴 하지만) 첫번째 CD로도 가능합니"
+"다."
 
 #. Tag: para
 #: install-methods.xml:30
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "As CDs have a rather limited capacity by today's standards, not all "
+#| "graphical desktop environments are installable with only the first CD; "
+#| "only XFCE (which is the default desktop environment installed by &debian-"
+#| "gnu; &release;) completely fits on the first CD. For all other desktop "
+#| "environments a CD installation requires either network connectivity "
+#| "during the installation to download the remaining files or additional CDs."
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
-msgstr "CD는 요즘 추세에서는 용량이 그리 크기 않기 때문에, 그래픽 데스크톱 환경 중에서는 첫 번째 CD로 설치할 수 없는 경우도 있습니다. XFCE는 첫번째 CD에 들어갑니다. &debian-gnu; &release;에서 설치하는 기본 데스크톱 환경입니다. 다른 데스크톱은 설치 중에 나머지 파일을 다운로드할 수 있도록 네트워크 연결이 필요하거나 추가 CD가 필요합니다."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
+msgstr ""
+"CD는 요즘 추세에서는 용량이 그리 크기 않기 때문에, 그래픽 데스크톱 환경 중에"
+"서는 첫 번째 CD로 설치할 수 없는 경우도 있습니다. XFCE는 첫번째 CD에 들어갑니"
+"다. &debian-gnu; &release;에서 설치하는 기본 데스크톱 환경입니다. 다른 데스크"
+"톱은 설치 중에 나머지 파일을 다운로드할 수 있도록 네트워크 연결이 필요하거나 "
+"추가 CD가 필요합니다."
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
 msgid ""
 "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
@@ -79,10 +102,21 @@ msgid ""
 "identical. So when archive file paths are given below for particular files "
 "you need for booting, look for those files in the same directories and "
 "subdirectories on your CD."
-msgstr "당신의 컴퓨터가 CD부팅을 지원하지 않지만<phrase arch=\"x86\">(아주 오래된 시스템의 경우에만 해당됩니다)</phrase> CD 세트를 가지고 있다면, 다른 방법으로 <phrase condition=\"supports-floppy-boot\">플로피 디스크,</phrase> <phrase arch=\"s390\">테이프, 테이프 에뮬레이션,</phrase> <phrase condition=\"bootable-disk\">하드 디스크,</phrase> <phrase condition=\"bootable-usb\">USB 메모리,</phrase> <phrase condition=\"supports-tftp\">네트워크 부팅</phrase> 방법을 사용할 수 있고 아니면 커널을 CD에서 수동으로 읽어들여 설치 프로그램을 부팅할 수 있습니다. 이렇게 부팅할 때 필요한 파일은 CD에 있습니다. &debian; 네트워크 아카이브와 CD의 폴더 구조는 동일합니다. 그러므로 부팅하는 데 필요한 어떤 파일이 아카이브에서 있다면, CD의 같은 서브 디렉터리에서 파일을 찾을 수 있습니다."
+msgstr ""
+"당신의 컴퓨터가 CD부팅을 지원하지 않지만<phrase arch=\"x86\">(아주 오래된 시"
+"스템의 경우에만 해당됩니다)</phrase> CD 세트를 가지고 있다면, 다른 방법으로 "
+"<phrase condition=\"supports-floppy-boot\">플로피 디스크,</phrase> <phrase "
+"arch=\"s390\">테이프, 테이프 에뮬레이션,</phrase> <phrase condition="
+"\"bootable-disk\">하드 디스크,</phrase> <phrase condition=\"bootable-usb"
+"\">USB 메모리,</phrase> <phrase condition=\"supports-tftp\">네트워크 부팅</"
+"phrase> 방법을 사용할 수 있고 아니면 커널을 CD에서 수동으로 읽어들여 설치 프"
+"로그램을 부팅할 수 있습니다. 이렇게 부팅할 때 필요한 파일은 CD에 있습니다. "
+"&debian; 네트워크 아카이브와 CD의 폴더 구조는 동일합니다. 그러므로 부팅하는 "
+"데 필요한 어떤 파일이 아카이브에서 있다면, CD의 같은 서브 디렉터리에서 파일"
+"을 찾을 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -92,7 +126,7 @@ msgstr ""
 "습니다."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -110,13 +144,13 @@ msgstr ""
 "시오. 그러면 이 파일을 이용해 설치 프로그램을 부팅할 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "&debian; 미러에서 파일 다운로드"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -126,7 +160,7 @@ msgstr ""
 "\"&url-debian-mirrors;\"> &debian; 미러 사이트 목록</ulink>를 참조하십시오."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -137,13 +171,13 @@ msgstr ""
 "동 선택 모드로 받으면 안됩니다."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "설치 이미지를 찾을 위치"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -158,13 +192,13 @@ msgstr ""
 "installer;images/MANIFEST\">MANIFEST</ulink>에 설명되어 있습니다."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Thecus N2100 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -178,13 +212,13 @@ msgstr ""
 "수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "GLAN Tank 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -195,13 +229,13 @@ msgstr ""
 "미지가 필요합니다. 이 이미지는 &glantank-firmware-img;에서 얻을 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Kurobox Pro 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -213,13 +247,13 @@ msgstr ""
 "서 취득할 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "HP mv2120 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -235,60 +269,69 @@ msgstr ""
 "다."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "QNAP Turbo Station 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
 "ramdisk as well as a script to write these images to flash. You can obtain "
 "the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
 "kirkwood-firmware-img;."
-msgstr "QNAP Turbo Station의 설치 파일은 커널, 램디스크 이미지, 그리고 플래시 메모리에 쓰는 스크립트로 구성되어 있습니다. 이 QNAP TS-11x, TS-21x 및 TS-41x용 설치 파일을 &qnap-kirkwood-firmware-img; 위치에서 구할 수 있습니다."
+msgstr ""
+"QNAP Turbo Station의 설치 파일은 커널, 램디스크 이미지, 그리고 플래시 메모리"
+"에 쓰는 스크립트로 구성되어 있습니다. 이 QNAP TS-11x, TS-21x 및 TS-41x용 설"
+"치 파일을 &qnap-kirkwood-firmware-img; 위치에서 구할 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Plug Computer 및 OpenRD 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
 msgid ""
 "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
 "etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
 "obtain these files from &kirkwood-marvell-firmware-img;."
-msgstr "플러그 컴퓨터(SheevaPlug, GuruPlug, DreamPlug 등) 및 OpenRD 장치의 설치 파일은 U-Boot용 커널과 initrd로 구성되어 있습니다. 이 파일을 &kirkwood-marvell-firmware-img; 위치에서 구할 수 있습니다."
+msgstr ""
+"플러그 컴퓨터(SheevaPlug, GuruPlug, DreamPlug 등) 및 OpenRD 장치의 설치 파일"
+"은 U-Boot용 커널과 initrd로 구성되어 있습니다. 이 파일을 &kirkwood-marvell-"
+"firmware-img; 위치에서 구할 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr "LaCie NAS 설치 파일"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
 msgid ""
 "The installation files for LaCie NASes (Network Space v2, Network Space Max "
 "v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
 "consist of a kernel and initrd for U-Boot. You can obtain these files from "
 "&lacie-kirkwood-firmware-img;."
-msgstr "Lacie NAS(Network Space v2, Network Space Max v2, d2 Network v2, 2Big Network v2, 5Big Network v2)의 설치 파일은 U-Boot용 커널과 initrd로 구성되어 있습니다. 이 파일을 &lacie-kirkwood-firmware-img; 위치에서 구할 수 있습니다."
+msgstr ""
+"Lacie NAS(Network Space v2, Network Space Max v2, d2 Network v2, 2Big "
+"Network v2, 5Big Network v2)의 설치 파일은 U-Boot용 커널과 initrd로 구성되어 "
+"있습니다. 이 파일을 &lacie-kirkwood-firmware-img; 위치에서 구할 수 있습니다."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "IPL 테이프 만들기"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -310,13 +353,13 @@ msgstr ""
 "linkend=\"where-files\"/> 부분을 참고하십시오."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "디스크 이미지에서 플로피 만들기"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -326,7 +369,7 @@ msgstr ""
 "플로피 디스크를 사용해 설치 프로그램을 부팅합니다."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -336,7 +379,7 @@ msgstr ""
 "그램 부팅하기가 실패합니다."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -355,7 +398,7 @@ msgstr ""
 "터를 플로피에 <emphasis>섹터 복사</emphasis>해야 합니다."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -366,7 +409,7 @@ msgstr ""
 "여러 가지 플랫폼에서 디스크 이미지로 플로피를 만드는 방법을 설명합니다."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -381,7 +424,7 @@ msgstr ""
 "다. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -392,13 +435,13 @@ msgstr ""
 "을 걸어 놓아서 플로피 내용이 손상되지 않도록 하십시오."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "리눅스나 유닉스 시스템에서 디스크 이미지 쓰기"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -434,7 +477,7 @@ msgstr ""
 "용하십시오. 맨페이지를 참고하십시오.)</phrase>"
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -466,7 +509,7 @@ msgstr ""
 "문의하십시오. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -478,13 +521,13 @@ msgstr ""
 "야 할 수도 있습니다."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "DOS, 윈도우, OS/2에서 디스크 이미지 쓰기"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -494,7 +537,7 @@ msgstr ""
 "로 복사하십시오."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -508,7 +551,7 @@ msgstr ""
 "기에서 이 프로그램을 두번 눌러도 동작하지 <emphasis>않습니다</emphasis>."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -520,7 +563,7 @@ msgstr ""
 "diskio.dll 파일을 풀어야 합니다."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -529,13 +572,13 @@ msgstr ""
 "이 도구는 공식 &debian; CD-ROM의 <filename>/tools</filename>에 있습니다."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "맥오에스에서 디스크 이미지 쓰기"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -556,7 +599,7 @@ msgstr ""
 "쓸 지 여부를 Disk Copy에서 묻습니다."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -570,13 +613,13 @@ msgstr ""
 "피 이미지를 만드려면 다음 방법 중의 하나를 사용하십시오."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "<command>Disk Copy</command>로 디스크 이미지 쓰기"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -589,7 +632,7 @@ msgstr ""
 "의 작업은 이미지 파일을 &debian; 미러에서 다운로드하는 경우에만 필요합니다."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -599,7 +642,7 @@ msgstr ""
 "서 그걸 이용해 <filename>root.bin</filename> 파일을 여십시오."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -611,7 +654,7 @@ msgstr ""
 "별합니다."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -626,7 +669,7 @@ msgstr ""
 "지를 마운트하더라도 부트 블록을 망가뜨리지 않습니다."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -638,7 +681,7 @@ msgstr ""
 "\"&url-powerpc-diskcopy;\"></ulink>에서 받으십시오."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -654,13 +697,13 @@ msgstr ""
 "정말로 플로피를 지울 지 물어봅니다. 다 마치면 플로피가 튀어 나옵니다."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "<command>suntar</command>로 디스크 이미지 쓰기"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -674,21 +717,21 @@ msgstr ""
 "선택하십시오."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr "플로피를 넣고, &enterkey;를 누르십시오. (섹터 0에서 시작)"
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr "파일 열기 창에서 <filename>root.bin</filename> 파일을 선택하십시오."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -701,7 +744,7 @@ msgstr ""
 "오류가 발생하면 그 플로피를 꺼내고 다른 플로피로 시도해 보십시오."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -713,13 +756,13 @@ msgstr ""
 "데이터를 망가뜨립니다."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "USB 메모리 부팅에 필요한 파일 준비하기"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -742,7 +785,7 @@ msgstr ""
 "야 할 수도 있습니다."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -755,13 +798,13 @@ msgstr ""
 "못 사용해 하드 디스크에 들어 있는 내용이 모두 지워질 수도 잇습니다."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "하이브리드 CD/DVD 이미지를 사용해 USB 메모리 준비하기"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -775,7 +818,7 @@ msgstr ""
 "\"official-cdrom\"/> 참고."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -788,7 +831,7 @@ msgstr ""
 "linkend=\"where-files\"/>에서 언급된 위치에서) 다운로드할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -805,7 +848,7 @@ msgstr ""
 "어 넣어야합니다."
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -821,7 +864,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -835,7 +878,7 @@ msgstr ""
 "야 합니다:"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -847,7 +890,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -858,13 +901,13 @@ msgstr ""
 "에 다른 방법은 더 복잡하고, 특별한 경우 아니면 필요가 없습니다."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "수동으로 USB 메모리에 파일 복사하기"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -877,7 +920,7 @@ msgstr ""
 ">에 쓰여 있는 대로 하면 더 작아도 가능합니다.)"
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -892,7 +935,7 @@ msgstr ""
 "media/boot.img.gz</filename>라는 올인원 파일이 있습니다."
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -906,19 +949,19 @@ msgstr ""
 "을 나눠서 새 파일 시스템을 만들어야 다른 용도로 사용할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr "이 이미지를 사용하려면 USB 메모리에 압축을 풀어 놓기만 하면 됩니다:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -930,13 +973,13 @@ msgstr ""
 "로 풀어 놓으십시오:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
 msgid ""
 "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -947,16 +990,23 @@ msgid ""
 "filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
 "CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
 "are done."
-msgstr "그 후, USB 메모리를 마운트하면<phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>)</phrase><phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>)</phrase> 그 안에 <phrase arch=\"x86\">FAT 파일 시스템</phrase> <phrase arch=\"powerpc\">HFS 파일 시스템</phrase>이 생깁니다. 거기에 &debian; ISO 이미지를 (netinst나 전체 이미지 중 하나) 복사합니다. USB 메모리를 마운트 해제하면 (<userinput>umount /mnt</userinput>) 끝납니다."
+msgstr ""
+"그 후, USB 메모리를 마운트하면<phrase arch=\"x86\">(<userinput>mount /dev/"
+"<replaceable>sdX</replaceable> /mnt</userinput>)</phrase><phrase arch="
+"\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</"
+"userinput>)</phrase> 그 안에 <phrase arch=\"x86\">FAT 파일 시스템</phrase> "
+"<phrase arch=\"powerpc\">HFS 파일 시스템</phrase>이 생깁니다. 거기에 "
+"&debian; ISO 이미지를 (netinst나 전체 이미지 중 하나) 복사합니다. USB 메모리"
+"를 마운트 해제하면 (<userinput>umount /mnt</userinput>) 끝납니다."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "수동으로 USB 메모리에 파일 복사하기 &mdash; 유연한 방법"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -971,13 +1021,13 @@ msgstr ""
 "는 점입니다."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "USB 메모리 파티션 나누기"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -987,7 +1037,7 @@ msgstr ""
 "법입니다."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
 "Since most USB sticks come pre-configured with a single FAT16 partition, you "
@@ -1005,14 +1055,23 @@ msgid ""
 "for your USB stick. The <command>mkdosfs</command> command is contained in "
 "the <classname>dosfstools</classname> &debian; package."
 msgstr ""
-"대부분의 USB 메모리는 FAT16 파티션 하나로 미리 설정되어 있으므로, 아마 USB 메모리의 파티션 분할을 재시도하거나 다시 포맷할 필요가 없습니다. 포맷 해야하는 경우는 <command>cfdisk</command>나 기타 파티션 도구를 사용하고, FAT16 파티션을 만들고<footnote><para><quote>bootable</quote> 플래그를 잊지 말고 붙이십시오. </para></footnote> 다음과 같이 MBR을 설치하십시오.<informalexample><screen>\n"
+"대부분의 USB 메모리는 FAT16 파티션 하나로 미리 설정되어 있으므로, 아마 USB 메"
+"모리의 파티션 분할을 재시도하거나 다시 포맷할 필요가 없습니다. 포맷 해야하는 "
+"경우는 <command>cfdisk</command>나 기타 파티션 도구를 사용하고, FAT16 파티션"
+"을 만들고<footnote><para><quote>bootable</quote> 플래그를 잊지 말고 붙이십시"
+"오. </para></footnote> 다음과 같이 MBR을 설치하십시오."
+"<informalexample><screen>\n"
 "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-" </screen></informalexample> <command>install-mbr</command> 명령은 <classname>mbr</classname> &debian; 패키지에 들어 있습니다. 다음과 같이 파일 시스템을 만드십시오: <informalexample><screen>\n"
+" </screen></informalexample> <command>install-mbr</command> 명령은 "
+"<classname>mbr</classname> &debian; 패키지에 들어 있습니다. 다음과 같이 파일 "
+"시스템을 만드십시오: <informalexample><screen>\n"
 "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-"</screen></informalexample> 주의해서 USB 메모리의 정확한 디바이스 이름을 사용하십시오. <command>mkdosfs</command>는 <classname>dosfstools</classname> &debian; 패키지에 포함되어 있습니다."
+"</screen></informalexample> 주의해서 USB 메모리의 정확한 디바이스 이름을 사용"
+"하십시오. <command>mkdosfs</command>는 <classname>dosfstools</classname> "
+"&debian; 패키지에 포함되어 있습니다."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1030,7 +1089,7 @@ msgstr ""
 "떤 운영 체제라도 부트로더를 설정할 때 이용할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1053,13 +1112,13 @@ msgstr ""
 "<filename>ldlinux.sys</filename> 파일을 만듭니다."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "설치 프로그램 이미지 추가하기"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1084,7 +1143,7 @@ msgstr ""
 "이름만 처리할 수 없음에 주의하십시오."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
 "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1098,21 +1157,28 @@ msgid ""
 "<userinput>vga=788</userinput> to the second line. Other parameters can be "
 "appended as desired."
 msgstr ""
-"그 다음 <filename>syslinux.cfg</filename> 설정 파일을 만듭니다. 최소한 다음 두 줄이 필요합니다 (<filename>netboot</filename>를 사용하는 경우, 커널 바이너리 이름을 <quote><filename>linux</filename></quote>로 변경하십시오): <informalexample><screen>\n"
+"그 다음 <filename>syslinux.cfg</filename> 설정 파일을 만듭니다. 최소한 다음 "
+"두 줄이 필요합니다 (<filename>netboot</filename>를 사용하는 경우, 커널 바이너"
+"리 이름을 <quote><filename>linux</filename></quote>로 변경하십시오): "
+"<informalexample><screen>\n"
 "default vmlinuz\n"
 "append initrd=initrd.gz\n"
-"</screen></informalexample> 그래픽 설치 프로그램은 두 번째 줄에 <userinput>vga=788</userinput>를 추가하십시오. 다른 파라미터도 원하는대로 뒤에 붙일 수 있습니다."
+"</screen></informalexample> 그래픽 설치 프로그램은 두 번째 줄에 "
+"<userinput>vga=788</userinput>를 추가하십시오. 다른 파라미터도 원하는대로 뒤"
+"에 붙일 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
 "<userinput>prompt 1</userinput> line."
-msgstr "부팅 프롬프트에서 파라미터를 추가할 수 있게 허용하려면 <userinput>prompt 1</userinput> 줄을 추가하십시오."
+msgstr ""
+"부팅 프롬프트에서 파라미터를 추가할 수 있게 허용하려면 <userinput>prompt 1</"
+"userinput> 줄을 추가하십시오."
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
 msgid ""
 "If you used an <filename>hd-media</filename> image, you should now copy the "
@@ -1122,10 +1188,16 @@ msgid ""
 "filename></quote> image is not usable for this purpose. </para> </footnote> "
 "onto the stick. When you are done, unmount the USB memory stick "
 "(<userinput>umount /mnt</userinput>)."
-msgstr "<filename>hd-media</filename> 이미지를 사용하는 경우 여기에서 &debian; ISO 이미지 파일을<footnote><para> netinst나 전체 CD 이미지 중 하나를 사용할 수 있습니다(<xref linkend=\"official-cdrom\"/> 참조). 반드시 맞는 이미지를 선택하십시오. <quote>netboot<filename>mini.iso</filename></quote> 이미지는 이 용도에 사용할 수 없으니 주의하십시오.</para></footnote> USB 메모리에 복사합니다. 완료되면 USB 메모리 마운트를 해제하십시오 (<userinput>umount /mnt</userinput>)."
+msgstr ""
+"<filename>hd-media</filename> 이미지를 사용하는 경우 여기에서 &debian; ISO 이"
+"미지 파일을<footnote><para> netinst나 전체 CD 이미지 중 하나를 사용할 수 있습"
+"니다(<xref linkend=\"official-cdrom\"/> 참조). 반드시 맞는 이미지를 선택하십"
+"시오. <quote>netboot<filename>mini.iso</filename></quote> 이미지는 이 용도에 "
+"사용할 수 없으니 주의하십시오.</para></footnote> USB 메모리에 복사합니다. 완"
+"료되면 USB 메모리 마운트를 해제하십시오 (<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1154,7 +1226,7 @@ msgstr ""
 "&debian; 패키지에 포함되어 있습니다."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1169,7 +1241,7 @@ msgstr ""
 "체제라도 부트로더 설정을 바꾸는 데 이용할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1204,7 +1276,7 @@ msgstr ""
 "모리의 나머지를 준비할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1214,31 +1286,31 @@ msgstr ""
 "mnt</userinput>) 다음 설치 프로그램 파일을 USB 메모리로 복사하십시오:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (커널 바이너리)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (최초 램디스크 이미지)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yaboot 설정 파일)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (추가 부팅 메시지)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1273,13 +1345,13 @@ msgstr ""
 "팅하려는 이미지에 따라 크기를 늘려야 할 수도 있습니다."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "하드 디스크 부팅에 필요한 파일 준비하기"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1291,7 +1363,7 @@ msgstr ""
 "접 부트로더를 실행할 수도 있습니다."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1304,7 +1376,7 @@ msgstr ""
 "불안한 플로피와 씨름할 필요도 없습니다."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1326,7 +1398,7 @@ msgstr ""
 "로드할 때 이 파티션이 필요합니다."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1337,7 +1409,7 @@ msgstr ""
 "라, 하드 디스크로 설치 시스템을 부팅할 때 여러 가지 프로그램을 사용합니다."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1347,7 +1419,7 @@ msgstr ""
 "치 프로그램 부팅"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1358,7 +1430,7 @@ msgstr ""
 "합니다."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1370,7 +1442,7 @@ msgstr ""
 "수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1382,19 +1454,19 @@ msgstr ""
 "<filename>/boot/newinstall/</filename> 등입니다."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (커널 바이너리)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (램디스크 이미지)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1404,7 +1476,7 @@ msgstr ""
 "행하십시오."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
@@ -1412,7 +1484,7 @@ msgstr ""
 "기"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1422,7 +1494,7 @@ msgstr ""
 "작하도록 하드 디스크를 준비하는 방법을 설명합니다."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1432,7 +1504,7 @@ msgstr ""
 "오."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1440,19 +1512,19 @@ msgstr ""
 "<filename>/&x86-install-dir;</filename>커널 바이너리와 RAM 디스크 이미지)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (loadlin 도구)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "올드월드 맥에서 하드 디스크 설치 프로그램 부팅"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1475,7 +1547,7 @@ msgstr ""
 "는 <application>BootX</application>이 필요합니다."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1502,13 +1574,13 @@ msgstr ""
 "filename> 폴더를 활성화한 System Folder에 놓으십시오."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "뉴월드 맥에서 하드 디스크 설치 프로그램 부팅"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1528,7 +1600,7 @@ msgstr ""
 "지원하지 않고 뉴월드 파워맥에서는 사용해서는 안 됩니다."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1541,31 +1613,31 @@ msgstr ""
 "<keycap>option</keycap> 키를 누르고 하드 드라이브 아이콘으로 드래그합니다)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1580,7 +1652,7 @@ msgstr ""
 "프트에서 설치 프로그램을 부팅하는 명령에서 사용합니다."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1588,13 +1660,13 @@ msgstr ""
 "진행하십시오."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "TFTP 네트워크 부팅에 필요한 파일 준비하기"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1609,7 +1681,7 @@ msgstr ""
 "니다."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1621,7 +1693,7 @@ msgstr ""
 "\"supports-bootp\">, 아니면 BOOTP 서버</phrase>를 설정해야 합니다."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1641,7 +1713,7 @@ msgstr ""
 "장 기능입니다. 일부 시스템은 DHCP를 이용해야만 설정할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1653,7 +1725,7 @@ msgstr ""
 "다."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1663,7 +1735,7 @@ msgstr ""
 "합니다. &debian;은 <classname>rbootd</classname> 패키지가 포함되어 있습니다."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1677,7 +1749,7 @@ msgstr ""
 "서 사용하는 명령을 예로 듭니다."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1691,13 +1763,13 @@ msgstr ""
 "classname>입니다."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "RARP 서버 준비하기"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1716,7 +1788,7 @@ msgstr ""
 "시오."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1739,13 +1811,13 @@ msgstr ""
 "는 <userinput>/usr/etc/rarpd -a</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "DHCP 서버 준비하기"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1759,7 +1831,7 @@ msgstr ""
 "filename> 파일을 보십시오):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1803,7 +1875,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1820,7 +1892,7 @@ msgstr ""
 "다."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1831,13 +1903,13 @@ msgstr ""
 "작하십시오."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "DHCP 설정에서 PXE 부팅하게 만들기"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -1907,13 +1979,13 @@ msgstr ""
 "linkend=\"tftp-images\"/> 부분 참고)"
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "BOOTP 서버 준비하기"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -1928,7 +2000,7 @@ msgstr ""
 "server</classname>라는 패키지로 포함되어 있습니다."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -1990,7 +2062,7 @@ msgstr ""
 "<userinput>eaddr</userinput> 변수가 컴퓨터의 MAC 주소입니다. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2012,13 +2084,13 @@ msgstr ""
 "명령으로 <command>dhcpd</command>를 다시 시작하면 됩니다."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "TFTP 서버 사용하기"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2028,7 +2100,7 @@ msgstr ""
 "지 확인해야 합니다."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2043,7 +2115,7 @@ msgstr ""
 "법 중에 어떤 패키지를 다시 구성하여 설치할 때 사용되며 변경할 수 있습니다."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2061,7 +2133,7 @@ msgstr ""
 "제에서는 이 점을 고려해서 적용하십시오."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2077,7 +2149,7 @@ msgstr ""
 "확인하는 것이 좋습니다."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2106,13 +2178,13 @@ msgstr ""
 "를 조정하십시오."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "TFTP 이미지를 적당한 위치에 놓기"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2128,7 +2200,7 @@ msgstr ""
 "클라이언트가 결정하고, 어떤 표준도 없습니다."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2143,13 +2215,13 @@ msgstr ""
 "을 다운로드해야 합니다:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2165,7 +2237,7 @@ msgstr ""
 "오."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2181,13 +2253,13 @@ msgstr ""
 "DHCP 서버에 설정하십시오."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "SPARC TFTP 부팅"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2217,7 +2289,7 @@ msgstr ""
 "니다."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2230,7 +2302,7 @@ msgstr ""
 "고 어떤 이미지 이름을 요청했는 지 확인하십시오."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2243,13 +2315,13 @@ msgstr ""
 "userinput>. 파일은 TFTP 서버가 찾는 디렉터리 안에 들어 있어야 합니다."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI TFTP 부팅"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2263,13 +2335,13 @@ msgstr ""
 "<userinput>filename=</userinput> 옵션으로 지정합니다."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "자동 설치"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2284,13 +2356,13 @@ msgstr ""
 "project.org\">FAI 홈페이지</ulink>를 참조하십시오."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "&debian; 설치 프로그램을 이용한 자동 설치"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2303,7 +2375,7 @@ msgstr ""
 "에 질문에 대한 답변을 묻어가는 데 사용됩니다."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/nl/administrivia.po b/po/nl/administrivia.po
index 29c5f204a..164f2ad70 100644
--- a/po/nl/administrivia.po
+++ b/po/nl/administrivia.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,44 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:11
 #, no-c-format
-msgid "This manual was created for Sarge's debian-installer, based on the Woody installation manual for boot-floppies, which was based on earlier Debian installation manuals, and on the Progeny distribution manual which was released under GPL in 2003."
+msgid ""
+"This manual was created for Sarge's debian-installer, based on the Woody "
+"installation manual for boot-floppies, which was based on earlier Debian "
+"installation manuals, and on the Progeny distribution manual which was "
+"released under GPL in 2003."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:18
 #, no-c-format
-msgid "This document is written in DocBook XML. Output formats are generated by various programs using information from the <classname>docbook-xml</classname> and <classname>docbook-xsl</classname> packages."
+msgid ""
+"This document is written in DocBook XML. Output formats are generated by "
+"various programs using information from the <classname>docbook-xml</"
+"classname> and <classname>docbook-xsl</classname> packages."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:25
 #, no-c-format
-msgid "In order to increase the maintainability of this document, we use a number of XML features, such as entities and profiling attributes. These play a role akin to variables and conditionals in programming languages. The XML source to this document contains information for each different architecture &mdash; profiling attributes are used to isolate certain bits of text as architecture-specific."
+msgid ""
+"In order to increase the maintainability of this document, we use a number "
+"of XML features, such as entities and profiling attributes. These play a "
+"role akin to variables and conditionals in programming languages. The XML "
+"source to this document contains information for each different architecture "
+"&mdash; profiling attributes are used to isolate certain bits of text as "
+"architecture-specific."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:34
 #, no-c-format
-msgid "Translators can use this paragraph to acknowledge the people responsible for the translation of the manual. Translation teams are advised to just mention the coordinator and maybe major contributors and thank everybody else in a phrase like \"all translators and reviewers from the translation team for {your language} at {your l10n mailinglist}\". See build/lang-options/README on how to enable this paragraph. Its condition is \"about-langteam\"."
+msgid ""
+"Translators can use this paragraph to acknowledge the people responsible for "
+"the translation of the manual. Translation teams are advised to just mention "
+"the coordinator and maybe major contributors and thank everybody else in a "
+"phrase like \"all translators and reviewers from the translation team for "
+"{your language} at {your l10n mailinglist}\". See build/lang-options/README "
+"on how to enable this paragraph. Its condition is \"about-langteam\"."
 msgstr ""
 
 #. Tag: title
@@ -58,19 +78,46 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:52
 #, no-c-format
-msgid "If you have problems or suggestions regarding this document, you should probably submit them as a bug report against the package <classname>installation-guide</classname>. See the <classname>reportbug</classname> package or read the online documentation of the <ulink url=\"&url-bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could check the <ulink url=\"&url-bts;installation-guide\">open bugs against installation-guide</ulink> to see whether your problem has already been reported. If so, you can supply additional corroboration or helpful information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, where <replaceable>XXXX</replaceable> is the number for the already-reported bug."
+msgid ""
+"If you have problems or suggestions regarding this document, you should "
+"probably submit them as a bug report against the package "
+"<classname>installation-guide</classname>. See the <classname>reportbug</"
+"classname> package or read the online documentation of the <ulink url=\"&url-"
+"bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could "
+"check the <ulink url=\"&url-bts;installation-guide\">open bugs against "
+"installation-guide</ulink> to see whether your problem has already been "
+"reported. If so, you can supply additional corroboration or helpful "
+"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</"
+"email>, where <replaceable>XXXX</replaceable> is the number for the already-"
+"reported bug."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:68
 #, no-c-format
-msgid "Better yet, get a copy of the DocBook source for this document, and produce patches against it. The DocBook source can be found at the <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with DocBook, don't worry: there is a simple cheatsheet in the manuals directory that will get you started. It's like html, but oriented towards the meaning of the text rather than the presentation. Patches submitted to the debian-boot mailing list (see below) are welcomed. For instructions on how to check out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> from the source root directory."
+msgid ""
+"Better yet, get a copy of the DocBook source for this document, and produce "
+"patches against it. The DocBook source can be found at the <ulink url=\"&url-"
+"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with "
+"DocBook, don't worry: there is a simple cheatsheet in the manuals directory "
+"that will get you started. It's like html, but oriented towards the meaning "
+"of the text rather than the presentation. Patches submitted to the debian-"
+"boot mailing list (see below) are welcomed. For instructions on how to check "
+"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> "
+"from the source root directory."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:82
 #, no-c-format
-msgid "Please do <emphasis>not</emphasis> contact the authors of this document directly. There is also a discussion list for &d-i;, which includes discussions of this manual. The mailing list is <email>debian-boot@lists.debian.org</email>. Instructions for subscribing to this list can be found at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online."
+msgid ""
+"Please do <emphasis>not</emphasis> contact the authors of this document "
+"directly. There is also a discussion list for &d-i;, which includes "
+"discussions of this manual. The mailing list is <email>debian-boot@lists."
+"debian.org</email>. Instructions for subscribing to this list can be found "
+"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List "
+"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-"
+"list-archives;\">Debian Mailing List Archives</ulink> online."
 msgstr ""
 
 #. Tag: title
@@ -82,37 +129,62 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:101
 #, no-c-format
-msgid "This document was originally written by Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the Installation Howto."
+msgid ""
+"This document was originally written by Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the "
+"Installation Howto."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:107
 #, no-c-format
-msgid "Miroslav Kuře has documented a lot of the new functionality in Sarge's debian-installer. Frans Pop was the main editor and release manager during the Etch, Lenny and Squeeze releases."
+msgid ""
+"Miroslav Kuře has documented a lot of the new functionality in Sarge's "
+"debian-installer. Frans Pop was the main editor and release manager during "
+"the Etch, Lenny and Squeeze releases."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:113
 #, no-c-format
-msgid "Many, many Debian users and developers contributed to this document. Particular note must be made of Michael Schmitz (m68k support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. We have to thank Pascal Le Bail for useful information about booting from USB memory sticks."
+msgid ""
+"Many, many Debian users and developers contributed to this document. "
+"Particular note must be made of Michael Schmitz (m68k support), Frank "
+"Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;"
+"\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins "
+"(SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous "
+"edits and text. We have to thank Pascal Le Bail for useful information about "
+"booting from USB memory sticks."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:124
 #, no-c-format
-msgid "Extremely helpful text and information was found in Jim Mintha's HOWTO for network booting (no URL available), the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, amongst others. The maintainers of these freely available and rich sources of information must be recognized."
+msgid ""
+"Extremely helpful text and information was found in Jim Mintha's HOWTO for "
+"network booting (no URL available), the <ulink url=\"&url-debian-faq;"
+"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors "
+"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, "
+"amongst others. The maintainers of these freely available and rich sources "
+"of information must be recognized."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:136
 #, no-c-format
-msgid "The section on chrooted installations in this manual (<xref linkend=\"linux-upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
+msgid ""
+"The section on chrooted installations in this manual (<xref linkend=\"linux-"
+"upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:142
 #, no-c-format
-msgid "The section on installations over plip in this manual (<xref linkend=\"plip\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> by Gilles Lamiral."
+msgid ""
+"The section on installations over plip in this manual (<xref linkend=\"plip"
+"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> by Gilles Lamiral."
 msgstr ""
 
 #. Tag: title
@@ -126,4 +198,3 @@ msgstr ""
 #, no-c-format
 msgid "All trademarks are property of their respective trademark owners."
 msgstr ""
-
diff --git a/po/nl/boot-installer.po b/po/nl/boot-installer.po
index 26928271b..9daaf7e68 100644
--- a/po/nl/boot-installer.po
+++ b/po/nl/boot-installer.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,21 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:15
 #, no-c-format
-msgid "If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly shut down <emphasis>before</emphasis> you boot the installer. Installing an operating system while another operating system is in hibernation (has been suspended to disk) could result in loss of, or damage to the state of the suspended operating system which could cause problems when it is rebooted."
+msgid ""
+"If you have any other operating systems on your system that you wish to keep "
+"(dual boot setup), you should make sure that they have been properly shut "
+"down <emphasis>before</emphasis> you boot the installer. Installing an "
+"operating system while another operating system is in hibernation (has been "
+"suspended to disk) could result in loss of, or damage to the state of the "
+"suspended operating system which could cause problems when it is rebooted."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:26
 #, no-c-format
-msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For information on how to boot the graphical installer, see <xref linkend="
+"\"graphical\"/>."
 msgstr ""
 
 #. Tag: title
@@ -44,21 +53,30 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
-msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
+msgid ""
+"Booting from the network requires that you have a network connection and a "
+"TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
-msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
+msgid ""
+"Older systems such as the 715 might require the use of an RBOOT server "
+"instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
-msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The installation method to support network booting is described in <xref "
+"linkend=\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -68,27 +86,47 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
-msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
+msgid ""
+"The easiest route for most people will be to use a set of &debian; CDs. If "
+"you have a CD set, and if your machine supports booting directly off the CD, "
+"great! Simply <phrase arch=\"x86\"> configure your system for booting off a "
+"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
+"your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
-msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
+msgid ""
+"Note that certain CD drives may require special drivers, and thus be "
+"inaccessible in the early installation stages. If it turns out the standard "
+"way of booting off a CD doesn't work for your hardware, revisit this chapter "
+"and read about alternate kernels and installation methods which may work for "
+"you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
-msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
+msgid ""
+"Even if you cannot boot from CD-ROM, you can probably install the &debian; "
+"system components and any packages you want from CD-ROM. Simply boot using a "
+"different media, such as floppies. When it's time to install the operating "
+"system, base system, and any additional packages, point the installation "
+"system at the CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
-msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
@@ -100,13 +138,20 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:113
 #, no-c-format
-msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines."
+msgid ""
+"There is an increasing number of consumer devices that directly boot from a "
+"flash chip on the device. The installer can be written to flash so it will "
+"automatically start when you reboot your machines."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:119
 #, no-c-format
-msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely."
+msgid ""
+"In many cases, changing the firmware of an embedded device voids your "
+"warranty. Sometimes you are also not able to recover your device if there "
+"are problems during the flashing process. Therefore, please take care and "
+"follow the steps precisely."
 msgstr ""
 
 #. Tag: title
@@ -118,13 +163,28 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:132
 #, no-c-format
-msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>."
+msgid ""
+"Due to limitations in the SS4000-E firmware, it unfortunately is not "
+"possible to boot the installer without the use of a serial port at this "
+"time. To boot the installer, you will need a serial nullmodem cable; a "
+"computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB "
+"serial converter will also work. </para> </footnote>; and a ribbon cable "
+"with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the "
+"other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older "
+"desktop machines with builtin 9-pin serial ports. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:153
 #, no-c-format
-msgid "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a &debian; GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:"
+msgid ""
+"To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable "
+"to connect to the serial port of the SS4000-E, and reboot the machine. You "
+"need to use a serial terminal application to communicate with the machine; a "
+"good option on a &debian; GNU/Linux is to use the <command>cu</command> "
+"program, in the package of the same name. Assuming the serial port on your "
+"computer is to be found on <filename>/dev/ttyS0</filename>, use the "
+"following command line:"
 msgstr ""
 
 #. Tag: screen
@@ -136,7 +196,10 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:167
 #, no-c-format
-msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit."
+msgid ""
+"If using Windows, you may want to consider using the program "
+"<classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word "
+"length, no stop bits, and one parity bit."
 msgstr ""
 
 #. Tag: para
@@ -149,63 +212,86 @@ msgstr ""
 #: boot-installer.xml:179
 #, no-c-format
 msgid ""
-      "No network interfaces found\n"
-      "\n"
-      "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
-      "== Executing boot script in 1.000 seconds - enter ^C to abort"
+"No network interfaces found\n"
+"\n"
+"EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
+"== Executing boot script in 1.000 seconds - enter ^C to abort"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:181
 #, no-c-format
-msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following commands:"
+msgid ""
+"At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-"
+"s4ke-sec\"> <para> Note that you have only one second to do so; if you miss "
+"this window, just powercycle the machine and try again. </para> </footnote>. "
+"This will give you the RedBoot prompt. Enter the following commands:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:194
 #, no-c-format
 msgid ""
-      "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
-      "load -v -r -b 0x01008000 -m ymodem zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
+"load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
+"load -v -r -b 0x01008000 -m ymodem zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:196
 #, no-c-format
-msgid "After every <command>load</command> command, the system will expect a file to be transmitted using the YMODEM protocol. When using cu, make sure you have the package <classname>lrzsz</classname> installed, then hit enter, followed by the <quote>~&lt;</quote> escape sequence to start an external program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</command>."
+msgid ""
+"After every <command>load</command> command, the system will expect a file "
+"to be transmitted using the YMODEM protocol. When using cu, make sure you "
+"have the package <classname>lrzsz</classname> installed, then hit enter, "
+"followed by the <quote>~&lt;</quote> escape sequence to start an external "
+"program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:205
 #, no-c-format
-msgid "Alternatively, it is possible to load the kernel and ramdisk using HTTP rather than YMODEM. This is faster, but requires a working HTTP server on the network. To do so, first switch the bootloader to RAM mode:"
+msgid ""
+"Alternatively, it is possible to load the kernel and ramdisk using HTTP "
+"rather than YMODEM. This is faster, but requires a working HTTP server on "
+"the network. To do so, first switch the bootloader to RAM mode:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:211
 #, no-c-format
 msgid ""
-      "fis load rammode\n"
-      "g"
+"fis load rammode\n"
+"g"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:213
 #, no-c-format
-msgid "This will seemingly restart the machine; but in reality, it loads redboot to RAM and restarts it from there. Not doing this step will cause the system to hang in the necessary ip_address step that comes next."
+msgid ""
+"This will seemingly restart the machine; but in reality, it loads redboot to "
+"RAM and restarts it from there. Not doing this step will cause the system to "
+"hang in the necessary ip_address step that comes next."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:219
 #, no-c-format
 msgid ""
-      "You will need to hit Ctrl-C again to interrupt the boot. Then: <informalexample><screen>\n"
-      "ip_address -l <replaceable>192.168.2.249</replaceable> -h <replaceable>192.168.2.4</replaceable>\n"
-      "load -v -r -b 0x01800000 -m http /initrd.gz\n"
-      "load -v -r -b 0x01008000 -m http /zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000\n"
-      "</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> is the IP address of the installed system and <replaceable>192.168.2.4</replaceable> the IP address of the HTTP server containing the kernel and ramdisk files."
+"You will need to hit Ctrl-C again to interrupt the boot. Then: "
+"<informalexample><screen>\n"
+"ip_address -l <replaceable>192.168.2.249</replaceable> -h "
+"<replaceable>192.168.2.4</replaceable>\n"
+"load -v -r -b 0x01800000 -m http /initrd.gz\n"
+"load -v -r -b 0x01008000 -m http /zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000\n"
+"</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> "
+"is the IP address of the installed system and <replaceable>192.168.2.4</"
+"replaceable> the IP address of the HTTP server containing the kernel and "
+"ramdisk files."
 msgstr ""
 
 #. Tag: para
@@ -215,7 +301,8 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -235,2042 +322,3004 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:355
 #, no-c-format
-msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+msgid ""
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
-msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
+msgid ""
+"download a standalone Windows executable, which is available as tools/win32-"
+"loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
-msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
+msgid ""
+"If you use an installation CD or DVD, a pre-installation program should be "
+"launched automatically when you insert the disc. In case Windows does not "
+"start it automatically, or if you are using a USB memory stick, you can run "
+"it manually by accessing the device and executing <command>setup.exe</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
-msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
+msgid ""
+"After the program has been started, a few preliminary questions will be "
+"asked and the system will be prepared to reboot into the &debian-gnu; "
+"installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
-msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
+msgid ""
+"Boot into DOS (not Windows). To do this, you can for instance boot from a "
+"recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
-      "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
-      "d:\n"
-      "</screen></informalexample> else make sure you have first prepared your hard disk as explained in <xref linkend=\"files-loadlin\"/>, and change the current drive to it if needed."
+"If you can access the installation CD, change the current drive to the CD-"
+"ROM drive, e.g. <informalexample><screen>\n"
+"d:\n"
+"</screen></informalexample> else make sure you have first prepared your hard "
+"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the "
+"current drive to it if needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
-      "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
-      "cd \\&x86-install-dir;\n"
-      "</screen></informalexample> If you prefer using the graphical installer, enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
-      "cd gtk\n"
-      "</screen></informalexample> Next, execute <command>install.bat</command>. The kernel will load and launch the installer system."
+"Enter the subdirectory for the flavor you chose, e.g., "
+"<informalexample><screen>\n"
+"cd \\&x86-install-dir;\n"
+"</screen></informalexample> If you prefer using the graphical installer, "
+"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
+"cd gtk\n"
+"</screen></informalexample> Next, execute <command>install.bat</command>. "
+"The kernel will load and launch the installer system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
-msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
-msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you must first download and place the "
+"needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
-msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
+msgid ""
+"If you intend to use the hard drive only for booting and then download "
+"everything over the network, you should download the <filename>netboot/"
+"debian-installer/&architecture;/initrd.gz</filename> file and its "
+"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
+"linux</filename>. This will allow you to repartition the hard disk from "
+"which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
-msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
+msgid ""
+"Alternatively, if you intend to keep an existing partition on the hard drive "
+"unchanged during the install, you can download the <filename>hd-media/initrd."
+"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
+"drive (make sure the file is named ending in <literal>.iso</literal>). The "
+"installer can then boot from the drive and install from the CD/DVD image, "
+"without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
-msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
+msgid ""
+"For <command>LILO</command>, you will need to configure two essential things "
+"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
+"load the <filename>initrd.gz</filename> installer at boot time; </para></"
+"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
+"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
+"a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
-      "image=/boot/newinstall/vmlinuz\n"
-      "       label=newinstall\n"
-      "       initrd=/boot/newinstall/initrd.gz"
+"image=/boot/newinstall/vmlinuz\n"
+"       label=newinstall\n"
+"       initrd=/boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
-msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
+msgid ""
+"For more details, refer to the <citerefentry><refentrytitle>initrd</"
+"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
+"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
+"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
+"reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
-msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
+msgid ""
+"The procedure for <command>GRUB1</command> is quite similar. Locate your "
+"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
+"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
+"entry for the installer, for example (assuming <filename>/boot</filename> is "
+"on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
-      "title  New Install\n"
-      "root   (hd0,0)\n"
-      "kernel /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz"
+"title  New Install\n"
+"root   (hd0,0)\n"
+"kernel /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
-msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
+msgid ""
+"The procedure for <command>GRUB2</command> is very similar. The file is "
+"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
+"filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
-      "menuentry 'New Install' {\n"
-      "insmod part_msdos\n"
-      "insmod ext2\n"
-      "set root='(hd0,msdos1)'\n"
-      "linux /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz\n"
-      "}"
+"menuentry 'New Install' {\n"
+"insmod part_msdos\n"
+"insmod ext2\n"
+"set root='(hd0,msdos1)'\n"
+"linux /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz\n"
+"}"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
-msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
+msgid ""
+"From here on, there should be no difference between <command>GRUB</command> "
+"or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
-msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
+"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
+"stick into some free USB connector and reboot the computer. The system "
+"should boot up, and unless you have used the flexible way to build the stick "
+"and not enabled it, you should be presented with the <prompt>boot:</prompt> "
+"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
-msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
+msgid ""
+"You will have already downloaded the floppy images you needed and created "
+"floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
-msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
+msgid ""
+"To boot from the installer boot floppy, place it in the primary floppy "
+"drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
-msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
+msgid ""
+"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
+"you need to specify the virtual location for the floppy device. This is done "
+"with the <emphasis>root=</emphasis> boot argument, giving the device that "
+"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
+"is connected as the first IDE device (master) on the second cable, you enter "
+"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
-msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
+msgid ""
+"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
+"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
+"machine, so a <quote>hard</quote> reboot is recommended. If you are "
+"installing from an existing operating system (e.g., from a DOS box) you "
+"don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
-msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
+msgid ""
+"The floppy disk will be accessed, and you should then see a screen that "
+"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
-msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
+msgid ""
+"Once you press &enterkey;, you should see the message "
+"<computeroutput>Loading...</computeroutput>, followed by "
+"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
+"screenfull or so of information about the hardware in your system. More "
+"information on this phase of the boot process can be found below in <xref "
+"linkend=\"kernel-msgs\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
-msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
+msgid ""
+"After booting from the boot floppy, the root floppy is requested. Insert the "
+"root floppy and press &enterkey;, and the contents are loaded into memory. "
+"The installer program <command>debian-installer</command> is automatically "
+"launched."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
-msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
+msgid ""
+"It could be that your Network Interface Card or Motherboard provides PXE "
+"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
+"re-implementation of TFTP boot. If so, you may be able to configure your "
+"BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
-msgid "It could be that your Network Interface Card provides TFTP boot functionality."
+msgid ""
+"It could be that your Network Interface Card provides TFTP boot "
+"functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
-msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
+msgid ""
+"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
+"Please refer to this document."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
-msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
+msgid ""
+"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
+"provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
-      "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
-      "Installer boot menu\n"
-      "\n"
-      "Install\n"
-      "Graphical install\n"
-      "Advanced options             >\n"
-      "Help\n"
-      "Install with speech synthesis\n"
-      "\n"
-      "Press ENTER to boot or TAB to edit a menu entry\n"
-      "</screen></informalexample> Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:658
+"When the installer boots, you should be presented with a friendly graphical "
+"screen showing the &debian; logo and a menu: <informalexample><screen>\n"
+"Installer boot menu\n"
+"\n"
+"Install\n"
+"Graphical install\n"
+"Advanced options             >\n"
+"Help\n"
+"Install with speech synthesis\n"
+"\n"
+"Press ENTER to boot or TAB to edit a menu entry\n"
+"</screen></informalexample> Depending on the installation method you are "
+"using, the <quote>Graphical install</quote> option may not be available. Bi-"
+"arch images additionally have a 64 bit variant for each install option, "
+"right below it, thus almost doubling the number of options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:660
 #, no-c-format
-msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
+msgid ""
+"For a normal installation, select either the <quote>Install</quote> or the "
+"<quote>Graphical install</quote> entry &mdash; using either the arrow keys "
+"on your keyboard or by typing the first (highlighted) letter, the "
+"<quote>Install</quote> entry is already selected by default &mdash; and "
+"press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
-msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
+msgid ""
+"The <quote>Advanced options</quote> entry gives access to a second menu that "
+"allows to boot the installer in expert mode, in rescue mode and for "
+"automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
-msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
+msgid ""
+"If you wish or need to add any boot parameters for either the installer or "
+"the kernel, press &tabkey;. This will display the default boot command for "
+"the selected menu entry and allow to add additional options. The help "
+"screens (see below) list some common possible options. Press &enterkey; to "
+"boot the installer with your options; pressing &escapekey; will return you "
+"to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
-      "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
-      "Press F1 for the help index, or ENTER to boot:\n"
-      "</screen></informalexample> At this boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot command and, optionally, boot parameters. A number of boot parameters which might be useful can be found on the various help screens. If you do add any parameters to the boot command line, be sure to first type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)."
+"Choosing the <quote>Help</quote> entry will result in the first help screen "
+"being displayed which gives an overview of all available help screens. To "
+"return to the boot menu after the help screens have been displayed, type "
+"'menu' at the boot prompt and press &enterkey;. All help screens have a boot "
+"prompt at which the boot command can be typed: <informalexample><screen>\n"
+"Press F1 for the help index, or ENTER to boot:\n"
+"</screen></informalexample> At this boot prompt you can either just press "
+"&enterkey; to boot the installer with default options or enter a specific "
+"boot command and, optionally, boot parameters. A number of boot parameters "
+"which might be useful can be found on the various help screens. If you do "
+"add any parameters to the boot command line, be sure to first type the boot "
+"method (the default is <userinput>install</userinput>) and a space before "
+"the first parameter (e.g., <userinput>install fb=false</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
-msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
+msgid ""
+"The keyboard is assumed to have a default American English layout at this "
+"point. This means that if your keyboard has a different (language-specific) "
+"layout, the characters that appear on the screen may be different from what "
+"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-"
+"keymap;\">schema of the US keyboard layout</ulink> which can be used as a "
+"reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
-msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
+msgid ""
+"If you are using a system that has the BIOS configured to use serial "
+"console, you may not be able to see the initial graphical splash screen upon "
+"booting the installer; you may even not see the boot menu. The same can "
+"happen if you are installing the system via a remote management device that "
+"provides a text interface to the VGA console. Examples of these devices "
+"include the text console of Compaq's <quote>integrated Lights Out</quote> "
+"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
-msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
+msgid ""
+"To bypass the graphical boot screen you can either blindly press &escapekey; "
+"to get a text boot prompt, or (equally blindly) press <quote>H</quote> "
+"followed by &enterkey; to select the <quote>Help</quote> option described "
+"above. After that your keystrokes should be echoed at the prompt. To prevent "
+"the installer from using the framebuffer for the rest of the installation, "
+"you will also want to add <userinput>vga=normal fb=false</userinput> to the "
+"boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
-msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network."
+msgid ""
+"There are three basic variations of &debian; Install CDs. The "
+"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
+"fit on the small form factor CD media. It requires a network connection in "
+"order to install the rest of the base installation and make a usable system. "
+"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
+"base install but requires a network connection to a &debian; mirror site in "
+"order to install the extra packages one would want for a complete system . "
+"The set of &debian; CDs can install a complete system from the wide range of "
+"packages without needing access to the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
-msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
+msgid ""
+"The IA-64 architecture uses the next generation Extensible Firmware "
+"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows "
+"little about the boot device other than the partition table and Master Boot "
+"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted "
+"disk partitions. This simplifies the often arcane process of starting a "
+"system. The system boot loader and the EFI firmware that supports it have a "
+"full filesystem to store the files necessary for booting the machine. This "
+"means that the system disk on an IA-64 system has an additional disk "
+"partition dedicated to EFI instead of the simple MBR or boot block on more "
+"conventional systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
-msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
+msgid ""
+"The &debian; Installer CD contains a small EFI partition where the "
+"<command>ELILO</command> bootloader, its configuration file, the installer's "
+"kernel, and initial filesystem (initrd) are located. The running system also "
+"contains an EFI partition where the necessary files for booting the system "
+"reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
-msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
+msgid ""
+"Most of the details of how <command>ELILO</command> actually loads and "
+"starts a system are transparent to the system installer. However, the "
+"installer must set up an EFI partition prior to installing the base system. "
+"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
+"the system un-bootable. The EFI partition is allocated and formatted in the "
+"partitioning step of the installation prior to loading any packages on the "
+"system disk. The partitioning task also verifies that a suitable EFI "
+"partition is present before allowing the installation to proceed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
-msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
+msgid ""
+"The EFI Boot Manager is presented as the last step of the firmware "
+"initialization. It displays a menu list from which the user can select an "
+"option. Depending on the model of system and what other software has been "
+"loaded on the system, this menu may be different from one system to another. "
+"There should be at least two menu items displayed, <command>Boot Option "
+"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
+"Using the first option is preferred, however, if that option is not "
+"available or the CD for some reason does not boot with it, use the second "
+"option."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
-msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
+msgid ""
+"The EFI Boot Manager will select a default boot action, typically the first "
+"menu choice, within a pre-set number of seconds. This is indicated by a "
+"countdown at the bottom of the screen. Once the timer expires and the "
+"systems starts the default action, you may have to reboot the machine in "
+"order to continue the installation. If the default action is the EFI Shell, "
+"you can return to the Boot Manager by running <command>exit</command> at the "
+"shell prompt."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes its system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
-msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
+msgid ""
+"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
+"keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
-msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
+msgid ""
+"Select <command>Boot From a File</command> from the menu with the arrow keys "
+"and press <command>ENTER</command>. This will display a list of devices "
+"probed by the firmware. You should see two menu lines containing either the "
+"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
+"Boot</command>. If you examine the rest of the menu line, you will notice "
+"that the device and controller information should be the same."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
-msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
+msgid ""
+"You can choose either of the entries that refer to the CD/DVD drive. Select "
+"your choice with the arrow keys and press <command>ENTER</command>. If you "
+"choose <command>Removable Media Boot</command> the machine will immediately "
+"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
+"command> instead, it will display a directory listing of the bootable "
+"portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
-msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
+"command>. The directory listing will also show <command>[Treat like "
+"Removable Media Boot]</command> on the next to the last line. Select this "
+"line with the arrow keys and press <command>ENTER</command>. This will start "
+"the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
-msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
+msgid ""
+"These steps start the &debian; boot loader which will display a menu page "
+"for you to select a boot kernel and options. Proceed to selecting the boot "
+"kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
-msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:"
+msgid ""
+"If, for some reason, option 1 is not successful, reboot the machine and when "
+"the EFI Boot Manager screen appears there should be one option called "
+"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with "
+"the following steps:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
-msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
+msgid ""
+"Select <command>EFI Shell</command> from the menu with the arrow keys and "
+"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
+"devices and display them to the console before displaying its command "
+"prompt. The recognized bootable partitions on devices will show a device "
+"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
+"recognized partitions will be named <filename>blk<replaceable>n</"
+"replaceable>:</filename>. If you inserted the CD just before entering the "
+"shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
-msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
+msgid ""
+"Examine the output from the shell looking for the CDROM drive. It is most "
+"likely the <filename>fs0:</filename> device although other devices with "
+"bootable partitions will also show up as <filename>fs<replaceable>n</"
+"replaceable></filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
-msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
+msgid ""
+"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
+"<command>ENTER</command> to select that device where <replaceable>n</"
+"replaceable> is the partition number for the CDROM. The shell will now "
+"display the partition number as its prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
-msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
+"start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
-msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
+msgid ""
+"As with option 1, these steps start the &debian; boot loader which will "
+"display a menu page for you to select a boot kernel and options. You can "
+"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
+"command> command at the shell prompt. Proceed to selecting the boot kernel "
+"and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
-msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
+msgid ""
+"You may choose to perform an install using a monitor and keyboard or using a "
+"serial connection. To use a monitor/keyboard setup, select an option "
+"containing the string [VGA console]. To install over a serial connection, "
+"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
+"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
+"serial console. Menu items for the most typical baud rate settings on the "
+"ttyS0 device are preconfigured."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
-msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
+msgid ""
+"In most circumstances, you will want the installer to use the same baud rate "
+"as your connection to the EFI console. If you aren't sure what this setting "
+"is, you can obtain it using the command <command>baud</command> at the EFI "
+"shell."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
-msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
+msgid ""
+"If there is not an option available that is configured for the serial device "
+"or baud rate you would like to use, you may override the console setting for "
+"one of the existing menu options. For example, to use a 57600 baud console "
+"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
+"the <classname>Boot:</classname> text window."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
-msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
+msgid ""
+"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
+"setting is rather slow, and the normal installation process will take a "
+"significant time to draw each screen. You should consider either increasing "
+"the baud rate used for performing the installation, or performing a Text "
+"Mode installation. See the <classname>Params</classname> help menu for "
+"instructions on starting the installer in Text Mode."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
-msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
+msgid ""
+"If you select the wrong console type, you will be able to select the kernel "
+"and enter parameters but both the display and your input will go dead as "
+"soon as the kernel starts, requiring you to reboot before you can begin the "
+"installation."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
-msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
+msgid ""
+"The boot loader will display a form with a menu list and a text window with "
+"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
+"the menu and any text typed at the keyboard will appear in the text window. "
+"There are also help screens which can be displayed by pressing the "
+"appropriate function key. The <classname>General</classname> help screen "
+"explains the menu choices and the <classname>Params</classname> screen "
+"explains the common command line options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
-msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
+msgid ""
+"Consult the <classname>General</classname> help screen for the description "
+"of the kernels and install modes most appropriate for your installation. You "
+"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
+"parameters that you may want to set in the <classname>Boot:</classname> text "
+"window. The kernel version you choose selects the kernel version that will "
+"be used for both the installation process and the installed system. If you "
+"encounter kernel problems with the installation, you may also have those "
+"same problems with the system you install. The following two steps will "
+"select and start the install:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
-msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
+msgid ""
+"Select the kernel version and installation mode most appropriate to your "
+"needs with the arrow keys."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
-msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
+msgid ""
+"Enter any boot parameters by typing at the keyboard. The text will be "
+"displayed directly in the text window. This is where kernel parameters (such "
+"as serial console settings) are specified."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
-msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer."
+msgid ""
+"Press <command>ENTER</command>. This will load and start the kernel. The "
+"kernel will display its usual initialization messages followed by the first "
+"screen of the &debian; Installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
-msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
+msgid ""
+"Proceed to the next chapter to continue the installation where you will set "
+"up the language locale, network, and disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
-msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
+msgid ""
+"Booting an IA-64 system from the network is similar to a CD boot. The only "
+"difference is how the installation kernel is loaded. The EFI Boot Manager "
+"can load and start programs from a server on the network. Once the "
+"installation kernel is loaded and starts, the system install will proceed "
+"through the same steps as the CD install with the exception that the "
+"packages of the base install will be loaded from the network rather than the "
+"CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
-msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
+msgid ""
+"Network booting an IA-64 system requires two architecture-specific actions. "
+"On the boot server, DHCP and TFTP must be configured to deliver "
+"<command>elilo</command>. On the client a new boot option must be defined in "
+"the EFI boot manager to enable loading over a network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
-      "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
-      "host mcmuffin {\n"
-      "        hardware ethernet 00:30:6e:1e:0e:83;\n"
-      "        fixed-address 10.0.0.21;\n"
-      "        filename \"debian-installer/ia64/elilo.efi\";\n"
-      "}\n"
-      "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
+"A suitable TFTP entry for network booting an IA-64 system looks something "
+"like this: <informalexample><screen>\n"
+"host mcmuffin {\n"
+"        hardware ethernet 00:30:6e:1e:0e:83;\n"
+"        fixed-address 10.0.0.21;\n"
+"        filename \"debian-installer/ia64/elilo.efi\";\n"
+"}\n"
+"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
+"command> running on the client."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
-msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
+msgid ""
+"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
+"as the root for your tftp server. Typical tftp root directories include "
+"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
+"will create a <filename>debian-installer</filename> directory tree "
+"containing the boot files for an IA-64 system."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
-      "# cd /var/lib/tftp\n"
-      "# tar xvfz /home/user/netboot.tar.gz\n"
-      "./\n"
-      "./debian-installer/\n"
-      "./debian-installer/ia64/\n"
-      "[...]"
+"# cd /var/lib/tftp\n"
+"# tar xvfz /home/user/netboot.tar.gz\n"
+"./\n"
+"./debian-installer/\n"
+"./debian-installer/ia64/\n"
+"[...]"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
-msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
+msgid ""
+"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
+"filename> file that should work for most configurations. However, should you "
+"need to make changes to this file, you can find it in the <filename>debian-"
+"installer/ia64/</filename> directory. It is possible to have different "
+"config files for different clients by naming them using the client's IP "
+"address in hex with the suffix <filename>.conf</filename> instead of "
+"<filename>elilo.conf</filename>. See documentation provided in the "
+"<classname>elilo</classname> package for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
-msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
+msgid ""
+"To configure the client to support TFTP booting, start by booting to EFI and "
+"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
+"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
+"should see one or more lines with the text <guimenuitem>Load File [Acpi"
+"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose "
+"the one containing the MAC address of the interface from which you'll be "
+"booting. Use the arrow keys to highlight your choice, then press enter. </"
+"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
+"userinput> or something similar, save, and exit back to the boot options "
+"menu. </para></listitem> </itemizedlist> You should see the new boot option "
+"you just created, and selecting it should initiate a DHCP query, leading to "
+"a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
-msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer."
+msgid ""
+"The boot loader will display its prompt after it has downloaded and "
+"processed its configuration file. At this point, the installation proceeds "
+"with the same steps as a CD install. Select a boot option as in above and "
+"when the kernel has completed installing itself from the network, it will "
+"start the &debian; Installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
-      "After entering the command monitor use <informalexample><screen>\n"
-      "bootp():\n"
-      "</screen></informalexample> on SGI machines to boot linux and to begin installation of the &debian; Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n"
-      "unsetenv netaddr\n"
-      "</screen></informalexample> in the command monitor to do this."
+"After entering the command monitor use <informalexample><screen>\n"
+"bootp():\n"
+"</screen></informalexample> on SGI machines to boot linux and to begin "
+"installation of the &debian; Software. In order to make this work you may "
+"have to unset the <envar>netaddr</envar> environment variable. Type "
+"<informalexample><screen>\n"
+"unsetenv netaddr\n"
+"</screen></informalexample> in the command monitor to do this."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
-msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
+msgid ""
+"On SGI machines you can append boot parameters to the <command>bootp():</"
+"command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
-      "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
-      "bootp():/boot/tftpboot.img\n"
-      "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
+"Following the <command>bootp():</command> command you can give the path and "
+"name of the file to boot if you did not give an explicit name via your bootp/"
+"dhcp server. Example: <informalexample><screen>\n"
+"bootp():/boot/tftpboot.img\n"
+"</screen></informalexample> Further kernel parameters can be passed via "
+"<command>append</command>:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
-msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
+msgid ""
+"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
+"install an NFS server and put the installer files in <filename>/nfsroot</"
+"filename>. When you boot your Cobalt, you have to press the left and the "
+"right cursor buttons at the same time and the machine will boot via the "
+"network from NFS. It will then display several options on the display. There "
+"are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
-msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
+msgid ""
+"Via SSH (default): In this case, the installer will configure the network "
+"via DHCP and start an SSH server. It will then display a random password and "
+"other login information (such as the IP address) on the Cobalt LCD. When you "
+"connect to the machine with an SSH client you can start with the "
+"installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
-msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
+msgid ""
+"Via serial console: Using a null modem cable, you can connect to the serial "
+"port of your Cobalt machine (using 115200 bps) and perform the installation "
+"this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
-msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
+msgid ""
+"You cannot pass any boot parameters directly. Instead, you have to edit the "
+"<filename>/nfsroot/default.colo</filename> file on the NFS server and add "
+"your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
-msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
+msgid ""
+"In order to run the installation system a working network setup and ssh "
+"session is needed on S/390."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
-msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
+msgid ""
+"The booting process starts with a network setup that prompts you for several "
+"network parameters. If the setup is successful, you will login to the system "
+"by starting an ssh session which will launch the standard installation "
+"system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
-msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
+msgid ""
+"On S/390 you can append boot parameters in the parm file. This file can "
+"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
+"debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
-msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive."
+msgid ""
+"Currently, the only &arch-title; subarchitectures that support CD-ROM "
+"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
+"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
+"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
+"and <keycap>Delete</keycap> keys together while booting to boot from the "
+"factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
-      "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
-      "0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
-      "</screen></informalexample> for an alternative way to boot from the internal factory default CD/DVD drive type"
+"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
+"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
+"type <informalexample><screen>\n"
+"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
+"</screen></informalexample> for an alternative way to boot from the internal "
+"factory default CD/DVD drive type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
-msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
+msgid ""
+"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
+"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
+"software version of this driver is not available. All OldWorld systems have "
+"floppy drives, so use the floppy drive to launch the installer, and then "
+"point the installer to the CD for the needed files."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
-msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
+msgid ""
+"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
+"immediately after pressing the power-on button, when SmartFirmware prompt "
+"appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
-msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
+msgid ""
+"Booting from an existing operating system is often a convenient option; for "
+"some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
-msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you will have already completed "
+"downloading and placing the needed files as described in <xref linkend="
+"\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
-msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
+msgid ""
+"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
+"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
+"application icon. Click on the <guibutton>Options</guibutton> button and "
+"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
+"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
+"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
+"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
+"down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
-      "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
-      "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
-      "</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n"
-      "boot:\n"
-      "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The &debian; installation program should start."
+"You will have already placed the <filename>vmlinux</filename>, "
+"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
+"<filename>yaboot.conf</filename> files at the root level of your HFS "
+"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
+"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
+"prompt, type <informalexample><screen>\n"
+"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
+"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
+"partition number of the HFS partition where the kernel and yaboot files were "
+"placed, followed by a &enterkey;. On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
+"more seconds you will see a yaboot prompt <informalexample><screen>\n"
+"boot:\n"
+"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
+"either <userinput>install</userinput> or <userinput>install video=ofonly</"
+"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
+"argument is for maximum compatibility; you can try it if <userinput>install</"
+"userinput> doesn't work. The &debian; installation program should start."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
-msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
+msgid ""
+"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
+">. To boot a Macintosh system from a USB stick, you will need to use the "
+"Open Firmware prompt, since Open Firmware does not search USB storage "
+"devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
-msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
+msgid ""
+"You will need to work out where the USB storage device appears in the device "
+"tree, since at the moment <command>ofpath</command> cannot work that out "
+"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
+"userinput> at the Open Firmware prompt to get a list of all known devices "
+"and device aliases. On the author's system with various types of USB stick, "
+"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
+"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
+"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
-      "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
-      "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n"
-      "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
+"Having worked out the device path, use a command like this to boot the "
+"installer: <informalexample><screen>\n"
+"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
+"tbxi\n"
+"</screen></informalexample> The <replaceable>2</replaceable> matches the "
+"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
+"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
+"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
+"<command>yaboot</command>) in the directory previously blessed with "
+"<command>hattrib -b</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
-msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"The system should now boot up, and you should be presented with the "
+"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
+"or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
-msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
+msgid ""
+"This boot method is new, and may be difficult to get to work on some "
+"NewWorld systems. If you have problems, please file an installation report, "
+"as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
-      "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
-      "0 &gt; boot enet:0\n"
-      "</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>\n"
-      "0 &gt; boot enet:0,yaboot\n"
-      "</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>\n"
-      "boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>\n"
-      "</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:1676
+"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
+"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
+"<informalexample><screen>\n"
+"0 &gt; boot enet:0\n"
+"</screen></informalexample> If this doesn't work, you might have to add the "
+"filename like this: <informalexample><screen>\n"
+"0 &gt; boot enet:0,yaboot\n"
+"</screen></informalexample> PReP and CHRP boxes may have different ways of "
+"addressing the network. On a PReP machine, you should try "
+"<informalexample><screen>\n"
+"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
+"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
+"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
+"machines) the command <userinput>help boot</userinput> may give a "
+"description of syntax and available options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:1678
 #, no-c-format
-msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
+msgid ""
+"Booting from floppies is supported for &arch-title;, although it is "
+"generally only applicable for OldWorld systems. NewWorld systems are not "
+"equipped with floppy drives, and attached USB floppy drives are not "
+"supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
-msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
+msgid ""
+"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
+"in floppy drive after shutting the system down, and before pressing the "
+"power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
-msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
+msgid ""
+"For those not familiar with Macintosh floppy operations: a floppy placed in "
+"the machine prior to boot will be the first priority for the system to boot "
+"from. A floppy without a valid boot system will be ejected, and the machine "
+"will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
-msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
+msgid ""
+"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
+"the root floppy and press &enterkey;. The installer program is automatically "
+"launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
-msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
+msgid ""
+"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
+"skewed on an older Apple monitor, try appending the boot argument "
+"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
+"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
+"<userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
-msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
+msgid ""
+"On machines with OpenBoot, simply enter the boot monitor on the machine "
+"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
+"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
+"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
+"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
+"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
-msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
+msgid ""
+"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
+"which is simply an alias to boot from the SCSI device on ID 6 (or the "
+"secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
-msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
+msgid ""
+"If you cannot boot because you get messages about a problem with "
+"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
+"holds configuration information for you firmware, has run out. See the "
+"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
+"information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
-msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
+msgid ""
+"Some users may need specific support because of e.g. some visual impairment. "
+"<phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected "
+"automatically (not serial displays connected via a serial-to-USB converter), "
+"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</"
+"phrase> accessibility features have to be enabled manually. <phrase arch="
+"\"x86\">On machines that support it, the boot menu emits a beep when it is "
+"ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch="
+"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
+"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that "
+"on most architectures the boot loader interprets your keyboard as a QWERTY "
+"keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
-msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"USB braille displays should be automatically detected. A textual version of "
+"the installer will then be automatically selected, and support for the "
+"braille display will be automatically installed on the target system. You "
+"can thus just press &enterkey; at the boot menu. Once <classname>brltty</"
+"classname> is started, you can choose a braille table by entering the "
+"preference menu. Documentation on key bindings for braille devices is "
+"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
+"classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
-msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"Serial braille displays cannot safely be automatically detected (since that "
+"may damage some of them). You thus need to append the "
+"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
+"replaceable>,<replaceable>table</replaceable></userinput> boot parameter to "
+"tell <classname>brltty</classname> which driver it should use. "
+"<replaceable>driver</replaceable> should be replaced by the two-letter "
+"driver code for your terminal (see the <ulink url=\"&url-brltty-manual;"
+"\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be "
+"replaced by the name of the serial port the display is connected to, "
+"<userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> "
+"can be typically used when using a serial-to-USB converter. "
+"<replaceable>table</replaceable> is the name of the braille table to be used "
+"(see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the "
+"English table is the default. Note that the table can be changed later by "
+"entering the preference menu. Documentation on key bindings for braille "
+"devices is available on the <ulink url=\"&url-brltty-driver-help;"
+"\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
-msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
+msgid ""
+"Support for software speech synthesis can be activated by selecting it in "
+"the boot menu by typing <userinput>s</userinput> &enterkey;. The first "
+"question (language) is spoken in english, and the remainder of installation "
+"is spoken in the selected language (if available in <classname>espeak</"
+"classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
+msgid ""
+"Support for hardware speech synthesis devices is available only alongside "
+"support for graphical installer. You thus need to select a <quote>Graphical "
+"install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
-msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
+msgid ""
+"Hardware speech synthesis devices cannot be automatically detected. You thus "
+"need to append the <userinput>speakup.synth=<replaceable>driver</"
+"replaceable></userinput> boot parameter to tell <classname>speakup</"
+"classname> which driver it should use. <replaceable>driver</replaceable> "
+"should be replaced by the driver code for your device (see <ulink url=\"&url-"
+"speakup-driver-codes;\">driver code list</ulink>). The textual version of "
+"the installer will then be automatically selected, and support for the "
+"speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
-msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
+msgid ""
+"Some accessibility devices are actual boards that are plugged inside the "
+"machine and that read text directly from the video memory. To get them to "
+"work framebuffer support must be disabled by using the <userinput arch="
+"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot "
+"parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
-msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
+msgid ""
+"If desired a textual version of the bootloader can be activated before "
+"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
-msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
+msgid ""
+"For users with low vision, the installer can use a high-contrast theme that "
+"makes it more readable. To enable it, append the <userinput>theme=dark</"
+"userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
-msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Alternatively, &debian; can be installed completely automatically by using "
+"preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
-msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
+msgid ""
+"Boot parameters are Linux kernel parameters which are generally used to make "
+"sure that peripherals are dealt with properly. For the most part, the kernel "
+"can auto-detect information about your peripherals. However, in some cases "
+"you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
-msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
+msgid ""
+"If this is the first time you're booting the system, try the default boot "
+"parameters (i.e., don't try setting parameters) and see if it works "
+"correctly. It probably will. If not, you can reboot later and look for any "
+"special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
-msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"Information on many boot parameters can be found in the <ulink url=\"http://"
+"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
+"including tips for obscure hardware. This section contains only a sketch of "
+"the most salient parameters. Some common gotchas are included below in <xref "
+"linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
-msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
+msgid ""
+"If you are booting with a serial console, generally the kernel will "
+"autodetect this. If you have a videocard (framebuffer) and a keyboard also "
+"attached to the computer which you wish to boot via serial console, you may "
+"have to pass the <userinput>console=<replaceable>device</replaceable></"
+"userinput> argument to the kernel, where <replaceable>device</replaceable> "
+"is your serial device, which is usually something like <filename>ttyS0</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
-msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
+msgid ""
+"In order to ensure the terminal type used by the installer matches your "
+"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
+"replaceable></userinput> can be added. Note that the installer only supports "
+"the following terminal types: <literal>linux</literal>, <literal>bterm</"
+"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
+"<literal>dumb</literal>. The default for serial console in &d-i; is "
+"<userinput>vt102</userinput>. If you are using a virtualization tool which "
+"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, "
+"you can start it inside a <command>screen</command> session. That will "
+"indeed perform translation into the <literal>screen</literal> terminal type, "
+"which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
-msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
+msgid ""
+"For &arch-title; the serial devices are <filename>ttya</filename> or "
+"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
+"envar> and <envar>output-device</envar> OpenPROM variables to "
+"<filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
+msgid ""
+"The installation system recognizes a few additional boot "
+"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
+"use 32 command line options and 32 environment options. If these numbers are "
+"exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
-msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
+msgid ""
+"A number of parameters have a <quote>short form</quote> that helps avoid the "
+"limitations of the kernel command line options and makes entering the "
+"parameters easier. If a parameter has a short form, it will be listed in "
+"brackets behind the (normal) long form. Examples in this manual will "
+"normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
-msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
+msgid ""
+"The default installation uses <userinput>priority=high</userinput>. This "
+"means that both high and critical priority messages are shown, but medium "
+"and low priority messages are skipped. If problems are encountered, the "
+"installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
-msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
+msgid ""
+"If you add <userinput>priority=medium</userinput> as boot parameter, you "
+"will be shown the installation menu and gain more control over the "
+"installation. When <userinput>priority=low</userinput> is used, all messages "
+"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
+"method). With <userinput>priority=critical</userinput>, the installation "
+"system will display only critical messages and try to do the right thing "
+"without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
-msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
+msgid ""
+"This boot parameter controls the type of user interface used for the "
+"installer. The current possible parameter settings are: <itemizedlist> "
+"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
+"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
+"userinput></para> </listitem><listitem> "
+"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
+"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
+"</listitem> </itemizedlist> The default frontend is "
+"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
+"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
+"console installs. Some specialized types of install media may only offer a "
+"limited selection of frontends, but the <userinput>newt</userinput> and "
+"<userinput>text</userinput> frontends are available on most default install "
+"media. On architectures that support it, the graphical installer uses the "
+"<userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
-msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
+msgid ""
+"Setting this boot parameter to 2 will cause the installer's boot process to "
+"be verbosely logged. Setting it to 3 makes debug shells available at "
+"strategic points in the boot process. (Exit the shells to continue the boot "
+"process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
-msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
+msgid ""
+"Shells are run at various points in the boot process to allow detailed "
+"debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
-msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
+msgid ""
+"The value of the parameter is the path to the device to load the &debian; "
+"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
+"userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
-msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
+msgid ""
+"The boot floppy, which normally scans all floppies it can to find the root "
+"floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
-msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
+msgid ""
+"Causes the installer to send log messages to a remote syslog on the "
+"specified host and port as well as to a local file. If not specified, the "
+"port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
-msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
+msgid ""
+"Can be used to force the installer to a lowmem level higher than the one the "
+"installer sets by default based on available memory. Possible values are 1 "
+"and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
-msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
+msgid ""
+"Prevents the installer from offering interactive shells on tty2 and tty3. "
+"Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
-msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
+msgid ""
+"Some architectures use the kernel framebuffer to offer installation in a "
+"number of languages. If framebuffer causes a problem on your system you can "
+"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</"
+"userinput> <userinput>fb=false</userinput>. Problem symptoms are error "
+"messages about bterm or bogl, a blank screen, or a freeze within a few "
+"minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
-msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
+msgid ""
+"Because of display problems on some systems, framebuffer support is "
+"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
+"in ugly display on systems that do properly support the framebuffer, like "
+"those with ATI graphical cards. If you see display problems in the "
+"installer, you can try booting with parameter <userinput>debian-installer/"
+"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
-msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
+msgid ""
+"A theme determines how the user interface of the installer looks (colors, "
+"icons, etc.). What themes are available differs per frontend. Currently both "
+"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
+"designed for visually impaired users. Set the theme by booting with "
+"<userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
-msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
+msgid ""
+"By default, the &d-i; automatically probes for network configuration via "
+"DHCP. If the probe succeeds, you won't have a chance to review and change "
+"the obtained settings. You can get to the manual network setup only in case "
+"the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
-msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
+msgid ""
+"If you have a DHCP server on your local network, but want to avoid it "
+"because e.g. it gives wrong answers, you can use the parameter "
+"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
+"network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
+msgid ""
+"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
+"that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
+msgid ""
+"Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
+"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note "
+"that this support is currently experimental. Additional information can be "
+"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
-msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the url to a preconfiguration file to download and use for "
+"automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
-msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the path to a preconfiguration file to load for automating the "
+"install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
+msgid ""
+"Set to <userinput>true</userinput> to display questions even if they have "
+"been preseeded. Can be useful for testing or debugging a preconfiguration "
+"file. Note that this will have no effect on parameters that are passed as "
+"boot parameters, but for those a special syntax can be used. See <xref "
+"linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
-msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
+msgid ""
+"Delay questions that are normally asked before preseeding is possible until "
+"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
+"details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
-msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
+msgid ""
+"During installations from serial or management console, the regular virtual "
+"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
+"filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
-msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
+msgid ""
+"By default, before rebooting, &d-i; automatically ejects the optical media "
+"used during the installation. This can be unnecessary if the system does not "
+"automatically boot off the CD. In some cases it may even be undesirable, for "
+"example if the optical drive cannot reinsert the media itself and the user "
+"is not there to do it manually. Many slot loading, slim-line, and caddy "
+"style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
+msgid ""
+"Set to <userinput>false</userinput> to disable automatic ejection, and be "
+"aware that you may need to ensure that the system does not automatically "
+"boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
-msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
+msgid ""
+"By setting this option to <userinput>false</userinput>, the package "
+"management system will be configured to not automatically install "
+"<quote>Recommends</quote>, both during the installation and for the "
+"installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
-msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
+msgid ""
+"Note that this option allows to have a leaner system, but can also result in "
+"features being missing that you might normally expect to be available. You "
+"may have to manually install some of the recommended packages to obtain the "
+"full functionality you want. This option should therefore only be used by "
+"very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
-msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
+msgid ""
+"By default the installer requires that repositories be authenticated using a "
+"known gpg key. Set to <userinput>true</userinput> to disable that "
+"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
+"emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
-msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
+msgid ""
+"This parameter should already be set to a correct value where needed; set it "
+"only it you see errors during the boot that indicate the ramdisk could not "
+"be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
+msgid ""
+"Set to <userinput>true</userinput> to enter rescue mode rather than "
+"performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
-msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
+msgid ""
+"With some exceptions, a value can be set at the boot prompt for any question "
+"asked during the installation, though this is only really useful in specific "
+"cases. General instructions how to do this can be found in <xref linkend="
+"\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
-msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
+msgid ""
+"There are two ways to specify the language, country and locale to use for "
+"the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
-msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
+msgid ""
+"The first and easiest is to pass only the parameter <literal>locale</"
+"literal>. Language and country will then be derived from its value. You can "
+"for example use <userinput>locale=de_CH</userinput> to select German as "
+"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be "
+"set as default locale for the installed system). Limitation is that not all "
+"possible combinations of language, country and locale can be achieved this "
+"way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
-msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
+msgid ""
+"The second, more flexible option is to specify <literal>language</literal> "
+"and <literal>country</literal> separately. In this case <literal>locale</"
+"literal> can optionally be added to specify a specific default locale for "
+"the installed system. Example: <userinput>language=en country=DE "
+"locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
-msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
+msgid ""
+"Can be used to automatically load installer components that are not loaded "
+"by default. Examples of optional components that may be useful are "
+"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
+"command> during the installation)<phrase arch=\"not-s390\"> and "
+"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
-msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
+msgid ""
+"Set to <userinput>true</userinput> if you want to disable DHCP and instead "
+"force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
-msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
+msgid ""
+"By default the installer will use the http protocol to download files from "
+"&debian; mirrors and changing that to ftp is not possible during "
+"installations at normal priority. By setting this parameter to "
+"<userinput>ftp</userinput>, you can force the installer to use that protocol "
+"instead. Note that you cannot select an ftp mirror from a list, you have to "
+"enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
-msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
+msgid ""
+"Can be used to select tasks that are not available from the interactive task "
+"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
+"\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
-msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
+msgid ""
+"If drivers are compiled into the kernel, you can pass parameters to them as "
+"described in the kernel documentation. However, if drivers are compiled as "
+"modules and because kernel modules are loaded a bit differently during an "
+"installation than when booting an installed system, it is not possible to "
+"pass parameters to modules as you would normally do. Instead, you need to "
+"use a special syntax recognized by the installer which will then make sure "
+"that the parameters are saved in the proper configuration files and will "
+"thus be used when the modules are actually loaded. The parameters will also "
+"be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
-msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
+msgid ""
+"Note that it is now quite rare that parameters need to be passed to modules. "
+"In most cases the kernel will be able to probe the hardware present in a "
+"system and set good defaults that way. However, in some situations it may "
+"still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
-      "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
-      "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n"
-      "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:"
+"The syntax to use to set parameters for modules is: "
+"<informalexample><screen>\n"
+"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
+"replaceable>=<replaceable>value</replaceable>\n"
+"</screen></informalexample> If you need to pass multiple parameters to the "
+"same or different modules, just repeat this. For example, to set an old 3Com "
+"network interface card to use the BNC (coax) connector and IRQ 10, you would "
+"pass:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
-msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
+msgid ""
+"Sometimes it may be necessary to blacklist a module to prevent it from being "
+"loaded automatically by the kernel and udev. One reason could be that a "
+"particular module causes problems with your hardware. The kernel also "
+"sometimes lists two different drivers for the same device. This can cause "
+"the device to not work correctly if the drivers conflict or if the wrong "
+"driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
-msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
+msgid ""
+"You can blacklist a module using the following syntax: "
+"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
+"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
+"blacklist.local</filename> both during the installation and for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
-msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
+msgid ""
+"Note that a module may still be loaded by the installation system itself. "
+"You can prevent that from happening by running the installation in expert "
+"mode and unselecting the module from the list of modules displayed during "
+"the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
-msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
+msgid ""
+"Sometimes, especially with older CD-ROM drives, the installer may fail to "
+"boot from a CD-ROM. The installer may also &mdash; even after booting "
+"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
+"errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
-msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
+msgid ""
+"There are many different possible causes for these problems. We can only "
+"list some common issues and provide general suggestions on how to deal with "
+"them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
-msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
+msgid ""
+"If the CD-ROM does not boot, check that it was inserted correctly and that "
+"it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
-msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
+msgid ""
+"If the installer fails to recognize a CD-ROM, try just running the option "
+"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
+"menuchoice> a second time. Some DMA related issues with very old CD-ROM "
+"drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
-msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
+msgid ""
+"If this does not work, then try the suggestions in the subsections below. "
+"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
+"DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
-msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
+msgid ""
+"If you cannot get the installation working from CD-ROM, try one of the other "
+"installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
-msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
+msgid ""
+"Some older CD-ROM drives do not support reading from discs that were burned "
+"at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
-msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
+msgid ""
+"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
+"access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
-msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
+msgid ""
+"Check that your BIOS actually supports booting from CD-ROM (only an issue "
+"for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
-      "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
-      "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM."
+"If you downloaded an iso image, check that the md5sum of that image matches "
+"the one listed for the image in the <filename>MD5SUMS</filename> file that "
+"should be present in the same location as where you downloaded the image "
+"from. <informalexample><screen>\n"
+"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
+"iso</replaceable>\n"
+"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
+"matches as well. The following command should work. It uses the size of the "
+"image to read the correct number of bytes from the CD-ROM."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
-      "$ dd if=/dev/cdrom | \\\n"
-      "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n"
-      "> md5sum\n"
-      "a20391b12f7ff22ef705cee4059c6b92  -\n"
-      "262668+0 records in\n"
-      "262668+0 records out\n"
-      "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
+"$ dd if=/dev/cdrom | \\\n"
+"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
+"replaceable>` | \\\n"
+"> md5sum\n"
+"a20391b12f7ff22ef705cee4059c6b92  -\n"
+"262668+0 records in\n"
+"262668+0 records out\n"
+"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
-msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
+msgid ""
+"If, after the installer has been booted successfully, the CD-ROM is not "
+"detected, sometimes simply trying again may solve the problem. If you have "
+"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
+"that does not work or if the CD-ROM is recognized but there are errors when "
+"reading from it, try the suggestions listed below. Some basic knowledge of "
+"&arch-kernel; is required for this. To execute any of the commands, you "
+"should first switch to the second virtual console (VT2) and activate the "
+"shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
-msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
+msgid ""
+"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
+"(use <command>nano</command> as editor) to check for any specific error "
+"messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
-      "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
-      "Probing IDE interface ide1...\n"
-      "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
-      "ide1 at 0x170-0x177,0x376 on irq 15\n"
-      "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
-      "Uniform CD-ROM driver Revision: 3.20\n"
-      "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using <command>modprobe</command>."
+"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
+"recognized. You should see something like (the lines do not necessarily have "
+"to be consecutive): <informalexample><screen>\n"
+"Probing IDE interface ide1...\n"
+"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
+"ide1 at 0x170-0x177,0x376 on irq 15\n"
+"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
+"Uniform CD-ROM driver Revision: 3.20\n"
+"</screen></informalexample> If you don't see something like that, chances "
+"are the controller your CD-ROM is connected to was not recognized or may be "
+"not supported at all. If you know what driver is needed for the controller, "
+"you can try loading it manually using <command>modprobe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
-msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
+msgid ""
+"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
+"</filename>. In the example above, this would be <filename>/dev/hdc</"
+"filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
-      "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
-      "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
-      "</screen></informalexample> Check if there are any error messages after that command."
+"Use the <command>mount</command> command to check if the CD-ROM is already "
+"mounted; if not, try mounting it manually: <informalexample><screen>\n"
+"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
+"</screen></informalexample> Check if there are any error messages after that "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
-      "Check if DMA is currently enabled: <informalexample><screen>\n"
-      "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
-      "$ grep using_dma settings\n"
-      "using_dma      1       0       1       rw\n"
-      "</screen></informalexample> A <quote>1</quote> in the first column after <literal>using_dma</literal> means it is enabled. If it is, try disabling it: <informalexample><screen>\n"
-      "$ echo -n \"using_dma:0\" >settings\n"
-      "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive."
+"Check if DMA is currently enabled: <informalexample><screen>\n"
+"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
+"$ grep using_dma settings\n"
+"using_dma      1       0       1       rw\n"
+"</screen></informalexample> A <quote>1</quote> in the first column after "
+"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
+"it: <informalexample><screen>\n"
+"$ echo -n \"using_dma:0\" >settings\n"
+"</screen></informalexample> Make sure that you are in the directory for the "
+"device that corresponds to your CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
-msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
+msgid ""
+"If there are any problems during the installation, try checking the "
+"integrity of the CD-ROM using the option near the bottom of the installer's "
+"main menu. This option can also be used as a general test if the CD-ROM can "
+"be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
-msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
+msgid ""
+"The biggest problem for people using floppy disks to install &debian; seems "
+"to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
-msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
+msgid ""
+"The boot floppy is the floppy with the worst problems, because it is read by "
+"the hardware directly, before Linux boots. Often, the hardware doesn't read "
+"as reliably as the Linux floppy disk driver, and may just stop without "
+"printing an error message if it reads incorrect data. There can also be "
+"failures in the driver floppies, most of which indicate themselves with a "
+"flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
-msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
+msgid ""
+"If you are having the installation stall at a particular floppy, the first "
+"thing you should do is write the image to a <emphasis>different</emphasis> "
+"floppy and see if that solves the problem. Simply reformatting the old "
+"floppy may not be sufficient, even if it appears that the floppy was "
+"reformatted and written with no errors. It is sometimes useful to try "
+"writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
-msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
+msgid ""
+"One user reports he had to write the images to floppy <emphasis>three</"
+"emphasis> times before one worked, and then everything was fine with the "
+"third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
-msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
+msgid ""
+"Normally you should not have to download a floppy image again, but if you "
+"are experiencing problems it is always useful to verify that the images were "
+"downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
-msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
+msgid ""
+"Other users have reported that simply rebooting a few times with the same "
+"floppy in the floppy drive can lead to a successful boot. This is all due to "
+"buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
-msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
+msgid ""
+"If you have problems and the kernel hangs during the boot process, doesn't "
+"recognize peripherals you actually have, or drives are not recognized "
+"properly, the first thing to check is the boot parameters, as discussed in "
+"<xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
-msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
+msgid ""
+"In some cases, malfunctions can be caused by missing device firmware (see "
+"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
+">)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
-msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
+msgid ""
+"If software speech synthesis does not work, there is most probably an issue "
+"with your sound board, usually because either the driver for it is not "
+"included in the installer, or because it has unusual mixer level names which "
+"are set to muted by default. You should thus submit a bug report which "
+"includes the output of the following commands, run on the same machine from "
+"a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
-msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
+msgid ""
+"There are some common installation problems that can be solved or avoided by "
+"passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
-msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
+msgid ""
+"If your screen begins to show a weird picture while the kernel boots, eg. "
+"pure white, pure black or colored pixel garbage, your system may contain a "
+"problematic video card which does not switch to the framebuffer mode "
+"properly. Then you can use the boot parameter <userinput>fb=false</"
+"userinput> to disable the framebuffer console. Only a reduced set of "
+"languages will be available during the installation due to limited console "
+"features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
-msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
+msgid ""
+"Some very old laptop models produced by Dell are known to crash when PCMCIA "
+"device detection tries to access some hardware addresses. Other laptops may "
+"display similar problems. If you experience such a problem and you don't "
+"need PCMCIA support during the installation, you can disable PCMCIA using "
+"the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
+"can then configure PCMCIA after the installation is completed and exclude "
+"the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
-msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
+msgid ""
+"Alternatively, you can boot the installer in expert mode. You will then be "
+"asked to enter the resource range options your hardware needs. For example, "
+"if you have one of the Dell laptops mentioned above, you should enter "
+"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
+"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
+"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
+"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
+"commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
-      "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
-      "Remapping the kernel... done\n"
-      "Booting Linux...\n"
-      "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>."
+"It is fairly common for &arch-title; to have two video cards in one machine, "
+"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
+"in the video output getting misdirected soon after the system boots. In "
+"typical cases, the display will only show: <informalexample><screen>\n"
+"Remapping the kernel... done\n"
+"Booting Linux...\n"
+"</screen></informalexample> To work around this, you can either pull out one "
+"of the video cards, or disable the one not used during the OpenProm boot "
+"phase using a kernel parameter. For example, to disable an ATI card, you "
+"should boot the installer with <userinput>video=atyfb:off</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
-msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"Note that you may also have to manually add this parameter to the silo "
+"configuration (edit <filename>/target/etc/silo.conf</filename> before "
+"rebooting) and, if you installed X11, modify the video driver in <filename>/"
+"etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
-msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
+msgid ""
+"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
+"they do boot, there may be inexplicable failures during the installation. "
+"Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
-msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
+msgid ""
+"During the boot sequence, you may see many messages in the form "
+"<computeroutput>can't find <replaceable>something</replaceable></"
+"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
+"present</computeroutput>, <computeroutput>can't initialize "
+"<replaceable>something</replaceable></computeroutput>, or even "
+"<computeroutput>this driver release depends on <replaceable>something</"
+"replaceable></computeroutput>. Most of these messages are harmless. You see "
+"them because the kernel for the installation system is built to run on "
+"computers with many different peripheral devices. Obviously, no one computer "
+"will have every possible peripheral device, so the operating system may emit "
+"a few complaints while it looks for peripherals you don't own. You may also "
+"see the system pause for a while. This happens when it is waiting for a "
+"device to respond, and that device is not present on your system. If you "
+"find the time it takes to boot the system unacceptably long, you can create "
+"a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
+"baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
-msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
+msgid ""
+"If you get through the initial boot phase but cannot complete the install, "
+"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
+"It lets you store system error logs and configuration information from the "
+"installer to a floppy, or download them using a web browser. This "
+"information may provide clues as to what went wrong and how to fix it. If "
+"you are submitting a bug report, you may want to attach this information to "
+"the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
-msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"Other pertinent installation messages may be found in <filename>/var/log/</"
+"filename> during the installation, and <filename>/var/log/installer/</"
+"filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
-msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
+msgid ""
+"If you still have problems, please submit an installation report. We also "
+"encourage installation reports to be sent even if the installation is "
+"successful, so that we can get as much information as possible on the "
+"largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
-msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
+msgid ""
+"Note that your installation report will be published in the Debian Bug "
+"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
+"you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
-msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
+msgid ""
+"If you have a working &debian; system, the easiest way to send an "
+"installation report is to install the <classname>installation-report</"
+"classname> and <classname>reportbug</classname> packages (<command>aptitude "
+"install installation-report reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run the command <command>reportbug installation-reports</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
-      "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
-      "Package: installation-reports\n"
-      "\n"
-      "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
-      "Image version: &lt;Full URL to image you downloaded is best&gt;\n"
-      "Date: &lt;Date and time of the install&gt;\n"
-      "\n"
-      "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
-      "Processor:\n"
-      "Memory:\n"
-      "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
-      "\n"
-      "Output of lspci -knn (or lspci -nn):\n"
-      "\n"
-      "Base System Installation Checklist:\n"
-      "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
-      "\n"
-      "Initial boot:           [ ]\n"
-      "Detect network card:    [ ]\n"
-      "Configure network:      [ ]\n"
-      "Detect CD:              [ ]\n"
-      "Load installer modules: [ ]\n"
-      "Detect hard drives:     [ ]\n"
-      "Partition hard drives:  [ ]\n"
-      "Install base system:    [ ]\n"
-      "Clock/timezone setup:   [ ]\n"
-      "User/password setup:    [ ]\n"
-      "Install tasks:          [ ]\n"
-      "Install boot loader:    [ ]\n"
-      "Overall install:        [ ]\n"
-      "\n"
-      "Comments/Problems:\n"
-      "\n"
-      "&lt;Description of the install, in prose, and any thoughts, comments\n"
-      "      and ideas you had during the initial install.&gt;\n"
-      "</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state."
+"Alternatively you can use this template when filling out installation "
+"reports, and file the report as a bug report against the "
+"<classname>installation-reports</classname> pseudo package, by sending it to "
+"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
+"Package: installation-reports\n"
+"\n"
+"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
+"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
+"Date: &lt;Date and time of the install&gt;\n"
+"\n"
+"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
+"Processor:\n"
+"Memory:\n"
+"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
+"\n"
+"Output of lspci -knn (or lspci -nn):\n"
+"\n"
+"Base System Installation Checklist:\n"
+"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
+"\n"
+"Initial boot:           [ ]\n"
+"Detect network card:    [ ]\n"
+"Configure network:      [ ]\n"
+"Detect CD:              [ ]\n"
+"Load installer modules: [ ]\n"
+"Detect hard drives:     [ ]\n"
+"Partition hard drives:  [ ]\n"
+"Install base system:    [ ]\n"
+"Clock/timezone setup:   [ ]\n"
+"User/password setup:    [ ]\n"
+"Install tasks:          [ ]\n"
+"Install boot loader:    [ ]\n"
+"Overall install:        [ ]\n"
+"\n"
+"Comments/Problems:\n"
+"\n"
+"&lt;Description of the install, in prose, and any thoughts, comments\n"
+"      and ideas you had during the initial install.&gt;\n"
+"</screen></informalexample> In the bug report, describe what the problem is, "
+"including the last visible kernel messages in the event of a kernel hang. "
+"Describe the steps that you did which brought the system into the problem "
+"state."
 msgstr ""
-
diff --git a/po/nl/boot-new.po b/po/nl/boot-new.po
index 202d93271..f4d294cfc 100644
--- a/po/nl/boot-new.po
+++ b/po/nl/boot-new.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,31 +29,59 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:8
 #, no-c-format
-msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>."
+msgid ""
+"Your system's first boot on its own power is what electrical engineers call "
+"the <quote>smoke test</quote>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:13
 #, no-c-format
-msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new &debian; system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu."
+msgid ""
+"If you did a default installation, the first thing you should see when you "
+"boot the system is the menu of the <classname>grub</classname><phrase arch="
+"\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. "
+"The first choices in the menu will be for your new &debian; system. If you "
+"had any other operating systems on your computer (like Windows) that were "
+"detected by the installation system, those will be listed lower down in the "
+"menu."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:23
 #, no-c-format
-msgid "If the system fails to start up correctly, don't panic. If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting &debian;. In most cases such problems can be fixed without having to repeat the installation. One available option to fix boot problems is to use the installer's built-in rescue mode (see <xref linkend=\"rescue\"/>)."
+msgid ""
+"If the system fails to start up correctly, don't panic. If the installation "
+"was successful, chances are good that there is only a relatively minor "
+"problem that is preventing the system from booting &debian;. In most cases "
+"such problems can be fixed without having to repeat the installation. One "
+"available option to fix boot problems is to use the installer's built-in "
+"rescue mode (see <xref linkend=\"rescue\"/>)."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:32
 #, no-c-format
-msgid "If you are new to &debian; and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue."
+msgid ""
+"If you are new to &debian; and &arch-kernel;, you may need some help from "
+"more experienced users. <phrase arch=\"x86\">For direct on-line help you can "
+"try the IRC channels #debian or #debian-boot on the OFTC network. "
+"Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-"
+"user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common "
+"architectures like &arch-title;, your best option is to ask on the <ulink "
+"url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</"
+"phrase> You can also file an installation report as described in <xref "
+"linkend=\"submit-bug\"/>. Please make sure that you describe your problem "
+"clearly and include any messages that are displayed and may help others to "
+"diagnose the issue."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:48
 #, no-c-format
-msgid "If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report."
+msgid ""
+"If you had any other operating systems on your computer that were not "
+"detected or not detected correctly, please file an installation report."
 msgstr ""
 
 #. Tag: title
@@ -64,19 +93,42 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:57
 #, no-c-format
-msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
+msgid ""
+"If the machine fails to boot after completing the installation, and stops "
+"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</"
+"userinput> followed by &enterkey;. (The default boot configuration in "
+"<filename>quik.conf</filename> is labeled Linux). The labels defined in "
+"<filename>quik.conf</filename> will be displayed if you press the "
+"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also "
+"try booting back into the installer, and editing the <filename>/target/etc/"
+"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard "
+"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are "
+"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:71
 #, no-c-format
-msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"To boot back into MacOS without resetting the nvram, type <userinput>bye</"
+"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed "
+"from the machine). To obtain an OpenFirmware prompt, hold down the "
+"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</"
+"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. "
+"If you need to reset the OpenFirmware nvram changes to the MacOS default in "
+"order to boot back to MacOS, hold down the <keycombo> <keycap>command</"
+"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </"
+"keycombo> keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:84
 #, no-c-format
-msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
+msgid ""
+"If you use <command>BootX</command> to boot into the installed system, just "
+"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
+"un-choose the ramdisk option, and add a root device corresponding to your "
+"installation; e.g. <userinput>/dev/hda8</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -88,31 +140,52 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:97
 #, no-c-format
-msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon."
+msgid ""
+"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key "
+"and get a graphical screen with a button for each bootable OS, &debian-gnu; "
+"will be a button with a small penguin icon."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:104
 #, no-c-format
-msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-"
+"device</envar> variable you should reset OpenFirmware to its default "
+"configuration. To do this hold down the <keycombo> <keycap>command</keycap> "
+"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> "
+"keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:112
 #, no-c-format
-msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
+msgid ""
+"The labels defined in <filename>yaboot.conf</filename> will be displayed if "
+"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:118
 #, no-c-format
-msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
+msgid ""
+"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-"
+"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap "
+"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an "
+"IDE disk this may not work and you will have to enter OpenFirmware and set "
+"the <envar>boot-device</envar> variable, <command>ybin</command> normally "
+"does this automatically."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:127
 #, no-c-format
-msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
+msgid ""
+"After you boot &debian-gnu; for the first time you can add any additional "
+"options you desire (such as dual boot options) to <filename>/etc/yaboot."
+"conf</filename> and run <command>ybin</command> to update your boot "
+"partition with the changed configuration. Please read the <ulink url=\"&url-"
+"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
 msgstr ""
 
 #. Tag: title
@@ -124,7 +197,11 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:147
 #, no-c-format
-msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
+msgid ""
+"If you created encrypted volumes during the installation and assigned them "
+"mount points, you will be asked to enter the passphrase for each of these "
+"volumes during the boot. The actual procedure differs slightly between dm-"
+"crypt and loop-AES."
 msgstr ""
 
 #. Tag: title
@@ -137,31 +214,54 @@ msgstr ""
 #: boot-new.xml:159
 #, no-c-format
 msgid ""
-      "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
-      "Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
-      "Enter LUKS passphrase:\n"
-      "</screen></informalexample> In the first line of the prompt, <replaceable>part</replaceable> is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename><replaceable>part</replaceable>_crypt</filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system."
+"For partitions encrypted using dm-crypt you will be shown the following "
+"prompt during the boot: <informalexample><screen>\n"
+"Starting early crypto disks... <replaceable>part</replaceable>_crypt"
+"(starting)\n"
+"Enter LUKS passphrase:\n"
+"</screen></informalexample> In the first line of the prompt, "
+"<replaceable>part</replaceable> is the name of the underlying partition, e."
+"g. sda2 or md0. You are now probably wondering <emphasis>for which volume</"
+"emphasis> you are actually entering the passphrase. Does it relate to your "
+"<filename>/home</filename>? Or to <filename>/var</filename>? Of course, if "
+"you have just one encrypted volume, this is easy and you can just enter the "
+"passphrase you used when setting up this volume. If you set up more than one "
+"encrypted volume during the installation, the notes you wrote down as the "
+"last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did "
+"not make a note of the mapping between <filename><replaceable>part</"
+"replaceable>_crypt</filename> and the mount points before, you can still "
+"find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</"
+"filename> of your new system."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:182
 #, no-c-format
-msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
+msgid ""
+"The prompt may look somewhat different when an encrypted root file system is "
+"mounted. This depends on which initramfs generator was used to generate the "
+"initrd used to boot the system. The example below is for an initrd generated "
+"using <classname>initramfs-tools</classname>:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:189
 #, no-c-format
 msgid ""
-      "Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
-      "Begin: Running /scripts/local-top ...\n"
-      "Enter LUKS passphrase:"
+"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
+"Begin: Running /scripts/local-top ...\n"
+"Enter LUKS passphrase:"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:191 boot-new.xml:216
 #, no-c-format
-msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
+msgid ""
+"No characters (even asterisks) will be shown while entering the passphrase. "
+"If you enter the wrong passphrase, you have two more tries to correct it. "
+"After the third try the boot process will skip this volume and continue to "
+"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting"
+"\"/> for further information."
 msgstr ""
 
 #. Tag: para
@@ -179,16 +279,19 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:209
 #, no-c-format
-msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
+msgid ""
+"For partitions encrypted using loop-AES you will be shown the following "
+"prompt during the boot:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:214
 #, no-c-format
 msgid ""
-      "Checking loop-encrypted file systems.\n"
-      "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
-      "Password:"
+"Checking loop-encrypted file systems.\n"
+"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</"
+"replaceable>)\n"
+"Password:"
 msgstr ""
 
 #. Tag: title
@@ -200,47 +303,77 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:234
 #, no-c-format
-msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
+msgid ""
+"If some of the encrypted volumes could not be mounted because a wrong "
+"passphrase was entered, you will have to mount them manually after the boot. "
+"There are several cases."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:243
 #, no-c-format
-msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
+msgid ""
+"The first case concerns the root partition. When it is not mounted "
+"correctly, the boot process will halt and you will have to reboot the "
+"computer to try again."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:250
 #, no-c-format
 msgid ""
-      "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
-      "<prompt>Password:</prompt>\n"
-      "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
+"The easiest case is for encrypted volumes holding data like <filename>/home</"
+"filename> or <filename>/srv</filename>. You can simply mount them manually "
+"after the boot. For loop-AES this is a one-step operation: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>\n"
+"<prompt>Password:</prompt>\n"
+"</screen></informalexample> where <replaceable>/mount_point</replaceable> "
+"should be replaced by the particular directory (e.g. <filename>/home</"
+"filename>). The only difference from an ordinary mount is that you will be "
+"asked to enter the passphrase for this volume."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:264
 #, no-c-format
 msgid ""
-      "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-      "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
+"For dm-crypt this is a bit trickier. First you need to register the volumes "
+"with <application>device mapper</application> by running: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
+"</screen></informalexample> This will scan all volumes mentioned in "
+"<filename>/etc/crypttab</filename> and will create appropriate devices under "
+"the <filename>/dev</filename> directory after entering the correct "
+"passphrases. (Already registered volumes will be skipped, so you can repeat "
+"this command several times without worrying.) After successful registration "
+"you can simply mount the volumes the usual way:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:279
 #, no-c-format
-msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
+msgid ""
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:282
 #, no-c-format
 msgid ""
-      "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-      "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
+"If any volume holding noncritical system files could not be mounted "
+"(<filename>/usr</filename> or <filename>/var</filename>), the system should "
+"still boot and you should be able to mount the volumes manually like in the "
+"previous case. However, you will also need to (re)start any services usually "
+"running in your default runlevel because it is very likely that they were "
+"not started. The easiest way to achieve this is by switching to the first "
+"runlevel and back by entering <informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>init 1</userinput>\n"
+"</screen></informalexample> at the shell prompt and pressing <keycombo> "
+"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the "
+"root password."
 msgstr ""
 
 #. Tag: title
@@ -252,46 +385,81 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:307
 #, no-c-format
-msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
+msgid ""
+"Once your system boots, you'll be presented with the login prompt. Log in "
+"using the personal login and password you selected during the installation "
+"process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:313
 #, no-c-format
-msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
+msgid ""
+"If you are a new user, you may want to explore the documentation which is "
+"already installed on your system as you start to use it. There are currently "
+"several documentation systems, work is proceeding on integrating the "
+"different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:321
 #, no-c-format
-msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
+msgid ""
+"Documentation accompanying programs you have installed can be found in "
+"<filename>/usr/share/doc/</filename>, under a subdirectory named after the "
+"program (or, more precise, the &debian; package that contains the program). "
+"However, more extensive documentation is often packaged separately in "
+"special documentation packages that are mostly not installed by default. For "
+"example, documentation about the package management tool <command>apt</"
+"command> can be found in the packages <classname>apt-doc</classname> or "
+"<classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:332
 #, no-c-format
-msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
+msgid ""
+"In addition, there are some special folders within the <filename>/usr/share/"
+"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</"
+"emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</"
+"filename>. After installing <classname>dhelp</classname>, you will find a "
+"browsable index of documentation in <filename>/usr/share/doc/HTML/index."
+"html</filename>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:341
 #, no-c-format
 msgid ""
-      "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
-      "$ cd /usr/share/doc/\n"
-      "$ w3m .\n"
-      "</screen></informalexample> The dot after the <command>w3m</command> command tells it to show the contents of the current directory."
+"One easy way to view these documents using a text based browser is to enter "
+"the following commands: <informalexample><screen>\n"
+"$ cd /usr/share/doc/\n"
+"$ w3m .\n"
+"</screen></informalexample> The dot after the <command>w3m</command> command "
+"tells it to show the contents of the current directory."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:351
 #, no-c-format
-msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
+msgid ""
+"If you have a graphical desktop environment installed, you can also use its "
+"web browser. Start the web browser from the application menu and enter "
+"<userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:357
 #, no-c-format
-msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
+msgid ""
+"You can also type <userinput>info <replaceable>command</replaceable></"
+"userinput> or <userinput>man <replaceable>command</replaceable></userinput> "
+"to see documentation on most commands available at the command prompt. "
+"Typing <userinput>help</userinput> will display help on shell commands. And "
+"typing a command followed by <userinput>--help</userinput> will usually "
+"display a short summary of the command's usage. If a command's results "
+"scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> "
+"after the command to cause the results to pause before scrolling past the "
+"top of the screen. To see a list of all commands available which begin with "
+"a certain letter, type the letter and then two tabs."
 msgstr ""
-
diff --git a/po/nl/gpl.po b/po/nl/gpl.po
index 3582cbd8a..5f7616aa6 100644
--- a/po/nl/gpl.po
+++ b/po/nl/gpl.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,35 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:6
 #, no-c-format
-msgid "[[This note, consisting of two paragraphs, should only be included in your translation if you translate the GPL in this appendix. See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English name of your language. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[This note, consisting of two paragraphs, should only be included in your "
+"translation if you translate the GPL in this appendix. See build/lang-"
+"options/README on how to enable this paragraph and for additional "
+"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH "
+"IN ENGLISH! Only replace {language} with the English name of your language. "
+"Do not change the link to the GPL!]] This is an unofficial translation of "
+"the GNU General Public License into {language}. It was not published by the "
+"Free Software Foundation, and does not legally state the distribution terms "
+"for software that uses the GNU GPL &mdash; only the original <ulink url="
+"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. "
+"However, we hope that this translation will help {language} speakers to "
+"better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:22
 #, no-c-format
-msgid "[[See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of your language before translating. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[See build/lang-options/README on how to enable this paragraph and for "
+"additional information. Its condition is \"gpl-unofficial\".]] [[THIS "
+"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of "
+"your language before translating. Do not change the link to the GPL!]] This "
+"is an unofficial translation of the GNU General Public License into "
+"{language}. It was not published by the Free Software Foundation, and does "
+"not legally state the distribution terms for software that uses the GNU GPL "
+"&mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</"
+"ulink> of the GNU GPL does that. However, we hope that this translation will "
+"help {language} speakers to better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
@@ -41,11 +64,11 @@ msgstr ""
 #: gpl.xml:41
 #, no-c-format
 msgid ""
-      "Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
-      "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
-      "\n"
-      "Everyone is permitted to copy and distribute verbatim copies\n"
-      "of this license document, but changing it is not allowed."
+"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
+"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
+"\n"
+"Everyone is permitted to copy and distribute verbatim copies\n"
+"of this license document, but changing it is not allowed."
 msgstr ""
 
 #. Tag: title
@@ -57,49 +80,87 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:46
 #, no-c-format
-msgid "The licenses for most software are designed to take away your freedom to share and change it. By contrast, the gnu General Public License is intended to guarantee your freedom to share and change free software &mdash; to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the gnu Library General Public License instead.) You can apply it to your programs, too."
+msgid ""
+"The licenses for most software are designed to take away your freedom to "
+"share and change it. By contrast, the gnu General Public License is intended "
+"to guarantee your freedom to share and change free software &mdash; to make "
+"sure the software is free for all its users. This General Public License "
+"applies to most of the Free Software Foundation's software and to any other "
+"program whose authors commit to using it. (Some other Free Software "
+"Foundation software is covered by the gnu Library General Public License "
+"instead.) You can apply it to your programs, too."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:58
 #, no-c-format
-msgid "When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+msgid ""
+"When we speak of free software, we are referring to freedom, not price. Our "
+"General Public Licenses are designed to make sure that you have the freedom "
+"to distribute copies of free software (and charge for this service if you "
+"wish), that you receive source code or can get it if you want it, that you "
+"can change the software or use pieces of it in new free programs; and that "
+"you know you can do these things."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:68
 #, no-c-format
-msgid "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it."
+msgid ""
+"To protect your rights, we need to make restrictions that forbid anyone to "
+"deny you these rights or to ask you to surrender the rights. These "
+"restrictions translate to certain responsibilities for you if you distribute "
+"copies of the software, or if you modify it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:75
 #, no-c-format
-msgid "For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
+msgid ""
+"For example, if you distribute copies of such a program, whether gratis or "
+"for a fee, you must give the recipients all the rights that you have. You "
+"must make sure that they, too, receive or can get the source code. And you "
+"must show them these terms so they know their rights."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:83
 #, no-c-format
-msgid "We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
+msgid ""
+"We protect your rights with two steps: (1) copyright the software, and (2) "
+"offer you this license which gives you legal permission to copy, distribute "
+"and/or modify the software."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:89
 #, no-c-format
-msgid "Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations."
+msgid ""
+"Also, for each author's protection and ours, we want to make certain that "
+"everyone understands that there is no warranty for this free software. If "
+"the software is modified by someone else and passed on, we want its "
+"recipients to know that what they have is not the original, so that any "
+"problems introduced by others will not reflect on the original authors' "
+"reputations."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:98
 #, no-c-format
-msgid "Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."
+msgid ""
+"Finally, any free program is threatened constantly by software patents. We "
+"wish to avoid the danger that redistributors of a free program will "
+"individually obtain patent licenses, in effect making the program "
+"proprietary. To prevent this, we have made it clear that any patent must be "
+"licensed for everyone's free use or not licensed at all."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:107
 #, no-c-format
-msgid "The precise terms and conditions for copying, distribution and modification follow."
+msgid ""
+"The precise terms and conditions for copying, distribution and modification "
+"follow."
 msgstr ""
 
 #. Tag: title
@@ -117,163 +178,327 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:121
 #, no-c-format
-msgid "<emphasis role=\"bold\">0.</emphasis> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \"Program\", below, refers to any such program or work, and a \"work based on the Program\" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \"modification\".) Each licensee is addressed as \"you\"."
+msgid ""
+"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or "
+"other work which contains a notice placed by the copyright holder saying it "
+"may be distributed under the terms of this General Public License. The "
+"\"Program\", below, refers to any such program or work, and a \"work based "
+"on the Program\" means either the Program or any derivative work under "
+"copyright law: that is to say, a work containing the Program or a portion of "
+"it, either verbatim or with modifications and/or translated into another "
+"language. (Hereinafter, translation is included without limitation in the "
+"term \"modification\".) Each licensee is addressed as \"you\"."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:134
 #, no-c-format
-msgid "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
+msgid ""
+"Activities other than copying, distribution and modification are not covered "
+"by this License; they are outside its scope. The act of running the Program "
+"is not restricted, and the output from the Program is covered only if its "
+"contents constitute a work based on the Program (independent of having been "
+"made by running the Program). Whether that is true depends on what the "
+"Program does."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:143
 #, no-c-format
-msgid "<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program."
+msgid ""
+"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim "
+"copies of the Program's source code as you receive it, in any medium, "
+"provided that you conspicuously and appropriately publish on each copy an "
+"appropriate copyright notice and disclaimer of warranty; keep intact all the "
+"notices that refer to this License and to the absence of any warranty; and "
+"give any other recipients of the Program a copy of this License along with "
+"the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:154
 #, no-c-format
-msgid "You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
+msgid ""
+"You may charge a fee for the physical act of transferring a copy, and you "
+"may at your option offer warranty protection in exchange for a fee."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:160
 #, no-c-format
-msgid "<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:"
+msgid ""
+"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of "
+"the Program or any portion of it, thus forming a work based on the Program, "
+"and copy and distribute such modifications or work under the terms of "
+"Section 1 above, provided that you also meet all of these conditions:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:169
 #, no-c-format
-msgid "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."
+msgid ""
+"You must cause the modified files to carry prominent notices stating that "
+"you changed the files and the date of any change."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:175
 #, no-c-format
-msgid "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License."
+msgid ""
+"You must cause any work that you distribute or publish, that in whole or in "
+"part contains or is derived from the Program or any part thereof, to be "
+"licensed as a whole at no charge to all third parties under the terms of "
+"this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:183
 #, no-c-format
-msgid "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
+msgid ""
+"If the modified program normally reads commands interactively when run, you "
+"must cause it, when started running for such interactive use in the most "
+"ordinary way, to print or display an announcement including an appropriate "
+"copyright notice and a notice that there is no warranty (or else, saying "
+"that you provide a warranty) and that users may redistribute the program "
+"under these conditions, and telling the user how to view a copy of this "
+"License. (Exception: if the Program itself is interactive but does not "
+"normally print such an announcement, your work based on the Program is not "
+"required to print an announcement.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:197
 #, no-c-format
-msgid "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
+msgid ""
+"These requirements apply to the modified work as a whole. If identifiable "
+"sections of that work are not derived from the Program, and can be "
+"reasonably considered independent and separate works in themselves, then "
+"this License, and its terms, do not apply to those sections when you "
+"distribute them as separate works. But when you distribute the same sections "
+"as part of a whole which is a work based on the Program, the distribution of "
+"the whole must be on the terms of this License, whose permissions for other "
+"licensees extend to the entire whole, and thus to each and every part "
+"regardless of who wrote it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:210
 #, no-c-format
-msgid "Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program."
+msgid ""
+"Thus, it is not the intent of this section to claim rights or contest your "
+"rights to work written entirely by you; rather, the intent is to exercise "
+"the right to control the distribution of derivative or collective works "
+"based on the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:217
 #, no-c-format
-msgid "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
+msgid ""
+"In addition, mere aggregation of another work not based on the Program with "
+"the Program (or with a work based on the Program) on a volume of a storage "
+"or distribution medium does not bring the other work under the scope of this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:224
 #, no-c-format
-msgid "<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:"
+msgid ""
+"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the "
+"Program (or a work based on it, under Section 2) in object code or "
+"executable form under the terms of Sections 1 and 2 above provided that you "
+"also do one of the following:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:233
 #, no-c-format
-msgid "Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with the complete corresponding machine-readable source code, "
+"which must be distributed under the terms of Sections 1 and 2 above on a "
+"medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:241
 #, no-c-format
-msgid "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with a written offer, valid for at least three years, to give "
+"any third party, for a charge no more than your cost of physically "
+"performing source distribution, a complete machine-readable copy of the "
+"corresponding source code, to be distributed under the terms of Sections 1 "
+"and 2 above on a medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:251
 #, no-c-format
-msgid "Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)"
+msgid ""
+"Accompany it with the information you received as to the offer to distribute "
+"corresponding source code. (This alternative is allowed only for "
+"noncommercial distribution and only if you received the program in object "
+"code or executable form with such an offer, in accord with Subsection b "
+"above.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:260
 #, no-c-format
-msgid "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."
+msgid ""
+"The source code for a work means the preferred form of the work for making "
+"modifications to it. For an executable work, complete source code means all "
+"the source code for all modules it contains, plus any associated interface "
+"definition files, plus the scripts used to control compilation and "
+"installation of the executable. However, as a special exception, the source "
+"code distributed need not include anything that is normally distributed (in "
+"either source or binary form) with the major components (compiler, kernel, "
+"and so on) of the operating system on which the executable runs, unless that "
+"component itself accompanies the executable."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:273
 #, no-c-format
-msgid "If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code."
+msgid ""
+"If distribution of executable or object code is made by offering access to "
+"copy from a designated place, then offering equivalent access to copy the "
+"source code from the same place counts as distribution of the source code, "
+"even though third parties are not compelled to copy the source along with "
+"the object code."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:281
 #, no-c-format
-msgid "<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."
+msgid ""
+"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, "
+"or distribute the Program except as expressly provided under this License. "
+"Any attempt otherwise to copy, modify, sublicense or distribute the Program "
+"is void, and will automatically terminate your rights under this License. "
+"However, parties who have received copies, or rights, from you under this "
+"License will not have their licenses terminated so long as such parties "
+"remain in full compliance."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:292
 #, no-c-format
-msgid "<emphasis role=\"bold\">5.</emphasis> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
+msgid ""
+"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this "
+"License, since you have not signed it. However, nothing else grants you "
+"permission to modify or distribute the Program or its derivative works. "
+"These actions are prohibited by law if you do not accept this License. "
+"Therefore, by modifying or distributing the Program (or any work based on "
+"the Program), you indicate your acceptance of this License to do so, and all "
+"its terms and conditions for copying, distributing or modifying the Program "
+"or works based on it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:304
 #, no-c-format
-msgid "<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."
+msgid ""
+"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program "
+"(or any work based on the Program), the recipient automatically receives a "
+"license from the original licensor to copy, distribute or modify the Program "
+"subject to these terms and conditions. You may not impose any further "
+"restrictions on the recipients' exercise of the rights granted herein. You "
+"are not responsible for enforcing compliance by third parties to this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:315
 #, no-c-format
-msgid "<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
+msgid ""
+"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court "
+"judgment or allegation of patent infringement or for any other reason (not "
+"limited to patent issues), conditions are imposed on you (whether by court "
+"order, agreement or otherwise) that contradict the conditions of this "
+"License, they do not excuse you from the conditions of this License. If you "
+"cannot distribute so as to satisfy simultaneously your obligations under "
+"this License and any other pertinent obligations, then as a consequence you "
+"may not distribute the Program at all. For example, if a patent license "
+"would not permit royalty-free redistribution of the Program by all those who "
+"receive copies directly or indirectly through you, then the only way you "
+"could satisfy both it and this License would be to refrain entirely from "
+"distribution of the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:332
 #, no-c-format
-msgid "If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances."
+msgid ""
+"If any portion of this section is held invalid or unenforceable under any "
+"particular circumstance, the balance of the section is intended to apply and "
+"the section as a whole is intended to apply in other circumstances."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:339
 #, no-c-format
-msgid "It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
+msgid ""
+"It is not the purpose of this section to induce you to infringe any patents "
+"or other property right claims or to contest validity of any such claims; "
+"this section has the sole purpose of protecting the integrity of the free "
+"software distribution system, which is implemented by public license "
+"practices. Many people have made generous contributions to the wide range of "
+"software distributed through that system in reliance on consistent "
+"application of that system; it is up to the author/donor to decide if he or "
+"she is willing to distribute software through any other system and a "
+"licensee cannot impose that choice."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:352
 #, no-c-format
-msgid "This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License."
+msgid ""
+"This section is intended to make thoroughly clear what is believed to be a "
+"consequence of the rest of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:357
 #, no-c-format
-msgid "<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License."
+msgid ""
+"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the "
+"Program is restricted in certain countries either by patents or by "
+"copyrighted interfaces, the original copyright holder who places the Program "
+"under this License may add an explicit geographical distribution limitation "
+"excluding those countries, so that distribution is permitted only in or "
+"among countries not thus excluded. In such case, this License incorporates "
+"the limitation as if written in the body of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:368
 #, no-c-format
-msgid "<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \"any later version\", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
+msgid ""
+"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may "
+"publish revised and/or new versions of the General Public License from time "
+"to time. Such new versions will be similar in spirit to the present version, "
+"but may differ in detail to address new problems or concerns. Each version "
+"is given a distinguishing version number. If the Program specifies a version "
+"number of this License which applies to it and \"any later version\", you "
+"have the option of following the terms and conditions either of that version "
+"or of any later version published by the Free Software Foundation. If the "
+"Program does not specify a version number of this License, you may choose "
+"any version ever published by the Free Software Foundation."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:383
 #, no-c-format
-msgid "<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally."
+msgid ""
+"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of "
+"the Program into other free programs whose distribution conditions are "
+"different, write to the author to ask for permission. For software which is "
+"copyrighted by the Free Software Foundation, write to the Free Software "
+"Foundation; we sometimes make exceptions for this. Our decision will be "
+"guided by the two goals of preserving the free status of all derivatives of "
+"our free software and of promoting the sharing and reuse of software "
+"generally."
 msgstr ""
 
 #. Tag: emphasis
@@ -285,13 +510,31 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:399
 #, no-c-format
-msgid "<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION."
+msgid ""
+"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE "
+"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY "
+"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT "
+"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY "
+"OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE "
+"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. "
+"THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH "
+"YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL "
+"NECESSARY SERVICING, REPAIR OR CORRECTION."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:412
 #, no-c-format
-msgid "<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgid ""
+"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY "
+"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY "
+"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED "
+"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, "
+"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO "
+"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING "
+"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE "
+"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR "
+"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
 msgstr ""
 
 #. Tag: emphasis
@@ -309,87 +552,111 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:434
 #, no-c-format
-msgid "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."
+msgid ""
+"If you develop a new program, and you want it to be of the greatest possible "
+"use to the public, the best way to achieve this is to make it free software "
+"which everyone can redistribute and change under these terms."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:441
 #, no-c-format
-msgid "To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \"copyright\" line and a pointer to where the full notice is found."
+msgid ""
+"To do so, attach the following notices to the program. It is safest to "
+"attach them to the start of each source file to most effectively convey the "
+"exclusion of warranty; and each file should have at least the \"copyright\" "
+"line and a pointer to where the full notice is found."
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:448
 #, no-c-format
 msgid ""
-      "<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable>\n"
-      "Copyright (C) <replaceable>year  name of author</replaceable>\n"
-      "\n"
-      "This program is free software; you can redistribute it and/or\n"
-      "modify it under the terms of the GNU General Public License\n"
-      "as published by the Free Software Foundation; either version 2\n"
-      "of the License, or (at your option) any later version.\n"
-      "\n"
-      "This program is distributed in the hope that it will be useful,\n"
-      "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
-      "MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
-      "GNU General Public License for more details.\n"
-      "\n"
-      "You should have received a copy of the GNU General Public License\n"
-      "along with this program; if not, write to the Free Software\n"
-      "Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA."
+"<replaceable>one line to give the program's name and a brief idea of what it "
+"does.</replaceable>\n"
+"Copyright (C) <replaceable>year  name of author</replaceable>\n"
+"\n"
+"This program is free software; you can redistribute it and/or\n"
+"modify it under the terms of the GNU General Public License\n"
+"as published by the Free Software Foundation; either version 2\n"
+"of the License, or (at your option) any later version.\n"
+"\n"
+"This program is distributed in the hope that it will be useful,\n"
+"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
+"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
+"GNU General Public License for more details.\n"
+"\n"
+"You should have received a copy of the GNU General Public License\n"
+"along with this program; if not, write to the Free Software\n"
+"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, "
+"USA."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:450
 #, no-c-format
-msgid "Also add information on how to contact you by electronic and paper mail."
+msgid ""
+"Also add information on how to contact you by electronic and paper mail."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:455
 #, no-c-format
-msgid "If the program is interactive, make it output a short notice like this when it starts in an interactive mode:"
+msgid ""
+"If the program is interactive, make it output a short notice like this when "
+"it starts in an interactive mode:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:460
 #, no-c-format
 msgid ""
-      "Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable>\n"
-      "Gnomovision comes with absolutely no warranty; for details\n"
-      "type `show w'. This is free software, and you are welcome\n"
-      "to redistribute it under certain conditions; type `show c'\n"
-      "for details."
+"Gnomovision version 69, Copyright (C) <replaceable>year name of author</"
+"replaceable>\n"
+"Gnomovision comes with absolutely no warranty; for details\n"
+"type `show w'. This is free software, and you are welcome\n"
+"to redistribute it under certain conditions; type `show c'\n"
+"for details."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:462
 #, no-c-format
-msgid "The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items &mdash; whatever suits your program."
+msgid ""
+"The hypothetical commands `show w' and `show c' should show the appropriate "
+"parts of the General Public License. Of course, the commands you use may be "
+"called something other than `show w' and `show c'; they could even be mouse-"
+"clicks or menu items &mdash; whatever suits your program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:470
 #, no-c-format
-msgid "You should also get your employer (if you work as a programmer) or your school, if any, to sign a \"copyright disclaimer\" for the program, if necessary. Here is a sample; alter the names:"
+msgid ""
+"You should also get your employer (if you work as a programmer) or your "
+"school, if any, to sign a \"copyright disclaimer\" for the program, if "
+"necessary. Here is a sample; alter the names:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:476
 #, no-c-format
 msgid ""
-      "Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
-      "program `Gnomovision' (which makes passes at compilers) written\n"
-      "by James Hacker.\n"
-      "\n"
-      "<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
-      "Ty Coon, President of Vice"
+"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
+"program `Gnomovision' (which makes passes at compilers) written\n"
+"by James Hacker.\n"
+"\n"
+"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
+"Ty Coon, President of Vice"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:478
 #, no-c-format
-msgid "This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
+msgid ""
+"This General Public License does not permit incorporating your program into "
+"proprietary programs. If your program is a subroutine library, you may "
+"consider it more useful to permit linking proprietary applications with the "
+"library. If this is what you want to do, use the GNU Lesser General Public "
+"License instead of this License."
 msgstr ""
-
diff --git a/po/nl/hardware.po b/po/nl/hardware.po
index c3e0c1251..96af36f01 100644
--- a/po/nl/hardware.po
+++ b/po/nl/hardware.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:7
 #, no-c-format
-msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;."
+msgid ""
+"This section contains information about what hardware you need to get "
+"started with &debian;. You will also find links to further information about "
+"hardware supported by GNU and &arch-kernel;."
 msgstr ""
 
 #. Tag: title
@@ -34,13 +38,23 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;."
+msgid ""
+"&debian; does not impose hardware requirements beyond the requirements of "
+"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
+"architecture or platform to which the Linux or kFreeBSD kernel, libc, "
+"<command>gcc</command>, etc. have been ported, and for which a &debian; port "
+"exists, can run &debian;. Please refer to the Ports pages at <ulink url="
+"\"&url-ports;\"></ulink> for more details on &arch-title; architecture "
+"systems which have been tested with &debian-gnu;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:32
 #, no-c-format
-msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found."
+msgid ""
+"Rather than attempting to describe all the different hardware configurations "
+"which are supported for &arch-title;, this section contains general "
+"information and pointers to where additional information can be found."
 msgstr ""
 
 #. Tag: title
@@ -52,7 +66,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid ""
+"&debian; GNU/Linux &release; supports eleven major architectures and several "
+"variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -430,19 +446,38 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:203
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are "
+"looking for information on any of the other &debian;-supported architectures "
+"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-"
+"Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
+msgid ""
+"The &arch-title; architecture only supports Intel Itanium processors and not "
+"the much more common 64-bit processors from the Intel 64 family (including e."
+"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
+"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
+"userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:223
 #, no-c-format
-msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
+msgid ""
+"This is the first official release of &debian-gnu; for the &arch-title; "
+"architecture. We feel that it has proven itself sufficiently to be released. "
+"However, because it has not had the exposure (and hence testing by users) "
+"that some other architectures have had, you may encounter a few bugs. Use "
+"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any "
+"problems; make sure to mention the fact that the bug is on the &arch-title; "
+"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
+"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
@@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
+#: hardware.xml:522 hardware.xml:575
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -466,13 +502,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:273
 #, no-c-format
-msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
+msgid ""
+"Each distinct ARM architecture requires its own kernel. Because of this the "
+"standard &debian; distribution only supports installation on a number of the "
+"most common platforms. The &debian; userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:282
 #, no-c-format
-msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
+msgid ""
+"Most ARM CPUs may be run in either endian mode (big or little). However, the "
+"majority of current system implementation uses little-endian mode. &debian; "
+"currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
@@ -490,7 +533,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:298
 #, no-c-format
-msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
+msgid ""
+"Intel's I/O Processor (IOP) line is found in a number of products related to "
+"data storage and processing. &debian; currently supports the IOP32x "
+"platform, featuring the IOP 80219 and 32x chips commonly found in Network "
+"Attached Storage (NAS) devices. &debian; explicitly supports two such "
+"devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from "
+"IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -502,7 +551,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:312
 #, no-c-format
-msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
+msgid ""
+"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
+"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
+"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
+"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
+"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
+"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
+"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
+"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
@@ -514,7 +571,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:329
 #, no-c-format
-msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
+msgid ""
+"Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, "
+"Ethernet, SATA, USB, and other functionality in one chip. There are many "
+"Network Attached Storage (NAS) devices on the market that are based on an "
+"Orion chip. We currently support the following Orion based devices: <ulink "
+"url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url="
+"\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
+"cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -526,19 +590,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:344
 #, no-c-format
-msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
+msgid ""
+"The Versatile platform is emulated by QEMU and is therefore a nice way to "
+"test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:363
 #, no-c-format
-msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
+msgid ""
+"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-"
+"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit "
+"processors whereas the 2.0 architecture is targeted to the 64-bit "
+"processors. Some systems are able to run either kernel. In both cases, the "
+"userland is 32-bit. There is the possibility of a 64-bit userland in the "
+"future."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:382
 #, no-c-format
-msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
+msgid ""
+"Complete information concerning supported peripherals can be found at <ulink "
+"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. "
+"This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
@@ -550,19 +625,43 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:391
 #, no-c-format
-msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
+msgid ""
+"Nearly all x86-based (IA-32) processors still in use in personal computers "
+"are supported, including all varieties of Intel's \"Pentium\" series. This "
+"also includes 32-bit AMD and VIA (former Cyrix) processors, and processors "
+"like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:398
 #, no-c-format
-msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
+msgid ""
+"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run "
+"on 386 or earlier processors. Despite the architecture name \"i386\", "
+"support for actual 80386 processors (and their clones) was dropped with the "
+"Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to "
+"avoid this, but in the end it was necessary due a unfortunate series of "
+"issues with the compiler and the kernel, starting with an bug in the C++ ABI "
+"provided by GCC. You should still be able to run &debian; GNU/Linux on "
+"actual 80386 processors if you compile your own kernel and compile all "
+"packages from source, but that is beyond the scope of this manual. </para> </"
+"footnote>. (No version of Linux has ever supported the 286 or earlier chips "
+"in the series.) All i486 and later processors are still supported<footnote> "
+"<para> Many &debian; packages will actually run slightly faster on modern "
+"computers as a positive side effect of dropping support for these old chips. "
+"The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) "
+"which the i386, introduced in 1986, did not have. Previously, these could "
+"not be easily used by most &debian; packages; now they can. </para> </"
+"footnote>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+msgid ""
+"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
+"you will probably want to use the installer for the amd64 architecture "
+"instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
@@ -574,31 +673,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:441
 #, no-c-format
-msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
+msgid ""
+"The system bus is the part of the motherboard which allows the CPU to "
+"communicate with peripherals such as storage devices. Your computer must use "
+"the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called "
+"the VL bus). Essentially all personal computers sold in recent years use one "
+"of these."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:465
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, "
+"Indigo 2 and Challenge S. Since these machines are very similar, whenever "
+"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant "
+"as well. </para></listitem> <listitem><para> SGI IP32: this platform is "
+"generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: "
+"this platform is emulated by QEMU and is therefore a nice way to test and "
+"run &debian; on MIPS if you don't have the hardware. </para></listitem> </"
+"itemizedlist> Complete information regarding supported mips/mipsel machines "
+"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</"
+"ulink>. In the following, only the systems supported by the &debian; "
+"installer will be covered. If you are looking for support for other "
+"subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> "
+"debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
+msgid ""
+"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and "
+"R5000 processors are supported by the &debian; installation system on big "
+"endian MIPS. On SGI IP32, currently only systems based on the R5000 are "
+"supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
+msgid ""
+"Some MIPS machines can be operated in both big and little endian mode. For "
+"little endian MIPS, please read the documentation for the mipsel "
+"architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:523
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are "
+"covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway "
+"Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform "
+"is emulated by QEMU and is therefore a nice way to test and run &debian; on "
+"MIPS if you don't have the hardware. </para></listitem> </itemizedlist> "
+"Complete information regarding supported mips/mipsel machines can be found "
+"at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the "
+"following, only the systems supported by the &debian; installer will be "
+"covered. If you are looking for support for other subarchitectures, please "
+"contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; "
+"mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -610,7 +747,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:553
 #, no-c-format
-msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
+msgid ""
+"All MIPS based Cobalt machines are supported with the exception of the Qube "
+"2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
@@ -628,7 +767,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:576
 #, no-c-format
-msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
+msgid ""
+"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
+"PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +781,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:599
 #, no-c-format
-msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
+msgid ""
+"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -652,7 +795,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:607
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid ""
+"Most systems use this kernel flavour, which supports the PowerPC 601, 603, "
+"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and "
+"including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
@@ -670,19 +816,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:622
 #, no-c-format
-msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
+msgid ""
+"The POWER3 processor is used in older IBM 64-bit server systems: known "
+"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, "
+"and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:628
 #, no-c-format
-msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
+msgid ""
+"The POWER4 processor is used in more recent IBM 64-bit server systems: known "
+"models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:633
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid ""
+"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
+"architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
@@ -694,25 +847,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:669
 #, no-c-format
-msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
+msgid ""
+"Apple (and briefly a few other manufacturers &mdash; Power Computing, for "
+"example) made a series of Macintosh computers based on the PowerPC "
+"processor. For purposes of architecture support, they are categorized as "
+"NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:676
 #, no-c-format
-msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
+msgid ""
+"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI "
+"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld "
+"machines. Those pre-iMac PowerPC models from Apple use a four digit naming "
+"scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:684
 #, no-c-format
-msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
+msgid ""
+"The so called NewWorld PowerMacs are any PowerMacs in translucent colored "
+"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, "
+"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. "
+"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</"
+"quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:692
 #, no-c-format
-msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
+msgid ""
+"Specifications for Apple hardware are available at <ulink url=\"http://www."
+"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older "
+"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/"
+"index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
@@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
+#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
+#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
+#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
+#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
+#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
+#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
+#: hardware.xml:825
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -1084,7 +1261,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:933
 #, no-c-format
-msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
+msgid ""
+"NuBus systems are not currently supported by &debian;/powerpc. The "
+"monolithic Linux/PPC kernel architecture does not have support for these "
+"machines; instead, one must use the MkLinux Mach microkernel, which &debian; "
+"does not yet support. These include the following: <itemizedlist> "
+"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> "
+"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> "
+"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> "
+"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </"
+"itemizedlist> A linux kernel for these machines and limited support is "
+"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1096,19 +1283,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:972
 #, no-c-format
-msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
+msgid ""
+"Macintosh computers using the 680x0 series of processors are <emphasis>not</"
+"emphasis> in the PowerPC family but are instead m68k machines. Those models "
+"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> "
+"family, then the Centris series, and culminate in the Quadras and Performas. "
+"These models usually have a Roman numeral or 3-digit model number such as "
+"Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:981
 #, no-c-format
-msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
+msgid ""
+"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, "
+"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, "
+"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra "
+"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the "
+"Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:989
 #, no-c-format
-msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
+msgid ""
+"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs "
+"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, "
+"please see the section above)."
 msgstr ""
 
 #. Tag: title
@@ -1120,7 +1321,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1006
 #, no-c-format
-msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
+msgid ""
+"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
+"Your machine needs to support the z/Architecture, 64-bit support is "
+"mandatory. The userland of the s390 port is still compiled for ESA/390, "
+"though. All zSeries and System z hardware is fully supported. &arch-title; "
+"support software is included from the kernel 3.1 development stream. The "
+"most current information about IBM's Linux support can be found at the "
+"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
+"development_technical.html\"> Linux on <trademark class=\"registered"
+"\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1132,7 +1342,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1024
 #, no-c-format
-msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
+msgid ""
+"PAV and HyperPAV are supported transparently, multipathing is not needed to "
+"take advantage of these storage system features. Be sure to configure the "
+"devices during DASD device selection. The alias devices will not be offered "
+"neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
@@ -1144,7 +1358,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1041
 #, no-c-format
-msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
+msgid ""
+"Sparc-based hardware is divided into a number of different subarchitectures, "
+"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u "
+"or sun4v. The following list describes what machines they include and what "
+"level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
@@ -1156,13 +1374,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1054
 #, no-c-format
-msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
+msgid ""
+"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a "
+"complete list of machines belonging to these subarchitectures, please "
+"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation"
+"\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1061
 #, no-c-format
-msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
+msgid ""
+"The last &debian; release to support sparc32 was Etch, but even then only "
+"for sun4m systems. Support for the other 32-bits subarchitectures had "
+"already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
@@ -1174,7 +1399,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1073
 #, no-c-format
-msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
+msgid ""
+"This subarchitecture includes all 64-bit machines (sparc64) based on the "
+"UltraSparc processor and its clones. Most of the machines are well "
+"supported, even though for some you may experience problems booting from CD "
+"due to firmware or bootloader bugs (this problem may be worked around by "
+"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP "
+"configurations respectively."
 msgstr ""
 
 #. Tag: term
@@ -1186,13 +1417,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1088
 #, no-c-format
-msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
+msgid ""
+"This is the newest addition to the Sparc family, which includes machines "
+"based on the Niagara multi-core CPUs. At the moment such CPUs are only "
+"available in T1000 and T2000 servers by Sun, and are well supported. Use the "
+"sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1099
 #, no-c-format
-msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
+msgid ""
+"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
+"not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
@@ -1204,7 +1441,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1109
 #, no-c-format
-msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
+msgid ""
+"From a technical point of view, laptops are normal PCs, so all information "
+"regarding PC systems applies to laptops as well. Installations on laptops "
+"nowadays usually work out of the box, including things like automatically "
+"suspending the system on closing the lid and laptop specfic hardware buttons "
+"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
+"Nonetheless sometimes the hardware vendors use specialized or proprietary "
+"hardware for some laptop-specific functions which might not be supported. To "
+"see if your particular laptop works well with GNU/Linux, see for example the "
+"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1216,61 +1462,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1127
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. Having multiple "
+"processors in a computer was originally only an issue for high-end server "
+"systems but has become quite common in recent years even for rather low-end "
+"desktop computers and laptops with the introduction of so called "
+"<quote>multi-core</quote> processors. These contain two or more processor "
+"units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1137
 #, no-c-format
-msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
+msgid ""
+"The standard &debian; &release; kernel image has been compiled with SMP "
+"support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1148
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. The standard "
+"&debian; &release; kernel image has been compiled with <firstterm>SMP-"
+"alternatives</firstterm> support. This means that the kernel will detect the "
+"number of processors (or processor cores) and will automatically deactivate "
+"SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1157
 #, no-c-format
-msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Having multiple processors in a computer was originally only an issue for "
+"high-end server systems but has become quite common in recent years even for "
+"rather low-end desktop computers and laptops with the introduction of so "
+"called <quote>multi-core</quote> processors. These contain two or more "
+"processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1165
 #, no-c-format
-msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
+msgid ""
+"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
+"not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1175
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. However, the "
+"standard &debian; &release; kernel image does not support SMP. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1184
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a "
+"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this "
+"time (kernel version &kernelversion;) the way you enable SMP is to select "
+"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</"
+"quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1198
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture, and is supported "
+"by a precompiled &debian; kernel image. Depending on your install media, "
+"this SMP-capable kernel may or may not be installed by default. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1208
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
+msgid ""
+"In order to take advantage of multiple processors, you should check to see "
+"if a kernel package that supports SMP is installed, and if not, choose an "
+"appropriate kernel package."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1214
 #, no-c-format
-msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"You can also build your own customized kernel to support SMP.<phrase arch="
+"\"linux-any\"> You can find a discussion of how to do this in <xref linkend="
+"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way "
+"you enable SMP is to select <quote>&smp-config-option;</quote> in the "
+"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1282,13 +1575,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1226
 #, no-c-format
-msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
+msgid ""
+"&debian;'s support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. On modern PCs, having a graphical "
+"display usually works out of the box. Whether advanced graphics card "
+"features such as 3D-hardware acceleration or hardware-accelerated video are "
+"available, depends on the actual graphics hardware used in the system and in "
+"some cases on the installation of additional <quote>firmware</quote> images "
+"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
+"been reports about hardware on which installation of additional graphics "
+"card firmware was required even for basic graphics support, but these have "
+"been rare exceptions."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1239
 #, no-c-format
-msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
+msgid ""
+"Details on supported graphics cards and pointing devices can be found at "
+"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
+"version &x11ver;."
 msgstr ""
 
 #. Tag: para
@@ -1300,13 +1606,31 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1249
 #, no-c-format
-msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
+msgid ""
+"Most graphics options commonly found on Sparc-based machines are supported. "
+"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, "
+"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), "
+"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards "
+"(glint driver). To use an Elite3D card with X.org you additionally need to "
+"install the <classname>afbinit</classname> package, and read the "
+"documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1259
 #, no-c-format
-msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
+msgid ""
+"It is not uncommon for a Sparc machine to have two graphics cards in a "
+"default configuration. In such a case there is a possibility that the Linux "
+"kernel will not direct its output to the card initially used by the "
+"firmware. The lack of output on the graphical console may then be mistaken "
+"for a hang (usually the last message seen on console is 'Booting Linux...'). "
+"One possible solution is to physically remove one of the video cards; "
+"another option is to disable one of the cards using a kernel boot parameter. "
+"Also, if graphical output is not required or desired, serial console may be "
+"used as an alternative. On some systems use of serial console can be "
+"activated automatically by disconnecting the keyboard before booting the "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -1318,13 +1642,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1282
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
+msgid ""
+"Almost any network interface card (NIC) supported by the &arch-kernel; "
+"kernel should also be supported by the installation system; drivers should "
+"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
+"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
+"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1292
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+msgid ""
+"This includes a lot of generic PCI cards (for systems that have PCI) and the "
+"following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
@@ -1384,7 +1715,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1349
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
+msgid ""
+"On &arch-title;, most built-in Ethernet devices are supported and modules "
+"for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
@@ -1402,31 +1735,52 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1362
 #, no-c-format
-msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
+msgid ""
+"Wireless networking is in general supported as well and a growing number of "
+"wireless adapters are supported by the official &arch-kernel; kernel, "
+"although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1369
 #, no-c-format
-msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
+msgid ""
+"If firmware is needed, the installer will prompt you to load firmware. See "
+"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
+"firmware during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1374
 #, no-c-format
-msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
+msgid ""
+"Wireless NICs that are not supported by the official &arch-kernel; kernel "
+"can generally be made to work under &debian-gnu;, but are not supported "
+"during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1379
 #, no-c-format
-msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
+msgid ""
+"If there is a problem with wireless and there is no other NIC you can use "
+"during the installation, it is still possible to install &debian-gnu; using "
+"a full CD-ROM or DVD image. Select the option to not configure a network and "
+"install using only the packages available from the CD/DVD. You can then "
+"install the driver and firmware you need after the installation is completed "
+"(after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1389
 #, no-c-format
-msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
+msgid ""
+"In some cases the driver you need may not be available as a &debian; "
+"package. You will then have to look if there is source code available in the "
+"internet and compile the driver yourself. How to do this is outside the "
+"scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, "
+"your last resort is to use the <classname>ndiswrapper</classname> package, "
+"which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1438,7 +1792,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1404
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid ""
+"There are a couple of issues with specific network cards that are worth "
+"mentioning here."
 msgstr ""
 
 #. Tag: title
@@ -1450,19 +1806,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1413
 #, no-c-format
-msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
+msgid ""
+"There are various PCI network cards that have the same PCI identification, "
+"but are supported by related, but different drivers. Some cards work with "
+"the <literal>tulip</literal> driver, others with the <literal>dfme</literal> "
+"driver. Because they have the same identification, the kernel cannot "
+"distinguish between them and it is not certain which driver will be loaded. "
+"If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1423
 #, no-c-format
-msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
+msgid ""
+"This is a common problem on Netra systems with a Davicom (DEC-Tulip "
+"compatible) NIC. In that case the <literal>tulip</literal> driver is "
+"probably the correct one. You can prevent this issue by blacklisting the "
+"wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1431
 #, no-c-format
-msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
+msgid ""
+"An alternative solution during the installation is to switch to a shell and "
+"unload the wrong driver module using <userinput>modprobe -r "
+"<replaceable>module</replaceable></userinput> (or both, if they are both "
+"loaded). After that you can load the correct module using "
+"<userinput>modprobe <replaceable>module</replaceable></userinput>. Note that "
+"the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
@@ -1474,7 +1846,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1446
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid ""
+"The <literal>cassini</literal> network driver does not work with Sun B100 "
+"blade systems."
 msgstr ""
 
 #. Tag: title
@@ -1486,7 +1860,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1462
 #, no-c-format
-msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
+msgid ""
+"Support for braille displays is determined by the underlying support found "
+"in <classname>brltty</classname>. Most displays work under "
+"<classname>brltty</classname>, connected via either a serial port, USB or "
+"bluetooth. Details on supported braille devices can be found on the <ulink "
+"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
+"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
@@ -1498,7 +1878,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1477
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
+msgid ""
+"Support for hardware speech synthesis devices is determined by the "
+"underlying support found in <classname>speakup</classname>. "
+"<classname>speakup</classname> only supports integrated boards and external "
+"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
+"are supported). Details on supported hardware speech synthesis devices can "
+"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
+"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
+"classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
@@ -1510,25 +1898,37 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1498
 #, no-c-format
-msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
+msgid ""
+"&arch-kernel; supports a large variety of hardware devices such as mice, "
+"printers, scanners, PCMCIA and USB devices. However, most of these devices "
+"are not required while installing the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1504
 #, no-c-format
-msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
+msgid ""
+"USB hardware generally works fine. On some very old PC systems some USB "
+"keyboards may require additional configuration (see <xref linkend=\"hardware-"
+"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
+"any specific configuration."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1513
 #, no-c-format
-msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
+msgid ""
+"Package installations from XPRAM and tape are not supported by this system. "
+"All packages that you want to install need to be available on a DASD or over "
+"the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1519
 #, no-c-format
-msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Cobalt RaQ has no support for additional devices but the Qube has one "
+"PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -1540,31 +1940,63 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1532
 #, no-c-format
-msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
+msgid ""
+"Besides the availability of a device driver, some hardware also requires so-"
+"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> "
+"to be loaded into the device before it can become operational. This is most "
+"common for network interface cards (especially wireless NICs), but for "
+"example some USB devices and even some hard disk controllers also require "
+"firmware. With many graphics cards, basic functionality is available without "
+"additional firmware, but the use of advanced features requires an "
+"appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1543
 #, no-c-format
-msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
+msgid ""
+"On many older devices which require firmware to work, the firmware file was "
+"permanently placed in an EEPROM/Flash chip on the device itself by the "
+"manufacturer. Nowadays most new devices do not have the firmware embedded "
+"this way anymore, so the firmware file must be uploaded into the device by "
+"the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1551
 #, no-c-format
-msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
+msgid ""
+"In most cases firmware is non-free according to the criteria used by the "
+"&debian-gnu; project and thus cannot be included in the main distribution or "
+"in the installation system. If the device driver itself is included in the "
+"distribution and if &debian-gnu; legally can distribute the firmware, it "
+"will often be available as a separate package from the non-free section of "
+"the archive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1560
 #, no-c-format
-msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
+msgid ""
+"However, this does not mean that such hardware cannot be used during an "
+"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
+"firmware files or packages containing firmware from a removable medium, such "
+"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
+"information on how to load firmware files or packages during the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1569
 #, no-c-format
-msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
+msgid ""
+"If the &d-i; prompts for a firmware file and you do not have this firmware "
+"file available or do not want to install a non-free firmware file on your "
+"system, you can try to proceed without loading the firmware. There are "
+"several cases where a driver prompts for additional firmware because it may "
+"be needed under certain circumstances, but the device does work without it "
+"on most systems (this e.g. happens with certain network cards using the tg3 "
+"driver)."
 msgstr ""
 
 #. Tag: title
@@ -1576,19 +2008,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1588
 #, no-c-format
-msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
+msgid ""
+"There are several vendors, who ship systems with &debian; or other "
+"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</"
+"ulink>. You might pay more for the privilege, but it does buy a level of "
+"peace of mind, since you can be sure that the hardware is well-supported by "
+"GNU/Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1596
 #, no-c-format
-msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
+msgid ""
+"If you do have to buy a machine with Windows bundled, carefully read the "
+"software license that comes with Windows; you may be able to reject the "
+"license and obtain a rebate from your vendor. Searching the Internet for "
+"<quote>windows refund</quote> may get you some useful information to help "
+"with that."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1604
 #, no-c-format
-msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
+"even a used system, it is still important to check that your hardware is "
+"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
+"the references found above. Let your salesperson (if any) know that you're "
+"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
+"vendors."
 msgstr ""
 
 #. Tag: title
@@ -1600,31 +2048,67 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1616
 #, no-c-format
-msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
+msgid ""
+"Some hardware manufacturers simply won't tell us how to write drivers for "
+"their hardware. Others won't allow us access to the documentation without a "
+"non-disclosure agreement that would prevent us from releasing the driver's "
+"source code, which is one of the central elements of free software. Since we "
+"haven't been granted access to usable documentation on these devices, they "
+"simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1626
 #, no-c-format
-msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
+msgid ""
+"In many cases there are standards (or at least some de-facto standards) "
+"describing how an operating system and its device drivers communicate with a "
+"certain class of devices. All devices which comply to such a (de-facto-)"
+"standard can be used with a single generic device driver and no device-"
+"specific drivers are required. With some kinds of hardware (e.g. USB "
+"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
+"mass storage devices like USB flash disks and memory card readers) this "
+"works very well and practically every device sold in the market is standards-"
+"compliant."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1638
 #, no-c-format
-msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
+msgid ""
+"In other fields, among them e.g. printers, this is unfortunately not the "
+"case. While there are many printers which can be addressed via a small set "
+"of (de-facto-)standard control languages and therefore can be made to work "
+"without problems in any operating system, there are quite a few models which "
+"only understand proprietary control commands for which no usable "
+"documentation is available and therefore either cannot be used at all on "
+"free operating systems or can only be used with a vendor-supplied closed-"
+"source driver."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1649
 #, no-c-format
-msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
+msgid ""
+"Even if there is a vendor-provided closed-source driver for such hardware "
+"when purchasing the device, the practical lifespan of the device is limited "
+"by driver availability. Nowadays product cycles have become short and it is "
+"not uncommon that a short time after a consumer device has ceased "
+"production, no driver updates get made available any more by the "
+"manufacturer. If the old closed-source driver does not work anymore after a "
+"system update, an otherwise perfectly working device becomes unusable due to "
+"lacking driver support and there is nothing that can be done in this case. "
+"You should therefore avoid buying closed hardware in the first place, "
+"regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1662
 #, no-c-format
-msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
+msgid ""
+"You can help improve this situation by encouraging manufacturers of closed "
+"hardware to release the documentation and other resources necessary for us "
+"to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
@@ -1636,7 +2120,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1679
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
+msgid ""
+"This section will help you determine which different media types you can use "
+"to install &debian;. There is a whole chapter devoted to media, <xref "
+"linkend=\"install-methods\"/>, which lists the advantages and disadvantages "
+"of each media type. You may want to refer back to this page once you reach "
+"that section."
 msgstr ""
 
 #. Tag: title
@@ -1648,7 +2137,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
+msgid ""
+"In some cases, you'll have to do your first boot from floppy disks. "
+"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch "
+"floppy drive."
 msgstr ""
 
 #. Tag: para
@@ -1666,7 +2158,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1705
 #, no-c-format
-msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
+msgid ""
+"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-"
+"ROMs and DVD-ROMs, because both technologies are really the same from the "
+"operating system's point of view."
 msgstr ""
 
 #. Tag: para
@@ -1684,7 +2179,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1719
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid ""
+"USB CD-ROM drives are also supported, as are FireWire devices that are "
+"supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
@@ -1696,7 +2193,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1728
 #, no-c-format
-msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
+msgid ""
+"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of "
+"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM "
+"drives sold on the PC market do not have this capability. If your CD-ROM "
+"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</"
+"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. "
+"To start the install, simply choose the <quote>System installation</quote> "
+"entry in the firmware."
 msgstr ""
 
 #. Tag: title
@@ -1708,7 +2212,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1744
 #, no-c-format
-msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
+msgid ""
+"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
+"cheap storage device. Most modern computer systems also allow booting the &d-"
+"i; from such a stick. Many modern computer systems, in particular netbooks "
+"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
+"from USB media ist the standard way of installing a new operating system on "
+"them."
 msgstr ""
 
 #. Tag: title
@@ -1720,19 +2230,36 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1758
 #, no-c-format
-msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
+msgid ""
+"The network can be used during the installation to retrieve files needed for "
+"the installation. Whether the network is used or not depends on the "
+"installation method you choose and your answers to certain questions that "
+"will be asked during the installation. The installation system supports most "
+"types of network connections (including PPPoE, but not ISDN or PPP), via "
+"either HTTP or FTP. After the installation is completed, you can also "
+"configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1768
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> the installation system over the "
+"network without needing any local media like CDs/DVDs or USB sticks. If you "
+"already have a netboot-infrastructure available (i.e. you are already "
+"running DHCP and TFTP services in your network), this allows an easy and "
+"fast deployment of a large number of machines. Setting up the necessary "
+"infrastructure requires a certain level of technical experience, so this is "
+"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the "
+"preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1781
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+msgid ""
+"Diskless installation, using network booting from a local area network and "
+"NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
@@ -1744,13 +2271,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1792
 #, no-c-format
-msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
+msgid ""
+"Booting the installation system directly from a hard disk is another option "
+"for many architectures. This will require some other operating system to "
+"load the installer onto the hard disk. This method is only recommended for "
+"special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1799
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid ""
+"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
+"can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
@@ -1762,7 +2295,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1810
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian-gnu; without using the &d-i; described in the rest of this manual. "
+"This kind of install may be useful for users with otherwise unsupported "
+"hardware or on hosts which can't afford downtime. If you are interested in "
+"this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This "
+"installation method is only recommended for advanced users when no other "
+"installation method is available."
 msgstr ""
 
 #. Tag: title
@@ -1774,43 +2314,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1825
 #, no-c-format
-msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
+msgid ""
+"The &debian; installer contains a kernel which is built to maximize the "
+"number of systems it runs on."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1829
 #, no-c-format
-msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+msgid ""
+"Generally, the &debian; installation system includes support for IDE (also "
+"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
+"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
+"(VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1846
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. The following SCSI drivers are supported in the default kernel: "
+"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> "
+"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec "
+"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></"
+"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also "
+"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC "
+"Processors FAQ</ulink> for more information on SPARC hardware supported by "
+"the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1879
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support floppies on "
+"CHRP systems at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support the floppy "
+"drive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1891
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1896
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This means that FBA and ECKD DASDs are supported with the old "
+"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
@@ -1822,12 +2388,22 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1915
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space to perform a normal installation. Note that these are fairly "
+"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-"
+"hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1922
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgid ""
+"Installation on systems with less memory<footnote condition=\"gtk\"> <para> "
+"Installation images that support the graphical installer require more memory "
+"than images that support only the textual installer and should not be used "
+"on systems with less than &minimum-memory; of memory. If there is a choice "
+"between booting the regular and the graphical installer, the former should "
+"be selected. </para> </footnote> or disk space available may be possible but "
+"is only advised for experienced users."
 msgstr ""
-
diff --git a/po/nl/install-methods.po b/po/nl/install-methods.po
index c164d8428..6f56f6790 100644
--- a/po/nl/install-methods.po
+++ b/po/nl/install-methods.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,1149 +29,1719 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian-gnu; is from an Official &debian; CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/DVD-ROM images from a &debian; mirror and make your own set, if you have a fast network connection and a CD/DVD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, which is the case on all modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/>. Much effort has been expended to ensure the most-used files are on the first CDs and DVDs, so that a basic desktop installation can be done with only the first DVD or - to a limited extent - even with only the first CD."
+msgid ""
+"By far the easiest way to install &debian-gnu; is from an Official &debian; "
+"CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-"
+"debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/"
+"DVD-ROM images from a &debian; mirror and make your own set, if you have a "
+"fast network connection and a CD/DVD burner (see the <ulink url=\"&url-"
+"debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;"
+"\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; "
+"CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, "
+"which is the case on all modern PCs</phrase>, you can skip right to <xref "
+"linkend=\"boot-installer\"/>. Much effort has been expended to ensure the "
+"most-used files are on the first CDs and DVDs, so that a basic desktop "
+"installation can be done with only the first DVD or - to a limited extent - "
+"even with only the first CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid ""
+"As CDs have a rather limited capacity by today's standards, not all "
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid ""
+"If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
+"relevant on very old PC systems)</phrase>, but you do have a CD set, you can "
+"use an alternative strategy such as <phrase condition=\"supports-floppy-boot"
+"\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition="
+"\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net "
+"boot,</phrase> or manually loading the kernel from the CD to initially boot "
+"the system installer. The files you need for booting by another means are "
+"also on the CD; the &debian; network archive and CD folder organization are "
+"identical. So when archive file paths are given below for particular files "
+"you need for booting, look for those files in the same directories and "
+"subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
-msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a &debian; mirror using FTP, be sure to download "
+"the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
-msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each &debian; mirror in the directory "
+"<ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
-msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
+msgid ""
+"A firmware image is provided for the Thecus N2100 which will automatically "
+"boot <classname>debian-installer</classname>. This image can be installed "
+"using the Thecus firmware upgrade process. This firmware image can be "
+"obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
-msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
+msgid ""
+"The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
+"on which you intend to install &debian;. These images can be obtained from "
+"&glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
-msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
+msgid ""
+"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
+"disk on which you intend to install &debian;. These images can be obtained "
+"from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
-msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
+msgid ""
+"A firmware image is provided for the HP mv2120 which will automatically boot "
+"<classname>debian-installer</classname>. This image can be installed with "
+"uphpmvault on Linux and other systems and with the HP Media Vault Firmware "
+"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-"
+"firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
-msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
+msgid ""
+"The installation files for the QNAP Turbo Station consist of a kernel and "
+"ramdisk as well as a script to write these images to flash. You can obtain "
+"the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
+"kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
-msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
+msgid ""
+"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
+"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
+"obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
-msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
+msgid ""
+"The installation files for LaCie NASes (Network Space v2, Network Space Max "
+"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
+"consist of a kernel and initrd for U-Boot. You can obtain these files from "
+"&lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
-msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
+msgid ""
+"Bootable floppy disks are generally used as a last resort to boot the "
+"installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
-msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
+msgid ""
+"Booting the installer from floppy disk reportedly fails on Mac USB floppy "
+"drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images. This "
+"section describes how to create floppies from disk images on different "
+"platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
-msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
+msgid ""
+"Before you can create the floppies, you will first need to download them "
+"from one of the &debian; mirrors, as explained in <xref linkend="
+"\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an "
+"installation CD-ROM or DVD, the floppy images may also be included on the CD/"
+"DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
-msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
+msgid ""
+"No matter which method you use to create your floppies, you should remember "
+"to flip the write-protect tab on the floppies once you have written them, to "
+"ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
-      "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
-      "$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-      "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> (on Solaris, use <command>eject</command>, see the manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:337
+"To write the floppy disk image files to the floppy disks, you will probably "
+"need root access to the system. Place a good, blank floppy in the floppy "
+"drive. Next, use the command <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly "
+"used name of the floppy disk device, it may be different on your "
+"workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</"
+"filename>)</phrase>. The command may return to the prompt before Unix has "
+"finished writing the floppy disk, so look for the disk-in-use light on the "
+"floppy drive and be sure that the light is out and the disk has stopped "
+"revolving before you remove it from the drive. On some systems, you'll have "
+"to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> "
+"(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:336
 #, no-c-format
-msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+msgid ""
+"Some systems attempt to automatically mount a floppy disk when you place it "
+"in the drive. You might have to disable this feature before the workstation "
+"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
+"management to get raw access to the floppy. First, make sure that the floppy "
+"is auto-mounted (using <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
-msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 or amd64 machine, you can use one of the "
+"following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> programs can "
+"be used under MS-DOS. To use these programs, first make sure that you are "
+"booted into DOS. Trying to use these programs from within a DOS box in "
+"Windows, or double-clicking on these programs from the Windows Explorer is "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
-msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
+msgid ""
+"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
+"ME, XP and probably later versions. To use it you will need to unpack diskio."
+"dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
-msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official &debian; CD-ROMs under the "
+"<filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
-msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
+msgid ""
+"An AppleScript, <application>Make &debian; Floppy</application>, is "
+"available for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on "
+"your desktop, and then drag any floppy image file to it. You must have "
+"Applescript installed and enabled in your extensions manager. Disk Copy will "
+"ask you to confirm that you wish to erase the floppy and proceed to write "
+"the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> file is an example of a floppy image. Use one of the following "
+"methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian-gnu; CD, then the Type and Creator are already set "
+"correctly. The following <command>Creator-Changer</command> steps are only "
+"necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> image file from the "
+"resulting dialog. It will ask you to insert a floppy, then ask if you really "
+"want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
-msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
+msgid ""
+"To prepare the USB stick, you will need a system where GNU/Linux is already "
+"running and where USB is supported. With current GNU/Linux systems the USB "
+"stick should be automatically recognized when you insert it. If it is not "
+"you should check that the usb-storage kernel module is loaded. When the USB "
+"stick is inserted, it will be mapped to a device named <filename>/dev/sdX</"
+"filename>, where the <quote>X</quote> is a letter in the range a-z. You "
+"should be able to see to which device the USB stick was mapped by running "
+"the command <command>dmesg</command> after inserting it. To write to your "
+"stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
-msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
+msgid ""
+"The procedures described in this section will destroy anything already on "
+"the device! Make very sure that you use the correct device name for your USB "
+"stick. If you use the wrong device the result could be that all information "
+"on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
-msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
+msgid ""
+"Debian CD and DVD images can now be written directly a USB stick, which is a "
+"very easy way to make a bootable USB stick. Simply choose a CD or DVD image "
+"that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to "
+"get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
-msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
+msgid ""
+"Alternatively, for very small USB sticks, only a few megabytes in size, you "
+"can download the <filename>mini.iso</filename> image from the "
+"<filename>netboot</filename> directory (at the location mentioned in <xref "
+"linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
-msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
+msgid ""
+"A special method can be used to add firmware to the <filename>mini.iso</"
+"filename>. First, write the <filename>mini.iso</filename> to the USB stick. "
+"Next obtain the necessary firmware files. See <xref linkend=\"loading-"
+"firmware\"/> for more information about firmware. Now unplug and replug the "
+"USB stick, and two partitions should now be visible on it. You should mount "
+"the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
-      "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
-      "# cd /mnt\n"
-      "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
-      "# cd /\n"
-      "# umount"
+"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
+"# cd /mnt\n"
+"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
+"# cd /\n"
+"# umount"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
-msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
+msgid ""
+"The CD or DVD image you choose should be written directly to the USB stick, "
+"overwriting its current contents. For example, when using an existing GNU/"
+"Linux system, the CD or DVD image file can be written to a USB stick as "
+"follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
-      "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
-      "<prompt>#</prompt> <userinput>sync</userinput>"
+"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
+"<replaceable>sdX</replaceable></userinput>\n"
+"<prompt>#</prompt> <userinput>sync</userinput>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
-msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
+msgid ""
+"Simply writing the CD or DVD image to USB like this should work fine for "
+"most users. The other options below are more complex, mainly for people with "
+"specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
-msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"An alternative way to set up your USB stick is to manually copy the "
+"installer files, and also a CD image to it. Note that the USB stick should "
+"be at least 1 GB in size (smaller setups are possible if you follow <xref "
+"linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
-msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
+msgid ""
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) <phrase arch="
+"\"x86\">as well as <classname>syslinux</classname> and its configuration "
+"file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</"
+"classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
-msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
+msgid ""
+"Note that, although convenient, this method does have one major "
+"disadvantage: the logical size of the device will be limited to 1 GB, even "
+"if the capacity of the USB stick is larger. You will need to repartition the "
+"USB stick and create new file systems to get its full capacity back if you "
+"ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
-msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
+msgid ""
+"Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
+"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract "
+"the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
-msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"After that, mount the USB memory stick <phrase arch=\"x86\">"
+"(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</"
+"phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</"
+"replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch="
+"\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS "
+"filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
+"CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
+"are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
-msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
+msgid ""
+"If you like more flexibility or just want to know what's going on, you "
+"should use the following method to put the files on your stick. One "
+"advantage of using this method is that &mdash; if the capacity of your USB "
+"stick is large enough &mdash; you have the option of copying a full CD ISO "
+"image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
-msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to set up the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
-      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
-      "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
+"Since most USB sticks come pre-configured with a single FAT16 partition, you "
+"probably won't have to repartition or reformat the stick. If you have to do "
+"that anyway, use <command>cfdisk</command> or any other partitioning tool to "
+"create a FAT16 partition<footnote> <para> Don't forget to set the "
+"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR "
+"using: <informalexample><screen>\n"
+"# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+"</screen></informalexample> The <command>install-mbr</command> command is "
+"contained in the <classname>mbr</classname> &debian; package. Then create "
+"the filesystem using: <informalexample><screen>\n"
+"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. Although any boot loader (e.g. <classname>lilo</"
+"classname>) should work, it's convenient to use <classname>syslinux</"
+"classname>, since it uses a FAT16 partition and can be reconfigured by just "
+"editing a text file. Any operating system which supports the FAT file system "
+"can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
-      "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
-      "# syslinux /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>syslinux</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"To put <classname>syslinux</classname> on the FAT16 partition on your USB "
+"stick, install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
+"# syslinux /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>syslinux</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick: "
+"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or "
+"<filename>linux</filename> (kernel binary) </para></listitem> "
+"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </"
+"para></listitem> </itemizedlist> You can choose between either the regular "
+"version or the graphical version of the installer. The latter can be found "
+"in the <filename>gtk</filename> subdirectory. If you want to rename the "
+"files, please note that <classname>syslinux</classname> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
-      "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
-      "default vmlinuz\n"
-      "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
+"Next you should create a <filename>syslinux.cfg</filename> configuration "
+"file, which at a bare minimum should contain the following two lines (change "
+"the name of the kernel binary to <quote><filename>linux</filename></quote> "
+"if you used a <filename>netboot</filename> image): "
+"<informalexample><screen>\n"
+"default vmlinuz\n"
+"append initrd=initrd.gz\n"
+"</screen></informalexample> For the graphical installer you should add "
+"<userinput>vga=788</userinput> to the second line. Other parameters can be "
+"appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
-msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgid ""
+"To enable the boot prompt to permit further parameter appending, add a "
+"<userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
-msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
+msgid ""
+"If you used an <filename>hd-media</filename> image, you should now copy the "
+"ISO file of a &debian; ISO image<footnote> <para> You can use either a "
+"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure "
+"to select one that fits. Note that the <quote>netboot <filename>mini.iso</"
+"filename></quote> image is not usable for this purpose. </para> </footnote> "
+"onto the stick. When you are done, unmount the USB memory stick "
+"(<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
-      "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
-      "$ hformat /dev/<replaceable>sdX2</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> &debian; package."
+"Most USB sticks do not come pre-configured in such a way that Open Firmware "
+"can boot from them, so you will need to repartition the stick. On Mac "
+"systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></"
+"userinput>, initialise a new partition map using the <userinput>i</"
+"userinput> command, and create a new partition of type Apple_Bootstrap using "
+"the <userinput>C</userinput> command. (Note that the first \"partition\" "
+"will always be the partition map itself.) Then type "
+"<informalexample><screen>\n"
+"$ hformat /dev/<replaceable>sdX2</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> boot loader can be "
+"installed on an HFS filesystem and can be reconfigured by just editing a "
+"text file. Any operating system which supports the HFS file system can be "
+"used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
-      "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
-      "$ hmount /dev/<replaceable>sdX2</replaceable>\n"
-      "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
-      "$ hattrib -c UNIX -t tbxi :yaboot\n"
-      "$ hattrib -b :\n"
-      "$ humount\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:857
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
+"$ hmount /dev/<replaceable>sdX2</replaceable>\n"
+"$ hcopy -r /usr/lib/yaboot/yaboot :\n"
+"$ hattrib -c UNIX -t tbxi :yaboot\n"
+"$ hattrib -b :\n"
+"$ humount\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be otherwise mounted during this procedure. "
+"This procedure writes the boot loader to the partition, and uses the HFS "
+"utilities to mark it in such a way that Open Firmware will boot it. Having "
+"done this, the rest of the USB stick may be prepared using the normal Unix "
+"utilities."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:856
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
-      "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
-      "default=install\n"
-      "root=/dev/ram\n"
-      "\n"
-      "message=/boot.msg\n"
-      "\n"
-      "image=/vmlinux\n"
-      "        label=install\n"
-      "        initrd=/initrd.gz\n"
-      "        initrd-size=10000\n"
-      "        read-only\n"
-      "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
+"default=install\n"
+"root=/dev/ram\n"
+"\n"
+"message=/boot.msg\n"
+"\n"
+"image=/vmlinux\n"
+"        label=install\n"
+"        initrd=/initrd.gz\n"
+"        initrd-size=10000\n"
+"        read-only\n"
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
-msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
+msgid ""
+"The installer may be booted using boot files placed on an existing hard "
+"drive partition, either launched from another operating system or by "
+"invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
-msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+msgid ""
+"The installer cannot boot from files on an HFS+ file system. MacOS System "
+"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To "
+"determine whether your existing file system is HFS+, select <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
-msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
+msgid ""
+"At boot time, both bootloaders support loading in memory not only the "
+"kernel, but also a disk image. This RAM disk can be used as the root file-"
+"system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
-msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the &debian; archives to a convenient location "
+"on your hard drive (note that LILO can not boot from files on an NTFS file "
+"system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
-msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
+msgid ""
+"This section explains how to prepare your hard drive for booting the "
+"installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
-msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
+msgid ""
+"Copy the following directories from a &debian; CD image to <filename>c:\\</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
-msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
+msgid ""
+"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your &debian; installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on &debian; http/ftp mirrors and official &debian; CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
-msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+msgid ""
+"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
+"well as loading ELF binaries directly from the hard disk. These machines "
+"will boot Linux directly via <command>yaboot</command>, which supports "
+"loading a kernel and RAMdisk directly from an ext2 partition, as well as "
+"dual-booting with MacOS. Hard disk booting of the installer is particularly "
+"appropriate for newer machines without floppy drives. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (not move) the following four files which you "
+"downloaded earlier from the &debian; archives, onto the root level of your "
+"hard drive (this can be accomplished by <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the <command>L</command> command to check for the partition number. You "
+"will need this partition number for the command you type at the Open "
+"Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
-msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
+msgid ""
+"If your machine is connected to a local area network, you may be able to "
+"boot it over the network from another machine, using TFTP. If you intend to "
+"boot the installation system from another machine, the boot files will need "
+"to be placed in specific locations on that machine, and the machine "
+"configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
-msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
+msgid ""
+"You need to set up a TFTP server, and for many machines a DHCP server<phrase "
+"condition=\"supports-rarp\">, or RARP server</phrase><phrase condition="
+"\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol.</phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image.</phrase> The DHCP "
+"(Dynamic Host Configuration Protocol) is a more flexible, backwards-"
+"compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
-msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
+msgid ""
+"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
+"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
+"boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
-msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
+msgid ""
+"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
+"the client. Theoretically, any server, on any platform, which implements "
+"these protocols, may be used. In the examples in this section, we shall "
+"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
-msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
+msgid ""
+"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
+"It's written by the same author as the <classname>syslinux</classname> "
+"bootloader and is therefore least likely to cause issues. A good alternative "
+"is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
-msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
+msgid ""
+"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>ip addr show dev eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
+msgid ""
+"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
+"you use the <command>rarpd</command> program. You need to ensure that the "
+"Ethernet hardware address for the client is listed in the <quote>ethers</"
+"quote> database (either in the <filename>/etc/ethers</filename> file, or via "
+"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start "
+"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</"
+"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/"
+"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/"
+"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
+"gnu;, the <classname>dhcp3-server</classname> package is recommended. Here "
+"is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</"
+"filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
-      "option domain-name \"example.com\";\n"
-      "option domain-name-servers ns1.example.com;\n"
-      "option subnet-mask 255.255.255.0;\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "server-name \"servername\";\n"
-      "\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option routers 192.168.1.1;\n"
-      "}\n"
-      "\n"
-      "host clientname {\n"
-      "  filename \"/tftpboot.img\";\n"
-      "  server-name \"servername\";\n"
-      "  next-server servername;\n"
-      "  hardware ethernet 01:23:45:67:89:AB;\n"
-      "  fixed-address 192.168.1.90;\n"
-      "}"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1237
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+"  filename \"/tftpboot.img\";\n"
+"  server-name \"servername\";\n"
+"  next-server servername;\n"
+"  hardware ethernet 01:23:45:67:89:AB;\n"
+"  fixed-address 192.168.1.90;\n"
+"}"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1236
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
-#, no-c-format
-msgid ""
-      "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
-      "option domain-name \"example.com\";\n"
-      "\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "\n"
-      "allow booting;\n"
-      "allow bootp;\n"
-      "\n"
-      "# The next paragraph needs to be modified to fit your case\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option broadcast-address 192.168.1.255;\n"
-      "# the gateway address which can be different\n"
-      "# (access to the internet for instance)\n"
-      "  option routers 192.168.1.1;\n"
-      "# indicate the dns you want to use\n"
-      "  option domain-name-servers 192.168.1.3;\n"
-      "}\n"
-      "\n"
-      "group {\n"
-      "  next-server 192.168.1.3;\n"
-      "  host tftpclient {\n"
-      "# tftp client hardware address\n"
-      "  hardware ethernet  00:10:DC:27:6C:15;\n"
-      "  filename \"pxelinux.0\";\n"
-      " }\n"
-      "}\n"
-      "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+#: install-methods.xml:1255
+#, no-c-format
+msgid ""
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different\n"
+"# (access to the internet for instance)\n"
+"  option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+"  option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"group {\n"
+"  next-server 192.168.1.3;\n"
+"  host tftpclient {\n"
+"# tftp client hardware address\n"
+"  hardware ethernet  00:10:DC:27:6C:15;\n"
+"  filename \"pxelinux.0\";\n"
+" }\n"
+"}\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux. The first is CMU "
+"<command>bootpd</command>. The other is actually a DHCP server: ISC "
+"<command>dhcpd</command>. In &debian-gnu; these are contained in the "
+"<classname>bootp</classname> and <classname>dhcp3-server</classname> "
+"packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
-      "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
-      "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-      "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
-      "client:\\\n"
-      "  hd=/tftpboot:\\\n"
-      "  bf=tftpboot.img:\\\n"
-      "  ip=192.168.1.90:\\\n"
-      "  sm=255.255.255.0:\\\n"
-      "  sa=192.168.1.1:\\\n"
-      "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1318
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you "
+"can run <userinput>update-inetd --enable bootps</userinput>, then "
+"<userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your "
+"BOOTP server does not run &debian;, the line in question should look like: "
+"<informalexample><screen>\n"
+"bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
+"client:\\\n"
+"  hd=/tftpboot:\\\n"
+"  bf=tftpboot.img:\\\n"
+"  ip=192.168.1.90:\\\n"
+"  sm=255.255.255.0:\\\n"
+"  sa=192.168.1.1:\\\n"
+"  ha=0123456789AB:\n"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI machines you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1317
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd."
+"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/"
+"init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
-msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
+msgid ""
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
-msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
+msgid ""
+"In the case of <classname>tftpd-hpa</classname> there are two ways the "
+"service can be run. It can be started on demand by the system's "
+"<classname>inetd</classname> daemon, or it can be set up to run as an "
+"independent daemon. Which of these methods is used is selected when the "
+"package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
-msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
+msgid ""
+"Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
+"to serve images from. However, &debian-gnu; packages may use other "
+"directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by "
+"default uses <filename>/srv/tftp</filename>. You may have to adjust the "
+"configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
-msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
+msgid ""
+"All <command>in.tftpd</command> alternatives available in &debian; should "
+"log TFTP requests to the system logs by default. Some of them support a "
+"<userinput>-v</userinput> argument to increase verbosity. It is recommended "
+"to check these log messages in case of boot problems as they are a good "
+"starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
-      "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
-      "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
-      "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-      "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"If you intend to install &debian; on an SGI machine and your TFTP server is "
+"a GNU/Linux box running Linux 2.4, you'll need to set the following on your "
+"server: <informalexample><screen>\n"
+"# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets "
+"are sent from a source port no greater than 32767, or the download will "
+"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
+"the PROM, and you can avoid it by setting <informalexample><screen>\n"
+"# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. You may "
+"have to make a link from that file to the file which <command>tftpd</"
+"command> will use for booting a particular client. Unfortunately, the file "
+"name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. You will need to download the following files from the "
+"<filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
-      "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-      "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
-      "</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"Some SPARC architectures add the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your "
+"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename "
+"would be <filename>C0A80103.SUN4C</filename>. However, there are also "
+"subarchitectures where the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. An easy way to determine the "
+"hexadecimal code for the IP address is to enter the following command in a "
+"shell (assuming the machine's intended IP is 10.0.0.4). "
+"<informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> To get to the correct filename, you will need to "
+"change all letters to uppercase and if necessary append the subarchitecture "
+"name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
-msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
+msgid ""
+"If you've done all this correctly, giving the command <userinput>boot net</"
+"userinput> from the OpenPROM should load the image. If the image cannot be "
+"found, try checking the logs on your tftp server to see which image name is "
+"being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
-msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+msgid ""
+"You can also force some sparc systems to look for a specific file name by "
+"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
-msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI machines you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. &debian; packages intended for this include <classname>fai-"
+"quickstart</classname> (which can use an install server) and the &debian; "
+"Installer itself. Have a look at the <ulink url=\"http://fai-project.org"
+"\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
-msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
+msgid ""
+"The &debian; Installer supports automating installs via preconfiguration "
+"files. A preconfiguration file can be loaded from the network or from "
+"removable media, and used to fill in answers to questions asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
-msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Full documentation on preseeding including a working example that you can "
+"edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-
diff --git a/po/nl/installation-howto.po b/po/nl/installation-howto.po
index 6b8f358e5..369f718c1 100644
--- a/po/nl/installation-howto.po
+++ b/po/nl/installation-howto.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:7
 #, no-c-format
-msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document."
+msgid ""
+"This document describes how to install &debian-gnu; &releasename; for the "
+"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a "
+"quick walkthrough of the installation process which should contain all the "
+"information you will need for most installs. When more information can be "
+"useful, we will link to more detailed explanations in other parts of this "
+"document."
 msgstr ""
 
 #. Tag: title
@@ -34,7 +41,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:20
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)."
+msgid ""
+"<phrase condition=\"unofficial-build\"> The debian-installer is still in a "
+"beta state. </phrase> If you encounter bugs during your install, please "
+"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report "
+"them. If you have questions which cannot be answered by this document, "
+"please direct them to the debian-boot mailing list (&email-debian-boot-"
+"list;) or ask on IRC (#debian-boot on the OFTC network)."
 msgstr ""
 
 #. Tag: title
@@ -46,19 +59,30 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:37
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>."
+msgid ""
+"<phrase condition=\"unofficial-build\"> For some quick links to CD images, "
+"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> "
+"The debian-cd team provides builds of CD images using &d-i; on the <ulink "
+"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on "
+"where to get CDs, see <xref linkend=\"official-cdrom\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:47
 #, no-c-format
-msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on &debian; mirrors."
+msgid ""
+"Some installation methods require other images than CD images. <phrase "
+"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home "
+"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files"
+"\"/> explains how to find images on &debian; mirrors."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:57
 #, no-c-format
-msgid "The subsections below will give the details about which images you should get for each possible means of installation."
+msgid ""
+"The subsections below will give the details about which images you should "
+"get for each possible means of installation."
 msgstr ""
 
 #. Tag: title
@@ -70,13 +94,26 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:67
 #, no-c-format
-msgid "The netinst CD image is a popular image which can be used to install &releasename; with the &d-i;. This image is intended to boot from CD and install additional packages over a network; hence the name 'netinst'. The image has the software components needed to run the installer and the base packages to provide a minimal &releasename; system. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set."
+msgid ""
+"The netinst CD image is a popular image which can be used to install "
+"&releasename; with the &d-i;. This image is intended to boot from CD and "
+"install additional packages over a network; hence the name 'netinst'. The "
+"image has the software components needed to run the installer and the base "
+"packages to provide a minimal &releasename; system. If you'd rather, you can "
+"get a full size CD image which will not need the network to install. You "
+"only need the first CD of the set."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:77
 #, no-c-format
-msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>"
+msgid ""
+"Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-"
+"x86\">To boot the CD, you may need to change your BIOS configuration, as "
+"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc"
+"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while "
+"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -88,31 +125,50 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:92
 #, no-c-format
-msgid "If you can't boot from CD, you can download floppy images to install &debian;. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks."
+msgid ""
+"If you can't boot from CD, you can download floppy images to install "
+"&debian;. You need the <filename>floppy/boot.img</filename>, the "
+"<filename>floppy/root.img</filename> and one or more of the driver disks."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:98
 #, no-c-format
-msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy &mdash; use the one with <filename>root.img</filename> on it."
+msgid ""
+"The boot floppy is the one with <filename>boot.img</filename> on it. This "
+"floppy, when booted, will prompt you to insert a second floppy &mdash; use "
+"the one with <filename>root.img</filename> on it."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:104
 #, no-c-format
-msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>."
+msgid ""
+"If you're planning to install over the network, you will usually need the "
+"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, "
+"and some less common network cards, you will also need a second driver "
+"floppy, <filename>floppy/net-drivers-2.img</filename>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:111
 #, no-c-format
-msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD."
+msgid ""
+"If you have a CD, but cannot boot from it, then boot from floppies and use "
+"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the "
+"install using the CD."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:117
 #, no-c-format
-msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them."
+msgid ""
+"Floppy disks are one of the least reliable media around, so be prepared for "
+"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each "
+"<filename>.img</filename> file you downloaded goes on a single floppy; you "
+"can use the dd command to write it to /dev/fd0 or some other means (see "
+"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than "
+"one floppy, it's a good idea to label them."
 msgstr ""
 
 #. Tag: title
@@ -124,37 +180,62 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:131
 #, no-c-format
-msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy &debian; install medium that you can take with you anywhere."
+msgid ""
+"It's also possible to install from removable USB storage devices. For "
+"example a USB keychain can make a handy &debian; install medium that you can "
+"take with you anywhere."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:137
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download any Debian "
+"CD or DVD image that will fit on it, and write the CD image directly to the "
+"memory stick. Of course this will destroy anything already on the memory "
+"stick. This works because Debian CD images are \"isohybrid\" images that can "
+"boot both from CD and from USB drives."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:145
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from that file. Write this image directly to your memory stick, which must be at least 1 GB in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download <filename>hd-"
+"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from "
+"that file. Write this image directly to your memory stick, which must be at "
+"least 1 GB in size. Of course this will destroy anything already on the "
+"memory stick. Then mount the memory stick, which will now have a FAT "
+"filesystem on it. Next, download a &debian; netinst CD image, and copy that "
+"file to the memory stick; any filename is ok as long as it ends in <literal>."
+"iso</literal>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:156
 #, no-c-format
-msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
+msgid ""
+"There are other, more flexible ways to set up a memory stick to use the "
+"debian-installer, and it's possible to get it to work with smaller memory "
+"sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:162
 #, no-c-format
-msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Some BIOSes can boot USB storage directly, and some cannot. You may need to "
+"configure your BIOS to boot from a <quote>removable drive</quote> or even a "
+"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful "
+"hints and details, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:169
 #, no-c-format
-msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Booting Macintosh systems from USB storage devices involves manual use of "
+"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: title
@@ -166,13 +247,22 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:179
 #, no-c-format
-msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;."
+msgid ""
+"It's also possible to boot &d-i; completely from the net. The various "
+"methods to netboot depend on your architecture and netboot setup. The files "
+"in <filename>netboot/</filename> can be used to netboot &d-i;."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:185
 #, no-c-format
-msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The easiest thing to set up is probably PXE netbooting. Untar the file "
+"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</"
+"filename> or wherever is appropriate for your tftp server. Set up your DHCP "
+"server to pass filename <filename>pxelinux.0</filename> to clients, and with "
+"luck everything will just work. For detailed instructions, see <xref linkend="
+"\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -184,7 +274,15 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:200
 #, no-c-format
-msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>"
+msgid ""
+"It's possible to boot the installer using no removable media, but just an "
+"existing hard disk, which can have a different OS on it. Download "
+"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</"
+"filename>, and a &debian; CD image to the top-level directory of the hard "
+"disk. Make sure that the CD image has a filename ending in <literal>.iso</"
+"literal>. Now it's just a matter of booting linux with the initrd. <phrase "
+"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -196,91 +294,156 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:218
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
+msgid ""
+"Once the installer starts, you will be greeted with an initial screen. Press "
+"&enterkey; to boot, or read the instructions for other boot methods and "
+"parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:224
 #, no-c-format
-msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
+msgid ""
+"After a while you will be asked to select your language. Use the arrow keys "
+"to pick a language and press &enterkey; to continue. Next you'll be asked to "
+"select your country, with the choices including countries where your "
+"language is spoken. If it's not on the short list, a list of all the "
+"countries in the world is available."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:232
 #, no-c-format
-msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
+msgid ""
+"You may be asked to confirm your keyboard layout. Choose the default unless "
+"you know better."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:237
 #, no-c-format
-msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
+msgid ""
+"Now sit back while debian-installer detects some of your hardware, and loads "
+"the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:242
 #, no-c-format
-msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
+msgid ""
+"Next the installer will try to detect your network hardware and set up "
+"networking by DHCP. If you are not on a network or do not have DHCP, you "
+"will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:248
 #, no-c-format
-msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones."
+msgid ""
+"The next step is setting up your clock and time zone. The installer will try "
+"to contact a time server on the Internet to ensure the clock is set "
+"correctly. The time zone is based on the country selected earlier and the "
+"installer will only ask to select one if a country has multiple zones."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:255
 #, no-c-format
-msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"Now it is time to partition your disks. First you will be given the "
+"opportunity to automatically partition either an entire drive, or available "
+"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is "
+"recommended for new users or anyone in a hurry. If you do not want to "
+"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:263
 #, no-c-format
-msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size."
+msgid ""
+"If you have an existing DOS or Windows partition that you want to preserve, "
+"be very careful with automatic partitioning. If you choose manual "
+"partitioning, you can use the installer to resize existing FAT or NTFS "
+"partitions to create room for the &debian; install: simply select the "
+"partition and specify its new size."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:270
 #, no-c-format
-msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning."
+msgid ""
+"On the next screen you will see your partition table, how the partitions "
+"will be formatted, and where they will be mounted. Select a partition to "
+"modify or delete it. If you did automatic partitioning, you should just be "
+"able to choose <guimenuitem>Finish partitioning and write changes to disk</"
+"guimenuitem> from the menu to use what it set up. Remember to assign at "
+"least one partition for swap space and to mount a partition on <filename>/</"
+"filename>. For more detailed information on how to use the partitioner, "
+"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend="
+"\"partitioning\"/> has more general information about partitioning."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:283
 #, no-c-format
-msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
+msgid ""
+"Now &d-i; formats your partitions and starts to install the base system, "
+"which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:288
 #, no-c-format
-msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step."
+msgid ""
+"The base system that was installed earlier is a working, but very minimal "
+"installation. To make the system more functional the next step allows you to "
+"install additional packages by selecting tasks. Before packages can be "
+"installed <classname>apt</classname> needs to be configured as that defines "
+"from where the packages will be retrieved. The <quote>Standard system</"
+"quote> task will be selected by default and should normally be installed. "
+"Select the <quote>Desktop environment</quote> task if you would like to have "
+"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> "
+"for additional information about this step."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:300
 #, no-c-format
-msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account."
+msgid ""
+"Installation of the base system is followed by setting up user accounts. By "
+"default you will need to provide a password for the <quote>root</quote> "
+"(administrator) account and information necessary to create one regular user "
+"account."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:307
 #, no-c-format
-msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
+msgid ""
+"The last step is to install a boot loader. If the installer detects other "
+"operating systems on your computer, it will add them to the boot menu and "
+"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to "
+"the master boot record of the first harddrive, which is generally a good "
+"choice. You'll be given the opportunity to override that choice and install "
+"it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:317
 #, no-c-format
-msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>."
+msgid ""
+"&d-i; will now tell you that the installation has finished. Remove the cdrom "
+"or other boot media and hit &enterkey; to reboot your machine. It should "
+"boot up into the newly installed system and allow you to log in. This is "
+"explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:324
 #, no-c-format
-msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
+msgid ""
+"If you need more information on the install process, see <xref linkend=\"d-i-"
+"intro\"/>."
 msgstr ""
 
 #. Tag: title
@@ -292,13 +455,23 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:334
 #, no-c-format
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>."
+msgid ""
+"If you successfully managed an installation with &d-i;, please take time to "
+"provide us with a report. The simplest way to do so is to install the "
+"reportbug package (<command>aptitude install reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:344
 #, no-c-format
-msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
+msgid ""
+"If you did not complete the install, you probably found a bug in debian-"
+"installer. To improve the installer it is necessary that we know about them, "
+"so please take the time to report them. You can use an installation report "
+"to report problems; if the install completely fails, see <xref linkend="
+"\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
@@ -310,6 +483,7 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:357
 #, no-c-format
-msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read <xref linkend=\"post-install\"/>."
+msgid ""
+"We hope that your &debian; installation is pleasant and that you find "
+"&debian; useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
-
diff --git a/po/nl/partitioning.po b/po/nl/partitioning.po
index 5cab7d795..2be4d60bf 100644
--- a/po/nl/partitioning.po
+++ b/po/nl/partitioning.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,57 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
+msgid ""
+"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can "
+"have a single partition containing the entire operating system, "
+"applications, and your personal files. Most people feel that a separate swap "
+"partition is also a necessity, although it's not strictly true. <quote>Swap</"
+"quote> is scratch space for an operating system, which allows the system to "
+"use disk storage as <quote>virtual memory</quote>. By putting swap on a "
+"separate partition, &arch-kernel; can make much more efficient use of it. It "
+"is possible to force &arch-kernel; to use a regular file as swap, but it is "
+"not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid ""
+"Most people choose to give GNU/&arch-kernel; more than the minimum number of "
+"partitions, however. There are two reasons you might want to break up the "
+"file system into a number of smaller partitions. The first is for safety. If "
+"something happens to corrupt the file system, generally only one partition "
+"is affected. Thus, you only have to replace (from the backups you've been "
+"carefully keeping) a portion of your system. At a bare minimum, you should "
+"consider creating what is commonly called a <quote>root partition</quote>. "
+"This contains the most essential components of the system. If any other "
+"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix "
+"the system. This can save you the trouble of having to reinstall the system "
+"from scratch."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:40
 #, no-c-format
-msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed."
+msgid ""
+"The second reason is generally more important in a business setting, but it "
+"really depends on your use of the machine. For example, a mail server "
+"getting spammed with e-mail can easily fill a partition. If you made "
+"<filename>/var/mail</filename> a separate partition on the mail server, most "
+"of the system will remain working even if you get spammed."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:48
 #, no-c-format
-msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?"
+msgid ""
+"The only real drawback to using more partitions is that it is often "
+"difficult to know in advance what your needs will be. If you make a "
+"partition too small then you will either have to reinstall the system or you "
+"will be constantly moving things around to make room in the undersized "
+"partition. On the other hand, if you make the partition too big, you will be "
+"wasting space that could be used elsewhere. Disk space is cheap nowadays, "
+"but why throw your money away?"
 msgstr ""
 
 #. Tag: title
@@ -58,7 +91,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:68
 #, no-c-format
-msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all &debian; systems include these directories:"
+msgid ""
+"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink> for directory and file naming. This standard "
+"allows users and software programs to predict the location of files and "
+"directories. The root level directory is represented simply by the slash "
+"<filename>/</filename>. At the root level, all &debian; systems include "
+"these directories:"
 msgstr ""
 
 #. Tag: entry
@@ -280,37 +319,77 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:142
 #, no-c-format
-msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
+msgid ""
+"The following is a list of important considerations regarding directories "
+"and partitions. Note that disk usage varies widely given system "
+"configuration and specific usage patterns. The recommendations here are "
+"general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
+msgid ""
+"The root partition <filename>/</filename> must always physically contain "
+"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</"
+"filename>, <filename>/lib</filename> and <filename>/dev</filename>, "
+"otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for "
+"the root partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
+msgid ""
+"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</"
+"filename>), libraries (<filename>/usr/lib</filename>), documentation "
+"(<filename>/usr/share/doc</filename>), etc. This is the part of the file "
+"system that generally takes up most space. You should provide at least 500MB "
+"of disk space. This amount should be increased depending on the number and "
+"type of packages you plan to install. A generous workstation or server "
+"installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid ""
+"<filename>/var</filename>: variable data like news articles, e-mails, web "
+"sites, databases, the packaging system cache, etc. will be placed under this "
+"directory. The size of this directory depends greatly on the usage of your "
+"system, but for most people will be dictated by the package management "
+"tool's overhead. If you are going to do a full installation of just about "
+"everything &debian; has to offer, all in one session, setting aside 2 or 3 "
+"GB of space for <filename>/var</filename> should be sufficient. If you are "
+"going to install in pieces (that is to say, install services and utilities, "
+"followed by text stuff, then X, ...), you can get away with 300&ndash;500 "
+"MB. If hard drive space is at a premium and you don't plan on doing major "
+"system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid ""
+"<filename>/tmp</filename>: temporary data created by programs will most "
+"likely go in this directory. 40&ndash;100MB should usually be enough. Some "
+"applications &mdash; including archive manipulators, CD/DVD authoring tools, "
+"and multimedia software &mdash; may use <filename>/tmp</filename> to "
+"temporarily store image files. If you plan to use such applications, you "
+"should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid ""
+"<filename>/home</filename>: every user will put his personal data into a "
+"subdirectory of this directory. Its size depends on how many users will be "
+"using the system and what files are to be stored in their directories. "
+"Depending on your planned usage you should reserve about 100MB for each "
+"user, but adapt this value to your needs. Reserve a lot more space if you "
+"plan to save a lot of multimedia files (pictures, MP3, movies) in your home "
+"directory."
 msgstr ""
 
 #. Tag: title
@@ -322,49 +401,91 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:223
 #, no-c-format
-msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
+msgid ""
+"For new users, personal &debian; boxes, home systems, and other single-user "
+"setups, a single <filename>/</filename> partition (plus swap) is probably "
+"the easiest, simplest way to go. However, if your partition is larger than "
+"around 6GB, choose ext3 as your partition type. Ext2 partitions need "
+"periodic file system integrity checking, and this can cause delays during "
+"booting when the partition is large."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:232
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid ""
+"For multi-user systems or systems with lots of disk space, it's best to put "
+"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</"
+"filename>, and <filename>/home</filename> each on their own partitions "
+"separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid ""
+"You might need a separate <filename>/usr/local</filename> partition if you "
+"plan to install many programs that are not part of the &debian; "
+"distribution. If your machine will be a mail server, you might need to make "
+"<filename>/var/mail</filename> a separate partition. Often, putting "
+"<filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, "
+"is a good idea. If you are setting up a server with lots of user accounts, "
+"it's generally good to have a separate, large <filename>/home</filename> "
+"partition. In general, the partitioning situation varies from computer to "
+"computer depending on its uses."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:252
 #, no-c-format
-msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
+msgid ""
+"For very complex systems, you should see the <ulink url=\"&url-multidisk-"
+"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, "
+"mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:259
 #, no-c-format
-msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
+msgid ""
+"With respect to the issue of swap partition size, there are many views. One "
+"rule of thumb which works well is to use as much swap as you have system "
+"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, "
+"there are exceptions to these rules. If you are trying to solve 10000 "
+"simultaneous equations on a machine with 256MB of memory, you may need a "
+"gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:268
 #, no-c-format
-msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
+msgid ""
+"On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap "
+"partition is 2GB. That should be enough for nearly any installation. "
+"However, if your swap requirements are this high, you should probably try to "
+"spread the swap across different disks (also called <quote>spindles</quote>) "
+"and, if possible, different SCSI or IDE channels. The kernel will balance "
+"swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:278
 #, no-c-format
-msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
+msgid ""
+"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE "
+"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for "
+"another operating system on <filename>/dev/hda1</filename>, a 32MB swap "
+"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/"
+"dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:287
 #, no-c-format
-msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
+msgid ""
+"For an idea of the space taken by tasks you might be interested in adding "
+"after your system installation is complete, check <xref linkend=\"tasksel-"
+"size-list\"/>."
 msgstr ""
 
 #. Tag: title
@@ -376,7 +497,10 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:304
 #, no-c-format
-msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
+msgid ""
+"Linux disks and partition names may be different from other operating "
+"systems. You need to know the names that Linux uses when you create and "
+"mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
@@ -394,37 +518,51 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:322
 #, no-c-format
-msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
+msgid ""
+"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:328
 #, no-c-format
-msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
+msgid ""
+"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, "
+"and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:334
 #, no-c-format
-msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
+msgid ""
+"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as "
+"<filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:340
 #, no-c-format
-msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
+msgid ""
+"The master disk on IDE primary controller is named <filename>/dev/hda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:346
 #, no-c-format
-msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
+msgid ""
+"The slave disk on IDE primary controller is named <filename>/dev/hdb</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:352
 #, no-c-format
-msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
+msgid ""
+"The master and slave disks of the secondary controller can be called "
+"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, "
+"respectively. Newer IDE controllers can actually have two channels, "
+"effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
@@ -436,43 +574,74 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:369
 #, no-c-format
-msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
+msgid ""
+"The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:377
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>sda1</filename> and <filename>sda2</filename> "
+"represent the first and second partitions of the first SCSI disk drive in "
+"your system."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:384
 #, no-c-format
-msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
+msgid ""
+"Here is a real-life example. Let's assume you have a system with 2 SCSI "
+"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk "
+"(at address 2) is then named <filename>sda</filename>, and the second "
+"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 "
+"partitions on it, these will be named <filename>sda1</filename>, "
+"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies "
+"to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:395
 #, no-c-format
-msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
+msgid ""
+"Note that if you have two SCSI host bus adapters (i.e., controllers), the "
+"order of the drives can get confusing. The best solution in this case is to "
+"watch the boot messages, assuming you know the drive models and/or "
+"capacities."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:402
 #, no-c-format
-msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
+msgid ""
+"Linux represents the primary partitions as the drive name, plus the numbers "
+"1 through 4. For example, the first primary partition on the first IDE drive "
+"is <filename>/dev/hda1</filename>. The logical partitions are numbered "
+"starting at 5, so the first logical partition on that same drive is "
+"<filename>/dev/hda5</filename>. Remember that the extended partition, that "
+"is, the primary partition holding the logical partitions, is not usable by "
+"itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:413
 #, no-c-format
-msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
+msgid ""
+"Sun disk partitions allow for 8 separate partitions (or slices). The third "
+"partition is usually (and is preferred to have) the <quote>Whole Disk</"
+"quote> partition. This partition references all of the sectors of the disk, "
+"and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:420
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> "
+"represent the first and second partitions of the first DASD device in your "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -484,7 +653,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:436
 #, no-c-format
-msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
+msgid ""
+"Several varieties of partitioning programs have been adapted by &debian; "
+"developers to work on various types of hard disks and computer "
+"architectures. Following is a list of the program(s) applicable for your "
+"architecture."
 msgstr ""
 
 #. Tag: command
@@ -496,7 +669,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:449
 #, no-c-format
-msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
+msgid ""
+"Recommended partitioning tool in &debian;. This Swiss army knife can also "
+"resize partitions, create filesystems <phrase arch=\"any-x86\"> "
+"(<quote>format</quote> in Windows speak)</phrase> and assign them to the "
+"mountpoints."
 msgstr ""
 
 #. Tag: command
@@ -514,7 +691,12 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:465
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
+msgid ""
+"Be careful if you have existing FreeBSD partitions on your machine. The "
+"installation kernels include support for these partitions, but the way that "
+"<command>fdisk</command> represents them (or not) can make the device names "
+"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</"
+"ulink>."
 msgstr ""
 
 #. Tag: command
@@ -532,7 +714,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:482
 #, no-c-format
-msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
+msgid ""
+"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at "
+"all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
@@ -580,7 +764,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:519
 #, no-c-format
-msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
+msgid ""
+"PowerMac-aware version of <command>fdisk</command>, also used by BVM and "
+"Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
@@ -592,13 +778,21 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:529
 #, no-c-format
-msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
+msgid ""
+"&arch-title; version of <command>fdisk</command>; Please read the fdasd "
+"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/"
+"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and "
+"Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:540
 #, no-c-format
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
+msgid ""
+"One of these programs will be run by default when you select "
+"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible "
+"to use a different partitioning tool from the command line on VT2, but this "
+"is not recommended."
 msgstr ""
 
 #. Tag: para
@@ -610,11 +804,18 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:550
 #, no-c-format
-msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
+msgid ""
+"One key point when partitioning for Mac type disks is that the swap "
+"partition is identified by its name; it must be named <quote>swap</quote>. "
+"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. "
+"Please read the fine manual. We also suggest reading the <ulink url=\"&url-"
+"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you "
+"should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686
+#: partitioning.xml:800 partitioning.xml:877
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
@@ -622,61 +823,138 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:567
 #, no-c-format
-msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
+msgid ""
+"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> "
+"somewhere in the first 2GB. This is where the boot loader and an optional "
+"kernel and RAMdisk will be stored, so make it big enough for that &mdash; at "
+"least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware "
+"is that the Linux kernel must reside within the first 2GB of the disk. This "
+"is typically achieved by making the root ext2 partition fit entirely within "
+"the first 2GB of the disk. Alternatively you can create a small ext2 "
+"partition near the start of the disk and mount that on <filename>/boot</"
+"filename>, since that is the directory where the Linux kernel(s) will be "
+"stored. <filename>/boot</filename> needs to be big enough to hold whatever "
+"kernels (and backups) you might wish to load; 25&ndash;50MB is generally "
+"sufficient."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:591
 #, no-c-format
-msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
+msgid ""
+"If you have an existing other operating system such as DOS or Windows and "
+"you want to preserve that operating system while installing &debian;, you "
+"may need to resize its partition to free up space for the &debian; "
+"installation. The installer supports resizing of both FAT and NTFS "
+"filesystems; when you get to the installer's partitioning step, select the "
+"option <guimenuitem>Manual</guimenuitem> and then simply select an existing "
+"partition and change its size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:601
 #, no-c-format
-msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
+msgid ""
+"The PC BIOS generally adds additional constraints for disk partitioning. "
+"There is a limit to how many <quote>primary</quote> and <quote>logical</"
+"quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 "
+"BIOSes, there are limits to where on the drive the BIOS can boot from. More "
+"information can be found in the <ulink url=\"&url-partition-howto;\">Linux "
+"Partition HOWTO</ulink>, but this section will include a brief overview to "
+"help you plan most situations."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:611
 #, no-c-format
-msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
+msgid ""
+"<quote>Primary</quote> partitions are the original partitioning scheme for "
+"PC disks. However, there can only be four of them. To get past this "
+"limitation, <quote>extended</quote> and <quote>logical</quote> partitions "
+"were invented. By setting one of your primary partitions as an extended "
+"partition, you can subdivide all the space allocated to that partition into "
+"logical partitions. You can create up to 60 logical partitions per extended "
+"partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:622
 #, no-c-format
-msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
+msgid ""
+"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 "
+"usable primary partitions, 252 logical partitions), and 63 partitions on an "
+"IDE drive (3 usable primary partitions, 60 logical partitions). However the "
+"normal &debian-gnu; system provides only 20 devices for partitions, so you "
+"may not install on partitions higher than 20 unless you first manually "
+"create devices for those partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:632
 #, no-c-format
-msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
+msgid ""
+"If you have a large IDE disk, and are using neither LBA addressing, nor "
+"overlay drivers (sometimes provided by hard disk manufacturers), then the "
+"boot partition (the partition containing your kernel image) must be placed "
+"within the first 1024 cylinders of your hard drive (usually around 524 "
+"megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:640
 #, no-c-format
-msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
+msgid ""
+"This restriction doesn't apply if you have a BIOS newer than around "
+"1995&ndash;98 (depending on the manufacturer) that supports the "
+"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the "
+"Linux loader, and &debian;'s alternative <command>mbr</command> must use the "
+"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large "
+"disk access extensions are found to be present, they will be utilized. "
+"Otherwise, the legacy disk access interface is used as a fall-back, and it "
+"cannot be used to address any location on the disk higher than the 1023rd "
+"cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer "
+"has, these restrictions no longer apply, since &arch-kernel; does not use "
+"the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:654
 #, no-c-format
-msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
+msgid ""
+"If you have a large disk, you might have to use cylinder translation "
+"techniques, which you can set from your BIOS setup program, such as LBA "
+"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). "
+"More information about issues with large disks can be found in the <ulink "
+"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a "
+"cylinder translation scheme, and the BIOS does not support the large disk "
+"access extensions, then your boot partition has to fit within the "
+"<emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:666
 #, no-c-format
-msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
+msgid ""
+"The recommended way of accomplishing this is to create a small "
+"(25&ndash;50MB should suffice) partition at the beginning of the disk to be "
+"used as the boot partition, and then create whatever other partitions you "
+"wish to have, in the remaining area. This boot partition <emphasis>must</"
+"emphasis> be mounted on <filename>/boot</filename>, since that is the "
+"directory where the &arch-kernel; kernel(s) will be stored. This "
+"configuration will work on any system, regardless of whether LBA or large "
+"disk CHS translation is used, and regardless of whether your BIOS supports "
+"the large disk access extensions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:687
 #, no-c-format
-msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
+msgid ""
+"The <command>partman</command> disk partitioner is the default partitioning "
+"tool for the installer. It manages the set of partitions and their mount "
+"points to ensure that the disks and filesystems are properly configured for "
+"a successful installation. It actually uses <command>parted</command> to do "
+"the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
@@ -688,28 +966,52 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:700
 #, no-c-format
-msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+msgid ""
+"The IA-64 EFI firmware supports two partition table (or disk label) formats, "
+"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer "
+"recommended for IA-64 systems. Although the installer also provides "
+"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> "
+"<command>parted</command></ulink> because only it can manage both GPT and MS-"
+"DOS tables correctly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:712
 #, no-c-format
-msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
+msgid ""
+"The automatic partitioning recipes for <command>partman</command> allocate "
+"an EFI partition as the first partition on the disk. You can also set up the "
+"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the "
+"main menu in a manner similar to setting up a <emphasis>swap</emphasis> "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:720
 #, no-c-format
 msgid ""
-      "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
-      "      mklabel gpt\n"
-      "      mkpartfs primary fat 0 50\n"
-      "      mkpartfs primary linux-swap 51 1000\n"
-      "      mkpartfs primary ext2 1001 3000\n"
-      "      set 1 boot on\n"
-      "      print\n"
-      "      quit\n"
-      "</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks."
+"The <command>partman</command> partitioner will handle most disk layouts. "
+"For those rare cases where it is necessary to manually set up a disk, you "
+"can use the shell as described above and run the <command>parted</command> "
+"utility directly using its command line interface. Assuming that you want to "
+"erase your whole disk and create a GPT table and some partitions, then "
+"something similar to the following command sequence could be used: "
+"<informalexample><screen>\n"
+"      mklabel gpt\n"
+"      mkpartfs primary fat 0 50\n"
+"      mkpartfs primary linux-swap 51 1000\n"
+"      mkpartfs primary ext2 1001 3000\n"
+"      set 1 boot on\n"
+"      print\n"
+"      quit\n"
+"</screen></informalexample> This creates a new partition table, and three "
+"partitions to be used as an EFI boot partition, swap space, and a root file "
+"system. Finally it sets the boot flag on the EFI partition. Partitions are "
+"specified in Megabytes, with start and end offsets from the beginning of the "
+"disk. So, for example, above we created a 1999MB ext2 file system starting "
+"at offset 1001MB from the start of the disk. Note that formatting swap space "
+"with <command>parted</command> can take a few minutes to complete, as it "
+"scans the partition for bad blocks."
 msgstr ""
 
 #. Tag: title
@@ -721,19 +1023,36 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:746
 #, no-c-format
-msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
+msgid ""
+"ELILO, the IA-64 boot loader, requires a partition containing a FAT file "
+"system with the <userinput>boot</userinput> flag set. The partition must be "
+"big enough to hold the boot loader and any kernels or RAMdisks you may wish "
+"to boot. A minimum size would be about 20MB, but if you expect to run with "
+"multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:755
 #, no-c-format
-msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
+msgid ""
+"The EFI Boot Manager and the EFI Shell fully support the GPT table so the "
+"boot partition does not necessarily have to be the first partition or even "
+"on the same disk. This is convenient if you should forget to allocate the "
+"partition and only find out after you have formatted the other partitions on "
+"your disk(s). The <command>partman</command> partitioner checks for an EFI "
+"partition at the same time it checks for a properly set up <emphasis>root</"
+"emphasis> partition. This gives you an opportunity to correct the disk "
+"layout before the package install begins. The easiest way to correct this "
+"omission is to shrink the last partition of the disk to make enough free "
+"space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:770
 #, no-c-format
-msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
+msgid ""
+"It is strongly recommended that you allocate the EFI boot partition on the "
+"same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -745,13 +1064,27 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:779
 #, no-c-format
-msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
+msgid ""
+"The EFI firmware is significantly more sophisticated than the usual BIOS "
+"seen on most x86 PCs. Some system vendors take advantage of the ability of "
+"the EFI to access files and run programs from a hard disk filesystem to "
+"store diagnostics and EFI based system management utilities on the hard "
+"disk. This is a separate FAT format filesystem on the system disk. Consult "
+"the system documentation and accessories that come with the system for "
+"details. The easiest time to set up a diagnostics partition is at the same "
+"time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:801
 #, no-c-format
-msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
+msgid ""
+"SGI machines require an SGI disk label in order to make the system bootable "
+"from hard disk. It can be created in the fdisk expert menu. The thereby "
+"created volume header (partition number 9) should be at least 3MB large. If "
+"the volume header created is too small, you can simply delete partition "
+"number 9 and re-add it with a different size. Note that the volume header "
+"must start at sector 0."
 msgstr ""
 
 #. Tag: title
@@ -763,48 +1096,94 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:819
 #, no-c-format
-msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
+msgid ""
+"If you are installing onto a NewWorld PowerMac you must create a special "
+"bootstrap partition to hold the boot loader. The size of this partition must "
+"have at least 819200 bytes and its partition type must be "
+"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not "
+"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine "
+"cannot be made bootable from the hard disk. This partition can easily be "
+"created by creating a new partition in <command>partman</command> and "
+"telling it to use it as a <quote>NewWorld boot partition</quote>, or in "
+"<command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:832
 #, no-c-format
-msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
+msgid ""
+"The special partition type Apple_Bootstrap is required to prevent MacOS from "
+"mounting and damaging the bootstrap partition, as there are special "
+"modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:839
 #, no-c-format
-msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
+msgid ""
+"Note that the bootstrap partition is only meant to hold 3 very small files: "
+"the <command>yaboot</command> binary, its configuration <filename>yaboot."
+"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</"
+"command>. It need not and must not be mounted on your file system nor have "
+"kernels or anything else copied to it. The <command>ybin</command> and "
+"<command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:849
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
+msgid ""
+"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap "
+"partition should appear before other boot partitions on the disk, especially "
+"MacOS boot partitions. The bootstrap partition should be the first one you "
+"create. However, if you add a bootstrap partition later, you can use "
+"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder "
+"the partition map so the bootstrap partition comes right after the map "
+"(which is always partition 1). It's the logical map order, not the physical "
+"address order, that counts."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:861
 #, no-c-format
-msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
+msgid ""
+"Apple disks normally have several small driver partitions. If you intend to "
+"dual boot your machine with MacOSX, you should retain these partitions and a "
+"small HFS partition (800k is the minimum size). That is because MacOSX, on "
+"every boot, offers to initialize any disks which do not have active MacOS "
+"partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:878
 #, no-c-format
-msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
+msgid ""
+"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This "
+"is the only kind of partition scheme that the OpenBoot PROM understands, and "
+"so it's the only scheme from which you can boot. The <keycap>s</keycap> key "
+"is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:886
 #, no-c-format
-msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
+msgid ""
+"Furthermore, on &arch-title; disks, make sure your first partition on your "
+"boot disk starts at cylinder 0. While this is required, it also means that "
+"the first partition will contain the partition table and the boot block, "
+"which are the first two sectors of the disk. You must <emphasis>not</"
+"emphasis> put swap on the first partition of the boot drive, since swap "
+"partitions do not preserve the first few sectors of the partition. You can "
+"put Ext2 or UFS partitions there; these will leave the partition table and "
+"the boot block alone."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:897
 #, no-c-format
-msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
+msgid ""
+"It is also advised that the third partition should be of type <quote>Whole "
+"disk</quote> (type 5), and contain the entire disk (from the first cylinder "
+"to the last). This is simply a convention of Sun disk labels, and helps the "
+"<command>SILO</command> boot loader keep its bearings."
 msgstr ""
-
diff --git a/po/nl/post-install.po b/po/nl/post-install.po
index 8367ac28c..e22aac91d 100644
--- a/po/nl/post-install.po
+++ b/po/nl/post-install.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,27 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:15
 #, no-c-format
-msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system."
+msgid ""
+"To shut down a running &debian-gnu; system, you must not reboot with the "
+"reset switch on the front or back of your computer, or just turn off the "
+"computer. &debian-gnu; should be shut down in a controlled manner, otherwise "
+"files might get lost and/or disk damage might occur. If you run a desktop "
+"environment, there is usually an option to <quote>log out</quote> available "
+"from the application menu that allows you to shutdown (or reboot) the system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:25
 #, no-c-format
-msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system."
+msgid ""
+"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</"
+"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch="
+"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> "
+"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last "
+"option is to log in as root and type one of the commands <command>poweroff</"
+"command>, <command>halt</command> or <command>shutdown -h now</command> if "
+"either of the key combinations do not work or you prefer to type commands; "
+"use <command>reboot</command> to reboot the system."
 msgstr ""
 
 #. Tag: title
@@ -46,13 +61,26 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:47
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:55
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as &debian; packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as &debian; "
+"packages."
 msgstr ""
 
 #. Tag: title
@@ -64,7 +92,13 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:77
 #, no-c-format
-msgid "&debian; is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about &debian; to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use &debian;, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"&debian; is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about &debian; to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use &debian;, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -76,13 +110,32 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:89
 #, no-c-format
-msgid "The most important concept to grasp is the &debian; packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the &debian; packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:130
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
@@ -94,7 +147,12 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:142
 #, no-c-format
-msgid "There are official and unofficial software repositories that are not enabled in the default &debian; install. These contain software which many find important and expect to have. Information on these additional repositories can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-software;\">The Software Available for &debian;'s Stable Release</ulink>."
+msgid ""
+"There are official and unofficial software repositories that are not enabled "
+"in the default &debian; install. These contain software which many find "
+"important and expect to have. Information on these additional repositories "
+"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-"
+"software;\">The Software Available for &debian;'s Stable Release</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,7 +164,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:155
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
@@ -118,19 +179,34 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:166
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:175
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user account under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:184
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -142,25 +218,50 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:200
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:206
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about &debian;-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about &debian;-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:217
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about &debian;. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more &debian; documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The &debian; community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on &debian;."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about &debian;. In particular, see the "
+"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> "
+"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference"
+"\">Debian Reference</ulink>. An index of more &debian; documentation is "
+"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian "
+"Documentation Project</ulink>. The &debian; community is self-supporting; to "
+"subscribe to one or more of the Debian mailing lists, see the <ulink url="
+"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</"
+"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/"
+"\">Debian Mailing List Archives</ulink> contain a wealth of information on "
+"&debian;."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:235
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
@@ -172,31 +273,59 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:252
 #, no-c-format
-msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some &debian; utilities, we will try to cover the basics in this section."
+msgid ""
+"Today, email is an important part of many people's life. As there are many "
+"options as to how to set it up, and as having it set up correctly is "
+"important for some &debian; utilities, we will try to cover the basics in "
+"this section."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:259
 #, no-c-format
-msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox."
+msgid ""
+"There are three main functions that make up an e-mail system. First there is "
+"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user "
+"actually uses to compose and read mails. Then there is the <firstterm>Mail "
+"Transfer Agent</firstterm> (MTA) that takes care of transferring messages "
+"from one computer to another. And last there is the <firstterm>Mail Delivery "
+"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the "
+"user's inbox."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:269
 #, no-c-format
-msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail."
+msgid ""
+"These three functions can be performed by separate programs, but they can "
+"also be combined in one or two programs. It is also possible to have "
+"different programs handle these functions for different types of mail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:275
 #, no-c-format
-msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA."
+msgid ""
+"On Linux and Unix systems <command>mutt</command> is historically a very "
+"popular MUA. Like most traditional Linux programs it is text based. It is "
+"often used in combination with <command>exim</command> or <command>sendmail</"
+"command> as MTA and <command>procmail</command> as MDA."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:282
 #, no-c-format
-msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in &debian; available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in &debian; has to do with licensing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can &mdash; and often are &mdash; also be used in combination with the traditional Linux tools."
+msgid ""
+"With the increasing popularity of graphical desktop systems, the use of "
+"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's "
+"<command>kmail</command> or Mozilla's <command>thunderbird</command> (in "
+"&debian; available as <command>icedove</command><footnote> <para> The reason "
+"that <command>thunderbird</command> has been renamed to <command>icedove</"
+"command> in &debian; has to do with licensing issues. Details are outside "
+"the scope of this manual. </para> </footnote>) is becoming more popular. "
+"These programs combine the function of a MUA, MTA and MDA, but can &mdash; "
+"and often are &mdash; also be used in combination with the traditional Linux "
+"tools."
 msgstr ""
 
 #. Tag: title
@@ -208,19 +337,40 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:303
 #, no-c-format
-msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, &hellip; </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes."
+msgid ""
+"Even if you are planning to use a graphical mail program, it is important "
+"that a traditional MTA/MDA is also installed and correctly set up on your "
+"&debian-gnu; system. Reason is that various utilities running on the "
+"system<footnote> <para> Examples are: <command>cron</command>, "
+"<command>quota</command>, <command>logcheck</command>, <command>aide</"
+"command>, &hellip; </para> </footnote> can send important notices by e-mail "
+"to inform the system administrator of (potential) problems or changes."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:318
 #, no-c-format
-msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>."
+msgid ""
+"For this reason the packages <classname>exim4</classname> and "
+"<classname>mutt</classname> will be installed by default (provided you did "
+"not unselect the <quote>standard</quote> task during the installation). "
+"<classname>exim4</classname> is a combination MTA/MDA that is relatively "
+"small but very flexible. By default it will be configured to only handle e-"
+"mail local to the system itself and e-mails addressed to the system "
+"administrator (root account) will be delivered to the regular user account "
+"created during the installation<footnote> <para> The forwarding of mail for "
+"root to the regular user account is configured in <filename>/etc/aliases</"
+"filename>. If no regular user account was created, the mail will of course "
+"be delivered to the root account itself. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:337
 #, no-c-format
-msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>."
+msgid ""
+"When system e-mails are delivered they are added to a file in <filename>/var/"
+"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be "
+"read using <command>mutt</command>."
 msgstr ""
 
 #. Tag: title
@@ -232,31 +382,51 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:348
 #, no-c-format
-msgid "As mentioned earlier, the installed &debian; system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others."
+msgid ""
+"As mentioned earlier, the installed &debian; system is only set up to handle "
+"e-mail local to the system, not for sending mail to others nor for receiving "
+"mail from others."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:354
 #, no-c-format
-msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly."
+msgid ""
+"If you would like <classname>exim4</classname> to handle external e-mail, "
+"please refer to the next subsection for the basic available configuration "
+"options. Make sure to test that mail can be sent and received correctly."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:360
 #, no-c-format
-msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)."
+msgid ""
+"If you intend to use a graphical mail program and use a mail server of your "
+"Internet Service Provider (ISP) or your company, there is not really any "
+"need to configure <classname>exim4</classname> for handling external e-mail. "
+"Just configure your favorite graphical mail program to use the correct "
+"servers to send and receive e-mail (how is outside the scope of this manual)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:369
 #, no-c-format
-msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against &debian; packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports."
+msgid ""
+"However, in that case you may need to configure individual utilities to "
+"correctly send e-mails. One such utility is <command>reportbug</command>, a "
+"program that facilitates submitting bug reports against &debian; packages. "
+"By default it expects to be able to use <classname>exim4</classname> to "
+"submit bug reports."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:377
 #, no-c-format
-msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports."
+msgid ""
+"To correctly set up <command>reportbug</command> to use an external mail "
+"server, please run the command <command>reportbug --configure</command> and "
+"answer <quote>no</quote> to the question if an MTA is available. You will "
+"then be asked for the SMTP server to be used for submitting bug reports."
 msgstr ""
 
 #. Tag: title
@@ -268,7 +438,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:389
 #, no-c-format
-msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:"
+msgid ""
+"If you would like your system to also handle external e-mail, you will need "
+"to reconfigure the <classname>exim4</classname> package<footnote> <para> You "
+"can of course also remove <classname>exim4</classname> and replace it with "
+"an alternative MTA/MDA. </para> </footnote>:"
 msgstr ""
 
 #. Tag: screen
@@ -280,13 +454,18 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:403
 #, no-c-format
-msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option."
+msgid ""
+"After entering that command (as root), you will be asked if you want split "
+"the configuration into small files. If you are unsure, select the default "
+"option."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:409
 #, no-c-format
-msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs."
+msgid ""
+"Next you will be presented with several common mail scenarios. Choose the "
+"one that most closely resembles your needs."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +477,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:419
 #, no-c-format
-msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
+msgid ""
+"Your system is connected to a network and your mail is sent and received "
+"directly using SMTP. On the following screens you will be asked a few basic "
+"questions, like your machine's mail name, or a list of domains for which you "
+"accept or relay mail."
 msgstr ""
 
 #. Tag: term
@@ -310,13 +493,22 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:431
 #, no-c-format
-msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which takes care of sending the message on to its destination. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail."
+msgid ""
+"In this scenario your outgoing mail is forwarded to another machine, called "
+"a <quote>smarthost</quote>, which takes care of sending the message on to "
+"its destination. The smarthost also usually stores incoming mail addressed "
+"to your computer, so you don't need to be permanently online. That also "
+"means you have to download your mail from the smarthost via programs like "
+"fetchmail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:441
 #, no-c-format
-msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network."
+msgid ""
+"In a lot of cases the smarthost will be your ISP's mail server, which makes "
+"this option very suitable for dial-up users. It can also be a company mail "
+"server, or even another system on your own network."
 msgstr ""
 
 #. Tag: term
@@ -328,7 +520,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:452
 #, no-c-format
-msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled."
+msgid ""
+"This option is basically the same as the previous one except that the system "
+"will not be set up to handle mail for a local e-mail domain. Mail on the "
+"system itself (e.g. for the system administrator) will still be handled."
 msgstr ""
 
 #. Tag: term
@@ -352,19 +547,37 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:473
 #, no-c-format
-msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
+msgid ""
+"Choose this if you are absolutely convinced you know what you are doing. "
+"This will leave you with an unconfigured mail system &mdash; until you "
+"configure it, you won't be able to send or receive any mail and you may miss "
+"some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:484
 #, no-c-format
-msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has further details about configuring <classname>exim4</classname> and explains where to find additional documentation."
+msgid ""
+"If none of these scenarios suits your needs, or if you need a finer grained "
+"setup, you will need to edit configuration files under the <filename>/etc/"
+"exim4</filename> directory after the installation is complete. More "
+"information about <classname>exim4</classname> may be found under <filename>/"
+"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</"
+"filename> has further details about configuring <classname>exim4</classname> "
+"and explains where to find additional documentation."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:495
 #, no-c-format
-msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>."
+msgid ""
+"Note that sending mail directly to the Internet when you don't have an "
+"official domain name, can result in your mail being rejected because of anti-"
+"spam measures on receiving servers. Using your ISP's mail server is "
+"preferred. If you still do want to send out mail directly, you may want to "
+"use a different e-mail address than is generated by default. If you use "
+"<classname>exim4</classname> as your MTA, this is possible by adding an "
+"entry in <filename>/etc/email-addresses</filename>."
 msgstr ""
 
 #. Tag: title
@@ -376,19 +589,29 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:514
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with &debian; handles most configurations. Also, &debian; often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with &debian; handles most configurations. "
+"Also, &debian; often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:524
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:530
 #, no-c-format
-msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
@@ -430,67 +653,135 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:565
 #, no-c-format
-msgid "To compile a kernel the &debian; way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the &debian; way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<classname>linux-source-2.6</classname> and a few others which are probably "
+"already installed (see <filename>/usr/share/doc/kernel-package/README.gz</"
+"filename> for the complete list)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:574
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:582
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>&debian; way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>&debian; way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <classname>linux-source-2.6</"
+"classname>, yet still use the <classname>kernel-package</classname> "
+"compilation method."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:591
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:598
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/"
+"linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory "
+"<filename>linux-source-&kernelversion;</filename> that will have been "
+"created."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:618
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your &debian; installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your &debian; installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:633
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:638
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --"
+"revision=custom.1.0 kernel_image</userinput>. The version number of "
+"<quote>1.0</quote> can be changed at will; this is just a version number "
+"that you will use to track your kernel builds. Likewise, you can put any "
+"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel "
+"compilation may take quite a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:648
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well."
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../&kernelpackage;-"
+"&kernelversion;-<replaceable>subarchitecture</"
+"replaceable>_custom.1.0_&architecture;.deb</userinput>. The "
+"<replaceable>subarchitecture</replaceable> part is an optional sub-"
+"architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> "
+"depending on what kernel options you set. <userinput>dpkg -i</userinput> "
+"will install the kernel, along with some other nice supporting files. For "
+"instance, the <filename>System.map</filename> will be properly installed "
+"(helpful for debugging kernel problems), and <filename>/boot/config-"
+"&kernelversion;</filename> will be installed, containing your current "
+"configuration set. Your new kernel package is also clever enough to "
+"automatically update your boot loader to use the new kernel. If you have "
+"created a modules package, you'll need to install that package as well."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:668
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:673
 #, no-c-format
-msgid "For more information on &debian; kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"For more information on &debian; kernels and kernel compilation, see the "
+"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. "
+"For more information on <classname>kernel-package</classname>, read the fine "
+"documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
@@ -502,31 +793,63 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:690
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:700
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:715
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:723
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:735
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
@@ -538,6 +861,8 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:748
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/nl/preparing.po b/po/nl/preparing.po
index 9378d6304..86a142b74 100644
--- a/po/nl/preparing.po
+++ b/po/nl/preparing.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:6
 #, no-c-format
-msgid "This chapter deals with the preparation for installing &debian; before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information."
+msgid ""
+"This chapter deals with the preparation for installing &debian; before you "
+"even boot the installer. This includes backing up your data, gathering "
+"information about your hardware, and locating any necessary information."
 msgstr ""
 
 #. Tag: title
@@ -34,37 +38,59 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:20
 #, no-c-format
-msgid "First, just a note about re-installations. With &debian;, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case."
+msgid ""
+"First, just a note about re-installations. With &debian;, a circumstance "
+"that will require a complete re-installation of your system is very rare; "
+"perhaps mechanical failure of the hard disk would be the most common case."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:27
 #, no-c-format
-msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS."
+msgid ""
+"Many common operating systems may require a complete installation to be "
+"performed when critical failures take place or for upgrades to new OS "
+"versions. Even if a completely new installation isn't required, often the "
+"programs you use must be re-installed to operate properly in the new OS."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:35
 #, no-c-format
-msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the &debian; packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system."
+msgid ""
+"Under &debian-gnu;, it is much more likely that your OS can be repaired "
+"rather than replaced if things go wrong. Upgrades never require a wholesale "
+"installation; you can always upgrade in-place. And the programs are almost "
+"always compatible with successive OS releases. If a new program version "
+"requires newer supporting software, the &debian; packaging system ensures "
+"that all the necessary software is automatically identified and installed. "
+"The point is, much effort has been put into avoiding the need for re-"
+"installation, so think of it as your very last option. The installer is "
+"<emphasis>not</emphasis> designed to re-install over an existing system."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:48
 #, no-c-format
-msgid "Here's a road map for the steps you will take during the installation process."
+msgid ""
+"Here's a road map for the steps you will take during the installation "
+"process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:56
 #, no-c-format
-msgid "Back up any existing data or documents on the hard disk where you plan to install."
+msgid ""
+"Back up any existing data or documents on the hard disk where you plan to "
+"install."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:62
 #, no-c-format
-msgid "Gather information about your computer and any needed documentation, before starting the installation."
+msgid ""
+"Gather information about your computer and any needed documentation, before "
+"starting the installation."
 msgstr ""
 
 #. Tag: para
@@ -76,13 +102,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-msgid "Locate and/or download the installer software and any specialized driver or firmware files your machine requires."
+msgid ""
+"Locate and/or download the installer software and any specialized driver or "
+"firmware files your machine requires."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:79
 #, no-c-format
-msgid "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot infrastructure from which the installer can be booted."
+msgid ""
+"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
+"infrastructure from which the installer can be booted."
 msgstr ""
 
 #. Tag: para
@@ -124,7 +154,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:117
 #, no-c-format
-msgid "If necessary, resize existing partitions on your target harddisk to make space for the installation."
+msgid ""
+"If necessary, resize existing partitions on your target harddisk to make "
+"space for the installation."
 msgstr ""
 
 #. Tag: para
@@ -136,13 +168,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:127
 #, no-c-format
-msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>."
+msgid ""
+"Watch the automatic download/install/setup of the <firstterm>base system</"
+"firstterm>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:133
 #, no-c-format
-msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system."
+msgid ""
+"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
+"and/or your existing system."
 msgstr ""
 
 #. Tag: para
@@ -154,37 +190,68 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
+"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
+"of the installation system. For more information about this graphical "
+"installer, see <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:154
 #, no-c-format
-msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
+msgid ""
+"If you have problems during the installation, it helps to know which "
+"packages are involved in which steps. Introducing the leading software "
+"actors in this installation drama:"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:160
 #, no-c-format
-msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
+msgid ""
+"The installer software, <classname>debian-installer</classname>, is the "
+"primary concern of this manual. It detects hardware and loads appropriate "
+"drivers, uses <classname>dhcp-client</classname> to set up the network "
+"connection, runs <classname>debootstrap</classname> to install the base "
+"system packages, and runs <classname>tasksel</classname> to allow you to "
+"install certain additional software. Many more actors play smaller parts in "
+"this process, but <classname>debian-installer</classname> has completed its "
+"task when you load the new system for the first time."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:172
 #, no-c-format
-msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
+msgid ""
+"To tune the system to your needs, <classname>tasksel</classname> allows you "
+"to choose to install various predefined bundles of software like a Web "
+"server or a Desktop environment."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because in relation to a text-mode-only system it requires a comparatively large amount of disk space and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid ""
+"One important option during the installation is whether or not to install a "
+"graphical desktop environment, consisting of the X Window System and one of "
+"the available graphical desktop environments. If you choose not to select "
+"the <quote>Desktop environment</quote> task, you will only have a relatively "
+"basic, command line driven system. Installing the Desktop environment task "
+"is optional because in relation to a text-mode-only system it requires a "
+"comparatively large amount of disk space and because many &debian-gnu; "
+"systems are servers which don't really have any need for a graphical user "
+"interface to do their job."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Troubleshooting of the X Window System is not within the scope of this manual."
+msgid ""
+"Just be aware that the X Window System is completely separate from "
+"<classname>debian-installer</classname>, and in fact is much more "
+"complicated. Troubleshooting of the X Window System is not within the scope "
+"of this manual."
 msgstr ""
 
 #. Tag: title
@@ -196,13 +263,29 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system is going to be installed on your computer, it is quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in the installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
+msgid ""
+"Before you start, make sure to back up every file that is now on your "
+"system. If this is the first time a non-native operating system is going to "
+"be installed on your computer, it is quite likely you will need to re-"
+"partition your disk to make room for &debian-gnu;. Anytime you partition "
+"your disk, you run a risk of losing everything on the disk, no matter what "
+"program you use to do it. The programs used in the installation are quite "
+"reliable and most have seen years of use; but they are also quite powerful "
+"and a false move can cost you. Even after backing up, be careful and think "
+"about your answers and actions. Two minutes of thinking can save hours of "
+"unnecessary work."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Even though this is normally not necessary, there might be situations in which you could be required to reinstall your operating system's boot loader to make the system boot or in a worst case even have to reinstall the complete operating system and restore your previously made backup."
+msgid ""
+"If you are creating a multi-boot system, make sure that you have the "
+"distribution media of any other present operating systems on hand. Even "
+"though this is normally not necessary, there might be situations in which "
+"you could be required to reinstall your operating system's boot loader to "
+"make the system boot or in a worst case even have to reinstall the complete "
+"operating system and restore your previously made backup."
 msgstr ""
 
 #. Tag: title
@@ -238,13 +321,20 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:259
 #, no-c-format
-msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of &debian;; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is the official version of the "
+"Installation Guide for the &releasename; release of &debian;; available in "
+"<ulink url=\"&url-release-area;/installmanual\">various formats and "
+"translations</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:268
 #, no-c-format
-msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of &debian;; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is a development version of the "
+"Installation Guide for the next release of &debian;; available in <ulink url="
+"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -256,7 +346,8 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:281
 #, no-c-format
-msgid "Often contains useful information on configuring or using your hardware."
+msgid ""
+"Often contains useful information on configuring or using your hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -286,7 +377,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:314
 #, no-c-format
-msgid "Documentation of &arch-title;-specific boot sequence, commands and device drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
+msgid ""
+"Documentation of &arch-title;-specific boot sequence, commands and device "
+"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
 msgstr ""
 
 #. Tag: ulink
@@ -298,7 +391,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:330
 #, no-c-format
-msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
+msgid ""
+"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
+"&arch-title; hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -310,7 +405,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:346
 #, no-c-format
-msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about &debian; but the basic installation concepts are the same across all &arch-title; distributions."
+msgid ""
+"IBM Redbook describing the Linux distributions available for the mainframe. "
+"It has no chapter about &debian; but the basic installation concepts are the "
+"same across all &arch-title; distributions."
 msgstr ""
 
 #. Tag: ulink
@@ -328,7 +426,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:368
 #, no-c-format
-msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
+msgid ""
+"In many cases, the installer will be able to automatically detect your "
+"hardware. But to be prepared, we do recommend familiarizing yourself with "
+"your hardware before the install."
 msgstr ""
 
 #. Tag: para
@@ -346,7 +447,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys or key combinations. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
+msgid ""
+"The BIOS setup screens of your computer. You can view these screens when you "
+"start your computer by pressing a combination of keys. Check your manual for "
+"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
+"keycap> key, but some manufacturers use other keys or key combinations. "
+"Usually upon starting the computer there will be a message stating which key "
+"to press to enter the setup screen."
 msgstr ""
 
 #. Tag: para
@@ -364,13 +471,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:408
 #, no-c-format
-msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
+msgid ""
+"System commands or tools in another operating system, including file manager "
+"displays. This source is especially useful for information about RAM and "
+"hard drive memory."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:415
 #, no-c-format
-msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
+msgid ""
+"Your system administrator or Internet Service Provider. These sources can "
+"tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
 #. Tag: title
@@ -514,61 +626,115 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-msgid "Many products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems."
+msgid ""
+"Many products work without trouble on &arch-kernel;. Moreover, hardware "
+"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
+"does not run as many different types of hardware as some operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:516
 #, no-c-format
-msgid "Drivers in &arch-kernel; in most cases are not written for a certain <quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names."
+msgid ""
+"Drivers in &arch-kernel; in most cases are not written for a certain "
+"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
+"but for a certain hardware/chipset. Many seemingly different products/brands "
+"are based on the same hardware design; it is not uncommon that chip "
+"manufacturers provide so-called <quote>reference designs</quote> for "
+"products based on their chips which are then used by several different "
+"device manufacturers and sold under lots of different product or brand names."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:527
 #, no-c-format
-msgid "This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them."
+msgid ""
+"This has advantages and disadvantages. An advantage is that a driver for one "
+"chipset works with lots of different products from different manufacturers, "
+"as long as their product is based on the same chipset. The disadvantage is "
+"that it is not always easy to see which actual chipset is used in a certain "
+"product/brand. Unfortunately sometimes device manufacturers change the "
+"hardware base of their product without changing the product name or at least "
+"the product version number, so that when having two items of the same brand/"
+"product name bought at different times, they can sometimes be based on two "
+"different chipsets and therefore use two different drivers or there might be "
+"no driver at all for one of them."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:540
 #, no-c-format
-msgid "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and <quote>product</quote> IDs, and the combination of these two is usually the same for any product based on the same chipset."
+msgid ""
+"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
+"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
+"Express/ExpressCard devices have so called <quote>vendor</quote> and "
+"<quote>product</quote> IDs, and the combination of these two is usually the "
+"same for any product based on the same chipset."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:548
 #, no-c-format
-msgid "On Linux systems, these IDs can be read with the <command>lsusb</command> command for USB devices and with the <command>lspci -nn</command> command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as <quote>1d6b:0001</quote>."
+msgid ""
+"On Linux systems, these IDs can be read with the <command>lsusb</command> "
+"command for USB devices and with the <command>lspci -nn</command> command "
+"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
+"usually given in the form of two hexadecimal numbers, seperated by a colon, "
+"such as <quote>1d6b:0001</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:556
 #, no-c-format
-msgid "An example for the output of <command>lsusb</command>: <quote>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the vendor ID and 0002 is the product ID."
+msgid ""
+"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
+"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
+"vendor ID and 0002 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:562
 #, no-c-format
-msgid "An example for the output of <command>lspci -nn</command> for an Ethernet card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID."
+msgid ""
+"An example for the output of <command>lspci -nn</command> for an Ethernet "
+"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
+"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
+"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
+"here 10ec is the vendor- and 8168 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:570
 #, no-c-format
-msgid "As another example, a graphics card could give the following output: <quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
+msgid ""
+"As another example, a graphics card could give the following output: "
+"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
+"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:576
 #, no-c-format
-msgid "On Windows systems, the IDs for a device can be found in the Windows device manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the device manager's details tab to actually see the IDs, as they are not displayed by default."
+msgid ""
+"On Windows systems, the IDs for a device can be found in the Windows device "
+"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
+"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
+"you have to select the property <quote>Hardware IDs</quote> in the device "
+"manager's details tab to actually see the IDs, as they are not displayed by "
+"default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:586
 #, no-c-format
-msgid "Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and <quote>driver</quote> as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the graphics card example), can help."
+msgid ""
+"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
+"quote> and <quote>driver</quote> as the search terms often results in "
+"information regarding the driver support status for a certain chipset. If a "
+"search for the vendor/product ID does not yield usable results, a search for "
+"the chip code names, which are also often provided by lsusb and lspci "
+"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
+"and <quote>RV710</quote> in the graphics card example), can help."
 msgstr ""
 
 #. Tag: title
@@ -580,19 +746,42 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:601
 #, no-c-format
-msgid "&debian-gnu; is also available as a so-called <quote>live system</quote> for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by &debian-gnu;, the easiest way is to run a &debian; live system on it and try it out."
+msgid ""
+"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
+"certain architectures. A live system is a preconfigured ready-to-use system "
+"in a compressed format that can be booted and used from a read-only medium "
+"like a CD or DVD. Using it by default does not create any permanent changes "
+"on your computer. You can change user settings and install additional "
+"programs from within the live system, but all this only happens in the "
+"computer's RAM, i.e. if you turn off the computer and boot the live system "
+"again, everything is reset to its defaults. If you want to see whether your "
+"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
+"live system on it and try it out."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:614
 #, no-c-format
-msgid "There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official &debian-gnu; live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the &d-i;, so installation of non-free components must be done manually if needed."
+msgid ""
+"There are a few limitations in using a live system. The first is that as all "
+"changes you do within the live system must be held in your computer's RAM, "
+"this only works on systems with enough RAM to do that, so installing "
+"additional large software packages may fail due to memory constraints. "
+"Another limitation with regards to hardware compatibility testing is that "
+"the official &debian-gnu; live system contains only free components, i.e. "
+"there are no non-free firmware files included in it. Such non-free packages "
+"can of course be installed manually within the system, but there is no "
+"automatic detection of required firmware files like in the &d-i;, so "
+"installation of non-free components must be done manually if needed."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:627
 #, no-c-format
-msgid "Information about the available variants of the &debian; live images can be found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</ulink>."
+msgid ""
+"Information about the available variants of the &debian; live images can be "
+"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
+"ulink>."
 msgstr ""
 
 #. Tag: title
@@ -604,7 +793,11 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-msgid "If your computer is connected to a fixed network (i.e. an Ethernet or equivalent connection &mdash; not a dialup/PPP connection) which is administered by somebody else, you should ask your network's system administrator for this information:"
+msgid ""
+"If your computer is connected to a fixed network (i.e. an Ethernet or "
+"equivalent connection &mdash; not a dialup/PPP connection) which is "
+"administered by somebody else, you should ask your network's system "
+"administrator for this information:"
 msgstr ""
 
 #. Tag: para
@@ -634,31 +827,47 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:671
 #, no-c-format
-msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
+msgid ""
+"The IP address of the default gateway system you should route to, if your "
+"network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:677
 #, no-c-format
-msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
+msgid ""
+"The system on your network that you should use as a DNS (Domain Name "
+"Service) server."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-msgid "If the network you are connected to uses DHCP (Dynamic Host Configuration Protocol) for configuring network settings, you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
+msgid ""
+"If the network you are connected to uses DHCP (Dynamic Host Configuration "
+"Protocol) for configuring network settings, you don't need this information "
+"because the DHCP server will provide it directly to your computer during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:692
 #, no-c-format
-msgid "If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default."
+msgid ""
+"If you have internet access via DSL or cable modem (i.e. over a cable tv "
+"network) and have a router (often provided preconfigured by your phone or "
+"catv provider) which handles your network connectivity, DHCP is usually "
+"available by default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:700
 #, no-c-format
-msgid "As a rule of thumb: if you run a Windows system in your home network and did not have to manually perform any network settings there to achieve Internet access, network connectivity in &debian-gnu; will also be configured automatically."
+msgid ""
+"As a rule of thumb: if you run a Windows system in your home network and did "
+"not have to manually perform any network settings there to achieve Internet "
+"access, network connectivity in &debian-gnu; will also be configured "
+"automatically."
 msgstr ""
 
 #. Tag: para
@@ -688,19 +897,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:735
 #, no-c-format
-msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
+msgid ""
+"Once you have gathered information about your computer's hardware, check "
+"that your hardware will let you do the type of installation that you want to "
+"do."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:741
 #, no-c-format
-msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
+msgid ""
+"Depending on your needs, you might manage with less than some of the "
+"recommended hardware listed in the table below. However, most users risk "
+"being frustrated if they ignore these suggestions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:747
 #, no-c-format
-msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
+msgid ""
+"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
 msgstr ""
 
 #. Tag: para
@@ -790,31 +1006,58 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:785
 #, no-c-format
-msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
+msgid ""
+"The actual minimum memory requirements are a lot less then the numbers "
+"listed in this table. Depending on the architecture, it is possible to "
+"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
+"same goes for the disk space requirements, especially if you pick and choose "
+"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
+"additional information on disk space requirements."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:795
 #, no-c-format
-msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
+msgid ""
+"It is possible to run a graphical desktop environment on older or low-end "
+"systems, but in that case it is recommended to install a window manager that "
+"is less resource-hungry than those of the GNOME or KDE desktop environments; "
+"alternatives include <classname>xfce4</classname>, <classname>icewm</"
+"classname> and <classname>wmaker</classname>, but there are others to choose "
+"from."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:804
 #, no-c-format
-msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
+msgid ""
+"It is practically impossible to give general memory or disk space "
+"requirements for server installations as those very much depend on what the "
+"server is to be used for."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:810
 #, no-c-format
-msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
+msgid ""
+"Remember that these sizes don't include all the other materials which are "
+"usually to be found, such as user files, mail, and data. It is always best "
+"to be generous when considering the space for your own files and data."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:817
 #, no-c-format
-msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to &debian; in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
+msgid ""
+"Disk space required for the smooth operation of the &debian-gnu; system "
+"itself is taken into account in these recommended system requirements. "
+"Notably, the <filename>/var</filename> partition contains a lot of state "
+"information specific to &debian; in addition to its regular contents, like "
+"logfiles. The <command>dpkg</command> files (with information on all "
+"installed packages) can easily consume 40MB. Also, <command>apt-get</"
+"command> puts downloaded packages here before they are installed. You should "
+"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
+"more if you install a graphical desktop environment."
 msgstr ""
 
 #. Tag: title
@@ -826,43 +1069,83 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:842
 #, no-c-format
-msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
+msgid ""
+"Partitioning your disk simply refers to the act of breaking up your disk "
+"into sections. Each section is then independent of the others. It's roughly "
+"equivalent to putting up walls inside a house; if you add furniture to one "
+"room it doesn't affect any other room."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:849
 #, no-c-format
-msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
+msgid ""
+"Whenever this section talks about <quote>disks</quote> you should translate "
+"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
+"means an LPAR or VM guest in this case."
 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 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."
 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 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
 #: preparing.xml:884
 #, no-c-format
-msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
+msgid ""
+"In general, changing a partition with a file system already on it will "
+"destroy any information there. Thus you should always make backups before "
+"doing any repartitioning. Using the analogy of the house, you would probably "
+"want to move all the furniture out of the way before moving a wall or you "
+"risk destroying it."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:892
 #, no-c-format
-msgid "Several modern operating systems offer the ability to move and resize certain existing partitions without destroying their contents. This allows making space for additional partitions without losing existing data. Even though this works quite well in most cases, making changes to the partitioning of a disk is an inherently dangerous action and should only be done after having made a full backup of all data. <phrase arch=\"any-x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, the ability to move and resize them losslessly is provided both by &d-i; as well as by the integrated Disk Manager of Windows 7. </phrase>"
+msgid ""
+"Several modern operating systems offer the ability to move and resize "
+"certain existing partitions without destroying their contents. This allows "
+"making space for additional partitions without losing existing data. Even "
+"though this works quite well in most cases, making changes to the "
+"partitioning of a disk is an inherently dangerous action and should only be "
+"done after having made a full backup of all data. <phrase arch=\"any-"
+"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
+"the ability to move and resize them losslessly is provided both by &d-i; as "
+"well as by the integrated Disk Manager of Windows 7. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:907
 #, no-c-format
-msgid "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size."
+msgid ""
+"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
+"to the partitioning step, select the option for manual partitioning, select "
+"the partition to resize, and simply specify its new size."
 msgstr ""
 
 #. Tag: emphasis
@@ -874,25 +1157,50 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:917
 #, no-c-format
-msgid "Creating and deleting partitions can be done from within &d-i; as well as from an existing operating system. As a rule of thumb, partitions should be created by the system for which they are to be used, i.e. partitions to be used by &debian-gnu; should be created from within &d-i; and partitions to be used from another operating system should be created from there. &d-i; is capable of creating non-&arch-kernel; partitions, and partitions created this way usually work without problems when used in other operating systems, but there are a few rare corner cases in which this could cause problems, so if you want to be sure, use the native partitioning tools to create partitions for use by other operating systems."
+msgid ""
+"Creating and deleting partitions can be done from within &d-i; as well as "
+"from an existing operating system. As a rule of thumb, partitions should be "
+"created by the system for which they are to be used, i.e. partitions to be "
+"used by &debian-gnu; should be created from within &d-i; and partitions to "
+"be used from another operating system should be created from there. &d-i; is "
+"capable of creating non-&arch-kernel; partitions, and partitions created "
+"this way usually work without problems when used in other operating systems, "
+"but there are a few rare corner cases in which this could cause problems, so "
+"if you want to be sure, use the native partitioning tools to create "
+"partitions for use by other operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with the &debian; installation. Windows and other OS installations may destroy your ability to start &debian;, or encourage you to reformat non-native partitions."
+msgid ""
+"If you are going to install more than one operating system on the same "
+"machine, you should install all other system(s) before proceeding with the "
+"&debian; installation. Windows and other OS installations may destroy your "
+"ability to start &debian;, or encourage you to reformat non-native "
+"partitions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:938
 #, no-c-format
-msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
+msgid ""
+"You can recover from these actions or avoid them, but installing the native "
+"system first saves you trouble."
 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 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."
 msgstr ""
 
 #. Tag: title
@@ -904,7 +1212,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1021
 #, no-c-format
-msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and &debian; on the same machine, it is recommended that you partition using SunOS prior to installing &debian;. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
+msgid ""
+"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
+"both SunOS and &debian; on the same machine, it is recommended that you "
+"partition using SunOS prior to installing &debian;. The Linux kernel "
+"understands Sun disk labels, so there are no problems there. SILO supports "
+"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
+"iso9660 (CDROM) partitions."
 msgstr ""
 
 #. Tag: title
@@ -916,13 +1230,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1035
 #, no-c-format
-msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
+msgid ""
+"Whatever system you are using to partition, make sure you create a "
+"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
+"partition scheme that the OpenBoot PROM understands, and so it's the only "
+"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
+"keycap> key is used to create Sun disk labels. You only need to do this on "
+"drives that do not already have a Sun disk label. If you are using a drive "
+"that was previously formatted using a PC (or other architecture) you must "
+"create a new disk label, or problems with the disk geometry will most likely "
+"occur."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1047
 #, no-c-format
-msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
+msgid ""
+"You will probably be using <command>SILO</command> as your boot loader (the "
+"small program which runs the operating system kernel). <command>SILO</"
+"command> has certain requirements for partition sizes and location; see "
+"<xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: title
@@ -934,25 +1261,49 @@ 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>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>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1071
 #, 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."
+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
 #, 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 ""
+"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."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1090
 #, 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 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."
 msgstr ""
 
 #. Tag: title
@@ -964,7 +1315,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1111
 #, 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)."
+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
@@ -976,7 +1333,15 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1128
 #, 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."
+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
@@ -988,31 +1353,63 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1144
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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>"
+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: title
@@ -1024,29 +1421,53 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1204
 #, 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."
+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:1212
 #, 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."
+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:1220
 #, no-c-format
 msgid ""
-      "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
-      "ok\n"
-      "0 &gt;\n"
-      "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
+"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
+"ok\n"
+"0 &gt;\n"
+"</screen></informalexample> Note that on older model &arch-title; Macs, the "
+"default and sometimes hardwired I/O for OpenFirmware user interaction is "
+"through the serial (modem) port. If you invoke OpenFirmware on one of these "
+"machines, you will just see a black screen. In that case, a terminal program "
+"running on another computer, connected to the modem port, is needed to "
+"interact with OpenFirmware."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1233
 #, 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."
+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
@@ -1058,45 +1479,90 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1255
 #, 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."
+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:1263
 #, 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."
+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:1275
 #, 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."
+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:1288
 #, 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>."
+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:1298
 #, 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"
-      "<replaceable>driver-name</replaceable>@\n"
-      "<replaceable>unit-address</replaceable>:\n"
-      "<replaceable>device-arguments</replaceable>\n"
-      "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
+"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"
+"<replaceable>driver-name</replaceable>@\n"
+"<replaceable>unit-address</replaceable>:\n"
+"<replaceable>device-arguments</replaceable>\n"
+"</screen></informalexample> In older revisions of OpenBoot, device naming is "
+"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
+"disk devices are of the form <quote>sd(<replaceable>controller</"
+"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
+"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
+"newer OpenBoot revisions is useful for viewing the currently configured "
+"devices. For full information, whatever your revision, see the <ulink url="
+"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1321
 #, 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"
-      "# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
-      "</screen></informalexample> and under Solaris:"
+"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"
+"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
+"</screen></informalexample> and under Solaris:"
 msgstr ""
 
 #. Tag: screen
@@ -1114,19 +1580,45 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1351
 #, 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."
+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:1363
 #, 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."
+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:1373
 #, 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."
+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
@@ -1138,7 +1630,12 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1391
 #, 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."
+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
@@ -1150,13 +1647,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1407
 #, 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."
+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:1417
 #, 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."
+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
@@ -1168,13 +1678,21 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1436
 #, 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."
+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:1444
 #, 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."
+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
@@ -1198,7 +1716,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1464
 #, 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."
+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
@@ -1210,6 +1734,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1479
 #, 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>."
+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 ""
-
diff --git a/po/nl/preseed.po b/po/nl/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/nl/preseed.po
+++ b/po/nl/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-
diff --git a/po/nl/random-bits.po b/po/nl/random-bits.po
index ff94f432b..26dbb7c32 100644
--- a/po/nl/random-bits.po
+++ b/po/nl/random-bits.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,7 +29,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:12
 #, no-c-format
-msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below."
+msgid ""
+"In Linux various special files can be found under the directory <filename>/"
+"dev</filename>. These files are called device files and behave unlike "
+"ordinary files. The most common types of device files are for block devices "
+"and character devices. These files are an interface to the actual driver "
+"(part of the Linux kernel) which in turn accesses the hardware. Another, "
+"less common, type of device file is the named <firstterm>pipe</firstterm>. "
+"The most important device files are listed in the tables below."
 msgstr ""
 
 #. Tag: filename
@@ -316,33 +324,62 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:126
 #, no-c-format
-msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. Normally, this is a simple matter of installing <filename>gpm</"
+"filename> and the X server itself. Both should be configured to use "
+"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse "
+"protocol is named <userinput>exps2</userinput> in gpm, and "
+"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files "
+"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:137
 #, no-c-format
-msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>."
+msgid ""
+"Certain kernel modules must be loaded in order for your mouse to work. In "
+"most cases the correct modules are autodetected, but not always for old-"
+"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole "
+"D-shaped connector; bus mice have an 8-pin round connector, not to be "
+"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round "
+"connector of an ADB mouse. </para> </footnote>, which are quite rare except "
+"on very old computers. Summary of Linux kernel modules needed for different "
+"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</"
+"entry> <entry>Description</entry> </row> </thead><tbody> <row> "
+"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </"
+"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</"
+"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> "
+"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech "
+"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse "
+"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></"
+"informaltable> To load a mouse driver module, you can use the "
+"<command>modconf</command> command (from the package with the same name) and "
+"look in the category <userinput>kernel/drivers/input/mouse</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:184
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:191
 #, no-c-format
 msgid ""
-      "# 3-button mouse emulation\n"
-      "# turn on emulation\n"
-      "/dev/mac_hid/mouse_button_emulation = 1\n"
-      "# Send middle mouse button signal with the F11 key\n"
-      "/dev/mac_hid/mouse_button2_keycode = 87\n"
-      "# Send right mouse button signal with the F12 key\n"
-      "/dev/mac_hid/mouse_button3_keycode = 88\n"
-      "# For different keys, use showkey to tell you what the code is."
+"# 3-button mouse emulation\n"
+"# turn on emulation\n"
+"/dev/mac_hid/mouse_button_emulation = 1\n"
+"# Send middle mouse button signal with the F11 key\n"
+"/dev/mac_hid/mouse_button2_keycode = 87\n"
+"# Send right mouse button signal with the F12 key\n"
+"/dev/mac_hid/mouse_button3_keycode = 88\n"
+"# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
 #. Tag: title
@@ -354,31 +391,54 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "A standard installation for the amd64 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB."
+msgid ""
+"A standard installation for the amd64 architecture, including all standard "
+"packages and using the default 2.6 kernel, takes up &std-system-size;MB of "
+"disk space. A minimal base installation, without the <quote>Standard system</"
+"quote> task selected, will take &base-system-size;MB."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:207
 #, no-c-format
-msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use."
+msgid ""
+"In both cases this is the actual disk space used <emphasis>after</emphasis> "
+"the installation is finished and any temporary files deleted. It also does "
+"not take into account overhead used by the file system, for example for "
+"journal files. This means that significantly more disk space is needed both "
+"<emphasis>during</emphasis> the installation and for normal system use."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:216
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:223
 #, no-c-format
-msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)."
+msgid ""
+"By default the installer will install the GNOME desktop environment, but "
+"alternative desktop environments can be selected either by using one of the "
+"special CD images, or by specifying the desired desktop environment when the "
+"installer is booted (see <xref linkend=\"pkgsel\"/>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:230
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the standard installation when determining the size of partitions. Most of "
+"the size listed as <quote>Installed size</quote> will end up in <filename>/"
+"usr</filename> and in <filename>/lib</filename>; the size listed as "
+"<quote>Download size</quote> is (temporarily) required in <filename>/var</"
+"filename>."
 msgstr ""
 
 #. Tag: entry
@@ -522,7 +582,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid ""
+"There is some overlap of the Laptop task with the Desktop environment task. "
+"If you install both, the Laptop task will only require a few MB additional "
+"disk space."
 msgstr ""
 
 #. Tag: entry
@@ -714,7 +777,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:350
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -726,19 +793,40 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:367
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
+msgid ""
+"This section explains how to install &debian-gnu; from an existing Unix or "
+"Linux system, without using the menu-driven installer as explained in the "
+"rest of the manual. This <quote>cross-install</quote> HOWTO has been "
+"requested by users switching to &debian-gnu; from Red Hat, Mandriva, and "
+"SUSE. In this section some familiarity with entering *nix commands and "
+"navigating the file system is assumed. In this section, <prompt>$</prompt> "
+"symbolizes a command to be entered in the user's current system, while "
+"<prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:379
 #, no-c-format
-msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new &debian; system configured to your preference, you "
+"can migrate your existing user data (if any) to it, and keep on rolling. "
+"This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's "
+"also a clever way for dealing with hardware that otherwise doesn't play "
+"friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:390
 #, no-c-format
-msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
+msgid ""
+"As this is a mostly manual procedure, you should bear in mind that you will "
+"need to do a lot of basic configuration of the system yourself, which will "
+"also require more knowledge of &debian; and of &arch-kernel; in general than "
+"performing a regular installation. You cannot expect this procedure to "
+"result in a system that is identical to a system from a regular "
+"installation. You should also keep in mind that this procedure only gives "
+"the basic steps to set up a system. Additional installation and/or "
+"configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
@@ -750,41 +838,56 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:405
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need around &base-"
+"system-size;MB of space available for a console only install, or about &task-"
+"desktop-lxde-inst;MB if you plan to install X (more if you intend to install "
+"desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:413
 #, no-c-format
 msgid ""
-      "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
-      "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
-      "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"Next, create file systems on the partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
+"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:423
 #, no-c-format
 msgid ""
-      "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
-      "# mkswap /dev/<replaceable>hda5</replaceable>\n"
-      "# sync; sync; sync\n"
-      "# swapon /dev/<replaceable>hda5</replaceable>\n"
-      "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"Initialize and activate swap (substitute the partition number for your "
+"intended &debian; swap partition): <informalexample><screen>\n"
+"# mkswap /dev/<replaceable>hda5</replaceable>\n"
+"# sync; sync; sync\n"
+"# swapon /dev/<replaceable>hda5</replaceable>\n"
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:435
 #, no-c-format
 msgid ""
-      "# mkdir /mnt/debinst\n"
-      "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
+"# mkdir /mnt/debinst\n"
+"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:438
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
@@ -796,26 +899,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:449
 #, no-c-format
-msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The utility used by the &debian; installer, and recognized as the official "
+"way to install a &debian; base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname> and basic Unix/Linux "
+"tools<footnote> <para> These include the GNU core utilities and commands "
+"like <command>sed</command>, <command>grep</command>, <command>tar</command> "
+"and <command>gzip</command>. </para> </footnote>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:479
 #, no-c-format
 msgid ""
-      "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
-      "# mkdir work\n"
-      "# cd work\n"
-      "</screen></informalexample> The <command>debootstrap</command> binary is located in the &debian; archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files."
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
+"# mkdir work\n"
+"# cd work\n"
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the &debian; archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the files from it. "
+"You will need to have root privileges to install the files."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:494
 #, no-c-format
 msgid ""
-      "# ar -x debootstrap_0.X.X_all.deb\n"
-      "# cd /\n"
-      "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
+"# ar -x debootstrap_0.X.X_all.deb\n"
+"# cd /\n"
+"# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
 #. Tag: title
@@ -827,27 +945,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any &debian; archive mirror "
+"for <userinput>&archive-mirror;/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:510
 #, no-c-format
-msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>amd64</userinput>, "
+"<userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, "
+"<userinput>mipsel</userinput>, <userinput>powerpc</userinput>, "
+"<userinput>s390</userinput>, <userinput>s390x</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:533
 #, no-c-format
 msgid ""
-      "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
-      "     /mnt/debinst http://ftp.us.debian.org/debian"
+"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
+"     /mnt/debinst http://ftp.us.debian.org/debian"
 msgstr ""
 
 #. Tag: title
@@ -860,9 +993,11 @@ msgstr ""
 #: random-bits.xml:540
 #, no-c-format
 msgid ""
-      "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
-      "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
-      "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:"
+"Now you've got a real &debian; system, though rather lean, on disk. "
+"<command>chroot</command> into it: <informalexample><screen>\n"
+"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
+"</screen></informalexample> After chrooting you may need to set the terminal "
+"definition to be compatible with the &debian; base system, for example:"
 msgstr ""
 
 #. Tag: screen
@@ -880,7 +1015,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:556
 #, no-c-format
-msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
+msgid ""
+"At this point <filename>/dev/</filename> only contains very basic device "
+"files. For the next steps of the installation additional device files may be "
+"needed. There are different ways to go about this and which method you "
+"should use depends on the host system you are using for the installation, on "
+"whether you intend to use a modular kernel or not, and on whether you intend "
+"to use dynamic (e.g. using <classname>udev</classname>) or static device "
+"files for the new system."
 msgstr ""
 
 #. Tag: para
@@ -892,28 +1034,34 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:571
 #, no-c-format
-msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
+msgid ""
+"install the makedev package, and create a default set of static device files "
+"using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:575
 #, no-c-format
 msgid ""
-      "# apt-get install makedev\n"
-      "# cd /dev\n"
-      "# MAKEDEV generic"
+"# apt-get install makedev\n"
+"# cd /dev\n"
+"# MAKEDEV generic"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:578
 #, no-c-format
-msgid "manually create only specific device files using <command>MAKEDEV</command>"
+msgid ""
+"manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:583
 #, no-c-format
-msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
+msgid ""
+"bind mount /dev from your host system on top of /dev in the target system; "
+"note that the postinst scripts of some packages may try to create device "
+"files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
@@ -926,34 +1074,44 @@ msgstr ""
 #: random-bits.xml:597
 #, no-c-format
 msgid ""
-      "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
-      "# editor /etc/fstab\n"
-      "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
-      "# /etc/fstab: static file system information.\n"
-      "#\n"
-      "# file system    mount point   type    options                  dump pass\n"
-      "/dev/XXX         /             ext3    defaults                 0    1\n"
-      "/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
-      "\n"
-      "/dev/XXX         none          swap    sw                       0    0\n"
-      "proc             /proc         proc    defaults                 0    0\n"
-      "\n"
-      "/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
-      "/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
-      "\n"
-      "/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
-      "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-      "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n"
-      "# mount /path   # e.g.: mount /usr\n"
-      "</screen></informalexample> Current &debian; systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n"
-      "# cd /media\n"
-      "# mkdir cdrom0\n"
-      "# ln -s cdrom0 cdrom\n"
-      "# cd /\n"
-      "# ln -s media/cdrom\n"
-      "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
+"# editor /etc/fstab\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
+"# /etc/fstab: static file system information.\n"
+"#\n"
+"# file system    mount point   type    options                  dump pass\n"
+"/dev/XXX         /             ext3    defaults                 0    1\n"
+"/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
+"\n"
+"/dev/XXX         none          swap    sw                       0    0\n"
+"proc             /proc         proc    defaults                 0    0\n"
+"\n"
+"/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
+"/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
+"\n"
+"/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
+"/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or, to mount file systems individually, use: <informalexample><screen>\n"
+"# mount /path   # e.g.: mount /usr\n"
+"</screen></informalexample> Current &debian; systems have mountpoints for "
+"removable media under <filename>/media</filename>, but keep compatibility "
+"symlinks in <filename>/</filename>. Create these as as needed, for example: "
+"<informalexample><screen>\n"
+"# cd /media\n"
+"# mkdir cdrom0\n"
+"# ln -s cdrom0 cdrom\n"
+"# cd /\n"
+"# ln -s media/cdrom\n"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -965,7 +1123,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:625
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -983,15 +1144,19 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:638
 #, no-c-format
-msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
+msgid ""
+"An option in the file <filename>/etc/default/rcS</filename> determines "
+"whether the system will interpret the hardware clock as being set to UTC or "
+"local time. The following command allows you to set that and choose your "
+"timezone."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:645
 #, no-c-format
 msgid ""
-      "# editor /etc/default/rcS\n"
-      "# dpkg-reconfigure tzdata"
+"# editor /etc/default/rcS\n"
+"# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
@@ -1004,54 +1169,64 @@ msgstr ""
 #: random-bits.xml:652
 #, no-c-format
 msgid ""
-      "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
-      "# editor /etc/network/interfaces\n"
-      "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
-      "######################################################################\n"
-      "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
-      "# See the interfaces(5) manpage for information on what options are\n"
-      "# available.\n"
-      "######################################################################\n"
-      "\n"
-      "# We always want the loopback interface.\n"
-      "#\n"
-      "auto lo\n"
-      "iface lo inet loopback\n"
-      "\n"
-      "# To use dhcp:\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet dhcp\n"
-      "\n"
-      "# An example static IP setup: (broadcast and gateway are optional)\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet static\n"
-      "#     address 192.168.0.42\n"
-      "#     network 192.168.0.0\n"
-      "#     netmask 255.255.255.0\n"
-      "#     broadcast 192.168.0.255\n"
-      "#     gateway 192.168.0.1\n"
-      "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "# editor /etc/resolv.conf\n"
-      "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "search hqdom.local\n"
-      "nameserver 10.1.1.36\n"
-      "nameserver 192.168.9.100\n"
-      "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
-      "# echo DebianHostName &gt; /etc/hostname\n"
-      "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n"
-      "127.0.0.1 localhost\n"
-      "127.0.1.1 DebianHostName\n"
-      "\n"
-      "# The following lines are desirable for IPv6 capable hosts\n"
-      "::1     ip6-localhost ip6-loopback\n"
-      "fe00::0 ip6-localnet\n"
-      "ff00::0 ip6-mcastprefix\n"
-      "ff02::1 ip6-allnodes\n"
-      "ff02::2 ip6-allrouters\n"
-      "ff02::3 ip6-allhosts\n"
-      "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> "
+"and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
+"# editor /etc/network/interfaces\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"######################################################################\n"
+"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
+"# See the interfaces(5) manpage for information on what options are\n"
+"# available.\n"
+"######################################################################\n"
+"\n"
+"# We always want the loopback interface.\n"
+"#\n"
+"auto lo\n"
+"iface lo inet loopback\n"
+"\n"
+"# To use dhcp:\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet dhcp\n"
+"\n"
+"# An example static IP setup: (broadcast and gateway are optional)\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet static\n"
+"#     address 192.168.0.42\n"
+"#     network 192.168.0.0\n"
+"#     netmask 255.255.255.0\n"
+"#     broadcast 192.168.0.255\n"
+"#     gateway 192.168.0.1\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"# editor /etc/resolv.conf\n"
+"</screen></informalexample> A simple example <filename>/etc/resolv.conf</"
+"filename>: <informalexample><screen>\n"
+"search hqdom.local\n"
+"nameserver 10.1.1.36\n"
+"nameserver 192.168.9.100\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
+"# echo DebianHostName &gt; /etc/hostname\n"
+"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with "
+"IPv6 support: <informalexample><screen>\n"
+"127.0.0.1 localhost\n"
+"127.0.1.1 DebianHostName\n"
+"\n"
+"# The following lines are desirable for IPv6 capable hosts\n"
+"::1     ip6-localhost ip6-loopback\n"
+"fe00::0 ip6-localnet\n"
+"ff00::0 ip6-mcastprefix\n"
+"ff02::1 ip6-allnodes\n"
+"ff02::2 ip6-allrouters\n"
+"ff02::3 ip6-allhosts\n"
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1064,12 +1239,16 @@ msgstr ""
 #: random-bits.xml:694
 #, no-c-format
 msgid ""
-      "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
-      "deb-src http://ftp.us.debian.org/debian &releasename; main\n"
-      "\n"
-      "deb http://security.debian.org/ &releasename;/updates main\n"
-      "deb-src http://security.debian.org/ &releasename;/updates main\n"
-      "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list."
+"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</"
+"filename> that will allow installing additional packages. However, you may "
+"want to add some additional sources, for example for source packages and "
+"security updates: <informalexample><screen>\n"
+"deb-src http://ftp.us.debian.org/debian &releasename; main\n"
+"\n"
+"deb http://security.debian.org/ &releasename;/updates main\n"
+"deb-src http://security.debian.org/ &releasename;/updates main\n"
+"</screen></informalexample> Make sure to run <userinput>aptitude update</"
+"userinput> after you have made changes to the sources list."
 msgstr ""
 
 #. Tag: title
@@ -1082,24 +1261,29 @@ msgstr ""
 #: random-bits.xml:711
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
-      "# aptitude install locales\n"
-      "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> To configure your keyboard (if needed):"
+"To configure your locale settings to use a language other than English, "
+"install the <classname>locales</classname> support package and configure it. "
+"Currently the use of UTF-8 locales is recommended. "
+"<informalexample><screen>\n"
+"# aptitude install locales\n"
+"# dpkg-reconfigure locales\n"
+"</screen></informalexample> To configure your keyboard (if needed):"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:721
 #, no-c-format
 msgid ""
-      "# aptitude install console-setup\n"
-      "# dpkg-reconfigure keyboard-configuration"
+"# aptitude install console-setup\n"
+"# dpkg-reconfigure keyboard-configuration"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:723
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1111,7 +1295,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:734
 #, no-c-format
-msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
+msgid ""
+"If you intend to boot this system, you probably want a &arch-kernel; kernel "
+"and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
@@ -1129,7 +1315,9 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:745
 #, no-c-format
-msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid ""
+"# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</"
+"replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1141,30 +1329,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:752
 #, no-c-format
-msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
+msgid ""
+"To make your &debian-gnu; system bootable, set up your boot loader to load "
+"the installed kernel with your new root partition. Note that "
+"<command>debootstrap</command> does not install a boot loader, though you "
+"can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:759
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
+msgid ""
+"Check <userinput>info grub</userinput> <phrase arch=\"x86\">or "
+"<userinput>man lilo.conf</userinput></phrase> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing grub2 "
+"<filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</"
+"filename>. For <filename>lilo.conf</filename>, you could also copy it to the "
+"new system and edit it there. After you are done editing, call "
+"<command>lilo</command> (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:771
 #, no-c-format
 msgid ""
-      "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
-      "# aptitude install grub-pc\n"
-      "# grub-install /dev/<replaceable>hda</replaceable>\n"
-      "# update-grub\n"
-      "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>."
+"Installing and setting up <classname>grub2</classname> is as easy as: "
+"<informalexample><screen>\n"
+"# aptitude install grub-pc\n"
+"# grub-install /dev/<replaceable>hda</replaceable>\n"
+"# update-grub\n"
+"</screen></informalexample> The second command will install <command>grub2</"
+"command> (in this case in the MBR of <literal>hda</literal>). The last "
+"command will create a sane and working <filename>/boot/grub/grub.cfg</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:781
 #, no-c-format
-msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
+msgid ""
+"Note that this assumes that a <filename>/dev/hda</filename> device file has "
+"been created. There are alternative methods to install <command>grub2</"
+"command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
@@ -1177,36 +1385,44 @@ msgstr ""
 #: random-bits.xml:791
 #, no-c-format
 msgid ""
-      "boot=/dev/<replaceable>hda6</replaceable>\n"
-      "root=/dev/<replaceable>hda6</replaceable>\n"
-      "install=menu\n"
-      "delay=20\n"
-      "lba32\n"
-      "image=/vmlinuz\n"
-      "initrd=/initrd.img\n"
-      "label=Debian"
+"boot=/dev/<replaceable>hda6</replaceable>\n"
+"root=/dev/<replaceable>hda6</replaceable>\n"
+"install=menu\n"
+"delay=20\n"
+"lba32\n"
+"image=/vmlinuz\n"
+"initrd=/initrd.img\n"
+"label=Debian"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:793
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:803
 #, no-c-format
 msgid ""
-      "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
-      "boot=/dev/hda2\n"
-      "device=hd:\n"
-      "partition=6\n"
-      "root=/dev/hda6\n"
-      "magicboot=/usr/lib/yaboot/ofboot\n"
-      "timeout=50\n"
-      "image=/vmlinux\n"
-      "label=Debian\n"
-      "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
+"boot=/dev/hda2\n"
+"device=hd:\n"
+"partition=6\n"
+"root=/dev/hda6\n"
+"magicboot=/usr/lib/yaboot/ofboot\n"
+"timeout=50\n"
+"image=/vmlinux\n"
+"label=Debian\n"
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1218,15 +1434,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:817
 #, no-c-format
-msgid "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set a password for root:"
+msgid ""
+"In case you can login to the system via console, you can skip this section. "
+"If the system should be accessible via the network later on, you need to "
+"install SSH and set a password for root:"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:823
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+"# aptitude install ssh\n"
+"# passwd"
 msgstr ""
 
 #. Tag: title
@@ -1239,15 +1458,22 @@ msgstr ""
 #: random-bits.xml:829
 #, no-c-format
 msgid ""
-      "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
-      "# tasksel install standard\n"
-      "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually."
+"As mentioned earlier, the installed system will be very basic. If you would "
+"like to make the system a bit more mature, there is an easy method to "
+"install all packages with <quote>standard</quote> priority: "
+"<informalexample><screen>\n"
+"# tasksel install standard\n"
+"</screen></informalexample> Of course, you can also just use "
+"<command>aptitude</command> to install packages individually."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:840
 #, no-c-format
-msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
+msgid ""
+"After the installation there will be a lot of downloaded packages in "
+"<filename>/var/cache/apt/archives/</filename>. You can free up some "
+"diskspace by running:"
 msgstr ""
 
 #. Tag: screen
@@ -1265,25 +1491,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:859
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian-gnu; on a computer without an "
+"Ethernet card, but with just a remote gateway computer attached via a Null-"
+"Modem cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a &debian; mirror on it (e.g. to the "
+"Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:867
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:875
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:880
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1295,7 +1538,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:893
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where &debian; will "
+"be installed."
 msgstr ""
 
 #. Tag: para
@@ -1307,13 +1552,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:904
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:910
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
@@ -1325,28 +1575,33 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:923
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:928
 #, no-c-format
 msgid ""
-      "#!/bin/sh\n"
-      "\n"
-      "# We remove running modules from kernel to avoid conflicts and to\n"
-      "# reconfigure them manually.\n"
-      "modprobe -r lp parport_pc\n"
-      "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
-      "modprobe plip\n"
-      "\n"
-      "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-      "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
-      "\n"
-      "# Configure gateway\n"
-      "modprobe iptable_nat\n"
-      "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
-      "echo 1 > /proc/sys/net/ipv4/ip_forward"
+"#!/bin/sh\n"
+"\n"
+"# We remove running modules from kernel to avoid conflicts and to\n"
+"# reconfigure them manually.\n"
+"modprobe -r lp parport_pc\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
+"modprobe plip\n"
+"\n"
+"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"\n"
+"# Configure gateway\n"
+"modprobe iptable_nat\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
+"echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
 #. Tag: title
@@ -1359,9 +1614,16 @@ msgstr ""
 #: random-bits.xml:935
 #, no-c-format
 msgid ""
-      "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
-      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
-      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to "
+"set parameters for kernel modules, you also need to do this at the boot "
+"prompt. For example, to boot the installer and set values for the <quote>io</"
+"quote> and <quote>irq</quote> options for the parport_pc module, enter the "
+"following at the boot prompt: <informalexample><screen>\n"
+"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc."
+"irq=<replaceable>7</replaceable>\n"
+"</screen></informalexample> Below are the answers that should be given "
+"during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1373,7 +1635,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:956
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1385,13 +1649,20 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:969
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:978
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1409,19 +1680,24 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:998
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1003
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1009
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
@@ -1433,67 +1709,112 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1030
 #, no-c-format
-msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
+msgid ""
+"In some countries PPP over Ethernet (PPPoE) is a common protocol for "
+"broadband (ADSL or cable) connections to an Internet Service Provider. "
+"Setting up a network connection using PPPoE is not supported by default in "
+"the installer, but can be made to work very simply. This section explains "
+"how."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1038
 #, no-c-format
-msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PPPoE connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1043
 #, no-c-format
-msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
+msgid ""
+"To have the option of setting up and using PPPoE during the installation, "
+"you will need to install using one of the CD-ROM/DVD images that are "
+"available. It is not supported for other installation methods (e.g. "
+"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1050
 #, no-c-format
-msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
+msgid ""
+"Installing over PPPoE is mostly the same as any other installation. The "
+"following steps explain the differences."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1058
 #, no-c-format
-msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
+msgid ""
+"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</"
+"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> "
+"for information on how to add a boot parameter. </para> </footnote>. This "
+"will ensure the component responsible for the setup of PPPoE (<classname>ppp-"
+"udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1073
 #, no-c-format
-msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
+msgid ""
+"Follow the regular initial steps of the installation (language, country and "
+"keyboard selection; the loading of additional installer components<footnote> "
+"<para> The <classname>ppp-udeb</classname> component is loaded as one of the "
+"additional components in this step. If you want to install at medium or low "
+"priority (expert mode), you can also manually select the <classname>ppp-"
+"udeb</classname> instead of entering the <quote>modules</quote> parameter at "
+"the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1092
 #, no-c-format
-msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
+msgid ""
+"The next step is the detection of network hardware, in order to identify any "
+"Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1098
 #, no-c-format
-msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
+msgid ""
+"After this the actual setup of PPPoE is started. The installer will probe "
+"all the detected Ethernet interfaces in an attempt to find a PPPoE "
+"concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1104
 #, no-c-format
-msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
+msgid ""
+"It is possible that the concentrator will not to be found at the first "
+"attempt. This can happen occasionally on slow or loaded networks or with "
+"faulty servers. In most cases a second attempt to detect the concentrator "
+"will be successful; to retry, select <guimenuitem>Configure and start a "
+"PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1113
 #, no-c-format
-msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
+msgid ""
+"After a concentrator is found, the user will be prompted to type the login "
+"information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1119
 #, no-c-format
-msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
+msgid ""
+"At this point the installer will use the provided information to establish "
+"the PPPoE connection. If the correct information was provided, the PPPoE "
+"connection should be configured and the installer should be able to use it "
+"to connect to the Internet and retrieve packages over it (if needed). If the "
+"login information is not correct or some error appears, the installer will "
+"stop, but the configuration can be attempted again by selecting the menu "
+"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
@@ -1505,49 +1826,89 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1140
 #, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
+msgid ""
+"The graphical version of the installer is only available for a limited "
+"number of architectures, including &arch-title;. The functionality of the "
+"graphical installer is essentially the same as that of the regular installer "
+"as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1148
 #, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
+msgid ""
+"Although the functionality is identical, the graphical installer still has a "
+"few significant advantages. The main advantage is that it supports more "
+"languages, namely those that use a character set that cannot be displayed "
+"with the regular <quote>newt</quote> frontend. It also has a few usability "
+"advantages such as the option to use a mouse, and in some cases several "
+"questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1157
 #, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
+msgid ""
+"The graphical installer is available with all CD images and with the hd-"
+"media installation method. To boot the graphical installer simply select the "
+"relevant option from the boot menu. Expert and rescue mode for the graphical "
+"installer can be selected from the <quote>Advanced options</quote> menu. The "
+"previously used boot methods <userinput>installgui</userinput>, "
+"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
+"still be used from the boot prompt which is shown after selecting the "
+"<quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1168
 #, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
+msgid ""
+"There is also a graphical installer image that can be netbooted. And there "
+"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> "
+"<para> The mini ISO image can be downloaded from a &debian; mirror as "
+"described in <xref linkend=\"downloading-files\"/>. Look for "
+"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
+"mainly useful for testing."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1181
 #, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
+msgid ""
+"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
+"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image "
+"can be downloaded from a &debian; mirror as described in <xref linkend="
+"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
+"</para> </footnote>. It should work on almost all PowerPC systems that have "
+"an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1195
 #, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
+msgid ""
+"Just as with the regular installer it is possible to add boot parameters "
+"when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1201
 #, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
+msgid ""
+"The graphical installer requires significantly more memory to run than the "
+"regular installer: &minimum-memory-gtk;. If insufficient memory is "
+"available, it will automatically fall back to the regular <quote>newt</"
+"quote> frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1208
 #, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
+msgid ""
+"If the amount of memory in your system is below &minimum-memory;, the "
+"graphical installer may fail to boot at all while booting the regular "
+"installer would still work. Using the regular installer is recommended for "
+"systems with little available memory."
 msgstr ""
 
 #. Tag: title
@@ -1559,24 +1920,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1219
 #, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
+msgid ""
+"As already mentioned, the graphical installer basically works the same as "
+"the regular installer and thus the rest of this manual can be used to guide "
+"you through the installation process."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1225
 #, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgid ""
+"If you prefer using the keyboard over the mouse, there are two things you "
+"need to know. To expand a collapsed list (used for example for the selection "
+"of countries within continents), you can use the <keycap>+</keycap> and "
+"<keycap>-</keycap> keys. For questions where more than one item can be "
+"selected (e.g. task selection), you first need to tab to the &BTN-CONT; "
+"button after making your selections; hitting enter will toggle a selection, "
+"not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1235
 #, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgid ""
+"If a dialog offers additional help information, a <guibutton>Help</"
+"guibutton> button will be displayed. The help information can be accessed "
+"either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1241
 #, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgid ""
+"To switch to another console, you will also need to use the <keycap>Ctrl</"
+"keycap> key, just as with the X Window System. For example, to switch to VT2 "
+"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> "
+"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical "
+"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</"
+"keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""
-
diff --git a/po/nl/using-d-i.po b/po/nl/using-d-i.po
index bbba423e4..85197cce6 100644
--- a/po/nl/using-d-i.po
+++ b/po/nl/using-d-i.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,79 +29,147 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:8
 #, no-c-format
-msgid "The &debian; Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started."
+msgid ""
+"The &debian; Installer consists of a number of special-purpose components to "
+"perform each installation task. Each component performs its task, asking the "
+"user questions as necessary to do its job. The questions themselves are "
+"given priorities, and the priority of questions to be asked is set when the "
+"installer is started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:16
 #, no-c-format
-msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked."
+msgid ""
+"When a default installation is performed, only essential (high priority) "
+"questions will be asked. This results in a highly automated installation "
+"process with little user interaction. Components are automatically run in "
+"sequence; which components are run depends mainly on the installation method "
+"you use and on your hardware. The installer will use default values for "
+"questions that are not asked."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:25
 #, no-c-format
-msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified."
+msgid ""
+"If there is a problem, the user will see an error screen, and the installer "
+"menu may be shown in order to select some alternative action. If there are "
+"no problems, the user will never see the installer menu, but will simply "
+"answer questions for each component in turn. Serious error notifications are "
+"set to priority <quote>critical</quote> so the user will always be notified."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:34
 #, no-c-format
-msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
+msgid ""
+"Some of the defaults that the installer uses can be influenced by passing "
+"boot arguments when &d-i; is started. If, for example, you wish to force "
+"static network configuration (DHCP is used by default if available), you "
+"could add the boot parameter <userinput>netcfg/disable_dhcp=true</"
+"userinput>. See <xref linkend=\"installer-args\"/> for available options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:42
 #, no-c-format
-msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>."
+msgid ""
+"Power users may be more comfortable with a menu-driven interface, where each "
+"step is controlled by the user rather than the installer performing each "
+"step automatically in sequence. To use the installer in a manual, menu-"
+"driven way, add the boot argument <userinput>priority=medium</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:50
 #, no-c-format
-msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;."
+msgid ""
+"If your hardware requires you to pass options to kernel modules as they are "
+"installed, you will need to start the installer in <quote>expert</quote> "
+"mode. This can be done by either using the <command>expert</command> command "
+"to start the installer or by adding the boot argument "
+"<userinput>priority=low</userinput>. Expert mode gives you full control over "
+"&d-i;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:59
 #, no-c-format
-msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgid ""
+"For this architecture the &d-i; supports two different user interfaces: a "
+"character-based one and a graphical one. The character-based interface is "
+"used by default unless you selected the <quote>Graphical install</quote> "
+"option in the initial boot menu. For more information about the graphical "
+"installer, please refer to <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:67
 #, no-c-format
-msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
+msgid ""
+"For this architecture the installer uses a character-based user interface. A "
+"graphical user interface is currently not available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:72
 #, no-c-format
-msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
+msgid ""
+"In the character-based environment the use of a mouse is not supported. Here "
+"are the keys you can use to navigate within the various dialogs. The "
+"<keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move "
+"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> "
+"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move "
+"<quote>backward</quote> between displayed buttons and selections. The "
+"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items "
+"within a scrollable list, and also scroll the list itself. In addition, in "
+"long lists, you can type a letter to cause the list to scroll directly to "
+"the section with items starting with the letter you typed and use <keycap>Pg-"
+"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The "
+"<keycap>space bar</keycap> selects an item such as a checkbox. Use "
+"&enterkey; to activate choices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:89
 #, no-c-format
-msgid "Some dialogs may offer additional help information. If help is available this will be indicated on the bottom line of the screen by displaying that help information can be accessed by pressing the <keycap>F1</keycap> key."
+msgid ""
+"Some dialogs may offer additional help information. If help is available "
+"this will be indicated on the bottom line of the screen by displaying that "
+"help information can be accessed by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:95
 #, no-c-format
-msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
+msgid ""
+"S/390 does not support virtual consoles. You may open a second and third ssh "
+"session to view the logs described below."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:100
 #, no-c-format
-msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"Error messages and logs are redirected to the fourth console. You can access "
+"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</"
+"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing "
+"the <keycap>F4</keycap> function key); get back to the main installer "
+"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></"
+"keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:110
 #, no-c-format
-msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"These messages can also be found in <filename>/var/log/syslog</filename>. "
+"After installation, this log is copied to <filename>/var/log/installer/"
+"syslog</filename> on your new system. Other installation messages may be "
+"found in <filename>/var/log/</filename> during the installation, and "
+"<filename>/var/log/installer/</filename> after the computer has been booted "
+"into the installed system."
 msgstr ""
 
 #. Tag: title
@@ -112,7 +181,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:125
 #, no-c-format
-msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
+msgid ""
+"Here is a list of installer components with a brief description of each "
+"component's purpose. Details you might need to know about using a particular "
+"component are in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: term
@@ -124,13 +196,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:136
 #, no-c-format
-msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
+msgid ""
+"Shows the list of components to the user during installer operation, and "
+"starts a component when it is selected. Main-menu's questions are set to "
+"priority medium, so if your priority is set to high or critical (high is the "
+"default), you will not see the menu. On the other hand, if there is an error "
+"which requires your intervention, the question priority may be downgraded "
+"temporarily to allow you to resolve the problem, and in that case the menu "
+"may appear."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:146
 #, no-c-format
-msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
+msgid ""
+"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly "
+"to back all the way out of the currently running component."
 msgstr ""
 
 #. Tag: term
@@ -142,7 +223,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:155
 #, no-c-format
-msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
+msgid ""
+"Allows the user to select localization options for the installation and the "
+"installed system: language, country and locales. The installer will display "
+"messages in the selected language, unless the translation for that language "
+"is not complete in which case some messages may be shown in English."
 msgstr ""
 
 #. Tag: term
@@ -154,7 +239,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:167
 #, no-c-format
-msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
+msgid ""
+"Shows a list of keyboards, from which the user chooses the model which "
+"matches his own."
 msgstr ""
 
 #. Tag: term
@@ -166,7 +253,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:176
 #, no-c-format
-msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
+msgid ""
+"Automatically detects most of the system's hardware, including network "
+"cards, disk drives, and PCMCIA."
 msgstr ""
 
 #. Tag: term
@@ -190,7 +279,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:193
 #, no-c-format
-msgid "Configures the computer's network connections so it can communicate over the internet."
+msgid ""
+"Configures the computer's network connections so it can communicate over the "
+"internet."
 msgstr ""
 
 #. Tag: term
@@ -202,7 +293,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:202
 #, no-c-format
-msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
+msgid ""
+"Searches for ISO images (<filename>.iso</filename> files) on hard drives."
 msgstr ""
 
 #. Tag: term
@@ -214,7 +306,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:210
 #, no-c-format
-msgid "Presents a list of &debian; archive mirrors. The user may choose the source of his installation packages."
+msgid ""
+"Presents a list of &debian; archive mirrors. The user may choose the source "
+"of his installation packages."
 msgstr ""
 
 #. Tag: term
@@ -226,7 +320,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:219
 #, no-c-format
-msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
+msgid ""
+"Checks integrity of a CD-ROM. This way, the user may assure him/herself that "
+"the installation CD-ROM was not corrupted."
 msgstr ""
 
 #. Tag: term
@@ -238,7 +334,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:228
 #, no-c-format
-msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
+msgid ""
+"Lowmem tries to detect systems with low memory and then does various tricks "
+"to remove unnecessary parts of &d-i; from the memory (at the cost of some "
+"features)."
 msgstr ""
 
 #. Tag: term
@@ -250,7 +349,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:238
 #, no-c-format
-msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
+msgid ""
+"Anna's Not Nearly APT. Installs packages which have been retrieved from the "
+"chosen mirror or CD."
 msgstr ""
 
 #. Tag: term
@@ -274,7 +375,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:255
 #, no-c-format
-msgid "Updates the system clock and determines whether the clock is set to UTC or not."
+msgid ""
+"Updates the system clock and determines whether the clock is set to UTC or "
+"not."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +401,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:272
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
+msgid ""
+"Allows the user to partition disks attached to the system, create file "
+"systems on the selected partitions, and attach them to the mountpoints. "
+"Included are also interesting features like a fully automatic mode or LVM "
+"support. This is the preferred partitioning tool in &debian;."
 msgstr ""
 
 #. Tag: term
@@ -310,7 +417,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:284
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
+msgid ""
+"Allows the user to partition disks attached to the system. A partitioning "
+"program appropriate to your computer's architecture is chosen."
 msgstr ""
 
 #. Tag: term
@@ -322,7 +431,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:294
 #, no-c-format
-msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
+msgid ""
+"Displays a list of partitions, and creates file systems on the selected "
+"partitions according to user instructions."
 msgstr ""
 
 #. Tag: term
@@ -334,7 +445,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:303
 #, no-c-format
-msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
+msgid ""
+"Helps the user with the configuration of the <firstterm>LVM</firstterm> "
+"(Logical Volume Manager)."
 msgstr ""
 
 #. Tag: term
@@ -346,7 +459,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:312
 #, no-c-format
-msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
+msgid ""
+"Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant "
+"Array of Inexpensive Disks). This Software RAID is usually superior to the "
+"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
 #. Tag: term
@@ -358,7 +474,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:323
 #, no-c-format
-msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
+msgid ""
+"Installs the most basic set of packages which would allow the computer to "
+"operate under &debian-gnu; when rebooted."
 msgstr ""
 
 #. Tag: term
@@ -370,7 +488,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:332
 #, no-c-format
-msgid "Configures apt, mostly automatically, based on what media the installer is running from."
+msgid ""
+"Configures apt, mostly automatically, based on what media the installer is "
+"running from."
 msgstr ""
 
 #. Tag: term
@@ -382,7 +502,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:341
 #, no-c-format
-msgid "Uses <classname>tasksel</classname> to select and install additional software."
+msgid ""
+"Uses <classname>tasksel</classname> to select and install additional "
+"software."
 msgstr ""
 
 #. Tag: term
@@ -394,7 +516,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:349
 #, no-c-format
-msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
+msgid ""
+"Detects currently installed operating systems on the computer and passes "
+"this information to the bootloader-installer, which may offer you an ability "
+"to add discovered operating systems to the bootloader's start menu. This way "
+"the user could easily choose at the boot time which operating system to "
+"start."
 msgstr ""
 
 #. Tag: term
@@ -406,7 +533,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:361
 #, no-c-format
-msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
+msgid ""
+"The various bootloader installers each install a boot loader program on the "
+"hard disk, which is necessary for the computer to start up using &arch-"
+"kernel; without using a floppy or CD-ROM. Many boot loaders allow the user "
+"to choose an alternate operating system each time the computer boots."
 msgstr ""
 
 #. Tag: term
@@ -418,7 +549,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:372
 #, no-c-format
-msgid "Allows the user to execute a shell from the menu, or in the second console."
+msgid ""
+"Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
 #. Tag: term
@@ -430,7 +562,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:381
 #, no-c-format
-msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to &debian; developers later."
+msgid ""
+"Provides a way for the user to record information on a floppy disk, network, "
+"hard disk, or other media when trouble is encountered, in order to "
+"accurately report installer software problems to &debian; developers later."
 msgstr ""
 
 #. Tag: title
@@ -442,7 +577,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:400
 #, no-c-format
-msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
+msgid ""
+"In this section we will describe each installer component in detail. The "
+"components have been grouped into stages that should be recognizable for "
+"users. They are presented in the order they appear during the install. Note "
+"that not all modules will be used for every installation; which modules are "
+"actually used depends on the installation method you use and on your "
+"hardware."
 msgstr ""
 
 #. Tag: title
@@ -454,19 +595,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:413
 #, no-c-format
-msgid "Let's assume the &debian; Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
+msgid ""
+"Let's assume the &debian; Installer has booted and you are facing its first "
+"screen. At this time, the capabilities of &d-i; are still quite limited. It "
+"doesn't know much about your hardware, preferred language, or even the task "
+"it should perform. Don't worry. Because &d-i; is quite clever, it can "
+"automatically probe your hardware, locate the rest of its components and "
+"upgrade itself to a capable installation system. However, you still need to "
+"help &d-i; with some information it can't determine automatically (like "
+"selecting your preferred language, keyboard layout or desired network "
+"mirror)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:426
 #, no-c-format
-msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
+msgid ""
+"You will notice that &d-i; performs <firstterm>hardware detection</"
+"firstterm> several times during this stage. The first time is targeted "
+"specifically at the hardware needed to load installer components (e.g. your "
+"CD-ROM or network card). As not all drivers may be available during this "
+"first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:434
 #, no-c-format
-msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
+msgid ""
+"During hardware detection &d-i; checks if any of the drivers for the "
+"hardware devices in your system require firmware to be loaded. If any "
+"firmware is requested but unavailable, a dialog will be displayed that "
+"allows the missing firmware to be loaded from a removable medium. See <xref "
+"linkend=\"loading-firmware\"/> for further details."
 msgstr ""
 
 #. Tag: title
@@ -478,43 +638,75 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:451
 #, no-c-format
-msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system."
+msgid ""
+"One of the first things &d-i; does, is to check available memory. If the "
+"available memory is limited, this component will make some changes in the "
+"installation process which hopefully will allow you to install &debian-gnu; "
+"on your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:458
 #, no-c-format
-msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
+msgid ""
+"The first measure taken to reduce memory consumption by the installer is to "
+"disable translations, which means that the installation can only be done in "
+"English. Of course, you can still localize the installed system after the "
+"installation has completed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:465
 #, no-c-format
-msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
+msgid ""
+"If that is not sufficient, the installer will further reduce memory "
+"consumption by loading only those components essential to complete a basic "
+"installation. This reduces the functionality of the installation system. You "
+"will be given the opportunity to load additional components manually, but "
+"you should be aware that each component you select will use additional "
+"memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:474
 #, no-c-format
-msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
+msgid ""
+"If the installer runs in low memory mode, it is recommended to create a "
+"relatively large swap partition (64&ndash;128MB). The swap partition will be "
+"used as virtual memory and thus increases the amount of memory available to "
+"the system. The installer will activate the swap partition as early as "
+"possible in the installation process. Note that heavy use of swap will "
+"reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:484
 #, no-c-format
-msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
+msgid ""
+"Despite these measures, it is still possible that your system freezes, that "
+"unexpected errors occur or that processes are killed by the kernel because "
+"the system runs out of memory (which will result in <quote>Out of memory</"
+"quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:491
 #, no-c-format
-msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
+msgid ""
+"For example, it has been reported that creating a big ext3 file system fails "
+"in low memory mode when there is insufficient swap space. If a larger swap "
+"doesn't help, try creating the file system as ext2 (which is an essential "
+"component of the installer) instead. It is possible to change an ext2 "
+"partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:499
 #, no-c-format
-msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
+msgid ""
+"It is possible to force the installer to use a higher lowmem level than the "
+"one based on available memory by using the boot parameter <quote>lowmem</"
+"quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
@@ -526,61 +718,116 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:516
 #, no-c-format
-msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, location and locales."
+msgid ""
+"In most cases the first questions you will be asked concern the selection of "
+"localization options to be used both for the installation and for the "
+"installed system. The localization options consist of language, location and "
+"locales."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:523
 #, no-c-format
-msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
+msgid ""
+"The language you choose will be used for the rest of the installation "
+"process, provided a translation of the different dialogs is available. If no "
+"valid translation is available for the selected language, the installer will "
+"default to English."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:530
 #, no-c-format
-msgid "The selected geographic location (in most cases a country) will be used later in the installation process to select the correct time zone and a &debian; mirror appropriate for that country. Language and country together will help determine the default locale for your system and select the correct keyboard layout."
+msgid ""
+"The selected geographic location (in most cases a country) will be used "
+"later in the installation process to select the correct time zone and a "
+"&debian; mirror appropriate for that country. Language and country together "
+"will help determine the default locale for your system and select the "
+"correct keyboard layout."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:538
 #, no-c-format
-msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
+msgid ""
+"You will first be asked to select your preferred language. The language "
+"names are listed both in English (left side) and in the language itself "
+"(right side); the names on the right side are also shown in the proper "
+"script for the language. The list is sorted on the English names. At the top "
+"of the list is an extra option that allows you to select the <quote>C</"
+"quote> locale instead of a language. Choosing the <quote>C</quote> locale "
+"will result in the installation proceding in English; the installed system "
+"will have no localization support as the <classname>locales</classname> "
+"package will not be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:550
 #, no-c-format
-msgid "Next you will be asked to select your geographic location. If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
+msgid ""
+"Next you will be asked to select your geographic location. If you selected a "
+"language that is recognized as an official language for more than one "
+"country<footnote> <para> In technical terms: where multiple locales exist "
+"for that language with differing country codes. </para> </footnote>, you "
+"will be shown a list of only those countries. To select a country that is "
+"not in that list, choose <guimenuitem>other</guimenuitem> (the last option). "
+"You will then be presented with a list of continents; selecting a continent "
+"will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:567
 #, no-c-format
-msgid "If the language has only one country associated with it, a list of countries will be displayed for the continent or region the country belongs to, with that country selected as the default. Use the <guibutton>Go Back</guibutton> option to select countries on a different continent."
+msgid ""
+"If the language has only one country associated with it, a list of countries "
+"will be displayed for the continent or region the country belongs to, with "
+"that country selected as the default. Use the <guibutton>Go Back</guibutton> "
+"option to select countries on a different continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:574
 #, no-c-format
-msgid "It is important to select the country where you live or where you are located as it determines the time zone that will be configured for the installed system."
+msgid ""
+"It is important to select the country where you live or where you are "
+"located as it determines the time zone that will be configured for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:580
 #, no-c-format
-msgid "If you selected a combination of language and country for which no locale is defined and there exist multiple locales for the language, then the installer will allow you to choose which of those locales you prefer as the default locale for the installed system<footnote> <para> At medium and low priority you can always select your preferred locale from those available for the selected language (if there's more than one). </para> </footnote>. In all other cases a default locale will be selected based on the selected language and country."
+msgid ""
+"If you selected a combination of language and country for which no locale is "
+"defined and there exist multiple locales for the language, then the "
+"installer will allow you to choose which of those locales you prefer as the "
+"default locale for the installed system<footnote> <para> At medium and low "
+"priority you can always select your preferred locale from those available "
+"for the selected language (if there's more than one). </para> </footnote>. "
+"In all other cases a default locale will be selected based on the selected "
+"language and country."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:595
 #, no-c-format
-msgid "Any default locale selected as described in the previous paragraph will use <firstterm>UTF-8</firstterm> as character encoding."
+msgid ""
+"Any default locale selected as described in the previous paragraph will use "
+"<firstterm>UTF-8</firstterm> as character encoding."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:600
 #, no-c-format
-msgid "If you are installing at low priority, you will have the option of selecting additional locales, including so-called <quote>legacy</quote> locales<footnote> <para> Legacy locales are locales which do not use UTF-8, but one of the older standards for character encoding such as ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by Japanese). </para> </footnote>, to be generated for the installed system; if you do, you will be asked which of the selected locales should be the default for the installed system."
+msgid ""
+"If you are installing at low priority, you will have the option of selecting "
+"additional locales, including so-called <quote>legacy</quote> "
+"locales<footnote> <para> Legacy locales are locales which do not use UTF-8, "
+"but one of the older standards for character encoding such as "
+"ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by "
+"Japanese). </para> </footnote>, to be generated for the installed system; if "
+"you do, you will be asked which of the selected locales should be the "
+"default for the installed system."
 msgstr ""
 
 #. Tag: title
@@ -592,13 +839,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:626
 #, no-c-format
-msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>dpkg-reconfigure keyboard-configuration</command> as root after you have completed the installation)."
+msgid ""
+"Keyboards are often tailored to the characters used in a language. Select a "
+"layout that conforms to the keyboard you are using, or select something "
+"close if the keyboard layout you want isn't represented. Once the system "
+"installation is complete, you'll be able to select a keyboard layout from a "
+"wider range of choices (run <command>dpkg-reconfigure keyboard-"
+"configuration</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:636
 #, no-c-format
-msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration."
+msgid ""
+"Move the highlight to the keyboard selection you desire and press "
+"&enterkey;. Use the arrow keys to move the highlight &mdash; they are in the "
+"same place in all national language keyboard layouts, so they are "
+"independent of the keyboard configuration."
 msgstr ""
 
 #. Tag: title
@@ -610,25 +867,51 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:664
 #, no-c-format
-msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the &debian; Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
+msgid ""
+"When installing via the <emphasis>hd-media</emphasis> method, there will be "
+"a moment where you need to find and mount the &debian; Installer iso image "
+"in order to get the rest of the installation files. The component "
+"<command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:671
 #, no-c-format
-msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid &debian; iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
+msgid ""
+"At first, <command>iso-scan</command> automatically mounts all block devices "
+"(e.g. partitions) which have some known filesystem on them and sequentially "
+"searches for filenames ending with <filename>.iso</filename> (or <filename>."
+"ISO</filename> for that matter). Beware that the first attempt scans only "
+"files in the root directory and in the first level of subdirectories (i.e. "
+"it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, "
+"<filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not "
+"<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). "
+"After an iso image has been found, <command>iso-scan</command> checks its "
+"content to determine if the image is a valid &debian; iso image or not. In "
+"the former case we are done, in the latter <command>iso-scan</command> seeks "
+"for another image."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:688
 #, no-c-format
-msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
+msgid ""
+"In case the previous attempt to find an installer iso image fails, "
+"<command>iso-scan</command> will ask you whether you would like to perform a "
+"more thorough search. This pass doesn't just look into the topmost "
+"directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:695
 #, no-c-format
-msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
+msgid ""
+"If <command>iso-scan</command> does not discover your installer iso image, "
+"reboot back to your original operating system and check if the image is "
+"named correctly (ending in <filename>.iso</filename>), if it is placed on a "
+"filesystem recognizable by &d-i;, and if it is not corrupted (verify the "
+"checksum). Experienced Unix users could do this without rebooting on the "
+"second console."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +923,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:718
 #, no-c-format
-msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
+msgid ""
+"As you enter this step, if the system detects that you have more than one "
+"network device, you'll be asked to choose which device will be your "
+"<emphasis>primary</emphasis> network interface, i.e. the one which you want "
+"to use for installation. The other interfaces won't be configured at this "
+"time. You may configure additional interfaces after installation is "
+"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> "
+"<manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: title
@@ -652,7 +942,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:733
 #, no-c-format
-msgid "By default, &d-i; tries to configure your computer's network automatically as far as possible. If the automatic configuration fails, that may be caused by many factors ranging from an unplugged network cable to missing infrastructure for automatic configuration. For further explanation in case of errors, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. Sometimes the network services used for autoconfiguration can be slow in their responses, so if you are sure everything is in place, simply start the autoconfiguration attempt again. If autoconfiguration fails repeatedly, you can instead choose the manual network setup."
+msgid ""
+"By default, &d-i; tries to configure your computer's network automatically "
+"as far as possible. If the automatic configuration fails, that may be caused "
+"by many factors ranging from an unplugged network cable to missing "
+"infrastructure for automatic configuration. For further explanation in case "
+"of errors, check the error messages on the fourth console. In any case, you "
+"will be asked if you want to retry, or if you want to perform a manual "
+"setup. Sometimes the network services used for autoconfiguration can be slow "
+"in their responses, so if you are sure everything is in place, simply start "
+"the autoconfiguration attempt again. If autoconfiguration fails repeatedly, "
+"you can instead choose the manual network setup."
 msgstr ""
 
 #. Tag: title
@@ -664,13 +964,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:753
 #, no-c-format
-msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network name</quote>) and a <computeroutput>WEP key</computeroutput> or <computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
+msgid ""
+"The manual network setup in turn asks you a number of questions about your "
+"network, notably <computeroutput>IP address</computeroutput>, "
+"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</"
+"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and "
+"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a "
+"wireless network interface, you will be asked to provide your "
+"<computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network "
+"name</quote>) and a <computeroutput>WEP key</computeroutput> or "
+"<computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers "
+"from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:769
 #, no-c-format
-msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
+msgid ""
+"Some technical details you might, or might not, find handy: the program "
+"assumes the network IP address is the bitwise-AND of your system's IP "
+"address and your netmask. The default broadcast address is calculated as the "
+"bitwise OR of your system's IP address with the bitwise negation of the "
+"netmask. It will also guess your gateway. If you can't find any of these "
+"answers, use the offered defaults &mdash; if necessary, you can change them "
+"by editing <filename>/etc/network/interfaces</filename> once the system has "
+"been installed."
 msgstr ""
 
 #. Tag: title
@@ -682,13 +1000,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:785
 #, no-c-format
-msgid "From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
+msgid ""
+"From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 "
+"as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and "
+"IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:791
 #, no-c-format
-msgid "Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration using NDP (Neighbor Discovery Protocol, including recursive DNS server (RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed stateless/stateful autoconfiguration (address configuration via NDP, additional parameters via DHCPv6)."
+msgid ""
+"Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration "
+"Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration "
+"using NDP (Neighbor Discovery Protocol, including recursive DNS server "
+"(RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed "
+"stateless/stateful autoconfiguration (address configuration via NDP, "
+"additional parameters via DHCPv6)."
 msgstr ""
 
 #. Tag: title
@@ -700,7 +1027,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:839
 #, no-c-format
-msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
+msgid ""
+"The installer will first attempt to connect to a time server on the Internet "
+"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set "
+"the system time. If this does not succeed, the installer will assume the "
+"time and date obtained from the system clock when the installation system "
+"was booted are correct. It is not possible to manually set the system time "
+"during the installation process."
 msgstr ""
 
 #. Tag: para
@@ -712,25 +1045,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:861
 #, no-c-format
-msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone."
+msgid ""
+"Depending on the location selected earlier in the installation process, you "
+"may be shown a list of time zones relevant for that location. If your "
+"location has only one time zone and you are doing a default installation, "
+"you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:869
 #, no-c-format
-msgid "In expert mode or when installing at medium priority, you will have the additional option to select <quote>Coordinated Universal Time</quote> (UTC) as time zone."
+msgid ""
+"In expert mode or when installing at medium priority, you will have the "
+"additional option to select <quote>Coordinated Universal Time</quote> (UTC) "
+"as time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:875
 #, no-c-format
-msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
+msgid ""
+"If for some reason you wish to set a time zone for the installed system that "
+"does <emphasis>not</emphasis> match the selected location, there are two "
+"options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:886
 #, no-c-format
-msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:"
+msgid ""
+"The simplest option is to just select a different time zone after the "
+"installation has been completed and you've booted into the new system. The "
+"command to do this is:"
 msgstr ""
 
 #. Tag: screen
@@ -742,13 +1088,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:898
 #, no-c-format
-msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
+msgid ""
+"Alternatively, the time zone can be set at the very start of the "
+"installation by passing the parameter <userinput>time/"
+"zone=<replaceable>value</replaceable></userinput> when you boot the "
+"installation system. The value should of course be a valid time zone, for "
+"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:912
 #, no-c-format
-msgid "For automated installations the time zone can be set to any desired value using preseeding."
+msgid ""
+"For automated installations the time zone can be set to any desired value "
+"using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -760,7 +1113,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:927
 #, no-c-format
-msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
+msgid ""
+"Just before configuring the clock, the installer will allow you to set up "
+"the <quote>root</quote> account and/or an account for the first user. Other "
+"user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
@@ -772,19 +1128,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:945
 #, no-c-format
-msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
+msgid ""
+"The <emphasis>root</emphasis> account is also called the <emphasis>super-"
+"user</emphasis>; it is a login that bypasses all security protection on your "
+"system. The root account should only be used to perform system "
+"administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:953
 #, no-c-format
-msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
+msgid ""
+"Any password you create should contain at least 6 characters, and should "
+"contain both upper- and lower-case characters, as well as punctuation "
+"characters. Take extra care when setting your root password, since it is "
+"such a powerful account. Avoid dictionary words or use of any personal "
+"information which could be guessed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:961
 #, no-c-format
-msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
+msgid ""
+"If anyone ever tells you they need your root password, be extremely wary. "
+"You should normally never give your root password out, unless you are "
+"administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
@@ -796,25 +1164,42 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:973
 #, no-c-format
-msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
+msgid ""
+"The system will ask you whether you wish to create an ordinary user account "
+"at this point. This account should be your main personal log-in. You should "
+"<emphasis>not</emphasis> use the root account for daily use or as your "
+"personal login."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:982
 #, no-c-format
-msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
+msgid ""
+"Why not? Well, one reason to avoid using root's privileges is that it is "
+"very easy to do irreparable damage as root. Another reason is that you might "
+"be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; "
+"that is a program that takes advantage of your super-user powers to "
+"compromise the security of your system behind your back. Any good book on "
+"Unix system administration will cover this topic in more detail &mdash; "
+"consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:992
 #, no-c-format
-msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
+msgid ""
+"You will first be prompted for the user's full name. Then you'll be asked "
+"for a name for the user account; generally your first name or something "
+"similar will suffice and indeed will be the default. Finally, you will be "
+"prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:999
 #, no-c-format
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgid ""
+"If at any point after installation you would like to create another account, "
+"use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
@@ -826,28 +1211,45 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1011
 #, no-c-format
-msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
+msgid ""
+"At this time, after hardware detection has been executed a final time, &d-i; "
+"should be at its full strength, customized for the user's needs and ready to "
+"do some real work. As the title of this section indicates, the main task of "
+"the next few components lies in partitioning your disks, creating "
+"filesystems, assigning mountpoints and optionally configuring closely "
+"related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1032
 #, no-c-format
-msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
+msgid ""
+"If you are uncomfortable with partitioning, or just want to know more "
+"details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1038
 #, no-c-format
 msgid ""
-      "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
-      "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n"
-      "</screen></informalexample> Note that this will make any existing data on that disk inaccessible."
+"If a hard disk has previously used under Solaris, the partitioner may not "
+"detect the size of the drive correctly. Creating a new partition table does "
+"not fix this issue. What does help, is to <quote>zero</quote> the first few "
+"sectors of the drive: <informalexample><screen>\n"
+"# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; "
+"sync\n"
+"</screen></informalexample> Note that this will make any existing data on "
+"that disk inaccessible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1051
 #, no-c-format
-msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"First you will be given the opportunity to automatically partition either an "
+"entire drive, or available free space on a drive. This is also called "
+"<quote>guided</quote> partitioning. If you do not want to autopartition, "
+"choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
@@ -859,19 +1261,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1062
 #, no-c-format
-msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
+msgid ""
+"The partitioner used in &d-i; is fairly versatile. It allows to create many "
+"different partitioning schemes, using various partition tables, file systems "
+"and advanced block devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1068
 #, no-c-format
-msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
+msgid ""
+"Exactly which options are available depends mainly on the architecture, but "
+"also on other factors. For example, on systems with limited internal memory "
+"some options may not be available. Defaults may vary as well. The type of "
+"partition table used by default can for example be different for large "
+"capacity hard disks than for smaller hard disks. Some options can only be "
+"changed when installing at medium or low debconf priority; at higher "
+"priorities sensible defaults will be used."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1079
 #, no-c-format
-msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
+msgid ""
+"The installer supports various forms of advanced partitioning and use of "
+"storage devices, which in many cases can be used in combination."
 msgstr ""
 
 #. Tag: emphasis
@@ -901,13 +1315,18 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1096
 #, no-c-format
-msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
+msgid ""
+"<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1098
 #, no-c-format
-msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
+msgid ""
+"Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support "
+"for Serial ATA RAID is currently only available if enabled when the "
+"installer is booted. Further information is available on <ulink url=\"&url-d-"
+"i-sataraid;\">our Wiki</ulink>."
 msgstr ""
 
 #. Tag: para
@@ -919,7 +1338,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1106
 #, no-c-format
-msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
+msgid ""
+"See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. "
+"Support for multipath is currently only available if enabled when the "
+"installer is booted."
 msgstr ""
 
 #. Tag: para
@@ -931,13 +1353,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1118
 #, no-c-format
-msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></phrase>"
+msgid ""
+"<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> "
+"<emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</"
+"emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></"
+"phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1123
 #, no-c-format
-msgid "The default file system selected in most cases is ext3; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
+msgid ""
+"The default file system selected in most cases is ext3; for <filename>/boot</"
+"filename> partitions ext2 will be selected by default when guided "
+"partitioning is used."
 msgstr ""
 
 #. Tag: para
@@ -973,37 +1402,59 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1141
 #, no-c-format
-msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:"
+msgid ""
+"As ZFS support in the installer is still in development, only a basic subset "
+"of ZFS features are supported. Some of them can be enabled manually after "
+"the initial install, but there are some caveats:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1146
 #, no-c-format
-msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the <quote>zfs create</quote> command."
+msgid ""
+"Each ZFS pool will host only one filesystem. After install is finished, more "
+"filesystems can be created on this pool by using the <quote>zfs create</"
+"quote> command."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1151
 #, no-c-format
-msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the <quote>zpool add</quote> command, or into a mirrored pool by using the <quote>zpool attach</quote> command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system."
+msgid ""
+"Each ZFS pool will be composed of exactly one partition. After install is "
+"finished, a single-device ZFS pool can be converted into a multi-device pool "
+"by using the <quote>zpool add</quote> command, or into a mirrored pool by "
+"using the <quote>zpool attach</quote> command. However, you shouldn't do "
+"this on the pool that hosts root filesystem, as it would prevent GRUB from "
+"booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1159
 #, no-c-format
-msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the <quote>compression</quote> property via the <quote>zfs set</quote> command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system."
+msgid ""
+"Compression is not currently supported. After the install is finished, "
+"compression can be enabled by setting the <quote>compression</quote> "
+"property via the <quote>zfs set</quote> command. However, if a compression "
+"algorithm other than the default (lzjb) is used on the pool that hosts your "
+"root filesystem, this may prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1168
 #, no-c-format
-msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
+msgid ""
+"<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1170
 #, no-c-format
-msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
+msgid ""
+"Support for the Reiser file system is no longer available by default. When "
+"the installer is running at medium or low debconf priority it can be enabled "
+"by selecting the <classname>partman-reiserfs</classname> component. Only "
+"version 3 of the file system is supported."
 msgstr ""
 
 #. Tag: emphasis
@@ -1015,7 +1466,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1178
 #, no-c-format
-msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
+msgid ""
+"Used on some systems to read flash memory. It is not possible to create new "
+"jffs2 partitions."
 msgstr ""
 
 #. Tag: emphasis
@@ -1027,7 +1480,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1184
 #, no-c-format
-msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
+msgid ""
+"Existing partitions will be recognized and it is possible to assign mount "
+"points for them. It is not possible to create new qnx4 partitions."
 msgstr ""
 
 #. Tag: para
@@ -1045,7 +1500,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1193
 #, no-c-format
-msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
+msgid ""
+"Existing NTFS partitions can be resized and it is possible to assign mount "
+"points for them. It is not possible to create new NTFS partitions."
 msgstr ""
 
 #. Tag: title
@@ -1057,49 +1514,89 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1204
 #, no-c-format
-msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
+msgid ""
+"If you choose guided partitioning, you may have three options: to create "
+"partitions directly on the hard disk (classic method), or to create them "
+"using Logical Volume Management (LVM), or to create them using encrypted "
+"LVM<footnote> <para> The installer will encrypt the LVM volume group using a "
+"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> "
+"support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1219
 #, no-c-format
-msgid "The option to use (encrypted) LVM may not be available on all architectures."
+msgid ""
+"The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1224
 #, no-c-format
-msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
+msgid ""
+"When using LVM or encrypted LVM, the installer will create most partitions "
+"inside one big partition; the advantage of this method is that partitions "
+"inside this big partition can be resized relatively easily later. In the "
+"case of encrypted LVM the big partition will not be readable without knowing "
+"a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1233
 #, no-c-format
-msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
+msgid ""
+"When using encrypted LVM, the installer will also automatically erase the "
+"disk by writing random data to it. This further improves security (as it "
+"makes it impossible to tell which parts of the disk are in use and also "
+"makes sure that any traces of previous installations are erased), but may "
+"take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1242
 #, no-c-format
-msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
+msgid ""
+"If you choose guided partitioning using LVM or encrypted LVM, some changes "
+"in the partition table will need to be written to the selected disk while "
+"LVM is being set up. These changes effectively erase all data that is "
+"currently on the selected hard disk and you will not be able to undo them "
+"later. However, the installer will ask you to confirm these changes before "
+"they are written to disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1252
 #, no-c-format
-msgid "If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
+msgid ""
+"If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic "
+"or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked "
+"to select the disk you want to use. Check that all your disks are listed "
+"and, if you have several disks, make sure you select the correct one. The "
+"order they are listed in may differ from what you are used to. The size of "
+"the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1261
 #, no-c-format
-msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. <phrase arch=\"linux-any\"> If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. </phrase>"
+msgid ""
+"Any data on the disk you select will eventually be lost, but you will always "
+"be asked to confirm any changes before they are written to the disk. <phrase "
+"arch=\"linux-any\"> If you have selected the classic method of partitioning, "
+"you will be able to undo any changes right until the end; when using "
+"(encrypted) LVM this is not possible. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1271
 #, no-c-format
-msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
+msgid ""
+"Next, you will be able to choose from the schemes listed in the table below. "
+"All schemes have their pros and cons, some of which are discussed in <xref "
+"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in "
+"mind that guided partitioning needs a certain minimal amount of free space "
+"to operate with. If you don't give it at least about 1GB of space (depends "
+"on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
@@ -1171,54 +1668,79 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1307
 #, no-c-format
-msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
+msgid ""
+"<filename>/</filename>, <filename>/home</filename>, <filename>/usr</"
+"filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1316
 #, no-c-format
-msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
+msgid ""
+"If you choose guided partitioning using (encrypted) LVM, the installer will "
+"also create a separate <filename>/boot</filename> partition. The other "
+"partitions, including the swap partition, will be created inside the LVM "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1322
 #, no-c-format
-msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
+msgid ""
+"If you choose guided partitioning for your IA-64 system, there will be an "
+"additional partition, formatted as a FAT16 bootable filesystem, for the EFI "
+"boot loader. There is also an additional menu item in the formatting menu to "
+"manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1330
 #, no-c-format
-msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
+msgid ""
+"After selecting a scheme, the next screen will show your new partition "
+"table, including information on whether and how partitions will be formatted "
+"and where they will be mounted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1336
 #, no-c-format
 msgid ""
-      "The list of partitions might look like this: <informalexample><screen>\n"
-      "  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
-      "        #1 primary   16.4 MB  B f ext2       /boot\n"
-      "        #2 primary  551.0 MB      swap       swap\n"
-      "        #3 primary    5.8 GB      ntfs\n"
-      "           pri/log    8.2 MB      FREE SPACE\n"
-      "\n"
-      "  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
-      "        #1 primary   15.9 MB      ext3\n"
-      "        #2 primary  996.0 MB      fat16\n"
-      "        #3 primary    3.9 GB      xfs        /home\n"
-      "        #5 logical    6.0 GB    f ext3       /\n"
-      "        #6 logical    1.0 GB    f ext3       /var\n"
-      "        #7 logical  498.8 MB      ext3\n"
-      "        #8 logical  551.5 MB      swap       swap\n"
-      "        #9 logical   65.8 GB      ext2\n"
-      "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning."
+"The list of partitions might look like this: <informalexample><screen>\n"
+"  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
+"        #1 primary   16.4 MB  B f ext2       /boot\n"
+"        #2 primary  551.0 MB      swap       swap\n"
+"        #3 primary    5.8 GB      ntfs\n"
+"           pri/log    8.2 MB      FREE SPACE\n"
+"\n"
+"  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
+"        #1 primary   15.9 MB      ext3\n"
+"        #2 primary  996.0 MB      fat16\n"
+"        #3 primary    3.9 GB      xfs        /home\n"
+"        #5 logical    6.0 GB    f ext3       /\n"
+"        #6 logical    1.0 GB    f ext3       /var\n"
+"        #7 logical  498.8 MB      ext3\n"
+"        #8 logical  551.5 MB      swap       swap\n"
+"        #9 logical   65.8 GB      ext2\n"
+"</screen></informalexample> This example shows two IDE harddrives divided "
+"into several partitions; the first disk has some free space. Each partition "
+"line consists of the partition number, its type, size, optional flags, file "
+"system, and mountpoint (if any). Note: this particular setup cannot be "
+"created using guided partitioning but it does show possible variation that "
+"can be achieved using manual partitioning."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1349
 #, no-c-format
-msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
+msgid ""
+"This concludes the guided partitioning. If you are satisfied with the "
+"generated partition table, you can choose <guimenuitem>Finish partitioning "
+"and write changes to disk</guimenuitem> from the menu to implement the new "
+"partition table (as described at the end of this section). If you are not "
+"happy, you can choose to <guimenuitem>Undo changes to partitions</"
+"guimenuitem> and run guided partitioning again, or modify the proposed "
+"changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
@@ -1230,49 +1752,101 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1364
 #, no-c-format
-msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
+msgid ""
+"A similar screen to the one shown just above will be displayed if you choose "
+"manual partitioning except that your existing partition table will be shown "
+"and without the mount points. How to manually set up your partition table "
+"and the usage of partitions by your new &debian; system will be covered in "
+"the remainder of this section."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1372
 #, no-c-format
-msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
+msgid ""
+"If you select a pristine disk which has neither partitions nor free space on "
+"it, you will be asked if a new partition table should be created (this is "
+"needed so you can create new partitions). After this, a new line entitled "
+"<quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1380
 #, no-c-format
-msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file system,</phrase> or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap,<phrase arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
+msgid ""
+"If you select some free space, you will have the opportunity to create a new "
+"partition. You will have to answer a quick series of questions about its "
+"size, type (primary or logical), and location (beginning or end of the free "
+"space). After this, you will be presented with a detailed overview of your "
+"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which "
+"determines if the partition will have a file system on it, or be used for "
+"swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file "
+"system,</phrase> or not be used at all. Other settings include mountpoint, "
+"mount options, and bootable flag; which settings are shown depends on how "
+"the partition is to be used. If you don't like the preselected defaults, "
+"feel free to change them to your liking. E.g. by selecting the option "
+"<guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem "
+"for this partition, including options to use the partition for swap,<phrase "
+"arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. "
+"Another nice feature is the ability to copy data from an existing partition "
+"onto this one. When you are satisfied with your new partition, select "
+"<guimenuitem>Done setting up the partition</guimenuitem> and you will return "
+"to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1402
 #, no-c-format
-msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
+msgid ""
+"If you decide you want to change something about your partition, simply "
+"select the partition, which will bring you to the partition configuration "
+"menu. This is the same screen as is used when creating a new partition, so "
+"you can change the same settings. One thing that may not be very obvious at "
+"a first glance is that you can resize the partition by selecting the item "
+"displaying the size of the partition. Filesystems known to work are at least "
+"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1413
 #, no-c-format
-msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
+msgid ""
+"Be sure to create at least two partitions: one for the <emphasis>root</"
+"emphasis> filesystem (which must be mounted as <filename>/</filename>) and "
+"one for <emphasis>swap</emphasis>. If you forget to mount the root "
+"filesystem, <command>partman</command> won't let you continue until you "
+"correct this issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1421
 #, no-c-format
-msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
+msgid ""
+"If you forget to select and format an EFI boot partition, <command>partman</"
+"command> will detect this and will not let you continue until you allocate "
+"one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1427
 #, no-c-format
-msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
+msgid ""
+"Capabilities of <command>partman</command> can be extended with installer "
+"modules, but are dependent on your system's architecture. So if you can't "
+"see all promised goodies, check if you have loaded all required modules (e."
+"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or "
+"<filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1435
 #, no-c-format
-msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
+msgid ""
+"After you are satisfied with partitioning, select <guimenuitem>Finish "
+"partitioning and write changes to disk</guimenuitem> from the partitioning "
+"menu. You will be presented with a summary of changes made to the disks and "
+"asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
@@ -1284,19 +1858,82 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1464
 #, no-c-format
-msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
+msgid ""
+"If you have more than one harddrive<footnote><para> To be honest, you can "
+"construct an MD device even from partitions residing on single physical "
+"drive, but that won't give any benefits. </para></footnote> in your "
+"computer, you can use <command>mdcfg</command> to set up your drives for "
+"increased performance and/or better reliability of your data. The result is "
+"called <firstterm>Multidisk Device</firstterm> (or after its most famous "
+"variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1477
 #, no-c-format
-msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
+msgid ""
+"MD is basically a bunch of partitions located on different disks and "
+"combined together to form a <emphasis>logical</emphasis> device. This device "
+"can then be used like an ordinary partition (i.e. in <command>partman</"
+"command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1485
 #, no-c-format
-msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
+msgid ""
+"What benefits this brings depends on the type of MD device you are creating. "
+"Currently supported are: <variablelist> <varlistentry> <term>RAID0</"
+"term><listitem><para> Is mainly aimed at performance. RAID0 splits all "
+"incoming data into <firstterm>stripes</firstterm> and distributes them "
+"equally over each disk in the array. This can increase the speed of read/"
+"write operations, but when one of the disks fails, you will lose "
+"<emphasis>everything</emphasis> (part of the information is still on the "
+"healthy disk(s), the other part <emphasis>was</emphasis> on the failed "
+"disk). </para><para> The typical use for RAID0 is a partition for video "
+"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</"
+"term><listitem><para> Is suitable for setups where reliability is the first "
+"concern. It consists of several (usually two) equally-sized partitions where "
+"every partition contains exactly the same data. This essentially means three "
+"things. First, if one of your disks fails, you still have the data mirrored "
+"on the remaining disks. Second, you can use only a fraction of the available "
+"capacity (more precisely, it is the size of the smallest partition in the "
+"RAID). Third, file-reads are load-balanced among the disks, which can "
+"improve performance on a server, such as a file server, that tends to be "
+"loaded with more disk reads than writes. </para><para> Optionally you can "
+"have a spare disk in the array which will take the place of the failed disk "
+"in the case of failure. </para></listitem> </varlistentry> <varlistentry> "
+"<term>RAID5</term><listitem><para> Is a good compromise between speed, "
+"reliability and data redundancy. RAID5 splits all incoming data into stripes "
+"and distributes them equally on all but one disk (similar to RAID0). Unlike "
+"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which "
+"gets written on the remaining disk. The parity disk is not static (that "
+"would be called RAID4), but is changing periodically, so the parity "
+"information is distributed equally on all disks. When one of the disks "
+"fails, the missing part of information can be computed from remaining data "
+"and its parity. RAID5 must consist of at least three active partitions. "
+"Optionally you can have a spare disk in the array which will take the place "
+"of the failed disk in the case of failure. </para><para> As you can see, "
+"RAID5 has a similar degree of reliability to RAID1 while achieving less "
+"redundancy. On the other hand, it might be a bit slower on write operations "
+"than RAID0 due to computation of parity information. </para></listitem> </"
+"varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar "
+"to RAID5 except that it uses two parity devices instead of one. </"
+"para><para> A RAID6 array can survive up to two disk failures. </para></"
+"listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> "
+"RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It "
+"creates <replaceable>n</replaceable> copies of incoming data and distributes "
+"them across the partitions so that none of the copies of the same data are "
+"on the same device. The default value of <replaceable>n</replaceable> is 2, "
+"but it can be set to something else in expert mode. The number of partitions "
+"used must be at least <replaceable>n</replaceable>. RAID10 has different "
+"layouts for distributing the copies. The default is near copies. Near copies "
+"have all of the copies at about the same offset on all of the disks. Far "
+"copies have the copies at different offsets on the disks. Offset copies copy "
+"the stripe, not the individual copies. </para><para> RAID10 can be used to "
+"achieve reliability and redundancy without the drawback of having to "
+"calculate parity. </para></listitem> </varlistentry> </variablelist> To sum "
+"it up:"
 msgstr ""
 
 #. Tag: entry
@@ -1392,7 +2029,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1629
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus one)"
 msgstr ""
 
 #. Tag: entry
@@ -1410,7 +2049,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1640
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus two)"
 msgstr ""
 
 #. Tag: entry
@@ -1422,79 +2063,140 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1651
 #, no-c-format
-msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
+msgid ""
+"Total of all partitions divided by the number of chunk copies (defaults to "
+"two)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1658
 #, no-c-format
-msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
+msgid ""
+"If you want to know more about Software RAID, have a look at <ulink url="
+"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1663
 #, no-c-format
-msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
+msgid ""
+"To create an MD device, you need to have the desired partitions it should "
+"consist of marked for use in a RAID. (This is done in <command>partman</"
+"command> in the <guimenu>Partition settings</guimenu> menu where you should "
+"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume "
+"for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1672
 #, no-c-format
-msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
+msgid ""
+"Make sure that the system can be booted with the partitioning scheme you are "
+"planning. In general it will be necessary to create a separate file system "
+"for <filename>/boot</filename> when using RAID for the root (<filename>/</"
+"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including "
+"lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using "
+"for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</"
+"filename> can be an option."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1684
 #, no-c-format
-msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
+msgid ""
+"Support for MD is a relatively new addition to the installer. You may "
+"experience problems for some RAID levels and in combination with some "
+"bootloaders if you try to use MD for the root (<filename>/</filename>) file "
+"system. For experienced users, it may be possible to work around some of "
+"these problems by executing some configuration or installation steps "
+"manually from a shell."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1693
 #, no-c-format
-msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
+msgid ""
+"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> "
+"from the main <command>partman</command> menu. (The menu will only appear "
+"after you mark at least one partition for use as <guimenuitem>physical "
+"volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</"
+"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will "
+"be presented with a list of supported types of MD devices, from which you "
+"should choose one (e.g. RAID1). What follows depends on the type of MD you "
+"selected."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1706
 #, no-c-format
-msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
+msgid ""
+"RAID0 is simple &mdash; you will be issued with the list of available RAID "
+"partitions and your only task is to select the partitions which will form "
+"the MD."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1713
 #, no-c-format
-msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
+msgid ""
+"RAID1 is a bit more tricky. First, you will be asked to enter the number of "
+"active devices and the number of spare devices which will form the MD. Next, "
+"you need to select from the list of available RAID partitions those that "
+"will be active and then those that will be spare. The count of selected "
+"partitions must be equal to the number provided earlier. Don't worry. If you "
+"make a mistake and select a different number of partitions, &d-i; won't let "
+"you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1725
 #, no-c-format
-msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+msgid ""
+"RAID5 has a setup procedure similar to RAID1 with the exception that you "
+"need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1731
 #, no-c-format
-msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
+msgid ""
+"RAID6 also has a setup procedure similar to RAID1 except that at least "
+"<emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1737
 #, no-c-format
-msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
+msgid ""
+"RAID10 again has a setup procedure similar to RAID1 except in expert mode. "
+"In expert mode, &d-i; will ask you for the layout. The layout has two parts. "
+"The first part is the layout type. It is either <literal>n</literal> (for "
+"near copies), <literal>f</literal> (for far copies), or <literal>o</literal> "
+"(for offset copies). The second part is the number of copies to make of the "
+"data. There must be at least that many active devices so that all of the "
+"copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1751
 #, no-c-format
-msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
+msgid ""
+"It is perfectly possible to have several types of MD at once. For example, "
+"if you have three 200 GB hard drives dedicated to MD, each containing two "
+"100 GB partitions, you can combine the first partitions on all three disks "
+"into the RAID0 (fast 300 GB video editing partition) and use the other three "
+"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition "
+"for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1760
 #, no-c-format
-msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
+msgid ""
+"After you set up MD devices to your liking, you can <guimenuitem>Finish</"
+"guimenuitem> <command>mdcfg</command> to return back to the "
+"<command>partman</command> to create filesystems on your new MD devices and "
+"assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
@@ -1506,37 +2208,70 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1776
 #, no-c-format
-msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
+msgid ""
+"If you are working with computers at the level of system administrator or "
+"<quote>advanced</quote> user, you have surely seen the situation where some "
+"disk partition (usually the most important one) was short on space, while "
+"some other partition was grossly underused and you had to manage this "
+"situation by moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1784
 #, no-c-format
-msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
+msgid ""
+"To avoid the described situation you can use Logical Volume Manager (LVM). "
+"Simply said, with LVM you can combine your partitions (<firstterm>physical "
+"volumes</firstterm> in LVM lingo) to form a virtual disk (so called "
+"<firstterm>volume group</firstterm>), which can then be divided into virtual "
+"partitions (<firstterm>logical volumes</firstterm>). The point is that "
+"logical volumes (and of course underlying volume groups) can span across "
+"several physical disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1794
 #, no-c-format
-msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
+msgid ""
+"Now when you realize you need more space for your old 160GB <filename>/home</"
+"filename> partition, you can simply add a new 300GB disk to the computer, "
+"join it with your existing volume group and then resize the logical volume "
+"which holds your <filename>/home</filename> filesystem and voila &mdash; "
+"your users have some room again on their renewed 460GB partition. This "
+"example is of course a bit oversimplified. If you haven't read it yet, you "
+"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1805
 #, no-c-format
-msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
+msgid ""
+"LVM setup in &d-i; is quite simple and completely supported inside "
+"<command>partman</command>. First, you have to mark the partition(s) to be "
+"used as physical volumes for LVM. This is done in the <guimenu>Partition "
+"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:"
+"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1814
 #, no-c-format
-msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
+msgid ""
+"When you return to the main <command>partman</command> screen, you will see "
+"a new option <guimenuitem>Configure the Logical Volume Manager</"
+"guimenuitem>. When you select that, you will first be asked to confirm "
+"pending changes to the partition table (if any) and after that the LVM "
+"configuration menu will be shown. Above the menu a summary of the LVM "
+"configuration is shown. The menu itself is context sensitive and only shows "
+"valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1825
 #, no-c-format
-msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
+msgid ""
+"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device "
+"structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1578,19 +2313,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1847
 #, no-c-format
-msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
+msgid ""
+"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</"
+"command> screen"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1853
 #, no-c-format
-msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
+msgid ""
+"Use the options in that menu to first create a volume group and then create "
+"your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1858
 #, no-c-format
-msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
+msgid ""
+"After you return to the main <command>partman</command> screen, any created "
+"logical volumes will be displayed in the same way as ordinary partitions "
+"(and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
@@ -1602,37 +2344,76 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1873
 #, no-c-format
-msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
+msgid ""
+"&d-i; allows you to set up encrypted partitions. Every file you write to "
+"such a partition is immediately saved to the device in encrypted form. "
+"Access to the encrypted data is granted only after entering the "
+"<firstterm>passphrase</firstterm> used when the encrypted partition was "
+"originally created. This feature is useful to protect sensitive data in case "
+"your laptop or hard drive gets stolen. The thief might get physical access "
+"to the hard drive, but without knowing the right passphrase, the data on the "
+"hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1885
 #, no-c-format
-msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+msgid ""
+"The two most important partitions to encrypt are: the home partition, where "
+"your private data resides, and the swap partition, where sensitive data "
+"might be stored temporarily during operation. Of course, nothing prevents "
+"you from encrypting any other partitions that might be of interest. For "
+"example <filename>/var</filename> where database servers, mail servers or "
+"print servers store their data, or <filename>/tmp</filename> which is used "
+"by various programs to store potentially interesting temporary files. Some "
+"people may even want to encrypt their whole system. The only exception is "
+"the <filename>/boot</filename> partition which must remain unencrypted, "
+"because currently there is no way to load the kernel from an encrypted "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1900
 #, no-c-format
-msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
+msgid ""
+"Please note that the performance of encrypted partitions will be less than "
+"that of unencrypted ones because the data needs to be decrypted or encrypted "
+"for every read or write. The performance impact depends on your CPU speed, "
+"chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1907
 #, no-c-format
-msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
+msgid ""
+"To use encryption, you have to create a new partition by selecting some free "
+"space in the main partitioning menu. Another option is to choose an existing "
+"partition (e.g. a regular partition, an LVM logical volume or a RAID "
+"volume). In the <guimenu>Partition settings</guimenu> menu, you need to "
+"select <guimenuitem>physical volume for encryption</guimenuitem> at the "
+"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will "
+"then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1918
 #, no-c-format
-msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+msgid ""
+"&d-i; supports several encryption methods. The default method is "
+"<firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to "
+"host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> "
+"(older, maintained separately from the Linux kernel tree). Unless you have "
+"compelling reasons to do otherwise, it is recommended to use the default."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1930
 #, no-c-format
-msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid ""
+"First, let's have a look at the options available when you select "
+"<userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As "
+"always: when in doubt, use the defaults, because they have been carefully "
+"chosen with security in mind."
 msgstr ""
 
 #. Tag: term
@@ -1644,7 +2425,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1942
 #, no-c-format
-msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
+msgid ""
+"This option lets you select the encryption algorithm (<firstterm>cipher</"
+"firstterm>) which will be used to encrypt the data on the partition. &d-i; "
+"currently supports the following block ciphers: <firstterm>aes</firstterm>, "
+"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and "
+"<firstterm>twofish</firstterm>. It is beyond the scope of this document to "
+"discuss the qualities of these different algorithms, however, it might help "
+"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by "
+"the American National Institute of Standards and Technology as the standard "
+"encryption algorithm for protecting sensitive information in the 21st "
+"century."
 msgstr ""
 
 #. Tag: term
@@ -1656,7 +2447,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1962
 #, no-c-format
-msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
+msgid ""
+"Here you can specify the length of the encryption key. With a larger key "
+"size, the strength of the encryption is generally improved. On the other "
+"hand, increasing the length of the key usually has a negative impact on "
+"performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
@@ -1668,13 +2463,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1976
 #, no-c-format
-msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
+msgid ""
+"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</"
+"firstterm> algorithm is used in cryptography to ensure that applying the "
+"cipher on the same <firstterm>clear text</firstterm> data with the same key "
+"always produces a unique <firstterm>cipher text</firstterm>. The idea is to "
+"prevent the attacker from deducing information from repeated patterns in the "
+"encrypted data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1986
 #, no-c-format
-msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
+msgid ""
+"From the provided alternatives, the default <userinput>cbc-essiv:sha256</"
+"userinput> is currently the least vulnerable to known attacks. Use the other "
+"alternatives only when you need to ensure compatibility with some previously "
+"installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
@@ -1698,7 +2503,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2007
 #, no-c-format
-msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
+msgid ""
+"The encryption key will be computed<footnote> <para> Using a passphrase as "
+"the key currently means that the partition will be set up using <ulink url="
+"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase "
+"which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
@@ -1710,13 +2519,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2023
 #, no-c-format
-msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
+msgid ""
+"A new encryption key will be generated from random data each time you try to "
+"bring up the encrypted partition. In other words: on every shutdown the "
+"content of the partition will be lost as the key is deleted from memory. (Of "
+"course, you could try to guess the key with a brute force attack, but unless "
+"there is an unknown weakness in the cipher algorithm, it is not achievable "
+"in our lifetime.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2032
 #, no-c-format
-msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
+msgid ""
+"Random keys are useful for swap partitions because you do not need to bother "
+"yourself with remembering the passphrase or wiping sensitive information "
+"from the swap partition before shutting down your computer. However, it also "
+"means that you will <emphasis>not</emphasis> be able to use the "
+"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels "
+"as it will be impossible (during a subsequent boot) to recover the suspended "
+"data written to the swap partition."
 msgstr ""
 
 #. Tag: term
@@ -1728,13 +2550,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2053
 #, no-c-format
-msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
+msgid ""
+"Determines whether the content of this partition should be overwritten with "
+"random data before setting up the encryption. This is recommended because it "
+"might otherwise be possible for an attacker to discern which parts of the "
+"partition are in use and which are not. In addition, this will make it "
+"harder to recover any leftover data from previous "
+"installations<footnote><para> It is believed that the guys from three-letter "
+"agencies can restore the data even after several rewrites of the "
+"magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2073
 #, no-c-format
-msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
+msgid ""
+"If you select <menuchoice> <guimenu>Encryption method:</guimenu> "
+"<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu "
+"changes to provide the following options:"
 msgstr ""
 
 #. Tag: term
@@ -1746,7 +2579,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2084
 #, no-c-format
-msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
+msgid ""
+"For loop-AES, unlike dm-crypt, the options for cipher and key size are "
+"combined, so you can select both at the same time. Please see the above "
+"sections on ciphers and key sizes for further information."
 msgstr ""
 
 #. Tag: term
@@ -1770,7 +2606,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2103
 #, no-c-format
-msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
+msgid ""
+"The encryption key will be generated from random data during the "
+"installation. Moreover this key will be encrypted with <application>GnuPG</"
+"application>, so to use it, you will need to enter the proper passphrase "
+"(you will be asked to provide one later in the process)."
 msgstr ""
 
 #. Tag: para
@@ -1788,50 +2628,93 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2139
 #, no-c-format
-msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
+msgid ""
+"After you have selected the desired parameters for your encrypted "
+"partitions, return back to the main partitioning menu. There should now be a "
+"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After "
+"you select it, you will be asked to confirm the deletion of data on "
+"partitions marked to be erased and possibly other actions such as writing a "
+"new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2149
 #, no-c-format
-msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
+msgid ""
+"Next you will be asked to enter a passphrase for partitions configured to "
+"use one. Good passphrases should be longer than 8 characters, should be a "
+"mixture of letters, numbers and other characters and should not contain "
+"common dictionary words or information easily associable with you (such as "
+"birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2158
 #, no-c-format
-msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
+msgid ""
+"Before you input any passphrases, you should have made sure that your "
+"keyboard is configured correctly and generates the expected characters. If "
+"you are unsure, you can switch to the second virtual console and type some "
+"text at the prompt. This ensures that you won't be surprised later, e.g. by "
+"trying to input a passphrase using a qwerty keyboard layout when you used an "
+"azerty layout during the installation. This situation can have several "
+"causes. Maybe you switched to another keyboard layout during the "
+"installation, or the selected keyboard layout might not have been set up yet "
+"when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2171
 #, no-c-format
-msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
+msgid ""
+"If you selected to use methods other than a passphrase to create encryption "
+"keys, they will be generated now. Because the kernel may not have gathered a "
+"sufficient amount of entropy at this early stage of the installation, the "
+"process may take a long time. You can help speed up the process by "
+"generating entropy: e.g. by pressing random keys, or by switching to the "
+"shell on the second virtual console and generating some network and disk "
+"traffic (downloading some files, feeding big files into <filename>/dev/null</"
+"filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2187
 #, no-c-format
 msgid ""
-      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
-      "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
-      "     #1 115.1 GB  F ext3\n"
-      "\n"
-      "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-      "     #1 515.2 MB  F ext3\n"
-      "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you."
+"After returning to the main partitioning menu, you will see all encrypted "
+"volumes as additional partitions which can be configured in the same way as "
+"ordinary partitions. The following example shows two different volumes. The "
+"first one is encrypted via dm-crypt, the second one via loop-AES. "
+"<informalexample><screen>\n"
+"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux "
+"device-mapper\n"
+"     #1 115.1 GB  F ext3\n"
+"\n"
+"Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
+"     #1 515.2 MB  F ext3\n"
+"</screen></informalexample> Now is the time to assign mount points to the "
+"volumes and optionally change the file system types if the defaults do not "
+"suit you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2200
 #, no-c-format
-msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+msgid ""
+"Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</"
+"replaceable> and <replaceable>loop0</replaceable> in this case) and the "
+"mount points you assigned to each encrypted volume. You will need this "
+"information later when booting the new system. The differences between the "
+"ordinary boot process and the boot process with encryption involved will be "
+"covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2210
 #, no-c-format
-msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
+msgid ""
+"Once you are satisfied with the partitioning scheme, continue with the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -1843,37 +2726,63 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2222
 #, no-c-format
-msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
+msgid ""
+"Although this stage is the least problematic, it consumes a significant "
+"fraction of the install because it downloads, verifies and unpacks the whole "
+"base system. If you have a slow computer or network connection, this could "
+"take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2235
 #, no-c-format
-msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"During installation of the base system, package unpacking and setup messages "
+"are redirected to <userinput>tty4</userinput>. You can access this terminal "
+"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></"
+"keycombo>; get back to the main installer process with "
+"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2244
 #, no-c-format
-msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
+msgid ""
+"The unpack/setup messages generated during this phase are also saved in "
+"<filename>/var/log/syslog</filename>. You can check them there if the "
+"installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2250
 #, no-c-format
-msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
+msgid ""
+"As part of the installation, a &arch-kernel; kernel will be installed. At "
+"the default priority, the installer will choose one for you that best "
+"matches your hardware. In lower priority modes, you will be able to choose "
+"from a list of available kernels."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2257
 #, no-c-format
-msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
+msgid ""
+"When packages are installed using the package management system, it will by "
+"default also install packages that are recommended by those packages. "
+"Recommended packages are not strictly required for the core functionality of "
+"the selected software, but they do enhance that software and should, in the "
+"view of the package maintainers, normally be installed together with that "
+"software."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2267
 #, no-c-format
-msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
+msgid ""
+"For technical reasons packages installed during the installation of the base "
+"system are installed without their <quote>Recommends</quote>. The rule "
+"described above only takes effect after this point in the installation "
+"process."
 msgstr ""
 
 #. Tag: title
@@ -1885,7 +2794,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2280
 #, no-c-format
-msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
+msgid ""
+"At this point you have a usable but limited system. Most users will want to "
+"install additional software on the system to tune it to their needs, and the "
+"installer allows you do so. This step can take even longer than installing "
+"the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
@@ -1897,25 +2810,55 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2297
 #, no-c-format
-msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
+msgid ""
+"One of the tools used to install packages on a &debian-gnu; system is a "
+"program called <command>apt-get</command>, from the <classname>apt</"
+"classname> package<footnote> <para> Note that the program which actually "
+"installs the packages is called <command>dpkg</command>. However, this "
+"program is more of a low-level tool. <command>apt-get</command> is a higher-"
+"level tool, which will invoke <command>dpkg</command> as appropriate. It "
+"knows how to retrieve packages from your CD, the network, or wherever. It is "
+"also able to automatically install other packages which are required to make "
+"the package you're trying to install work correctly. </para> </footnote>. "
+"Other front-ends for package management, like <command>aptitude</command> "
+"and <command>synaptic</command>, are also in use. These front-ends are "
+"recommended for new users, since they integrate some additional features "
+"(package searching and status checks) in a nice user interface. In fact, "
+"<command>aptitude</command> is now the recommended utility for package "
+"management."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2321
 #, no-c-format
-msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
+msgid ""
+"<command>apt</command> must be configured so that it knows from where to "
+"retrieve packages. The results of this configuration are written to the file "
+"<filename>/etc/apt/sources.list</filename>. You can examine and edit this "
+"file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2328
 #, no-c-format
-msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
+msgid ""
+"If you are installing at default priority, the installer will largely take "
+"care of the configuration automatically, based on the installation method "
+"you are using and possibly using choices made earlier in the installation. "
+"In most cases the installer will automatically add a security mirror and, if "
+"you are installing the stable distribution, a mirror for the "
+"<quote>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2337
 #, no-c-format
-msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
+msgid ""
+"If you are installing at a lower priority (e.g. in expert mode), you will be "
+"able to make more decisions yourself. You can choose whether or not to use "
+"the security and/or volatile update services, and you can choose to add "
+"packages from the <quote>contrib</quote> and <quote>non-free</quote> "
+"sections of the archive."
 msgstr ""
 
 #. Tag: title
@@ -1927,37 +2870,64 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2350
 #, no-c-format
-msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
+msgid ""
+"If you are installing from a CD or a DVD that is part of a larger set, the "
+"installer will ask if you want to scan additional CDs or DVDs. If you have "
+"additional CDs or DVDs available, you probably want to do this so the "
+"installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2357
 #, no-c-format
-msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
+msgid ""
+"If you do not have any additional CDs or DVDs, that is no problem: using "
+"them is not required. If you also do not use a network mirror (as explained "
+"in the next section), it can mean that not all packages belonging to the "
+"tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2365
 #, no-c-format
-msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
+msgid ""
+"Packages are included on CDs (and DVDs) in the order of their popularity. "
+"This means that for most uses only the first CDs in a set are needed and "
+"that only very few people actually use any of the packages included on the "
+"last CDs in a set."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2372
 #, no-c-format
-msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
+msgid ""
+"It also means that buying or downloading and burning a full CD set is just a "
+"waste of money as you'll never use most of them. In most cases you are "
+"better off getting only the first 3 to 8 CDs and installing any additional "
+"packages you may need from the Internet by using a mirror. The same goes for "
+"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2381
 #, no-c-format
-msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
+msgid ""
+"A good rule of thumb is that for a regular desktop installation (using the "
+"GNOME desktop environment) only the first three CDs are needed. For the "
+"alternative desktop environments (KDE or Xfce), additional CDs are needed. "
+"The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2389
 #, no-c-format
-msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
+msgid ""
+"If you do scan multiple CDs or DVDs, the installer will prompt you to "
+"exchange them when it needs packages from another CD/DVD than the one "
+"currently in the drive. Note that only CDs or DVDs that belong to the same "
+"set should be scanned. The order in which they are scanned does not really "
+"matter, but scanning them in ascending order will reduce the chance of "
+"mistakes."
 msgstr ""
 
 #. Tag: title
@@ -1969,37 +2939,67 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2404
 #, no-c-format
-msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
+msgid ""
+"One question that will be asked during most installs is whether or not to "
+"use a network mirror as a source for packages. In most cases the default "
+"answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2410
 #, no-c-format
-msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
+msgid ""
+"If you are <emphasis>not</emphasis> installing from a full CD or DVD or "
+"using a full CD/DVD image, you really should use a network mirror as "
+"otherwise you will end up with only a very minimal system. However, if you "
+"have a limited Internet connection it is best <emphasis>not</emphasis> to "
+"select the <literal>desktop</literal> task in the next step of the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2419
 #, no-c-format
-msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
+msgid ""
+"If you are installing from a single full CD or using a full CD image, using "
+"a network mirror is not required, but is still strongly recommended because "
+"a single CD contains only a fairly limited number of packages. If you have a "
+"limited Internet connection it may still be best to <emphasis>not</emphasis> "
+"select a network mirror here, but to finish the installation using only "
+"what's available on the CD and selectively install additional packages after "
+"the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2430
 #, no-c-format
-msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
+msgid ""
+"If you are installing from a DVD or using a DVD image, any packages needed "
+"during the installation should be present on the first DVD. The same is true "
+"if you have scanned multiple CDs as explained in the previous section. Use "
+"of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2437
 #, no-c-format
-msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
+msgid ""
+"One advantage of adding a network mirror is that updates that have occurred "
+"since the CD/DVD set was created and have been included in a point release, "
+"will become available for installation, thus extending the life of your CD/"
+"DVD set without compromising the security or stability of the installed "
+"system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2444
 #, no-c-format
-msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
+msgid ""
+"In summary: selecting a network mirror is generally a good idea, except if "
+"you do not have a good Internet connection. If the current version of a "
+"package is available from CD/DVD, the installer will always use that. The "
+"amount of data that will be downloaded if you do select a mirror thus "
+"depends on"
 msgstr ""
 
 #. Tag: para
@@ -2017,19 +3017,27 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2463
 #, no-c-format
-msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
+msgid ""
+"which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2468
 #, no-c-format
-msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
+msgid ""
+"whether any updated versions of packages included on the CDs or DVDs are "
+"available from a mirror (either a regular package mirror, or a mirror for "
+"security or volatile updates)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2477
 #, no-c-format
-msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
+msgid ""
+"Note that the last point means that, even if you choose not to use a network "
+"mirror, some packages may still be downloaded from the Internet if there is "
+"a security or volatile update available for them and those services have "
+"been configured."
 msgstr ""
 
 #. Tag: title
@@ -2041,19 +3049,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2489
 #, no-c-format
-msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine."
+msgid ""
+"If you have selected to use a network mirror during the installation "
+"(optional for CD/DVD installs, required for netboot images), you will be "
+"presented with a list of geographically nearby (and therefore hopefully "
+"fast) network mirrors, based upon your country selection earlier in the "
+"installation process. Choosing the offered default is usually fine."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2497
 #, no-c-format
-msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one."
+msgid ""
+"If your computer is on an IPv6-only network (which is probably not the case "
+"for the vast majority of users), using the default mirror for your country "
+"might not work. All the mirrors in the list are reachable via IPv4, but only "
+"some of them can be used via IPv6. As connectivity of individual mirrors can "
+"change over time, this information is not available in the installer. If "
+"there is no IPv6 connectivity for the default mirror for your country, you "
+"can either try some of the other mirrors offered to you or choose the "
+"<quote>enter information manually</quote> option. You can then specify "
+"<quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for "
+"a mirror available via IPv6, although it will probably not be the fastest "
+"possible one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2511
 #, no-c-format
-msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
+msgid ""
+"Another option when choosing to specify the mirror manually is to use "
+"<quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</"
+"quote> is not a physical mirror but a mirror redirection service, i.e. it "
+"automatically refers your system to a real mirror near you in terms of "
+"network topology. It takes into account by which protocol you connect to it, "
+"i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
 msgstr ""
 
 #. Tag: title
@@ -2065,85 +3095,165 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2532
 #, no-c-format
-msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
+msgid ""
+"During the installation process, you are given the opportunity to select "
+"additional software to install. Rather than picking individual software "
+"packages from the &num-of-distrib-pkgs; available packages, this stage of "
+"the installation process focuses on selecting and installing predefined "
+"collections of software to quickly set up your computer to perform various "
+"tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2541
 #, no-c-format
-msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
+msgid ""
+"So, you have the ability to choose <emphasis>tasks</emphasis> first, and "
+"then add on more individual packages later. These tasks loosely represent a "
+"number of different jobs or things you want to do with your computer, such "
+"as <quote>Desktop environment</quote>, <quote>Web server</quote>, or "
+"<quote>Print server</quote><footnote> <para> You should know that to present "
+"this list, the installer is merely invoking the <command>tasksel</command> "
+"program. It can be run at any time after installation to install more "
+"packages (or remove them), or you can use a more fine-grained tool such as "
+"<command>aptitude</command>. If you are looking for a specific single "
+"package, after installation is complete, simply run <userinput>aptitude "
+"install <replaceable>package</replaceable></userinput>, where "
+"<replaceable>package</replaceable> is the name of the package you are "
+"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> "
+"lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2568
 #, no-c-format
-msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
+msgid ""
+"Some tasks may be pre-selected based on the characteristics of the computer "
+"you are installing. If you disagree with these selections you can deselect "
+"them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2575
 #, no-c-format
-msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+msgid ""
+"In the standard user interface of the installer, you can use the space bar "
+"to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2581
 #, no-c-format
-msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
+msgid ""
+"Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop "
+"environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2586
 #, no-c-format
-msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using <literal>desktop=xfce</literal> or <literal>desktop=lxde</literal>."
+msgid ""
+"It is not possible to interactively select a different desktop during the "
+"installation. However, it <emphasis>is</emphasis> possible to get &d-i; to "
+"install a KDE desktop environment instead of GNOME by using preseeding (see "
+"<xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter "
+"<literal>desktop=kde</literal> at the boot prompt when starting the "
+"installer. Alternatively the more lightweight Xfce and LXDE desktop "
+"environments can be selected by using <literal>desktop=xfce</literal> or "
+"<literal>desktop=lxde</literal>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2597
 #, no-c-format
-msgid "Some CD images (netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>."
+msgid ""
+"Some CD images (netinst and DVD) also allow selection of the desired desktop "
+"environment from the graphical boot menu. Select the <quote>Advanced "
+"options</quote> option in the main menu and look for <quote>Alternative "
+"desktop environments</quote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2604
 #, no-c-format
-msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method."
+msgid ""
+"Note that this will only work if the packages needed for the desired desktop "
+"environment are actually available. If you are installing using a single "
+"full CD image, they will need to be downloaded from a mirror as most needed "
+"packages are only included on later CDs; installing KDE, Xfce or LXDE this "
+"way should work fine if you are using a DVD image or any other installation "
+"method."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2614
 #, no-c-format
-msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
+msgid ""
+"The various server tasks will install software roughly as follows. DNS "
+"server: <classname>bind9</classname>; File server: <classname>samba</"
+"classname>, <classname>nfs</classname>; Mail server: <classname>exim4</"
+"classname>, <classname>spamassassin</classname>, <classname>uw-imap</"
+"classname>; Print server: <classname>cups</classname>; SQL database: "
+"<classname>postgresql</classname>; Web server: <classname>apache2</"
+"classname>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2625
 #, no-c-format
-msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system."
+msgid ""
+"The <quote>Standard system</quote> task will install any package that has a "
+"priority <quote>standard</quote>. This includes a lot of common utilities "
+"that are normally available on any Linux or Unix system. You should leave "
+"this task selected unless you know what you are doing and want a really "
+"minimal system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2633
 #, no-c-format
-msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)."
+msgid ""
+"If during language selection a default locale other than the <quote>C</"
+"quote> locale was selected, <command>tasksel</command> will check if any "
+"localization tasks are defined for that locale and will automatically try to "
+"install relevant localization packages. This includes for example packages "
+"containing word lists or special fonts for your language. If a desktop "
+"environment was selected, it will also install appropriate localization "
+"packages for that (if available)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2643
 #, no-c-format
-msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
+msgid ""
+"Once you've selected your tasks, select &BTN-CONT;. At this point, "
+"<command>aptitude</command> will install the packages that are part of the "
+"selected tasks. If a particular program needs more information from the "
+"user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2650
 #, no-c-format
-msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
+msgid ""
+"You should be aware that especially the Desktop task is very large. "
+"Especially when installing from a normal CD-ROM in combination with a mirror "
+"for packages not on the CD-ROM, the installer may want to retrieve a lot of "
+"packages over the network. If you have a relatively slow Internet "
+"connection, this can take a long time. There is no option to cancel the "
+"installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2659
 #, no-c-format
-msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
+msgid ""
+"Even when packages are included on the CD-ROM, the installer may still "
+"retrieve them from the mirror if the version available on the mirror is more "
+"recent than the one included on the CD-ROM. If you are installing the stable "
+"distribution, this can happen after a point release (an update of the "
+"original stable release); if you are installing the testing distribution "
+"this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: title
@@ -2155,7 +3265,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2676
 #, no-c-format
-msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
+msgid ""
+"If you are installing a diskless workstation, obviously, booting off the "
+"local disk isn't a meaningful option, and this step will be skipped. <phrase "
+"arch=\"sparc\">You may wish to set OpenBoot to boot from the network by "
+"default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -2167,13 +3281,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2693
 #, no-c-format
-msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;."
+msgid ""
+"Before a boot loader is installed, the installer will attempt to probe for "
+"other operating systems which are installed on the machine. If it finds a "
+"supported operating system, you will be informed of this during the boot "
+"loader installation step, and the computer will be configured to boot this "
+"other operating system in addition to &debian;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2701
 #, no-c-format
-msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
+msgid ""
+"Note that multiple operating systems booting on a single machine is still "
+"something of a black art. The automatic support for detecting and setting up "
+"boot loaders to boot other operating systems varies by architecture and even "
+"by subarchitecture. If it does not work you should consult your boot "
+"manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
@@ -2185,7 +3309,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2720
 #, no-c-format
-msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
+msgid ""
+"The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is "
+"similar in configuration and usage to <command>LILO</command>, with a few "
+"exceptions. First of all, <command>PALO</command> allows you to boot any "
+"kernel image on your boot partition. This is because <command>PALO</command> "
+"can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
@@ -2203,19 +3332,28 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2743
 #, no-c-format
-msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
+msgid ""
+"The main &architecture; boot loader is called <quote>grub</quote>. Grub is a "
+"flexible and robust boot loader and a good default choice for new users and "
+"old hands alike."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2749
 #, no-c-format
-msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
+msgid ""
+"By default, grub will be installed into the Master Boot Record (MBR), where "
+"it will take over complete control of the boot process. If you prefer, you "
+"can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2755
 #, no-c-format
-msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
+msgid ""
+"If you do not want to install grub, use the &BTN-GOBACK; button to get to "
+"the main menu, and from there select whatever bootloader you would like to "
+"use."
 msgstr ""
 
 #. Tag: title
@@ -2227,19 +3365,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2770
 #, no-c-format
-msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
+msgid ""
+"The second &architecture; boot loader is called <quote>LILO</quote>. It is "
+"an old complex program which offers lots of functionality, including DOS, "
+"Windows, and OS/2 boot management. Please carefully read the instructions in "
+"the directory <filename>/usr/share/doc/lilo/</filename> if you have special "
+"needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2780
 #, no-c-format
-msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
+msgid ""
+"Currently the LILO installation will only create menu entries for other "
+"operating systems if these can be <firstterm>chainloaded</firstterm>. This "
+"means you may have to manually add a menu entry for operating systems like "
+"GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2788
 #, no-c-format
-msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
+msgid ""
+"&d-i; offers you three choices on where to install the <command>LILO</"
+"command> boot loader:"
 msgstr ""
 
 #. Tag: term
@@ -2251,7 +3400,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2795
 #, no-c-format
-msgid "This way the <command>LILO</command> will take complete control of the boot process."
+msgid ""
+"This way the <command>LILO</command> will take complete control of the boot "
+"process."
 msgstr ""
 
 #. Tag: term
@@ -2263,7 +3414,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2802
 #, no-c-format
-msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader."
+msgid ""
+"Choose this if you want to use another boot manager. <command>LILO</command> "
+"will install itself at the beginning of the new &debian; partition and it "
+"will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
@@ -2275,13 +3429,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2811
 #, no-c-format
-msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+msgid ""
+"Useful for advanced users who want to install <command>LILO</command> "
+"somewhere else. In this case you will be asked for desired location. You can "
+"use traditional device names such as <filename>/dev/hda</filename> or "
+"<filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2821
 #, no-c-format
-msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into &debian;!"
+msgid ""
+"If you can no longer boot into Windows 9x (or DOS) after this step, you'll "
+"need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /"
+"mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; "
+"however, this means that you'll need to use some other way to get back into "
+"&debian;!"
 msgstr ""
 
 #. Tag: title
@@ -2293,13 +3456,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2839
 #, no-c-format
-msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
+msgid ""
+"The &architecture; boot loader is called <quote>elilo</quote>. It is modeled "
+"on the <quote>lilo</quote> boot loader for the x86 architecture and uses a "
+"similar configuration file. However, instead of writing an MBR or partition "
+"boot record to the disk, it copies the necessary files to a separate FAT "
+"formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</"
+"guimenuitem> menu in the firmware to point to the files in the EFI "
+"partition. The <command>elilo</command> boot loader is really in two parts. "
+"The <filename>/usr/sbin/elilo</filename> command manages the partition and "
+"copies files into it. The <filename>elilo.efi</filename> program is copied "
+"into the EFI partition and then run by the <quote>EFI Boot Manager</quote> "
+"to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2855
 #, no-c-format
-msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
+msgid ""
+"The <quote>elilo</quote> configuration and installation is done as the last "
+"step of installing the packages of the base installation. &d-i; will present "
+"you with a list of potential disk partitions that it has found suitable for "
+"an EFI partition. Select the partition you set up earlier in the "
+"installation, typically a partition on the same disk that contains your "
+"<emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2311,7 +3491,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2869
 #, no-c-format
-msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
+msgid ""
+"The criterion for selecting a partition is that it must be a FAT format "
+"filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show "
+"multiple choices depending on what it finds from scanning all of the disks "
+"of the system including EFI partitions of other system disks and EFI "
+"diagnostic partitions. Remember, <command>elilo</command> may format the "
+"partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
@@ -2323,7 +3509,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2886
 #, no-c-format
-msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
+msgid ""
+"The EFI partition is a FAT filesystem format partition on one of the hard "
+"disks of the system, usually the same disk that contains the <emphasis>root</"
+"emphasis> filesystem. It is normally not mounted on a running system as it "
+"is only needed by the <quote>EFI Boot Manager</quote> to load the system and "
+"the installer part of the <command>elilo</command> writes to the filesystem "
+"directly. The <command>/usr/sbin/elilo</command> utility writes the "
+"following files into the <filename>efi/debian</filename> directory of the "
+"EFI partition during the installation. Note that the <quote>EFI Boot "
+"Manager</quote> would find these files using the path "
+"<filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may "
+"be other files in this filesystem as well over time as the system is updated "
+"or re-configured."
 msgstr ""
 
 #. Tag: filename
@@ -2335,7 +3533,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2909
 #, no-c-format
-msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
+msgid ""
+"This is the configuration file read by the boot loader when it starts. It is "
+"a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-"
+"written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
@@ -2347,7 +3548,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2919
 #, no-c-format
-msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
+msgid ""
+"This is the boot loader program that the <quote>EFI Boot Manager</quote> "
+"runs to boot the system. It is the program behind the <guimenuitem>&debian; "
+"GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> "
+"command menu."
 msgstr ""
 
 #. Tag: filename
@@ -2359,7 +3564,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2930
 #, no-c-format
-msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
+msgid ""
+"This is the initial root filesystem used to boot the kernel. It is a copy of "
+"the file referenced in the <filename>/etc/elilo.conf</filename>. In a "
+"standard &debian; installation it would be the file in <filename>/boot</"
+"filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
@@ -2371,7 +3580,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2943
 #, no-c-format
-msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
+msgid ""
+"This is a small text file warning you that the contents of the directory are "
+"managed by the <command>elilo</command> and that any local changes would be "
+"lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
@@ -2383,7 +3595,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2954
 #, no-c-format
-msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
+msgid ""
+"This is the compressed kernel itself. It is a copy of the file referenced in "
+"the <filename>/etc/elilo.conf</filename>. In a standard &debian; "
+"installation it would be the file in <filename>/boot</filename> pointed to "
+"by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
@@ -2396,13 +3612,25 @@ msgstr ""
 #: using-d-i.xml:2975
 #, no-c-format
 msgid ""
-      "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
-      "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
-      "<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n"
-      "<userinput> setenv OSLoader arcboot</userinput>\n"
-      "<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n"
-      "<userinput> setenv AutoLoad yes</userinput>\n"
-      "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
+"The boot loader on SGI machines is <command>arcboot</command>. It has to be "
+"installed on the same hard disk as the kernel (this is done automatically by "
+"the installer). Arcboot supports different configurations which are set up "
+"in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique "
+"name, the default setup as created by the installer is <quote>linux</quote>. "
+"After arcboot has been installed, the system can be booted from hard disk by "
+"setting some firmware environment variables entering "
+"<informalexample><screen>\n"
+"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
+"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</"
+"replaceable>)</userinput>\n"
+"<userinput> setenv OSLoader arcboot</userinput>\n"
+"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></"
+"userinput>\n"
+"<userinput> setenv AutoLoad yes</userinput>\n"
+"</screen></informalexample> on the firmware prompt, and then typing "
+"<command>boot</command>."
 msgstr ""
 
 #. Tag: replaceable
@@ -2414,7 +3642,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2995
 #, no-c-format
-msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
+msgid ""
+"is the SCSI bus to be booted from, this is <userinput>0</userinput> for the "
+"onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
@@ -2426,7 +3656,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3004
 #, no-c-format
-msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
+msgid ""
+"is the SCSI ID of the hard disk on which <command>arcboot</command> is "
+"installed"
 msgstr ""
 
 #. Tag: replaceable
@@ -2438,7 +3670,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3013
 #, no-c-format
-msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
+msgid ""
+"is the number of the partition on which <filename>/etc/arcboot.conf</"
+"filename> resides"
 msgstr ""
 
 #. Tag: replaceable
@@ -2450,7 +3684,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3022
 #, no-c-format
-msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
+msgid ""
+"is the name of the configuration entry in <filename>/etc/arcboot.conf</"
+"filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
@@ -2462,7 +3698,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3044
 #, no-c-format
-msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;."
+msgid ""
+"Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their "
+"boot loader. The installer will set up <command>yaboot</command> "
+"automatically, so all you need is a small 820k partition named "
+"<quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> "
+"created back in the partitioning component. If this step completes "
+"successfully then your disk should now be bootable and OpenFirmware will be "
+"set to boot &debian-gnu;."
 msgstr ""
 
 #. Tag: title
@@ -2474,7 +3717,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3063
 #, no-c-format
-msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
+msgid ""
+"The boot loader for OldWorld Power Macintosh machines is <command>quik</"
+"command>. You can also use it on CHRP. The installer will attempt to set up "
+"<command>quik</command> automatically. The setup has been known to work on "
+"7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
@@ -2486,7 +3733,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3080
 #, no-c-format
-msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
+msgid ""
+"The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. Please take a look at <quote>LINUX for &arch-title; "
+"Device Drivers and Installation Commands</quote> from IBM's developerWorks "
+"web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
@@ -2498,7 +3750,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3099
 #, no-c-format
-msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
+msgid ""
+"The standard &architecture; boot loader is called <quote>silo</quote>. It is "
+"documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. First of all, <command>SILO</command> allows you to "
+"boot any kernel image on your drive, even if it is not listed in <filename>/"
+"etc/silo.conf</filename>. This is because <command>SILO</command> can "
+"actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is "
+"read at boot time, so there is no need to rerun <command>silo</command> "
+"after installing a new kernel like you would with <command>LILO</command>. "
+"<command>SILO</command> can also read UFS partitions, which means it can "
+"boot SunOS/Solaris partitions as well. This is useful if you want to install "
+"GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
@@ -2510,13 +3774,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3126
 #, no-c-format
-msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)."
+msgid ""
+"This option can be used to complete the installation even when no boot "
+"loader is to be installed, either because the arch/subarch doesn't provide "
+"one, or because none is desired (e.g. you will use existing boot loader)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3133
 #, no-c-format
-msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
+msgid ""
+"If you plan to manually configure your bootloader, you should check the name "
+"of the installed kernel in <filename>/target/boot</filename>. You should "
+"also check that directory for the presence of an <firstterm>initrd</"
+"firstterm>; if one is present, you will probably have to instruct your "
+"bootloader to use it. Other information you will need are the disk and "
+"partition you selected for your <filename>/</filename> filesystem and, if "
+"you chose to install <filename>/boot</filename> on a separate partition, "
+"also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2528,7 +3803,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3151
 #, no-c-format
-msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
+msgid ""
+"This is the last step in the &debian; installation process during which the "
+"installer will do any last minute tasks. It mostly consists of tidying up "
+"after the &d-i;."
 msgstr ""
 
 #. Tag: title
@@ -2540,19 +3818,32 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3166
 #, no-c-format
-msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
+msgid ""
+"The installer may ask you if the computer's clock is set to UTC. Normally "
+"this question is avoided if possible and the installer tries to work out "
+"whether the clock is set to UTC based on things like what other operating "
+"systems are installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3173
 #, no-c-format
-msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
+msgid ""
+"In expert mode you will always be able to choose whether or not the clock is "
+"set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally "
+"set to local time. If you want to dual-boot, select local time instead of "
+"UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or "
+"Windows are normally set to local time. If you want to dual-boot, select "
+"local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3184
 #, no-c-format
-msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
+msgid ""
+"At this point &d-i; will also attempt to save the current time to the "
+"system's hardware clock. This will be done either in UTC or local time, "
+"depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
@@ -2564,13 +3855,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3201
 #, no-c-format
-msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system."
+msgid ""
+"You will be prompted to remove the boot media (CD, floppy, etc) that you "
+"used to boot the installer. After that the system will be rebooted into your "
+"new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3207
 #, no-c-format
-msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation."
+msgid ""
+"After a final prompt the system will be halted because rebooting is not "
+"supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD "
+"which you selected for the root filesystem during the first steps of the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2582,7 +3880,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3221
 #, no-c-format
-msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
+msgid ""
+"The components listed in this section are usually not involved in the "
+"installation process, but are waiting in the background to help the user in "
+"case something goes wrong."
 msgstr ""
 
 #. Tag: title
@@ -2594,13 +3895,21 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3236
 #, no-c-format
-msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system."
+msgid ""
+"If the installation is successful, the logfiles created during the "
+"installation process will be automatically saved to <filename>/var/log/"
+"installer/</filename> on your new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3243
 #, no-c-format
-msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
+msgid ""
+"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu "
+"allows you to save the log files to a floppy disk, network, hard disk, or "
+"other media. This can be useful if you encounter fatal problems during the "
+"installation and wish to study the logs on another system or attach them to "
+"an installation report."
 msgstr ""
 
 #. Tag: title
@@ -2612,7 +3921,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3265
 #, no-c-format
-msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
+msgid ""
+"There are several methods you can use to get a shell while running an "
+"installation. On most systems, and if you are not installing over serial "
+"console, the easiest method is to switch to the second <emphasis>virtual "
+"console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> "
+"<keycap>F2</keycap></keycombo><footnote> <para> That is: press the "
+"<keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</"
+"keycap> and the <keycap>F2</keycap> function key at the same time. </para> </"
+"footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</"
+"keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</"
+"keycap></keycombo> to switch back to the installer itself."
 msgstr ""
 
 #. Tag: para
@@ -2624,31 +3943,52 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3287
 #, no-c-format
-msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
+msgid ""
+"If you cannot switch consoles, there is also an <guimenuitem>Execute a "
+"Shell</guimenuitem> item on the main menu that can be used to start a shell. "
+"You can get to the main menu from most dialogs by using the &BTN-GOBACK; "
+"button one or more times. Type <userinput>exit</userinput> to close the "
+"shell and return to the installer."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3295
 #, no-c-format
-msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
+msgid ""
+"At this point you are booted from the RAM disk, and there is a limited set "
+"of Unix utilities available for your use. You can see what programs are "
+"available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</"
+"command> and by typing <command>help</command>. The shell is a Bourne shell "
+"clone called <command>ash</command> and has some nice features like "
+"autocompletion and history."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3304
 #, no-c-format
-msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
+msgid ""
+"To edit and view files, use the text editor <command>nano</command>. Log "
+"files for the installation system can be found in the <filename>/var/log</"
+"filename> directory."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3311
 #, no-c-format
-msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
+msgid ""
+"Although you can do basically anything in a shell that the available "
+"commands allow you to do, the option to use a shell is really only there in "
+"case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3317
 #, no-c-format
-msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
+msgid ""
+"Doing things manually from the shell may interfere with the installation "
+"process and result in errors or an incomplete installation. In particular, "
+"you should always use let the installer activate your swap partition and not "
+"do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
@@ -2660,70 +4000,146 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3335
 #, no-c-format
-msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
+msgid ""
+"One of the more interesting components is <firstterm>network-console</"
+"firstterm>. It allows you to do a large part of the installation over the "
+"network via SSH. The use of the network implies you will have to perform the "
+"first steps of the installation from the console, at least to the point of "
+"setting up the networking. (Although you can automate that part with <xref "
+"linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3345
 #, no-c-format
-msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
+msgid ""
+"This component is not loaded into the main installation menu by default, so "
+"you have to explicitly ask for it. If you are installing from CD, you need "
+"to boot with medium priority or otherwise invoke the main installation menu "
+"and choose <guimenuitem>Load installer components from CD</guimenuitem> and "
+"from the list of additional components select <guimenuitem>network-console: "
+"Continue installation remotely using SSH</guimenuitem>. Successful load is "
+"indicated by a new menu entry called <guimenuitem>Continue installation "
+"remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3358
 #, no-c-format
-msgid "For installations on &arch-title;, this is the default method after setting up the network."
+msgid ""
+"For installations on &arch-title;, this is the default method after setting "
+"up the network."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3363
 #, no-c-format
-msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely."
+msgid ""
+"<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> "
+"<phrase arch=\"s390\">You</phrase> will be asked for a new password to be "
+"used for connecting to the installation system and for its confirmation. "
+"That's all. Now you should see a screen which instructs you to login "
+"remotely as the user <emphasis>installer</emphasis> with the password you "
+"just provided. Another important detail to notice on this screen is the "
+"fingerprint of this system. You need to transfer the fingerprint securely to "
+"the person who will continue the installation remotely."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3375
 #, no-c-format
-msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
+msgid ""
+"Should you decide to continue with the installation locally, you can always "
+"press &enterkey;, which will bring you back to the main menu, where you can "
+"select another component."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3381
 #, no-c-format
 msgid ""
-      "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
-      "<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n"
-      "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct."
+"Now let's switch to the other side of the wire. As a prerequisite, you need "
+"to configure your terminal for UTF-8 encoding, because that is what the "
+"installation system uses. If you do not, remote installation will be still "
+"possible, but you may encounter strange display artefacts like destroyed "
+"dialog borders or unreadable non-ascii characters. Establishing a connection "
+"with the installation system is as simple as typing: "
+"<informalexample><screen>\n"
+"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</"
+"replaceable></userinput>\n"
+"</screen></informalexample> Where <replaceable>install_host</replaceable> is "
+"either the name or IP address of the computer being installed. Before the "
+"actual login the fingerprint of the remote system will be displayed and you "
+"will have to confirm that it is correct."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3398
 #, no-c-format
-msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
+msgid ""
+"The <command>ssh</command> server in the installer uses a default "
+"configuration that does not send keep-alive packets. In principle, a "
+"connection to the system being installed should be kept open indefinitely. "
+"However, in some situations &mdash; depending on your local network setup "
+"&mdash; the connection may be lost after some period of inactivity. One "
+"common case where this can happen is when there is some form of Network "
+"Address Translation (NAT) somewhere between the client and the system being "
+"installed. Depending on at which point of the installation the connection "
+"was lost, you may or may not be able to resume the installation after "
+"reconnecting."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3411
 #, no-c-format
-msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
+msgid ""
+"You may be able to avoid the connection being dropped by adding the option "
+"<userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></"
+"userinput> when starting the <command>ssh</command> connection, or by adding "
+"that option in your <command>ssh</command> configuration file. Note however "
+"that in some cases adding this option may also <emphasis>cause</emphasis> a "
+"connection to be dropped (for example if keep-alive packets are sent during "
+"a brief network outage, from which <command>ssh</command> would otherwise "
+"have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3424
 #, no-c-format
-msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
+msgid ""
+"If you install several computers in turn and they happen to have the same IP "
+"address or hostname, <command>ssh</command> will refuse to connect to such "
+"host. The reason is that it will have different fingerprint, which is "
+"usually a sign of a spoofing attack. If you are sure this is not the case, "
+"you will need to delete the relevant line from <filename>~/.ssh/known_hosts</"
+"filename><footnote> <para> The following command will remove an existing "
+"entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</"
+"replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </"
+"para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3440
 #, no-c-format
-msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
+msgid ""
+"After the login you will be presented with an initial screen where you have "
+"two possibilities called <guimenuitem>Start menu</guimenuitem> and "
+"<guimenuitem>Start shell</guimenuitem>. The former brings you to the main "
+"installer menu, where you can continue with the installation as usual. The "
+"latter starts a shell from which you can examine and possibly fix the remote "
+"system. You should only start one SSH session for the installation menu, but "
+"may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3450
 #, no-c-format
-msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
+msgid ""
+"After you have started the installation remotely over SSH, you should not go "
+"back to the installation session running on the local console. Doing so may "
+"corrupt the database that holds the configuration of the new system. This in "
+"turn may result in a failed installation or problems with the installed "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -2735,25 +4151,44 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3470
 #, no-c-format
-msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
+msgid ""
+"As described in <xref linkend=\"hardware-firmware\"/>, some devices require "
+"firmware to be loaded. In most cases the device will not work at all if the "
+"firmware is not available; sometimes basic functionality is not impaired if "
+"it is missing and the firmware is only needed to enable additional features."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3478
 #, no-c-format
-msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
+msgid ""
+"If a device driver requests firmware that is not available, &d-i; will "
+"display a dialog offering to load the missing firmware. If this option is "
+"selected, &d-i; will scan available devices for either loose firmware files "
+"or packages containing firmware. If found, the firmware will be copied to "
+"the correct location (<filename>/lib/firmware</filename>) and the driver "
+"module will be reloaded."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3488
 #, no-c-format
-msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
+msgid ""
+"Which devices are scanned and which file systems are supported depends on "
+"the architecture, the installation method and the stage of the installation. "
+"Especially during the early stages of the installation, loading the firmware "
+"is most likely to succeed from a FAT-formatted floppy disk or USB stick. "
+"<phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an "
+"MMC or SD card.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3498
 #, no-c-format
-msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
+msgid ""
+"Note that it is possible to skip loading the firmware if you know the device "
+"will also function without it, or if the device is not needed during the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2765,25 +4200,47 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3507
 #, no-c-format
-msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
+msgid ""
+"Official CD images do not include non-free firmware. The most common method "
+"to load such firmware is from some removable medium such as a USB stick. "
+"Alternatively, unofficial CD builds containing non-free firmware can be "
+"found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick "
+"(or other medium like a hard drive partition, or floppy disk), the firmware "
+"files or packages must be placed in either the root directory or a directory "
+"named <filename>/firmware</filename> of the file system on the medium. The "
+"recommended file system to use is FAT as that is most certain to be "
+"supported during the early stages of the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3520
 #, no-c-format
-msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
+msgid ""
+"Tarballs and zip files containing current packages for the most common "
+"firmware are available from: <itemizedlist> <listitem><para> <ulink url="
+"\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just "
+"download the tarball or zip file for the correct release and unpack it to "
+"the file system on the medium."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3534
 #, no-c-format
-msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
+msgid ""
+"If the firmware you need is not included in the tarball, you can also "
+"download specific firmware packages from the (non-free section of the) "
+"archive. The following overview should list most available firmware packages "
+"but is not guaranteed to be complete and may also contain non-firmware "
+"packages:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3548
 #, no-c-format
-msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
+msgid ""
+"It is also possible to copy individual firmware files to the medium. Loose "
+"firmware could be obtained for example from an already installed system or "
+"from a hardware vendor."
 msgstr ""
 
 #. Tag: title
@@ -2795,24 +4252,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3558
 #, no-c-format
-msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
+msgid ""
+"Any firmware loaded during the installation will be copied automatically to "
+"the installed system. In most cases this will ensure that the device that "
+"requires the firmware will also work correctly after the system is rebooted "
+"into the installed system. However, if the installed system runs a different "
+"kernel version from the installer there is a slight chance that the firmware "
+"cannot be loaded due to version skew."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3567
 #, no-c-format
-msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
+msgid ""
+"If the firmware was loaded from a firmware package, &d-i; will also install "
+"this package for the installed system and will automatically add the non-"
+"free section of the package archive in APT's <filename>sources.list</"
+"filename>. This has the advantage that the firmware should be updated "
+"automatically if a new version becomes available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3575
 #, no-c-format
-msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
+msgid ""
+"If loading the firmware was skipped during the installation, the relevant "
+"device will probably not work with the installed system until the firmware "
+"(package) is installed manually."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3582
 #, no-c-format
-msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
+msgid ""
+"If the firmware was loaded from loose firmware files, the firmware copied to "
+"the installed system will <emphasis>not</emphasis> be automatically updated "
+"unless the corresponding firmware package (if available) is installed after "
+"the installation is completed."
 msgstr ""
-
diff --git a/po/nl/welcome.po b/po/nl/welcome.po
index 0d1732af4..17fad591c 100644
--- a/po/nl/welcome.po
+++ b/po/nl/welcome.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:5
 #, no-c-format
-msgid "This chapter provides an overview of the &debian; Project and &debian-gnu;. If you already know about the &debian; Project's history and the &debian-gnu; distribution, feel free to skip to the next chapter."
+msgid ""
+"This chapter provides an overview of the &debian; Project and &debian-gnu;. "
+"If you already know about the &debian; Project's history and the &debian-"
+"gnu; distribution, feel free to skip to the next chapter."
 msgstr ""
 
 #. Tag: title
@@ -34,67 +38,116 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:20
 #, no-c-format
-msgid "Debian is an all-volunteer organization dedicated to developing free software and promoting the ideals of the Free Software community. The Debian Project began in 1993, when Ian Murdock issued an open invitation to software developers to contribute to a complete and coherent software distribution based on the relatively new Linux kernel. That relatively small band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-fsf;\">Free Software Foundation</ulink> and influenced by the <ulink url=\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years into an organization of around &num-of-debian-developers; <firstterm>Debian Developers</firstterm>."
+msgid ""
+"Debian is an all-volunteer organization dedicated to developing free "
+"software and promoting the ideals of the Free Software community. The Debian "
+"Project began in 1993, when Ian Murdock issued an open invitation to "
+"software developers to contribute to a complete and coherent software "
+"distribution based on the relatively new Linux kernel. That relatively small "
+"band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-"
+"fsf;\">Free Software Foundation</ulink> and influenced by the <ulink url="
+"\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years into an "
+"organization of around &num-of-debian-developers; <firstterm>Debian "
+"Developers</firstterm>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:35
 #, no-c-format
-msgid "Debian Developers are involved in a variety of activities, including <ulink url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;\">FTP</ulink> site administration, graphic design, legal analysis of software licenses, writing documentation, and, of course, maintaining software packages."
+msgid ""
+"Debian Developers are involved in a variety of activities, including <ulink "
+"url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;"
+"\">FTP</ulink> site administration, graphic design, legal analysis of "
+"software licenses, writing documentation, and, of course, maintaining "
+"software packages."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:44
 #, no-c-format
-msgid "In the interest of communicating our philosophy and attracting developers who believe in the principles that Debian stands for, the Debian Project has published a number of documents that outline our values and serve as guides to what it means to be a Debian Developer:"
+msgid ""
+"In the interest of communicating our philosophy and attracting developers "
+"who believe in the principles that Debian stands for, the Debian Project has "
+"published a number of documents that outline our values and serve as guides "
+"to what it means to be a Debian Developer:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:52
 #, no-c-format
-msgid "The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a statement of Debian's commitments to the Free Software Community. Anyone who agrees to abide to the Social Contract may become a <ulink url=\"&url-new-maintainer;\">maintainer</ulink>. Any maintainer can introduce new software into Debian &mdash; provided that the software meets our criteria for being free, and the package follows our quality standards."
+msgid ""
+"The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a "
+"statement of Debian's commitments to the Free Software Community. Anyone who "
+"agrees to abide to the Social Contract may become a <ulink url=\"&url-new-"
+"maintainer;\">maintainer</ulink>. Any maintainer can introduce new software "
+"into Debian &mdash; provided that the software meets our criteria for being "
+"free, and the package follows our quality standards."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:64
 #, no-c-format
-msgid "The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a clear and concise statement of Debian's criteria for free software. The DFSG is a very influential document in the Free Software Movement, and was the foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</ulink>."
+msgid ""
+"The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a "
+"clear and concise statement of Debian's criteria for free software. The DFSG "
+"is a very influential document in the Free Software Movement, and was the "
+"foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</"
+"ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:74
 #, no-c-format
-msgid "The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an extensive specification of the Debian Project's standards of quality."
+msgid ""
+"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an "
+"extensive specification of the Debian Project's standards of quality."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:82
 #, no-c-format
-msgid "Debian developers are also involved in a number of other projects; some specific to Debian, others involving some or all of the Linux community. Some examples include:"
+msgid ""
+"Debian developers are also involved in a number of other projects; some "
+"specific to Debian, others involving some or all of the Linux community. "
+"Some examples include:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:89
 #, no-c-format
-msgid "The <ulink url=\"&url-lsb-org;\">Linux Standard Base</ulink> (LSB) is a project aimed at standardizing the basic GNU/Linux system, which will enable third-party software and hardware developers to easily design programs and device drivers for Linux-in-general, rather than for a specific GNU/Linux distribution."
+msgid ""
+"The <ulink url=\"&url-lsb-org;\">Linux Standard Base</ulink> (LSB) is a "
+"project aimed at standardizing the basic GNU/Linux system, which will enable "
+"third-party software and hardware developers to easily design programs and "
+"device drivers for Linux-in-general, rather than for a specific GNU/Linux "
+"distribution."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:99
 #, no-c-format
-msgid "The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> (FHS) is an effort to standardize the layout of the Linux file system. The FHS will allow software developers to concentrate their efforts on designing programs, without having to worry about how the package will be installed in different GNU/Linux distributions."
+msgid ""
+"The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> "
+"(FHS) is an effort to standardize the layout of the Linux file system. The "
+"FHS will allow software developers to concentrate their efforts on designing "
+"programs, without having to worry about how the package will be installed in "
+"different GNU/Linux distributions."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:109
 #, no-c-format
-msgid "<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, aimed at making sure Debian has something to offer to our youngest users."
+msgid ""
+"<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, "
+"aimed at making sure Debian has something to offer to our youngest users."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:118
 #, no-c-format
-msgid "For more general information about Debian, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>."
+msgid ""
+"For more general information about Debian, see the <ulink url=\"&url-debian-"
+"faq;\">Debian FAQ</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,61 +159,113 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:134
 #, no-c-format
-msgid "Linux is an operating system: a series of programs that let you interact with your computer and run other programs."
+msgid ""
+"Linux is an operating system: a series of programs that let you interact "
+"with your computer and run other programs."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:139
 #, no-c-format
-msgid "An operating system consists of various fundamental programs which are needed by your computer so that it can communicate and receive instructions from users; read and write data to hard disks, tapes, and printers; control the use of memory; and run other software. The most important part of an operating system is the kernel. In a GNU/Linux system, Linux is the kernel component. The rest of the system consists of other programs, many of which were written by or for the GNU Project. Because the Linux kernel alone does not form a working operating system, we prefer to use the term <quote>GNU/Linux</quote> to refer to systems that many people casually refer to as <quote>Linux</quote>."
+msgid ""
+"An operating system consists of various fundamental programs which are "
+"needed by your computer so that it can communicate and receive instructions "
+"from users; read and write data to hard disks, tapes, and printers; control "
+"the use of memory; and run other software. The most important part of an "
+"operating system is the kernel. In a GNU/Linux system, Linux is the kernel "
+"component. The rest of the system consists of other programs, many of which "
+"were written by or for the GNU Project. Because the Linux kernel alone does "
+"not form a working operating system, we prefer to use the term <quote>GNU/"
+"Linux</quote> to refer to systems that many people casually refer to as "
+"<quote>Linux</quote>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:153
 #, no-c-format
-msgid "Linux is modelled on the Unix operating system. From the start, Linux was designed to be a multi-tasking, multi-user system. These facts are enough to make Linux different from other well-known operating systems. However, Linux is even more different than you might imagine. In contrast to other operating systems, nobody owns Linux. Much of its development is done by unpaid volunteers."
+msgid ""
+"Linux is modelled on the Unix operating system. From the start, Linux was "
+"designed to be a multi-tasking, multi-user system. These facts are enough to "
+"make Linux different from other well-known operating systems. However, Linux "
+"is even more different than you might imagine. In contrast to other "
+"operating systems, nobody owns Linux. Much of its development is done by "
+"unpaid volunteers."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:162
 #, no-c-format
-msgid "Development of what later became GNU/Linux began in 1984, when the <ulink url=\"&url-fsf;\">Free Software Foundation</ulink> began development of a free Unix-like operating system called GNU."
+msgid ""
+"Development of what later became GNU/Linux began in 1984, when the <ulink "
+"url=\"&url-fsf;\">Free Software Foundation</ulink> began development of a "
+"free Unix-like operating system called GNU."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:168
 #, no-c-format
-msgid "The <ulink url=\"&url-gnu;\">GNU Project</ulink> has developed a comprehensive set of free software tools for use with Unix&trade; and Unix-like operating systems such as Linux. These tools enable users to perform tasks ranging from the mundane (such as copying or removing files from the system) to the arcane (such as writing and compiling programs or doing sophisticated editing in a variety of document formats)."
+msgid ""
+"The <ulink url=\"&url-gnu;\">GNU Project</ulink> has developed a "
+"comprehensive set of free software tools for use with Unix&trade; and Unix-"
+"like operating systems such as Linux. These tools enable users to perform "
+"tasks ranging from the mundane (such as copying or removing files from the "
+"system) to the arcane (such as writing and compiling programs or doing "
+"sophisticated editing in a variety of document formats)."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:178
 #, no-c-format
-msgid "While many groups and individuals have contributed to Linux, the largest single contributor is still the Free Software Foundation, which created not only most of the tools used in Linux, but also the philosophy and the community that made Linux possible."
+msgid ""
+"While many groups and individuals have contributed to Linux, the largest "
+"single contributor is still the Free Software Foundation, which created not "
+"only most of the tools used in Linux, but also the philosophy and the "
+"community that made Linux possible."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:185
 #, no-c-format
-msgid "The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in 1991, when a Finnish computing science student named Linus Torvalds announced an early version of a replacement kernel for Minix to the Usenet newsgroup <userinput>comp.os.minix</userinput>. See Linux International's <ulink url=\"&url-linux-history;\">Linux History Page</ulink>."
+msgid ""
+"The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in "
+"1991, when a Finnish computing science student named Linus Torvalds "
+"announced an early version of a replacement kernel for Minix to the Usenet "
+"newsgroup <userinput>comp.os.minix</userinput>. See Linux International's "
+"<ulink url=\"&url-linux-history;\">Linux History Page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:194
 #, no-c-format
-msgid "Linus Torvalds continues to coordinate the work of several hundred developers with the help of a number of subsystem maintainers. There is an <ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux kernel. More information about the <userinput>linux-kernel</userinput> mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel mailing list FAQ</ulink>."
+msgid ""
+"Linus Torvalds continues to coordinate the work of several hundred "
+"developers with the help of a number of subsystem maintainers. There is an "
+"<ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux "
+"kernel. More information about the <userinput>linux-kernel</userinput> "
+"mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;"
+"\">linux-kernel mailing list FAQ</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:204
 #, no-c-format
-msgid "Linux users have immense freedom of choice in their software. For example, Linux users can choose from a dozen different command line shells and several graphical desktops. This selection is often bewildering to users of other operating systems, who are not used to thinking of the command line or desktop as something that they can change."
+msgid ""
+"Linux users have immense freedom of choice in their software. For example, "
+"Linux users can choose from a dozen different command line shells and "
+"several graphical desktops. This selection is often bewildering to users of "
+"other operating systems, who are not used to thinking of the command line or "
+"desktop as something that they can change."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:213
 #, no-c-format
-msgid "Linux is also less likely to crash, better able to run more than one program at the same time, and more secure than many operating systems. With these advantages, Linux is the fastest growing operating system in the server market. More recently, Linux has begun to be popular among home and business users as well."
+msgid ""
+"Linux is also less likely to crash, better able to run more than one program "
+"at the same time, and more secure than many operating systems. With these "
+"advantages, Linux is the fastest growing operating system in the server "
+"market. More recently, Linux has begun to be popular among home and business "
+"users as well."
 msgstr ""
 
 #. Tag: title
@@ -172,49 +277,96 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:232
 #, no-c-format
-msgid "The combination of &debian;'s philosophy and methodology and the GNU tools, the Linux kernel, and other important free software, form a unique software distribution called &debian; GNU/Linux. This distribution is made up of a large number of software <emphasis>packages</emphasis>. Each package in the distribution contains executables, scripts, documentation, and configuration information, and has a <emphasis>maintainer</emphasis> who is primarily responsible for keeping the package up-to-date, tracking bug reports, and communicating with the upstream author(s) of the packaged software. Our extremely large user base, combined with our bug tracking system ensures that problems are found and fixed quickly."
+msgid ""
+"The combination of &debian;'s philosophy and methodology and the GNU tools, "
+"the Linux kernel, and other important free software, form a unique software "
+"distribution called &debian; GNU/Linux. This distribution is made up of a "
+"large number of software <emphasis>packages</emphasis>. Each package in the "
+"distribution contains executables, scripts, documentation, and configuration "
+"information, and has a <emphasis>maintainer</emphasis> who is primarily "
+"responsible for keeping the package up-to-date, tracking bug reports, and "
+"communicating with the upstream author(s) of the packaged software. Our "
+"extremely large user base, combined with our bug tracking system ensures "
+"that problems are found and fixed quickly."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:246
 #, no-c-format
-msgid "&debian;'s attention to detail allows us to produce a high-quality, stable, and scalable distribution. Installations can be easily configured to serve many roles, from stripped-down firewalls to desktop scientific workstations to high-end network servers."
+msgid ""
+"&debian;'s attention to detail allows us to produce a high-quality, stable, "
+"and scalable distribution. Installations can be easily configured to serve "
+"many roles, from stripped-down firewalls to desktop scientific workstations "
+"to high-end network servers."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:253
 #, no-c-format
-msgid "&debian; is especially popular among advanced users because of its technical excellence and its deep commitment to the needs and expectations of the Linux community. &debian; also introduced many features to Linux that are now commonplace."
+msgid ""
+"&debian; is especially popular among advanced users because of its technical "
+"excellence and its deep commitment to the needs and expectations of the "
+"Linux community. &debian; also introduced many features to Linux that are "
+"now commonplace."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:260
 #, no-c-format
-msgid "For example, &debian; was the first Linux distribution to include a package management system for easy installation and removal of software. It was also the first Linux distribution that could be upgraded without requiring reinstallation."
+msgid ""
+"For example, &debian; was the first Linux distribution to include a package "
+"management system for easy installation and removal of software. It was also "
+"the first Linux distribution that could be upgraded without requiring "
+"reinstallation."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:267
 #, no-c-format
-msgid "&debian; continues to be a leader in Linux development. Its development process is an example of just how well the Open Source development model can work &mdash; even for very complex tasks such as building and maintaining a complete operating system."
+msgid ""
+"&debian; continues to be a leader in Linux development. Its development "
+"process is an example of just how well the Open Source development model can "
+"work &mdash; even for very complex tasks such as building and maintaining a "
+"complete operating system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:274
 #, no-c-format
-msgid "The feature that most distinguishes &debian; from other Linux distributions is its package management system. These tools give the administrator of a &debian; system complete control over the packages installed on that system, including the ability to install a single package or automatically update the entire operating system. Individual packages can also be protected from being updated. You can even tell the package management system about software you have compiled yourself and what dependencies it fulfills."
+msgid ""
+"The feature that most distinguishes &debian; from other Linux distributions "
+"is its package management system. These tools give the administrator of a "
+"&debian; system complete control over the packages installed on that system, "
+"including the ability to install a single package or automatically update "
+"the entire operating system. Individual packages can also be protected from "
+"being updated. You can even tell the package management system about "
+"software you have compiled yourself and what dependencies it fulfills."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:285
 #, no-c-format
-msgid "To protect your system against <quote>Trojan horses</quote> and other malevolent software, &debian;'s servers verify that uploaded packages come from their registered &debian; maintainers. &debian; packagers also take great care to configure their packages in a secure manner. When security problems in shipped packages do appear, fixes are usually available very quickly. With &debian;'s simple update options, security fixes can be downloaded and installed automatically across the Internet."
+msgid ""
+"To protect your system against <quote>Trojan horses</quote> and other "
+"malevolent software, &debian;'s servers verify that uploaded packages come "
+"from their registered &debian; maintainers. &debian; packagers also take "
+"great care to configure their packages in a secure manner. When security "
+"problems in shipped packages do appear, fixes are usually available very "
+"quickly. With &debian;'s simple update options, security fixes can be "
+"downloaded and installed automatically across the Internet."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:295
 #, no-c-format
-msgid "The primary, and best, method of getting support for your &debian; GNU/Linux system and communicating with &debian; Developers is through the many mailing lists maintained by the &debian; Project (there are more than &num-of-debian-maillists; at this writing). The easiest way to subscribe to one or more of these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> Debian's mailing list subscription page</ulink> and fill out the form you'll find there."
+msgid ""
+"The primary, and best, method of getting support for your &debian; GNU/Linux "
+"system and communicating with &debian; Developers is through the many "
+"mailing lists maintained by the &debian; Project (there are more than &num-"
+"of-debian-maillists; at this writing). The easiest way to subscribe to one "
+"or more of these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> "
+"Debian's mailing list subscription page</ulink> and fill out the form you'll "
+"find there."
 msgstr ""
 
 #. Tag: title
@@ -226,25 +378,33 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:317
 #, no-c-format
-msgid "&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel."
+msgid ""
+"&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:321
 #, no-c-format
-msgid "This port of &debian; is currently only being developed for the i386 and amd64 architectures, although ports to other architectures is possible."
+msgid ""
+"This port of &debian; is currently only being developed for the i386 and "
+"amd64 architectures, although ports to other architectures is possible."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:326
 #, no-c-format
-msgid "Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some information on Linux system may not apply to it."
+msgid ""
+"Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some "
+"information on Linux system may not apply to it."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:331
 #, no-c-format
-msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/kfreebsd-gnu/\"> &debian; GNU/kFreeBSD ports page</ulink> and the <email>debian-bsd@lists.debian.org</email> mailing list."
+msgid ""
+"For more information, see the <ulink url=\"http://www.debian.org/ports/"
+"kfreebsd-gnu/\"> &debian; GNU/kFreeBSD ports page</ulink> and the "
+"<email>debian-bsd@lists.debian.org</email> mailing list."
 msgstr ""
 
 #. Tag: title
@@ -256,25 +416,36 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:352
 #, no-c-format
-msgid "&debian; GNU/Hurd is a &debian; GNU system with the GNU Hurd &mdash; a set of servers running on top of the GNU Mach microkernel."
+msgid ""
+"&debian; GNU/Hurd is a &debian; GNU system with the GNU Hurd &mdash; a set "
+"of servers running on top of the GNU Mach microkernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:357
 #, no-c-format
-msgid "The Hurd is still unfinished, and is unsuitable for day-to-day use, but work is continuing. The Hurd is currently only being developed for the i386 architecture, although ports to other architectures will be made once the system becomes more stable."
+msgid ""
+"The Hurd is still unfinished, and is unsuitable for day-to-day use, but work "
+"is continuing. The Hurd is currently only being developed for the i386 "
+"architecture, although ports to other architectures will be made once the "
+"system becomes more stable."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:365
 #, no-c-format
-msgid "Please note that &debian; GNU/Hurd is not a Linux system, and thus some information on Linux system may not apply to it."
+msgid ""
+"Please note that &debian; GNU/Hurd is not a Linux system, and thus some "
+"information on Linux system may not apply to it."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:370
 #, no-c-format
-msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/\"> &debian; GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists.debian.org</email> mailing list."
+msgid ""
+"For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/"
+"\"> &debian; GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists."
+"debian.org</email> mailing list."
 msgstr ""
 
 #. Tag: title
@@ -286,13 +457,21 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:389
 #, no-c-format
-msgid "For information on how to download &debian-gnu; from the Internet or from whom official &debian; CDs can be purchased, see the <ulink url=\"&url-debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink> contains a full set of official &debian; mirrors, so you can easily find the nearest one."
+msgid ""
+"For information on how to download &debian-gnu; from the Internet or from "
+"whom official &debian; CDs can be purchased, see the <ulink url=\"&url-"
+"debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-"
+"debian-mirrors;\">list of &debian; mirrors</ulink> contains a full set of "
+"official &debian; mirrors, so you can easily find the nearest one."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:398
 #, no-c-format
-msgid "&debian; can be upgraded after installation very easily. The installation procedure will help set up the system so that you can make those upgrades once installation is complete, if need be."
+msgid ""
+"&debian; can be upgraded after installation very easily. The installation "
+"procedure will help set up the system so that you can make those upgrades "
+"once installation is complete, if need be."
 msgstr ""
 
 #. Tag: title
@@ -304,7 +483,12 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:415
 #, no-c-format
-msgid "This document is constantly being revised. Be sure to check the <ulink url=\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute information about the &release; release of the &debian-gnu; system. Updated versions of this installation manual are also available from the <ulink url=\"&url-install-manual;\">official Install Manual pages</ulink>."
+msgid ""
+"This document is constantly being revised. Be sure to check the <ulink url="
+"\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute "
+"information about the &release; release of the &debian-gnu; system. Updated "
+"versions of this installation manual are also available from the <ulink url="
+"\"&url-install-manual;\">official Install Manual pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -316,67 +500,104 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:435
 #, no-c-format
-msgid "This document is meant to serve as a manual for first-time &debian; users. It tries to make as few assumptions as possible about your level of expertise. However, we do assume that you have a general understanding of how the hardware in your computer works."
+msgid ""
+"This document is meant to serve as a manual for first-time &debian; users. "
+"It tries to make as few assumptions as possible about your level of "
+"expertise. However, we do assume that you have a general understanding of "
+"how the hardware in your computer works."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:442
 #, no-c-format
-msgid "Expert users may also find interesting reference information in this document, including minimum installation sizes, details about the hardware supported by the &debian; installation system, and so on. We encourage expert users to jump around in the document."
+msgid ""
+"Expert users may also find interesting reference information in this "
+"document, including minimum installation sizes, details about the hardware "
+"supported by the &debian; installation system, and so on. We encourage "
+"expert users to jump around in the document."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:449
 #, no-c-format
-msgid "In general, this manual is arranged in a linear fashion, walking you through the installation process from start to finish. Here are the steps in installing &debian-gnu;, and the sections of this document which correlate with each step:"
+msgid ""
+"In general, this manual is arranged in a linear fashion, walking you through "
+"the installation process from start to finish. Here are the steps in "
+"installing &debian-gnu;, and the sections of this document which correlate "
+"with each step:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:457
 #, no-c-format
-msgid "Determine whether your hardware meets the requirements for using the installation system, in <xref linkend=\"hardware-req\"/>."
+msgid ""
+"Determine whether your hardware meets the requirements for using the "
+"installation system, in <xref linkend=\"hardware-req\"/>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:463
 #, no-c-format
-msgid "Backup your system, perform any necessary planning and hardware configuration prior to installing &debian;, in <xref linkend=\"preparing\"/>. If you are preparing a multi-boot system, you may need to create partitionable space on your hard disk for &debian; to use."
+msgid ""
+"Backup your system, perform any necessary planning and hardware "
+"configuration prior to installing &debian;, in <xref linkend=\"preparing\"/"
+">. If you are preparing a multi-boot system, you may need to create "
+"partitionable space on your hard disk for &debian; to use."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:471
 #, no-c-format
-msgid "In <xref linkend=\"install-methods\"/>, you will obtain the necessary installation files for your method of installation."
+msgid ""
+"In <xref linkend=\"install-methods\"/>, you will obtain the necessary "
+"installation files for your method of installation."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:477
 #, no-c-format
-msgid "describes booting into the installation system. This chapter also discusses troubleshooting procedures in case you have problems with this step."
+msgid ""
+"describes booting into the installation system. This chapter also discusses "
+"troubleshooting procedures in case you have problems with this step."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:484
 #, no-c-format
-msgid "Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a &debian; server (if you are not installing from a CD/DVD set), partitioning your hard drives and installation of a base system, then selection and installation of tasks. (Some background about setting up the partitions for your &debian; system is explained in <xref linkend=\"partitioning\"/>.)"
+msgid ""
+"Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. "
+"This involves choosing your language, configuring peripheral driver modules, "
+"configuring your network connection, so that remaining installation files "
+"can be obtained directly from a &debian; server (if you are not installing "
+"from a CD/DVD set), partitioning your hard drives and installation of a base "
+"system, then selection and installation of tasks. (Some background about "
+"setting up the partitions for your &debian; system is explained in <xref "
+"linkend=\"partitioning\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:497
 #, no-c-format
-msgid "Boot into your newly installed base system, from <xref linkend=\"boot-new\"/>."
+msgid ""
+"Boot into your newly installed base system, from <xref linkend=\"boot-new\"/"
+">."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:505
 #, no-c-format
-msgid "Once you've got your system installed, you can read <xref linkend=\"post-install\"/>. That chapter explains where to look to find more information about Unix and &debian;, and how to replace your kernel."
+msgid ""
+"Once you've got your system installed, you can read <xref linkend=\"post-"
+"install\"/>. That chapter explains where to look to find more information "
+"about Unix and &debian;, and how to replace your kernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:515
 #, no-c-format
-msgid "Finally, information about this document and how to contribute to it may be found in <xref linkend=\"administrivia\"/>."
+msgid ""
+"Finally, information about this document and how to contribute to it may be "
+"found in <xref linkend=\"administrivia\"/>."
 msgstr ""
 
 #. Tag: title
@@ -388,13 +609,22 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:527
 #, no-c-format
-msgid "Any help, suggestions, and especially, patches, are greatly appreciated. Working versions of this document can be found at <ulink url=\"&url-d-i-alioth-manual;\"></ulink>. There you will find a list of all the different architectures and languages for which this document is available."
+msgid ""
+"Any help, suggestions, and especially, patches, are greatly appreciated. "
+"Working versions of this document can be found at <ulink url=\"&url-d-i-"
+"alioth-manual;\"></ulink>. There you will find a list of all the different "
+"architectures and languages for which this document is available."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:534
 #, no-c-format
-msgid "Source is also available publicly; look in <xref linkend=\"administrivia\"/> for more information concerning how to contribute. We welcome suggestions, comments, patches, and bug reports (use the package <classname>installation-guide</classname> for bugs, but check first to see if the problem is already reported)."
+msgid ""
+"Source is also available publicly; look in <xref linkend=\"administrivia\"/> "
+"for more information concerning how to contribute. We welcome suggestions, "
+"comments, patches, and bug reports (use the package <classname>installation-"
+"guide</classname> for bugs, but check first to see if the problem is already "
+"reported)."
 msgstr ""
 
 #. Tag: title
@@ -406,42 +636,91 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:553
 #, no-c-format
-msgid "We're sure that you've read some of the licenses that come with most commercial software &mdash; they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of &debian-gnu; on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and <emphasis>sell</emphasis> them &mdash; albeit with a few restrictions. Your freedom to install and use the system comes directly from &debian; being based on <emphasis>free software</emphasis>."
+msgid ""
+"We're sure that you've read some of the licenses that come with most "
+"commercial software &mdash; they usually say that you can only use one copy "
+"of the software on a single computer. This system's license isn't like that "
+"at all. We encourage you to put a copy of &debian-gnu; on every computer in "
+"your school or place of business. Lend your installation media to your "
+"friends and help them install it on their computers! You can even make "
+"thousands of copies and <emphasis>sell</emphasis> them &mdash; albeit with a "
+"few restrictions. Your freedom to install and use the system comes directly "
+"from &debian; being based on <emphasis>free software</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:566
 #, no-c-format
-msgid "Calling software <emphasis>free</emphasis> doesn't mean that the software isn't copyrighted, and it doesn't mean that CDs/DVDs containing that software must be distributed at no charge. Free software, in part, means that the licenses of individual programs do not require you to pay for the privilege of distributing or using those programs. Free software also means that not only may anyone extend, adapt, and modify the software, but that they may distribute the results of their work as well."
+msgid ""
+"Calling software <emphasis>free</emphasis> doesn't mean that the software "
+"isn't copyrighted, and it doesn't mean that CDs/DVDs containing that "
+"software must be distributed at no charge. Free software, in part, means "
+"that the licenses of individual programs do not require you to pay for the "
+"privilege of distributing or using those programs. Free software also means "
+"that not only may anyone extend, adapt, and modify the software, but that "
+"they may distribute the results of their work as well."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:577
 #, no-c-format
-msgid "The &debian; project, as a pragmatic concession to its users, does make some packages available that do not meet our criteria for being free. These packages are not part of the official distribution, however, and are only available from the <userinput>contrib</userinput> or <userinput>non-free</userinput> areas of &debian; mirrors or on third-party CD/DVD-ROMs; see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian FTP archives</quote>, for more information about the layout and contents of the archives."
+msgid ""
+"The &debian; project, as a pragmatic concession to its users, does make some "
+"packages available that do not meet our criteria for being free. These "
+"packages are not part of the official distribution, however, and are only "
+"available from the <userinput>contrib</userinput> or <userinput>non-free</"
+"userinput> areas of &debian; mirrors or on third-party CD/DVD-ROMs; see the "
+"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian "
+"FTP archives</quote>, for more information about the layout and contents of "
+"the archives."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:591
 #, no-c-format
-msgid "Many of the programs in the system are licensed under the <emphasis>GNU</emphasis> <emphasis>General Public License</emphasis>, often simply referred to as <quote>the GPL</quote>. The GPL requires you to make the <emphasis>source code</emphasis> of the programs available whenever you distribute a binary copy of the program; that provision of the license ensures that any user will be able to modify the software. Because of this provision, the source code<footnote> <para> For information on how to locate, unpack, and build binaries from &debian; source packages, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of the Debian Package Management System</quote>. </para> </footnote> for all such programs is available in the &debian; system."
+msgid ""
+"Many of the programs in the system are licensed under the <emphasis>GNU</"
+"emphasis> <emphasis>General Public License</emphasis>, often simply referred "
+"to as <quote>the GPL</quote>. The GPL requires you to make the "
+"<emphasis>source code</emphasis> of the programs available whenever you "
+"distribute a binary copy of the program; that provision of the license "
+"ensures that any user will be able to modify the software. Because of this "
+"provision, the source code<footnote> <para> For information on how to "
+"locate, unpack, and build binaries from &debian; source packages, see the "
+"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of "
+"the Debian Package Management System</quote>. </para> </footnote> for all "
+"such programs is available in the &debian; system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:610
 #, no-c-format
-msgid "There are several other forms of copyright statements and software licenses used on the programs in &debian;. You can find the copyrights and licenses for every package installed on your system by looking in the file <filename>/usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> once you've installed a package on your system."
+msgid ""
+"There are several other forms of copyright statements and software licenses "
+"used on the programs in &debian;. You can find the copyrights and licenses "
+"for every package installed on your system by looking in the file <filename>/"
+"usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> "
+"once you've installed a package on your system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:620
 #, no-c-format
-msgid "For more information about licenses and how &debian; determines whether software is free enough to be included in the main distribution, see the <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>."
+msgid ""
+"For more information about licenses and how &debian; determines whether "
+"software is free enough to be included in the main distribution, see the "
+"<ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:626
 #, no-c-format
-msgid "The most important legal notice is that this software comes with <emphasis>no warranties</emphasis>. The programmers who have created this software have done so for the benefit of the community. No guarantee is made as to the suitability of the software for any given purpose. However, since the software is free, you are empowered to modify that software to suit your needs &mdash; and to enjoy the benefits of the changes made by others who have extended the software in this way."
+msgid ""
+"The most important legal notice is that this software comes with "
+"<emphasis>no warranties</emphasis>. The programmers who have created this "
+"software have done so for the benefit of the community. No guarantee is made "
+"as to the suitability of the software for any given purpose. However, since "
+"the software is free, you are empowered to modify that software to suit your "
+"needs &mdash; and to enjoy the benefits of the changes made by others who "
+"have extended the software in this way."
 msgstr ""
-
diff --git a/po/nn/administrivia.po b/po/nn/administrivia.po
index 29c5f204a..164f2ad70 100644
--- a/po/nn/administrivia.po
+++ b/po/nn/administrivia.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,44 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:11
 #, no-c-format
-msgid "This manual was created for Sarge's debian-installer, based on the Woody installation manual for boot-floppies, which was based on earlier Debian installation manuals, and on the Progeny distribution manual which was released under GPL in 2003."
+msgid ""
+"This manual was created for Sarge's debian-installer, based on the Woody "
+"installation manual for boot-floppies, which was based on earlier Debian "
+"installation manuals, and on the Progeny distribution manual which was "
+"released under GPL in 2003."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:18
 #, no-c-format
-msgid "This document is written in DocBook XML. Output formats are generated by various programs using information from the <classname>docbook-xml</classname> and <classname>docbook-xsl</classname> packages."
+msgid ""
+"This document is written in DocBook XML. Output formats are generated by "
+"various programs using information from the <classname>docbook-xml</"
+"classname> and <classname>docbook-xsl</classname> packages."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:25
 #, no-c-format
-msgid "In order to increase the maintainability of this document, we use a number of XML features, such as entities and profiling attributes. These play a role akin to variables and conditionals in programming languages. The XML source to this document contains information for each different architecture &mdash; profiling attributes are used to isolate certain bits of text as architecture-specific."
+msgid ""
+"In order to increase the maintainability of this document, we use a number "
+"of XML features, such as entities and profiling attributes. These play a "
+"role akin to variables and conditionals in programming languages. The XML "
+"source to this document contains information for each different architecture "
+"&mdash; profiling attributes are used to isolate certain bits of text as "
+"architecture-specific."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:34
 #, no-c-format
-msgid "Translators can use this paragraph to acknowledge the people responsible for the translation of the manual. Translation teams are advised to just mention the coordinator and maybe major contributors and thank everybody else in a phrase like \"all translators and reviewers from the translation team for {your language} at {your l10n mailinglist}\". See build/lang-options/README on how to enable this paragraph. Its condition is \"about-langteam\"."
+msgid ""
+"Translators can use this paragraph to acknowledge the people responsible for "
+"the translation of the manual. Translation teams are advised to just mention "
+"the coordinator and maybe major contributors and thank everybody else in a "
+"phrase like \"all translators and reviewers from the translation team for "
+"{your language} at {your l10n mailinglist}\". See build/lang-options/README "
+"on how to enable this paragraph. Its condition is \"about-langteam\"."
 msgstr ""
 
 #. Tag: title
@@ -58,19 +78,46 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:52
 #, no-c-format
-msgid "If you have problems or suggestions regarding this document, you should probably submit them as a bug report against the package <classname>installation-guide</classname>. See the <classname>reportbug</classname> package or read the online documentation of the <ulink url=\"&url-bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could check the <ulink url=\"&url-bts;installation-guide\">open bugs against installation-guide</ulink> to see whether your problem has already been reported. If so, you can supply additional corroboration or helpful information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, where <replaceable>XXXX</replaceable> is the number for the already-reported bug."
+msgid ""
+"If you have problems or suggestions regarding this document, you should "
+"probably submit them as a bug report against the package "
+"<classname>installation-guide</classname>. See the <classname>reportbug</"
+"classname> package or read the online documentation of the <ulink url=\"&url-"
+"bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could "
+"check the <ulink url=\"&url-bts;installation-guide\">open bugs against "
+"installation-guide</ulink> to see whether your problem has already been "
+"reported. If so, you can supply additional corroboration or helpful "
+"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</"
+"email>, where <replaceable>XXXX</replaceable> is the number for the already-"
+"reported bug."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:68
 #, no-c-format
-msgid "Better yet, get a copy of the DocBook source for this document, and produce patches against it. The DocBook source can be found at the <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with DocBook, don't worry: there is a simple cheatsheet in the manuals directory that will get you started. It's like html, but oriented towards the meaning of the text rather than the presentation. Patches submitted to the debian-boot mailing list (see below) are welcomed. For instructions on how to check out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> from the source root directory."
+msgid ""
+"Better yet, get a copy of the DocBook source for this document, and produce "
+"patches against it. The DocBook source can be found at the <ulink url=\"&url-"
+"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with "
+"DocBook, don't worry: there is a simple cheatsheet in the manuals directory "
+"that will get you started. It's like html, but oriented towards the meaning "
+"of the text rather than the presentation. Patches submitted to the debian-"
+"boot mailing list (see below) are welcomed. For instructions on how to check "
+"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> "
+"from the source root directory."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:82
 #, no-c-format
-msgid "Please do <emphasis>not</emphasis> contact the authors of this document directly. There is also a discussion list for &d-i;, which includes discussions of this manual. The mailing list is <email>debian-boot@lists.debian.org</email>. Instructions for subscribing to this list can be found at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online."
+msgid ""
+"Please do <emphasis>not</emphasis> contact the authors of this document "
+"directly. There is also a discussion list for &d-i;, which includes "
+"discussions of this manual. The mailing list is <email>debian-boot@lists."
+"debian.org</email>. Instructions for subscribing to this list can be found "
+"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List "
+"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-"
+"list-archives;\">Debian Mailing List Archives</ulink> online."
 msgstr ""
 
 #. Tag: title
@@ -82,37 +129,62 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:101
 #, no-c-format
-msgid "This document was originally written by Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the Installation Howto."
+msgid ""
+"This document was originally written by Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the "
+"Installation Howto."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:107
 #, no-c-format
-msgid "Miroslav Kuře has documented a lot of the new functionality in Sarge's debian-installer. Frans Pop was the main editor and release manager during the Etch, Lenny and Squeeze releases."
+msgid ""
+"Miroslav Kuře has documented a lot of the new functionality in Sarge's "
+"debian-installer. Frans Pop was the main editor and release manager during "
+"the Etch, Lenny and Squeeze releases."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:113
 #, no-c-format
-msgid "Many, many Debian users and developers contributed to this document. Particular note must be made of Michael Schmitz (m68k support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. We have to thank Pascal Le Bail for useful information about booting from USB memory sticks."
+msgid ""
+"Many, many Debian users and developers contributed to this document. "
+"Particular note must be made of Michael Schmitz (m68k support), Frank "
+"Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;"
+"\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins "
+"(SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous "
+"edits and text. We have to thank Pascal Le Bail for useful information about "
+"booting from USB memory sticks."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:124
 #, no-c-format
-msgid "Extremely helpful text and information was found in Jim Mintha's HOWTO for network booting (no URL available), the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, amongst others. The maintainers of these freely available and rich sources of information must be recognized."
+msgid ""
+"Extremely helpful text and information was found in Jim Mintha's HOWTO for "
+"network booting (no URL available), the <ulink url=\"&url-debian-faq;"
+"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors "
+"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, "
+"amongst others. The maintainers of these freely available and rich sources "
+"of information must be recognized."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:136
 #, no-c-format
-msgid "The section on chrooted installations in this manual (<xref linkend=\"linux-upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
+msgid ""
+"The section on chrooted installations in this manual (<xref linkend=\"linux-"
+"upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:142
 #, no-c-format
-msgid "The section on installations over plip in this manual (<xref linkend=\"plip\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> by Gilles Lamiral."
+msgid ""
+"The section on installations over plip in this manual (<xref linkend=\"plip"
+"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> by Gilles Lamiral."
 msgstr ""
 
 #. Tag: title
@@ -126,4 +198,3 @@ msgstr ""
 #, no-c-format
 msgid "All trademarks are property of their respective trademark owners."
 msgstr ""
-
diff --git a/po/nn/boot-installer.po b/po/nn/boot-installer.po
index 26928271b..9daaf7e68 100644
--- a/po/nn/boot-installer.po
+++ b/po/nn/boot-installer.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,21 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:15
 #, no-c-format
-msgid "If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly shut down <emphasis>before</emphasis> you boot the installer. Installing an operating system while another operating system is in hibernation (has been suspended to disk) could result in loss of, or damage to the state of the suspended operating system which could cause problems when it is rebooted."
+msgid ""
+"If you have any other operating systems on your system that you wish to keep "
+"(dual boot setup), you should make sure that they have been properly shut "
+"down <emphasis>before</emphasis> you boot the installer. Installing an "
+"operating system while another operating system is in hibernation (has been "
+"suspended to disk) could result in loss of, or damage to the state of the "
+"suspended operating system which could cause problems when it is rebooted."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:26
 #, no-c-format
-msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For information on how to boot the graphical installer, see <xref linkend="
+"\"graphical\"/>."
 msgstr ""
 
 #. Tag: title
@@ -44,21 +53,30 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
-msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
+msgid ""
+"Booting from the network requires that you have a network connection and a "
+"TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
-msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
+msgid ""
+"Older systems such as the 715 might require the use of an RBOOT server "
+"instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
-msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The installation method to support network booting is described in <xref "
+"linkend=\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -68,27 +86,47 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
-msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
+msgid ""
+"The easiest route for most people will be to use a set of &debian; CDs. If "
+"you have a CD set, and if your machine supports booting directly off the CD, "
+"great! Simply <phrase arch=\"x86\"> configure your system for booting off a "
+"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
+"your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
-msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
+msgid ""
+"Note that certain CD drives may require special drivers, and thus be "
+"inaccessible in the early installation stages. If it turns out the standard "
+"way of booting off a CD doesn't work for your hardware, revisit this chapter "
+"and read about alternate kernels and installation methods which may work for "
+"you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
-msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
+msgid ""
+"Even if you cannot boot from CD-ROM, you can probably install the &debian; "
+"system components and any packages you want from CD-ROM. Simply boot using a "
+"different media, such as floppies. When it's time to install the operating "
+"system, base system, and any additional packages, point the installation "
+"system at the CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
-msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
@@ -100,13 +138,20 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:113
 #, no-c-format
-msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines."
+msgid ""
+"There is an increasing number of consumer devices that directly boot from a "
+"flash chip on the device. The installer can be written to flash so it will "
+"automatically start when you reboot your machines."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:119
 #, no-c-format
-msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely."
+msgid ""
+"In many cases, changing the firmware of an embedded device voids your "
+"warranty. Sometimes you are also not able to recover your device if there "
+"are problems during the flashing process. Therefore, please take care and "
+"follow the steps precisely."
 msgstr ""
 
 #. Tag: title
@@ -118,13 +163,28 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:132
 #, no-c-format
-msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>."
+msgid ""
+"Due to limitations in the SS4000-E firmware, it unfortunately is not "
+"possible to boot the installer without the use of a serial port at this "
+"time. To boot the installer, you will need a serial nullmodem cable; a "
+"computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB "
+"serial converter will also work. </para> </footnote>; and a ribbon cable "
+"with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the "
+"other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older "
+"desktop machines with builtin 9-pin serial ports. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:153
 #, no-c-format
-msgid "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a &debian; GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:"
+msgid ""
+"To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable "
+"to connect to the serial port of the SS4000-E, and reboot the machine. You "
+"need to use a serial terminal application to communicate with the machine; a "
+"good option on a &debian; GNU/Linux is to use the <command>cu</command> "
+"program, in the package of the same name. Assuming the serial port on your "
+"computer is to be found on <filename>/dev/ttyS0</filename>, use the "
+"following command line:"
 msgstr ""
 
 #. Tag: screen
@@ -136,7 +196,10 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:167
 #, no-c-format
-msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit."
+msgid ""
+"If using Windows, you may want to consider using the program "
+"<classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word "
+"length, no stop bits, and one parity bit."
 msgstr ""
 
 #. Tag: para
@@ -149,63 +212,86 @@ msgstr ""
 #: boot-installer.xml:179
 #, no-c-format
 msgid ""
-      "No network interfaces found\n"
-      "\n"
-      "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
-      "== Executing boot script in 1.000 seconds - enter ^C to abort"
+"No network interfaces found\n"
+"\n"
+"EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
+"== Executing boot script in 1.000 seconds - enter ^C to abort"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:181
 #, no-c-format
-msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following commands:"
+msgid ""
+"At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-"
+"s4ke-sec\"> <para> Note that you have only one second to do so; if you miss "
+"this window, just powercycle the machine and try again. </para> </footnote>. "
+"This will give you the RedBoot prompt. Enter the following commands:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:194
 #, no-c-format
 msgid ""
-      "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
-      "load -v -r -b 0x01008000 -m ymodem zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
+"load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
+"load -v -r -b 0x01008000 -m ymodem zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:196
 #, no-c-format
-msgid "After every <command>load</command> command, the system will expect a file to be transmitted using the YMODEM protocol. When using cu, make sure you have the package <classname>lrzsz</classname> installed, then hit enter, followed by the <quote>~&lt;</quote> escape sequence to start an external program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</command>."
+msgid ""
+"After every <command>load</command> command, the system will expect a file "
+"to be transmitted using the YMODEM protocol. When using cu, make sure you "
+"have the package <classname>lrzsz</classname> installed, then hit enter, "
+"followed by the <quote>~&lt;</quote> escape sequence to start an external "
+"program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:205
 #, no-c-format
-msgid "Alternatively, it is possible to load the kernel and ramdisk using HTTP rather than YMODEM. This is faster, but requires a working HTTP server on the network. To do so, first switch the bootloader to RAM mode:"
+msgid ""
+"Alternatively, it is possible to load the kernel and ramdisk using HTTP "
+"rather than YMODEM. This is faster, but requires a working HTTP server on "
+"the network. To do so, first switch the bootloader to RAM mode:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:211
 #, no-c-format
 msgid ""
-      "fis load rammode\n"
-      "g"
+"fis load rammode\n"
+"g"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:213
 #, no-c-format
-msgid "This will seemingly restart the machine; but in reality, it loads redboot to RAM and restarts it from there. Not doing this step will cause the system to hang in the necessary ip_address step that comes next."
+msgid ""
+"This will seemingly restart the machine; but in reality, it loads redboot to "
+"RAM and restarts it from there. Not doing this step will cause the system to "
+"hang in the necessary ip_address step that comes next."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:219
 #, no-c-format
 msgid ""
-      "You will need to hit Ctrl-C again to interrupt the boot. Then: <informalexample><screen>\n"
-      "ip_address -l <replaceable>192.168.2.249</replaceable> -h <replaceable>192.168.2.4</replaceable>\n"
-      "load -v -r -b 0x01800000 -m http /initrd.gz\n"
-      "load -v -r -b 0x01008000 -m http /zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000\n"
-      "</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> is the IP address of the installed system and <replaceable>192.168.2.4</replaceable> the IP address of the HTTP server containing the kernel and ramdisk files."
+"You will need to hit Ctrl-C again to interrupt the boot. Then: "
+"<informalexample><screen>\n"
+"ip_address -l <replaceable>192.168.2.249</replaceable> -h "
+"<replaceable>192.168.2.4</replaceable>\n"
+"load -v -r -b 0x01800000 -m http /initrd.gz\n"
+"load -v -r -b 0x01008000 -m http /zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000\n"
+"</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> "
+"is the IP address of the installed system and <replaceable>192.168.2.4</"
+"replaceable> the IP address of the HTTP server containing the kernel and "
+"ramdisk files."
 msgstr ""
 
 #. Tag: para
@@ -215,7 +301,8 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -235,2042 +322,3004 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:355
 #, no-c-format
-msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+msgid ""
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
-msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
+msgid ""
+"download a standalone Windows executable, which is available as tools/win32-"
+"loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
-msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
+msgid ""
+"If you use an installation CD or DVD, a pre-installation program should be "
+"launched automatically when you insert the disc. In case Windows does not "
+"start it automatically, or if you are using a USB memory stick, you can run "
+"it manually by accessing the device and executing <command>setup.exe</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
-msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
+msgid ""
+"After the program has been started, a few preliminary questions will be "
+"asked and the system will be prepared to reboot into the &debian-gnu; "
+"installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
-msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
+msgid ""
+"Boot into DOS (not Windows). To do this, you can for instance boot from a "
+"recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
-      "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
-      "d:\n"
-      "</screen></informalexample> else make sure you have first prepared your hard disk as explained in <xref linkend=\"files-loadlin\"/>, and change the current drive to it if needed."
+"If you can access the installation CD, change the current drive to the CD-"
+"ROM drive, e.g. <informalexample><screen>\n"
+"d:\n"
+"</screen></informalexample> else make sure you have first prepared your hard "
+"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the "
+"current drive to it if needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
-      "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
-      "cd \\&x86-install-dir;\n"
-      "</screen></informalexample> If you prefer using the graphical installer, enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
-      "cd gtk\n"
-      "</screen></informalexample> Next, execute <command>install.bat</command>. The kernel will load and launch the installer system."
+"Enter the subdirectory for the flavor you chose, e.g., "
+"<informalexample><screen>\n"
+"cd \\&x86-install-dir;\n"
+"</screen></informalexample> If you prefer using the graphical installer, "
+"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
+"cd gtk\n"
+"</screen></informalexample> Next, execute <command>install.bat</command>. "
+"The kernel will load and launch the installer system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
-msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
-msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you must first download and place the "
+"needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
-msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
+msgid ""
+"If you intend to use the hard drive only for booting and then download "
+"everything over the network, you should download the <filename>netboot/"
+"debian-installer/&architecture;/initrd.gz</filename> file and its "
+"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
+"linux</filename>. This will allow you to repartition the hard disk from "
+"which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
-msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
+msgid ""
+"Alternatively, if you intend to keep an existing partition on the hard drive "
+"unchanged during the install, you can download the <filename>hd-media/initrd."
+"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
+"drive (make sure the file is named ending in <literal>.iso</literal>). The "
+"installer can then boot from the drive and install from the CD/DVD image, "
+"without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
-msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
+msgid ""
+"For <command>LILO</command>, you will need to configure two essential things "
+"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
+"load the <filename>initrd.gz</filename> installer at boot time; </para></"
+"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
+"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
+"a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
-      "image=/boot/newinstall/vmlinuz\n"
-      "       label=newinstall\n"
-      "       initrd=/boot/newinstall/initrd.gz"
+"image=/boot/newinstall/vmlinuz\n"
+"       label=newinstall\n"
+"       initrd=/boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
-msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
+msgid ""
+"For more details, refer to the <citerefentry><refentrytitle>initrd</"
+"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
+"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
+"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
+"reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
-msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
+msgid ""
+"The procedure for <command>GRUB1</command> is quite similar. Locate your "
+"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
+"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
+"entry for the installer, for example (assuming <filename>/boot</filename> is "
+"on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
-      "title  New Install\n"
-      "root   (hd0,0)\n"
-      "kernel /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz"
+"title  New Install\n"
+"root   (hd0,0)\n"
+"kernel /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
-msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
+msgid ""
+"The procedure for <command>GRUB2</command> is very similar. The file is "
+"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
+"filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
-      "menuentry 'New Install' {\n"
-      "insmod part_msdos\n"
-      "insmod ext2\n"
-      "set root='(hd0,msdos1)'\n"
-      "linux /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz\n"
-      "}"
+"menuentry 'New Install' {\n"
+"insmod part_msdos\n"
+"insmod ext2\n"
+"set root='(hd0,msdos1)'\n"
+"linux /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz\n"
+"}"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
-msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
+msgid ""
+"From here on, there should be no difference between <command>GRUB</command> "
+"or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
-msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
+"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
+"stick into some free USB connector and reboot the computer. The system "
+"should boot up, and unless you have used the flexible way to build the stick "
+"and not enabled it, you should be presented with the <prompt>boot:</prompt> "
+"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
-msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
+msgid ""
+"You will have already downloaded the floppy images you needed and created "
+"floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
-msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
+msgid ""
+"To boot from the installer boot floppy, place it in the primary floppy "
+"drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
-msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
+msgid ""
+"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
+"you need to specify the virtual location for the floppy device. This is done "
+"with the <emphasis>root=</emphasis> boot argument, giving the device that "
+"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
+"is connected as the first IDE device (master) on the second cable, you enter "
+"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
-msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
+msgid ""
+"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
+"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
+"machine, so a <quote>hard</quote> reboot is recommended. If you are "
+"installing from an existing operating system (e.g., from a DOS box) you "
+"don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
-msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
+msgid ""
+"The floppy disk will be accessed, and you should then see a screen that "
+"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
-msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
+msgid ""
+"Once you press &enterkey;, you should see the message "
+"<computeroutput>Loading...</computeroutput>, followed by "
+"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
+"screenfull or so of information about the hardware in your system. More "
+"information on this phase of the boot process can be found below in <xref "
+"linkend=\"kernel-msgs\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
-msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
+msgid ""
+"After booting from the boot floppy, the root floppy is requested. Insert the "
+"root floppy and press &enterkey;, and the contents are loaded into memory. "
+"The installer program <command>debian-installer</command> is automatically "
+"launched."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
-msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
+msgid ""
+"It could be that your Network Interface Card or Motherboard provides PXE "
+"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
+"re-implementation of TFTP boot. If so, you may be able to configure your "
+"BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
-msgid "It could be that your Network Interface Card provides TFTP boot functionality."
+msgid ""
+"It could be that your Network Interface Card provides TFTP boot "
+"functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
-msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
+msgid ""
+"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
+"Please refer to this document."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
-msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
+msgid ""
+"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
+"provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
-      "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
-      "Installer boot menu\n"
-      "\n"
-      "Install\n"
-      "Graphical install\n"
-      "Advanced options             >\n"
-      "Help\n"
-      "Install with speech synthesis\n"
-      "\n"
-      "Press ENTER to boot or TAB to edit a menu entry\n"
-      "</screen></informalexample> Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:658
+"When the installer boots, you should be presented with a friendly graphical "
+"screen showing the &debian; logo and a menu: <informalexample><screen>\n"
+"Installer boot menu\n"
+"\n"
+"Install\n"
+"Graphical install\n"
+"Advanced options             >\n"
+"Help\n"
+"Install with speech synthesis\n"
+"\n"
+"Press ENTER to boot or TAB to edit a menu entry\n"
+"</screen></informalexample> Depending on the installation method you are "
+"using, the <quote>Graphical install</quote> option may not be available. Bi-"
+"arch images additionally have a 64 bit variant for each install option, "
+"right below it, thus almost doubling the number of options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:660
 #, no-c-format
-msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
+msgid ""
+"For a normal installation, select either the <quote>Install</quote> or the "
+"<quote>Graphical install</quote> entry &mdash; using either the arrow keys "
+"on your keyboard or by typing the first (highlighted) letter, the "
+"<quote>Install</quote> entry is already selected by default &mdash; and "
+"press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
-msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
+msgid ""
+"The <quote>Advanced options</quote> entry gives access to a second menu that "
+"allows to boot the installer in expert mode, in rescue mode and for "
+"automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
-msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
+msgid ""
+"If you wish or need to add any boot parameters for either the installer or "
+"the kernel, press &tabkey;. This will display the default boot command for "
+"the selected menu entry and allow to add additional options. The help "
+"screens (see below) list some common possible options. Press &enterkey; to "
+"boot the installer with your options; pressing &escapekey; will return you "
+"to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
-      "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
-      "Press F1 for the help index, or ENTER to boot:\n"
-      "</screen></informalexample> At this boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot command and, optionally, boot parameters. A number of boot parameters which might be useful can be found on the various help screens. If you do add any parameters to the boot command line, be sure to first type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)."
+"Choosing the <quote>Help</quote> entry will result in the first help screen "
+"being displayed which gives an overview of all available help screens. To "
+"return to the boot menu after the help screens have been displayed, type "
+"'menu' at the boot prompt and press &enterkey;. All help screens have a boot "
+"prompt at which the boot command can be typed: <informalexample><screen>\n"
+"Press F1 for the help index, or ENTER to boot:\n"
+"</screen></informalexample> At this boot prompt you can either just press "
+"&enterkey; to boot the installer with default options or enter a specific "
+"boot command and, optionally, boot parameters. A number of boot parameters "
+"which might be useful can be found on the various help screens. If you do "
+"add any parameters to the boot command line, be sure to first type the boot "
+"method (the default is <userinput>install</userinput>) and a space before "
+"the first parameter (e.g., <userinput>install fb=false</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
-msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
+msgid ""
+"The keyboard is assumed to have a default American English layout at this "
+"point. This means that if your keyboard has a different (language-specific) "
+"layout, the characters that appear on the screen may be different from what "
+"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-"
+"keymap;\">schema of the US keyboard layout</ulink> which can be used as a "
+"reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
-msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
+msgid ""
+"If you are using a system that has the BIOS configured to use serial "
+"console, you may not be able to see the initial graphical splash screen upon "
+"booting the installer; you may even not see the boot menu. The same can "
+"happen if you are installing the system via a remote management device that "
+"provides a text interface to the VGA console. Examples of these devices "
+"include the text console of Compaq's <quote>integrated Lights Out</quote> "
+"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
-msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
+msgid ""
+"To bypass the graphical boot screen you can either blindly press &escapekey; "
+"to get a text boot prompt, or (equally blindly) press <quote>H</quote> "
+"followed by &enterkey; to select the <quote>Help</quote> option described "
+"above. After that your keystrokes should be echoed at the prompt. To prevent "
+"the installer from using the framebuffer for the rest of the installation, "
+"you will also want to add <userinput>vga=normal fb=false</userinput> to the "
+"boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
-msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network."
+msgid ""
+"There are three basic variations of &debian; Install CDs. The "
+"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
+"fit on the small form factor CD media. It requires a network connection in "
+"order to install the rest of the base installation and make a usable system. "
+"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
+"base install but requires a network connection to a &debian; mirror site in "
+"order to install the extra packages one would want for a complete system . "
+"The set of &debian; CDs can install a complete system from the wide range of "
+"packages without needing access to the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
-msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
+msgid ""
+"The IA-64 architecture uses the next generation Extensible Firmware "
+"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows "
+"little about the boot device other than the partition table and Master Boot "
+"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted "
+"disk partitions. This simplifies the often arcane process of starting a "
+"system. The system boot loader and the EFI firmware that supports it have a "
+"full filesystem to store the files necessary for booting the machine. This "
+"means that the system disk on an IA-64 system has an additional disk "
+"partition dedicated to EFI instead of the simple MBR or boot block on more "
+"conventional systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
-msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
+msgid ""
+"The &debian; Installer CD contains a small EFI partition where the "
+"<command>ELILO</command> bootloader, its configuration file, the installer's "
+"kernel, and initial filesystem (initrd) are located. The running system also "
+"contains an EFI partition where the necessary files for booting the system "
+"reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
-msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
+msgid ""
+"Most of the details of how <command>ELILO</command> actually loads and "
+"starts a system are transparent to the system installer. However, the "
+"installer must set up an EFI partition prior to installing the base system. "
+"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
+"the system un-bootable. The EFI partition is allocated and formatted in the "
+"partitioning step of the installation prior to loading any packages on the "
+"system disk. The partitioning task also verifies that a suitable EFI "
+"partition is present before allowing the installation to proceed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
-msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
+msgid ""
+"The EFI Boot Manager is presented as the last step of the firmware "
+"initialization. It displays a menu list from which the user can select an "
+"option. Depending on the model of system and what other software has been "
+"loaded on the system, this menu may be different from one system to another. "
+"There should be at least two menu items displayed, <command>Boot Option "
+"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
+"Using the first option is preferred, however, if that option is not "
+"available or the CD for some reason does not boot with it, use the second "
+"option."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
-msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
+msgid ""
+"The EFI Boot Manager will select a default boot action, typically the first "
+"menu choice, within a pre-set number of seconds. This is indicated by a "
+"countdown at the bottom of the screen. Once the timer expires and the "
+"systems starts the default action, you may have to reboot the machine in "
+"order to continue the installation. If the default action is the EFI Shell, "
+"you can return to the Boot Manager by running <command>exit</command> at the "
+"shell prompt."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes its system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
-msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
+msgid ""
+"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
+"keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
-msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
+msgid ""
+"Select <command>Boot From a File</command> from the menu with the arrow keys "
+"and press <command>ENTER</command>. This will display a list of devices "
+"probed by the firmware. You should see two menu lines containing either the "
+"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
+"Boot</command>. If you examine the rest of the menu line, you will notice "
+"that the device and controller information should be the same."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
-msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
+msgid ""
+"You can choose either of the entries that refer to the CD/DVD drive. Select "
+"your choice with the arrow keys and press <command>ENTER</command>. If you "
+"choose <command>Removable Media Boot</command> the machine will immediately "
+"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
+"command> instead, it will display a directory listing of the bootable "
+"portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
-msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
+"command>. The directory listing will also show <command>[Treat like "
+"Removable Media Boot]</command> on the next to the last line. Select this "
+"line with the arrow keys and press <command>ENTER</command>. This will start "
+"the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
-msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
+msgid ""
+"These steps start the &debian; boot loader which will display a menu page "
+"for you to select a boot kernel and options. Proceed to selecting the boot "
+"kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
-msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:"
+msgid ""
+"If, for some reason, option 1 is not successful, reboot the machine and when "
+"the EFI Boot Manager screen appears there should be one option called "
+"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with "
+"the following steps:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
-msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
+msgid ""
+"Select <command>EFI Shell</command> from the menu with the arrow keys and "
+"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
+"devices and display them to the console before displaying its command "
+"prompt. The recognized bootable partitions on devices will show a device "
+"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
+"recognized partitions will be named <filename>blk<replaceable>n</"
+"replaceable>:</filename>. If you inserted the CD just before entering the "
+"shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
-msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
+msgid ""
+"Examine the output from the shell looking for the CDROM drive. It is most "
+"likely the <filename>fs0:</filename> device although other devices with "
+"bootable partitions will also show up as <filename>fs<replaceable>n</"
+"replaceable></filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
-msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
+msgid ""
+"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
+"<command>ENTER</command> to select that device where <replaceable>n</"
+"replaceable> is the partition number for the CDROM. The shell will now "
+"display the partition number as its prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
-msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
+"start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
-msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
+msgid ""
+"As with option 1, these steps start the &debian; boot loader which will "
+"display a menu page for you to select a boot kernel and options. You can "
+"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
+"command> command at the shell prompt. Proceed to selecting the boot kernel "
+"and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
-msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
+msgid ""
+"You may choose to perform an install using a monitor and keyboard or using a "
+"serial connection. To use a monitor/keyboard setup, select an option "
+"containing the string [VGA console]. To install over a serial connection, "
+"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
+"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
+"serial console. Menu items for the most typical baud rate settings on the "
+"ttyS0 device are preconfigured."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
-msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
+msgid ""
+"In most circumstances, you will want the installer to use the same baud rate "
+"as your connection to the EFI console. If you aren't sure what this setting "
+"is, you can obtain it using the command <command>baud</command> at the EFI "
+"shell."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
-msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
+msgid ""
+"If there is not an option available that is configured for the serial device "
+"or baud rate you would like to use, you may override the console setting for "
+"one of the existing menu options. For example, to use a 57600 baud console "
+"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
+"the <classname>Boot:</classname> text window."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
-msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
+msgid ""
+"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
+"setting is rather slow, and the normal installation process will take a "
+"significant time to draw each screen. You should consider either increasing "
+"the baud rate used for performing the installation, or performing a Text "
+"Mode installation. See the <classname>Params</classname> help menu for "
+"instructions on starting the installer in Text Mode."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
-msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
+msgid ""
+"If you select the wrong console type, you will be able to select the kernel "
+"and enter parameters but both the display and your input will go dead as "
+"soon as the kernel starts, requiring you to reboot before you can begin the "
+"installation."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
-msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
+msgid ""
+"The boot loader will display a form with a menu list and a text window with "
+"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
+"the menu and any text typed at the keyboard will appear in the text window. "
+"There are also help screens which can be displayed by pressing the "
+"appropriate function key. The <classname>General</classname> help screen "
+"explains the menu choices and the <classname>Params</classname> screen "
+"explains the common command line options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
-msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
+msgid ""
+"Consult the <classname>General</classname> help screen for the description "
+"of the kernels and install modes most appropriate for your installation. You "
+"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
+"parameters that you may want to set in the <classname>Boot:</classname> text "
+"window. The kernel version you choose selects the kernel version that will "
+"be used for both the installation process and the installed system. If you "
+"encounter kernel problems with the installation, you may also have those "
+"same problems with the system you install. The following two steps will "
+"select and start the install:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
-msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
+msgid ""
+"Select the kernel version and installation mode most appropriate to your "
+"needs with the arrow keys."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
-msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
+msgid ""
+"Enter any boot parameters by typing at the keyboard. The text will be "
+"displayed directly in the text window. This is where kernel parameters (such "
+"as serial console settings) are specified."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
-msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer."
+msgid ""
+"Press <command>ENTER</command>. This will load and start the kernel. The "
+"kernel will display its usual initialization messages followed by the first "
+"screen of the &debian; Installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
-msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
+msgid ""
+"Proceed to the next chapter to continue the installation where you will set "
+"up the language locale, network, and disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
-msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
+msgid ""
+"Booting an IA-64 system from the network is similar to a CD boot. The only "
+"difference is how the installation kernel is loaded. The EFI Boot Manager "
+"can load and start programs from a server on the network. Once the "
+"installation kernel is loaded and starts, the system install will proceed "
+"through the same steps as the CD install with the exception that the "
+"packages of the base install will be loaded from the network rather than the "
+"CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
-msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
+msgid ""
+"Network booting an IA-64 system requires two architecture-specific actions. "
+"On the boot server, DHCP and TFTP must be configured to deliver "
+"<command>elilo</command>. On the client a new boot option must be defined in "
+"the EFI boot manager to enable loading over a network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
-      "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
-      "host mcmuffin {\n"
-      "        hardware ethernet 00:30:6e:1e:0e:83;\n"
-      "        fixed-address 10.0.0.21;\n"
-      "        filename \"debian-installer/ia64/elilo.efi\";\n"
-      "}\n"
-      "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
+"A suitable TFTP entry for network booting an IA-64 system looks something "
+"like this: <informalexample><screen>\n"
+"host mcmuffin {\n"
+"        hardware ethernet 00:30:6e:1e:0e:83;\n"
+"        fixed-address 10.0.0.21;\n"
+"        filename \"debian-installer/ia64/elilo.efi\";\n"
+"}\n"
+"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
+"command> running on the client."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
-msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
+msgid ""
+"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
+"as the root for your tftp server. Typical tftp root directories include "
+"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
+"will create a <filename>debian-installer</filename> directory tree "
+"containing the boot files for an IA-64 system."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
-      "# cd /var/lib/tftp\n"
-      "# tar xvfz /home/user/netboot.tar.gz\n"
-      "./\n"
-      "./debian-installer/\n"
-      "./debian-installer/ia64/\n"
-      "[...]"
+"# cd /var/lib/tftp\n"
+"# tar xvfz /home/user/netboot.tar.gz\n"
+"./\n"
+"./debian-installer/\n"
+"./debian-installer/ia64/\n"
+"[...]"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
-msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
+msgid ""
+"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
+"filename> file that should work for most configurations. However, should you "
+"need to make changes to this file, you can find it in the <filename>debian-"
+"installer/ia64/</filename> directory. It is possible to have different "
+"config files for different clients by naming them using the client's IP "
+"address in hex with the suffix <filename>.conf</filename> instead of "
+"<filename>elilo.conf</filename>. See documentation provided in the "
+"<classname>elilo</classname> package for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
-msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
+msgid ""
+"To configure the client to support TFTP booting, start by booting to EFI and "
+"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
+"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
+"should see one or more lines with the text <guimenuitem>Load File [Acpi"
+"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose "
+"the one containing the MAC address of the interface from which you'll be "
+"booting. Use the arrow keys to highlight your choice, then press enter. </"
+"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
+"userinput> or something similar, save, and exit back to the boot options "
+"menu. </para></listitem> </itemizedlist> You should see the new boot option "
+"you just created, and selecting it should initiate a DHCP query, leading to "
+"a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
-msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer."
+msgid ""
+"The boot loader will display its prompt after it has downloaded and "
+"processed its configuration file. At this point, the installation proceeds "
+"with the same steps as a CD install. Select a boot option as in above and "
+"when the kernel has completed installing itself from the network, it will "
+"start the &debian; Installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
-      "After entering the command monitor use <informalexample><screen>\n"
-      "bootp():\n"
-      "</screen></informalexample> on SGI machines to boot linux and to begin installation of the &debian; Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n"
-      "unsetenv netaddr\n"
-      "</screen></informalexample> in the command monitor to do this."
+"After entering the command monitor use <informalexample><screen>\n"
+"bootp():\n"
+"</screen></informalexample> on SGI machines to boot linux and to begin "
+"installation of the &debian; Software. In order to make this work you may "
+"have to unset the <envar>netaddr</envar> environment variable. Type "
+"<informalexample><screen>\n"
+"unsetenv netaddr\n"
+"</screen></informalexample> in the command monitor to do this."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
-msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
+msgid ""
+"On SGI machines you can append boot parameters to the <command>bootp():</"
+"command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
-      "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
-      "bootp():/boot/tftpboot.img\n"
-      "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
+"Following the <command>bootp():</command> command you can give the path and "
+"name of the file to boot if you did not give an explicit name via your bootp/"
+"dhcp server. Example: <informalexample><screen>\n"
+"bootp():/boot/tftpboot.img\n"
+"</screen></informalexample> Further kernel parameters can be passed via "
+"<command>append</command>:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
-msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
+msgid ""
+"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
+"install an NFS server and put the installer files in <filename>/nfsroot</"
+"filename>. When you boot your Cobalt, you have to press the left and the "
+"right cursor buttons at the same time and the machine will boot via the "
+"network from NFS. It will then display several options on the display. There "
+"are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
-msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
+msgid ""
+"Via SSH (default): In this case, the installer will configure the network "
+"via DHCP and start an SSH server. It will then display a random password and "
+"other login information (such as the IP address) on the Cobalt LCD. When you "
+"connect to the machine with an SSH client you can start with the "
+"installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
-msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
+msgid ""
+"Via serial console: Using a null modem cable, you can connect to the serial "
+"port of your Cobalt machine (using 115200 bps) and perform the installation "
+"this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
-msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
+msgid ""
+"You cannot pass any boot parameters directly. Instead, you have to edit the "
+"<filename>/nfsroot/default.colo</filename> file on the NFS server and add "
+"your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
-msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
+msgid ""
+"In order to run the installation system a working network setup and ssh "
+"session is needed on S/390."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
-msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
+msgid ""
+"The booting process starts with a network setup that prompts you for several "
+"network parameters. If the setup is successful, you will login to the system "
+"by starting an ssh session which will launch the standard installation "
+"system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
-msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
+msgid ""
+"On S/390 you can append boot parameters in the parm file. This file can "
+"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
+"debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
-msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive."
+msgid ""
+"Currently, the only &arch-title; subarchitectures that support CD-ROM "
+"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
+"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
+"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
+"and <keycap>Delete</keycap> keys together while booting to boot from the "
+"factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
-      "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
-      "0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
-      "</screen></informalexample> for an alternative way to boot from the internal factory default CD/DVD drive type"
+"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
+"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
+"type <informalexample><screen>\n"
+"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
+"</screen></informalexample> for an alternative way to boot from the internal "
+"factory default CD/DVD drive type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
-msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
+msgid ""
+"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
+"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
+"software version of this driver is not available. All OldWorld systems have "
+"floppy drives, so use the floppy drive to launch the installer, and then "
+"point the installer to the CD for the needed files."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
-msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
+msgid ""
+"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
+"immediately after pressing the power-on button, when SmartFirmware prompt "
+"appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
-msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
+msgid ""
+"Booting from an existing operating system is often a convenient option; for "
+"some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
-msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you will have already completed "
+"downloading and placing the needed files as described in <xref linkend="
+"\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
-msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
+msgid ""
+"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
+"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
+"application icon. Click on the <guibutton>Options</guibutton> button and "
+"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
+"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
+"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
+"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
+"down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
-      "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
-      "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
-      "</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n"
-      "boot:\n"
-      "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The &debian; installation program should start."
+"You will have already placed the <filename>vmlinux</filename>, "
+"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
+"<filename>yaboot.conf</filename> files at the root level of your HFS "
+"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
+"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
+"prompt, type <informalexample><screen>\n"
+"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
+"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
+"partition number of the HFS partition where the kernel and yaboot files were "
+"placed, followed by a &enterkey;. On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
+"more seconds you will see a yaboot prompt <informalexample><screen>\n"
+"boot:\n"
+"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
+"either <userinput>install</userinput> or <userinput>install video=ofonly</"
+"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
+"argument is for maximum compatibility; you can try it if <userinput>install</"
+"userinput> doesn't work. The &debian; installation program should start."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
-msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
+msgid ""
+"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
+">. To boot a Macintosh system from a USB stick, you will need to use the "
+"Open Firmware prompt, since Open Firmware does not search USB storage "
+"devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
-msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
+msgid ""
+"You will need to work out where the USB storage device appears in the device "
+"tree, since at the moment <command>ofpath</command> cannot work that out "
+"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
+"userinput> at the Open Firmware prompt to get a list of all known devices "
+"and device aliases. On the author's system with various types of USB stick, "
+"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
+"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
+"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
-      "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
-      "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n"
-      "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
+"Having worked out the device path, use a command like this to boot the "
+"installer: <informalexample><screen>\n"
+"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
+"tbxi\n"
+"</screen></informalexample> The <replaceable>2</replaceable> matches the "
+"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
+"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
+"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
+"<command>yaboot</command>) in the directory previously blessed with "
+"<command>hattrib -b</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
-msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"The system should now boot up, and you should be presented with the "
+"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
+"or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
-msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
+msgid ""
+"This boot method is new, and may be difficult to get to work on some "
+"NewWorld systems. If you have problems, please file an installation report, "
+"as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
-      "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
-      "0 &gt; boot enet:0\n"
-      "</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>\n"
-      "0 &gt; boot enet:0,yaboot\n"
-      "</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>\n"
-      "boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>\n"
-      "</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:1676
+"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
+"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
+"<informalexample><screen>\n"
+"0 &gt; boot enet:0\n"
+"</screen></informalexample> If this doesn't work, you might have to add the "
+"filename like this: <informalexample><screen>\n"
+"0 &gt; boot enet:0,yaboot\n"
+"</screen></informalexample> PReP and CHRP boxes may have different ways of "
+"addressing the network. On a PReP machine, you should try "
+"<informalexample><screen>\n"
+"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
+"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
+"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
+"machines) the command <userinput>help boot</userinput> may give a "
+"description of syntax and available options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:1678
 #, no-c-format
-msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
+msgid ""
+"Booting from floppies is supported for &arch-title;, although it is "
+"generally only applicable for OldWorld systems. NewWorld systems are not "
+"equipped with floppy drives, and attached USB floppy drives are not "
+"supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
-msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
+msgid ""
+"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
+"in floppy drive after shutting the system down, and before pressing the "
+"power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
-msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
+msgid ""
+"For those not familiar with Macintosh floppy operations: a floppy placed in "
+"the machine prior to boot will be the first priority for the system to boot "
+"from. A floppy without a valid boot system will be ejected, and the machine "
+"will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
-msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
+msgid ""
+"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
+"the root floppy and press &enterkey;. The installer program is automatically "
+"launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
-msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
+msgid ""
+"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
+"skewed on an older Apple monitor, try appending the boot argument "
+"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
+"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
+"<userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
-msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
+msgid ""
+"On machines with OpenBoot, simply enter the boot monitor on the machine "
+"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
+"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
+"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
+"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
+"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
-msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
+msgid ""
+"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
+"which is simply an alias to boot from the SCSI device on ID 6 (or the "
+"secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
-msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
+msgid ""
+"If you cannot boot because you get messages about a problem with "
+"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
+"holds configuration information for you firmware, has run out. See the "
+"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
+"information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
-msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
+msgid ""
+"Some users may need specific support because of e.g. some visual impairment. "
+"<phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected "
+"automatically (not serial displays connected via a serial-to-USB converter), "
+"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</"
+"phrase> accessibility features have to be enabled manually. <phrase arch="
+"\"x86\">On machines that support it, the boot menu emits a beep when it is "
+"ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch="
+"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
+"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that "
+"on most architectures the boot loader interprets your keyboard as a QWERTY "
+"keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
-msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"USB braille displays should be automatically detected. A textual version of "
+"the installer will then be automatically selected, and support for the "
+"braille display will be automatically installed on the target system. You "
+"can thus just press &enterkey; at the boot menu. Once <classname>brltty</"
+"classname> is started, you can choose a braille table by entering the "
+"preference menu. Documentation on key bindings for braille devices is "
+"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
+"classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
-msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"Serial braille displays cannot safely be automatically detected (since that "
+"may damage some of them). You thus need to append the "
+"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
+"replaceable>,<replaceable>table</replaceable></userinput> boot parameter to "
+"tell <classname>brltty</classname> which driver it should use. "
+"<replaceable>driver</replaceable> should be replaced by the two-letter "
+"driver code for your terminal (see the <ulink url=\"&url-brltty-manual;"
+"\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be "
+"replaced by the name of the serial port the display is connected to, "
+"<userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> "
+"can be typically used when using a serial-to-USB converter. "
+"<replaceable>table</replaceable> is the name of the braille table to be used "
+"(see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the "
+"English table is the default. Note that the table can be changed later by "
+"entering the preference menu. Documentation on key bindings for braille "
+"devices is available on the <ulink url=\"&url-brltty-driver-help;"
+"\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
-msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
+msgid ""
+"Support for software speech synthesis can be activated by selecting it in "
+"the boot menu by typing <userinput>s</userinput> &enterkey;. The first "
+"question (language) is spoken in english, and the remainder of installation "
+"is spoken in the selected language (if available in <classname>espeak</"
+"classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
+msgid ""
+"Support for hardware speech synthesis devices is available only alongside "
+"support for graphical installer. You thus need to select a <quote>Graphical "
+"install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
-msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
+msgid ""
+"Hardware speech synthesis devices cannot be automatically detected. You thus "
+"need to append the <userinput>speakup.synth=<replaceable>driver</"
+"replaceable></userinput> boot parameter to tell <classname>speakup</"
+"classname> which driver it should use. <replaceable>driver</replaceable> "
+"should be replaced by the driver code for your device (see <ulink url=\"&url-"
+"speakup-driver-codes;\">driver code list</ulink>). The textual version of "
+"the installer will then be automatically selected, and support for the "
+"speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
-msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
+msgid ""
+"Some accessibility devices are actual boards that are plugged inside the "
+"machine and that read text directly from the video memory. To get them to "
+"work framebuffer support must be disabled by using the <userinput arch="
+"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot "
+"parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
-msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
+msgid ""
+"If desired a textual version of the bootloader can be activated before "
+"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
-msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
+msgid ""
+"For users with low vision, the installer can use a high-contrast theme that "
+"makes it more readable. To enable it, append the <userinput>theme=dark</"
+"userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
-msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Alternatively, &debian; can be installed completely automatically by using "
+"preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
-msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
+msgid ""
+"Boot parameters are Linux kernel parameters which are generally used to make "
+"sure that peripherals are dealt with properly. For the most part, the kernel "
+"can auto-detect information about your peripherals. However, in some cases "
+"you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
-msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
+msgid ""
+"If this is the first time you're booting the system, try the default boot "
+"parameters (i.e., don't try setting parameters) and see if it works "
+"correctly. It probably will. If not, you can reboot later and look for any "
+"special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
-msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"Information on many boot parameters can be found in the <ulink url=\"http://"
+"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
+"including tips for obscure hardware. This section contains only a sketch of "
+"the most salient parameters. Some common gotchas are included below in <xref "
+"linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
-msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
+msgid ""
+"If you are booting with a serial console, generally the kernel will "
+"autodetect this. If you have a videocard (framebuffer) and a keyboard also "
+"attached to the computer which you wish to boot via serial console, you may "
+"have to pass the <userinput>console=<replaceable>device</replaceable></"
+"userinput> argument to the kernel, where <replaceable>device</replaceable> "
+"is your serial device, which is usually something like <filename>ttyS0</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
-msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
+msgid ""
+"In order to ensure the terminal type used by the installer matches your "
+"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
+"replaceable></userinput> can be added. Note that the installer only supports "
+"the following terminal types: <literal>linux</literal>, <literal>bterm</"
+"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
+"<literal>dumb</literal>. The default for serial console in &d-i; is "
+"<userinput>vt102</userinput>. If you are using a virtualization tool which "
+"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, "
+"you can start it inside a <command>screen</command> session. That will "
+"indeed perform translation into the <literal>screen</literal> terminal type, "
+"which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
-msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
+msgid ""
+"For &arch-title; the serial devices are <filename>ttya</filename> or "
+"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
+"envar> and <envar>output-device</envar> OpenPROM variables to "
+"<filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
+msgid ""
+"The installation system recognizes a few additional boot "
+"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
+"use 32 command line options and 32 environment options. If these numbers are "
+"exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
-msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
+msgid ""
+"A number of parameters have a <quote>short form</quote> that helps avoid the "
+"limitations of the kernel command line options and makes entering the "
+"parameters easier. If a parameter has a short form, it will be listed in "
+"brackets behind the (normal) long form. Examples in this manual will "
+"normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
-msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
+msgid ""
+"The default installation uses <userinput>priority=high</userinput>. This "
+"means that both high and critical priority messages are shown, but medium "
+"and low priority messages are skipped. If problems are encountered, the "
+"installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
-msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
+msgid ""
+"If you add <userinput>priority=medium</userinput> as boot parameter, you "
+"will be shown the installation menu and gain more control over the "
+"installation. When <userinput>priority=low</userinput> is used, all messages "
+"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
+"method). With <userinput>priority=critical</userinput>, the installation "
+"system will display only critical messages and try to do the right thing "
+"without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
-msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
+msgid ""
+"This boot parameter controls the type of user interface used for the "
+"installer. The current possible parameter settings are: <itemizedlist> "
+"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
+"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
+"userinput></para> </listitem><listitem> "
+"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
+"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
+"</listitem> </itemizedlist> The default frontend is "
+"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
+"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
+"console installs. Some specialized types of install media may only offer a "
+"limited selection of frontends, but the <userinput>newt</userinput> and "
+"<userinput>text</userinput> frontends are available on most default install "
+"media. On architectures that support it, the graphical installer uses the "
+"<userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
-msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
+msgid ""
+"Setting this boot parameter to 2 will cause the installer's boot process to "
+"be verbosely logged. Setting it to 3 makes debug shells available at "
+"strategic points in the boot process. (Exit the shells to continue the boot "
+"process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
-msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
+msgid ""
+"Shells are run at various points in the boot process to allow detailed "
+"debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
-msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
+msgid ""
+"The value of the parameter is the path to the device to load the &debian; "
+"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
+"userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
-msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
+msgid ""
+"The boot floppy, which normally scans all floppies it can to find the root "
+"floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
-msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
+msgid ""
+"Causes the installer to send log messages to a remote syslog on the "
+"specified host and port as well as to a local file. If not specified, the "
+"port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
-msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
+msgid ""
+"Can be used to force the installer to a lowmem level higher than the one the "
+"installer sets by default based on available memory. Possible values are 1 "
+"and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
-msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
+msgid ""
+"Prevents the installer from offering interactive shells on tty2 and tty3. "
+"Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
-msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
+msgid ""
+"Some architectures use the kernel framebuffer to offer installation in a "
+"number of languages. If framebuffer causes a problem on your system you can "
+"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</"
+"userinput> <userinput>fb=false</userinput>. Problem symptoms are error "
+"messages about bterm or bogl, a blank screen, or a freeze within a few "
+"minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
-msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
+msgid ""
+"Because of display problems on some systems, framebuffer support is "
+"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
+"in ugly display on systems that do properly support the framebuffer, like "
+"those with ATI graphical cards. If you see display problems in the "
+"installer, you can try booting with parameter <userinput>debian-installer/"
+"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
-msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
+msgid ""
+"A theme determines how the user interface of the installer looks (colors, "
+"icons, etc.). What themes are available differs per frontend. Currently both "
+"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
+"designed for visually impaired users. Set the theme by booting with "
+"<userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
-msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
+msgid ""
+"By default, the &d-i; automatically probes for network configuration via "
+"DHCP. If the probe succeeds, you won't have a chance to review and change "
+"the obtained settings. You can get to the manual network setup only in case "
+"the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
-msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
+msgid ""
+"If you have a DHCP server on your local network, but want to avoid it "
+"because e.g. it gives wrong answers, you can use the parameter "
+"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
+"network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
+msgid ""
+"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
+"that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
+msgid ""
+"Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
+"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note "
+"that this support is currently experimental. Additional information can be "
+"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
-msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the url to a preconfiguration file to download and use for "
+"automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
-msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the path to a preconfiguration file to load for automating the "
+"install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
+msgid ""
+"Set to <userinput>true</userinput> to display questions even if they have "
+"been preseeded. Can be useful for testing or debugging a preconfiguration "
+"file. Note that this will have no effect on parameters that are passed as "
+"boot parameters, but for those a special syntax can be used. See <xref "
+"linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
-msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
+msgid ""
+"Delay questions that are normally asked before preseeding is possible until "
+"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
+"details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
-msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
+msgid ""
+"During installations from serial or management console, the regular virtual "
+"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
+"filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
-msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
+msgid ""
+"By default, before rebooting, &d-i; automatically ejects the optical media "
+"used during the installation. This can be unnecessary if the system does not "
+"automatically boot off the CD. In some cases it may even be undesirable, for "
+"example if the optical drive cannot reinsert the media itself and the user "
+"is not there to do it manually. Many slot loading, slim-line, and caddy "
+"style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
+msgid ""
+"Set to <userinput>false</userinput> to disable automatic ejection, and be "
+"aware that you may need to ensure that the system does not automatically "
+"boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
-msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
+msgid ""
+"By setting this option to <userinput>false</userinput>, the package "
+"management system will be configured to not automatically install "
+"<quote>Recommends</quote>, both during the installation and for the "
+"installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
-msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
+msgid ""
+"Note that this option allows to have a leaner system, but can also result in "
+"features being missing that you might normally expect to be available. You "
+"may have to manually install some of the recommended packages to obtain the "
+"full functionality you want. This option should therefore only be used by "
+"very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
-msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
+msgid ""
+"By default the installer requires that repositories be authenticated using a "
+"known gpg key. Set to <userinput>true</userinput> to disable that "
+"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
+"emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
-msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
+msgid ""
+"This parameter should already be set to a correct value where needed; set it "
+"only it you see errors during the boot that indicate the ramdisk could not "
+"be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
+msgid ""
+"Set to <userinput>true</userinput> to enter rescue mode rather than "
+"performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
-msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
+msgid ""
+"With some exceptions, a value can be set at the boot prompt for any question "
+"asked during the installation, though this is only really useful in specific "
+"cases. General instructions how to do this can be found in <xref linkend="
+"\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
-msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
+msgid ""
+"There are two ways to specify the language, country and locale to use for "
+"the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
-msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
+msgid ""
+"The first and easiest is to pass only the parameter <literal>locale</"
+"literal>. Language and country will then be derived from its value. You can "
+"for example use <userinput>locale=de_CH</userinput> to select German as "
+"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be "
+"set as default locale for the installed system). Limitation is that not all "
+"possible combinations of language, country and locale can be achieved this "
+"way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
-msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
+msgid ""
+"The second, more flexible option is to specify <literal>language</literal> "
+"and <literal>country</literal> separately. In this case <literal>locale</"
+"literal> can optionally be added to specify a specific default locale for "
+"the installed system. Example: <userinput>language=en country=DE "
+"locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
-msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
+msgid ""
+"Can be used to automatically load installer components that are not loaded "
+"by default. Examples of optional components that may be useful are "
+"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
+"command> during the installation)<phrase arch=\"not-s390\"> and "
+"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
-msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
+msgid ""
+"Set to <userinput>true</userinput> if you want to disable DHCP and instead "
+"force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
-msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
+msgid ""
+"By default the installer will use the http protocol to download files from "
+"&debian; mirrors and changing that to ftp is not possible during "
+"installations at normal priority. By setting this parameter to "
+"<userinput>ftp</userinput>, you can force the installer to use that protocol "
+"instead. Note that you cannot select an ftp mirror from a list, you have to "
+"enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
-msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
+msgid ""
+"Can be used to select tasks that are not available from the interactive task "
+"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
+"\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
-msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
+msgid ""
+"If drivers are compiled into the kernel, you can pass parameters to them as "
+"described in the kernel documentation. However, if drivers are compiled as "
+"modules and because kernel modules are loaded a bit differently during an "
+"installation than when booting an installed system, it is not possible to "
+"pass parameters to modules as you would normally do. Instead, you need to "
+"use a special syntax recognized by the installer which will then make sure "
+"that the parameters are saved in the proper configuration files and will "
+"thus be used when the modules are actually loaded. The parameters will also "
+"be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
-msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
+msgid ""
+"Note that it is now quite rare that parameters need to be passed to modules. "
+"In most cases the kernel will be able to probe the hardware present in a "
+"system and set good defaults that way. However, in some situations it may "
+"still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
-      "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
-      "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n"
-      "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:"
+"The syntax to use to set parameters for modules is: "
+"<informalexample><screen>\n"
+"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
+"replaceable>=<replaceable>value</replaceable>\n"
+"</screen></informalexample> If you need to pass multiple parameters to the "
+"same or different modules, just repeat this. For example, to set an old 3Com "
+"network interface card to use the BNC (coax) connector and IRQ 10, you would "
+"pass:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
-msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
+msgid ""
+"Sometimes it may be necessary to blacklist a module to prevent it from being "
+"loaded automatically by the kernel and udev. One reason could be that a "
+"particular module causes problems with your hardware. The kernel also "
+"sometimes lists two different drivers for the same device. This can cause "
+"the device to not work correctly if the drivers conflict or if the wrong "
+"driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
-msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
+msgid ""
+"You can blacklist a module using the following syntax: "
+"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
+"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
+"blacklist.local</filename> both during the installation and for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
-msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
+msgid ""
+"Note that a module may still be loaded by the installation system itself. "
+"You can prevent that from happening by running the installation in expert "
+"mode and unselecting the module from the list of modules displayed during "
+"the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
-msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
+msgid ""
+"Sometimes, especially with older CD-ROM drives, the installer may fail to "
+"boot from a CD-ROM. The installer may also &mdash; even after booting "
+"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
+"errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
-msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
+msgid ""
+"There are many different possible causes for these problems. We can only "
+"list some common issues and provide general suggestions on how to deal with "
+"them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
-msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
+msgid ""
+"If the CD-ROM does not boot, check that it was inserted correctly and that "
+"it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
-msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
+msgid ""
+"If the installer fails to recognize a CD-ROM, try just running the option "
+"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
+"menuchoice> a second time. Some DMA related issues with very old CD-ROM "
+"drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
-msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
+msgid ""
+"If this does not work, then try the suggestions in the subsections below. "
+"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
+"DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
-msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
+msgid ""
+"If you cannot get the installation working from CD-ROM, try one of the other "
+"installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
-msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
+msgid ""
+"Some older CD-ROM drives do not support reading from discs that were burned "
+"at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
-msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
+msgid ""
+"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
+"access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
-msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
+msgid ""
+"Check that your BIOS actually supports booting from CD-ROM (only an issue "
+"for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
-      "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
-      "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM."
+"If you downloaded an iso image, check that the md5sum of that image matches "
+"the one listed for the image in the <filename>MD5SUMS</filename> file that "
+"should be present in the same location as where you downloaded the image "
+"from. <informalexample><screen>\n"
+"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
+"iso</replaceable>\n"
+"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
+"matches as well. The following command should work. It uses the size of the "
+"image to read the correct number of bytes from the CD-ROM."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
-      "$ dd if=/dev/cdrom | \\\n"
-      "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n"
-      "> md5sum\n"
-      "a20391b12f7ff22ef705cee4059c6b92  -\n"
-      "262668+0 records in\n"
-      "262668+0 records out\n"
-      "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
+"$ dd if=/dev/cdrom | \\\n"
+"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
+"replaceable>` | \\\n"
+"> md5sum\n"
+"a20391b12f7ff22ef705cee4059c6b92  -\n"
+"262668+0 records in\n"
+"262668+0 records out\n"
+"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
-msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
+msgid ""
+"If, after the installer has been booted successfully, the CD-ROM is not "
+"detected, sometimes simply trying again may solve the problem. If you have "
+"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
+"that does not work or if the CD-ROM is recognized but there are errors when "
+"reading from it, try the suggestions listed below. Some basic knowledge of "
+"&arch-kernel; is required for this. To execute any of the commands, you "
+"should first switch to the second virtual console (VT2) and activate the "
+"shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
-msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
+msgid ""
+"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
+"(use <command>nano</command> as editor) to check for any specific error "
+"messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
-      "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
-      "Probing IDE interface ide1...\n"
-      "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
-      "ide1 at 0x170-0x177,0x376 on irq 15\n"
-      "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
-      "Uniform CD-ROM driver Revision: 3.20\n"
-      "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using <command>modprobe</command>."
+"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
+"recognized. You should see something like (the lines do not necessarily have "
+"to be consecutive): <informalexample><screen>\n"
+"Probing IDE interface ide1...\n"
+"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
+"ide1 at 0x170-0x177,0x376 on irq 15\n"
+"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
+"Uniform CD-ROM driver Revision: 3.20\n"
+"</screen></informalexample> If you don't see something like that, chances "
+"are the controller your CD-ROM is connected to was not recognized or may be "
+"not supported at all. If you know what driver is needed for the controller, "
+"you can try loading it manually using <command>modprobe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
-msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
+msgid ""
+"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
+"</filename>. In the example above, this would be <filename>/dev/hdc</"
+"filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
-      "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
-      "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
-      "</screen></informalexample> Check if there are any error messages after that command."
+"Use the <command>mount</command> command to check if the CD-ROM is already "
+"mounted; if not, try mounting it manually: <informalexample><screen>\n"
+"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
+"</screen></informalexample> Check if there are any error messages after that "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
-      "Check if DMA is currently enabled: <informalexample><screen>\n"
-      "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
-      "$ grep using_dma settings\n"
-      "using_dma      1       0       1       rw\n"
-      "</screen></informalexample> A <quote>1</quote> in the first column after <literal>using_dma</literal> means it is enabled. If it is, try disabling it: <informalexample><screen>\n"
-      "$ echo -n \"using_dma:0\" >settings\n"
-      "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive."
+"Check if DMA is currently enabled: <informalexample><screen>\n"
+"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
+"$ grep using_dma settings\n"
+"using_dma      1       0       1       rw\n"
+"</screen></informalexample> A <quote>1</quote> in the first column after "
+"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
+"it: <informalexample><screen>\n"
+"$ echo -n \"using_dma:0\" >settings\n"
+"</screen></informalexample> Make sure that you are in the directory for the "
+"device that corresponds to your CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
-msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
+msgid ""
+"If there are any problems during the installation, try checking the "
+"integrity of the CD-ROM using the option near the bottom of the installer's "
+"main menu. This option can also be used as a general test if the CD-ROM can "
+"be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
-msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
+msgid ""
+"The biggest problem for people using floppy disks to install &debian; seems "
+"to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
-msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
+msgid ""
+"The boot floppy is the floppy with the worst problems, because it is read by "
+"the hardware directly, before Linux boots. Often, the hardware doesn't read "
+"as reliably as the Linux floppy disk driver, and may just stop without "
+"printing an error message if it reads incorrect data. There can also be "
+"failures in the driver floppies, most of which indicate themselves with a "
+"flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
-msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
+msgid ""
+"If you are having the installation stall at a particular floppy, the first "
+"thing you should do is write the image to a <emphasis>different</emphasis> "
+"floppy and see if that solves the problem. Simply reformatting the old "
+"floppy may not be sufficient, even if it appears that the floppy was "
+"reformatted and written with no errors. It is sometimes useful to try "
+"writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
-msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
+msgid ""
+"One user reports he had to write the images to floppy <emphasis>three</"
+"emphasis> times before one worked, and then everything was fine with the "
+"third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
-msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
+msgid ""
+"Normally you should not have to download a floppy image again, but if you "
+"are experiencing problems it is always useful to verify that the images were "
+"downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
-msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
+msgid ""
+"Other users have reported that simply rebooting a few times with the same "
+"floppy in the floppy drive can lead to a successful boot. This is all due to "
+"buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
-msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
+msgid ""
+"If you have problems and the kernel hangs during the boot process, doesn't "
+"recognize peripherals you actually have, or drives are not recognized "
+"properly, the first thing to check is the boot parameters, as discussed in "
+"<xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
-msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
+msgid ""
+"In some cases, malfunctions can be caused by missing device firmware (see "
+"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
+">)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
-msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
+msgid ""
+"If software speech synthesis does not work, there is most probably an issue "
+"with your sound board, usually because either the driver for it is not "
+"included in the installer, or because it has unusual mixer level names which "
+"are set to muted by default. You should thus submit a bug report which "
+"includes the output of the following commands, run on the same machine from "
+"a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
-msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
+msgid ""
+"There are some common installation problems that can be solved or avoided by "
+"passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
-msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
+msgid ""
+"If your screen begins to show a weird picture while the kernel boots, eg. "
+"pure white, pure black or colored pixel garbage, your system may contain a "
+"problematic video card which does not switch to the framebuffer mode "
+"properly. Then you can use the boot parameter <userinput>fb=false</"
+"userinput> to disable the framebuffer console. Only a reduced set of "
+"languages will be available during the installation due to limited console "
+"features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
-msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
+msgid ""
+"Some very old laptop models produced by Dell are known to crash when PCMCIA "
+"device detection tries to access some hardware addresses. Other laptops may "
+"display similar problems. If you experience such a problem and you don't "
+"need PCMCIA support during the installation, you can disable PCMCIA using "
+"the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
+"can then configure PCMCIA after the installation is completed and exclude "
+"the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
-msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
+msgid ""
+"Alternatively, you can boot the installer in expert mode. You will then be "
+"asked to enter the resource range options your hardware needs. For example, "
+"if you have one of the Dell laptops mentioned above, you should enter "
+"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
+"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
+"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
+"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
+"commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
-      "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
-      "Remapping the kernel... done\n"
-      "Booting Linux...\n"
-      "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>."
+"It is fairly common for &arch-title; to have two video cards in one machine, "
+"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
+"in the video output getting misdirected soon after the system boots. In "
+"typical cases, the display will only show: <informalexample><screen>\n"
+"Remapping the kernel... done\n"
+"Booting Linux...\n"
+"</screen></informalexample> To work around this, you can either pull out one "
+"of the video cards, or disable the one not used during the OpenProm boot "
+"phase using a kernel parameter. For example, to disable an ATI card, you "
+"should boot the installer with <userinput>video=atyfb:off</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
-msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"Note that you may also have to manually add this parameter to the silo "
+"configuration (edit <filename>/target/etc/silo.conf</filename> before "
+"rebooting) and, if you installed X11, modify the video driver in <filename>/"
+"etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
-msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
+msgid ""
+"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
+"they do boot, there may be inexplicable failures during the installation. "
+"Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
-msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
+msgid ""
+"During the boot sequence, you may see many messages in the form "
+"<computeroutput>can't find <replaceable>something</replaceable></"
+"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
+"present</computeroutput>, <computeroutput>can't initialize "
+"<replaceable>something</replaceable></computeroutput>, or even "
+"<computeroutput>this driver release depends on <replaceable>something</"
+"replaceable></computeroutput>. Most of these messages are harmless. You see "
+"them because the kernel for the installation system is built to run on "
+"computers with many different peripheral devices. Obviously, no one computer "
+"will have every possible peripheral device, so the operating system may emit "
+"a few complaints while it looks for peripherals you don't own. You may also "
+"see the system pause for a while. This happens when it is waiting for a "
+"device to respond, and that device is not present on your system. If you "
+"find the time it takes to boot the system unacceptably long, you can create "
+"a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
+"baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
-msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
+msgid ""
+"If you get through the initial boot phase but cannot complete the install, "
+"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
+"It lets you store system error logs and configuration information from the "
+"installer to a floppy, or download them using a web browser. This "
+"information may provide clues as to what went wrong and how to fix it. If "
+"you are submitting a bug report, you may want to attach this information to "
+"the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
-msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"Other pertinent installation messages may be found in <filename>/var/log/</"
+"filename> during the installation, and <filename>/var/log/installer/</"
+"filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
-msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
+msgid ""
+"If you still have problems, please submit an installation report. We also "
+"encourage installation reports to be sent even if the installation is "
+"successful, so that we can get as much information as possible on the "
+"largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
-msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
+msgid ""
+"Note that your installation report will be published in the Debian Bug "
+"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
+"you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
-msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
+msgid ""
+"If you have a working &debian; system, the easiest way to send an "
+"installation report is to install the <classname>installation-report</"
+"classname> and <classname>reportbug</classname> packages (<command>aptitude "
+"install installation-report reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run the command <command>reportbug installation-reports</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
-      "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
-      "Package: installation-reports\n"
-      "\n"
-      "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
-      "Image version: &lt;Full URL to image you downloaded is best&gt;\n"
-      "Date: &lt;Date and time of the install&gt;\n"
-      "\n"
-      "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
-      "Processor:\n"
-      "Memory:\n"
-      "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
-      "\n"
-      "Output of lspci -knn (or lspci -nn):\n"
-      "\n"
-      "Base System Installation Checklist:\n"
-      "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
-      "\n"
-      "Initial boot:           [ ]\n"
-      "Detect network card:    [ ]\n"
-      "Configure network:      [ ]\n"
-      "Detect CD:              [ ]\n"
-      "Load installer modules: [ ]\n"
-      "Detect hard drives:     [ ]\n"
-      "Partition hard drives:  [ ]\n"
-      "Install base system:    [ ]\n"
-      "Clock/timezone setup:   [ ]\n"
-      "User/password setup:    [ ]\n"
-      "Install tasks:          [ ]\n"
-      "Install boot loader:    [ ]\n"
-      "Overall install:        [ ]\n"
-      "\n"
-      "Comments/Problems:\n"
-      "\n"
-      "&lt;Description of the install, in prose, and any thoughts, comments\n"
-      "      and ideas you had during the initial install.&gt;\n"
-      "</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state."
+"Alternatively you can use this template when filling out installation "
+"reports, and file the report as a bug report against the "
+"<classname>installation-reports</classname> pseudo package, by sending it to "
+"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
+"Package: installation-reports\n"
+"\n"
+"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
+"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
+"Date: &lt;Date and time of the install&gt;\n"
+"\n"
+"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
+"Processor:\n"
+"Memory:\n"
+"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
+"\n"
+"Output of lspci -knn (or lspci -nn):\n"
+"\n"
+"Base System Installation Checklist:\n"
+"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
+"\n"
+"Initial boot:           [ ]\n"
+"Detect network card:    [ ]\n"
+"Configure network:      [ ]\n"
+"Detect CD:              [ ]\n"
+"Load installer modules: [ ]\n"
+"Detect hard drives:     [ ]\n"
+"Partition hard drives:  [ ]\n"
+"Install base system:    [ ]\n"
+"Clock/timezone setup:   [ ]\n"
+"User/password setup:    [ ]\n"
+"Install tasks:          [ ]\n"
+"Install boot loader:    [ ]\n"
+"Overall install:        [ ]\n"
+"\n"
+"Comments/Problems:\n"
+"\n"
+"&lt;Description of the install, in prose, and any thoughts, comments\n"
+"      and ideas you had during the initial install.&gt;\n"
+"</screen></informalexample> In the bug report, describe what the problem is, "
+"including the last visible kernel messages in the event of a kernel hang. "
+"Describe the steps that you did which brought the system into the problem "
+"state."
 msgstr ""
-
diff --git a/po/nn/boot-new.po b/po/nn/boot-new.po
index 202d93271..f4d294cfc 100644
--- a/po/nn/boot-new.po
+++ b/po/nn/boot-new.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,31 +29,59 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:8
 #, no-c-format
-msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>."
+msgid ""
+"Your system's first boot on its own power is what electrical engineers call "
+"the <quote>smoke test</quote>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:13
 #, no-c-format
-msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new &debian; system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu."
+msgid ""
+"If you did a default installation, the first thing you should see when you "
+"boot the system is the menu of the <classname>grub</classname><phrase arch="
+"\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. "
+"The first choices in the menu will be for your new &debian; system. If you "
+"had any other operating systems on your computer (like Windows) that were "
+"detected by the installation system, those will be listed lower down in the "
+"menu."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:23
 #, no-c-format
-msgid "If the system fails to start up correctly, don't panic. If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting &debian;. In most cases such problems can be fixed without having to repeat the installation. One available option to fix boot problems is to use the installer's built-in rescue mode (see <xref linkend=\"rescue\"/>)."
+msgid ""
+"If the system fails to start up correctly, don't panic. If the installation "
+"was successful, chances are good that there is only a relatively minor "
+"problem that is preventing the system from booting &debian;. In most cases "
+"such problems can be fixed without having to repeat the installation. One "
+"available option to fix boot problems is to use the installer's built-in "
+"rescue mode (see <xref linkend=\"rescue\"/>)."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:32
 #, no-c-format
-msgid "If you are new to &debian; and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue."
+msgid ""
+"If you are new to &debian; and &arch-kernel;, you may need some help from "
+"more experienced users. <phrase arch=\"x86\">For direct on-line help you can "
+"try the IRC channels #debian or #debian-boot on the OFTC network. "
+"Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-"
+"user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common "
+"architectures like &arch-title;, your best option is to ask on the <ulink "
+"url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</"
+"phrase> You can also file an installation report as described in <xref "
+"linkend=\"submit-bug\"/>. Please make sure that you describe your problem "
+"clearly and include any messages that are displayed and may help others to "
+"diagnose the issue."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:48
 #, no-c-format
-msgid "If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report."
+msgid ""
+"If you had any other operating systems on your computer that were not "
+"detected or not detected correctly, please file an installation report."
 msgstr ""
 
 #. Tag: title
@@ -64,19 +93,42 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:57
 #, no-c-format
-msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
+msgid ""
+"If the machine fails to boot after completing the installation, and stops "
+"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</"
+"userinput> followed by &enterkey;. (The default boot configuration in "
+"<filename>quik.conf</filename> is labeled Linux). The labels defined in "
+"<filename>quik.conf</filename> will be displayed if you press the "
+"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also "
+"try booting back into the installer, and editing the <filename>/target/etc/"
+"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard "
+"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are "
+"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:71
 #, no-c-format
-msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"To boot back into MacOS without resetting the nvram, type <userinput>bye</"
+"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed "
+"from the machine). To obtain an OpenFirmware prompt, hold down the "
+"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</"
+"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. "
+"If you need to reset the OpenFirmware nvram changes to the MacOS default in "
+"order to boot back to MacOS, hold down the <keycombo> <keycap>command</"
+"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </"
+"keycombo> keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:84
 #, no-c-format
-msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
+msgid ""
+"If you use <command>BootX</command> to boot into the installed system, just "
+"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
+"un-choose the ramdisk option, and add a root device corresponding to your "
+"installation; e.g. <userinput>/dev/hda8</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -88,31 +140,52 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:97
 #, no-c-format
-msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon."
+msgid ""
+"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key "
+"and get a graphical screen with a button for each bootable OS, &debian-gnu; "
+"will be a button with a small penguin icon."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:104
 #, no-c-format
-msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-"
+"device</envar> variable you should reset OpenFirmware to its default "
+"configuration. To do this hold down the <keycombo> <keycap>command</keycap> "
+"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> "
+"keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:112
 #, no-c-format
-msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
+msgid ""
+"The labels defined in <filename>yaboot.conf</filename> will be displayed if "
+"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:118
 #, no-c-format
-msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
+msgid ""
+"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-"
+"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap "
+"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an "
+"IDE disk this may not work and you will have to enter OpenFirmware and set "
+"the <envar>boot-device</envar> variable, <command>ybin</command> normally "
+"does this automatically."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:127
 #, no-c-format
-msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
+msgid ""
+"After you boot &debian-gnu; for the first time you can add any additional "
+"options you desire (such as dual boot options) to <filename>/etc/yaboot."
+"conf</filename> and run <command>ybin</command> to update your boot "
+"partition with the changed configuration. Please read the <ulink url=\"&url-"
+"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
 msgstr ""
 
 #. Tag: title
@@ -124,7 +197,11 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:147
 #, no-c-format
-msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
+msgid ""
+"If you created encrypted volumes during the installation and assigned them "
+"mount points, you will be asked to enter the passphrase for each of these "
+"volumes during the boot. The actual procedure differs slightly between dm-"
+"crypt and loop-AES."
 msgstr ""
 
 #. Tag: title
@@ -137,31 +214,54 @@ msgstr ""
 #: boot-new.xml:159
 #, no-c-format
 msgid ""
-      "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
-      "Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
-      "Enter LUKS passphrase:\n"
-      "</screen></informalexample> In the first line of the prompt, <replaceable>part</replaceable> is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename><replaceable>part</replaceable>_crypt</filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system."
+"For partitions encrypted using dm-crypt you will be shown the following "
+"prompt during the boot: <informalexample><screen>\n"
+"Starting early crypto disks... <replaceable>part</replaceable>_crypt"
+"(starting)\n"
+"Enter LUKS passphrase:\n"
+"</screen></informalexample> In the first line of the prompt, "
+"<replaceable>part</replaceable> is the name of the underlying partition, e."
+"g. sda2 or md0. You are now probably wondering <emphasis>for which volume</"
+"emphasis> you are actually entering the passphrase. Does it relate to your "
+"<filename>/home</filename>? Or to <filename>/var</filename>? Of course, if "
+"you have just one encrypted volume, this is easy and you can just enter the "
+"passphrase you used when setting up this volume. If you set up more than one "
+"encrypted volume during the installation, the notes you wrote down as the "
+"last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did "
+"not make a note of the mapping between <filename><replaceable>part</"
+"replaceable>_crypt</filename> and the mount points before, you can still "
+"find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</"
+"filename> of your new system."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:182
 #, no-c-format
-msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
+msgid ""
+"The prompt may look somewhat different when an encrypted root file system is "
+"mounted. This depends on which initramfs generator was used to generate the "
+"initrd used to boot the system. The example below is for an initrd generated "
+"using <classname>initramfs-tools</classname>:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:189
 #, no-c-format
 msgid ""
-      "Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
-      "Begin: Running /scripts/local-top ...\n"
-      "Enter LUKS passphrase:"
+"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
+"Begin: Running /scripts/local-top ...\n"
+"Enter LUKS passphrase:"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:191 boot-new.xml:216
 #, no-c-format
-msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
+msgid ""
+"No characters (even asterisks) will be shown while entering the passphrase. "
+"If you enter the wrong passphrase, you have two more tries to correct it. "
+"After the third try the boot process will skip this volume and continue to "
+"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting"
+"\"/> for further information."
 msgstr ""
 
 #. Tag: para
@@ -179,16 +279,19 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:209
 #, no-c-format
-msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
+msgid ""
+"For partitions encrypted using loop-AES you will be shown the following "
+"prompt during the boot:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:214
 #, no-c-format
 msgid ""
-      "Checking loop-encrypted file systems.\n"
-      "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
-      "Password:"
+"Checking loop-encrypted file systems.\n"
+"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</"
+"replaceable>)\n"
+"Password:"
 msgstr ""
 
 #. Tag: title
@@ -200,47 +303,77 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:234
 #, no-c-format
-msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
+msgid ""
+"If some of the encrypted volumes could not be mounted because a wrong "
+"passphrase was entered, you will have to mount them manually after the boot. "
+"There are several cases."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:243
 #, no-c-format
-msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
+msgid ""
+"The first case concerns the root partition. When it is not mounted "
+"correctly, the boot process will halt and you will have to reboot the "
+"computer to try again."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:250
 #, no-c-format
 msgid ""
-      "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
-      "<prompt>Password:</prompt>\n"
-      "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
+"The easiest case is for encrypted volumes holding data like <filename>/home</"
+"filename> or <filename>/srv</filename>. You can simply mount them manually "
+"after the boot. For loop-AES this is a one-step operation: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>\n"
+"<prompt>Password:</prompt>\n"
+"</screen></informalexample> where <replaceable>/mount_point</replaceable> "
+"should be replaced by the particular directory (e.g. <filename>/home</"
+"filename>). The only difference from an ordinary mount is that you will be "
+"asked to enter the passphrase for this volume."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:264
 #, no-c-format
 msgid ""
-      "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-      "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
+"For dm-crypt this is a bit trickier. First you need to register the volumes "
+"with <application>device mapper</application> by running: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
+"</screen></informalexample> This will scan all volumes mentioned in "
+"<filename>/etc/crypttab</filename> and will create appropriate devices under "
+"the <filename>/dev</filename> directory after entering the correct "
+"passphrases. (Already registered volumes will be skipped, so you can repeat "
+"this command several times without worrying.) After successful registration "
+"you can simply mount the volumes the usual way:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:279
 #, no-c-format
-msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
+msgid ""
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:282
 #, no-c-format
 msgid ""
-      "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-      "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
+"If any volume holding noncritical system files could not be mounted "
+"(<filename>/usr</filename> or <filename>/var</filename>), the system should "
+"still boot and you should be able to mount the volumes manually like in the "
+"previous case. However, you will also need to (re)start any services usually "
+"running in your default runlevel because it is very likely that they were "
+"not started. The easiest way to achieve this is by switching to the first "
+"runlevel and back by entering <informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>init 1</userinput>\n"
+"</screen></informalexample> at the shell prompt and pressing <keycombo> "
+"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the "
+"root password."
 msgstr ""
 
 #. Tag: title
@@ -252,46 +385,81 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:307
 #, no-c-format
-msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
+msgid ""
+"Once your system boots, you'll be presented with the login prompt. Log in "
+"using the personal login and password you selected during the installation "
+"process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:313
 #, no-c-format
-msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
+msgid ""
+"If you are a new user, you may want to explore the documentation which is "
+"already installed on your system as you start to use it. There are currently "
+"several documentation systems, work is proceeding on integrating the "
+"different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:321
 #, no-c-format
-msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
+msgid ""
+"Documentation accompanying programs you have installed can be found in "
+"<filename>/usr/share/doc/</filename>, under a subdirectory named after the "
+"program (or, more precise, the &debian; package that contains the program). "
+"However, more extensive documentation is often packaged separately in "
+"special documentation packages that are mostly not installed by default. For "
+"example, documentation about the package management tool <command>apt</"
+"command> can be found in the packages <classname>apt-doc</classname> or "
+"<classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:332
 #, no-c-format
-msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
+msgid ""
+"In addition, there are some special folders within the <filename>/usr/share/"
+"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</"
+"emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</"
+"filename>. After installing <classname>dhelp</classname>, you will find a "
+"browsable index of documentation in <filename>/usr/share/doc/HTML/index."
+"html</filename>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:341
 #, no-c-format
 msgid ""
-      "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
-      "$ cd /usr/share/doc/\n"
-      "$ w3m .\n"
-      "</screen></informalexample> The dot after the <command>w3m</command> command tells it to show the contents of the current directory."
+"One easy way to view these documents using a text based browser is to enter "
+"the following commands: <informalexample><screen>\n"
+"$ cd /usr/share/doc/\n"
+"$ w3m .\n"
+"</screen></informalexample> The dot after the <command>w3m</command> command "
+"tells it to show the contents of the current directory."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:351
 #, no-c-format
-msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
+msgid ""
+"If you have a graphical desktop environment installed, you can also use its "
+"web browser. Start the web browser from the application menu and enter "
+"<userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:357
 #, no-c-format
-msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
+msgid ""
+"You can also type <userinput>info <replaceable>command</replaceable></"
+"userinput> or <userinput>man <replaceable>command</replaceable></userinput> "
+"to see documentation on most commands available at the command prompt. "
+"Typing <userinput>help</userinput> will display help on shell commands. And "
+"typing a command followed by <userinput>--help</userinput> will usually "
+"display a short summary of the command's usage. If a command's results "
+"scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> "
+"after the command to cause the results to pause before scrolling past the "
+"top of the screen. To see a list of all commands available which begin with "
+"a certain letter, type the letter and then two tabs."
 msgstr ""
-
diff --git a/po/nn/gpl.po b/po/nn/gpl.po
index 3582cbd8a..5f7616aa6 100644
--- a/po/nn/gpl.po
+++ b/po/nn/gpl.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,35 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:6
 #, no-c-format
-msgid "[[This note, consisting of two paragraphs, should only be included in your translation if you translate the GPL in this appendix. See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English name of your language. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[This note, consisting of two paragraphs, should only be included in your "
+"translation if you translate the GPL in this appendix. See build/lang-"
+"options/README on how to enable this paragraph and for additional "
+"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH "
+"IN ENGLISH! Only replace {language} with the English name of your language. "
+"Do not change the link to the GPL!]] This is an unofficial translation of "
+"the GNU General Public License into {language}. It was not published by the "
+"Free Software Foundation, and does not legally state the distribution terms "
+"for software that uses the GNU GPL &mdash; only the original <ulink url="
+"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. "
+"However, we hope that this translation will help {language} speakers to "
+"better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:22
 #, no-c-format
-msgid "[[See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of your language before translating. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[See build/lang-options/README on how to enable this paragraph and for "
+"additional information. Its condition is \"gpl-unofficial\".]] [[THIS "
+"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of "
+"your language before translating. Do not change the link to the GPL!]] This "
+"is an unofficial translation of the GNU General Public License into "
+"{language}. It was not published by the Free Software Foundation, and does "
+"not legally state the distribution terms for software that uses the GNU GPL "
+"&mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</"
+"ulink> of the GNU GPL does that. However, we hope that this translation will "
+"help {language} speakers to better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
@@ -41,11 +64,11 @@ msgstr ""
 #: gpl.xml:41
 #, no-c-format
 msgid ""
-      "Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
-      "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
-      "\n"
-      "Everyone is permitted to copy and distribute verbatim copies\n"
-      "of this license document, but changing it is not allowed."
+"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
+"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
+"\n"
+"Everyone is permitted to copy and distribute verbatim copies\n"
+"of this license document, but changing it is not allowed."
 msgstr ""
 
 #. Tag: title
@@ -57,49 +80,87 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:46
 #, no-c-format
-msgid "The licenses for most software are designed to take away your freedom to share and change it. By contrast, the gnu General Public License is intended to guarantee your freedom to share and change free software &mdash; to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the gnu Library General Public License instead.) You can apply it to your programs, too."
+msgid ""
+"The licenses for most software are designed to take away your freedom to "
+"share and change it. By contrast, the gnu General Public License is intended "
+"to guarantee your freedom to share and change free software &mdash; to make "
+"sure the software is free for all its users. This General Public License "
+"applies to most of the Free Software Foundation's software and to any other "
+"program whose authors commit to using it. (Some other Free Software "
+"Foundation software is covered by the gnu Library General Public License "
+"instead.) You can apply it to your programs, too."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:58
 #, no-c-format
-msgid "When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+msgid ""
+"When we speak of free software, we are referring to freedom, not price. Our "
+"General Public Licenses are designed to make sure that you have the freedom "
+"to distribute copies of free software (and charge for this service if you "
+"wish), that you receive source code or can get it if you want it, that you "
+"can change the software or use pieces of it in new free programs; and that "
+"you know you can do these things."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:68
 #, no-c-format
-msgid "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it."
+msgid ""
+"To protect your rights, we need to make restrictions that forbid anyone to "
+"deny you these rights or to ask you to surrender the rights. These "
+"restrictions translate to certain responsibilities for you if you distribute "
+"copies of the software, or if you modify it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:75
 #, no-c-format
-msgid "For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
+msgid ""
+"For example, if you distribute copies of such a program, whether gratis or "
+"for a fee, you must give the recipients all the rights that you have. You "
+"must make sure that they, too, receive or can get the source code. And you "
+"must show them these terms so they know their rights."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:83
 #, no-c-format
-msgid "We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
+msgid ""
+"We protect your rights with two steps: (1) copyright the software, and (2) "
+"offer you this license which gives you legal permission to copy, distribute "
+"and/or modify the software."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:89
 #, no-c-format
-msgid "Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations."
+msgid ""
+"Also, for each author's protection and ours, we want to make certain that "
+"everyone understands that there is no warranty for this free software. If "
+"the software is modified by someone else and passed on, we want its "
+"recipients to know that what they have is not the original, so that any "
+"problems introduced by others will not reflect on the original authors' "
+"reputations."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:98
 #, no-c-format
-msgid "Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."
+msgid ""
+"Finally, any free program is threatened constantly by software patents. We "
+"wish to avoid the danger that redistributors of a free program will "
+"individually obtain patent licenses, in effect making the program "
+"proprietary. To prevent this, we have made it clear that any patent must be "
+"licensed for everyone's free use or not licensed at all."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:107
 #, no-c-format
-msgid "The precise terms and conditions for copying, distribution and modification follow."
+msgid ""
+"The precise terms and conditions for copying, distribution and modification "
+"follow."
 msgstr ""
 
 #. Tag: title
@@ -117,163 +178,327 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:121
 #, no-c-format
-msgid "<emphasis role=\"bold\">0.</emphasis> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \"Program\", below, refers to any such program or work, and a \"work based on the Program\" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \"modification\".) Each licensee is addressed as \"you\"."
+msgid ""
+"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or "
+"other work which contains a notice placed by the copyright holder saying it "
+"may be distributed under the terms of this General Public License. The "
+"\"Program\", below, refers to any such program or work, and a \"work based "
+"on the Program\" means either the Program or any derivative work under "
+"copyright law: that is to say, a work containing the Program or a portion of "
+"it, either verbatim or with modifications and/or translated into another "
+"language. (Hereinafter, translation is included without limitation in the "
+"term \"modification\".) Each licensee is addressed as \"you\"."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:134
 #, no-c-format
-msgid "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
+msgid ""
+"Activities other than copying, distribution and modification are not covered "
+"by this License; they are outside its scope. The act of running the Program "
+"is not restricted, and the output from the Program is covered only if its "
+"contents constitute a work based on the Program (independent of having been "
+"made by running the Program). Whether that is true depends on what the "
+"Program does."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:143
 #, no-c-format
-msgid "<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program."
+msgid ""
+"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim "
+"copies of the Program's source code as you receive it, in any medium, "
+"provided that you conspicuously and appropriately publish on each copy an "
+"appropriate copyright notice and disclaimer of warranty; keep intact all the "
+"notices that refer to this License and to the absence of any warranty; and "
+"give any other recipients of the Program a copy of this License along with "
+"the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:154
 #, no-c-format
-msgid "You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
+msgid ""
+"You may charge a fee for the physical act of transferring a copy, and you "
+"may at your option offer warranty protection in exchange for a fee."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:160
 #, no-c-format
-msgid "<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:"
+msgid ""
+"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of "
+"the Program or any portion of it, thus forming a work based on the Program, "
+"and copy and distribute such modifications or work under the terms of "
+"Section 1 above, provided that you also meet all of these conditions:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:169
 #, no-c-format
-msgid "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."
+msgid ""
+"You must cause the modified files to carry prominent notices stating that "
+"you changed the files and the date of any change."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:175
 #, no-c-format
-msgid "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License."
+msgid ""
+"You must cause any work that you distribute or publish, that in whole or in "
+"part contains or is derived from the Program or any part thereof, to be "
+"licensed as a whole at no charge to all third parties under the terms of "
+"this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:183
 #, no-c-format
-msgid "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
+msgid ""
+"If the modified program normally reads commands interactively when run, you "
+"must cause it, when started running for such interactive use in the most "
+"ordinary way, to print or display an announcement including an appropriate "
+"copyright notice and a notice that there is no warranty (or else, saying "
+"that you provide a warranty) and that users may redistribute the program "
+"under these conditions, and telling the user how to view a copy of this "
+"License. (Exception: if the Program itself is interactive but does not "
+"normally print such an announcement, your work based on the Program is not "
+"required to print an announcement.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:197
 #, no-c-format
-msgid "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
+msgid ""
+"These requirements apply to the modified work as a whole. If identifiable "
+"sections of that work are not derived from the Program, and can be "
+"reasonably considered independent and separate works in themselves, then "
+"this License, and its terms, do not apply to those sections when you "
+"distribute them as separate works. But when you distribute the same sections "
+"as part of a whole which is a work based on the Program, the distribution of "
+"the whole must be on the terms of this License, whose permissions for other "
+"licensees extend to the entire whole, and thus to each and every part "
+"regardless of who wrote it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:210
 #, no-c-format
-msgid "Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program."
+msgid ""
+"Thus, it is not the intent of this section to claim rights or contest your "
+"rights to work written entirely by you; rather, the intent is to exercise "
+"the right to control the distribution of derivative or collective works "
+"based on the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:217
 #, no-c-format
-msgid "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
+msgid ""
+"In addition, mere aggregation of another work not based on the Program with "
+"the Program (or with a work based on the Program) on a volume of a storage "
+"or distribution medium does not bring the other work under the scope of this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:224
 #, no-c-format
-msgid "<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:"
+msgid ""
+"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the "
+"Program (or a work based on it, under Section 2) in object code or "
+"executable form under the terms of Sections 1 and 2 above provided that you "
+"also do one of the following:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:233
 #, no-c-format
-msgid "Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with the complete corresponding machine-readable source code, "
+"which must be distributed under the terms of Sections 1 and 2 above on a "
+"medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:241
 #, no-c-format
-msgid "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with a written offer, valid for at least three years, to give "
+"any third party, for a charge no more than your cost of physically "
+"performing source distribution, a complete machine-readable copy of the "
+"corresponding source code, to be distributed under the terms of Sections 1 "
+"and 2 above on a medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:251
 #, no-c-format
-msgid "Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)"
+msgid ""
+"Accompany it with the information you received as to the offer to distribute "
+"corresponding source code. (This alternative is allowed only for "
+"noncommercial distribution and only if you received the program in object "
+"code or executable form with such an offer, in accord with Subsection b "
+"above.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:260
 #, no-c-format
-msgid "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."
+msgid ""
+"The source code for a work means the preferred form of the work for making "
+"modifications to it. For an executable work, complete source code means all "
+"the source code for all modules it contains, plus any associated interface "
+"definition files, plus the scripts used to control compilation and "
+"installation of the executable. However, as a special exception, the source "
+"code distributed need not include anything that is normally distributed (in "
+"either source or binary form) with the major components (compiler, kernel, "
+"and so on) of the operating system on which the executable runs, unless that "
+"component itself accompanies the executable."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:273
 #, no-c-format
-msgid "If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code."
+msgid ""
+"If distribution of executable or object code is made by offering access to "
+"copy from a designated place, then offering equivalent access to copy the "
+"source code from the same place counts as distribution of the source code, "
+"even though third parties are not compelled to copy the source along with "
+"the object code."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:281
 #, no-c-format
-msgid "<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."
+msgid ""
+"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, "
+"or distribute the Program except as expressly provided under this License. "
+"Any attempt otherwise to copy, modify, sublicense or distribute the Program "
+"is void, and will automatically terminate your rights under this License. "
+"However, parties who have received copies, or rights, from you under this "
+"License will not have their licenses terminated so long as such parties "
+"remain in full compliance."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:292
 #, no-c-format
-msgid "<emphasis role=\"bold\">5.</emphasis> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
+msgid ""
+"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this "
+"License, since you have not signed it. However, nothing else grants you "
+"permission to modify or distribute the Program or its derivative works. "
+"These actions are prohibited by law if you do not accept this License. "
+"Therefore, by modifying or distributing the Program (or any work based on "
+"the Program), you indicate your acceptance of this License to do so, and all "
+"its terms and conditions for copying, distributing or modifying the Program "
+"or works based on it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:304
 #, no-c-format
-msgid "<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."
+msgid ""
+"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program "
+"(or any work based on the Program), the recipient automatically receives a "
+"license from the original licensor to copy, distribute or modify the Program "
+"subject to these terms and conditions. You may not impose any further "
+"restrictions on the recipients' exercise of the rights granted herein. You "
+"are not responsible for enforcing compliance by third parties to this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:315
 #, no-c-format
-msgid "<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
+msgid ""
+"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court "
+"judgment or allegation of patent infringement or for any other reason (not "
+"limited to patent issues), conditions are imposed on you (whether by court "
+"order, agreement or otherwise) that contradict the conditions of this "
+"License, they do not excuse you from the conditions of this License. If you "
+"cannot distribute so as to satisfy simultaneously your obligations under "
+"this License and any other pertinent obligations, then as a consequence you "
+"may not distribute the Program at all. For example, if a patent license "
+"would not permit royalty-free redistribution of the Program by all those who "
+"receive copies directly or indirectly through you, then the only way you "
+"could satisfy both it and this License would be to refrain entirely from "
+"distribution of the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:332
 #, no-c-format
-msgid "If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances."
+msgid ""
+"If any portion of this section is held invalid or unenforceable under any "
+"particular circumstance, the balance of the section is intended to apply and "
+"the section as a whole is intended to apply in other circumstances."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:339
 #, no-c-format
-msgid "It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
+msgid ""
+"It is not the purpose of this section to induce you to infringe any patents "
+"or other property right claims or to contest validity of any such claims; "
+"this section has the sole purpose of protecting the integrity of the free "
+"software distribution system, which is implemented by public license "
+"practices. Many people have made generous contributions to the wide range of "
+"software distributed through that system in reliance on consistent "
+"application of that system; it is up to the author/donor to decide if he or "
+"she is willing to distribute software through any other system and a "
+"licensee cannot impose that choice."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:352
 #, no-c-format
-msgid "This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License."
+msgid ""
+"This section is intended to make thoroughly clear what is believed to be a "
+"consequence of the rest of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:357
 #, no-c-format
-msgid "<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License."
+msgid ""
+"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the "
+"Program is restricted in certain countries either by patents or by "
+"copyrighted interfaces, the original copyright holder who places the Program "
+"under this License may add an explicit geographical distribution limitation "
+"excluding those countries, so that distribution is permitted only in or "
+"among countries not thus excluded. In such case, this License incorporates "
+"the limitation as if written in the body of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:368
 #, no-c-format
-msgid "<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \"any later version\", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
+msgid ""
+"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may "
+"publish revised and/or new versions of the General Public License from time "
+"to time. Such new versions will be similar in spirit to the present version, "
+"but may differ in detail to address new problems or concerns. Each version "
+"is given a distinguishing version number. If the Program specifies a version "
+"number of this License which applies to it and \"any later version\", you "
+"have the option of following the terms and conditions either of that version "
+"or of any later version published by the Free Software Foundation. If the "
+"Program does not specify a version number of this License, you may choose "
+"any version ever published by the Free Software Foundation."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:383
 #, no-c-format
-msgid "<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally."
+msgid ""
+"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of "
+"the Program into other free programs whose distribution conditions are "
+"different, write to the author to ask for permission. For software which is "
+"copyrighted by the Free Software Foundation, write to the Free Software "
+"Foundation; we sometimes make exceptions for this. Our decision will be "
+"guided by the two goals of preserving the free status of all derivatives of "
+"our free software and of promoting the sharing and reuse of software "
+"generally."
 msgstr ""
 
 #. Tag: emphasis
@@ -285,13 +510,31 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:399
 #, no-c-format
-msgid "<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION."
+msgid ""
+"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE "
+"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY "
+"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT "
+"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY "
+"OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE "
+"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. "
+"THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH "
+"YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL "
+"NECESSARY SERVICING, REPAIR OR CORRECTION."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:412
 #, no-c-format
-msgid "<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgid ""
+"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY "
+"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY "
+"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED "
+"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, "
+"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO "
+"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING "
+"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE "
+"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR "
+"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
 msgstr ""
 
 #. Tag: emphasis
@@ -309,87 +552,111 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:434
 #, no-c-format
-msgid "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."
+msgid ""
+"If you develop a new program, and you want it to be of the greatest possible "
+"use to the public, the best way to achieve this is to make it free software "
+"which everyone can redistribute and change under these terms."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:441
 #, no-c-format
-msgid "To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \"copyright\" line and a pointer to where the full notice is found."
+msgid ""
+"To do so, attach the following notices to the program. It is safest to "
+"attach them to the start of each source file to most effectively convey the "
+"exclusion of warranty; and each file should have at least the \"copyright\" "
+"line and a pointer to where the full notice is found."
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:448
 #, no-c-format
 msgid ""
-      "<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable>\n"
-      "Copyright (C) <replaceable>year  name of author</replaceable>\n"
-      "\n"
-      "This program is free software; you can redistribute it and/or\n"
-      "modify it under the terms of the GNU General Public License\n"
-      "as published by the Free Software Foundation; either version 2\n"
-      "of the License, or (at your option) any later version.\n"
-      "\n"
-      "This program is distributed in the hope that it will be useful,\n"
-      "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
-      "MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
-      "GNU General Public License for more details.\n"
-      "\n"
-      "You should have received a copy of the GNU General Public License\n"
-      "along with this program; if not, write to the Free Software\n"
-      "Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA."
+"<replaceable>one line to give the program's name and a brief idea of what it "
+"does.</replaceable>\n"
+"Copyright (C) <replaceable>year  name of author</replaceable>\n"
+"\n"
+"This program is free software; you can redistribute it and/or\n"
+"modify it under the terms of the GNU General Public License\n"
+"as published by the Free Software Foundation; either version 2\n"
+"of the License, or (at your option) any later version.\n"
+"\n"
+"This program is distributed in the hope that it will be useful,\n"
+"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
+"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
+"GNU General Public License for more details.\n"
+"\n"
+"You should have received a copy of the GNU General Public License\n"
+"along with this program; if not, write to the Free Software\n"
+"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, "
+"USA."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:450
 #, no-c-format
-msgid "Also add information on how to contact you by electronic and paper mail."
+msgid ""
+"Also add information on how to contact you by electronic and paper mail."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:455
 #, no-c-format
-msgid "If the program is interactive, make it output a short notice like this when it starts in an interactive mode:"
+msgid ""
+"If the program is interactive, make it output a short notice like this when "
+"it starts in an interactive mode:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:460
 #, no-c-format
 msgid ""
-      "Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable>\n"
-      "Gnomovision comes with absolutely no warranty; for details\n"
-      "type `show w'. This is free software, and you are welcome\n"
-      "to redistribute it under certain conditions; type `show c'\n"
-      "for details."
+"Gnomovision version 69, Copyright (C) <replaceable>year name of author</"
+"replaceable>\n"
+"Gnomovision comes with absolutely no warranty; for details\n"
+"type `show w'. This is free software, and you are welcome\n"
+"to redistribute it under certain conditions; type `show c'\n"
+"for details."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:462
 #, no-c-format
-msgid "The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items &mdash; whatever suits your program."
+msgid ""
+"The hypothetical commands `show w' and `show c' should show the appropriate "
+"parts of the General Public License. Of course, the commands you use may be "
+"called something other than `show w' and `show c'; they could even be mouse-"
+"clicks or menu items &mdash; whatever suits your program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:470
 #, no-c-format
-msgid "You should also get your employer (if you work as a programmer) or your school, if any, to sign a \"copyright disclaimer\" for the program, if necessary. Here is a sample; alter the names:"
+msgid ""
+"You should also get your employer (if you work as a programmer) or your "
+"school, if any, to sign a \"copyright disclaimer\" for the program, if "
+"necessary. Here is a sample; alter the names:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:476
 #, no-c-format
 msgid ""
-      "Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
-      "program `Gnomovision' (which makes passes at compilers) written\n"
-      "by James Hacker.\n"
-      "\n"
-      "<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
-      "Ty Coon, President of Vice"
+"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
+"program `Gnomovision' (which makes passes at compilers) written\n"
+"by James Hacker.\n"
+"\n"
+"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
+"Ty Coon, President of Vice"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:478
 #, no-c-format
-msgid "This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
+msgid ""
+"This General Public License does not permit incorporating your program into "
+"proprietary programs. If your program is a subroutine library, you may "
+"consider it more useful to permit linking proprietary applications with the "
+"library. If this is what you want to do, use the GNU Lesser General Public "
+"License instead of this License."
 msgstr ""
-
diff --git a/po/nn/hardware.po b/po/nn/hardware.po
index c3e0c1251..96af36f01 100644
--- a/po/nn/hardware.po
+++ b/po/nn/hardware.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:7
 #, no-c-format
-msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;."
+msgid ""
+"This section contains information about what hardware you need to get "
+"started with &debian;. You will also find links to further information about "
+"hardware supported by GNU and &arch-kernel;."
 msgstr ""
 
 #. Tag: title
@@ -34,13 +38,23 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;."
+msgid ""
+"&debian; does not impose hardware requirements beyond the requirements of "
+"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
+"architecture or platform to which the Linux or kFreeBSD kernel, libc, "
+"<command>gcc</command>, etc. have been ported, and for which a &debian; port "
+"exists, can run &debian;. Please refer to the Ports pages at <ulink url="
+"\"&url-ports;\"></ulink> for more details on &arch-title; architecture "
+"systems which have been tested with &debian-gnu;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:32
 #, no-c-format
-msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found."
+msgid ""
+"Rather than attempting to describe all the different hardware configurations "
+"which are supported for &arch-title;, this section contains general "
+"information and pointers to where additional information can be found."
 msgstr ""
 
 #. Tag: title
@@ -52,7 +66,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid ""
+"&debian; GNU/Linux &release; supports eleven major architectures and several "
+"variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -430,19 +446,38 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:203
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are "
+"looking for information on any of the other &debian;-supported architectures "
+"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-"
+"Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
+msgid ""
+"The &arch-title; architecture only supports Intel Itanium processors and not "
+"the much more common 64-bit processors from the Intel 64 family (including e."
+"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
+"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
+"userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:223
 #, no-c-format
-msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
+msgid ""
+"This is the first official release of &debian-gnu; for the &arch-title; "
+"architecture. We feel that it has proven itself sufficiently to be released. "
+"However, because it has not had the exposure (and hence testing by users) "
+"that some other architectures have had, you may encounter a few bugs. Use "
+"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any "
+"problems; make sure to mention the fact that the bug is on the &arch-title; "
+"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
+"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
@@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
+#: hardware.xml:522 hardware.xml:575
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -466,13 +502,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:273
 #, no-c-format
-msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
+msgid ""
+"Each distinct ARM architecture requires its own kernel. Because of this the "
+"standard &debian; distribution only supports installation on a number of the "
+"most common platforms. The &debian; userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:282
 #, no-c-format
-msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
+msgid ""
+"Most ARM CPUs may be run in either endian mode (big or little). However, the "
+"majority of current system implementation uses little-endian mode. &debian; "
+"currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
@@ -490,7 +533,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:298
 #, no-c-format
-msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
+msgid ""
+"Intel's I/O Processor (IOP) line is found in a number of products related to "
+"data storage and processing. &debian; currently supports the IOP32x "
+"platform, featuring the IOP 80219 and 32x chips commonly found in Network "
+"Attached Storage (NAS) devices. &debian; explicitly supports two such "
+"devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from "
+"IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -502,7 +551,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:312
 #, no-c-format
-msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
+msgid ""
+"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
+"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
+"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
+"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
+"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
+"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
+"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
+"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
@@ -514,7 +571,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:329
 #, no-c-format
-msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
+msgid ""
+"Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, "
+"Ethernet, SATA, USB, and other functionality in one chip. There are many "
+"Network Attached Storage (NAS) devices on the market that are based on an "
+"Orion chip. We currently support the following Orion based devices: <ulink "
+"url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url="
+"\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
+"cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -526,19 +590,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:344
 #, no-c-format
-msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
+msgid ""
+"The Versatile platform is emulated by QEMU and is therefore a nice way to "
+"test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:363
 #, no-c-format
-msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
+msgid ""
+"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-"
+"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit "
+"processors whereas the 2.0 architecture is targeted to the 64-bit "
+"processors. Some systems are able to run either kernel. In both cases, the "
+"userland is 32-bit. There is the possibility of a 64-bit userland in the "
+"future."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:382
 #, no-c-format
-msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
+msgid ""
+"Complete information concerning supported peripherals can be found at <ulink "
+"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. "
+"This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
@@ -550,19 +625,43 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:391
 #, no-c-format
-msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
+msgid ""
+"Nearly all x86-based (IA-32) processors still in use in personal computers "
+"are supported, including all varieties of Intel's \"Pentium\" series. This "
+"also includes 32-bit AMD and VIA (former Cyrix) processors, and processors "
+"like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:398
 #, no-c-format
-msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
+msgid ""
+"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run "
+"on 386 or earlier processors. Despite the architecture name \"i386\", "
+"support for actual 80386 processors (and their clones) was dropped with the "
+"Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to "
+"avoid this, but in the end it was necessary due a unfortunate series of "
+"issues with the compiler and the kernel, starting with an bug in the C++ ABI "
+"provided by GCC. You should still be able to run &debian; GNU/Linux on "
+"actual 80386 processors if you compile your own kernel and compile all "
+"packages from source, but that is beyond the scope of this manual. </para> </"
+"footnote>. (No version of Linux has ever supported the 286 or earlier chips "
+"in the series.) All i486 and later processors are still supported<footnote> "
+"<para> Many &debian; packages will actually run slightly faster on modern "
+"computers as a positive side effect of dropping support for these old chips. "
+"The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) "
+"which the i386, introduced in 1986, did not have. Previously, these could "
+"not be easily used by most &debian; packages; now they can. </para> </"
+"footnote>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+msgid ""
+"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
+"you will probably want to use the installer for the amd64 architecture "
+"instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
@@ -574,31 +673,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:441
 #, no-c-format
-msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
+msgid ""
+"The system bus is the part of the motherboard which allows the CPU to "
+"communicate with peripherals such as storage devices. Your computer must use "
+"the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called "
+"the VL bus). Essentially all personal computers sold in recent years use one "
+"of these."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:465
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, "
+"Indigo 2 and Challenge S. Since these machines are very similar, whenever "
+"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant "
+"as well. </para></listitem> <listitem><para> SGI IP32: this platform is "
+"generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: "
+"this platform is emulated by QEMU and is therefore a nice way to test and "
+"run &debian; on MIPS if you don't have the hardware. </para></listitem> </"
+"itemizedlist> Complete information regarding supported mips/mipsel machines "
+"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</"
+"ulink>. In the following, only the systems supported by the &debian; "
+"installer will be covered. If you are looking for support for other "
+"subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> "
+"debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
+msgid ""
+"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and "
+"R5000 processors are supported by the &debian; installation system on big "
+"endian MIPS. On SGI IP32, currently only systems based on the R5000 are "
+"supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
+msgid ""
+"Some MIPS machines can be operated in both big and little endian mode. For "
+"little endian MIPS, please read the documentation for the mipsel "
+"architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:523
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are "
+"covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway "
+"Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform "
+"is emulated by QEMU and is therefore a nice way to test and run &debian; on "
+"MIPS if you don't have the hardware. </para></listitem> </itemizedlist> "
+"Complete information regarding supported mips/mipsel machines can be found "
+"at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the "
+"following, only the systems supported by the &debian; installer will be "
+"covered. If you are looking for support for other subarchitectures, please "
+"contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; "
+"mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -610,7 +747,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:553
 #, no-c-format
-msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
+msgid ""
+"All MIPS based Cobalt machines are supported with the exception of the Qube "
+"2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
@@ -628,7 +767,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:576
 #, no-c-format
-msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
+msgid ""
+"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
+"PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +781,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:599
 #, no-c-format
-msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
+msgid ""
+"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -652,7 +795,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:607
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid ""
+"Most systems use this kernel flavour, which supports the PowerPC 601, 603, "
+"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and "
+"including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
@@ -670,19 +816,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:622
 #, no-c-format
-msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
+msgid ""
+"The POWER3 processor is used in older IBM 64-bit server systems: known "
+"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, "
+"and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:628
 #, no-c-format
-msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
+msgid ""
+"The POWER4 processor is used in more recent IBM 64-bit server systems: known "
+"models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:633
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid ""
+"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
+"architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
@@ -694,25 +847,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:669
 #, no-c-format
-msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
+msgid ""
+"Apple (and briefly a few other manufacturers &mdash; Power Computing, for "
+"example) made a series of Macintosh computers based on the PowerPC "
+"processor. For purposes of architecture support, they are categorized as "
+"NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:676
 #, no-c-format
-msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
+msgid ""
+"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI "
+"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld "
+"machines. Those pre-iMac PowerPC models from Apple use a four digit naming "
+"scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:684
 #, no-c-format
-msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
+msgid ""
+"The so called NewWorld PowerMacs are any PowerMacs in translucent colored "
+"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, "
+"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. "
+"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</"
+"quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:692
 #, no-c-format
-msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
+msgid ""
+"Specifications for Apple hardware are available at <ulink url=\"http://www."
+"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older "
+"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/"
+"index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
@@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
+#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
+#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
+#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
+#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
+#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
+#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
+#: hardware.xml:825
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -1084,7 +1261,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:933
 #, no-c-format
-msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
+msgid ""
+"NuBus systems are not currently supported by &debian;/powerpc. The "
+"monolithic Linux/PPC kernel architecture does not have support for these "
+"machines; instead, one must use the MkLinux Mach microkernel, which &debian; "
+"does not yet support. These include the following: <itemizedlist> "
+"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> "
+"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> "
+"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> "
+"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </"
+"itemizedlist> A linux kernel for these machines and limited support is "
+"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1096,19 +1283,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:972
 #, no-c-format
-msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
+msgid ""
+"Macintosh computers using the 680x0 series of processors are <emphasis>not</"
+"emphasis> in the PowerPC family but are instead m68k machines. Those models "
+"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> "
+"family, then the Centris series, and culminate in the Quadras and Performas. "
+"These models usually have a Roman numeral or 3-digit model number such as "
+"Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:981
 #, no-c-format
-msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
+msgid ""
+"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, "
+"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, "
+"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra "
+"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the "
+"Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:989
 #, no-c-format
-msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
+msgid ""
+"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs "
+"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, "
+"please see the section above)."
 msgstr ""
 
 #. Tag: title
@@ -1120,7 +1321,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1006
 #, no-c-format
-msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
+msgid ""
+"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
+"Your machine needs to support the z/Architecture, 64-bit support is "
+"mandatory. The userland of the s390 port is still compiled for ESA/390, "
+"though. All zSeries and System z hardware is fully supported. &arch-title; "
+"support software is included from the kernel 3.1 development stream. The "
+"most current information about IBM's Linux support can be found at the "
+"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
+"development_technical.html\"> Linux on <trademark class=\"registered"
+"\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1132,7 +1342,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1024
 #, no-c-format
-msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
+msgid ""
+"PAV and HyperPAV are supported transparently, multipathing is not needed to "
+"take advantage of these storage system features. Be sure to configure the "
+"devices during DASD device selection. The alias devices will not be offered "
+"neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
@@ -1144,7 +1358,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1041
 #, no-c-format
-msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
+msgid ""
+"Sparc-based hardware is divided into a number of different subarchitectures, "
+"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u "
+"or sun4v. The following list describes what machines they include and what "
+"level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
@@ -1156,13 +1374,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1054
 #, no-c-format
-msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
+msgid ""
+"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a "
+"complete list of machines belonging to these subarchitectures, please "
+"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation"
+"\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1061
 #, no-c-format
-msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
+msgid ""
+"The last &debian; release to support sparc32 was Etch, but even then only "
+"for sun4m systems. Support for the other 32-bits subarchitectures had "
+"already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
@@ -1174,7 +1399,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1073
 #, no-c-format
-msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
+msgid ""
+"This subarchitecture includes all 64-bit machines (sparc64) based on the "
+"UltraSparc processor and its clones. Most of the machines are well "
+"supported, even though for some you may experience problems booting from CD "
+"due to firmware or bootloader bugs (this problem may be worked around by "
+"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP "
+"configurations respectively."
 msgstr ""
 
 #. Tag: term
@@ -1186,13 +1417,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1088
 #, no-c-format
-msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
+msgid ""
+"This is the newest addition to the Sparc family, which includes machines "
+"based on the Niagara multi-core CPUs. At the moment such CPUs are only "
+"available in T1000 and T2000 servers by Sun, and are well supported. Use the "
+"sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1099
 #, no-c-format
-msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
+msgid ""
+"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
+"not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
@@ -1204,7 +1441,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1109
 #, no-c-format
-msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
+msgid ""
+"From a technical point of view, laptops are normal PCs, so all information "
+"regarding PC systems applies to laptops as well. Installations on laptops "
+"nowadays usually work out of the box, including things like automatically "
+"suspending the system on closing the lid and laptop specfic hardware buttons "
+"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
+"Nonetheless sometimes the hardware vendors use specialized or proprietary "
+"hardware for some laptop-specific functions which might not be supported. To "
+"see if your particular laptop works well with GNU/Linux, see for example the "
+"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1216,61 +1462,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1127
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. Having multiple "
+"processors in a computer was originally only an issue for high-end server "
+"systems but has become quite common in recent years even for rather low-end "
+"desktop computers and laptops with the introduction of so called "
+"<quote>multi-core</quote> processors. These contain two or more processor "
+"units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1137
 #, no-c-format
-msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
+msgid ""
+"The standard &debian; &release; kernel image has been compiled with SMP "
+"support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1148
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. The standard "
+"&debian; &release; kernel image has been compiled with <firstterm>SMP-"
+"alternatives</firstterm> support. This means that the kernel will detect the "
+"number of processors (or processor cores) and will automatically deactivate "
+"SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1157
 #, no-c-format
-msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Having multiple processors in a computer was originally only an issue for "
+"high-end server systems but has become quite common in recent years even for "
+"rather low-end desktop computers and laptops with the introduction of so "
+"called <quote>multi-core</quote> processors. These contain two or more "
+"processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1165
 #, no-c-format
-msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
+msgid ""
+"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
+"not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1175
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. However, the "
+"standard &debian; &release; kernel image does not support SMP. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1184
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a "
+"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this "
+"time (kernel version &kernelversion;) the way you enable SMP is to select "
+"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</"
+"quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1198
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture, and is supported "
+"by a precompiled &debian; kernel image. Depending on your install media, "
+"this SMP-capable kernel may or may not be installed by default. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1208
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
+msgid ""
+"In order to take advantage of multiple processors, you should check to see "
+"if a kernel package that supports SMP is installed, and if not, choose an "
+"appropriate kernel package."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1214
 #, no-c-format
-msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"You can also build your own customized kernel to support SMP.<phrase arch="
+"\"linux-any\"> You can find a discussion of how to do this in <xref linkend="
+"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way "
+"you enable SMP is to select <quote>&smp-config-option;</quote> in the "
+"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1282,13 +1575,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1226
 #, no-c-format
-msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
+msgid ""
+"&debian;'s support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. On modern PCs, having a graphical "
+"display usually works out of the box. Whether advanced graphics card "
+"features such as 3D-hardware acceleration or hardware-accelerated video are "
+"available, depends on the actual graphics hardware used in the system and in "
+"some cases on the installation of additional <quote>firmware</quote> images "
+"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
+"been reports about hardware on which installation of additional graphics "
+"card firmware was required even for basic graphics support, but these have "
+"been rare exceptions."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1239
 #, no-c-format
-msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
+msgid ""
+"Details on supported graphics cards and pointing devices can be found at "
+"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
+"version &x11ver;."
 msgstr ""
 
 #. Tag: para
@@ -1300,13 +1606,31 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1249
 #, no-c-format
-msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
+msgid ""
+"Most graphics options commonly found on Sparc-based machines are supported. "
+"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, "
+"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), "
+"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards "
+"(glint driver). To use an Elite3D card with X.org you additionally need to "
+"install the <classname>afbinit</classname> package, and read the "
+"documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1259
 #, no-c-format
-msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
+msgid ""
+"It is not uncommon for a Sparc machine to have two graphics cards in a "
+"default configuration. In such a case there is a possibility that the Linux "
+"kernel will not direct its output to the card initially used by the "
+"firmware. The lack of output on the graphical console may then be mistaken "
+"for a hang (usually the last message seen on console is 'Booting Linux...'). "
+"One possible solution is to physically remove one of the video cards; "
+"another option is to disable one of the cards using a kernel boot parameter. "
+"Also, if graphical output is not required or desired, serial console may be "
+"used as an alternative. On some systems use of serial console can be "
+"activated automatically by disconnecting the keyboard before booting the "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -1318,13 +1642,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1282
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
+msgid ""
+"Almost any network interface card (NIC) supported by the &arch-kernel; "
+"kernel should also be supported by the installation system; drivers should "
+"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
+"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
+"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1292
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+msgid ""
+"This includes a lot of generic PCI cards (for systems that have PCI) and the "
+"following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
@@ -1384,7 +1715,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1349
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
+msgid ""
+"On &arch-title;, most built-in Ethernet devices are supported and modules "
+"for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
@@ -1402,31 +1735,52 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1362
 #, no-c-format
-msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
+msgid ""
+"Wireless networking is in general supported as well and a growing number of "
+"wireless adapters are supported by the official &arch-kernel; kernel, "
+"although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1369
 #, no-c-format
-msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
+msgid ""
+"If firmware is needed, the installer will prompt you to load firmware. See "
+"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
+"firmware during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1374
 #, no-c-format
-msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
+msgid ""
+"Wireless NICs that are not supported by the official &arch-kernel; kernel "
+"can generally be made to work under &debian-gnu;, but are not supported "
+"during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1379
 #, no-c-format
-msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
+msgid ""
+"If there is a problem with wireless and there is no other NIC you can use "
+"during the installation, it is still possible to install &debian-gnu; using "
+"a full CD-ROM or DVD image. Select the option to not configure a network and "
+"install using only the packages available from the CD/DVD. You can then "
+"install the driver and firmware you need after the installation is completed "
+"(after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1389
 #, no-c-format
-msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
+msgid ""
+"In some cases the driver you need may not be available as a &debian; "
+"package. You will then have to look if there is source code available in the "
+"internet and compile the driver yourself. How to do this is outside the "
+"scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, "
+"your last resort is to use the <classname>ndiswrapper</classname> package, "
+"which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1438,7 +1792,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1404
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid ""
+"There are a couple of issues with specific network cards that are worth "
+"mentioning here."
 msgstr ""
 
 #. Tag: title
@@ -1450,19 +1806,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1413
 #, no-c-format
-msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
+msgid ""
+"There are various PCI network cards that have the same PCI identification, "
+"but are supported by related, but different drivers. Some cards work with "
+"the <literal>tulip</literal> driver, others with the <literal>dfme</literal> "
+"driver. Because they have the same identification, the kernel cannot "
+"distinguish between them and it is not certain which driver will be loaded. "
+"If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1423
 #, no-c-format
-msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
+msgid ""
+"This is a common problem on Netra systems with a Davicom (DEC-Tulip "
+"compatible) NIC. In that case the <literal>tulip</literal> driver is "
+"probably the correct one. You can prevent this issue by blacklisting the "
+"wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1431
 #, no-c-format
-msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
+msgid ""
+"An alternative solution during the installation is to switch to a shell and "
+"unload the wrong driver module using <userinput>modprobe -r "
+"<replaceable>module</replaceable></userinput> (or both, if they are both "
+"loaded). After that you can load the correct module using "
+"<userinput>modprobe <replaceable>module</replaceable></userinput>. Note that "
+"the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
@@ -1474,7 +1846,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1446
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid ""
+"The <literal>cassini</literal> network driver does not work with Sun B100 "
+"blade systems."
 msgstr ""
 
 #. Tag: title
@@ -1486,7 +1860,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1462
 #, no-c-format
-msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
+msgid ""
+"Support for braille displays is determined by the underlying support found "
+"in <classname>brltty</classname>. Most displays work under "
+"<classname>brltty</classname>, connected via either a serial port, USB or "
+"bluetooth. Details on supported braille devices can be found on the <ulink "
+"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
+"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
@@ -1498,7 +1878,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1477
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
+msgid ""
+"Support for hardware speech synthesis devices is determined by the "
+"underlying support found in <classname>speakup</classname>. "
+"<classname>speakup</classname> only supports integrated boards and external "
+"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
+"are supported). Details on supported hardware speech synthesis devices can "
+"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
+"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
+"classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
@@ -1510,25 +1898,37 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1498
 #, no-c-format
-msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
+msgid ""
+"&arch-kernel; supports a large variety of hardware devices such as mice, "
+"printers, scanners, PCMCIA and USB devices. However, most of these devices "
+"are not required while installing the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1504
 #, no-c-format
-msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
+msgid ""
+"USB hardware generally works fine. On some very old PC systems some USB "
+"keyboards may require additional configuration (see <xref linkend=\"hardware-"
+"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
+"any specific configuration."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1513
 #, no-c-format
-msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
+msgid ""
+"Package installations from XPRAM and tape are not supported by this system. "
+"All packages that you want to install need to be available on a DASD or over "
+"the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1519
 #, no-c-format
-msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Cobalt RaQ has no support for additional devices but the Qube has one "
+"PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -1540,31 +1940,63 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1532
 #, no-c-format
-msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
+msgid ""
+"Besides the availability of a device driver, some hardware also requires so-"
+"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> "
+"to be loaded into the device before it can become operational. This is most "
+"common for network interface cards (especially wireless NICs), but for "
+"example some USB devices and even some hard disk controllers also require "
+"firmware. With many graphics cards, basic functionality is available without "
+"additional firmware, but the use of advanced features requires an "
+"appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1543
 #, no-c-format
-msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
+msgid ""
+"On many older devices which require firmware to work, the firmware file was "
+"permanently placed in an EEPROM/Flash chip on the device itself by the "
+"manufacturer. Nowadays most new devices do not have the firmware embedded "
+"this way anymore, so the firmware file must be uploaded into the device by "
+"the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1551
 #, no-c-format
-msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
+msgid ""
+"In most cases firmware is non-free according to the criteria used by the "
+"&debian-gnu; project and thus cannot be included in the main distribution or "
+"in the installation system. If the device driver itself is included in the "
+"distribution and if &debian-gnu; legally can distribute the firmware, it "
+"will often be available as a separate package from the non-free section of "
+"the archive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1560
 #, no-c-format
-msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
+msgid ""
+"However, this does not mean that such hardware cannot be used during an "
+"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
+"firmware files or packages containing firmware from a removable medium, such "
+"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
+"information on how to load firmware files or packages during the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1569
 #, no-c-format
-msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
+msgid ""
+"If the &d-i; prompts for a firmware file and you do not have this firmware "
+"file available or do not want to install a non-free firmware file on your "
+"system, you can try to proceed without loading the firmware. There are "
+"several cases where a driver prompts for additional firmware because it may "
+"be needed under certain circumstances, but the device does work without it "
+"on most systems (this e.g. happens with certain network cards using the tg3 "
+"driver)."
 msgstr ""
 
 #. Tag: title
@@ -1576,19 +2008,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1588
 #, no-c-format
-msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
+msgid ""
+"There are several vendors, who ship systems with &debian; or other "
+"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</"
+"ulink>. You might pay more for the privilege, but it does buy a level of "
+"peace of mind, since you can be sure that the hardware is well-supported by "
+"GNU/Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1596
 #, no-c-format
-msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
+msgid ""
+"If you do have to buy a machine with Windows bundled, carefully read the "
+"software license that comes with Windows; you may be able to reject the "
+"license and obtain a rebate from your vendor. Searching the Internet for "
+"<quote>windows refund</quote> may get you some useful information to help "
+"with that."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1604
 #, no-c-format
-msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
+"even a used system, it is still important to check that your hardware is "
+"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
+"the references found above. Let your salesperson (if any) know that you're "
+"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
+"vendors."
 msgstr ""
 
 #. Tag: title
@@ -1600,31 +2048,67 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1616
 #, no-c-format
-msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
+msgid ""
+"Some hardware manufacturers simply won't tell us how to write drivers for "
+"their hardware. Others won't allow us access to the documentation without a "
+"non-disclosure agreement that would prevent us from releasing the driver's "
+"source code, which is one of the central elements of free software. Since we "
+"haven't been granted access to usable documentation on these devices, they "
+"simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1626
 #, no-c-format
-msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
+msgid ""
+"In many cases there are standards (or at least some de-facto standards) "
+"describing how an operating system and its device drivers communicate with a "
+"certain class of devices. All devices which comply to such a (de-facto-)"
+"standard can be used with a single generic device driver and no device-"
+"specific drivers are required. With some kinds of hardware (e.g. USB "
+"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
+"mass storage devices like USB flash disks and memory card readers) this "
+"works very well and practically every device sold in the market is standards-"
+"compliant."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1638
 #, no-c-format
-msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
+msgid ""
+"In other fields, among them e.g. printers, this is unfortunately not the "
+"case. While there are many printers which can be addressed via a small set "
+"of (de-facto-)standard control languages and therefore can be made to work "
+"without problems in any operating system, there are quite a few models which "
+"only understand proprietary control commands for which no usable "
+"documentation is available and therefore either cannot be used at all on "
+"free operating systems or can only be used with a vendor-supplied closed-"
+"source driver."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1649
 #, no-c-format
-msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
+msgid ""
+"Even if there is a vendor-provided closed-source driver for such hardware "
+"when purchasing the device, the practical lifespan of the device is limited "
+"by driver availability. Nowadays product cycles have become short and it is "
+"not uncommon that a short time after a consumer device has ceased "
+"production, no driver updates get made available any more by the "
+"manufacturer. If the old closed-source driver does not work anymore after a "
+"system update, an otherwise perfectly working device becomes unusable due to "
+"lacking driver support and there is nothing that can be done in this case. "
+"You should therefore avoid buying closed hardware in the first place, "
+"regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1662
 #, no-c-format
-msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
+msgid ""
+"You can help improve this situation by encouraging manufacturers of closed "
+"hardware to release the documentation and other resources necessary for us "
+"to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
@@ -1636,7 +2120,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1679
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
+msgid ""
+"This section will help you determine which different media types you can use "
+"to install &debian;. There is a whole chapter devoted to media, <xref "
+"linkend=\"install-methods\"/>, which lists the advantages and disadvantages "
+"of each media type. You may want to refer back to this page once you reach "
+"that section."
 msgstr ""
 
 #. Tag: title
@@ -1648,7 +2137,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
+msgid ""
+"In some cases, you'll have to do your first boot from floppy disks. "
+"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch "
+"floppy drive."
 msgstr ""
 
 #. Tag: para
@@ -1666,7 +2158,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1705
 #, no-c-format
-msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
+msgid ""
+"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-"
+"ROMs and DVD-ROMs, because both technologies are really the same from the "
+"operating system's point of view."
 msgstr ""
 
 #. Tag: para
@@ -1684,7 +2179,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1719
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid ""
+"USB CD-ROM drives are also supported, as are FireWire devices that are "
+"supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
@@ -1696,7 +2193,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1728
 #, no-c-format
-msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
+msgid ""
+"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of "
+"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM "
+"drives sold on the PC market do not have this capability. If your CD-ROM "
+"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</"
+"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. "
+"To start the install, simply choose the <quote>System installation</quote> "
+"entry in the firmware."
 msgstr ""
 
 #. Tag: title
@@ -1708,7 +2212,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1744
 #, no-c-format
-msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
+msgid ""
+"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
+"cheap storage device. Most modern computer systems also allow booting the &d-"
+"i; from such a stick. Many modern computer systems, in particular netbooks "
+"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
+"from USB media ist the standard way of installing a new operating system on "
+"them."
 msgstr ""
 
 #. Tag: title
@@ -1720,19 +2230,36 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1758
 #, no-c-format
-msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
+msgid ""
+"The network can be used during the installation to retrieve files needed for "
+"the installation. Whether the network is used or not depends on the "
+"installation method you choose and your answers to certain questions that "
+"will be asked during the installation. The installation system supports most "
+"types of network connections (including PPPoE, but not ISDN or PPP), via "
+"either HTTP or FTP. After the installation is completed, you can also "
+"configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1768
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> the installation system over the "
+"network without needing any local media like CDs/DVDs or USB sticks. If you "
+"already have a netboot-infrastructure available (i.e. you are already "
+"running DHCP and TFTP services in your network), this allows an easy and "
+"fast deployment of a large number of machines. Setting up the necessary "
+"infrastructure requires a certain level of technical experience, so this is "
+"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the "
+"preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1781
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+msgid ""
+"Diskless installation, using network booting from a local area network and "
+"NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
@@ -1744,13 +2271,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1792
 #, no-c-format
-msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
+msgid ""
+"Booting the installation system directly from a hard disk is another option "
+"for many architectures. This will require some other operating system to "
+"load the installer onto the hard disk. This method is only recommended for "
+"special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1799
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid ""
+"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
+"can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
@@ -1762,7 +2295,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1810
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian-gnu; without using the &d-i; described in the rest of this manual. "
+"This kind of install may be useful for users with otherwise unsupported "
+"hardware or on hosts which can't afford downtime. If you are interested in "
+"this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This "
+"installation method is only recommended for advanced users when no other "
+"installation method is available."
 msgstr ""
 
 #. Tag: title
@@ -1774,43 +2314,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1825
 #, no-c-format
-msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
+msgid ""
+"The &debian; installer contains a kernel which is built to maximize the "
+"number of systems it runs on."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1829
 #, no-c-format
-msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+msgid ""
+"Generally, the &debian; installation system includes support for IDE (also "
+"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
+"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
+"(VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1846
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. The following SCSI drivers are supported in the default kernel: "
+"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> "
+"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec "
+"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></"
+"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also "
+"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC "
+"Processors FAQ</ulink> for more information on SPARC hardware supported by "
+"the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1879
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support floppies on "
+"CHRP systems at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support the floppy "
+"drive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1891
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1896
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This means that FBA and ECKD DASDs are supported with the old "
+"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
@@ -1822,12 +2388,22 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1915
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space to perform a normal installation. Note that these are fairly "
+"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-"
+"hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1922
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgid ""
+"Installation on systems with less memory<footnote condition=\"gtk\"> <para> "
+"Installation images that support the graphical installer require more memory "
+"than images that support only the textual installer and should not be used "
+"on systems with less than &minimum-memory; of memory. If there is a choice "
+"between booting the regular and the graphical installer, the former should "
+"be selected. </para> </footnote> or disk space available may be possible but "
+"is only advised for experienced users."
 msgstr ""
-
diff --git a/po/nn/install-methods.po b/po/nn/install-methods.po
index c164d8428..6f56f6790 100644
--- a/po/nn/install-methods.po
+++ b/po/nn/install-methods.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,1149 +29,1719 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian-gnu; is from an Official &debian; CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/DVD-ROM images from a &debian; mirror and make your own set, if you have a fast network connection and a CD/DVD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, which is the case on all modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/>. Much effort has been expended to ensure the most-used files are on the first CDs and DVDs, so that a basic desktop installation can be done with only the first DVD or - to a limited extent - even with only the first CD."
+msgid ""
+"By far the easiest way to install &debian-gnu; is from an Official &debian; "
+"CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-"
+"debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/"
+"DVD-ROM images from a &debian; mirror and make your own set, if you have a "
+"fast network connection and a CD/DVD burner (see the <ulink url=\"&url-"
+"debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;"
+"\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; "
+"CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, "
+"which is the case on all modern PCs</phrase>, you can skip right to <xref "
+"linkend=\"boot-installer\"/>. Much effort has been expended to ensure the "
+"most-used files are on the first CDs and DVDs, so that a basic desktop "
+"installation can be done with only the first DVD or - to a limited extent - "
+"even with only the first CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid ""
+"As CDs have a rather limited capacity by today's standards, not all "
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid ""
+"If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
+"relevant on very old PC systems)</phrase>, but you do have a CD set, you can "
+"use an alternative strategy such as <phrase condition=\"supports-floppy-boot"
+"\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition="
+"\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net "
+"boot,</phrase> or manually loading the kernel from the CD to initially boot "
+"the system installer. The files you need for booting by another means are "
+"also on the CD; the &debian; network archive and CD folder organization are "
+"identical. So when archive file paths are given below for particular files "
+"you need for booting, look for those files in the same directories and "
+"subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
-msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a &debian; mirror using FTP, be sure to download "
+"the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
-msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each &debian; mirror in the directory "
+"<ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
-msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
+msgid ""
+"A firmware image is provided for the Thecus N2100 which will automatically "
+"boot <classname>debian-installer</classname>. This image can be installed "
+"using the Thecus firmware upgrade process. This firmware image can be "
+"obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
-msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
+msgid ""
+"The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
+"on which you intend to install &debian;. These images can be obtained from "
+"&glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
-msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
+msgid ""
+"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
+"disk on which you intend to install &debian;. These images can be obtained "
+"from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
-msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
+msgid ""
+"A firmware image is provided for the HP mv2120 which will automatically boot "
+"<classname>debian-installer</classname>. This image can be installed with "
+"uphpmvault on Linux and other systems and with the HP Media Vault Firmware "
+"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-"
+"firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
-msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
+msgid ""
+"The installation files for the QNAP Turbo Station consist of a kernel and "
+"ramdisk as well as a script to write these images to flash. You can obtain "
+"the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
+"kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
-msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
+msgid ""
+"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
+"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
+"obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
-msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
+msgid ""
+"The installation files for LaCie NASes (Network Space v2, Network Space Max "
+"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
+"consist of a kernel and initrd for U-Boot. You can obtain these files from "
+"&lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
-msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
+msgid ""
+"Bootable floppy disks are generally used as a last resort to boot the "
+"installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
-msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
+msgid ""
+"Booting the installer from floppy disk reportedly fails on Mac USB floppy "
+"drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images. This "
+"section describes how to create floppies from disk images on different "
+"platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
-msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
+msgid ""
+"Before you can create the floppies, you will first need to download them "
+"from one of the &debian; mirrors, as explained in <xref linkend="
+"\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an "
+"installation CD-ROM or DVD, the floppy images may also be included on the CD/"
+"DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
-msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
+msgid ""
+"No matter which method you use to create your floppies, you should remember "
+"to flip the write-protect tab on the floppies once you have written them, to "
+"ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
-      "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
-      "$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-      "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> (on Solaris, use <command>eject</command>, see the manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:337
+"To write the floppy disk image files to the floppy disks, you will probably "
+"need root access to the system. Place a good, blank floppy in the floppy "
+"drive. Next, use the command <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly "
+"used name of the floppy disk device, it may be different on your "
+"workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</"
+"filename>)</phrase>. The command may return to the prompt before Unix has "
+"finished writing the floppy disk, so look for the disk-in-use light on the "
+"floppy drive and be sure that the light is out and the disk has stopped "
+"revolving before you remove it from the drive. On some systems, you'll have "
+"to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> "
+"(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:336
 #, no-c-format
-msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+msgid ""
+"Some systems attempt to automatically mount a floppy disk when you place it "
+"in the drive. You might have to disable this feature before the workstation "
+"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
+"management to get raw access to the floppy. First, make sure that the floppy "
+"is auto-mounted (using <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
-msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 or amd64 machine, you can use one of the "
+"following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> programs can "
+"be used under MS-DOS. To use these programs, first make sure that you are "
+"booted into DOS. Trying to use these programs from within a DOS box in "
+"Windows, or double-clicking on these programs from the Windows Explorer is "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
-msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
+msgid ""
+"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
+"ME, XP and probably later versions. To use it you will need to unpack diskio."
+"dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
-msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official &debian; CD-ROMs under the "
+"<filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
-msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
+msgid ""
+"An AppleScript, <application>Make &debian; Floppy</application>, is "
+"available for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on "
+"your desktop, and then drag any floppy image file to it. You must have "
+"Applescript installed and enabled in your extensions manager. Disk Copy will "
+"ask you to confirm that you wish to erase the floppy and proceed to write "
+"the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> file is an example of a floppy image. Use one of the following "
+"methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian-gnu; CD, then the Type and Creator are already set "
+"correctly. The following <command>Creator-Changer</command> steps are only "
+"necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> image file from the "
+"resulting dialog. It will ask you to insert a floppy, then ask if you really "
+"want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
-msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
+msgid ""
+"To prepare the USB stick, you will need a system where GNU/Linux is already "
+"running and where USB is supported. With current GNU/Linux systems the USB "
+"stick should be automatically recognized when you insert it. If it is not "
+"you should check that the usb-storage kernel module is loaded. When the USB "
+"stick is inserted, it will be mapped to a device named <filename>/dev/sdX</"
+"filename>, where the <quote>X</quote> is a letter in the range a-z. You "
+"should be able to see to which device the USB stick was mapped by running "
+"the command <command>dmesg</command> after inserting it. To write to your "
+"stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
-msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
+msgid ""
+"The procedures described in this section will destroy anything already on "
+"the device! Make very sure that you use the correct device name for your USB "
+"stick. If you use the wrong device the result could be that all information "
+"on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
-msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
+msgid ""
+"Debian CD and DVD images can now be written directly a USB stick, which is a "
+"very easy way to make a bootable USB stick. Simply choose a CD or DVD image "
+"that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to "
+"get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
-msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
+msgid ""
+"Alternatively, for very small USB sticks, only a few megabytes in size, you "
+"can download the <filename>mini.iso</filename> image from the "
+"<filename>netboot</filename> directory (at the location mentioned in <xref "
+"linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
-msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
+msgid ""
+"A special method can be used to add firmware to the <filename>mini.iso</"
+"filename>. First, write the <filename>mini.iso</filename> to the USB stick. "
+"Next obtain the necessary firmware files. See <xref linkend=\"loading-"
+"firmware\"/> for more information about firmware. Now unplug and replug the "
+"USB stick, and two partitions should now be visible on it. You should mount "
+"the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
-      "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
-      "# cd /mnt\n"
-      "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
-      "# cd /\n"
-      "# umount"
+"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
+"# cd /mnt\n"
+"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
+"# cd /\n"
+"# umount"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
-msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
+msgid ""
+"The CD or DVD image you choose should be written directly to the USB stick, "
+"overwriting its current contents. For example, when using an existing GNU/"
+"Linux system, the CD or DVD image file can be written to a USB stick as "
+"follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
-      "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
-      "<prompt>#</prompt> <userinput>sync</userinput>"
+"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
+"<replaceable>sdX</replaceable></userinput>\n"
+"<prompt>#</prompt> <userinput>sync</userinput>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
-msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
+msgid ""
+"Simply writing the CD or DVD image to USB like this should work fine for "
+"most users. The other options below are more complex, mainly for people with "
+"specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
-msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"An alternative way to set up your USB stick is to manually copy the "
+"installer files, and also a CD image to it. Note that the USB stick should "
+"be at least 1 GB in size (smaller setups are possible if you follow <xref "
+"linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
-msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
+msgid ""
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) <phrase arch="
+"\"x86\">as well as <classname>syslinux</classname> and its configuration "
+"file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</"
+"classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
-msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
+msgid ""
+"Note that, although convenient, this method does have one major "
+"disadvantage: the logical size of the device will be limited to 1 GB, even "
+"if the capacity of the USB stick is larger. You will need to repartition the "
+"USB stick and create new file systems to get its full capacity back if you "
+"ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
-msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
+msgid ""
+"Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
+"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract "
+"the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
-msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"After that, mount the USB memory stick <phrase arch=\"x86\">"
+"(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</"
+"phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</"
+"replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch="
+"\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS "
+"filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
+"CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
+"are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
-msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
+msgid ""
+"If you like more flexibility or just want to know what's going on, you "
+"should use the following method to put the files on your stick. One "
+"advantage of using this method is that &mdash; if the capacity of your USB "
+"stick is large enough &mdash; you have the option of copying a full CD ISO "
+"image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
-msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to set up the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
-      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
-      "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
+"Since most USB sticks come pre-configured with a single FAT16 partition, you "
+"probably won't have to repartition or reformat the stick. If you have to do "
+"that anyway, use <command>cfdisk</command> or any other partitioning tool to "
+"create a FAT16 partition<footnote> <para> Don't forget to set the "
+"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR "
+"using: <informalexample><screen>\n"
+"# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+"</screen></informalexample> The <command>install-mbr</command> command is "
+"contained in the <classname>mbr</classname> &debian; package. Then create "
+"the filesystem using: <informalexample><screen>\n"
+"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. Although any boot loader (e.g. <classname>lilo</"
+"classname>) should work, it's convenient to use <classname>syslinux</"
+"classname>, since it uses a FAT16 partition and can be reconfigured by just "
+"editing a text file. Any operating system which supports the FAT file system "
+"can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
-      "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
-      "# syslinux /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>syslinux</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"To put <classname>syslinux</classname> on the FAT16 partition on your USB "
+"stick, install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
+"# syslinux /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>syslinux</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick: "
+"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or "
+"<filename>linux</filename> (kernel binary) </para></listitem> "
+"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </"
+"para></listitem> </itemizedlist> You can choose between either the regular "
+"version or the graphical version of the installer. The latter can be found "
+"in the <filename>gtk</filename> subdirectory. If you want to rename the "
+"files, please note that <classname>syslinux</classname> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
-      "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
-      "default vmlinuz\n"
-      "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
+"Next you should create a <filename>syslinux.cfg</filename> configuration "
+"file, which at a bare minimum should contain the following two lines (change "
+"the name of the kernel binary to <quote><filename>linux</filename></quote> "
+"if you used a <filename>netboot</filename> image): "
+"<informalexample><screen>\n"
+"default vmlinuz\n"
+"append initrd=initrd.gz\n"
+"</screen></informalexample> For the graphical installer you should add "
+"<userinput>vga=788</userinput> to the second line. Other parameters can be "
+"appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
-msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgid ""
+"To enable the boot prompt to permit further parameter appending, add a "
+"<userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
-msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
+msgid ""
+"If you used an <filename>hd-media</filename> image, you should now copy the "
+"ISO file of a &debian; ISO image<footnote> <para> You can use either a "
+"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure "
+"to select one that fits. Note that the <quote>netboot <filename>mini.iso</"
+"filename></quote> image is not usable for this purpose. </para> </footnote> "
+"onto the stick. When you are done, unmount the USB memory stick "
+"(<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
-      "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
-      "$ hformat /dev/<replaceable>sdX2</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> &debian; package."
+"Most USB sticks do not come pre-configured in such a way that Open Firmware "
+"can boot from them, so you will need to repartition the stick. On Mac "
+"systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></"
+"userinput>, initialise a new partition map using the <userinput>i</"
+"userinput> command, and create a new partition of type Apple_Bootstrap using "
+"the <userinput>C</userinput> command. (Note that the first \"partition\" "
+"will always be the partition map itself.) Then type "
+"<informalexample><screen>\n"
+"$ hformat /dev/<replaceable>sdX2</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> boot loader can be "
+"installed on an HFS filesystem and can be reconfigured by just editing a "
+"text file. Any operating system which supports the HFS file system can be "
+"used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
-      "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
-      "$ hmount /dev/<replaceable>sdX2</replaceable>\n"
-      "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
-      "$ hattrib -c UNIX -t tbxi :yaboot\n"
-      "$ hattrib -b :\n"
-      "$ humount\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:857
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
+"$ hmount /dev/<replaceable>sdX2</replaceable>\n"
+"$ hcopy -r /usr/lib/yaboot/yaboot :\n"
+"$ hattrib -c UNIX -t tbxi :yaboot\n"
+"$ hattrib -b :\n"
+"$ humount\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be otherwise mounted during this procedure. "
+"This procedure writes the boot loader to the partition, and uses the HFS "
+"utilities to mark it in such a way that Open Firmware will boot it. Having "
+"done this, the rest of the USB stick may be prepared using the normal Unix "
+"utilities."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:856
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
-      "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
-      "default=install\n"
-      "root=/dev/ram\n"
-      "\n"
-      "message=/boot.msg\n"
-      "\n"
-      "image=/vmlinux\n"
-      "        label=install\n"
-      "        initrd=/initrd.gz\n"
-      "        initrd-size=10000\n"
-      "        read-only\n"
-      "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
+"default=install\n"
+"root=/dev/ram\n"
+"\n"
+"message=/boot.msg\n"
+"\n"
+"image=/vmlinux\n"
+"        label=install\n"
+"        initrd=/initrd.gz\n"
+"        initrd-size=10000\n"
+"        read-only\n"
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
-msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
+msgid ""
+"The installer may be booted using boot files placed on an existing hard "
+"drive partition, either launched from another operating system or by "
+"invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
-msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+msgid ""
+"The installer cannot boot from files on an HFS+ file system. MacOS System "
+"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To "
+"determine whether your existing file system is HFS+, select <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
-msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
+msgid ""
+"At boot time, both bootloaders support loading in memory not only the "
+"kernel, but also a disk image. This RAM disk can be used as the root file-"
+"system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
-msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the &debian; archives to a convenient location "
+"on your hard drive (note that LILO can not boot from files on an NTFS file "
+"system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
-msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
+msgid ""
+"This section explains how to prepare your hard drive for booting the "
+"installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
-msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
+msgid ""
+"Copy the following directories from a &debian; CD image to <filename>c:\\</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
-msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
+msgid ""
+"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your &debian; installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on &debian; http/ftp mirrors and official &debian; CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
-msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+msgid ""
+"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
+"well as loading ELF binaries directly from the hard disk. These machines "
+"will boot Linux directly via <command>yaboot</command>, which supports "
+"loading a kernel and RAMdisk directly from an ext2 partition, as well as "
+"dual-booting with MacOS. Hard disk booting of the installer is particularly "
+"appropriate for newer machines without floppy drives. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (not move) the following four files which you "
+"downloaded earlier from the &debian; archives, onto the root level of your "
+"hard drive (this can be accomplished by <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the <command>L</command> command to check for the partition number. You "
+"will need this partition number for the command you type at the Open "
+"Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
-msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
+msgid ""
+"If your machine is connected to a local area network, you may be able to "
+"boot it over the network from another machine, using TFTP. If you intend to "
+"boot the installation system from another machine, the boot files will need "
+"to be placed in specific locations on that machine, and the machine "
+"configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
-msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
+msgid ""
+"You need to set up a TFTP server, and for many machines a DHCP server<phrase "
+"condition=\"supports-rarp\">, or RARP server</phrase><phrase condition="
+"\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol.</phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image.</phrase> The DHCP "
+"(Dynamic Host Configuration Protocol) is a more flexible, backwards-"
+"compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
-msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
+msgid ""
+"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
+"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
+"boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
-msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
+msgid ""
+"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
+"the client. Theoretically, any server, on any platform, which implements "
+"these protocols, may be used. In the examples in this section, we shall "
+"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
-msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
+msgid ""
+"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
+"It's written by the same author as the <classname>syslinux</classname> "
+"bootloader and is therefore least likely to cause issues. A good alternative "
+"is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
-msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
+msgid ""
+"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>ip addr show dev eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
+msgid ""
+"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
+"you use the <command>rarpd</command> program. You need to ensure that the "
+"Ethernet hardware address for the client is listed in the <quote>ethers</"
+"quote> database (either in the <filename>/etc/ethers</filename> file, or via "
+"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start "
+"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</"
+"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/"
+"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/"
+"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
+"gnu;, the <classname>dhcp3-server</classname> package is recommended. Here "
+"is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</"
+"filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
-      "option domain-name \"example.com\";\n"
-      "option domain-name-servers ns1.example.com;\n"
-      "option subnet-mask 255.255.255.0;\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "server-name \"servername\";\n"
-      "\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option routers 192.168.1.1;\n"
-      "}\n"
-      "\n"
-      "host clientname {\n"
-      "  filename \"/tftpboot.img\";\n"
-      "  server-name \"servername\";\n"
-      "  next-server servername;\n"
-      "  hardware ethernet 01:23:45:67:89:AB;\n"
-      "  fixed-address 192.168.1.90;\n"
-      "}"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1237
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+"  filename \"/tftpboot.img\";\n"
+"  server-name \"servername\";\n"
+"  next-server servername;\n"
+"  hardware ethernet 01:23:45:67:89:AB;\n"
+"  fixed-address 192.168.1.90;\n"
+"}"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1236
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
-#, no-c-format
-msgid ""
-      "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
-      "option domain-name \"example.com\";\n"
-      "\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "\n"
-      "allow booting;\n"
-      "allow bootp;\n"
-      "\n"
-      "# The next paragraph needs to be modified to fit your case\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option broadcast-address 192.168.1.255;\n"
-      "# the gateway address which can be different\n"
-      "# (access to the internet for instance)\n"
-      "  option routers 192.168.1.1;\n"
-      "# indicate the dns you want to use\n"
-      "  option domain-name-servers 192.168.1.3;\n"
-      "}\n"
-      "\n"
-      "group {\n"
-      "  next-server 192.168.1.3;\n"
-      "  host tftpclient {\n"
-      "# tftp client hardware address\n"
-      "  hardware ethernet  00:10:DC:27:6C:15;\n"
-      "  filename \"pxelinux.0\";\n"
-      " }\n"
-      "}\n"
-      "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+#: install-methods.xml:1255
+#, no-c-format
+msgid ""
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different\n"
+"# (access to the internet for instance)\n"
+"  option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+"  option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"group {\n"
+"  next-server 192.168.1.3;\n"
+"  host tftpclient {\n"
+"# tftp client hardware address\n"
+"  hardware ethernet  00:10:DC:27:6C:15;\n"
+"  filename \"pxelinux.0\";\n"
+" }\n"
+"}\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux. The first is CMU "
+"<command>bootpd</command>. The other is actually a DHCP server: ISC "
+"<command>dhcpd</command>. In &debian-gnu; these are contained in the "
+"<classname>bootp</classname> and <classname>dhcp3-server</classname> "
+"packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
-      "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
-      "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-      "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
-      "client:\\\n"
-      "  hd=/tftpboot:\\\n"
-      "  bf=tftpboot.img:\\\n"
-      "  ip=192.168.1.90:\\\n"
-      "  sm=255.255.255.0:\\\n"
-      "  sa=192.168.1.1:\\\n"
-      "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1318
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you "
+"can run <userinput>update-inetd --enable bootps</userinput>, then "
+"<userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your "
+"BOOTP server does not run &debian;, the line in question should look like: "
+"<informalexample><screen>\n"
+"bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
+"client:\\\n"
+"  hd=/tftpboot:\\\n"
+"  bf=tftpboot.img:\\\n"
+"  ip=192.168.1.90:\\\n"
+"  sm=255.255.255.0:\\\n"
+"  sa=192.168.1.1:\\\n"
+"  ha=0123456789AB:\n"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI machines you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1317
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd."
+"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/"
+"init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
-msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
+msgid ""
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
-msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
+msgid ""
+"In the case of <classname>tftpd-hpa</classname> there are two ways the "
+"service can be run. It can be started on demand by the system's "
+"<classname>inetd</classname> daemon, or it can be set up to run as an "
+"independent daemon. Which of these methods is used is selected when the "
+"package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
-msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
+msgid ""
+"Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
+"to serve images from. However, &debian-gnu; packages may use other "
+"directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by "
+"default uses <filename>/srv/tftp</filename>. You may have to adjust the "
+"configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
-msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
+msgid ""
+"All <command>in.tftpd</command> alternatives available in &debian; should "
+"log TFTP requests to the system logs by default. Some of them support a "
+"<userinput>-v</userinput> argument to increase verbosity. It is recommended "
+"to check these log messages in case of boot problems as they are a good "
+"starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
-      "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
-      "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
-      "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-      "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"If you intend to install &debian; on an SGI machine and your TFTP server is "
+"a GNU/Linux box running Linux 2.4, you'll need to set the following on your "
+"server: <informalexample><screen>\n"
+"# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets "
+"are sent from a source port no greater than 32767, or the download will "
+"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
+"the PROM, and you can avoid it by setting <informalexample><screen>\n"
+"# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. You may "
+"have to make a link from that file to the file which <command>tftpd</"
+"command> will use for booting a particular client. Unfortunately, the file "
+"name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. You will need to download the following files from the "
+"<filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
-      "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-      "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
-      "</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"Some SPARC architectures add the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your "
+"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename "
+"would be <filename>C0A80103.SUN4C</filename>. However, there are also "
+"subarchitectures where the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. An easy way to determine the "
+"hexadecimal code for the IP address is to enter the following command in a "
+"shell (assuming the machine's intended IP is 10.0.0.4). "
+"<informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> To get to the correct filename, you will need to "
+"change all letters to uppercase and if necessary append the subarchitecture "
+"name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
-msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
+msgid ""
+"If you've done all this correctly, giving the command <userinput>boot net</"
+"userinput> from the OpenPROM should load the image. If the image cannot be "
+"found, try checking the logs on your tftp server to see which image name is "
+"being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
-msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+msgid ""
+"You can also force some sparc systems to look for a specific file name by "
+"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
-msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI machines you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. &debian; packages intended for this include <classname>fai-"
+"quickstart</classname> (which can use an install server) and the &debian; "
+"Installer itself. Have a look at the <ulink url=\"http://fai-project.org"
+"\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
-msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
+msgid ""
+"The &debian; Installer supports automating installs via preconfiguration "
+"files. A preconfiguration file can be loaded from the network or from "
+"removable media, and used to fill in answers to questions asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
-msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Full documentation on preseeding including a working example that you can "
+"edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-
diff --git a/po/nn/installation-howto.po b/po/nn/installation-howto.po
index 6b8f358e5..369f718c1 100644
--- a/po/nn/installation-howto.po
+++ b/po/nn/installation-howto.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:7
 #, no-c-format
-msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document."
+msgid ""
+"This document describes how to install &debian-gnu; &releasename; for the "
+"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a "
+"quick walkthrough of the installation process which should contain all the "
+"information you will need for most installs. When more information can be "
+"useful, we will link to more detailed explanations in other parts of this "
+"document."
 msgstr ""
 
 #. Tag: title
@@ -34,7 +41,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:20
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)."
+msgid ""
+"<phrase condition=\"unofficial-build\"> The debian-installer is still in a "
+"beta state. </phrase> If you encounter bugs during your install, please "
+"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report "
+"them. If you have questions which cannot be answered by this document, "
+"please direct them to the debian-boot mailing list (&email-debian-boot-"
+"list;) or ask on IRC (#debian-boot on the OFTC network)."
 msgstr ""
 
 #. Tag: title
@@ -46,19 +59,30 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:37
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>."
+msgid ""
+"<phrase condition=\"unofficial-build\"> For some quick links to CD images, "
+"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> "
+"The debian-cd team provides builds of CD images using &d-i; on the <ulink "
+"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on "
+"where to get CDs, see <xref linkend=\"official-cdrom\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:47
 #, no-c-format
-msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on &debian; mirrors."
+msgid ""
+"Some installation methods require other images than CD images. <phrase "
+"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home "
+"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files"
+"\"/> explains how to find images on &debian; mirrors."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:57
 #, no-c-format
-msgid "The subsections below will give the details about which images you should get for each possible means of installation."
+msgid ""
+"The subsections below will give the details about which images you should "
+"get for each possible means of installation."
 msgstr ""
 
 #. Tag: title
@@ -70,13 +94,26 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:67
 #, no-c-format
-msgid "The netinst CD image is a popular image which can be used to install &releasename; with the &d-i;. This image is intended to boot from CD and install additional packages over a network; hence the name 'netinst'. The image has the software components needed to run the installer and the base packages to provide a minimal &releasename; system. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set."
+msgid ""
+"The netinst CD image is a popular image which can be used to install "
+"&releasename; with the &d-i;. This image is intended to boot from CD and "
+"install additional packages over a network; hence the name 'netinst'. The "
+"image has the software components needed to run the installer and the base "
+"packages to provide a minimal &releasename; system. If you'd rather, you can "
+"get a full size CD image which will not need the network to install. You "
+"only need the first CD of the set."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:77
 #, no-c-format
-msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>"
+msgid ""
+"Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-"
+"x86\">To boot the CD, you may need to change your BIOS configuration, as "
+"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc"
+"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while "
+"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -88,31 +125,50 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:92
 #, no-c-format
-msgid "If you can't boot from CD, you can download floppy images to install &debian;. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks."
+msgid ""
+"If you can't boot from CD, you can download floppy images to install "
+"&debian;. You need the <filename>floppy/boot.img</filename>, the "
+"<filename>floppy/root.img</filename> and one or more of the driver disks."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:98
 #, no-c-format
-msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy &mdash; use the one with <filename>root.img</filename> on it."
+msgid ""
+"The boot floppy is the one with <filename>boot.img</filename> on it. This "
+"floppy, when booted, will prompt you to insert a second floppy &mdash; use "
+"the one with <filename>root.img</filename> on it."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:104
 #, no-c-format
-msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>."
+msgid ""
+"If you're planning to install over the network, you will usually need the "
+"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, "
+"and some less common network cards, you will also need a second driver "
+"floppy, <filename>floppy/net-drivers-2.img</filename>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:111
 #, no-c-format
-msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD."
+msgid ""
+"If you have a CD, but cannot boot from it, then boot from floppies and use "
+"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the "
+"install using the CD."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:117
 #, no-c-format
-msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them."
+msgid ""
+"Floppy disks are one of the least reliable media around, so be prepared for "
+"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each "
+"<filename>.img</filename> file you downloaded goes on a single floppy; you "
+"can use the dd command to write it to /dev/fd0 or some other means (see "
+"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than "
+"one floppy, it's a good idea to label them."
 msgstr ""
 
 #. Tag: title
@@ -124,37 +180,62 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:131
 #, no-c-format
-msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy &debian; install medium that you can take with you anywhere."
+msgid ""
+"It's also possible to install from removable USB storage devices. For "
+"example a USB keychain can make a handy &debian; install medium that you can "
+"take with you anywhere."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:137
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download any Debian "
+"CD or DVD image that will fit on it, and write the CD image directly to the "
+"memory stick. Of course this will destroy anything already on the memory "
+"stick. This works because Debian CD images are \"isohybrid\" images that can "
+"boot both from CD and from USB drives."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:145
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from that file. Write this image directly to your memory stick, which must be at least 1 GB in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download <filename>hd-"
+"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from "
+"that file. Write this image directly to your memory stick, which must be at "
+"least 1 GB in size. Of course this will destroy anything already on the "
+"memory stick. Then mount the memory stick, which will now have a FAT "
+"filesystem on it. Next, download a &debian; netinst CD image, and copy that "
+"file to the memory stick; any filename is ok as long as it ends in <literal>."
+"iso</literal>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:156
 #, no-c-format
-msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
+msgid ""
+"There are other, more flexible ways to set up a memory stick to use the "
+"debian-installer, and it's possible to get it to work with smaller memory "
+"sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:162
 #, no-c-format
-msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Some BIOSes can boot USB storage directly, and some cannot. You may need to "
+"configure your BIOS to boot from a <quote>removable drive</quote> or even a "
+"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful "
+"hints and details, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:169
 #, no-c-format
-msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Booting Macintosh systems from USB storage devices involves manual use of "
+"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: title
@@ -166,13 +247,22 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:179
 #, no-c-format
-msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;."
+msgid ""
+"It's also possible to boot &d-i; completely from the net. The various "
+"methods to netboot depend on your architecture and netboot setup. The files "
+"in <filename>netboot/</filename> can be used to netboot &d-i;."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:185
 #, no-c-format
-msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The easiest thing to set up is probably PXE netbooting. Untar the file "
+"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</"
+"filename> or wherever is appropriate for your tftp server. Set up your DHCP "
+"server to pass filename <filename>pxelinux.0</filename> to clients, and with "
+"luck everything will just work. For detailed instructions, see <xref linkend="
+"\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -184,7 +274,15 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:200
 #, no-c-format
-msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>"
+msgid ""
+"It's possible to boot the installer using no removable media, but just an "
+"existing hard disk, which can have a different OS on it. Download "
+"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</"
+"filename>, and a &debian; CD image to the top-level directory of the hard "
+"disk. Make sure that the CD image has a filename ending in <literal>.iso</"
+"literal>. Now it's just a matter of booting linux with the initrd. <phrase "
+"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -196,91 +294,156 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:218
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
+msgid ""
+"Once the installer starts, you will be greeted with an initial screen. Press "
+"&enterkey; to boot, or read the instructions for other boot methods and "
+"parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:224
 #, no-c-format
-msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
+msgid ""
+"After a while you will be asked to select your language. Use the arrow keys "
+"to pick a language and press &enterkey; to continue. Next you'll be asked to "
+"select your country, with the choices including countries where your "
+"language is spoken. If it's not on the short list, a list of all the "
+"countries in the world is available."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:232
 #, no-c-format
-msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
+msgid ""
+"You may be asked to confirm your keyboard layout. Choose the default unless "
+"you know better."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:237
 #, no-c-format
-msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
+msgid ""
+"Now sit back while debian-installer detects some of your hardware, and loads "
+"the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:242
 #, no-c-format
-msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
+msgid ""
+"Next the installer will try to detect your network hardware and set up "
+"networking by DHCP. If you are not on a network or do not have DHCP, you "
+"will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:248
 #, no-c-format
-msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones."
+msgid ""
+"The next step is setting up your clock and time zone. The installer will try "
+"to contact a time server on the Internet to ensure the clock is set "
+"correctly. The time zone is based on the country selected earlier and the "
+"installer will only ask to select one if a country has multiple zones."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:255
 #, no-c-format
-msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"Now it is time to partition your disks. First you will be given the "
+"opportunity to automatically partition either an entire drive, or available "
+"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is "
+"recommended for new users or anyone in a hurry. If you do not want to "
+"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:263
 #, no-c-format
-msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size."
+msgid ""
+"If you have an existing DOS or Windows partition that you want to preserve, "
+"be very careful with automatic partitioning. If you choose manual "
+"partitioning, you can use the installer to resize existing FAT or NTFS "
+"partitions to create room for the &debian; install: simply select the "
+"partition and specify its new size."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:270
 #, no-c-format
-msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning."
+msgid ""
+"On the next screen you will see your partition table, how the partitions "
+"will be formatted, and where they will be mounted. Select a partition to "
+"modify or delete it. If you did automatic partitioning, you should just be "
+"able to choose <guimenuitem>Finish partitioning and write changes to disk</"
+"guimenuitem> from the menu to use what it set up. Remember to assign at "
+"least one partition for swap space and to mount a partition on <filename>/</"
+"filename>. For more detailed information on how to use the partitioner, "
+"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend="
+"\"partitioning\"/> has more general information about partitioning."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:283
 #, no-c-format
-msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
+msgid ""
+"Now &d-i; formats your partitions and starts to install the base system, "
+"which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:288
 #, no-c-format
-msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step."
+msgid ""
+"The base system that was installed earlier is a working, but very minimal "
+"installation. To make the system more functional the next step allows you to "
+"install additional packages by selecting tasks. Before packages can be "
+"installed <classname>apt</classname> needs to be configured as that defines "
+"from where the packages will be retrieved. The <quote>Standard system</"
+"quote> task will be selected by default and should normally be installed. "
+"Select the <quote>Desktop environment</quote> task if you would like to have "
+"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> "
+"for additional information about this step."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:300
 #, no-c-format
-msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account."
+msgid ""
+"Installation of the base system is followed by setting up user accounts. By "
+"default you will need to provide a password for the <quote>root</quote> "
+"(administrator) account and information necessary to create one regular user "
+"account."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:307
 #, no-c-format
-msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
+msgid ""
+"The last step is to install a boot loader. If the installer detects other "
+"operating systems on your computer, it will add them to the boot menu and "
+"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to "
+"the master boot record of the first harddrive, which is generally a good "
+"choice. You'll be given the opportunity to override that choice and install "
+"it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:317
 #, no-c-format
-msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>."
+msgid ""
+"&d-i; will now tell you that the installation has finished. Remove the cdrom "
+"or other boot media and hit &enterkey; to reboot your machine. It should "
+"boot up into the newly installed system and allow you to log in. This is "
+"explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:324
 #, no-c-format
-msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
+msgid ""
+"If you need more information on the install process, see <xref linkend=\"d-i-"
+"intro\"/>."
 msgstr ""
 
 #. Tag: title
@@ -292,13 +455,23 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:334
 #, no-c-format
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>."
+msgid ""
+"If you successfully managed an installation with &d-i;, please take time to "
+"provide us with a report. The simplest way to do so is to install the "
+"reportbug package (<command>aptitude install reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:344
 #, no-c-format
-msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
+msgid ""
+"If you did not complete the install, you probably found a bug in debian-"
+"installer. To improve the installer it is necessary that we know about them, "
+"so please take the time to report them. You can use an installation report "
+"to report problems; if the install completely fails, see <xref linkend="
+"\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
@@ -310,6 +483,7 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:357
 #, no-c-format
-msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read <xref linkend=\"post-install\"/>."
+msgid ""
+"We hope that your &debian; installation is pleasant and that you find "
+"&debian; useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
-
diff --git a/po/nn/partitioning.po b/po/nn/partitioning.po
index 5cab7d795..2be4d60bf 100644
--- a/po/nn/partitioning.po
+++ b/po/nn/partitioning.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,57 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
+msgid ""
+"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can "
+"have a single partition containing the entire operating system, "
+"applications, and your personal files. Most people feel that a separate swap "
+"partition is also a necessity, although it's not strictly true. <quote>Swap</"
+"quote> is scratch space for an operating system, which allows the system to "
+"use disk storage as <quote>virtual memory</quote>. By putting swap on a "
+"separate partition, &arch-kernel; can make much more efficient use of it. It "
+"is possible to force &arch-kernel; to use a regular file as swap, but it is "
+"not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid ""
+"Most people choose to give GNU/&arch-kernel; more than the minimum number of "
+"partitions, however. There are two reasons you might want to break up the "
+"file system into a number of smaller partitions. The first is for safety. If "
+"something happens to corrupt the file system, generally only one partition "
+"is affected. Thus, you only have to replace (from the backups you've been "
+"carefully keeping) a portion of your system. At a bare minimum, you should "
+"consider creating what is commonly called a <quote>root partition</quote>. "
+"This contains the most essential components of the system. If any other "
+"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix "
+"the system. This can save you the trouble of having to reinstall the system "
+"from scratch."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:40
 #, no-c-format
-msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed."
+msgid ""
+"The second reason is generally more important in a business setting, but it "
+"really depends on your use of the machine. For example, a mail server "
+"getting spammed with e-mail can easily fill a partition. If you made "
+"<filename>/var/mail</filename> a separate partition on the mail server, most "
+"of the system will remain working even if you get spammed."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:48
 #, no-c-format
-msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?"
+msgid ""
+"The only real drawback to using more partitions is that it is often "
+"difficult to know in advance what your needs will be. If you make a "
+"partition too small then you will either have to reinstall the system or you "
+"will be constantly moving things around to make room in the undersized "
+"partition. On the other hand, if you make the partition too big, you will be "
+"wasting space that could be used elsewhere. Disk space is cheap nowadays, "
+"but why throw your money away?"
 msgstr ""
 
 #. Tag: title
@@ -58,7 +91,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:68
 #, no-c-format
-msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all &debian; systems include these directories:"
+msgid ""
+"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink> for directory and file naming. This standard "
+"allows users and software programs to predict the location of files and "
+"directories. The root level directory is represented simply by the slash "
+"<filename>/</filename>. At the root level, all &debian; systems include "
+"these directories:"
 msgstr ""
 
 #. Tag: entry
@@ -280,37 +319,77 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:142
 #, no-c-format
-msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
+msgid ""
+"The following is a list of important considerations regarding directories "
+"and partitions. Note that disk usage varies widely given system "
+"configuration and specific usage patterns. The recommendations here are "
+"general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
+msgid ""
+"The root partition <filename>/</filename> must always physically contain "
+"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</"
+"filename>, <filename>/lib</filename> and <filename>/dev</filename>, "
+"otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for "
+"the root partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
+msgid ""
+"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</"
+"filename>), libraries (<filename>/usr/lib</filename>), documentation "
+"(<filename>/usr/share/doc</filename>), etc. This is the part of the file "
+"system that generally takes up most space. You should provide at least 500MB "
+"of disk space. This amount should be increased depending on the number and "
+"type of packages you plan to install. A generous workstation or server "
+"installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid ""
+"<filename>/var</filename>: variable data like news articles, e-mails, web "
+"sites, databases, the packaging system cache, etc. will be placed under this "
+"directory. The size of this directory depends greatly on the usage of your "
+"system, but for most people will be dictated by the package management "
+"tool's overhead. If you are going to do a full installation of just about "
+"everything &debian; has to offer, all in one session, setting aside 2 or 3 "
+"GB of space for <filename>/var</filename> should be sufficient. If you are "
+"going to install in pieces (that is to say, install services and utilities, "
+"followed by text stuff, then X, ...), you can get away with 300&ndash;500 "
+"MB. If hard drive space is at a premium and you don't plan on doing major "
+"system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid ""
+"<filename>/tmp</filename>: temporary data created by programs will most "
+"likely go in this directory. 40&ndash;100MB should usually be enough. Some "
+"applications &mdash; including archive manipulators, CD/DVD authoring tools, "
+"and multimedia software &mdash; may use <filename>/tmp</filename> to "
+"temporarily store image files. If you plan to use such applications, you "
+"should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid ""
+"<filename>/home</filename>: every user will put his personal data into a "
+"subdirectory of this directory. Its size depends on how many users will be "
+"using the system and what files are to be stored in their directories. "
+"Depending on your planned usage you should reserve about 100MB for each "
+"user, but adapt this value to your needs. Reserve a lot more space if you "
+"plan to save a lot of multimedia files (pictures, MP3, movies) in your home "
+"directory."
 msgstr ""
 
 #. Tag: title
@@ -322,49 +401,91 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:223
 #, no-c-format
-msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
+msgid ""
+"For new users, personal &debian; boxes, home systems, and other single-user "
+"setups, a single <filename>/</filename> partition (plus swap) is probably "
+"the easiest, simplest way to go. However, if your partition is larger than "
+"around 6GB, choose ext3 as your partition type. Ext2 partitions need "
+"periodic file system integrity checking, and this can cause delays during "
+"booting when the partition is large."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:232
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid ""
+"For multi-user systems or systems with lots of disk space, it's best to put "
+"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</"
+"filename>, and <filename>/home</filename> each on their own partitions "
+"separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid ""
+"You might need a separate <filename>/usr/local</filename> partition if you "
+"plan to install many programs that are not part of the &debian; "
+"distribution. If your machine will be a mail server, you might need to make "
+"<filename>/var/mail</filename> a separate partition. Often, putting "
+"<filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, "
+"is a good idea. If you are setting up a server with lots of user accounts, "
+"it's generally good to have a separate, large <filename>/home</filename> "
+"partition. In general, the partitioning situation varies from computer to "
+"computer depending on its uses."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:252
 #, no-c-format
-msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
+msgid ""
+"For very complex systems, you should see the <ulink url=\"&url-multidisk-"
+"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, "
+"mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:259
 #, no-c-format
-msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
+msgid ""
+"With respect to the issue of swap partition size, there are many views. One "
+"rule of thumb which works well is to use as much swap as you have system "
+"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, "
+"there are exceptions to these rules. If you are trying to solve 10000 "
+"simultaneous equations on a machine with 256MB of memory, you may need a "
+"gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:268
 #, no-c-format
-msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
+msgid ""
+"On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap "
+"partition is 2GB. That should be enough for nearly any installation. "
+"However, if your swap requirements are this high, you should probably try to "
+"spread the swap across different disks (also called <quote>spindles</quote>) "
+"and, if possible, different SCSI or IDE channels. The kernel will balance "
+"swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:278
 #, no-c-format
-msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
+msgid ""
+"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE "
+"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for "
+"another operating system on <filename>/dev/hda1</filename>, a 32MB swap "
+"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/"
+"dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:287
 #, no-c-format
-msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
+msgid ""
+"For an idea of the space taken by tasks you might be interested in adding "
+"after your system installation is complete, check <xref linkend=\"tasksel-"
+"size-list\"/>."
 msgstr ""
 
 #. Tag: title
@@ -376,7 +497,10 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:304
 #, no-c-format
-msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
+msgid ""
+"Linux disks and partition names may be different from other operating "
+"systems. You need to know the names that Linux uses when you create and "
+"mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
@@ -394,37 +518,51 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:322
 #, no-c-format
-msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
+msgid ""
+"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:328
 #, no-c-format
-msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
+msgid ""
+"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, "
+"and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:334
 #, no-c-format
-msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
+msgid ""
+"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as "
+"<filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:340
 #, no-c-format
-msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
+msgid ""
+"The master disk on IDE primary controller is named <filename>/dev/hda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:346
 #, no-c-format
-msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
+msgid ""
+"The slave disk on IDE primary controller is named <filename>/dev/hdb</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:352
 #, no-c-format
-msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
+msgid ""
+"The master and slave disks of the secondary controller can be called "
+"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, "
+"respectively. Newer IDE controllers can actually have two channels, "
+"effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
@@ -436,43 +574,74 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:369
 #, no-c-format
-msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
+msgid ""
+"The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:377
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>sda1</filename> and <filename>sda2</filename> "
+"represent the first and second partitions of the first SCSI disk drive in "
+"your system."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:384
 #, no-c-format
-msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
+msgid ""
+"Here is a real-life example. Let's assume you have a system with 2 SCSI "
+"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk "
+"(at address 2) is then named <filename>sda</filename>, and the second "
+"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 "
+"partitions on it, these will be named <filename>sda1</filename>, "
+"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies "
+"to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:395
 #, no-c-format
-msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
+msgid ""
+"Note that if you have two SCSI host bus adapters (i.e., controllers), the "
+"order of the drives can get confusing. The best solution in this case is to "
+"watch the boot messages, assuming you know the drive models and/or "
+"capacities."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:402
 #, no-c-format
-msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
+msgid ""
+"Linux represents the primary partitions as the drive name, plus the numbers "
+"1 through 4. For example, the first primary partition on the first IDE drive "
+"is <filename>/dev/hda1</filename>. The logical partitions are numbered "
+"starting at 5, so the first logical partition on that same drive is "
+"<filename>/dev/hda5</filename>. Remember that the extended partition, that "
+"is, the primary partition holding the logical partitions, is not usable by "
+"itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:413
 #, no-c-format
-msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
+msgid ""
+"Sun disk partitions allow for 8 separate partitions (or slices). The third "
+"partition is usually (and is preferred to have) the <quote>Whole Disk</"
+"quote> partition. This partition references all of the sectors of the disk, "
+"and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:420
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> "
+"represent the first and second partitions of the first DASD device in your "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -484,7 +653,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:436
 #, no-c-format
-msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
+msgid ""
+"Several varieties of partitioning programs have been adapted by &debian; "
+"developers to work on various types of hard disks and computer "
+"architectures. Following is a list of the program(s) applicable for your "
+"architecture."
 msgstr ""
 
 #. Tag: command
@@ -496,7 +669,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:449
 #, no-c-format
-msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
+msgid ""
+"Recommended partitioning tool in &debian;. This Swiss army knife can also "
+"resize partitions, create filesystems <phrase arch=\"any-x86\"> "
+"(<quote>format</quote> in Windows speak)</phrase> and assign them to the "
+"mountpoints."
 msgstr ""
 
 #. Tag: command
@@ -514,7 +691,12 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:465
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
+msgid ""
+"Be careful if you have existing FreeBSD partitions on your machine. The "
+"installation kernels include support for these partitions, but the way that "
+"<command>fdisk</command> represents them (or not) can make the device names "
+"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</"
+"ulink>."
 msgstr ""
 
 #. Tag: command
@@ -532,7 +714,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:482
 #, no-c-format
-msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
+msgid ""
+"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at "
+"all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
@@ -580,7 +764,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:519
 #, no-c-format
-msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
+msgid ""
+"PowerMac-aware version of <command>fdisk</command>, also used by BVM and "
+"Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
@@ -592,13 +778,21 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:529
 #, no-c-format
-msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
+msgid ""
+"&arch-title; version of <command>fdisk</command>; Please read the fdasd "
+"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/"
+"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and "
+"Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:540
 #, no-c-format
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
+msgid ""
+"One of these programs will be run by default when you select "
+"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible "
+"to use a different partitioning tool from the command line on VT2, but this "
+"is not recommended."
 msgstr ""
 
 #. Tag: para
@@ -610,11 +804,18 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:550
 #, no-c-format
-msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
+msgid ""
+"One key point when partitioning for Mac type disks is that the swap "
+"partition is identified by its name; it must be named <quote>swap</quote>. "
+"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. "
+"Please read the fine manual. We also suggest reading the <ulink url=\"&url-"
+"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you "
+"should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686
+#: partitioning.xml:800 partitioning.xml:877
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
@@ -622,61 +823,138 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:567
 #, no-c-format
-msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
+msgid ""
+"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> "
+"somewhere in the first 2GB. This is where the boot loader and an optional "
+"kernel and RAMdisk will be stored, so make it big enough for that &mdash; at "
+"least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware "
+"is that the Linux kernel must reside within the first 2GB of the disk. This "
+"is typically achieved by making the root ext2 partition fit entirely within "
+"the first 2GB of the disk. Alternatively you can create a small ext2 "
+"partition near the start of the disk and mount that on <filename>/boot</"
+"filename>, since that is the directory where the Linux kernel(s) will be "
+"stored. <filename>/boot</filename> needs to be big enough to hold whatever "
+"kernels (and backups) you might wish to load; 25&ndash;50MB is generally "
+"sufficient."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:591
 #, no-c-format
-msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
+msgid ""
+"If you have an existing other operating system such as DOS or Windows and "
+"you want to preserve that operating system while installing &debian;, you "
+"may need to resize its partition to free up space for the &debian; "
+"installation. The installer supports resizing of both FAT and NTFS "
+"filesystems; when you get to the installer's partitioning step, select the "
+"option <guimenuitem>Manual</guimenuitem> and then simply select an existing "
+"partition and change its size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:601
 #, no-c-format
-msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
+msgid ""
+"The PC BIOS generally adds additional constraints for disk partitioning. "
+"There is a limit to how many <quote>primary</quote> and <quote>logical</"
+"quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 "
+"BIOSes, there are limits to where on the drive the BIOS can boot from. More "
+"information can be found in the <ulink url=\"&url-partition-howto;\">Linux "
+"Partition HOWTO</ulink>, but this section will include a brief overview to "
+"help you plan most situations."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:611
 #, no-c-format
-msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
+msgid ""
+"<quote>Primary</quote> partitions are the original partitioning scheme for "
+"PC disks. However, there can only be four of them. To get past this "
+"limitation, <quote>extended</quote> and <quote>logical</quote> partitions "
+"were invented. By setting one of your primary partitions as an extended "
+"partition, you can subdivide all the space allocated to that partition into "
+"logical partitions. You can create up to 60 logical partitions per extended "
+"partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:622
 #, no-c-format
-msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
+msgid ""
+"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 "
+"usable primary partitions, 252 logical partitions), and 63 partitions on an "
+"IDE drive (3 usable primary partitions, 60 logical partitions). However the "
+"normal &debian-gnu; system provides only 20 devices for partitions, so you "
+"may not install on partitions higher than 20 unless you first manually "
+"create devices for those partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:632
 #, no-c-format
-msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
+msgid ""
+"If you have a large IDE disk, and are using neither LBA addressing, nor "
+"overlay drivers (sometimes provided by hard disk manufacturers), then the "
+"boot partition (the partition containing your kernel image) must be placed "
+"within the first 1024 cylinders of your hard drive (usually around 524 "
+"megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:640
 #, no-c-format
-msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
+msgid ""
+"This restriction doesn't apply if you have a BIOS newer than around "
+"1995&ndash;98 (depending on the manufacturer) that supports the "
+"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the "
+"Linux loader, and &debian;'s alternative <command>mbr</command> must use the "
+"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large "
+"disk access extensions are found to be present, they will be utilized. "
+"Otherwise, the legacy disk access interface is used as a fall-back, and it "
+"cannot be used to address any location on the disk higher than the 1023rd "
+"cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer "
+"has, these restrictions no longer apply, since &arch-kernel; does not use "
+"the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:654
 #, no-c-format
-msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
+msgid ""
+"If you have a large disk, you might have to use cylinder translation "
+"techniques, which you can set from your BIOS setup program, such as LBA "
+"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). "
+"More information about issues with large disks can be found in the <ulink "
+"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a "
+"cylinder translation scheme, and the BIOS does not support the large disk "
+"access extensions, then your boot partition has to fit within the "
+"<emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:666
 #, no-c-format
-msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
+msgid ""
+"The recommended way of accomplishing this is to create a small "
+"(25&ndash;50MB should suffice) partition at the beginning of the disk to be "
+"used as the boot partition, and then create whatever other partitions you "
+"wish to have, in the remaining area. This boot partition <emphasis>must</"
+"emphasis> be mounted on <filename>/boot</filename>, since that is the "
+"directory where the &arch-kernel; kernel(s) will be stored. This "
+"configuration will work on any system, regardless of whether LBA or large "
+"disk CHS translation is used, and regardless of whether your BIOS supports "
+"the large disk access extensions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:687
 #, no-c-format
-msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
+msgid ""
+"The <command>partman</command> disk partitioner is the default partitioning "
+"tool for the installer. It manages the set of partitions and their mount "
+"points to ensure that the disks and filesystems are properly configured for "
+"a successful installation. It actually uses <command>parted</command> to do "
+"the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
@@ -688,28 +966,52 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:700
 #, no-c-format
-msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+msgid ""
+"The IA-64 EFI firmware supports two partition table (or disk label) formats, "
+"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer "
+"recommended for IA-64 systems. Although the installer also provides "
+"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> "
+"<command>parted</command></ulink> because only it can manage both GPT and MS-"
+"DOS tables correctly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:712
 #, no-c-format
-msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
+msgid ""
+"The automatic partitioning recipes for <command>partman</command> allocate "
+"an EFI partition as the first partition on the disk. You can also set up the "
+"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the "
+"main menu in a manner similar to setting up a <emphasis>swap</emphasis> "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:720
 #, no-c-format
 msgid ""
-      "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
-      "      mklabel gpt\n"
-      "      mkpartfs primary fat 0 50\n"
-      "      mkpartfs primary linux-swap 51 1000\n"
-      "      mkpartfs primary ext2 1001 3000\n"
-      "      set 1 boot on\n"
-      "      print\n"
-      "      quit\n"
-      "</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks."
+"The <command>partman</command> partitioner will handle most disk layouts. "
+"For those rare cases where it is necessary to manually set up a disk, you "
+"can use the shell as described above and run the <command>parted</command> "
+"utility directly using its command line interface. Assuming that you want to "
+"erase your whole disk and create a GPT table and some partitions, then "
+"something similar to the following command sequence could be used: "
+"<informalexample><screen>\n"
+"      mklabel gpt\n"
+"      mkpartfs primary fat 0 50\n"
+"      mkpartfs primary linux-swap 51 1000\n"
+"      mkpartfs primary ext2 1001 3000\n"
+"      set 1 boot on\n"
+"      print\n"
+"      quit\n"
+"</screen></informalexample> This creates a new partition table, and three "
+"partitions to be used as an EFI boot partition, swap space, and a root file "
+"system. Finally it sets the boot flag on the EFI partition. Partitions are "
+"specified in Megabytes, with start and end offsets from the beginning of the "
+"disk. So, for example, above we created a 1999MB ext2 file system starting "
+"at offset 1001MB from the start of the disk. Note that formatting swap space "
+"with <command>parted</command> can take a few minutes to complete, as it "
+"scans the partition for bad blocks."
 msgstr ""
 
 #. Tag: title
@@ -721,19 +1023,36 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:746
 #, no-c-format
-msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
+msgid ""
+"ELILO, the IA-64 boot loader, requires a partition containing a FAT file "
+"system with the <userinput>boot</userinput> flag set. The partition must be "
+"big enough to hold the boot loader and any kernels or RAMdisks you may wish "
+"to boot. A minimum size would be about 20MB, but if you expect to run with "
+"multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:755
 #, no-c-format
-msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
+msgid ""
+"The EFI Boot Manager and the EFI Shell fully support the GPT table so the "
+"boot partition does not necessarily have to be the first partition or even "
+"on the same disk. This is convenient if you should forget to allocate the "
+"partition and only find out after you have formatted the other partitions on "
+"your disk(s). The <command>partman</command> partitioner checks for an EFI "
+"partition at the same time it checks for a properly set up <emphasis>root</"
+"emphasis> partition. This gives you an opportunity to correct the disk "
+"layout before the package install begins. The easiest way to correct this "
+"omission is to shrink the last partition of the disk to make enough free "
+"space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:770
 #, no-c-format
-msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
+msgid ""
+"It is strongly recommended that you allocate the EFI boot partition on the "
+"same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -745,13 +1064,27 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:779
 #, no-c-format
-msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
+msgid ""
+"The EFI firmware is significantly more sophisticated than the usual BIOS "
+"seen on most x86 PCs. Some system vendors take advantage of the ability of "
+"the EFI to access files and run programs from a hard disk filesystem to "
+"store diagnostics and EFI based system management utilities on the hard "
+"disk. This is a separate FAT format filesystem on the system disk. Consult "
+"the system documentation and accessories that come with the system for "
+"details. The easiest time to set up a diagnostics partition is at the same "
+"time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:801
 #, no-c-format
-msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
+msgid ""
+"SGI machines require an SGI disk label in order to make the system bootable "
+"from hard disk. It can be created in the fdisk expert menu. The thereby "
+"created volume header (partition number 9) should be at least 3MB large. If "
+"the volume header created is too small, you can simply delete partition "
+"number 9 and re-add it with a different size. Note that the volume header "
+"must start at sector 0."
 msgstr ""
 
 #. Tag: title
@@ -763,48 +1096,94 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:819
 #, no-c-format
-msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
+msgid ""
+"If you are installing onto a NewWorld PowerMac you must create a special "
+"bootstrap partition to hold the boot loader. The size of this partition must "
+"have at least 819200 bytes and its partition type must be "
+"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not "
+"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine "
+"cannot be made bootable from the hard disk. This partition can easily be "
+"created by creating a new partition in <command>partman</command> and "
+"telling it to use it as a <quote>NewWorld boot partition</quote>, or in "
+"<command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:832
 #, no-c-format
-msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
+msgid ""
+"The special partition type Apple_Bootstrap is required to prevent MacOS from "
+"mounting and damaging the bootstrap partition, as there are special "
+"modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:839
 #, no-c-format
-msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
+msgid ""
+"Note that the bootstrap partition is only meant to hold 3 very small files: "
+"the <command>yaboot</command> binary, its configuration <filename>yaboot."
+"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</"
+"command>. It need not and must not be mounted on your file system nor have "
+"kernels or anything else copied to it. The <command>ybin</command> and "
+"<command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:849
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
+msgid ""
+"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap "
+"partition should appear before other boot partitions on the disk, especially "
+"MacOS boot partitions. The bootstrap partition should be the first one you "
+"create. However, if you add a bootstrap partition later, you can use "
+"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder "
+"the partition map so the bootstrap partition comes right after the map "
+"(which is always partition 1). It's the logical map order, not the physical "
+"address order, that counts."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:861
 #, no-c-format
-msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
+msgid ""
+"Apple disks normally have several small driver partitions. If you intend to "
+"dual boot your machine with MacOSX, you should retain these partitions and a "
+"small HFS partition (800k is the minimum size). That is because MacOSX, on "
+"every boot, offers to initialize any disks which do not have active MacOS "
+"partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:878
 #, no-c-format
-msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
+msgid ""
+"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This "
+"is the only kind of partition scheme that the OpenBoot PROM understands, and "
+"so it's the only scheme from which you can boot. The <keycap>s</keycap> key "
+"is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:886
 #, no-c-format
-msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
+msgid ""
+"Furthermore, on &arch-title; disks, make sure your first partition on your "
+"boot disk starts at cylinder 0. While this is required, it also means that "
+"the first partition will contain the partition table and the boot block, "
+"which are the first two sectors of the disk. You must <emphasis>not</"
+"emphasis> put swap on the first partition of the boot drive, since swap "
+"partitions do not preserve the first few sectors of the partition. You can "
+"put Ext2 or UFS partitions there; these will leave the partition table and "
+"the boot block alone."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:897
 #, no-c-format
-msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
+msgid ""
+"It is also advised that the third partition should be of type <quote>Whole "
+"disk</quote> (type 5), and contain the entire disk (from the first cylinder "
+"to the last). This is simply a convention of Sun disk labels, and helps the "
+"<command>SILO</command> boot loader keep its bearings."
 msgstr ""
-
diff --git a/po/nn/post-install.po b/po/nn/post-install.po
index 8367ac28c..e22aac91d 100644
--- a/po/nn/post-install.po
+++ b/po/nn/post-install.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,27 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:15
 #, no-c-format
-msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system."
+msgid ""
+"To shut down a running &debian-gnu; system, you must not reboot with the "
+"reset switch on the front or back of your computer, or just turn off the "
+"computer. &debian-gnu; should be shut down in a controlled manner, otherwise "
+"files might get lost and/or disk damage might occur. If you run a desktop "
+"environment, there is usually an option to <quote>log out</quote> available "
+"from the application menu that allows you to shutdown (or reboot) the system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:25
 #, no-c-format
-msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system."
+msgid ""
+"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</"
+"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch="
+"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> "
+"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last "
+"option is to log in as root and type one of the commands <command>poweroff</"
+"command>, <command>halt</command> or <command>shutdown -h now</command> if "
+"either of the key combinations do not work or you prefer to type commands; "
+"use <command>reboot</command> to reboot the system."
 msgstr ""
 
 #. Tag: title
@@ -46,13 +61,26 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:47
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:55
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as &debian; packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as &debian; "
+"packages."
 msgstr ""
 
 #. Tag: title
@@ -64,7 +92,13 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:77
 #, no-c-format
-msgid "&debian; is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about &debian; to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use &debian;, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"&debian; is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about &debian; to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use &debian;, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -76,13 +110,32 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:89
 #, no-c-format
-msgid "The most important concept to grasp is the &debian; packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the &debian; packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:130
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
@@ -94,7 +147,12 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:142
 #, no-c-format
-msgid "There are official and unofficial software repositories that are not enabled in the default &debian; install. These contain software which many find important and expect to have. Information on these additional repositories can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-software;\">The Software Available for &debian;'s Stable Release</ulink>."
+msgid ""
+"There are official and unofficial software repositories that are not enabled "
+"in the default &debian; install. These contain software which many find "
+"important and expect to have. Information on these additional repositories "
+"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-"
+"software;\">The Software Available for &debian;'s Stable Release</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,7 +164,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:155
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
@@ -118,19 +179,34 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:166
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:175
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user account under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:184
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -142,25 +218,50 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:200
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:206
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about &debian;-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about &debian;-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:217
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about &debian;. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more &debian; documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The &debian; community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on &debian;."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about &debian;. In particular, see the "
+"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> "
+"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference"
+"\">Debian Reference</ulink>. An index of more &debian; documentation is "
+"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian "
+"Documentation Project</ulink>. The &debian; community is self-supporting; to "
+"subscribe to one or more of the Debian mailing lists, see the <ulink url="
+"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</"
+"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/"
+"\">Debian Mailing List Archives</ulink> contain a wealth of information on "
+"&debian;."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:235
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
@@ -172,31 +273,59 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:252
 #, no-c-format
-msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some &debian; utilities, we will try to cover the basics in this section."
+msgid ""
+"Today, email is an important part of many people's life. As there are many "
+"options as to how to set it up, and as having it set up correctly is "
+"important for some &debian; utilities, we will try to cover the basics in "
+"this section."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:259
 #, no-c-format
-msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox."
+msgid ""
+"There are three main functions that make up an e-mail system. First there is "
+"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user "
+"actually uses to compose and read mails. Then there is the <firstterm>Mail "
+"Transfer Agent</firstterm> (MTA) that takes care of transferring messages "
+"from one computer to another. And last there is the <firstterm>Mail Delivery "
+"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the "
+"user's inbox."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:269
 #, no-c-format
-msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail."
+msgid ""
+"These three functions can be performed by separate programs, but they can "
+"also be combined in one or two programs. It is also possible to have "
+"different programs handle these functions for different types of mail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:275
 #, no-c-format
-msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA."
+msgid ""
+"On Linux and Unix systems <command>mutt</command> is historically a very "
+"popular MUA. Like most traditional Linux programs it is text based. It is "
+"often used in combination with <command>exim</command> or <command>sendmail</"
+"command> as MTA and <command>procmail</command> as MDA."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:282
 #, no-c-format
-msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in &debian; available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in &debian; has to do with licensing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can &mdash; and often are &mdash; also be used in combination with the traditional Linux tools."
+msgid ""
+"With the increasing popularity of graphical desktop systems, the use of "
+"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's "
+"<command>kmail</command> or Mozilla's <command>thunderbird</command> (in "
+"&debian; available as <command>icedove</command><footnote> <para> The reason "
+"that <command>thunderbird</command> has been renamed to <command>icedove</"
+"command> in &debian; has to do with licensing issues. Details are outside "
+"the scope of this manual. </para> </footnote>) is becoming more popular. "
+"These programs combine the function of a MUA, MTA and MDA, but can &mdash; "
+"and often are &mdash; also be used in combination with the traditional Linux "
+"tools."
 msgstr ""
 
 #. Tag: title
@@ -208,19 +337,40 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:303
 #, no-c-format
-msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, &hellip; </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes."
+msgid ""
+"Even if you are planning to use a graphical mail program, it is important "
+"that a traditional MTA/MDA is also installed and correctly set up on your "
+"&debian-gnu; system. Reason is that various utilities running on the "
+"system<footnote> <para> Examples are: <command>cron</command>, "
+"<command>quota</command>, <command>logcheck</command>, <command>aide</"
+"command>, &hellip; </para> </footnote> can send important notices by e-mail "
+"to inform the system administrator of (potential) problems or changes."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:318
 #, no-c-format
-msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>."
+msgid ""
+"For this reason the packages <classname>exim4</classname> and "
+"<classname>mutt</classname> will be installed by default (provided you did "
+"not unselect the <quote>standard</quote> task during the installation). "
+"<classname>exim4</classname> is a combination MTA/MDA that is relatively "
+"small but very flexible. By default it will be configured to only handle e-"
+"mail local to the system itself and e-mails addressed to the system "
+"administrator (root account) will be delivered to the regular user account "
+"created during the installation<footnote> <para> The forwarding of mail for "
+"root to the regular user account is configured in <filename>/etc/aliases</"
+"filename>. If no regular user account was created, the mail will of course "
+"be delivered to the root account itself. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:337
 #, no-c-format
-msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>."
+msgid ""
+"When system e-mails are delivered they are added to a file in <filename>/var/"
+"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be "
+"read using <command>mutt</command>."
 msgstr ""
 
 #. Tag: title
@@ -232,31 +382,51 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:348
 #, no-c-format
-msgid "As mentioned earlier, the installed &debian; system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others."
+msgid ""
+"As mentioned earlier, the installed &debian; system is only set up to handle "
+"e-mail local to the system, not for sending mail to others nor for receiving "
+"mail from others."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:354
 #, no-c-format
-msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly."
+msgid ""
+"If you would like <classname>exim4</classname> to handle external e-mail, "
+"please refer to the next subsection for the basic available configuration "
+"options. Make sure to test that mail can be sent and received correctly."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:360
 #, no-c-format
-msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)."
+msgid ""
+"If you intend to use a graphical mail program and use a mail server of your "
+"Internet Service Provider (ISP) or your company, there is not really any "
+"need to configure <classname>exim4</classname> for handling external e-mail. "
+"Just configure your favorite graphical mail program to use the correct "
+"servers to send and receive e-mail (how is outside the scope of this manual)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:369
 #, no-c-format
-msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against &debian; packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports."
+msgid ""
+"However, in that case you may need to configure individual utilities to "
+"correctly send e-mails. One such utility is <command>reportbug</command>, a "
+"program that facilitates submitting bug reports against &debian; packages. "
+"By default it expects to be able to use <classname>exim4</classname> to "
+"submit bug reports."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:377
 #, no-c-format
-msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports."
+msgid ""
+"To correctly set up <command>reportbug</command> to use an external mail "
+"server, please run the command <command>reportbug --configure</command> and "
+"answer <quote>no</quote> to the question if an MTA is available. You will "
+"then be asked for the SMTP server to be used for submitting bug reports."
 msgstr ""
 
 #. Tag: title
@@ -268,7 +438,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:389
 #, no-c-format
-msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:"
+msgid ""
+"If you would like your system to also handle external e-mail, you will need "
+"to reconfigure the <classname>exim4</classname> package<footnote> <para> You "
+"can of course also remove <classname>exim4</classname> and replace it with "
+"an alternative MTA/MDA. </para> </footnote>:"
 msgstr ""
 
 #. Tag: screen
@@ -280,13 +454,18 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:403
 #, no-c-format
-msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option."
+msgid ""
+"After entering that command (as root), you will be asked if you want split "
+"the configuration into small files. If you are unsure, select the default "
+"option."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:409
 #, no-c-format
-msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs."
+msgid ""
+"Next you will be presented with several common mail scenarios. Choose the "
+"one that most closely resembles your needs."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +477,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:419
 #, no-c-format
-msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
+msgid ""
+"Your system is connected to a network and your mail is sent and received "
+"directly using SMTP. On the following screens you will be asked a few basic "
+"questions, like your machine's mail name, or a list of domains for which you "
+"accept or relay mail."
 msgstr ""
 
 #. Tag: term
@@ -310,13 +493,22 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:431
 #, no-c-format
-msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which takes care of sending the message on to its destination. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail."
+msgid ""
+"In this scenario your outgoing mail is forwarded to another machine, called "
+"a <quote>smarthost</quote>, which takes care of sending the message on to "
+"its destination. The smarthost also usually stores incoming mail addressed "
+"to your computer, so you don't need to be permanently online. That also "
+"means you have to download your mail from the smarthost via programs like "
+"fetchmail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:441
 #, no-c-format
-msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network."
+msgid ""
+"In a lot of cases the smarthost will be your ISP's mail server, which makes "
+"this option very suitable for dial-up users. It can also be a company mail "
+"server, or even another system on your own network."
 msgstr ""
 
 #. Tag: term
@@ -328,7 +520,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:452
 #, no-c-format
-msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled."
+msgid ""
+"This option is basically the same as the previous one except that the system "
+"will not be set up to handle mail for a local e-mail domain. Mail on the "
+"system itself (e.g. for the system administrator) will still be handled."
 msgstr ""
 
 #. Tag: term
@@ -352,19 +547,37 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:473
 #, no-c-format
-msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
+msgid ""
+"Choose this if you are absolutely convinced you know what you are doing. "
+"This will leave you with an unconfigured mail system &mdash; until you "
+"configure it, you won't be able to send or receive any mail and you may miss "
+"some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:484
 #, no-c-format
-msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has further details about configuring <classname>exim4</classname> and explains where to find additional documentation."
+msgid ""
+"If none of these scenarios suits your needs, or if you need a finer grained "
+"setup, you will need to edit configuration files under the <filename>/etc/"
+"exim4</filename> directory after the installation is complete. More "
+"information about <classname>exim4</classname> may be found under <filename>/"
+"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</"
+"filename> has further details about configuring <classname>exim4</classname> "
+"and explains where to find additional documentation."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:495
 #, no-c-format
-msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>."
+msgid ""
+"Note that sending mail directly to the Internet when you don't have an "
+"official domain name, can result in your mail being rejected because of anti-"
+"spam measures on receiving servers. Using your ISP's mail server is "
+"preferred. If you still do want to send out mail directly, you may want to "
+"use a different e-mail address than is generated by default. If you use "
+"<classname>exim4</classname> as your MTA, this is possible by adding an "
+"entry in <filename>/etc/email-addresses</filename>."
 msgstr ""
 
 #. Tag: title
@@ -376,19 +589,29 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:514
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with &debian; handles most configurations. Also, &debian; often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with &debian; handles most configurations. "
+"Also, &debian; often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:524
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:530
 #, no-c-format
-msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
@@ -430,67 +653,135 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:565
 #, no-c-format
-msgid "To compile a kernel the &debian; way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the &debian; way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<classname>linux-source-2.6</classname> and a few others which are probably "
+"already installed (see <filename>/usr/share/doc/kernel-package/README.gz</"
+"filename> for the complete list)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:574
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:582
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>&debian; way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>&debian; way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <classname>linux-source-2.6</"
+"classname>, yet still use the <classname>kernel-package</classname> "
+"compilation method."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:591
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:598
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/"
+"linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory "
+"<filename>linux-source-&kernelversion;</filename> that will have been "
+"created."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:618
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your &debian; installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your &debian; installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:633
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:638
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --"
+"revision=custom.1.0 kernel_image</userinput>. The version number of "
+"<quote>1.0</quote> can be changed at will; this is just a version number "
+"that you will use to track your kernel builds. Likewise, you can put any "
+"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel "
+"compilation may take quite a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:648
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well."
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../&kernelpackage;-"
+"&kernelversion;-<replaceable>subarchitecture</"
+"replaceable>_custom.1.0_&architecture;.deb</userinput>. The "
+"<replaceable>subarchitecture</replaceable> part is an optional sub-"
+"architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> "
+"depending on what kernel options you set. <userinput>dpkg -i</userinput> "
+"will install the kernel, along with some other nice supporting files. For "
+"instance, the <filename>System.map</filename> will be properly installed "
+"(helpful for debugging kernel problems), and <filename>/boot/config-"
+"&kernelversion;</filename> will be installed, containing your current "
+"configuration set. Your new kernel package is also clever enough to "
+"automatically update your boot loader to use the new kernel. If you have "
+"created a modules package, you'll need to install that package as well."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:668
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:673
 #, no-c-format
-msgid "For more information on &debian; kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"For more information on &debian; kernels and kernel compilation, see the "
+"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. "
+"For more information on <classname>kernel-package</classname>, read the fine "
+"documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
@@ -502,31 +793,63 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:690
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:700
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:715
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:723
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:735
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
@@ -538,6 +861,8 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:748
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/nn/preparing.po b/po/nn/preparing.po
index 9378d6304..86a142b74 100644
--- a/po/nn/preparing.po
+++ b/po/nn/preparing.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:6
 #, no-c-format
-msgid "This chapter deals with the preparation for installing &debian; before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information."
+msgid ""
+"This chapter deals with the preparation for installing &debian; before you "
+"even boot the installer. This includes backing up your data, gathering "
+"information about your hardware, and locating any necessary information."
 msgstr ""
 
 #. Tag: title
@@ -34,37 +38,59 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:20
 #, no-c-format
-msgid "First, just a note about re-installations. With &debian;, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case."
+msgid ""
+"First, just a note about re-installations. With &debian;, a circumstance "
+"that will require a complete re-installation of your system is very rare; "
+"perhaps mechanical failure of the hard disk would be the most common case."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:27
 #, no-c-format
-msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS."
+msgid ""
+"Many common operating systems may require a complete installation to be "
+"performed when critical failures take place or for upgrades to new OS "
+"versions. Even if a completely new installation isn't required, often the "
+"programs you use must be re-installed to operate properly in the new OS."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:35
 #, no-c-format
-msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the &debian; packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system."
+msgid ""
+"Under &debian-gnu;, it is much more likely that your OS can be repaired "
+"rather than replaced if things go wrong. Upgrades never require a wholesale "
+"installation; you can always upgrade in-place. And the programs are almost "
+"always compatible with successive OS releases. If a new program version "
+"requires newer supporting software, the &debian; packaging system ensures "
+"that all the necessary software is automatically identified and installed. "
+"The point is, much effort has been put into avoiding the need for re-"
+"installation, so think of it as your very last option. The installer is "
+"<emphasis>not</emphasis> designed to re-install over an existing system."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:48
 #, no-c-format
-msgid "Here's a road map for the steps you will take during the installation process."
+msgid ""
+"Here's a road map for the steps you will take during the installation "
+"process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:56
 #, no-c-format
-msgid "Back up any existing data or documents on the hard disk where you plan to install."
+msgid ""
+"Back up any existing data or documents on the hard disk where you plan to "
+"install."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:62
 #, no-c-format
-msgid "Gather information about your computer and any needed documentation, before starting the installation."
+msgid ""
+"Gather information about your computer and any needed documentation, before "
+"starting the installation."
 msgstr ""
 
 #. Tag: para
@@ -76,13 +102,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-msgid "Locate and/or download the installer software and any specialized driver or firmware files your machine requires."
+msgid ""
+"Locate and/or download the installer software and any specialized driver or "
+"firmware files your machine requires."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:79
 #, no-c-format
-msgid "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot infrastructure from which the installer can be booted."
+msgid ""
+"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
+"infrastructure from which the installer can be booted."
 msgstr ""
 
 #. Tag: para
@@ -124,7 +154,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:117
 #, no-c-format
-msgid "If necessary, resize existing partitions on your target harddisk to make space for the installation."
+msgid ""
+"If necessary, resize existing partitions on your target harddisk to make "
+"space for the installation."
 msgstr ""
 
 #. Tag: para
@@ -136,13 +168,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:127
 #, no-c-format
-msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>."
+msgid ""
+"Watch the automatic download/install/setup of the <firstterm>base system</"
+"firstterm>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:133
 #, no-c-format
-msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system."
+msgid ""
+"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
+"and/or your existing system."
 msgstr ""
 
 #. Tag: para
@@ -154,37 +190,68 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
+"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
+"of the installation system. For more information about this graphical "
+"installer, see <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:154
 #, no-c-format
-msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
+msgid ""
+"If you have problems during the installation, it helps to know which "
+"packages are involved in which steps. Introducing the leading software "
+"actors in this installation drama:"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:160
 #, no-c-format
-msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
+msgid ""
+"The installer software, <classname>debian-installer</classname>, is the "
+"primary concern of this manual. It detects hardware and loads appropriate "
+"drivers, uses <classname>dhcp-client</classname> to set up the network "
+"connection, runs <classname>debootstrap</classname> to install the base "
+"system packages, and runs <classname>tasksel</classname> to allow you to "
+"install certain additional software. Many more actors play smaller parts in "
+"this process, but <classname>debian-installer</classname> has completed its "
+"task when you load the new system for the first time."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:172
 #, no-c-format
-msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
+msgid ""
+"To tune the system to your needs, <classname>tasksel</classname> allows you "
+"to choose to install various predefined bundles of software like a Web "
+"server or a Desktop environment."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because in relation to a text-mode-only system it requires a comparatively large amount of disk space and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid ""
+"One important option during the installation is whether or not to install a "
+"graphical desktop environment, consisting of the X Window System and one of "
+"the available graphical desktop environments. If you choose not to select "
+"the <quote>Desktop environment</quote> task, you will only have a relatively "
+"basic, command line driven system. Installing the Desktop environment task "
+"is optional because in relation to a text-mode-only system it requires a "
+"comparatively large amount of disk space and because many &debian-gnu; "
+"systems are servers which don't really have any need for a graphical user "
+"interface to do their job."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Troubleshooting of the X Window System is not within the scope of this manual."
+msgid ""
+"Just be aware that the X Window System is completely separate from "
+"<classname>debian-installer</classname>, and in fact is much more "
+"complicated. Troubleshooting of the X Window System is not within the scope "
+"of this manual."
 msgstr ""
 
 #. Tag: title
@@ -196,13 +263,29 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system is going to be installed on your computer, it is quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in the installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
+msgid ""
+"Before you start, make sure to back up every file that is now on your "
+"system. If this is the first time a non-native operating system is going to "
+"be installed on your computer, it is quite likely you will need to re-"
+"partition your disk to make room for &debian-gnu;. Anytime you partition "
+"your disk, you run a risk of losing everything on the disk, no matter what "
+"program you use to do it. The programs used in the installation are quite "
+"reliable and most have seen years of use; but they are also quite powerful "
+"and a false move can cost you. Even after backing up, be careful and think "
+"about your answers and actions. Two minutes of thinking can save hours of "
+"unnecessary work."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Even though this is normally not necessary, there might be situations in which you could be required to reinstall your operating system's boot loader to make the system boot or in a worst case even have to reinstall the complete operating system and restore your previously made backup."
+msgid ""
+"If you are creating a multi-boot system, make sure that you have the "
+"distribution media of any other present operating systems on hand. Even "
+"though this is normally not necessary, there might be situations in which "
+"you could be required to reinstall your operating system's boot loader to "
+"make the system boot or in a worst case even have to reinstall the complete "
+"operating system and restore your previously made backup."
 msgstr ""
 
 #. Tag: title
@@ -238,13 +321,20 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:259
 #, no-c-format
-msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of &debian;; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is the official version of the "
+"Installation Guide for the &releasename; release of &debian;; available in "
+"<ulink url=\"&url-release-area;/installmanual\">various formats and "
+"translations</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:268
 #, no-c-format
-msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of &debian;; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is a development version of the "
+"Installation Guide for the next release of &debian;; available in <ulink url="
+"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -256,7 +346,8 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:281
 #, no-c-format
-msgid "Often contains useful information on configuring or using your hardware."
+msgid ""
+"Often contains useful information on configuring or using your hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -286,7 +377,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:314
 #, no-c-format
-msgid "Documentation of &arch-title;-specific boot sequence, commands and device drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
+msgid ""
+"Documentation of &arch-title;-specific boot sequence, commands and device "
+"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
 msgstr ""
 
 #. Tag: ulink
@@ -298,7 +391,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:330
 #, no-c-format
-msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
+msgid ""
+"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
+"&arch-title; hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -310,7 +405,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:346
 #, no-c-format
-msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about &debian; but the basic installation concepts are the same across all &arch-title; distributions."
+msgid ""
+"IBM Redbook describing the Linux distributions available for the mainframe. "
+"It has no chapter about &debian; but the basic installation concepts are the "
+"same across all &arch-title; distributions."
 msgstr ""
 
 #. Tag: ulink
@@ -328,7 +426,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:368
 #, no-c-format
-msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
+msgid ""
+"In many cases, the installer will be able to automatically detect your "
+"hardware. But to be prepared, we do recommend familiarizing yourself with "
+"your hardware before the install."
 msgstr ""
 
 #. Tag: para
@@ -346,7 +447,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys or key combinations. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
+msgid ""
+"The BIOS setup screens of your computer. You can view these screens when you "
+"start your computer by pressing a combination of keys. Check your manual for "
+"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
+"keycap> key, but some manufacturers use other keys or key combinations. "
+"Usually upon starting the computer there will be a message stating which key "
+"to press to enter the setup screen."
 msgstr ""
 
 #. Tag: para
@@ -364,13 +471,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:408
 #, no-c-format
-msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
+msgid ""
+"System commands or tools in another operating system, including file manager "
+"displays. This source is especially useful for information about RAM and "
+"hard drive memory."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:415
 #, no-c-format
-msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
+msgid ""
+"Your system administrator or Internet Service Provider. These sources can "
+"tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
 #. Tag: title
@@ -514,61 +626,115 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-msgid "Many products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems."
+msgid ""
+"Many products work without trouble on &arch-kernel;. Moreover, hardware "
+"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
+"does not run as many different types of hardware as some operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:516
 #, no-c-format
-msgid "Drivers in &arch-kernel; in most cases are not written for a certain <quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names."
+msgid ""
+"Drivers in &arch-kernel; in most cases are not written for a certain "
+"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
+"but for a certain hardware/chipset. Many seemingly different products/brands "
+"are based on the same hardware design; it is not uncommon that chip "
+"manufacturers provide so-called <quote>reference designs</quote> for "
+"products based on their chips which are then used by several different "
+"device manufacturers and sold under lots of different product or brand names."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:527
 #, no-c-format
-msgid "This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them."
+msgid ""
+"This has advantages and disadvantages. An advantage is that a driver for one "
+"chipset works with lots of different products from different manufacturers, "
+"as long as their product is based on the same chipset. The disadvantage is "
+"that it is not always easy to see which actual chipset is used in a certain "
+"product/brand. Unfortunately sometimes device manufacturers change the "
+"hardware base of their product without changing the product name or at least "
+"the product version number, so that when having two items of the same brand/"
+"product name bought at different times, they can sometimes be based on two "
+"different chipsets and therefore use two different drivers or there might be "
+"no driver at all for one of them."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:540
 #, no-c-format
-msgid "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and <quote>product</quote> IDs, and the combination of these two is usually the same for any product based on the same chipset."
+msgid ""
+"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
+"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
+"Express/ExpressCard devices have so called <quote>vendor</quote> and "
+"<quote>product</quote> IDs, and the combination of these two is usually the "
+"same for any product based on the same chipset."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:548
 #, no-c-format
-msgid "On Linux systems, these IDs can be read with the <command>lsusb</command> command for USB devices and with the <command>lspci -nn</command> command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as <quote>1d6b:0001</quote>."
+msgid ""
+"On Linux systems, these IDs can be read with the <command>lsusb</command> "
+"command for USB devices and with the <command>lspci -nn</command> command "
+"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
+"usually given in the form of two hexadecimal numbers, seperated by a colon, "
+"such as <quote>1d6b:0001</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:556
 #, no-c-format
-msgid "An example for the output of <command>lsusb</command>: <quote>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the vendor ID and 0002 is the product ID."
+msgid ""
+"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
+"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
+"vendor ID and 0002 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:562
 #, no-c-format
-msgid "An example for the output of <command>lspci -nn</command> for an Ethernet card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID."
+msgid ""
+"An example for the output of <command>lspci -nn</command> for an Ethernet "
+"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
+"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
+"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
+"here 10ec is the vendor- and 8168 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:570
 #, no-c-format
-msgid "As another example, a graphics card could give the following output: <quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
+msgid ""
+"As another example, a graphics card could give the following output: "
+"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
+"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:576
 #, no-c-format
-msgid "On Windows systems, the IDs for a device can be found in the Windows device manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the device manager's details tab to actually see the IDs, as they are not displayed by default."
+msgid ""
+"On Windows systems, the IDs for a device can be found in the Windows device "
+"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
+"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
+"you have to select the property <quote>Hardware IDs</quote> in the device "
+"manager's details tab to actually see the IDs, as they are not displayed by "
+"default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:586
 #, no-c-format
-msgid "Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and <quote>driver</quote> as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the graphics card example), can help."
+msgid ""
+"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
+"quote> and <quote>driver</quote> as the search terms often results in "
+"information regarding the driver support status for a certain chipset. If a "
+"search for the vendor/product ID does not yield usable results, a search for "
+"the chip code names, which are also often provided by lsusb and lspci "
+"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
+"and <quote>RV710</quote> in the graphics card example), can help."
 msgstr ""
 
 #. Tag: title
@@ -580,19 +746,42 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:601
 #, no-c-format
-msgid "&debian-gnu; is also available as a so-called <quote>live system</quote> for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by &debian-gnu;, the easiest way is to run a &debian; live system on it and try it out."
+msgid ""
+"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
+"certain architectures. A live system is a preconfigured ready-to-use system "
+"in a compressed format that can be booted and used from a read-only medium "
+"like a CD or DVD. Using it by default does not create any permanent changes "
+"on your computer. You can change user settings and install additional "
+"programs from within the live system, but all this only happens in the "
+"computer's RAM, i.e. if you turn off the computer and boot the live system "
+"again, everything is reset to its defaults. If you want to see whether your "
+"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
+"live system on it and try it out."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:614
 #, no-c-format
-msgid "There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official &debian-gnu; live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the &d-i;, so installation of non-free components must be done manually if needed."
+msgid ""
+"There are a few limitations in using a live system. The first is that as all "
+"changes you do within the live system must be held in your computer's RAM, "
+"this only works on systems with enough RAM to do that, so installing "
+"additional large software packages may fail due to memory constraints. "
+"Another limitation with regards to hardware compatibility testing is that "
+"the official &debian-gnu; live system contains only free components, i.e. "
+"there are no non-free firmware files included in it. Such non-free packages "
+"can of course be installed manually within the system, but there is no "
+"automatic detection of required firmware files like in the &d-i;, so "
+"installation of non-free components must be done manually if needed."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:627
 #, no-c-format
-msgid "Information about the available variants of the &debian; live images can be found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</ulink>."
+msgid ""
+"Information about the available variants of the &debian; live images can be "
+"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
+"ulink>."
 msgstr ""
 
 #. Tag: title
@@ -604,7 +793,11 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-msgid "If your computer is connected to a fixed network (i.e. an Ethernet or equivalent connection &mdash; not a dialup/PPP connection) which is administered by somebody else, you should ask your network's system administrator for this information:"
+msgid ""
+"If your computer is connected to a fixed network (i.e. an Ethernet or "
+"equivalent connection &mdash; not a dialup/PPP connection) which is "
+"administered by somebody else, you should ask your network's system "
+"administrator for this information:"
 msgstr ""
 
 #. Tag: para
@@ -634,31 +827,47 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:671
 #, no-c-format
-msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
+msgid ""
+"The IP address of the default gateway system you should route to, if your "
+"network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:677
 #, no-c-format
-msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
+msgid ""
+"The system on your network that you should use as a DNS (Domain Name "
+"Service) server."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-msgid "If the network you are connected to uses DHCP (Dynamic Host Configuration Protocol) for configuring network settings, you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
+msgid ""
+"If the network you are connected to uses DHCP (Dynamic Host Configuration "
+"Protocol) for configuring network settings, you don't need this information "
+"because the DHCP server will provide it directly to your computer during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:692
 #, no-c-format
-msgid "If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default."
+msgid ""
+"If you have internet access via DSL or cable modem (i.e. over a cable tv "
+"network) and have a router (often provided preconfigured by your phone or "
+"catv provider) which handles your network connectivity, DHCP is usually "
+"available by default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:700
 #, no-c-format
-msgid "As a rule of thumb: if you run a Windows system in your home network and did not have to manually perform any network settings there to achieve Internet access, network connectivity in &debian-gnu; will also be configured automatically."
+msgid ""
+"As a rule of thumb: if you run a Windows system in your home network and did "
+"not have to manually perform any network settings there to achieve Internet "
+"access, network connectivity in &debian-gnu; will also be configured "
+"automatically."
 msgstr ""
 
 #. Tag: para
@@ -688,19 +897,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:735
 #, no-c-format
-msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
+msgid ""
+"Once you have gathered information about your computer's hardware, check "
+"that your hardware will let you do the type of installation that you want to "
+"do."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:741
 #, no-c-format
-msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
+msgid ""
+"Depending on your needs, you might manage with less than some of the "
+"recommended hardware listed in the table below. However, most users risk "
+"being frustrated if they ignore these suggestions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:747
 #, no-c-format
-msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
+msgid ""
+"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
 msgstr ""
 
 #. Tag: para
@@ -790,31 +1006,58 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:785
 #, no-c-format
-msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
+msgid ""
+"The actual minimum memory requirements are a lot less then the numbers "
+"listed in this table. Depending on the architecture, it is possible to "
+"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
+"same goes for the disk space requirements, especially if you pick and choose "
+"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
+"additional information on disk space requirements."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:795
 #, no-c-format
-msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
+msgid ""
+"It is possible to run a graphical desktop environment on older or low-end "
+"systems, but in that case it is recommended to install a window manager that "
+"is less resource-hungry than those of the GNOME or KDE desktop environments; "
+"alternatives include <classname>xfce4</classname>, <classname>icewm</"
+"classname> and <classname>wmaker</classname>, but there are others to choose "
+"from."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:804
 #, no-c-format
-msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
+msgid ""
+"It is practically impossible to give general memory or disk space "
+"requirements for server installations as those very much depend on what the "
+"server is to be used for."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:810
 #, no-c-format
-msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
+msgid ""
+"Remember that these sizes don't include all the other materials which are "
+"usually to be found, such as user files, mail, and data. It is always best "
+"to be generous when considering the space for your own files and data."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:817
 #, no-c-format
-msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to &debian; in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
+msgid ""
+"Disk space required for the smooth operation of the &debian-gnu; system "
+"itself is taken into account in these recommended system requirements. "
+"Notably, the <filename>/var</filename> partition contains a lot of state "
+"information specific to &debian; in addition to its regular contents, like "
+"logfiles. The <command>dpkg</command> files (with information on all "
+"installed packages) can easily consume 40MB. Also, <command>apt-get</"
+"command> puts downloaded packages here before they are installed. You should "
+"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
+"more if you install a graphical desktop environment."
 msgstr ""
 
 #. Tag: title
@@ -826,43 +1069,83 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:842
 #, no-c-format
-msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
+msgid ""
+"Partitioning your disk simply refers to the act of breaking up your disk "
+"into sections. Each section is then independent of the others. It's roughly "
+"equivalent to putting up walls inside a house; if you add furniture to one "
+"room it doesn't affect any other room."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:849
 #, no-c-format
-msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
+msgid ""
+"Whenever this section talks about <quote>disks</quote> you should translate "
+"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
+"means an LPAR or VM guest in this case."
 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 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."
 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 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
 #: preparing.xml:884
 #, no-c-format
-msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
+msgid ""
+"In general, changing a partition with a file system already on it will "
+"destroy any information there. Thus you should always make backups before "
+"doing any repartitioning. Using the analogy of the house, you would probably "
+"want to move all the furniture out of the way before moving a wall or you "
+"risk destroying it."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:892
 #, no-c-format
-msgid "Several modern operating systems offer the ability to move and resize certain existing partitions without destroying their contents. This allows making space for additional partitions without losing existing data. Even though this works quite well in most cases, making changes to the partitioning of a disk is an inherently dangerous action and should only be done after having made a full backup of all data. <phrase arch=\"any-x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, the ability to move and resize them losslessly is provided both by &d-i; as well as by the integrated Disk Manager of Windows 7. </phrase>"
+msgid ""
+"Several modern operating systems offer the ability to move and resize "
+"certain existing partitions without destroying their contents. This allows "
+"making space for additional partitions without losing existing data. Even "
+"though this works quite well in most cases, making changes to the "
+"partitioning of a disk is an inherently dangerous action and should only be "
+"done after having made a full backup of all data. <phrase arch=\"any-"
+"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
+"the ability to move and resize them losslessly is provided both by &d-i; as "
+"well as by the integrated Disk Manager of Windows 7. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:907
 #, no-c-format
-msgid "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size."
+msgid ""
+"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
+"to the partitioning step, select the option for manual partitioning, select "
+"the partition to resize, and simply specify its new size."
 msgstr ""
 
 #. Tag: emphasis
@@ -874,25 +1157,50 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:917
 #, no-c-format
-msgid "Creating and deleting partitions can be done from within &d-i; as well as from an existing operating system. As a rule of thumb, partitions should be created by the system for which they are to be used, i.e. partitions to be used by &debian-gnu; should be created from within &d-i; and partitions to be used from another operating system should be created from there. &d-i; is capable of creating non-&arch-kernel; partitions, and partitions created this way usually work without problems when used in other operating systems, but there are a few rare corner cases in which this could cause problems, so if you want to be sure, use the native partitioning tools to create partitions for use by other operating systems."
+msgid ""
+"Creating and deleting partitions can be done from within &d-i; as well as "
+"from an existing operating system. As a rule of thumb, partitions should be "
+"created by the system for which they are to be used, i.e. partitions to be "
+"used by &debian-gnu; should be created from within &d-i; and partitions to "
+"be used from another operating system should be created from there. &d-i; is "
+"capable of creating non-&arch-kernel; partitions, and partitions created "
+"this way usually work without problems when used in other operating systems, "
+"but there are a few rare corner cases in which this could cause problems, so "
+"if you want to be sure, use the native partitioning tools to create "
+"partitions for use by other operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with the &debian; installation. Windows and other OS installations may destroy your ability to start &debian;, or encourage you to reformat non-native partitions."
+msgid ""
+"If you are going to install more than one operating system on the same "
+"machine, you should install all other system(s) before proceeding with the "
+"&debian; installation. Windows and other OS installations may destroy your "
+"ability to start &debian;, or encourage you to reformat non-native "
+"partitions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:938
 #, no-c-format
-msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
+msgid ""
+"You can recover from these actions or avoid them, but installing the native "
+"system first saves you trouble."
 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 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."
 msgstr ""
 
 #. Tag: title
@@ -904,7 +1212,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1021
 #, no-c-format
-msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and &debian; on the same machine, it is recommended that you partition using SunOS prior to installing &debian;. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
+msgid ""
+"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
+"both SunOS and &debian; on the same machine, it is recommended that you "
+"partition using SunOS prior to installing &debian;. The Linux kernel "
+"understands Sun disk labels, so there are no problems there. SILO supports "
+"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
+"iso9660 (CDROM) partitions."
 msgstr ""
 
 #. Tag: title
@@ -916,13 +1230,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1035
 #, no-c-format
-msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
+msgid ""
+"Whatever system you are using to partition, make sure you create a "
+"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
+"partition scheme that the OpenBoot PROM understands, and so it's the only "
+"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
+"keycap> key is used to create Sun disk labels. You only need to do this on "
+"drives that do not already have a Sun disk label. If you are using a drive "
+"that was previously formatted using a PC (or other architecture) you must "
+"create a new disk label, or problems with the disk geometry will most likely "
+"occur."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1047
 #, no-c-format
-msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
+msgid ""
+"You will probably be using <command>SILO</command> as your boot loader (the "
+"small program which runs the operating system kernel). <command>SILO</"
+"command> has certain requirements for partition sizes and location; see "
+"<xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: title
@@ -934,25 +1261,49 @@ 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>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>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1071
 #, 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."
+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
 #, 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 ""
+"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."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1090
 #, 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 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."
 msgstr ""
 
 #. Tag: title
@@ -964,7 +1315,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1111
 #, 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)."
+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
@@ -976,7 +1333,15 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1128
 #, 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."
+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
@@ -988,31 +1353,63 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1144
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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>"
+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: title
@@ -1024,29 +1421,53 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1204
 #, 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."
+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:1212
 #, 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."
+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:1220
 #, no-c-format
 msgid ""
-      "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
-      "ok\n"
-      "0 &gt;\n"
-      "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
+"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
+"ok\n"
+"0 &gt;\n"
+"</screen></informalexample> Note that on older model &arch-title; Macs, the "
+"default and sometimes hardwired I/O for OpenFirmware user interaction is "
+"through the serial (modem) port. If you invoke OpenFirmware on one of these "
+"machines, you will just see a black screen. In that case, a terminal program "
+"running on another computer, connected to the modem port, is needed to "
+"interact with OpenFirmware."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1233
 #, 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."
+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
@@ -1058,45 +1479,90 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1255
 #, 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."
+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:1263
 #, 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."
+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:1275
 #, 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."
+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:1288
 #, 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>."
+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:1298
 #, 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"
-      "<replaceable>driver-name</replaceable>@\n"
-      "<replaceable>unit-address</replaceable>:\n"
-      "<replaceable>device-arguments</replaceable>\n"
-      "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
+"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"
+"<replaceable>driver-name</replaceable>@\n"
+"<replaceable>unit-address</replaceable>:\n"
+"<replaceable>device-arguments</replaceable>\n"
+"</screen></informalexample> In older revisions of OpenBoot, device naming is "
+"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
+"disk devices are of the form <quote>sd(<replaceable>controller</"
+"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
+"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
+"newer OpenBoot revisions is useful for viewing the currently configured "
+"devices. For full information, whatever your revision, see the <ulink url="
+"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1321
 #, 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"
-      "# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
-      "</screen></informalexample> and under Solaris:"
+"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"
+"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
+"</screen></informalexample> and under Solaris:"
 msgstr ""
 
 #. Tag: screen
@@ -1114,19 +1580,45 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1351
 #, 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."
+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:1363
 #, 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."
+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:1373
 #, 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."
+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
@@ -1138,7 +1630,12 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1391
 #, 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."
+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
@@ -1150,13 +1647,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1407
 #, 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."
+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:1417
 #, 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."
+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
@@ -1168,13 +1678,21 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1436
 #, 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."
+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:1444
 #, 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."
+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
@@ -1198,7 +1716,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1464
 #, 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."
+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
@@ -1210,6 +1734,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1479
 #, 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>."
+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 ""
-
diff --git a/po/nn/preseed.po b/po/nn/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/nn/preseed.po
+++ b/po/nn/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-
diff --git a/po/nn/random-bits.po b/po/nn/random-bits.po
index ff94f432b..26dbb7c32 100644
--- a/po/nn/random-bits.po
+++ b/po/nn/random-bits.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,7 +29,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:12
 #, no-c-format
-msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below."
+msgid ""
+"In Linux various special files can be found under the directory <filename>/"
+"dev</filename>. These files are called device files and behave unlike "
+"ordinary files. The most common types of device files are for block devices "
+"and character devices. These files are an interface to the actual driver "
+"(part of the Linux kernel) which in turn accesses the hardware. Another, "
+"less common, type of device file is the named <firstterm>pipe</firstterm>. "
+"The most important device files are listed in the tables below."
 msgstr ""
 
 #. Tag: filename
@@ -316,33 +324,62 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:126
 #, no-c-format
-msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. Normally, this is a simple matter of installing <filename>gpm</"
+"filename> and the X server itself. Both should be configured to use "
+"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse "
+"protocol is named <userinput>exps2</userinput> in gpm, and "
+"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files "
+"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:137
 #, no-c-format
-msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>."
+msgid ""
+"Certain kernel modules must be loaded in order for your mouse to work. In "
+"most cases the correct modules are autodetected, but not always for old-"
+"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole "
+"D-shaped connector; bus mice have an 8-pin round connector, not to be "
+"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round "
+"connector of an ADB mouse. </para> </footnote>, which are quite rare except "
+"on very old computers. Summary of Linux kernel modules needed for different "
+"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</"
+"entry> <entry>Description</entry> </row> </thead><tbody> <row> "
+"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </"
+"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</"
+"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> "
+"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech "
+"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse "
+"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></"
+"informaltable> To load a mouse driver module, you can use the "
+"<command>modconf</command> command (from the package with the same name) and "
+"look in the category <userinput>kernel/drivers/input/mouse</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:184
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:191
 #, no-c-format
 msgid ""
-      "# 3-button mouse emulation\n"
-      "# turn on emulation\n"
-      "/dev/mac_hid/mouse_button_emulation = 1\n"
-      "# Send middle mouse button signal with the F11 key\n"
-      "/dev/mac_hid/mouse_button2_keycode = 87\n"
-      "# Send right mouse button signal with the F12 key\n"
-      "/dev/mac_hid/mouse_button3_keycode = 88\n"
-      "# For different keys, use showkey to tell you what the code is."
+"# 3-button mouse emulation\n"
+"# turn on emulation\n"
+"/dev/mac_hid/mouse_button_emulation = 1\n"
+"# Send middle mouse button signal with the F11 key\n"
+"/dev/mac_hid/mouse_button2_keycode = 87\n"
+"# Send right mouse button signal with the F12 key\n"
+"/dev/mac_hid/mouse_button3_keycode = 88\n"
+"# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
 #. Tag: title
@@ -354,31 +391,54 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "A standard installation for the amd64 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB."
+msgid ""
+"A standard installation for the amd64 architecture, including all standard "
+"packages and using the default 2.6 kernel, takes up &std-system-size;MB of "
+"disk space. A minimal base installation, without the <quote>Standard system</"
+"quote> task selected, will take &base-system-size;MB."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:207
 #, no-c-format
-msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use."
+msgid ""
+"In both cases this is the actual disk space used <emphasis>after</emphasis> "
+"the installation is finished and any temporary files deleted. It also does "
+"not take into account overhead used by the file system, for example for "
+"journal files. This means that significantly more disk space is needed both "
+"<emphasis>during</emphasis> the installation and for normal system use."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:216
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:223
 #, no-c-format
-msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)."
+msgid ""
+"By default the installer will install the GNOME desktop environment, but "
+"alternative desktop environments can be selected either by using one of the "
+"special CD images, or by specifying the desired desktop environment when the "
+"installer is booted (see <xref linkend=\"pkgsel\"/>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:230
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the standard installation when determining the size of partitions. Most of "
+"the size listed as <quote>Installed size</quote> will end up in <filename>/"
+"usr</filename> and in <filename>/lib</filename>; the size listed as "
+"<quote>Download size</quote> is (temporarily) required in <filename>/var</"
+"filename>."
 msgstr ""
 
 #. Tag: entry
@@ -522,7 +582,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid ""
+"There is some overlap of the Laptop task with the Desktop environment task. "
+"If you install both, the Laptop task will only require a few MB additional "
+"disk space."
 msgstr ""
 
 #. Tag: entry
@@ -714,7 +777,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:350
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -726,19 +793,40 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:367
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
+msgid ""
+"This section explains how to install &debian-gnu; from an existing Unix or "
+"Linux system, without using the menu-driven installer as explained in the "
+"rest of the manual. This <quote>cross-install</quote> HOWTO has been "
+"requested by users switching to &debian-gnu; from Red Hat, Mandriva, and "
+"SUSE. In this section some familiarity with entering *nix commands and "
+"navigating the file system is assumed. In this section, <prompt>$</prompt> "
+"symbolizes a command to be entered in the user's current system, while "
+"<prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:379
 #, no-c-format
-msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new &debian; system configured to your preference, you "
+"can migrate your existing user data (if any) to it, and keep on rolling. "
+"This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's "
+"also a clever way for dealing with hardware that otherwise doesn't play "
+"friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:390
 #, no-c-format
-msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
+msgid ""
+"As this is a mostly manual procedure, you should bear in mind that you will "
+"need to do a lot of basic configuration of the system yourself, which will "
+"also require more knowledge of &debian; and of &arch-kernel; in general than "
+"performing a regular installation. You cannot expect this procedure to "
+"result in a system that is identical to a system from a regular "
+"installation. You should also keep in mind that this procedure only gives "
+"the basic steps to set up a system. Additional installation and/or "
+"configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
@@ -750,41 +838,56 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:405
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need around &base-"
+"system-size;MB of space available for a console only install, or about &task-"
+"desktop-lxde-inst;MB if you plan to install X (more if you intend to install "
+"desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:413
 #, no-c-format
 msgid ""
-      "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
-      "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
-      "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"Next, create file systems on the partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
+"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:423
 #, no-c-format
 msgid ""
-      "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
-      "# mkswap /dev/<replaceable>hda5</replaceable>\n"
-      "# sync; sync; sync\n"
-      "# swapon /dev/<replaceable>hda5</replaceable>\n"
-      "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"Initialize and activate swap (substitute the partition number for your "
+"intended &debian; swap partition): <informalexample><screen>\n"
+"# mkswap /dev/<replaceable>hda5</replaceable>\n"
+"# sync; sync; sync\n"
+"# swapon /dev/<replaceable>hda5</replaceable>\n"
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:435
 #, no-c-format
 msgid ""
-      "# mkdir /mnt/debinst\n"
-      "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
+"# mkdir /mnt/debinst\n"
+"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:438
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
@@ -796,26 +899,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:449
 #, no-c-format
-msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The utility used by the &debian; installer, and recognized as the official "
+"way to install a &debian; base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname> and basic Unix/Linux "
+"tools<footnote> <para> These include the GNU core utilities and commands "
+"like <command>sed</command>, <command>grep</command>, <command>tar</command> "
+"and <command>gzip</command>. </para> </footnote>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:479
 #, no-c-format
 msgid ""
-      "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
-      "# mkdir work\n"
-      "# cd work\n"
-      "</screen></informalexample> The <command>debootstrap</command> binary is located in the &debian; archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files."
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
+"# mkdir work\n"
+"# cd work\n"
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the &debian; archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the files from it. "
+"You will need to have root privileges to install the files."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:494
 #, no-c-format
 msgid ""
-      "# ar -x debootstrap_0.X.X_all.deb\n"
-      "# cd /\n"
-      "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
+"# ar -x debootstrap_0.X.X_all.deb\n"
+"# cd /\n"
+"# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
 #. Tag: title
@@ -827,27 +945,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any &debian; archive mirror "
+"for <userinput>&archive-mirror;/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:510
 #, no-c-format
-msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>amd64</userinput>, "
+"<userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, "
+"<userinput>mipsel</userinput>, <userinput>powerpc</userinput>, "
+"<userinput>s390</userinput>, <userinput>s390x</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:533
 #, no-c-format
 msgid ""
-      "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
-      "     /mnt/debinst http://ftp.us.debian.org/debian"
+"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
+"     /mnt/debinst http://ftp.us.debian.org/debian"
 msgstr ""
 
 #. Tag: title
@@ -860,9 +993,11 @@ msgstr ""
 #: random-bits.xml:540
 #, no-c-format
 msgid ""
-      "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
-      "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
-      "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:"
+"Now you've got a real &debian; system, though rather lean, on disk. "
+"<command>chroot</command> into it: <informalexample><screen>\n"
+"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
+"</screen></informalexample> After chrooting you may need to set the terminal "
+"definition to be compatible with the &debian; base system, for example:"
 msgstr ""
 
 #. Tag: screen
@@ -880,7 +1015,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:556
 #, no-c-format
-msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
+msgid ""
+"At this point <filename>/dev/</filename> only contains very basic device "
+"files. For the next steps of the installation additional device files may be "
+"needed. There are different ways to go about this and which method you "
+"should use depends on the host system you are using for the installation, on "
+"whether you intend to use a modular kernel or not, and on whether you intend "
+"to use dynamic (e.g. using <classname>udev</classname>) or static device "
+"files for the new system."
 msgstr ""
 
 #. Tag: para
@@ -892,28 +1034,34 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:571
 #, no-c-format
-msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
+msgid ""
+"install the makedev package, and create a default set of static device files "
+"using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:575
 #, no-c-format
 msgid ""
-      "# apt-get install makedev\n"
-      "# cd /dev\n"
-      "# MAKEDEV generic"
+"# apt-get install makedev\n"
+"# cd /dev\n"
+"# MAKEDEV generic"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:578
 #, no-c-format
-msgid "manually create only specific device files using <command>MAKEDEV</command>"
+msgid ""
+"manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:583
 #, no-c-format
-msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
+msgid ""
+"bind mount /dev from your host system on top of /dev in the target system; "
+"note that the postinst scripts of some packages may try to create device "
+"files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
@@ -926,34 +1074,44 @@ msgstr ""
 #: random-bits.xml:597
 #, no-c-format
 msgid ""
-      "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
-      "# editor /etc/fstab\n"
-      "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
-      "# /etc/fstab: static file system information.\n"
-      "#\n"
-      "# file system    mount point   type    options                  dump pass\n"
-      "/dev/XXX         /             ext3    defaults                 0    1\n"
-      "/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
-      "\n"
-      "/dev/XXX         none          swap    sw                       0    0\n"
-      "proc             /proc         proc    defaults                 0    0\n"
-      "\n"
-      "/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
-      "/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
-      "\n"
-      "/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
-      "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-      "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n"
-      "# mount /path   # e.g.: mount /usr\n"
-      "</screen></informalexample> Current &debian; systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n"
-      "# cd /media\n"
-      "# mkdir cdrom0\n"
-      "# ln -s cdrom0 cdrom\n"
-      "# cd /\n"
-      "# ln -s media/cdrom\n"
-      "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
+"# editor /etc/fstab\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
+"# /etc/fstab: static file system information.\n"
+"#\n"
+"# file system    mount point   type    options                  dump pass\n"
+"/dev/XXX         /             ext3    defaults                 0    1\n"
+"/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
+"\n"
+"/dev/XXX         none          swap    sw                       0    0\n"
+"proc             /proc         proc    defaults                 0    0\n"
+"\n"
+"/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
+"/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
+"\n"
+"/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
+"/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or, to mount file systems individually, use: <informalexample><screen>\n"
+"# mount /path   # e.g.: mount /usr\n"
+"</screen></informalexample> Current &debian; systems have mountpoints for "
+"removable media under <filename>/media</filename>, but keep compatibility "
+"symlinks in <filename>/</filename>. Create these as as needed, for example: "
+"<informalexample><screen>\n"
+"# cd /media\n"
+"# mkdir cdrom0\n"
+"# ln -s cdrom0 cdrom\n"
+"# cd /\n"
+"# ln -s media/cdrom\n"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -965,7 +1123,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:625
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -983,15 +1144,19 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:638
 #, no-c-format
-msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
+msgid ""
+"An option in the file <filename>/etc/default/rcS</filename> determines "
+"whether the system will interpret the hardware clock as being set to UTC or "
+"local time. The following command allows you to set that and choose your "
+"timezone."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:645
 #, no-c-format
 msgid ""
-      "# editor /etc/default/rcS\n"
-      "# dpkg-reconfigure tzdata"
+"# editor /etc/default/rcS\n"
+"# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
@@ -1004,54 +1169,64 @@ msgstr ""
 #: random-bits.xml:652
 #, no-c-format
 msgid ""
-      "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
-      "# editor /etc/network/interfaces\n"
-      "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
-      "######################################################################\n"
-      "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
-      "# See the interfaces(5) manpage for information on what options are\n"
-      "# available.\n"
-      "######################################################################\n"
-      "\n"
-      "# We always want the loopback interface.\n"
-      "#\n"
-      "auto lo\n"
-      "iface lo inet loopback\n"
-      "\n"
-      "# To use dhcp:\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet dhcp\n"
-      "\n"
-      "# An example static IP setup: (broadcast and gateway are optional)\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet static\n"
-      "#     address 192.168.0.42\n"
-      "#     network 192.168.0.0\n"
-      "#     netmask 255.255.255.0\n"
-      "#     broadcast 192.168.0.255\n"
-      "#     gateway 192.168.0.1\n"
-      "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "# editor /etc/resolv.conf\n"
-      "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "search hqdom.local\n"
-      "nameserver 10.1.1.36\n"
-      "nameserver 192.168.9.100\n"
-      "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
-      "# echo DebianHostName &gt; /etc/hostname\n"
-      "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n"
-      "127.0.0.1 localhost\n"
-      "127.0.1.1 DebianHostName\n"
-      "\n"
-      "# The following lines are desirable for IPv6 capable hosts\n"
-      "::1     ip6-localhost ip6-loopback\n"
-      "fe00::0 ip6-localnet\n"
-      "ff00::0 ip6-mcastprefix\n"
-      "ff02::1 ip6-allnodes\n"
-      "ff02::2 ip6-allrouters\n"
-      "ff02::3 ip6-allhosts\n"
-      "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> "
+"and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
+"# editor /etc/network/interfaces\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"######################################################################\n"
+"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
+"# See the interfaces(5) manpage for information on what options are\n"
+"# available.\n"
+"######################################################################\n"
+"\n"
+"# We always want the loopback interface.\n"
+"#\n"
+"auto lo\n"
+"iface lo inet loopback\n"
+"\n"
+"# To use dhcp:\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet dhcp\n"
+"\n"
+"# An example static IP setup: (broadcast and gateway are optional)\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet static\n"
+"#     address 192.168.0.42\n"
+"#     network 192.168.0.0\n"
+"#     netmask 255.255.255.0\n"
+"#     broadcast 192.168.0.255\n"
+"#     gateway 192.168.0.1\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"# editor /etc/resolv.conf\n"
+"</screen></informalexample> A simple example <filename>/etc/resolv.conf</"
+"filename>: <informalexample><screen>\n"
+"search hqdom.local\n"
+"nameserver 10.1.1.36\n"
+"nameserver 192.168.9.100\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
+"# echo DebianHostName &gt; /etc/hostname\n"
+"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with "
+"IPv6 support: <informalexample><screen>\n"
+"127.0.0.1 localhost\n"
+"127.0.1.1 DebianHostName\n"
+"\n"
+"# The following lines are desirable for IPv6 capable hosts\n"
+"::1     ip6-localhost ip6-loopback\n"
+"fe00::0 ip6-localnet\n"
+"ff00::0 ip6-mcastprefix\n"
+"ff02::1 ip6-allnodes\n"
+"ff02::2 ip6-allrouters\n"
+"ff02::3 ip6-allhosts\n"
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1064,12 +1239,16 @@ msgstr ""
 #: random-bits.xml:694
 #, no-c-format
 msgid ""
-      "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
-      "deb-src http://ftp.us.debian.org/debian &releasename; main\n"
-      "\n"
-      "deb http://security.debian.org/ &releasename;/updates main\n"
-      "deb-src http://security.debian.org/ &releasename;/updates main\n"
-      "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list."
+"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</"
+"filename> that will allow installing additional packages. However, you may "
+"want to add some additional sources, for example for source packages and "
+"security updates: <informalexample><screen>\n"
+"deb-src http://ftp.us.debian.org/debian &releasename; main\n"
+"\n"
+"deb http://security.debian.org/ &releasename;/updates main\n"
+"deb-src http://security.debian.org/ &releasename;/updates main\n"
+"</screen></informalexample> Make sure to run <userinput>aptitude update</"
+"userinput> after you have made changes to the sources list."
 msgstr ""
 
 #. Tag: title
@@ -1082,24 +1261,29 @@ msgstr ""
 #: random-bits.xml:711
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
-      "# aptitude install locales\n"
-      "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> To configure your keyboard (if needed):"
+"To configure your locale settings to use a language other than English, "
+"install the <classname>locales</classname> support package and configure it. "
+"Currently the use of UTF-8 locales is recommended. "
+"<informalexample><screen>\n"
+"# aptitude install locales\n"
+"# dpkg-reconfigure locales\n"
+"</screen></informalexample> To configure your keyboard (if needed):"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:721
 #, no-c-format
 msgid ""
-      "# aptitude install console-setup\n"
-      "# dpkg-reconfigure keyboard-configuration"
+"# aptitude install console-setup\n"
+"# dpkg-reconfigure keyboard-configuration"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:723
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1111,7 +1295,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:734
 #, no-c-format
-msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
+msgid ""
+"If you intend to boot this system, you probably want a &arch-kernel; kernel "
+"and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
@@ -1129,7 +1315,9 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:745
 #, no-c-format
-msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid ""
+"# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</"
+"replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1141,30 +1329,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:752
 #, no-c-format
-msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
+msgid ""
+"To make your &debian-gnu; system bootable, set up your boot loader to load "
+"the installed kernel with your new root partition. Note that "
+"<command>debootstrap</command> does not install a boot loader, though you "
+"can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:759
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
+msgid ""
+"Check <userinput>info grub</userinput> <phrase arch=\"x86\">or "
+"<userinput>man lilo.conf</userinput></phrase> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing grub2 "
+"<filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</"
+"filename>. For <filename>lilo.conf</filename>, you could also copy it to the "
+"new system and edit it there. After you are done editing, call "
+"<command>lilo</command> (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:771
 #, no-c-format
 msgid ""
-      "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
-      "# aptitude install grub-pc\n"
-      "# grub-install /dev/<replaceable>hda</replaceable>\n"
-      "# update-grub\n"
-      "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>."
+"Installing and setting up <classname>grub2</classname> is as easy as: "
+"<informalexample><screen>\n"
+"# aptitude install grub-pc\n"
+"# grub-install /dev/<replaceable>hda</replaceable>\n"
+"# update-grub\n"
+"</screen></informalexample> The second command will install <command>grub2</"
+"command> (in this case in the MBR of <literal>hda</literal>). The last "
+"command will create a sane and working <filename>/boot/grub/grub.cfg</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:781
 #, no-c-format
-msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
+msgid ""
+"Note that this assumes that a <filename>/dev/hda</filename> device file has "
+"been created. There are alternative methods to install <command>grub2</"
+"command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
@@ -1177,36 +1385,44 @@ msgstr ""
 #: random-bits.xml:791
 #, no-c-format
 msgid ""
-      "boot=/dev/<replaceable>hda6</replaceable>\n"
-      "root=/dev/<replaceable>hda6</replaceable>\n"
-      "install=menu\n"
-      "delay=20\n"
-      "lba32\n"
-      "image=/vmlinuz\n"
-      "initrd=/initrd.img\n"
-      "label=Debian"
+"boot=/dev/<replaceable>hda6</replaceable>\n"
+"root=/dev/<replaceable>hda6</replaceable>\n"
+"install=menu\n"
+"delay=20\n"
+"lba32\n"
+"image=/vmlinuz\n"
+"initrd=/initrd.img\n"
+"label=Debian"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:793
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:803
 #, no-c-format
 msgid ""
-      "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
-      "boot=/dev/hda2\n"
-      "device=hd:\n"
-      "partition=6\n"
-      "root=/dev/hda6\n"
-      "magicboot=/usr/lib/yaboot/ofboot\n"
-      "timeout=50\n"
-      "image=/vmlinux\n"
-      "label=Debian\n"
-      "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
+"boot=/dev/hda2\n"
+"device=hd:\n"
+"partition=6\n"
+"root=/dev/hda6\n"
+"magicboot=/usr/lib/yaboot/ofboot\n"
+"timeout=50\n"
+"image=/vmlinux\n"
+"label=Debian\n"
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1218,15 +1434,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:817
 #, no-c-format
-msgid "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set a password for root:"
+msgid ""
+"In case you can login to the system via console, you can skip this section. "
+"If the system should be accessible via the network later on, you need to "
+"install SSH and set a password for root:"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:823
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+"# aptitude install ssh\n"
+"# passwd"
 msgstr ""
 
 #. Tag: title
@@ -1239,15 +1458,22 @@ msgstr ""
 #: random-bits.xml:829
 #, no-c-format
 msgid ""
-      "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
-      "# tasksel install standard\n"
-      "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually."
+"As mentioned earlier, the installed system will be very basic. If you would "
+"like to make the system a bit more mature, there is an easy method to "
+"install all packages with <quote>standard</quote> priority: "
+"<informalexample><screen>\n"
+"# tasksel install standard\n"
+"</screen></informalexample> Of course, you can also just use "
+"<command>aptitude</command> to install packages individually."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:840
 #, no-c-format
-msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
+msgid ""
+"After the installation there will be a lot of downloaded packages in "
+"<filename>/var/cache/apt/archives/</filename>. You can free up some "
+"diskspace by running:"
 msgstr ""
 
 #. Tag: screen
@@ -1265,25 +1491,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:859
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian-gnu; on a computer without an "
+"Ethernet card, but with just a remote gateway computer attached via a Null-"
+"Modem cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a &debian; mirror on it (e.g. to the "
+"Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:867
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:875
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:880
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1295,7 +1538,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:893
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where &debian; will "
+"be installed."
 msgstr ""
 
 #. Tag: para
@@ -1307,13 +1552,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:904
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:910
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
@@ -1325,28 +1575,33 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:923
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:928
 #, no-c-format
 msgid ""
-      "#!/bin/sh\n"
-      "\n"
-      "# We remove running modules from kernel to avoid conflicts and to\n"
-      "# reconfigure them manually.\n"
-      "modprobe -r lp parport_pc\n"
-      "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
-      "modprobe plip\n"
-      "\n"
-      "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-      "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
-      "\n"
-      "# Configure gateway\n"
-      "modprobe iptable_nat\n"
-      "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
-      "echo 1 > /proc/sys/net/ipv4/ip_forward"
+"#!/bin/sh\n"
+"\n"
+"# We remove running modules from kernel to avoid conflicts and to\n"
+"# reconfigure them manually.\n"
+"modprobe -r lp parport_pc\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
+"modprobe plip\n"
+"\n"
+"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"\n"
+"# Configure gateway\n"
+"modprobe iptable_nat\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
+"echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
 #. Tag: title
@@ -1359,9 +1614,16 @@ msgstr ""
 #: random-bits.xml:935
 #, no-c-format
 msgid ""
-      "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
-      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
-      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to "
+"set parameters for kernel modules, you also need to do this at the boot "
+"prompt. For example, to boot the installer and set values for the <quote>io</"
+"quote> and <quote>irq</quote> options for the parport_pc module, enter the "
+"following at the boot prompt: <informalexample><screen>\n"
+"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc."
+"irq=<replaceable>7</replaceable>\n"
+"</screen></informalexample> Below are the answers that should be given "
+"during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1373,7 +1635,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:956
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1385,13 +1649,20 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:969
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:978
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1409,19 +1680,24 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:998
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1003
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1009
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
@@ -1433,67 +1709,112 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1030
 #, no-c-format
-msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
+msgid ""
+"In some countries PPP over Ethernet (PPPoE) is a common protocol for "
+"broadband (ADSL or cable) connections to an Internet Service Provider. "
+"Setting up a network connection using PPPoE is not supported by default in "
+"the installer, but can be made to work very simply. This section explains "
+"how."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1038
 #, no-c-format
-msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PPPoE connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1043
 #, no-c-format
-msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
+msgid ""
+"To have the option of setting up and using PPPoE during the installation, "
+"you will need to install using one of the CD-ROM/DVD images that are "
+"available. It is not supported for other installation methods (e.g. "
+"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1050
 #, no-c-format
-msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
+msgid ""
+"Installing over PPPoE is mostly the same as any other installation. The "
+"following steps explain the differences."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1058
 #, no-c-format
-msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
+msgid ""
+"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</"
+"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> "
+"for information on how to add a boot parameter. </para> </footnote>. This "
+"will ensure the component responsible for the setup of PPPoE (<classname>ppp-"
+"udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1073
 #, no-c-format
-msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
+msgid ""
+"Follow the regular initial steps of the installation (language, country and "
+"keyboard selection; the loading of additional installer components<footnote> "
+"<para> The <classname>ppp-udeb</classname> component is loaded as one of the "
+"additional components in this step. If you want to install at medium or low "
+"priority (expert mode), you can also manually select the <classname>ppp-"
+"udeb</classname> instead of entering the <quote>modules</quote> parameter at "
+"the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1092
 #, no-c-format
-msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
+msgid ""
+"The next step is the detection of network hardware, in order to identify any "
+"Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1098
 #, no-c-format
-msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
+msgid ""
+"After this the actual setup of PPPoE is started. The installer will probe "
+"all the detected Ethernet interfaces in an attempt to find a PPPoE "
+"concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1104
 #, no-c-format
-msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
+msgid ""
+"It is possible that the concentrator will not to be found at the first "
+"attempt. This can happen occasionally on slow or loaded networks or with "
+"faulty servers. In most cases a second attempt to detect the concentrator "
+"will be successful; to retry, select <guimenuitem>Configure and start a "
+"PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1113
 #, no-c-format
-msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
+msgid ""
+"After a concentrator is found, the user will be prompted to type the login "
+"information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1119
 #, no-c-format
-msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
+msgid ""
+"At this point the installer will use the provided information to establish "
+"the PPPoE connection. If the correct information was provided, the PPPoE "
+"connection should be configured and the installer should be able to use it "
+"to connect to the Internet and retrieve packages over it (if needed). If the "
+"login information is not correct or some error appears, the installer will "
+"stop, but the configuration can be attempted again by selecting the menu "
+"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
@@ -1505,49 +1826,89 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1140
 #, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
+msgid ""
+"The graphical version of the installer is only available for a limited "
+"number of architectures, including &arch-title;. The functionality of the "
+"graphical installer is essentially the same as that of the regular installer "
+"as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1148
 #, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
+msgid ""
+"Although the functionality is identical, the graphical installer still has a "
+"few significant advantages. The main advantage is that it supports more "
+"languages, namely those that use a character set that cannot be displayed "
+"with the regular <quote>newt</quote> frontend. It also has a few usability "
+"advantages such as the option to use a mouse, and in some cases several "
+"questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1157
 #, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
+msgid ""
+"The graphical installer is available with all CD images and with the hd-"
+"media installation method. To boot the graphical installer simply select the "
+"relevant option from the boot menu. Expert and rescue mode for the graphical "
+"installer can be selected from the <quote>Advanced options</quote> menu. The "
+"previously used boot methods <userinput>installgui</userinput>, "
+"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
+"still be used from the boot prompt which is shown after selecting the "
+"<quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1168
 #, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
+msgid ""
+"There is also a graphical installer image that can be netbooted. And there "
+"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> "
+"<para> The mini ISO image can be downloaded from a &debian; mirror as "
+"described in <xref linkend=\"downloading-files\"/>. Look for "
+"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
+"mainly useful for testing."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1181
 #, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
+msgid ""
+"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
+"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image "
+"can be downloaded from a &debian; mirror as described in <xref linkend="
+"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
+"</para> </footnote>. It should work on almost all PowerPC systems that have "
+"an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1195
 #, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
+msgid ""
+"Just as with the regular installer it is possible to add boot parameters "
+"when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1201
 #, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
+msgid ""
+"The graphical installer requires significantly more memory to run than the "
+"regular installer: &minimum-memory-gtk;. If insufficient memory is "
+"available, it will automatically fall back to the regular <quote>newt</"
+"quote> frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1208
 #, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
+msgid ""
+"If the amount of memory in your system is below &minimum-memory;, the "
+"graphical installer may fail to boot at all while booting the regular "
+"installer would still work. Using the regular installer is recommended for "
+"systems with little available memory."
 msgstr ""
 
 #. Tag: title
@@ -1559,24 +1920,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1219
 #, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
+msgid ""
+"As already mentioned, the graphical installer basically works the same as "
+"the regular installer and thus the rest of this manual can be used to guide "
+"you through the installation process."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1225
 #, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgid ""
+"If you prefer using the keyboard over the mouse, there are two things you "
+"need to know. To expand a collapsed list (used for example for the selection "
+"of countries within continents), you can use the <keycap>+</keycap> and "
+"<keycap>-</keycap> keys. For questions where more than one item can be "
+"selected (e.g. task selection), you first need to tab to the &BTN-CONT; "
+"button after making your selections; hitting enter will toggle a selection, "
+"not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1235
 #, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgid ""
+"If a dialog offers additional help information, a <guibutton>Help</"
+"guibutton> button will be displayed. The help information can be accessed "
+"either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1241
 #, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgid ""
+"To switch to another console, you will also need to use the <keycap>Ctrl</"
+"keycap> key, just as with the X Window System. For example, to switch to VT2 "
+"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> "
+"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical "
+"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</"
+"keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""
-
diff --git a/po/nn/using-d-i.po b/po/nn/using-d-i.po
index bbba423e4..85197cce6 100644
--- a/po/nn/using-d-i.po
+++ b/po/nn/using-d-i.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,79 +29,147 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:8
 #, no-c-format
-msgid "The &debian; Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started."
+msgid ""
+"The &debian; Installer consists of a number of special-purpose components to "
+"perform each installation task. Each component performs its task, asking the "
+"user questions as necessary to do its job. The questions themselves are "
+"given priorities, and the priority of questions to be asked is set when the "
+"installer is started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:16
 #, no-c-format
-msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked."
+msgid ""
+"When a default installation is performed, only essential (high priority) "
+"questions will be asked. This results in a highly automated installation "
+"process with little user interaction. Components are automatically run in "
+"sequence; which components are run depends mainly on the installation method "
+"you use and on your hardware. The installer will use default values for "
+"questions that are not asked."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:25
 #, no-c-format
-msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified."
+msgid ""
+"If there is a problem, the user will see an error screen, and the installer "
+"menu may be shown in order to select some alternative action. If there are "
+"no problems, the user will never see the installer menu, but will simply "
+"answer questions for each component in turn. Serious error notifications are "
+"set to priority <quote>critical</quote> so the user will always be notified."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:34
 #, no-c-format
-msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
+msgid ""
+"Some of the defaults that the installer uses can be influenced by passing "
+"boot arguments when &d-i; is started. If, for example, you wish to force "
+"static network configuration (DHCP is used by default if available), you "
+"could add the boot parameter <userinput>netcfg/disable_dhcp=true</"
+"userinput>. See <xref linkend=\"installer-args\"/> for available options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:42
 #, no-c-format
-msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>."
+msgid ""
+"Power users may be more comfortable with a menu-driven interface, where each "
+"step is controlled by the user rather than the installer performing each "
+"step automatically in sequence. To use the installer in a manual, menu-"
+"driven way, add the boot argument <userinput>priority=medium</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:50
 #, no-c-format
-msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;."
+msgid ""
+"If your hardware requires you to pass options to kernel modules as they are "
+"installed, you will need to start the installer in <quote>expert</quote> "
+"mode. This can be done by either using the <command>expert</command> command "
+"to start the installer or by adding the boot argument "
+"<userinput>priority=low</userinput>. Expert mode gives you full control over "
+"&d-i;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:59
 #, no-c-format
-msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgid ""
+"For this architecture the &d-i; supports two different user interfaces: a "
+"character-based one and a graphical one. The character-based interface is "
+"used by default unless you selected the <quote>Graphical install</quote> "
+"option in the initial boot menu. For more information about the graphical "
+"installer, please refer to <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:67
 #, no-c-format
-msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
+msgid ""
+"For this architecture the installer uses a character-based user interface. A "
+"graphical user interface is currently not available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:72
 #, no-c-format
-msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
+msgid ""
+"In the character-based environment the use of a mouse is not supported. Here "
+"are the keys you can use to navigate within the various dialogs. The "
+"<keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move "
+"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> "
+"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move "
+"<quote>backward</quote> between displayed buttons and selections. The "
+"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items "
+"within a scrollable list, and also scroll the list itself. In addition, in "
+"long lists, you can type a letter to cause the list to scroll directly to "
+"the section with items starting with the letter you typed and use <keycap>Pg-"
+"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The "
+"<keycap>space bar</keycap> selects an item such as a checkbox. Use "
+"&enterkey; to activate choices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:89
 #, no-c-format
-msgid "Some dialogs may offer additional help information. If help is available this will be indicated on the bottom line of the screen by displaying that help information can be accessed by pressing the <keycap>F1</keycap> key."
+msgid ""
+"Some dialogs may offer additional help information. If help is available "
+"this will be indicated on the bottom line of the screen by displaying that "
+"help information can be accessed by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:95
 #, no-c-format
-msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
+msgid ""
+"S/390 does not support virtual consoles. You may open a second and third ssh "
+"session to view the logs described below."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:100
 #, no-c-format
-msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"Error messages and logs are redirected to the fourth console. You can access "
+"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</"
+"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing "
+"the <keycap>F4</keycap> function key); get back to the main installer "
+"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></"
+"keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:110
 #, no-c-format
-msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"These messages can also be found in <filename>/var/log/syslog</filename>. "
+"After installation, this log is copied to <filename>/var/log/installer/"
+"syslog</filename> on your new system. Other installation messages may be "
+"found in <filename>/var/log/</filename> during the installation, and "
+"<filename>/var/log/installer/</filename> after the computer has been booted "
+"into the installed system."
 msgstr ""
 
 #. Tag: title
@@ -112,7 +181,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:125
 #, no-c-format
-msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
+msgid ""
+"Here is a list of installer components with a brief description of each "
+"component's purpose. Details you might need to know about using a particular "
+"component are in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: term
@@ -124,13 +196,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:136
 #, no-c-format
-msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
+msgid ""
+"Shows the list of components to the user during installer operation, and "
+"starts a component when it is selected. Main-menu's questions are set to "
+"priority medium, so if your priority is set to high or critical (high is the "
+"default), you will not see the menu. On the other hand, if there is an error "
+"which requires your intervention, the question priority may be downgraded "
+"temporarily to allow you to resolve the problem, and in that case the menu "
+"may appear."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:146
 #, no-c-format
-msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
+msgid ""
+"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly "
+"to back all the way out of the currently running component."
 msgstr ""
 
 #. Tag: term
@@ -142,7 +223,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:155
 #, no-c-format
-msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
+msgid ""
+"Allows the user to select localization options for the installation and the "
+"installed system: language, country and locales. The installer will display "
+"messages in the selected language, unless the translation for that language "
+"is not complete in which case some messages may be shown in English."
 msgstr ""
 
 #. Tag: term
@@ -154,7 +239,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:167
 #, no-c-format
-msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
+msgid ""
+"Shows a list of keyboards, from which the user chooses the model which "
+"matches his own."
 msgstr ""
 
 #. Tag: term
@@ -166,7 +253,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:176
 #, no-c-format
-msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
+msgid ""
+"Automatically detects most of the system's hardware, including network "
+"cards, disk drives, and PCMCIA."
 msgstr ""
 
 #. Tag: term
@@ -190,7 +279,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:193
 #, no-c-format
-msgid "Configures the computer's network connections so it can communicate over the internet."
+msgid ""
+"Configures the computer's network connections so it can communicate over the "
+"internet."
 msgstr ""
 
 #. Tag: term
@@ -202,7 +293,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:202
 #, no-c-format
-msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
+msgid ""
+"Searches for ISO images (<filename>.iso</filename> files) on hard drives."
 msgstr ""
 
 #. Tag: term
@@ -214,7 +306,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:210
 #, no-c-format
-msgid "Presents a list of &debian; archive mirrors. The user may choose the source of his installation packages."
+msgid ""
+"Presents a list of &debian; archive mirrors. The user may choose the source "
+"of his installation packages."
 msgstr ""
 
 #. Tag: term
@@ -226,7 +320,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:219
 #, no-c-format
-msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
+msgid ""
+"Checks integrity of a CD-ROM. This way, the user may assure him/herself that "
+"the installation CD-ROM was not corrupted."
 msgstr ""
 
 #. Tag: term
@@ -238,7 +334,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:228
 #, no-c-format
-msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
+msgid ""
+"Lowmem tries to detect systems with low memory and then does various tricks "
+"to remove unnecessary parts of &d-i; from the memory (at the cost of some "
+"features)."
 msgstr ""
 
 #. Tag: term
@@ -250,7 +349,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:238
 #, no-c-format
-msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
+msgid ""
+"Anna's Not Nearly APT. Installs packages which have been retrieved from the "
+"chosen mirror or CD."
 msgstr ""
 
 #. Tag: term
@@ -274,7 +375,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:255
 #, no-c-format
-msgid "Updates the system clock and determines whether the clock is set to UTC or not."
+msgid ""
+"Updates the system clock and determines whether the clock is set to UTC or "
+"not."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +401,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:272
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
+msgid ""
+"Allows the user to partition disks attached to the system, create file "
+"systems on the selected partitions, and attach them to the mountpoints. "
+"Included are also interesting features like a fully automatic mode or LVM "
+"support. This is the preferred partitioning tool in &debian;."
 msgstr ""
 
 #. Tag: term
@@ -310,7 +417,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:284
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
+msgid ""
+"Allows the user to partition disks attached to the system. A partitioning "
+"program appropriate to your computer's architecture is chosen."
 msgstr ""
 
 #. Tag: term
@@ -322,7 +431,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:294
 #, no-c-format
-msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
+msgid ""
+"Displays a list of partitions, and creates file systems on the selected "
+"partitions according to user instructions."
 msgstr ""
 
 #. Tag: term
@@ -334,7 +445,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:303
 #, no-c-format
-msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
+msgid ""
+"Helps the user with the configuration of the <firstterm>LVM</firstterm> "
+"(Logical Volume Manager)."
 msgstr ""
 
 #. Tag: term
@@ -346,7 +459,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:312
 #, no-c-format
-msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
+msgid ""
+"Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant "
+"Array of Inexpensive Disks). This Software RAID is usually superior to the "
+"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
 #. Tag: term
@@ -358,7 +474,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:323
 #, no-c-format
-msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
+msgid ""
+"Installs the most basic set of packages which would allow the computer to "
+"operate under &debian-gnu; when rebooted."
 msgstr ""
 
 #. Tag: term
@@ -370,7 +488,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:332
 #, no-c-format
-msgid "Configures apt, mostly automatically, based on what media the installer is running from."
+msgid ""
+"Configures apt, mostly automatically, based on what media the installer is "
+"running from."
 msgstr ""
 
 #. Tag: term
@@ -382,7 +502,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:341
 #, no-c-format
-msgid "Uses <classname>tasksel</classname> to select and install additional software."
+msgid ""
+"Uses <classname>tasksel</classname> to select and install additional "
+"software."
 msgstr ""
 
 #. Tag: term
@@ -394,7 +516,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:349
 #, no-c-format
-msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
+msgid ""
+"Detects currently installed operating systems on the computer and passes "
+"this information to the bootloader-installer, which may offer you an ability "
+"to add discovered operating systems to the bootloader's start menu. This way "
+"the user could easily choose at the boot time which operating system to "
+"start."
 msgstr ""
 
 #. Tag: term
@@ -406,7 +533,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:361
 #, no-c-format
-msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
+msgid ""
+"The various bootloader installers each install a boot loader program on the "
+"hard disk, which is necessary for the computer to start up using &arch-"
+"kernel; without using a floppy or CD-ROM. Many boot loaders allow the user "
+"to choose an alternate operating system each time the computer boots."
 msgstr ""
 
 #. Tag: term
@@ -418,7 +549,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:372
 #, no-c-format
-msgid "Allows the user to execute a shell from the menu, or in the second console."
+msgid ""
+"Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
 #. Tag: term
@@ -430,7 +562,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:381
 #, no-c-format
-msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to &debian; developers later."
+msgid ""
+"Provides a way for the user to record information on a floppy disk, network, "
+"hard disk, or other media when trouble is encountered, in order to "
+"accurately report installer software problems to &debian; developers later."
 msgstr ""
 
 #. Tag: title
@@ -442,7 +577,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:400
 #, no-c-format
-msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
+msgid ""
+"In this section we will describe each installer component in detail. The "
+"components have been grouped into stages that should be recognizable for "
+"users. They are presented in the order they appear during the install. Note "
+"that not all modules will be used for every installation; which modules are "
+"actually used depends on the installation method you use and on your "
+"hardware."
 msgstr ""
 
 #. Tag: title
@@ -454,19 +595,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:413
 #, no-c-format
-msgid "Let's assume the &debian; Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
+msgid ""
+"Let's assume the &debian; Installer has booted and you are facing its first "
+"screen. At this time, the capabilities of &d-i; are still quite limited. It "
+"doesn't know much about your hardware, preferred language, or even the task "
+"it should perform. Don't worry. Because &d-i; is quite clever, it can "
+"automatically probe your hardware, locate the rest of its components and "
+"upgrade itself to a capable installation system. However, you still need to "
+"help &d-i; with some information it can't determine automatically (like "
+"selecting your preferred language, keyboard layout or desired network "
+"mirror)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:426
 #, no-c-format
-msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
+msgid ""
+"You will notice that &d-i; performs <firstterm>hardware detection</"
+"firstterm> several times during this stage. The first time is targeted "
+"specifically at the hardware needed to load installer components (e.g. your "
+"CD-ROM or network card). As not all drivers may be available during this "
+"first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:434
 #, no-c-format
-msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
+msgid ""
+"During hardware detection &d-i; checks if any of the drivers for the "
+"hardware devices in your system require firmware to be loaded. If any "
+"firmware is requested but unavailable, a dialog will be displayed that "
+"allows the missing firmware to be loaded from a removable medium. See <xref "
+"linkend=\"loading-firmware\"/> for further details."
 msgstr ""
 
 #. Tag: title
@@ -478,43 +638,75 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:451
 #, no-c-format
-msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system."
+msgid ""
+"One of the first things &d-i; does, is to check available memory. If the "
+"available memory is limited, this component will make some changes in the "
+"installation process which hopefully will allow you to install &debian-gnu; "
+"on your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:458
 #, no-c-format
-msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
+msgid ""
+"The first measure taken to reduce memory consumption by the installer is to "
+"disable translations, which means that the installation can only be done in "
+"English. Of course, you can still localize the installed system after the "
+"installation has completed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:465
 #, no-c-format
-msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
+msgid ""
+"If that is not sufficient, the installer will further reduce memory "
+"consumption by loading only those components essential to complete a basic "
+"installation. This reduces the functionality of the installation system. You "
+"will be given the opportunity to load additional components manually, but "
+"you should be aware that each component you select will use additional "
+"memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:474
 #, no-c-format
-msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
+msgid ""
+"If the installer runs in low memory mode, it is recommended to create a "
+"relatively large swap partition (64&ndash;128MB). The swap partition will be "
+"used as virtual memory and thus increases the amount of memory available to "
+"the system. The installer will activate the swap partition as early as "
+"possible in the installation process. Note that heavy use of swap will "
+"reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:484
 #, no-c-format
-msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
+msgid ""
+"Despite these measures, it is still possible that your system freezes, that "
+"unexpected errors occur or that processes are killed by the kernel because "
+"the system runs out of memory (which will result in <quote>Out of memory</"
+"quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:491
 #, no-c-format
-msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
+msgid ""
+"For example, it has been reported that creating a big ext3 file system fails "
+"in low memory mode when there is insufficient swap space. If a larger swap "
+"doesn't help, try creating the file system as ext2 (which is an essential "
+"component of the installer) instead. It is possible to change an ext2 "
+"partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:499
 #, no-c-format
-msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
+msgid ""
+"It is possible to force the installer to use a higher lowmem level than the "
+"one based on available memory by using the boot parameter <quote>lowmem</"
+"quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
@@ -526,61 +718,116 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:516
 #, no-c-format
-msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, location and locales."
+msgid ""
+"In most cases the first questions you will be asked concern the selection of "
+"localization options to be used both for the installation and for the "
+"installed system. The localization options consist of language, location and "
+"locales."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:523
 #, no-c-format
-msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
+msgid ""
+"The language you choose will be used for the rest of the installation "
+"process, provided a translation of the different dialogs is available. If no "
+"valid translation is available for the selected language, the installer will "
+"default to English."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:530
 #, no-c-format
-msgid "The selected geographic location (in most cases a country) will be used later in the installation process to select the correct time zone and a &debian; mirror appropriate for that country. Language and country together will help determine the default locale for your system and select the correct keyboard layout."
+msgid ""
+"The selected geographic location (in most cases a country) will be used "
+"later in the installation process to select the correct time zone and a "
+"&debian; mirror appropriate for that country. Language and country together "
+"will help determine the default locale for your system and select the "
+"correct keyboard layout."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:538
 #, no-c-format
-msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
+msgid ""
+"You will first be asked to select your preferred language. The language "
+"names are listed both in English (left side) and in the language itself "
+"(right side); the names on the right side are also shown in the proper "
+"script for the language. The list is sorted on the English names. At the top "
+"of the list is an extra option that allows you to select the <quote>C</"
+"quote> locale instead of a language. Choosing the <quote>C</quote> locale "
+"will result in the installation proceding in English; the installed system "
+"will have no localization support as the <classname>locales</classname> "
+"package will not be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:550
 #, no-c-format
-msgid "Next you will be asked to select your geographic location. If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
+msgid ""
+"Next you will be asked to select your geographic location. If you selected a "
+"language that is recognized as an official language for more than one "
+"country<footnote> <para> In technical terms: where multiple locales exist "
+"for that language with differing country codes. </para> </footnote>, you "
+"will be shown a list of only those countries. To select a country that is "
+"not in that list, choose <guimenuitem>other</guimenuitem> (the last option). "
+"You will then be presented with a list of continents; selecting a continent "
+"will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:567
 #, no-c-format
-msgid "If the language has only one country associated with it, a list of countries will be displayed for the continent or region the country belongs to, with that country selected as the default. Use the <guibutton>Go Back</guibutton> option to select countries on a different continent."
+msgid ""
+"If the language has only one country associated with it, a list of countries "
+"will be displayed for the continent or region the country belongs to, with "
+"that country selected as the default. Use the <guibutton>Go Back</guibutton> "
+"option to select countries on a different continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:574
 #, no-c-format
-msgid "It is important to select the country where you live or where you are located as it determines the time zone that will be configured for the installed system."
+msgid ""
+"It is important to select the country where you live or where you are "
+"located as it determines the time zone that will be configured for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:580
 #, no-c-format
-msgid "If you selected a combination of language and country for which no locale is defined and there exist multiple locales for the language, then the installer will allow you to choose which of those locales you prefer as the default locale for the installed system<footnote> <para> At medium and low priority you can always select your preferred locale from those available for the selected language (if there's more than one). </para> </footnote>. In all other cases a default locale will be selected based on the selected language and country."
+msgid ""
+"If you selected a combination of language and country for which no locale is "
+"defined and there exist multiple locales for the language, then the "
+"installer will allow you to choose which of those locales you prefer as the "
+"default locale for the installed system<footnote> <para> At medium and low "
+"priority you can always select your preferred locale from those available "
+"for the selected language (if there's more than one). </para> </footnote>. "
+"In all other cases a default locale will be selected based on the selected "
+"language and country."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:595
 #, no-c-format
-msgid "Any default locale selected as described in the previous paragraph will use <firstterm>UTF-8</firstterm> as character encoding."
+msgid ""
+"Any default locale selected as described in the previous paragraph will use "
+"<firstterm>UTF-8</firstterm> as character encoding."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:600
 #, no-c-format
-msgid "If you are installing at low priority, you will have the option of selecting additional locales, including so-called <quote>legacy</quote> locales<footnote> <para> Legacy locales are locales which do not use UTF-8, but one of the older standards for character encoding such as ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by Japanese). </para> </footnote>, to be generated for the installed system; if you do, you will be asked which of the selected locales should be the default for the installed system."
+msgid ""
+"If you are installing at low priority, you will have the option of selecting "
+"additional locales, including so-called <quote>legacy</quote> "
+"locales<footnote> <para> Legacy locales are locales which do not use UTF-8, "
+"but one of the older standards for character encoding such as "
+"ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by "
+"Japanese). </para> </footnote>, to be generated for the installed system; if "
+"you do, you will be asked which of the selected locales should be the "
+"default for the installed system."
 msgstr ""
 
 #. Tag: title
@@ -592,13 +839,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:626
 #, no-c-format
-msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>dpkg-reconfigure keyboard-configuration</command> as root after you have completed the installation)."
+msgid ""
+"Keyboards are often tailored to the characters used in a language. Select a "
+"layout that conforms to the keyboard you are using, or select something "
+"close if the keyboard layout you want isn't represented. Once the system "
+"installation is complete, you'll be able to select a keyboard layout from a "
+"wider range of choices (run <command>dpkg-reconfigure keyboard-"
+"configuration</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:636
 #, no-c-format
-msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration."
+msgid ""
+"Move the highlight to the keyboard selection you desire and press "
+"&enterkey;. Use the arrow keys to move the highlight &mdash; they are in the "
+"same place in all national language keyboard layouts, so they are "
+"independent of the keyboard configuration."
 msgstr ""
 
 #. Tag: title
@@ -610,25 +867,51 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:664
 #, no-c-format
-msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the &debian; Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
+msgid ""
+"When installing via the <emphasis>hd-media</emphasis> method, there will be "
+"a moment where you need to find and mount the &debian; Installer iso image "
+"in order to get the rest of the installation files. The component "
+"<command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:671
 #, no-c-format
-msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid &debian; iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
+msgid ""
+"At first, <command>iso-scan</command> automatically mounts all block devices "
+"(e.g. partitions) which have some known filesystem on them and sequentially "
+"searches for filenames ending with <filename>.iso</filename> (or <filename>."
+"ISO</filename> for that matter). Beware that the first attempt scans only "
+"files in the root directory and in the first level of subdirectories (i.e. "
+"it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, "
+"<filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not "
+"<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). "
+"After an iso image has been found, <command>iso-scan</command> checks its "
+"content to determine if the image is a valid &debian; iso image or not. In "
+"the former case we are done, in the latter <command>iso-scan</command> seeks "
+"for another image."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:688
 #, no-c-format
-msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
+msgid ""
+"In case the previous attempt to find an installer iso image fails, "
+"<command>iso-scan</command> will ask you whether you would like to perform a "
+"more thorough search. This pass doesn't just look into the topmost "
+"directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:695
 #, no-c-format
-msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
+msgid ""
+"If <command>iso-scan</command> does not discover your installer iso image, "
+"reboot back to your original operating system and check if the image is "
+"named correctly (ending in <filename>.iso</filename>), if it is placed on a "
+"filesystem recognizable by &d-i;, and if it is not corrupted (verify the "
+"checksum). Experienced Unix users could do this without rebooting on the "
+"second console."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +923,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:718
 #, no-c-format
-msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
+msgid ""
+"As you enter this step, if the system detects that you have more than one "
+"network device, you'll be asked to choose which device will be your "
+"<emphasis>primary</emphasis> network interface, i.e. the one which you want "
+"to use for installation. The other interfaces won't be configured at this "
+"time. You may configure additional interfaces after installation is "
+"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> "
+"<manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: title
@@ -652,7 +942,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:733
 #, no-c-format
-msgid "By default, &d-i; tries to configure your computer's network automatically as far as possible. If the automatic configuration fails, that may be caused by many factors ranging from an unplugged network cable to missing infrastructure for automatic configuration. For further explanation in case of errors, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. Sometimes the network services used for autoconfiguration can be slow in their responses, so if you are sure everything is in place, simply start the autoconfiguration attempt again. If autoconfiguration fails repeatedly, you can instead choose the manual network setup."
+msgid ""
+"By default, &d-i; tries to configure your computer's network automatically "
+"as far as possible. If the automatic configuration fails, that may be caused "
+"by many factors ranging from an unplugged network cable to missing "
+"infrastructure for automatic configuration. For further explanation in case "
+"of errors, check the error messages on the fourth console. In any case, you "
+"will be asked if you want to retry, or if you want to perform a manual "
+"setup. Sometimes the network services used for autoconfiguration can be slow "
+"in their responses, so if you are sure everything is in place, simply start "
+"the autoconfiguration attempt again. If autoconfiguration fails repeatedly, "
+"you can instead choose the manual network setup."
 msgstr ""
 
 #. Tag: title
@@ -664,13 +964,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:753
 #, no-c-format
-msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network name</quote>) and a <computeroutput>WEP key</computeroutput> or <computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
+msgid ""
+"The manual network setup in turn asks you a number of questions about your "
+"network, notably <computeroutput>IP address</computeroutput>, "
+"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</"
+"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and "
+"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a "
+"wireless network interface, you will be asked to provide your "
+"<computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network "
+"name</quote>) and a <computeroutput>WEP key</computeroutput> or "
+"<computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers "
+"from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:769
 #, no-c-format
-msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
+msgid ""
+"Some technical details you might, or might not, find handy: the program "
+"assumes the network IP address is the bitwise-AND of your system's IP "
+"address and your netmask. The default broadcast address is calculated as the "
+"bitwise OR of your system's IP address with the bitwise negation of the "
+"netmask. It will also guess your gateway. If you can't find any of these "
+"answers, use the offered defaults &mdash; if necessary, you can change them "
+"by editing <filename>/etc/network/interfaces</filename> once the system has "
+"been installed."
 msgstr ""
 
 #. Tag: title
@@ -682,13 +1000,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:785
 #, no-c-format
-msgid "From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
+msgid ""
+"From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 "
+"as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and "
+"IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:791
 #, no-c-format
-msgid "Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration using NDP (Neighbor Discovery Protocol, including recursive DNS server (RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed stateless/stateful autoconfiguration (address configuration via NDP, additional parameters via DHCPv6)."
+msgid ""
+"Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration "
+"Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration "
+"using NDP (Neighbor Discovery Protocol, including recursive DNS server "
+"(RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed "
+"stateless/stateful autoconfiguration (address configuration via NDP, "
+"additional parameters via DHCPv6)."
 msgstr ""
 
 #. Tag: title
@@ -700,7 +1027,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:839
 #, no-c-format
-msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
+msgid ""
+"The installer will first attempt to connect to a time server on the Internet "
+"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set "
+"the system time. If this does not succeed, the installer will assume the "
+"time and date obtained from the system clock when the installation system "
+"was booted are correct. It is not possible to manually set the system time "
+"during the installation process."
 msgstr ""
 
 #. Tag: para
@@ -712,25 +1045,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:861
 #, no-c-format
-msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone."
+msgid ""
+"Depending on the location selected earlier in the installation process, you "
+"may be shown a list of time zones relevant for that location. If your "
+"location has only one time zone and you are doing a default installation, "
+"you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:869
 #, no-c-format
-msgid "In expert mode or when installing at medium priority, you will have the additional option to select <quote>Coordinated Universal Time</quote> (UTC) as time zone."
+msgid ""
+"In expert mode or when installing at medium priority, you will have the "
+"additional option to select <quote>Coordinated Universal Time</quote> (UTC) "
+"as time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:875
 #, no-c-format
-msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
+msgid ""
+"If for some reason you wish to set a time zone for the installed system that "
+"does <emphasis>not</emphasis> match the selected location, there are two "
+"options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:886
 #, no-c-format
-msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:"
+msgid ""
+"The simplest option is to just select a different time zone after the "
+"installation has been completed and you've booted into the new system. The "
+"command to do this is:"
 msgstr ""
 
 #. Tag: screen
@@ -742,13 +1088,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:898
 #, no-c-format
-msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
+msgid ""
+"Alternatively, the time zone can be set at the very start of the "
+"installation by passing the parameter <userinput>time/"
+"zone=<replaceable>value</replaceable></userinput> when you boot the "
+"installation system. The value should of course be a valid time zone, for "
+"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:912
 #, no-c-format
-msgid "For automated installations the time zone can be set to any desired value using preseeding."
+msgid ""
+"For automated installations the time zone can be set to any desired value "
+"using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -760,7 +1113,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:927
 #, no-c-format
-msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
+msgid ""
+"Just before configuring the clock, the installer will allow you to set up "
+"the <quote>root</quote> account and/or an account for the first user. Other "
+"user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
@@ -772,19 +1128,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:945
 #, no-c-format
-msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
+msgid ""
+"The <emphasis>root</emphasis> account is also called the <emphasis>super-"
+"user</emphasis>; it is a login that bypasses all security protection on your "
+"system. The root account should only be used to perform system "
+"administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:953
 #, no-c-format
-msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
+msgid ""
+"Any password you create should contain at least 6 characters, and should "
+"contain both upper- and lower-case characters, as well as punctuation "
+"characters. Take extra care when setting your root password, since it is "
+"such a powerful account. Avoid dictionary words or use of any personal "
+"information which could be guessed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:961
 #, no-c-format
-msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
+msgid ""
+"If anyone ever tells you they need your root password, be extremely wary. "
+"You should normally never give your root password out, unless you are "
+"administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
@@ -796,25 +1164,42 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:973
 #, no-c-format
-msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
+msgid ""
+"The system will ask you whether you wish to create an ordinary user account "
+"at this point. This account should be your main personal log-in. You should "
+"<emphasis>not</emphasis> use the root account for daily use or as your "
+"personal login."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:982
 #, no-c-format
-msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
+msgid ""
+"Why not? Well, one reason to avoid using root's privileges is that it is "
+"very easy to do irreparable damage as root. Another reason is that you might "
+"be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; "
+"that is a program that takes advantage of your super-user powers to "
+"compromise the security of your system behind your back. Any good book on "
+"Unix system administration will cover this topic in more detail &mdash; "
+"consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:992
 #, no-c-format
-msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
+msgid ""
+"You will first be prompted for the user's full name. Then you'll be asked "
+"for a name for the user account; generally your first name or something "
+"similar will suffice and indeed will be the default. Finally, you will be "
+"prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:999
 #, no-c-format
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgid ""
+"If at any point after installation you would like to create another account, "
+"use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
@@ -826,28 +1211,45 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1011
 #, no-c-format
-msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
+msgid ""
+"At this time, after hardware detection has been executed a final time, &d-i; "
+"should be at its full strength, customized for the user's needs and ready to "
+"do some real work. As the title of this section indicates, the main task of "
+"the next few components lies in partitioning your disks, creating "
+"filesystems, assigning mountpoints and optionally configuring closely "
+"related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1032
 #, no-c-format
-msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
+msgid ""
+"If you are uncomfortable with partitioning, or just want to know more "
+"details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1038
 #, no-c-format
 msgid ""
-      "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
-      "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n"
-      "</screen></informalexample> Note that this will make any existing data on that disk inaccessible."
+"If a hard disk has previously used under Solaris, the partitioner may not "
+"detect the size of the drive correctly. Creating a new partition table does "
+"not fix this issue. What does help, is to <quote>zero</quote> the first few "
+"sectors of the drive: <informalexample><screen>\n"
+"# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; "
+"sync\n"
+"</screen></informalexample> Note that this will make any existing data on "
+"that disk inaccessible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1051
 #, no-c-format
-msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"First you will be given the opportunity to automatically partition either an "
+"entire drive, or available free space on a drive. This is also called "
+"<quote>guided</quote> partitioning. If you do not want to autopartition, "
+"choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
@@ -859,19 +1261,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1062
 #, no-c-format
-msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
+msgid ""
+"The partitioner used in &d-i; is fairly versatile. It allows to create many "
+"different partitioning schemes, using various partition tables, file systems "
+"and advanced block devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1068
 #, no-c-format
-msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
+msgid ""
+"Exactly which options are available depends mainly on the architecture, but "
+"also on other factors. For example, on systems with limited internal memory "
+"some options may not be available. Defaults may vary as well. The type of "
+"partition table used by default can for example be different for large "
+"capacity hard disks than for smaller hard disks. Some options can only be "
+"changed when installing at medium or low debconf priority; at higher "
+"priorities sensible defaults will be used."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1079
 #, no-c-format
-msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
+msgid ""
+"The installer supports various forms of advanced partitioning and use of "
+"storage devices, which in many cases can be used in combination."
 msgstr ""
 
 #. Tag: emphasis
@@ -901,13 +1315,18 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1096
 #, no-c-format
-msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
+msgid ""
+"<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1098
 #, no-c-format
-msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
+msgid ""
+"Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support "
+"for Serial ATA RAID is currently only available if enabled when the "
+"installer is booted. Further information is available on <ulink url=\"&url-d-"
+"i-sataraid;\">our Wiki</ulink>."
 msgstr ""
 
 #. Tag: para
@@ -919,7 +1338,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1106
 #, no-c-format
-msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
+msgid ""
+"See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. "
+"Support for multipath is currently only available if enabled when the "
+"installer is booted."
 msgstr ""
 
 #. Tag: para
@@ -931,13 +1353,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1118
 #, no-c-format
-msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></phrase>"
+msgid ""
+"<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> "
+"<emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</"
+"emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></"
+"phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1123
 #, no-c-format
-msgid "The default file system selected in most cases is ext3; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
+msgid ""
+"The default file system selected in most cases is ext3; for <filename>/boot</"
+"filename> partitions ext2 will be selected by default when guided "
+"partitioning is used."
 msgstr ""
 
 #. Tag: para
@@ -973,37 +1402,59 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1141
 #, no-c-format
-msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:"
+msgid ""
+"As ZFS support in the installer is still in development, only a basic subset "
+"of ZFS features are supported. Some of them can be enabled manually after "
+"the initial install, but there are some caveats:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1146
 #, no-c-format
-msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the <quote>zfs create</quote> command."
+msgid ""
+"Each ZFS pool will host only one filesystem. After install is finished, more "
+"filesystems can be created on this pool by using the <quote>zfs create</"
+"quote> command."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1151
 #, no-c-format
-msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the <quote>zpool add</quote> command, or into a mirrored pool by using the <quote>zpool attach</quote> command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system."
+msgid ""
+"Each ZFS pool will be composed of exactly one partition. After install is "
+"finished, a single-device ZFS pool can be converted into a multi-device pool "
+"by using the <quote>zpool add</quote> command, or into a mirrored pool by "
+"using the <quote>zpool attach</quote> command. However, you shouldn't do "
+"this on the pool that hosts root filesystem, as it would prevent GRUB from "
+"booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1159
 #, no-c-format
-msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the <quote>compression</quote> property via the <quote>zfs set</quote> command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system."
+msgid ""
+"Compression is not currently supported. After the install is finished, "
+"compression can be enabled by setting the <quote>compression</quote> "
+"property via the <quote>zfs set</quote> command. However, if a compression "
+"algorithm other than the default (lzjb) is used on the pool that hosts your "
+"root filesystem, this may prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1168
 #, no-c-format
-msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
+msgid ""
+"<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1170
 #, no-c-format
-msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
+msgid ""
+"Support for the Reiser file system is no longer available by default. When "
+"the installer is running at medium or low debconf priority it can be enabled "
+"by selecting the <classname>partman-reiserfs</classname> component. Only "
+"version 3 of the file system is supported."
 msgstr ""
 
 #. Tag: emphasis
@@ -1015,7 +1466,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1178
 #, no-c-format
-msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
+msgid ""
+"Used on some systems to read flash memory. It is not possible to create new "
+"jffs2 partitions."
 msgstr ""
 
 #. Tag: emphasis
@@ -1027,7 +1480,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1184
 #, no-c-format
-msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
+msgid ""
+"Existing partitions will be recognized and it is possible to assign mount "
+"points for them. It is not possible to create new qnx4 partitions."
 msgstr ""
 
 #. Tag: para
@@ -1045,7 +1500,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1193
 #, no-c-format
-msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
+msgid ""
+"Existing NTFS partitions can be resized and it is possible to assign mount "
+"points for them. It is not possible to create new NTFS partitions."
 msgstr ""
 
 #. Tag: title
@@ -1057,49 +1514,89 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1204
 #, no-c-format
-msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
+msgid ""
+"If you choose guided partitioning, you may have three options: to create "
+"partitions directly on the hard disk (classic method), or to create them "
+"using Logical Volume Management (LVM), or to create them using encrypted "
+"LVM<footnote> <para> The installer will encrypt the LVM volume group using a "
+"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> "
+"support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1219
 #, no-c-format
-msgid "The option to use (encrypted) LVM may not be available on all architectures."
+msgid ""
+"The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1224
 #, no-c-format
-msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
+msgid ""
+"When using LVM or encrypted LVM, the installer will create most partitions "
+"inside one big partition; the advantage of this method is that partitions "
+"inside this big partition can be resized relatively easily later. In the "
+"case of encrypted LVM the big partition will not be readable without knowing "
+"a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1233
 #, no-c-format
-msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
+msgid ""
+"When using encrypted LVM, the installer will also automatically erase the "
+"disk by writing random data to it. This further improves security (as it "
+"makes it impossible to tell which parts of the disk are in use and also "
+"makes sure that any traces of previous installations are erased), but may "
+"take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1242
 #, no-c-format
-msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
+msgid ""
+"If you choose guided partitioning using LVM or encrypted LVM, some changes "
+"in the partition table will need to be written to the selected disk while "
+"LVM is being set up. These changes effectively erase all data that is "
+"currently on the selected hard disk and you will not be able to undo them "
+"later. However, the installer will ask you to confirm these changes before "
+"they are written to disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1252
 #, no-c-format
-msgid "If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
+msgid ""
+"If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic "
+"or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked "
+"to select the disk you want to use. Check that all your disks are listed "
+"and, if you have several disks, make sure you select the correct one. The "
+"order they are listed in may differ from what you are used to. The size of "
+"the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1261
 #, no-c-format
-msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. <phrase arch=\"linux-any\"> If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. </phrase>"
+msgid ""
+"Any data on the disk you select will eventually be lost, but you will always "
+"be asked to confirm any changes before they are written to the disk. <phrase "
+"arch=\"linux-any\"> If you have selected the classic method of partitioning, "
+"you will be able to undo any changes right until the end; when using "
+"(encrypted) LVM this is not possible. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1271
 #, no-c-format
-msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
+msgid ""
+"Next, you will be able to choose from the schemes listed in the table below. "
+"All schemes have their pros and cons, some of which are discussed in <xref "
+"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in "
+"mind that guided partitioning needs a certain minimal amount of free space "
+"to operate with. If you don't give it at least about 1GB of space (depends "
+"on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
@@ -1171,54 +1668,79 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1307
 #, no-c-format
-msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
+msgid ""
+"<filename>/</filename>, <filename>/home</filename>, <filename>/usr</"
+"filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1316
 #, no-c-format
-msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
+msgid ""
+"If you choose guided partitioning using (encrypted) LVM, the installer will "
+"also create a separate <filename>/boot</filename> partition. The other "
+"partitions, including the swap partition, will be created inside the LVM "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1322
 #, no-c-format
-msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
+msgid ""
+"If you choose guided partitioning for your IA-64 system, there will be an "
+"additional partition, formatted as a FAT16 bootable filesystem, for the EFI "
+"boot loader. There is also an additional menu item in the formatting menu to "
+"manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1330
 #, no-c-format
-msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
+msgid ""
+"After selecting a scheme, the next screen will show your new partition "
+"table, including information on whether and how partitions will be formatted "
+"and where they will be mounted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1336
 #, no-c-format
 msgid ""
-      "The list of partitions might look like this: <informalexample><screen>\n"
-      "  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
-      "        #1 primary   16.4 MB  B f ext2       /boot\n"
-      "        #2 primary  551.0 MB      swap       swap\n"
-      "        #3 primary    5.8 GB      ntfs\n"
-      "           pri/log    8.2 MB      FREE SPACE\n"
-      "\n"
-      "  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
-      "        #1 primary   15.9 MB      ext3\n"
-      "        #2 primary  996.0 MB      fat16\n"
-      "        #3 primary    3.9 GB      xfs        /home\n"
-      "        #5 logical    6.0 GB    f ext3       /\n"
-      "        #6 logical    1.0 GB    f ext3       /var\n"
-      "        #7 logical  498.8 MB      ext3\n"
-      "        #8 logical  551.5 MB      swap       swap\n"
-      "        #9 logical   65.8 GB      ext2\n"
-      "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning."
+"The list of partitions might look like this: <informalexample><screen>\n"
+"  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
+"        #1 primary   16.4 MB  B f ext2       /boot\n"
+"        #2 primary  551.0 MB      swap       swap\n"
+"        #3 primary    5.8 GB      ntfs\n"
+"           pri/log    8.2 MB      FREE SPACE\n"
+"\n"
+"  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
+"        #1 primary   15.9 MB      ext3\n"
+"        #2 primary  996.0 MB      fat16\n"
+"        #3 primary    3.9 GB      xfs        /home\n"
+"        #5 logical    6.0 GB    f ext3       /\n"
+"        #6 logical    1.0 GB    f ext3       /var\n"
+"        #7 logical  498.8 MB      ext3\n"
+"        #8 logical  551.5 MB      swap       swap\n"
+"        #9 logical   65.8 GB      ext2\n"
+"</screen></informalexample> This example shows two IDE harddrives divided "
+"into several partitions; the first disk has some free space. Each partition "
+"line consists of the partition number, its type, size, optional flags, file "
+"system, and mountpoint (if any). Note: this particular setup cannot be "
+"created using guided partitioning but it does show possible variation that "
+"can be achieved using manual partitioning."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1349
 #, no-c-format
-msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
+msgid ""
+"This concludes the guided partitioning. If you are satisfied with the "
+"generated partition table, you can choose <guimenuitem>Finish partitioning "
+"and write changes to disk</guimenuitem> from the menu to implement the new "
+"partition table (as described at the end of this section). If you are not "
+"happy, you can choose to <guimenuitem>Undo changes to partitions</"
+"guimenuitem> and run guided partitioning again, or modify the proposed "
+"changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
@@ -1230,49 +1752,101 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1364
 #, no-c-format
-msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
+msgid ""
+"A similar screen to the one shown just above will be displayed if you choose "
+"manual partitioning except that your existing partition table will be shown "
+"and without the mount points. How to manually set up your partition table "
+"and the usage of partitions by your new &debian; system will be covered in "
+"the remainder of this section."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1372
 #, no-c-format
-msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
+msgid ""
+"If you select a pristine disk which has neither partitions nor free space on "
+"it, you will be asked if a new partition table should be created (this is "
+"needed so you can create new partitions). After this, a new line entitled "
+"<quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1380
 #, no-c-format
-msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file system,</phrase> or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap,<phrase arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
+msgid ""
+"If you select some free space, you will have the opportunity to create a new "
+"partition. You will have to answer a quick series of questions about its "
+"size, type (primary or logical), and location (beginning or end of the free "
+"space). After this, you will be presented with a detailed overview of your "
+"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which "
+"determines if the partition will have a file system on it, or be used for "
+"swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file "
+"system,</phrase> or not be used at all. Other settings include mountpoint, "
+"mount options, and bootable flag; which settings are shown depends on how "
+"the partition is to be used. If you don't like the preselected defaults, "
+"feel free to change them to your liking. E.g. by selecting the option "
+"<guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem "
+"for this partition, including options to use the partition for swap,<phrase "
+"arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. "
+"Another nice feature is the ability to copy data from an existing partition "
+"onto this one. When you are satisfied with your new partition, select "
+"<guimenuitem>Done setting up the partition</guimenuitem> and you will return "
+"to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1402
 #, no-c-format
-msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
+msgid ""
+"If you decide you want to change something about your partition, simply "
+"select the partition, which will bring you to the partition configuration "
+"menu. This is the same screen as is used when creating a new partition, so "
+"you can change the same settings. One thing that may not be very obvious at "
+"a first glance is that you can resize the partition by selecting the item "
+"displaying the size of the partition. Filesystems known to work are at least "
+"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1413
 #, no-c-format
-msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
+msgid ""
+"Be sure to create at least two partitions: one for the <emphasis>root</"
+"emphasis> filesystem (which must be mounted as <filename>/</filename>) and "
+"one for <emphasis>swap</emphasis>. If you forget to mount the root "
+"filesystem, <command>partman</command> won't let you continue until you "
+"correct this issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1421
 #, no-c-format
-msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
+msgid ""
+"If you forget to select and format an EFI boot partition, <command>partman</"
+"command> will detect this and will not let you continue until you allocate "
+"one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1427
 #, no-c-format
-msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
+msgid ""
+"Capabilities of <command>partman</command> can be extended with installer "
+"modules, but are dependent on your system's architecture. So if you can't "
+"see all promised goodies, check if you have loaded all required modules (e."
+"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or "
+"<filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1435
 #, no-c-format
-msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
+msgid ""
+"After you are satisfied with partitioning, select <guimenuitem>Finish "
+"partitioning and write changes to disk</guimenuitem> from the partitioning "
+"menu. You will be presented with a summary of changes made to the disks and "
+"asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
@@ -1284,19 +1858,82 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1464
 #, no-c-format
-msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
+msgid ""
+"If you have more than one harddrive<footnote><para> To be honest, you can "
+"construct an MD device even from partitions residing on single physical "
+"drive, but that won't give any benefits. </para></footnote> in your "
+"computer, you can use <command>mdcfg</command> to set up your drives for "
+"increased performance and/or better reliability of your data. The result is "
+"called <firstterm>Multidisk Device</firstterm> (or after its most famous "
+"variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1477
 #, no-c-format
-msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
+msgid ""
+"MD is basically a bunch of partitions located on different disks and "
+"combined together to form a <emphasis>logical</emphasis> device. This device "
+"can then be used like an ordinary partition (i.e. in <command>partman</"
+"command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1485
 #, no-c-format
-msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
+msgid ""
+"What benefits this brings depends on the type of MD device you are creating. "
+"Currently supported are: <variablelist> <varlistentry> <term>RAID0</"
+"term><listitem><para> Is mainly aimed at performance. RAID0 splits all "
+"incoming data into <firstterm>stripes</firstterm> and distributes them "
+"equally over each disk in the array. This can increase the speed of read/"
+"write operations, but when one of the disks fails, you will lose "
+"<emphasis>everything</emphasis> (part of the information is still on the "
+"healthy disk(s), the other part <emphasis>was</emphasis> on the failed "
+"disk). </para><para> The typical use for RAID0 is a partition for video "
+"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</"
+"term><listitem><para> Is suitable for setups where reliability is the first "
+"concern. It consists of several (usually two) equally-sized partitions where "
+"every partition contains exactly the same data. This essentially means three "
+"things. First, if one of your disks fails, you still have the data mirrored "
+"on the remaining disks. Second, you can use only a fraction of the available "
+"capacity (more precisely, it is the size of the smallest partition in the "
+"RAID). Third, file-reads are load-balanced among the disks, which can "
+"improve performance on a server, such as a file server, that tends to be "
+"loaded with more disk reads than writes. </para><para> Optionally you can "
+"have a spare disk in the array which will take the place of the failed disk "
+"in the case of failure. </para></listitem> </varlistentry> <varlistentry> "
+"<term>RAID5</term><listitem><para> Is a good compromise between speed, "
+"reliability and data redundancy. RAID5 splits all incoming data into stripes "
+"and distributes them equally on all but one disk (similar to RAID0). Unlike "
+"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which "
+"gets written on the remaining disk. The parity disk is not static (that "
+"would be called RAID4), but is changing periodically, so the parity "
+"information is distributed equally on all disks. When one of the disks "
+"fails, the missing part of information can be computed from remaining data "
+"and its parity. RAID5 must consist of at least three active partitions. "
+"Optionally you can have a spare disk in the array which will take the place "
+"of the failed disk in the case of failure. </para><para> As you can see, "
+"RAID5 has a similar degree of reliability to RAID1 while achieving less "
+"redundancy. On the other hand, it might be a bit slower on write operations "
+"than RAID0 due to computation of parity information. </para></listitem> </"
+"varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar "
+"to RAID5 except that it uses two parity devices instead of one. </"
+"para><para> A RAID6 array can survive up to two disk failures. </para></"
+"listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> "
+"RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It "
+"creates <replaceable>n</replaceable> copies of incoming data and distributes "
+"them across the partitions so that none of the copies of the same data are "
+"on the same device. The default value of <replaceable>n</replaceable> is 2, "
+"but it can be set to something else in expert mode. The number of partitions "
+"used must be at least <replaceable>n</replaceable>. RAID10 has different "
+"layouts for distributing the copies. The default is near copies. Near copies "
+"have all of the copies at about the same offset on all of the disks. Far "
+"copies have the copies at different offsets on the disks. Offset copies copy "
+"the stripe, not the individual copies. </para><para> RAID10 can be used to "
+"achieve reliability and redundancy without the drawback of having to "
+"calculate parity. </para></listitem> </varlistentry> </variablelist> To sum "
+"it up:"
 msgstr ""
 
 #. Tag: entry
@@ -1392,7 +2029,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1629
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus one)"
 msgstr ""
 
 #. Tag: entry
@@ -1410,7 +2049,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1640
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus two)"
 msgstr ""
 
 #. Tag: entry
@@ -1422,79 +2063,140 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1651
 #, no-c-format
-msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
+msgid ""
+"Total of all partitions divided by the number of chunk copies (defaults to "
+"two)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1658
 #, no-c-format
-msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
+msgid ""
+"If you want to know more about Software RAID, have a look at <ulink url="
+"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1663
 #, no-c-format
-msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
+msgid ""
+"To create an MD device, you need to have the desired partitions it should "
+"consist of marked for use in a RAID. (This is done in <command>partman</"
+"command> in the <guimenu>Partition settings</guimenu> menu where you should "
+"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume "
+"for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1672
 #, no-c-format
-msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
+msgid ""
+"Make sure that the system can be booted with the partitioning scheme you are "
+"planning. In general it will be necessary to create a separate file system "
+"for <filename>/boot</filename> when using RAID for the root (<filename>/</"
+"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including "
+"lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using "
+"for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</"
+"filename> can be an option."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1684
 #, no-c-format
-msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
+msgid ""
+"Support for MD is a relatively new addition to the installer. You may "
+"experience problems for some RAID levels and in combination with some "
+"bootloaders if you try to use MD for the root (<filename>/</filename>) file "
+"system. For experienced users, it may be possible to work around some of "
+"these problems by executing some configuration or installation steps "
+"manually from a shell."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1693
 #, no-c-format
-msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
+msgid ""
+"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> "
+"from the main <command>partman</command> menu. (The menu will only appear "
+"after you mark at least one partition for use as <guimenuitem>physical "
+"volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</"
+"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will "
+"be presented with a list of supported types of MD devices, from which you "
+"should choose one (e.g. RAID1). What follows depends on the type of MD you "
+"selected."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1706
 #, no-c-format
-msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
+msgid ""
+"RAID0 is simple &mdash; you will be issued with the list of available RAID "
+"partitions and your only task is to select the partitions which will form "
+"the MD."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1713
 #, no-c-format
-msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
+msgid ""
+"RAID1 is a bit more tricky. First, you will be asked to enter the number of "
+"active devices and the number of spare devices which will form the MD. Next, "
+"you need to select from the list of available RAID partitions those that "
+"will be active and then those that will be spare. The count of selected "
+"partitions must be equal to the number provided earlier. Don't worry. If you "
+"make a mistake and select a different number of partitions, &d-i; won't let "
+"you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1725
 #, no-c-format
-msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+msgid ""
+"RAID5 has a setup procedure similar to RAID1 with the exception that you "
+"need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1731
 #, no-c-format
-msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
+msgid ""
+"RAID6 also has a setup procedure similar to RAID1 except that at least "
+"<emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1737
 #, no-c-format
-msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
+msgid ""
+"RAID10 again has a setup procedure similar to RAID1 except in expert mode. "
+"In expert mode, &d-i; will ask you for the layout. The layout has two parts. "
+"The first part is the layout type. It is either <literal>n</literal> (for "
+"near copies), <literal>f</literal> (for far copies), or <literal>o</literal> "
+"(for offset copies). The second part is the number of copies to make of the "
+"data. There must be at least that many active devices so that all of the "
+"copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1751
 #, no-c-format
-msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
+msgid ""
+"It is perfectly possible to have several types of MD at once. For example, "
+"if you have three 200 GB hard drives dedicated to MD, each containing two "
+"100 GB partitions, you can combine the first partitions on all three disks "
+"into the RAID0 (fast 300 GB video editing partition) and use the other three "
+"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition "
+"for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1760
 #, no-c-format
-msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
+msgid ""
+"After you set up MD devices to your liking, you can <guimenuitem>Finish</"
+"guimenuitem> <command>mdcfg</command> to return back to the "
+"<command>partman</command> to create filesystems on your new MD devices and "
+"assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
@@ -1506,37 +2208,70 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1776
 #, no-c-format
-msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
+msgid ""
+"If you are working with computers at the level of system administrator or "
+"<quote>advanced</quote> user, you have surely seen the situation where some "
+"disk partition (usually the most important one) was short on space, while "
+"some other partition was grossly underused and you had to manage this "
+"situation by moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1784
 #, no-c-format
-msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
+msgid ""
+"To avoid the described situation you can use Logical Volume Manager (LVM). "
+"Simply said, with LVM you can combine your partitions (<firstterm>physical "
+"volumes</firstterm> in LVM lingo) to form a virtual disk (so called "
+"<firstterm>volume group</firstterm>), which can then be divided into virtual "
+"partitions (<firstterm>logical volumes</firstterm>). The point is that "
+"logical volumes (and of course underlying volume groups) can span across "
+"several physical disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1794
 #, no-c-format
-msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
+msgid ""
+"Now when you realize you need more space for your old 160GB <filename>/home</"
+"filename> partition, you can simply add a new 300GB disk to the computer, "
+"join it with your existing volume group and then resize the logical volume "
+"which holds your <filename>/home</filename> filesystem and voila &mdash; "
+"your users have some room again on their renewed 460GB partition. This "
+"example is of course a bit oversimplified. If you haven't read it yet, you "
+"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1805
 #, no-c-format
-msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
+msgid ""
+"LVM setup in &d-i; is quite simple and completely supported inside "
+"<command>partman</command>. First, you have to mark the partition(s) to be "
+"used as physical volumes for LVM. This is done in the <guimenu>Partition "
+"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:"
+"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1814
 #, no-c-format
-msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
+msgid ""
+"When you return to the main <command>partman</command> screen, you will see "
+"a new option <guimenuitem>Configure the Logical Volume Manager</"
+"guimenuitem>. When you select that, you will first be asked to confirm "
+"pending changes to the partition table (if any) and after that the LVM "
+"configuration menu will be shown. Above the menu a summary of the LVM "
+"configuration is shown. The menu itself is context sensitive and only shows "
+"valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1825
 #, no-c-format
-msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
+msgid ""
+"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device "
+"structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1578,19 +2313,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1847
 #, no-c-format
-msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
+msgid ""
+"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</"
+"command> screen"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1853
 #, no-c-format
-msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
+msgid ""
+"Use the options in that menu to first create a volume group and then create "
+"your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1858
 #, no-c-format
-msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
+msgid ""
+"After you return to the main <command>partman</command> screen, any created "
+"logical volumes will be displayed in the same way as ordinary partitions "
+"(and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
@@ -1602,37 +2344,76 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1873
 #, no-c-format
-msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
+msgid ""
+"&d-i; allows you to set up encrypted partitions. Every file you write to "
+"such a partition is immediately saved to the device in encrypted form. "
+"Access to the encrypted data is granted only after entering the "
+"<firstterm>passphrase</firstterm> used when the encrypted partition was "
+"originally created. This feature is useful to protect sensitive data in case "
+"your laptop or hard drive gets stolen. The thief might get physical access "
+"to the hard drive, but without knowing the right passphrase, the data on the "
+"hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1885
 #, no-c-format
-msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+msgid ""
+"The two most important partitions to encrypt are: the home partition, where "
+"your private data resides, and the swap partition, where sensitive data "
+"might be stored temporarily during operation. Of course, nothing prevents "
+"you from encrypting any other partitions that might be of interest. For "
+"example <filename>/var</filename> where database servers, mail servers or "
+"print servers store their data, or <filename>/tmp</filename> which is used "
+"by various programs to store potentially interesting temporary files. Some "
+"people may even want to encrypt their whole system. The only exception is "
+"the <filename>/boot</filename> partition which must remain unencrypted, "
+"because currently there is no way to load the kernel from an encrypted "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1900
 #, no-c-format
-msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
+msgid ""
+"Please note that the performance of encrypted partitions will be less than "
+"that of unencrypted ones because the data needs to be decrypted or encrypted "
+"for every read or write. The performance impact depends on your CPU speed, "
+"chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1907
 #, no-c-format
-msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
+msgid ""
+"To use encryption, you have to create a new partition by selecting some free "
+"space in the main partitioning menu. Another option is to choose an existing "
+"partition (e.g. a regular partition, an LVM logical volume or a RAID "
+"volume). In the <guimenu>Partition settings</guimenu> menu, you need to "
+"select <guimenuitem>physical volume for encryption</guimenuitem> at the "
+"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will "
+"then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1918
 #, no-c-format
-msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+msgid ""
+"&d-i; supports several encryption methods. The default method is "
+"<firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to "
+"host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> "
+"(older, maintained separately from the Linux kernel tree). Unless you have "
+"compelling reasons to do otherwise, it is recommended to use the default."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1930
 #, no-c-format
-msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid ""
+"First, let's have a look at the options available when you select "
+"<userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As "
+"always: when in doubt, use the defaults, because they have been carefully "
+"chosen with security in mind."
 msgstr ""
 
 #. Tag: term
@@ -1644,7 +2425,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1942
 #, no-c-format
-msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
+msgid ""
+"This option lets you select the encryption algorithm (<firstterm>cipher</"
+"firstterm>) which will be used to encrypt the data on the partition. &d-i; "
+"currently supports the following block ciphers: <firstterm>aes</firstterm>, "
+"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and "
+"<firstterm>twofish</firstterm>. It is beyond the scope of this document to "
+"discuss the qualities of these different algorithms, however, it might help "
+"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by "
+"the American National Institute of Standards and Technology as the standard "
+"encryption algorithm for protecting sensitive information in the 21st "
+"century."
 msgstr ""
 
 #. Tag: term
@@ -1656,7 +2447,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1962
 #, no-c-format
-msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
+msgid ""
+"Here you can specify the length of the encryption key. With a larger key "
+"size, the strength of the encryption is generally improved. On the other "
+"hand, increasing the length of the key usually has a negative impact on "
+"performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
@@ -1668,13 +2463,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1976
 #, no-c-format
-msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
+msgid ""
+"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</"
+"firstterm> algorithm is used in cryptography to ensure that applying the "
+"cipher on the same <firstterm>clear text</firstterm> data with the same key "
+"always produces a unique <firstterm>cipher text</firstterm>. The idea is to "
+"prevent the attacker from deducing information from repeated patterns in the "
+"encrypted data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1986
 #, no-c-format
-msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
+msgid ""
+"From the provided alternatives, the default <userinput>cbc-essiv:sha256</"
+"userinput> is currently the least vulnerable to known attacks. Use the other "
+"alternatives only when you need to ensure compatibility with some previously "
+"installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
@@ -1698,7 +2503,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2007
 #, no-c-format
-msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
+msgid ""
+"The encryption key will be computed<footnote> <para> Using a passphrase as "
+"the key currently means that the partition will be set up using <ulink url="
+"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase "
+"which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
@@ -1710,13 +2519,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2023
 #, no-c-format
-msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
+msgid ""
+"A new encryption key will be generated from random data each time you try to "
+"bring up the encrypted partition. In other words: on every shutdown the "
+"content of the partition will be lost as the key is deleted from memory. (Of "
+"course, you could try to guess the key with a brute force attack, but unless "
+"there is an unknown weakness in the cipher algorithm, it is not achievable "
+"in our lifetime.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2032
 #, no-c-format
-msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
+msgid ""
+"Random keys are useful for swap partitions because you do not need to bother "
+"yourself with remembering the passphrase or wiping sensitive information "
+"from the swap partition before shutting down your computer. However, it also "
+"means that you will <emphasis>not</emphasis> be able to use the "
+"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels "
+"as it will be impossible (during a subsequent boot) to recover the suspended "
+"data written to the swap partition."
 msgstr ""
 
 #. Tag: term
@@ -1728,13 +2550,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2053
 #, no-c-format
-msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
+msgid ""
+"Determines whether the content of this partition should be overwritten with "
+"random data before setting up the encryption. This is recommended because it "
+"might otherwise be possible for an attacker to discern which parts of the "
+"partition are in use and which are not. In addition, this will make it "
+"harder to recover any leftover data from previous "
+"installations<footnote><para> It is believed that the guys from three-letter "
+"agencies can restore the data even after several rewrites of the "
+"magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2073
 #, no-c-format
-msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
+msgid ""
+"If you select <menuchoice> <guimenu>Encryption method:</guimenu> "
+"<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu "
+"changes to provide the following options:"
 msgstr ""
 
 #. Tag: term
@@ -1746,7 +2579,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2084
 #, no-c-format
-msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
+msgid ""
+"For loop-AES, unlike dm-crypt, the options for cipher and key size are "
+"combined, so you can select both at the same time. Please see the above "
+"sections on ciphers and key sizes for further information."
 msgstr ""
 
 #. Tag: term
@@ -1770,7 +2606,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2103
 #, no-c-format
-msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
+msgid ""
+"The encryption key will be generated from random data during the "
+"installation. Moreover this key will be encrypted with <application>GnuPG</"
+"application>, so to use it, you will need to enter the proper passphrase "
+"(you will be asked to provide one later in the process)."
 msgstr ""
 
 #. Tag: para
@@ -1788,50 +2628,93 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2139
 #, no-c-format
-msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
+msgid ""
+"After you have selected the desired parameters for your encrypted "
+"partitions, return back to the main partitioning menu. There should now be a "
+"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After "
+"you select it, you will be asked to confirm the deletion of data on "
+"partitions marked to be erased and possibly other actions such as writing a "
+"new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2149
 #, no-c-format
-msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
+msgid ""
+"Next you will be asked to enter a passphrase for partitions configured to "
+"use one. Good passphrases should be longer than 8 characters, should be a "
+"mixture of letters, numbers and other characters and should not contain "
+"common dictionary words or information easily associable with you (such as "
+"birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2158
 #, no-c-format
-msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
+msgid ""
+"Before you input any passphrases, you should have made sure that your "
+"keyboard is configured correctly and generates the expected characters. If "
+"you are unsure, you can switch to the second virtual console and type some "
+"text at the prompt. This ensures that you won't be surprised later, e.g. by "
+"trying to input a passphrase using a qwerty keyboard layout when you used an "
+"azerty layout during the installation. This situation can have several "
+"causes. Maybe you switched to another keyboard layout during the "
+"installation, or the selected keyboard layout might not have been set up yet "
+"when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2171
 #, no-c-format
-msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
+msgid ""
+"If you selected to use methods other than a passphrase to create encryption "
+"keys, they will be generated now. Because the kernel may not have gathered a "
+"sufficient amount of entropy at this early stage of the installation, the "
+"process may take a long time. You can help speed up the process by "
+"generating entropy: e.g. by pressing random keys, or by switching to the "
+"shell on the second virtual console and generating some network and disk "
+"traffic (downloading some files, feeding big files into <filename>/dev/null</"
+"filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2187
 #, no-c-format
 msgid ""
-      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
-      "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
-      "     #1 115.1 GB  F ext3\n"
-      "\n"
-      "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-      "     #1 515.2 MB  F ext3\n"
-      "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you."
+"After returning to the main partitioning menu, you will see all encrypted "
+"volumes as additional partitions which can be configured in the same way as "
+"ordinary partitions. The following example shows two different volumes. The "
+"first one is encrypted via dm-crypt, the second one via loop-AES. "
+"<informalexample><screen>\n"
+"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux "
+"device-mapper\n"
+"     #1 115.1 GB  F ext3\n"
+"\n"
+"Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
+"     #1 515.2 MB  F ext3\n"
+"</screen></informalexample> Now is the time to assign mount points to the "
+"volumes and optionally change the file system types if the defaults do not "
+"suit you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2200
 #, no-c-format
-msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+msgid ""
+"Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</"
+"replaceable> and <replaceable>loop0</replaceable> in this case) and the "
+"mount points you assigned to each encrypted volume. You will need this "
+"information later when booting the new system. The differences between the "
+"ordinary boot process and the boot process with encryption involved will be "
+"covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2210
 #, no-c-format
-msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
+msgid ""
+"Once you are satisfied with the partitioning scheme, continue with the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -1843,37 +2726,63 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2222
 #, no-c-format
-msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
+msgid ""
+"Although this stage is the least problematic, it consumes a significant "
+"fraction of the install because it downloads, verifies and unpacks the whole "
+"base system. If you have a slow computer or network connection, this could "
+"take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2235
 #, no-c-format
-msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"During installation of the base system, package unpacking and setup messages "
+"are redirected to <userinput>tty4</userinput>. You can access this terminal "
+"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></"
+"keycombo>; get back to the main installer process with "
+"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2244
 #, no-c-format
-msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
+msgid ""
+"The unpack/setup messages generated during this phase are also saved in "
+"<filename>/var/log/syslog</filename>. You can check them there if the "
+"installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2250
 #, no-c-format
-msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
+msgid ""
+"As part of the installation, a &arch-kernel; kernel will be installed. At "
+"the default priority, the installer will choose one for you that best "
+"matches your hardware. In lower priority modes, you will be able to choose "
+"from a list of available kernels."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2257
 #, no-c-format
-msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
+msgid ""
+"When packages are installed using the package management system, it will by "
+"default also install packages that are recommended by those packages. "
+"Recommended packages are not strictly required for the core functionality of "
+"the selected software, but they do enhance that software and should, in the "
+"view of the package maintainers, normally be installed together with that "
+"software."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2267
 #, no-c-format
-msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
+msgid ""
+"For technical reasons packages installed during the installation of the base "
+"system are installed without their <quote>Recommends</quote>. The rule "
+"described above only takes effect after this point in the installation "
+"process."
 msgstr ""
 
 #. Tag: title
@@ -1885,7 +2794,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2280
 #, no-c-format
-msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
+msgid ""
+"At this point you have a usable but limited system. Most users will want to "
+"install additional software on the system to tune it to their needs, and the "
+"installer allows you do so. This step can take even longer than installing "
+"the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
@@ -1897,25 +2810,55 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2297
 #, no-c-format
-msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
+msgid ""
+"One of the tools used to install packages on a &debian-gnu; system is a "
+"program called <command>apt-get</command>, from the <classname>apt</"
+"classname> package<footnote> <para> Note that the program which actually "
+"installs the packages is called <command>dpkg</command>. However, this "
+"program is more of a low-level tool. <command>apt-get</command> is a higher-"
+"level tool, which will invoke <command>dpkg</command> as appropriate. It "
+"knows how to retrieve packages from your CD, the network, or wherever. It is "
+"also able to automatically install other packages which are required to make "
+"the package you're trying to install work correctly. </para> </footnote>. "
+"Other front-ends for package management, like <command>aptitude</command> "
+"and <command>synaptic</command>, are also in use. These front-ends are "
+"recommended for new users, since they integrate some additional features "
+"(package searching and status checks) in a nice user interface. In fact, "
+"<command>aptitude</command> is now the recommended utility for package "
+"management."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2321
 #, no-c-format
-msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
+msgid ""
+"<command>apt</command> must be configured so that it knows from where to "
+"retrieve packages. The results of this configuration are written to the file "
+"<filename>/etc/apt/sources.list</filename>. You can examine and edit this "
+"file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2328
 #, no-c-format
-msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
+msgid ""
+"If you are installing at default priority, the installer will largely take "
+"care of the configuration automatically, based on the installation method "
+"you are using and possibly using choices made earlier in the installation. "
+"In most cases the installer will automatically add a security mirror and, if "
+"you are installing the stable distribution, a mirror for the "
+"<quote>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2337
 #, no-c-format
-msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
+msgid ""
+"If you are installing at a lower priority (e.g. in expert mode), you will be "
+"able to make more decisions yourself. You can choose whether or not to use "
+"the security and/or volatile update services, and you can choose to add "
+"packages from the <quote>contrib</quote> and <quote>non-free</quote> "
+"sections of the archive."
 msgstr ""
 
 #. Tag: title
@@ -1927,37 +2870,64 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2350
 #, no-c-format
-msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
+msgid ""
+"If you are installing from a CD or a DVD that is part of a larger set, the "
+"installer will ask if you want to scan additional CDs or DVDs. If you have "
+"additional CDs or DVDs available, you probably want to do this so the "
+"installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2357
 #, no-c-format
-msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
+msgid ""
+"If you do not have any additional CDs or DVDs, that is no problem: using "
+"them is not required. If you also do not use a network mirror (as explained "
+"in the next section), it can mean that not all packages belonging to the "
+"tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2365
 #, no-c-format
-msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
+msgid ""
+"Packages are included on CDs (and DVDs) in the order of their popularity. "
+"This means that for most uses only the first CDs in a set are needed and "
+"that only very few people actually use any of the packages included on the "
+"last CDs in a set."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2372
 #, no-c-format
-msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
+msgid ""
+"It also means that buying or downloading and burning a full CD set is just a "
+"waste of money as you'll never use most of them. In most cases you are "
+"better off getting only the first 3 to 8 CDs and installing any additional "
+"packages you may need from the Internet by using a mirror. The same goes for "
+"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2381
 #, no-c-format
-msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
+msgid ""
+"A good rule of thumb is that for a regular desktop installation (using the "
+"GNOME desktop environment) only the first three CDs are needed. For the "
+"alternative desktop environments (KDE or Xfce), additional CDs are needed. "
+"The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2389
 #, no-c-format
-msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
+msgid ""
+"If you do scan multiple CDs or DVDs, the installer will prompt you to "
+"exchange them when it needs packages from another CD/DVD than the one "
+"currently in the drive. Note that only CDs or DVDs that belong to the same "
+"set should be scanned. The order in which they are scanned does not really "
+"matter, but scanning them in ascending order will reduce the chance of "
+"mistakes."
 msgstr ""
 
 #. Tag: title
@@ -1969,37 +2939,67 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2404
 #, no-c-format
-msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
+msgid ""
+"One question that will be asked during most installs is whether or not to "
+"use a network mirror as a source for packages. In most cases the default "
+"answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2410
 #, no-c-format
-msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
+msgid ""
+"If you are <emphasis>not</emphasis> installing from a full CD or DVD or "
+"using a full CD/DVD image, you really should use a network mirror as "
+"otherwise you will end up with only a very minimal system. However, if you "
+"have a limited Internet connection it is best <emphasis>not</emphasis> to "
+"select the <literal>desktop</literal> task in the next step of the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2419
 #, no-c-format
-msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
+msgid ""
+"If you are installing from a single full CD or using a full CD image, using "
+"a network mirror is not required, but is still strongly recommended because "
+"a single CD contains only a fairly limited number of packages. If you have a "
+"limited Internet connection it may still be best to <emphasis>not</emphasis> "
+"select a network mirror here, but to finish the installation using only "
+"what's available on the CD and selectively install additional packages after "
+"the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2430
 #, no-c-format
-msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
+msgid ""
+"If you are installing from a DVD or using a DVD image, any packages needed "
+"during the installation should be present on the first DVD. The same is true "
+"if you have scanned multiple CDs as explained in the previous section. Use "
+"of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2437
 #, no-c-format
-msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
+msgid ""
+"One advantage of adding a network mirror is that updates that have occurred "
+"since the CD/DVD set was created and have been included in a point release, "
+"will become available for installation, thus extending the life of your CD/"
+"DVD set without compromising the security or stability of the installed "
+"system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2444
 #, no-c-format
-msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
+msgid ""
+"In summary: selecting a network mirror is generally a good idea, except if "
+"you do not have a good Internet connection. If the current version of a "
+"package is available from CD/DVD, the installer will always use that. The "
+"amount of data that will be downloaded if you do select a mirror thus "
+"depends on"
 msgstr ""
 
 #. Tag: para
@@ -2017,19 +3017,27 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2463
 #, no-c-format
-msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
+msgid ""
+"which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2468
 #, no-c-format
-msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
+msgid ""
+"whether any updated versions of packages included on the CDs or DVDs are "
+"available from a mirror (either a regular package mirror, or a mirror for "
+"security or volatile updates)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2477
 #, no-c-format
-msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
+msgid ""
+"Note that the last point means that, even if you choose not to use a network "
+"mirror, some packages may still be downloaded from the Internet if there is "
+"a security or volatile update available for them and those services have "
+"been configured."
 msgstr ""
 
 #. Tag: title
@@ -2041,19 +3049,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2489
 #, no-c-format
-msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine."
+msgid ""
+"If you have selected to use a network mirror during the installation "
+"(optional for CD/DVD installs, required for netboot images), you will be "
+"presented with a list of geographically nearby (and therefore hopefully "
+"fast) network mirrors, based upon your country selection earlier in the "
+"installation process. Choosing the offered default is usually fine."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2497
 #, no-c-format
-msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one."
+msgid ""
+"If your computer is on an IPv6-only network (which is probably not the case "
+"for the vast majority of users), using the default mirror for your country "
+"might not work. All the mirrors in the list are reachable via IPv4, but only "
+"some of them can be used via IPv6. As connectivity of individual mirrors can "
+"change over time, this information is not available in the installer. If "
+"there is no IPv6 connectivity for the default mirror for your country, you "
+"can either try some of the other mirrors offered to you or choose the "
+"<quote>enter information manually</quote> option. You can then specify "
+"<quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for "
+"a mirror available via IPv6, although it will probably not be the fastest "
+"possible one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2511
 #, no-c-format
-msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
+msgid ""
+"Another option when choosing to specify the mirror manually is to use "
+"<quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</"
+"quote> is not a physical mirror but a mirror redirection service, i.e. it "
+"automatically refers your system to a real mirror near you in terms of "
+"network topology. It takes into account by which protocol you connect to it, "
+"i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
 msgstr ""
 
 #. Tag: title
@@ -2065,85 +3095,165 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2532
 #, no-c-format
-msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
+msgid ""
+"During the installation process, you are given the opportunity to select "
+"additional software to install. Rather than picking individual software "
+"packages from the &num-of-distrib-pkgs; available packages, this stage of "
+"the installation process focuses on selecting and installing predefined "
+"collections of software to quickly set up your computer to perform various "
+"tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2541
 #, no-c-format
-msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
+msgid ""
+"So, you have the ability to choose <emphasis>tasks</emphasis> first, and "
+"then add on more individual packages later. These tasks loosely represent a "
+"number of different jobs or things you want to do with your computer, such "
+"as <quote>Desktop environment</quote>, <quote>Web server</quote>, or "
+"<quote>Print server</quote><footnote> <para> You should know that to present "
+"this list, the installer is merely invoking the <command>tasksel</command> "
+"program. It can be run at any time after installation to install more "
+"packages (or remove them), or you can use a more fine-grained tool such as "
+"<command>aptitude</command>. If you are looking for a specific single "
+"package, after installation is complete, simply run <userinput>aptitude "
+"install <replaceable>package</replaceable></userinput>, where "
+"<replaceable>package</replaceable> is the name of the package you are "
+"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> "
+"lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2568
 #, no-c-format
-msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
+msgid ""
+"Some tasks may be pre-selected based on the characteristics of the computer "
+"you are installing. If you disagree with these selections you can deselect "
+"them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2575
 #, no-c-format
-msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+msgid ""
+"In the standard user interface of the installer, you can use the space bar "
+"to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2581
 #, no-c-format
-msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
+msgid ""
+"Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop "
+"environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2586
 #, no-c-format
-msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using <literal>desktop=xfce</literal> or <literal>desktop=lxde</literal>."
+msgid ""
+"It is not possible to interactively select a different desktop during the "
+"installation. However, it <emphasis>is</emphasis> possible to get &d-i; to "
+"install a KDE desktop environment instead of GNOME by using preseeding (see "
+"<xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter "
+"<literal>desktop=kde</literal> at the boot prompt when starting the "
+"installer. Alternatively the more lightweight Xfce and LXDE desktop "
+"environments can be selected by using <literal>desktop=xfce</literal> or "
+"<literal>desktop=lxde</literal>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2597
 #, no-c-format
-msgid "Some CD images (netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>."
+msgid ""
+"Some CD images (netinst and DVD) also allow selection of the desired desktop "
+"environment from the graphical boot menu. Select the <quote>Advanced "
+"options</quote> option in the main menu and look for <quote>Alternative "
+"desktop environments</quote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2604
 #, no-c-format
-msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method."
+msgid ""
+"Note that this will only work if the packages needed for the desired desktop "
+"environment are actually available. If you are installing using a single "
+"full CD image, they will need to be downloaded from a mirror as most needed "
+"packages are only included on later CDs; installing KDE, Xfce or LXDE this "
+"way should work fine if you are using a DVD image or any other installation "
+"method."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2614
 #, no-c-format
-msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
+msgid ""
+"The various server tasks will install software roughly as follows. DNS "
+"server: <classname>bind9</classname>; File server: <classname>samba</"
+"classname>, <classname>nfs</classname>; Mail server: <classname>exim4</"
+"classname>, <classname>spamassassin</classname>, <classname>uw-imap</"
+"classname>; Print server: <classname>cups</classname>; SQL database: "
+"<classname>postgresql</classname>; Web server: <classname>apache2</"
+"classname>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2625
 #, no-c-format
-msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system."
+msgid ""
+"The <quote>Standard system</quote> task will install any package that has a "
+"priority <quote>standard</quote>. This includes a lot of common utilities "
+"that are normally available on any Linux or Unix system. You should leave "
+"this task selected unless you know what you are doing and want a really "
+"minimal system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2633
 #, no-c-format
-msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)."
+msgid ""
+"If during language selection a default locale other than the <quote>C</"
+"quote> locale was selected, <command>tasksel</command> will check if any "
+"localization tasks are defined for that locale and will automatically try to "
+"install relevant localization packages. This includes for example packages "
+"containing word lists or special fonts for your language. If a desktop "
+"environment was selected, it will also install appropriate localization "
+"packages for that (if available)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2643
 #, no-c-format
-msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
+msgid ""
+"Once you've selected your tasks, select &BTN-CONT;. At this point, "
+"<command>aptitude</command> will install the packages that are part of the "
+"selected tasks. If a particular program needs more information from the "
+"user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2650
 #, no-c-format
-msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
+msgid ""
+"You should be aware that especially the Desktop task is very large. "
+"Especially when installing from a normal CD-ROM in combination with a mirror "
+"for packages not on the CD-ROM, the installer may want to retrieve a lot of "
+"packages over the network. If you have a relatively slow Internet "
+"connection, this can take a long time. There is no option to cancel the "
+"installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2659
 #, no-c-format
-msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
+msgid ""
+"Even when packages are included on the CD-ROM, the installer may still "
+"retrieve them from the mirror if the version available on the mirror is more "
+"recent than the one included on the CD-ROM. If you are installing the stable "
+"distribution, this can happen after a point release (an update of the "
+"original stable release); if you are installing the testing distribution "
+"this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: title
@@ -2155,7 +3265,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2676
 #, no-c-format
-msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
+msgid ""
+"If you are installing a diskless workstation, obviously, booting off the "
+"local disk isn't a meaningful option, and this step will be skipped. <phrase "
+"arch=\"sparc\">You may wish to set OpenBoot to boot from the network by "
+"default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -2167,13 +3281,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2693
 #, no-c-format
-msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;."
+msgid ""
+"Before a boot loader is installed, the installer will attempt to probe for "
+"other operating systems which are installed on the machine. If it finds a "
+"supported operating system, you will be informed of this during the boot "
+"loader installation step, and the computer will be configured to boot this "
+"other operating system in addition to &debian;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2701
 #, no-c-format
-msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
+msgid ""
+"Note that multiple operating systems booting on a single machine is still "
+"something of a black art. The automatic support for detecting and setting up "
+"boot loaders to boot other operating systems varies by architecture and even "
+"by subarchitecture. If it does not work you should consult your boot "
+"manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
@@ -2185,7 +3309,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2720
 #, no-c-format
-msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
+msgid ""
+"The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is "
+"similar in configuration and usage to <command>LILO</command>, with a few "
+"exceptions. First of all, <command>PALO</command> allows you to boot any "
+"kernel image on your boot partition. This is because <command>PALO</command> "
+"can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
@@ -2203,19 +3332,28 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2743
 #, no-c-format
-msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
+msgid ""
+"The main &architecture; boot loader is called <quote>grub</quote>. Grub is a "
+"flexible and robust boot loader and a good default choice for new users and "
+"old hands alike."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2749
 #, no-c-format
-msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
+msgid ""
+"By default, grub will be installed into the Master Boot Record (MBR), where "
+"it will take over complete control of the boot process. If you prefer, you "
+"can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2755
 #, no-c-format
-msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
+msgid ""
+"If you do not want to install grub, use the &BTN-GOBACK; button to get to "
+"the main menu, and from there select whatever bootloader you would like to "
+"use."
 msgstr ""
 
 #. Tag: title
@@ -2227,19 +3365,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2770
 #, no-c-format
-msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
+msgid ""
+"The second &architecture; boot loader is called <quote>LILO</quote>. It is "
+"an old complex program which offers lots of functionality, including DOS, "
+"Windows, and OS/2 boot management. Please carefully read the instructions in "
+"the directory <filename>/usr/share/doc/lilo/</filename> if you have special "
+"needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2780
 #, no-c-format
-msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
+msgid ""
+"Currently the LILO installation will only create menu entries for other "
+"operating systems if these can be <firstterm>chainloaded</firstterm>. This "
+"means you may have to manually add a menu entry for operating systems like "
+"GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2788
 #, no-c-format
-msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
+msgid ""
+"&d-i; offers you three choices on where to install the <command>LILO</"
+"command> boot loader:"
 msgstr ""
 
 #. Tag: term
@@ -2251,7 +3400,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2795
 #, no-c-format
-msgid "This way the <command>LILO</command> will take complete control of the boot process."
+msgid ""
+"This way the <command>LILO</command> will take complete control of the boot "
+"process."
 msgstr ""
 
 #. Tag: term
@@ -2263,7 +3414,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2802
 #, no-c-format
-msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader."
+msgid ""
+"Choose this if you want to use another boot manager. <command>LILO</command> "
+"will install itself at the beginning of the new &debian; partition and it "
+"will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
@@ -2275,13 +3429,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2811
 #, no-c-format
-msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+msgid ""
+"Useful for advanced users who want to install <command>LILO</command> "
+"somewhere else. In this case you will be asked for desired location. You can "
+"use traditional device names such as <filename>/dev/hda</filename> or "
+"<filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2821
 #, no-c-format
-msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into &debian;!"
+msgid ""
+"If you can no longer boot into Windows 9x (or DOS) after this step, you'll "
+"need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /"
+"mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; "
+"however, this means that you'll need to use some other way to get back into "
+"&debian;!"
 msgstr ""
 
 #. Tag: title
@@ -2293,13 +3456,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2839
 #, no-c-format
-msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
+msgid ""
+"The &architecture; boot loader is called <quote>elilo</quote>. It is modeled "
+"on the <quote>lilo</quote> boot loader for the x86 architecture and uses a "
+"similar configuration file. However, instead of writing an MBR or partition "
+"boot record to the disk, it copies the necessary files to a separate FAT "
+"formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</"
+"guimenuitem> menu in the firmware to point to the files in the EFI "
+"partition. The <command>elilo</command> boot loader is really in two parts. "
+"The <filename>/usr/sbin/elilo</filename> command manages the partition and "
+"copies files into it. The <filename>elilo.efi</filename> program is copied "
+"into the EFI partition and then run by the <quote>EFI Boot Manager</quote> "
+"to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2855
 #, no-c-format
-msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
+msgid ""
+"The <quote>elilo</quote> configuration and installation is done as the last "
+"step of installing the packages of the base installation. &d-i; will present "
+"you with a list of potential disk partitions that it has found suitable for "
+"an EFI partition. Select the partition you set up earlier in the "
+"installation, typically a partition on the same disk that contains your "
+"<emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2311,7 +3491,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2869
 #, no-c-format
-msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
+msgid ""
+"The criterion for selecting a partition is that it must be a FAT format "
+"filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show "
+"multiple choices depending on what it finds from scanning all of the disks "
+"of the system including EFI partitions of other system disks and EFI "
+"diagnostic partitions. Remember, <command>elilo</command> may format the "
+"partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
@@ -2323,7 +3509,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2886
 #, no-c-format
-msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
+msgid ""
+"The EFI partition is a FAT filesystem format partition on one of the hard "
+"disks of the system, usually the same disk that contains the <emphasis>root</"
+"emphasis> filesystem. It is normally not mounted on a running system as it "
+"is only needed by the <quote>EFI Boot Manager</quote> to load the system and "
+"the installer part of the <command>elilo</command> writes to the filesystem "
+"directly. The <command>/usr/sbin/elilo</command> utility writes the "
+"following files into the <filename>efi/debian</filename> directory of the "
+"EFI partition during the installation. Note that the <quote>EFI Boot "
+"Manager</quote> would find these files using the path "
+"<filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may "
+"be other files in this filesystem as well over time as the system is updated "
+"or re-configured."
 msgstr ""
 
 #. Tag: filename
@@ -2335,7 +3533,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2909
 #, no-c-format
-msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
+msgid ""
+"This is the configuration file read by the boot loader when it starts. It is "
+"a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-"
+"written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
@@ -2347,7 +3548,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2919
 #, no-c-format
-msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
+msgid ""
+"This is the boot loader program that the <quote>EFI Boot Manager</quote> "
+"runs to boot the system. It is the program behind the <guimenuitem>&debian; "
+"GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> "
+"command menu."
 msgstr ""
 
 #. Tag: filename
@@ -2359,7 +3564,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2930
 #, no-c-format
-msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
+msgid ""
+"This is the initial root filesystem used to boot the kernel. It is a copy of "
+"the file referenced in the <filename>/etc/elilo.conf</filename>. In a "
+"standard &debian; installation it would be the file in <filename>/boot</"
+"filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
@@ -2371,7 +3580,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2943
 #, no-c-format
-msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
+msgid ""
+"This is a small text file warning you that the contents of the directory are "
+"managed by the <command>elilo</command> and that any local changes would be "
+"lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
@@ -2383,7 +3595,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2954
 #, no-c-format
-msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
+msgid ""
+"This is the compressed kernel itself. It is a copy of the file referenced in "
+"the <filename>/etc/elilo.conf</filename>. In a standard &debian; "
+"installation it would be the file in <filename>/boot</filename> pointed to "
+"by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
@@ -2396,13 +3612,25 @@ msgstr ""
 #: using-d-i.xml:2975
 #, no-c-format
 msgid ""
-      "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
-      "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
-      "<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n"
-      "<userinput> setenv OSLoader arcboot</userinput>\n"
-      "<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n"
-      "<userinput> setenv AutoLoad yes</userinput>\n"
-      "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
+"The boot loader on SGI machines is <command>arcboot</command>. It has to be "
+"installed on the same hard disk as the kernel (this is done automatically by "
+"the installer). Arcboot supports different configurations which are set up "
+"in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique "
+"name, the default setup as created by the installer is <quote>linux</quote>. "
+"After arcboot has been installed, the system can be booted from hard disk by "
+"setting some firmware environment variables entering "
+"<informalexample><screen>\n"
+"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
+"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</"
+"replaceable>)</userinput>\n"
+"<userinput> setenv OSLoader arcboot</userinput>\n"
+"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></"
+"userinput>\n"
+"<userinput> setenv AutoLoad yes</userinput>\n"
+"</screen></informalexample> on the firmware prompt, and then typing "
+"<command>boot</command>."
 msgstr ""
 
 #. Tag: replaceable
@@ -2414,7 +3642,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2995
 #, no-c-format
-msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
+msgid ""
+"is the SCSI bus to be booted from, this is <userinput>0</userinput> for the "
+"onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
@@ -2426,7 +3656,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3004
 #, no-c-format
-msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
+msgid ""
+"is the SCSI ID of the hard disk on which <command>arcboot</command> is "
+"installed"
 msgstr ""
 
 #. Tag: replaceable
@@ -2438,7 +3670,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3013
 #, no-c-format
-msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
+msgid ""
+"is the number of the partition on which <filename>/etc/arcboot.conf</"
+"filename> resides"
 msgstr ""
 
 #. Tag: replaceable
@@ -2450,7 +3684,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3022
 #, no-c-format
-msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
+msgid ""
+"is the name of the configuration entry in <filename>/etc/arcboot.conf</"
+"filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
@@ -2462,7 +3698,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3044
 #, no-c-format
-msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;."
+msgid ""
+"Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their "
+"boot loader. The installer will set up <command>yaboot</command> "
+"automatically, so all you need is a small 820k partition named "
+"<quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> "
+"created back in the partitioning component. If this step completes "
+"successfully then your disk should now be bootable and OpenFirmware will be "
+"set to boot &debian-gnu;."
 msgstr ""
 
 #. Tag: title
@@ -2474,7 +3717,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3063
 #, no-c-format
-msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
+msgid ""
+"The boot loader for OldWorld Power Macintosh machines is <command>quik</"
+"command>. You can also use it on CHRP. The installer will attempt to set up "
+"<command>quik</command> automatically. The setup has been known to work on "
+"7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
@@ -2486,7 +3733,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3080
 #, no-c-format
-msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
+msgid ""
+"The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. Please take a look at <quote>LINUX for &arch-title; "
+"Device Drivers and Installation Commands</quote> from IBM's developerWorks "
+"web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
@@ -2498,7 +3750,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3099
 #, no-c-format
-msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
+msgid ""
+"The standard &architecture; boot loader is called <quote>silo</quote>. It is "
+"documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. First of all, <command>SILO</command> allows you to "
+"boot any kernel image on your drive, even if it is not listed in <filename>/"
+"etc/silo.conf</filename>. This is because <command>SILO</command> can "
+"actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is "
+"read at boot time, so there is no need to rerun <command>silo</command> "
+"after installing a new kernel like you would with <command>LILO</command>. "
+"<command>SILO</command> can also read UFS partitions, which means it can "
+"boot SunOS/Solaris partitions as well. This is useful if you want to install "
+"GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
@@ -2510,13 +3774,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3126
 #, no-c-format
-msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)."
+msgid ""
+"This option can be used to complete the installation even when no boot "
+"loader is to be installed, either because the arch/subarch doesn't provide "
+"one, or because none is desired (e.g. you will use existing boot loader)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3133
 #, no-c-format
-msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
+msgid ""
+"If you plan to manually configure your bootloader, you should check the name "
+"of the installed kernel in <filename>/target/boot</filename>. You should "
+"also check that directory for the presence of an <firstterm>initrd</"
+"firstterm>; if one is present, you will probably have to instruct your "
+"bootloader to use it. Other information you will need are the disk and "
+"partition you selected for your <filename>/</filename> filesystem and, if "
+"you chose to install <filename>/boot</filename> on a separate partition, "
+"also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2528,7 +3803,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3151
 #, no-c-format
-msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
+msgid ""
+"This is the last step in the &debian; installation process during which the "
+"installer will do any last minute tasks. It mostly consists of tidying up "
+"after the &d-i;."
 msgstr ""
 
 #. Tag: title
@@ -2540,19 +3818,32 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3166
 #, no-c-format
-msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
+msgid ""
+"The installer may ask you if the computer's clock is set to UTC. Normally "
+"this question is avoided if possible and the installer tries to work out "
+"whether the clock is set to UTC based on things like what other operating "
+"systems are installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3173
 #, no-c-format
-msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
+msgid ""
+"In expert mode you will always be able to choose whether or not the clock is "
+"set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally "
+"set to local time. If you want to dual-boot, select local time instead of "
+"UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or "
+"Windows are normally set to local time. If you want to dual-boot, select "
+"local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3184
 #, no-c-format
-msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
+msgid ""
+"At this point &d-i; will also attempt to save the current time to the "
+"system's hardware clock. This will be done either in UTC or local time, "
+"depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
@@ -2564,13 +3855,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3201
 #, no-c-format
-msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system."
+msgid ""
+"You will be prompted to remove the boot media (CD, floppy, etc) that you "
+"used to boot the installer. After that the system will be rebooted into your "
+"new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3207
 #, no-c-format
-msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation."
+msgid ""
+"After a final prompt the system will be halted because rebooting is not "
+"supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD "
+"which you selected for the root filesystem during the first steps of the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2582,7 +3880,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3221
 #, no-c-format
-msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
+msgid ""
+"The components listed in this section are usually not involved in the "
+"installation process, but are waiting in the background to help the user in "
+"case something goes wrong."
 msgstr ""
 
 #. Tag: title
@@ -2594,13 +3895,21 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3236
 #, no-c-format
-msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system."
+msgid ""
+"If the installation is successful, the logfiles created during the "
+"installation process will be automatically saved to <filename>/var/log/"
+"installer/</filename> on your new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3243
 #, no-c-format
-msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
+msgid ""
+"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu "
+"allows you to save the log files to a floppy disk, network, hard disk, or "
+"other media. This can be useful if you encounter fatal problems during the "
+"installation and wish to study the logs on another system or attach them to "
+"an installation report."
 msgstr ""
 
 #. Tag: title
@@ -2612,7 +3921,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3265
 #, no-c-format
-msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
+msgid ""
+"There are several methods you can use to get a shell while running an "
+"installation. On most systems, and if you are not installing over serial "
+"console, the easiest method is to switch to the second <emphasis>virtual "
+"console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> "
+"<keycap>F2</keycap></keycombo><footnote> <para> That is: press the "
+"<keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</"
+"keycap> and the <keycap>F2</keycap> function key at the same time. </para> </"
+"footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</"
+"keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</"
+"keycap></keycombo> to switch back to the installer itself."
 msgstr ""
 
 #. Tag: para
@@ -2624,31 +3943,52 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3287
 #, no-c-format
-msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
+msgid ""
+"If you cannot switch consoles, there is also an <guimenuitem>Execute a "
+"Shell</guimenuitem> item on the main menu that can be used to start a shell. "
+"You can get to the main menu from most dialogs by using the &BTN-GOBACK; "
+"button one or more times. Type <userinput>exit</userinput> to close the "
+"shell and return to the installer."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3295
 #, no-c-format
-msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
+msgid ""
+"At this point you are booted from the RAM disk, and there is a limited set "
+"of Unix utilities available for your use. You can see what programs are "
+"available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</"
+"command> and by typing <command>help</command>. The shell is a Bourne shell "
+"clone called <command>ash</command> and has some nice features like "
+"autocompletion and history."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3304
 #, no-c-format
-msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
+msgid ""
+"To edit and view files, use the text editor <command>nano</command>. Log "
+"files for the installation system can be found in the <filename>/var/log</"
+"filename> directory."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3311
 #, no-c-format
-msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
+msgid ""
+"Although you can do basically anything in a shell that the available "
+"commands allow you to do, the option to use a shell is really only there in "
+"case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3317
 #, no-c-format
-msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
+msgid ""
+"Doing things manually from the shell may interfere with the installation "
+"process and result in errors or an incomplete installation. In particular, "
+"you should always use let the installer activate your swap partition and not "
+"do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
@@ -2660,70 +4000,146 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3335
 #, no-c-format
-msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
+msgid ""
+"One of the more interesting components is <firstterm>network-console</"
+"firstterm>. It allows you to do a large part of the installation over the "
+"network via SSH. The use of the network implies you will have to perform the "
+"first steps of the installation from the console, at least to the point of "
+"setting up the networking. (Although you can automate that part with <xref "
+"linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3345
 #, no-c-format
-msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
+msgid ""
+"This component is not loaded into the main installation menu by default, so "
+"you have to explicitly ask for it. If you are installing from CD, you need "
+"to boot with medium priority or otherwise invoke the main installation menu "
+"and choose <guimenuitem>Load installer components from CD</guimenuitem> and "
+"from the list of additional components select <guimenuitem>network-console: "
+"Continue installation remotely using SSH</guimenuitem>. Successful load is "
+"indicated by a new menu entry called <guimenuitem>Continue installation "
+"remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3358
 #, no-c-format
-msgid "For installations on &arch-title;, this is the default method after setting up the network."
+msgid ""
+"For installations on &arch-title;, this is the default method after setting "
+"up the network."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3363
 #, no-c-format
-msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely."
+msgid ""
+"<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> "
+"<phrase arch=\"s390\">You</phrase> will be asked for a new password to be "
+"used for connecting to the installation system and for its confirmation. "
+"That's all. Now you should see a screen which instructs you to login "
+"remotely as the user <emphasis>installer</emphasis> with the password you "
+"just provided. Another important detail to notice on this screen is the "
+"fingerprint of this system. You need to transfer the fingerprint securely to "
+"the person who will continue the installation remotely."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3375
 #, no-c-format
-msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
+msgid ""
+"Should you decide to continue with the installation locally, you can always "
+"press &enterkey;, which will bring you back to the main menu, where you can "
+"select another component."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3381
 #, no-c-format
 msgid ""
-      "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
-      "<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n"
-      "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct."
+"Now let's switch to the other side of the wire. As a prerequisite, you need "
+"to configure your terminal for UTF-8 encoding, because that is what the "
+"installation system uses. If you do not, remote installation will be still "
+"possible, but you may encounter strange display artefacts like destroyed "
+"dialog borders or unreadable non-ascii characters. Establishing a connection "
+"with the installation system is as simple as typing: "
+"<informalexample><screen>\n"
+"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</"
+"replaceable></userinput>\n"
+"</screen></informalexample> Where <replaceable>install_host</replaceable> is "
+"either the name or IP address of the computer being installed. Before the "
+"actual login the fingerprint of the remote system will be displayed and you "
+"will have to confirm that it is correct."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3398
 #, no-c-format
-msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
+msgid ""
+"The <command>ssh</command> server in the installer uses a default "
+"configuration that does not send keep-alive packets. In principle, a "
+"connection to the system being installed should be kept open indefinitely. "
+"However, in some situations &mdash; depending on your local network setup "
+"&mdash; the connection may be lost after some period of inactivity. One "
+"common case where this can happen is when there is some form of Network "
+"Address Translation (NAT) somewhere between the client and the system being "
+"installed. Depending on at which point of the installation the connection "
+"was lost, you may or may not be able to resume the installation after "
+"reconnecting."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3411
 #, no-c-format
-msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
+msgid ""
+"You may be able to avoid the connection being dropped by adding the option "
+"<userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></"
+"userinput> when starting the <command>ssh</command> connection, or by adding "
+"that option in your <command>ssh</command> configuration file. Note however "
+"that in some cases adding this option may also <emphasis>cause</emphasis> a "
+"connection to be dropped (for example if keep-alive packets are sent during "
+"a brief network outage, from which <command>ssh</command> would otherwise "
+"have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3424
 #, no-c-format
-msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
+msgid ""
+"If you install several computers in turn and they happen to have the same IP "
+"address or hostname, <command>ssh</command> will refuse to connect to such "
+"host. The reason is that it will have different fingerprint, which is "
+"usually a sign of a spoofing attack. If you are sure this is not the case, "
+"you will need to delete the relevant line from <filename>~/.ssh/known_hosts</"
+"filename><footnote> <para> The following command will remove an existing "
+"entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</"
+"replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </"
+"para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3440
 #, no-c-format
-msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
+msgid ""
+"After the login you will be presented with an initial screen where you have "
+"two possibilities called <guimenuitem>Start menu</guimenuitem> and "
+"<guimenuitem>Start shell</guimenuitem>. The former brings you to the main "
+"installer menu, where you can continue with the installation as usual. The "
+"latter starts a shell from which you can examine and possibly fix the remote "
+"system. You should only start one SSH session for the installation menu, but "
+"may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3450
 #, no-c-format
-msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
+msgid ""
+"After you have started the installation remotely over SSH, you should not go "
+"back to the installation session running on the local console. Doing so may "
+"corrupt the database that holds the configuration of the new system. This in "
+"turn may result in a failed installation or problems with the installed "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -2735,25 +4151,44 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3470
 #, no-c-format
-msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
+msgid ""
+"As described in <xref linkend=\"hardware-firmware\"/>, some devices require "
+"firmware to be loaded. In most cases the device will not work at all if the "
+"firmware is not available; sometimes basic functionality is not impaired if "
+"it is missing and the firmware is only needed to enable additional features."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3478
 #, no-c-format
-msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
+msgid ""
+"If a device driver requests firmware that is not available, &d-i; will "
+"display a dialog offering to load the missing firmware. If this option is "
+"selected, &d-i; will scan available devices for either loose firmware files "
+"or packages containing firmware. If found, the firmware will be copied to "
+"the correct location (<filename>/lib/firmware</filename>) and the driver "
+"module will be reloaded."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3488
 #, no-c-format
-msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
+msgid ""
+"Which devices are scanned and which file systems are supported depends on "
+"the architecture, the installation method and the stage of the installation. "
+"Especially during the early stages of the installation, loading the firmware "
+"is most likely to succeed from a FAT-formatted floppy disk or USB stick. "
+"<phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an "
+"MMC or SD card.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3498
 #, no-c-format
-msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
+msgid ""
+"Note that it is possible to skip loading the firmware if you know the device "
+"will also function without it, or if the device is not needed during the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2765,25 +4200,47 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3507
 #, no-c-format
-msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
+msgid ""
+"Official CD images do not include non-free firmware. The most common method "
+"to load such firmware is from some removable medium such as a USB stick. "
+"Alternatively, unofficial CD builds containing non-free firmware can be "
+"found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick "
+"(or other medium like a hard drive partition, or floppy disk), the firmware "
+"files or packages must be placed in either the root directory or a directory "
+"named <filename>/firmware</filename> of the file system on the medium. The "
+"recommended file system to use is FAT as that is most certain to be "
+"supported during the early stages of the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3520
 #, no-c-format
-msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
+msgid ""
+"Tarballs and zip files containing current packages for the most common "
+"firmware are available from: <itemizedlist> <listitem><para> <ulink url="
+"\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just "
+"download the tarball or zip file for the correct release and unpack it to "
+"the file system on the medium."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3534
 #, no-c-format
-msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
+msgid ""
+"If the firmware you need is not included in the tarball, you can also "
+"download specific firmware packages from the (non-free section of the) "
+"archive. The following overview should list most available firmware packages "
+"but is not guaranteed to be complete and may also contain non-firmware "
+"packages:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3548
 #, no-c-format
-msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
+msgid ""
+"It is also possible to copy individual firmware files to the medium. Loose "
+"firmware could be obtained for example from an already installed system or "
+"from a hardware vendor."
 msgstr ""
 
 #. Tag: title
@@ -2795,24 +4252,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3558
 #, no-c-format
-msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
+msgid ""
+"Any firmware loaded during the installation will be copied automatically to "
+"the installed system. In most cases this will ensure that the device that "
+"requires the firmware will also work correctly after the system is rebooted "
+"into the installed system. However, if the installed system runs a different "
+"kernel version from the installer there is a slight chance that the firmware "
+"cannot be loaded due to version skew."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3567
 #, no-c-format
-msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
+msgid ""
+"If the firmware was loaded from a firmware package, &d-i; will also install "
+"this package for the installed system and will automatically add the non-"
+"free section of the package archive in APT's <filename>sources.list</"
+"filename>. This has the advantage that the firmware should be updated "
+"automatically if a new version becomes available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3575
 #, no-c-format
-msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
+msgid ""
+"If loading the firmware was skipped during the installation, the relevant "
+"device will probably not work with the installed system until the firmware "
+"(package) is installed manually."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3582
 #, no-c-format
-msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
+msgid ""
+"If the firmware was loaded from loose firmware files, the firmware copied to "
+"the installed system will <emphasis>not</emphasis> be automatically updated "
+"unless the corresponding firmware package (if available) is installed after "
+"the installation is completed."
 msgstr ""
-
diff --git a/po/nn/welcome.po b/po/nn/welcome.po
index 0d1732af4..17fad591c 100644
--- a/po/nn/welcome.po
+++ b/po/nn/welcome.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:5
 #, no-c-format
-msgid "This chapter provides an overview of the &debian; Project and &debian-gnu;. If you already know about the &debian; Project's history and the &debian-gnu; distribution, feel free to skip to the next chapter."
+msgid ""
+"This chapter provides an overview of the &debian; Project and &debian-gnu;. "
+"If you already know about the &debian; Project's history and the &debian-"
+"gnu; distribution, feel free to skip to the next chapter."
 msgstr ""
 
 #. Tag: title
@@ -34,67 +38,116 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:20
 #, no-c-format
-msgid "Debian is an all-volunteer organization dedicated to developing free software and promoting the ideals of the Free Software community. The Debian Project began in 1993, when Ian Murdock issued an open invitation to software developers to contribute to a complete and coherent software distribution based on the relatively new Linux kernel. That relatively small band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-fsf;\">Free Software Foundation</ulink> and influenced by the <ulink url=\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years into an organization of around &num-of-debian-developers; <firstterm>Debian Developers</firstterm>."
+msgid ""
+"Debian is an all-volunteer organization dedicated to developing free "
+"software and promoting the ideals of the Free Software community. The Debian "
+"Project began in 1993, when Ian Murdock issued an open invitation to "
+"software developers to contribute to a complete and coherent software "
+"distribution based on the relatively new Linux kernel. That relatively small "
+"band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-"
+"fsf;\">Free Software Foundation</ulink> and influenced by the <ulink url="
+"\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years into an "
+"organization of around &num-of-debian-developers; <firstterm>Debian "
+"Developers</firstterm>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:35
 #, no-c-format
-msgid "Debian Developers are involved in a variety of activities, including <ulink url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;\">FTP</ulink> site administration, graphic design, legal analysis of software licenses, writing documentation, and, of course, maintaining software packages."
+msgid ""
+"Debian Developers are involved in a variety of activities, including <ulink "
+"url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;"
+"\">FTP</ulink> site administration, graphic design, legal analysis of "
+"software licenses, writing documentation, and, of course, maintaining "
+"software packages."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:44
 #, no-c-format
-msgid "In the interest of communicating our philosophy and attracting developers who believe in the principles that Debian stands for, the Debian Project has published a number of documents that outline our values and serve as guides to what it means to be a Debian Developer:"
+msgid ""
+"In the interest of communicating our philosophy and attracting developers "
+"who believe in the principles that Debian stands for, the Debian Project has "
+"published a number of documents that outline our values and serve as guides "
+"to what it means to be a Debian Developer:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:52
 #, no-c-format
-msgid "The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a statement of Debian's commitments to the Free Software Community. Anyone who agrees to abide to the Social Contract may become a <ulink url=\"&url-new-maintainer;\">maintainer</ulink>. Any maintainer can introduce new software into Debian &mdash; provided that the software meets our criteria for being free, and the package follows our quality standards."
+msgid ""
+"The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a "
+"statement of Debian's commitments to the Free Software Community. Anyone who "
+"agrees to abide to the Social Contract may become a <ulink url=\"&url-new-"
+"maintainer;\">maintainer</ulink>. Any maintainer can introduce new software "
+"into Debian &mdash; provided that the software meets our criteria for being "
+"free, and the package follows our quality standards."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:64
 #, no-c-format
-msgid "The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a clear and concise statement of Debian's criteria for free software. The DFSG is a very influential document in the Free Software Movement, and was the foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</ulink>."
+msgid ""
+"The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a "
+"clear and concise statement of Debian's criteria for free software. The DFSG "
+"is a very influential document in the Free Software Movement, and was the "
+"foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</"
+"ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:74
 #, no-c-format
-msgid "The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an extensive specification of the Debian Project's standards of quality."
+msgid ""
+"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an "
+"extensive specification of the Debian Project's standards of quality."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:82
 #, no-c-format
-msgid "Debian developers are also involved in a number of other projects; some specific to Debian, others involving some or all of the Linux community. Some examples include:"
+msgid ""
+"Debian developers are also involved in a number of other projects; some "
+"specific to Debian, others involving some or all of the Linux community. "
+"Some examples include:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:89
 #, no-c-format
-msgid "The <ulink url=\"&url-lsb-org;\">Linux Standard Base</ulink> (LSB) is a project aimed at standardizing the basic GNU/Linux system, which will enable third-party software and hardware developers to easily design programs and device drivers for Linux-in-general, rather than for a specific GNU/Linux distribution."
+msgid ""
+"The <ulink url=\"&url-lsb-org;\">Linux Standard Base</ulink> (LSB) is a "
+"project aimed at standardizing the basic GNU/Linux system, which will enable "
+"third-party software and hardware developers to easily design programs and "
+"device drivers for Linux-in-general, rather than for a specific GNU/Linux "
+"distribution."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:99
 #, no-c-format
-msgid "The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> (FHS) is an effort to standardize the layout of the Linux file system. The FHS will allow software developers to concentrate their efforts on designing programs, without having to worry about how the package will be installed in different GNU/Linux distributions."
+msgid ""
+"The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> "
+"(FHS) is an effort to standardize the layout of the Linux file system. The "
+"FHS will allow software developers to concentrate their efforts on designing "
+"programs, without having to worry about how the package will be installed in "
+"different GNU/Linux distributions."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:109
 #, no-c-format
-msgid "<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, aimed at making sure Debian has something to offer to our youngest users."
+msgid ""
+"<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, "
+"aimed at making sure Debian has something to offer to our youngest users."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:118
 #, no-c-format
-msgid "For more general information about Debian, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>."
+msgid ""
+"For more general information about Debian, see the <ulink url=\"&url-debian-"
+"faq;\">Debian FAQ</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,61 +159,113 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:134
 #, no-c-format
-msgid "Linux is an operating system: a series of programs that let you interact with your computer and run other programs."
+msgid ""
+"Linux is an operating system: a series of programs that let you interact "
+"with your computer and run other programs."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:139
 #, no-c-format
-msgid "An operating system consists of various fundamental programs which are needed by your computer so that it can communicate and receive instructions from users; read and write data to hard disks, tapes, and printers; control the use of memory; and run other software. The most important part of an operating system is the kernel. In a GNU/Linux system, Linux is the kernel component. The rest of the system consists of other programs, many of which were written by or for the GNU Project. Because the Linux kernel alone does not form a working operating system, we prefer to use the term <quote>GNU/Linux</quote> to refer to systems that many people casually refer to as <quote>Linux</quote>."
+msgid ""
+"An operating system consists of various fundamental programs which are "
+"needed by your computer so that it can communicate and receive instructions "
+"from users; read and write data to hard disks, tapes, and printers; control "
+"the use of memory; and run other software. The most important part of an "
+"operating system is the kernel. In a GNU/Linux system, Linux is the kernel "
+"component. The rest of the system consists of other programs, many of which "
+"were written by or for the GNU Project. Because the Linux kernel alone does "
+"not form a working operating system, we prefer to use the term <quote>GNU/"
+"Linux</quote> to refer to systems that many people casually refer to as "
+"<quote>Linux</quote>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:153
 #, no-c-format
-msgid "Linux is modelled on the Unix operating system. From the start, Linux was designed to be a multi-tasking, multi-user system. These facts are enough to make Linux different from other well-known operating systems. However, Linux is even more different than you might imagine. In contrast to other operating systems, nobody owns Linux. Much of its development is done by unpaid volunteers."
+msgid ""
+"Linux is modelled on the Unix operating system. From the start, Linux was "
+"designed to be a multi-tasking, multi-user system. These facts are enough to "
+"make Linux different from other well-known operating systems. However, Linux "
+"is even more different than you might imagine. In contrast to other "
+"operating systems, nobody owns Linux. Much of its development is done by "
+"unpaid volunteers."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:162
 #, no-c-format
-msgid "Development of what later became GNU/Linux began in 1984, when the <ulink url=\"&url-fsf;\">Free Software Foundation</ulink> began development of a free Unix-like operating system called GNU."
+msgid ""
+"Development of what later became GNU/Linux began in 1984, when the <ulink "
+"url=\"&url-fsf;\">Free Software Foundation</ulink> began development of a "
+"free Unix-like operating system called GNU."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:168
 #, no-c-format
-msgid "The <ulink url=\"&url-gnu;\">GNU Project</ulink> has developed a comprehensive set of free software tools for use with Unix&trade; and Unix-like operating systems such as Linux. These tools enable users to perform tasks ranging from the mundane (such as copying or removing files from the system) to the arcane (such as writing and compiling programs or doing sophisticated editing in a variety of document formats)."
+msgid ""
+"The <ulink url=\"&url-gnu;\">GNU Project</ulink> has developed a "
+"comprehensive set of free software tools for use with Unix&trade; and Unix-"
+"like operating systems such as Linux. These tools enable users to perform "
+"tasks ranging from the mundane (such as copying or removing files from the "
+"system) to the arcane (such as writing and compiling programs or doing "
+"sophisticated editing in a variety of document formats)."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:178
 #, no-c-format
-msgid "While many groups and individuals have contributed to Linux, the largest single contributor is still the Free Software Foundation, which created not only most of the tools used in Linux, but also the philosophy and the community that made Linux possible."
+msgid ""
+"While many groups and individuals have contributed to Linux, the largest "
+"single contributor is still the Free Software Foundation, which created not "
+"only most of the tools used in Linux, but also the philosophy and the "
+"community that made Linux possible."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:185
 #, no-c-format
-msgid "The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in 1991, when a Finnish computing science student named Linus Torvalds announced an early version of a replacement kernel for Minix to the Usenet newsgroup <userinput>comp.os.minix</userinput>. See Linux International's <ulink url=\"&url-linux-history;\">Linux History Page</ulink>."
+msgid ""
+"The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in "
+"1991, when a Finnish computing science student named Linus Torvalds "
+"announced an early version of a replacement kernel for Minix to the Usenet "
+"newsgroup <userinput>comp.os.minix</userinput>. See Linux International's "
+"<ulink url=\"&url-linux-history;\">Linux History Page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:194
 #, no-c-format
-msgid "Linus Torvalds continues to coordinate the work of several hundred developers with the help of a number of subsystem maintainers. There is an <ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux kernel. More information about the <userinput>linux-kernel</userinput> mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel mailing list FAQ</ulink>."
+msgid ""
+"Linus Torvalds continues to coordinate the work of several hundred "
+"developers with the help of a number of subsystem maintainers. There is an "
+"<ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux "
+"kernel. More information about the <userinput>linux-kernel</userinput> "
+"mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;"
+"\">linux-kernel mailing list FAQ</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:204
 #, no-c-format
-msgid "Linux users have immense freedom of choice in their software. For example, Linux users can choose from a dozen different command line shells and several graphical desktops. This selection is often bewildering to users of other operating systems, who are not used to thinking of the command line or desktop as something that they can change."
+msgid ""
+"Linux users have immense freedom of choice in their software. For example, "
+"Linux users can choose from a dozen different command line shells and "
+"several graphical desktops. This selection is often bewildering to users of "
+"other operating systems, who are not used to thinking of the command line or "
+"desktop as something that they can change."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:213
 #, no-c-format
-msgid "Linux is also less likely to crash, better able to run more than one program at the same time, and more secure than many operating systems. With these advantages, Linux is the fastest growing operating system in the server market. More recently, Linux has begun to be popular among home and business users as well."
+msgid ""
+"Linux is also less likely to crash, better able to run more than one program "
+"at the same time, and more secure than many operating systems. With these "
+"advantages, Linux is the fastest growing operating system in the server "
+"market. More recently, Linux has begun to be popular among home and business "
+"users as well."
 msgstr ""
 
 #. Tag: title
@@ -172,49 +277,96 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:232
 #, no-c-format
-msgid "The combination of &debian;'s philosophy and methodology and the GNU tools, the Linux kernel, and other important free software, form a unique software distribution called &debian; GNU/Linux. This distribution is made up of a large number of software <emphasis>packages</emphasis>. Each package in the distribution contains executables, scripts, documentation, and configuration information, and has a <emphasis>maintainer</emphasis> who is primarily responsible for keeping the package up-to-date, tracking bug reports, and communicating with the upstream author(s) of the packaged software. Our extremely large user base, combined with our bug tracking system ensures that problems are found and fixed quickly."
+msgid ""
+"The combination of &debian;'s philosophy and methodology and the GNU tools, "
+"the Linux kernel, and other important free software, form a unique software "
+"distribution called &debian; GNU/Linux. This distribution is made up of a "
+"large number of software <emphasis>packages</emphasis>. Each package in the "
+"distribution contains executables, scripts, documentation, and configuration "
+"information, and has a <emphasis>maintainer</emphasis> who is primarily "
+"responsible for keeping the package up-to-date, tracking bug reports, and "
+"communicating with the upstream author(s) of the packaged software. Our "
+"extremely large user base, combined with our bug tracking system ensures "
+"that problems are found and fixed quickly."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:246
 #, no-c-format
-msgid "&debian;'s attention to detail allows us to produce a high-quality, stable, and scalable distribution. Installations can be easily configured to serve many roles, from stripped-down firewalls to desktop scientific workstations to high-end network servers."
+msgid ""
+"&debian;'s attention to detail allows us to produce a high-quality, stable, "
+"and scalable distribution. Installations can be easily configured to serve "
+"many roles, from stripped-down firewalls to desktop scientific workstations "
+"to high-end network servers."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:253
 #, no-c-format
-msgid "&debian; is especially popular among advanced users because of its technical excellence and its deep commitment to the needs and expectations of the Linux community. &debian; also introduced many features to Linux that are now commonplace."
+msgid ""
+"&debian; is especially popular among advanced users because of its technical "
+"excellence and its deep commitment to the needs and expectations of the "
+"Linux community. &debian; also introduced many features to Linux that are "
+"now commonplace."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:260
 #, no-c-format
-msgid "For example, &debian; was the first Linux distribution to include a package management system for easy installation and removal of software. It was also the first Linux distribution that could be upgraded without requiring reinstallation."
+msgid ""
+"For example, &debian; was the first Linux distribution to include a package "
+"management system for easy installation and removal of software. It was also "
+"the first Linux distribution that could be upgraded without requiring "
+"reinstallation."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:267
 #, no-c-format
-msgid "&debian; continues to be a leader in Linux development. Its development process is an example of just how well the Open Source development model can work &mdash; even for very complex tasks such as building and maintaining a complete operating system."
+msgid ""
+"&debian; continues to be a leader in Linux development. Its development "
+"process is an example of just how well the Open Source development model can "
+"work &mdash; even for very complex tasks such as building and maintaining a "
+"complete operating system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:274
 #, no-c-format
-msgid "The feature that most distinguishes &debian; from other Linux distributions is its package management system. These tools give the administrator of a &debian; system complete control over the packages installed on that system, including the ability to install a single package or automatically update the entire operating system. Individual packages can also be protected from being updated. You can even tell the package management system about software you have compiled yourself and what dependencies it fulfills."
+msgid ""
+"The feature that most distinguishes &debian; from other Linux distributions "
+"is its package management system. These tools give the administrator of a "
+"&debian; system complete control over the packages installed on that system, "
+"including the ability to install a single package or automatically update "
+"the entire operating system. Individual packages can also be protected from "
+"being updated. You can even tell the package management system about "
+"software you have compiled yourself and what dependencies it fulfills."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:285
 #, no-c-format
-msgid "To protect your system against <quote>Trojan horses</quote> and other malevolent software, &debian;'s servers verify that uploaded packages come from their registered &debian; maintainers. &debian; packagers also take great care to configure their packages in a secure manner. When security problems in shipped packages do appear, fixes are usually available very quickly. With &debian;'s simple update options, security fixes can be downloaded and installed automatically across the Internet."
+msgid ""
+"To protect your system against <quote>Trojan horses</quote> and other "
+"malevolent software, &debian;'s servers verify that uploaded packages come "
+"from their registered &debian; maintainers. &debian; packagers also take "
+"great care to configure their packages in a secure manner. When security "
+"problems in shipped packages do appear, fixes are usually available very "
+"quickly. With &debian;'s simple update options, security fixes can be "
+"downloaded and installed automatically across the Internet."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:295
 #, no-c-format
-msgid "The primary, and best, method of getting support for your &debian; GNU/Linux system and communicating with &debian; Developers is through the many mailing lists maintained by the &debian; Project (there are more than &num-of-debian-maillists; at this writing). The easiest way to subscribe to one or more of these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> Debian's mailing list subscription page</ulink> and fill out the form you'll find there."
+msgid ""
+"The primary, and best, method of getting support for your &debian; GNU/Linux "
+"system and communicating with &debian; Developers is through the many "
+"mailing lists maintained by the &debian; Project (there are more than &num-"
+"of-debian-maillists; at this writing). The easiest way to subscribe to one "
+"or more of these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> "
+"Debian's mailing list subscription page</ulink> and fill out the form you'll "
+"find there."
 msgstr ""
 
 #. Tag: title
@@ -226,25 +378,33 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:317
 #, no-c-format
-msgid "&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel."
+msgid ""
+"&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:321
 #, no-c-format
-msgid "This port of &debian; is currently only being developed for the i386 and amd64 architectures, although ports to other architectures is possible."
+msgid ""
+"This port of &debian; is currently only being developed for the i386 and "
+"amd64 architectures, although ports to other architectures is possible."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:326
 #, no-c-format
-msgid "Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some information on Linux system may not apply to it."
+msgid ""
+"Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some "
+"information on Linux system may not apply to it."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:331
 #, no-c-format
-msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/kfreebsd-gnu/\"> &debian; GNU/kFreeBSD ports page</ulink> and the <email>debian-bsd@lists.debian.org</email> mailing list."
+msgid ""
+"For more information, see the <ulink url=\"http://www.debian.org/ports/"
+"kfreebsd-gnu/\"> &debian; GNU/kFreeBSD ports page</ulink> and the "
+"<email>debian-bsd@lists.debian.org</email> mailing list."
 msgstr ""
 
 #. Tag: title
@@ -256,25 +416,36 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:352
 #, no-c-format
-msgid "&debian; GNU/Hurd is a &debian; GNU system with the GNU Hurd &mdash; a set of servers running on top of the GNU Mach microkernel."
+msgid ""
+"&debian; GNU/Hurd is a &debian; GNU system with the GNU Hurd &mdash; a set "
+"of servers running on top of the GNU Mach microkernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:357
 #, no-c-format
-msgid "The Hurd is still unfinished, and is unsuitable for day-to-day use, but work is continuing. The Hurd is currently only being developed for the i386 architecture, although ports to other architectures will be made once the system becomes more stable."
+msgid ""
+"The Hurd is still unfinished, and is unsuitable for day-to-day use, but work "
+"is continuing. The Hurd is currently only being developed for the i386 "
+"architecture, although ports to other architectures will be made once the "
+"system becomes more stable."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:365
 #, no-c-format
-msgid "Please note that &debian; GNU/Hurd is not a Linux system, and thus some information on Linux system may not apply to it."
+msgid ""
+"Please note that &debian; GNU/Hurd is not a Linux system, and thus some "
+"information on Linux system may not apply to it."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:370
 #, no-c-format
-msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/\"> &debian; GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists.debian.org</email> mailing list."
+msgid ""
+"For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/"
+"\"> &debian; GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists."
+"debian.org</email> mailing list."
 msgstr ""
 
 #. Tag: title
@@ -286,13 +457,21 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:389
 #, no-c-format
-msgid "For information on how to download &debian-gnu; from the Internet or from whom official &debian; CDs can be purchased, see the <ulink url=\"&url-debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink> contains a full set of official &debian; mirrors, so you can easily find the nearest one."
+msgid ""
+"For information on how to download &debian-gnu; from the Internet or from "
+"whom official &debian; CDs can be purchased, see the <ulink url=\"&url-"
+"debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-"
+"debian-mirrors;\">list of &debian; mirrors</ulink> contains a full set of "
+"official &debian; mirrors, so you can easily find the nearest one."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:398
 #, no-c-format
-msgid "&debian; can be upgraded after installation very easily. The installation procedure will help set up the system so that you can make those upgrades once installation is complete, if need be."
+msgid ""
+"&debian; can be upgraded after installation very easily. The installation "
+"procedure will help set up the system so that you can make those upgrades "
+"once installation is complete, if need be."
 msgstr ""
 
 #. Tag: title
@@ -304,7 +483,12 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:415
 #, no-c-format
-msgid "This document is constantly being revised. Be sure to check the <ulink url=\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute information about the &release; release of the &debian-gnu; system. Updated versions of this installation manual are also available from the <ulink url=\"&url-install-manual;\">official Install Manual pages</ulink>."
+msgid ""
+"This document is constantly being revised. Be sure to check the <ulink url="
+"\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute "
+"information about the &release; release of the &debian-gnu; system. Updated "
+"versions of this installation manual are also available from the <ulink url="
+"\"&url-install-manual;\">official Install Manual pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -316,67 +500,104 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:435
 #, no-c-format
-msgid "This document is meant to serve as a manual for first-time &debian; users. It tries to make as few assumptions as possible about your level of expertise. However, we do assume that you have a general understanding of how the hardware in your computer works."
+msgid ""
+"This document is meant to serve as a manual for first-time &debian; users. "
+"It tries to make as few assumptions as possible about your level of "
+"expertise. However, we do assume that you have a general understanding of "
+"how the hardware in your computer works."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:442
 #, no-c-format
-msgid "Expert users may also find interesting reference information in this document, including minimum installation sizes, details about the hardware supported by the &debian; installation system, and so on. We encourage expert users to jump around in the document."
+msgid ""
+"Expert users may also find interesting reference information in this "
+"document, including minimum installation sizes, details about the hardware "
+"supported by the &debian; installation system, and so on. We encourage "
+"expert users to jump around in the document."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:449
 #, no-c-format
-msgid "In general, this manual is arranged in a linear fashion, walking you through the installation process from start to finish. Here are the steps in installing &debian-gnu;, and the sections of this document which correlate with each step:"
+msgid ""
+"In general, this manual is arranged in a linear fashion, walking you through "
+"the installation process from start to finish. Here are the steps in "
+"installing &debian-gnu;, and the sections of this document which correlate "
+"with each step:"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:457
 #, no-c-format
-msgid "Determine whether your hardware meets the requirements for using the installation system, in <xref linkend=\"hardware-req\"/>."
+msgid ""
+"Determine whether your hardware meets the requirements for using the "
+"installation system, in <xref linkend=\"hardware-req\"/>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:463
 #, no-c-format
-msgid "Backup your system, perform any necessary planning and hardware configuration prior to installing &debian;, in <xref linkend=\"preparing\"/>. If you are preparing a multi-boot system, you may need to create partitionable space on your hard disk for &debian; to use."
+msgid ""
+"Backup your system, perform any necessary planning and hardware "
+"configuration prior to installing &debian;, in <xref linkend=\"preparing\"/"
+">. If you are preparing a multi-boot system, you may need to create "
+"partitionable space on your hard disk for &debian; to use."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:471
 #, no-c-format
-msgid "In <xref linkend=\"install-methods\"/>, you will obtain the necessary installation files for your method of installation."
+msgid ""
+"In <xref linkend=\"install-methods\"/>, you will obtain the necessary "
+"installation files for your method of installation."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:477
 #, no-c-format
-msgid "describes booting into the installation system. This chapter also discusses troubleshooting procedures in case you have problems with this step."
+msgid ""
+"describes booting into the installation system. This chapter also discusses "
+"troubleshooting procedures in case you have problems with this step."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:484
 #, no-c-format
-msgid "Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a &debian; server (if you are not installing from a CD/DVD set), partitioning your hard drives and installation of a base system, then selection and installation of tasks. (Some background about setting up the partitions for your &debian; system is explained in <xref linkend=\"partitioning\"/>.)"
+msgid ""
+"Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. "
+"This involves choosing your language, configuring peripheral driver modules, "
+"configuring your network connection, so that remaining installation files "
+"can be obtained directly from a &debian; server (if you are not installing "
+"from a CD/DVD set), partitioning your hard drives and installation of a base "
+"system, then selection and installation of tasks. (Some background about "
+"setting up the partitions for your &debian; system is explained in <xref "
+"linkend=\"partitioning\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:497
 #, no-c-format
-msgid "Boot into your newly installed base system, from <xref linkend=\"boot-new\"/>."
+msgid ""
+"Boot into your newly installed base system, from <xref linkend=\"boot-new\"/"
+">."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:505
 #, no-c-format
-msgid "Once you've got your system installed, you can read <xref linkend=\"post-install\"/>. That chapter explains where to look to find more information about Unix and &debian;, and how to replace your kernel."
+msgid ""
+"Once you've got your system installed, you can read <xref linkend=\"post-"
+"install\"/>. That chapter explains where to look to find more information "
+"about Unix and &debian;, and how to replace your kernel."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:515
 #, no-c-format
-msgid "Finally, information about this document and how to contribute to it may be found in <xref linkend=\"administrivia\"/>."
+msgid ""
+"Finally, information about this document and how to contribute to it may be "
+"found in <xref linkend=\"administrivia\"/>."
 msgstr ""
 
 #. Tag: title
@@ -388,13 +609,22 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:527
 #, no-c-format
-msgid "Any help, suggestions, and especially, patches, are greatly appreciated. Working versions of this document can be found at <ulink url=\"&url-d-i-alioth-manual;\"></ulink>. There you will find a list of all the different architectures and languages for which this document is available."
+msgid ""
+"Any help, suggestions, and especially, patches, are greatly appreciated. "
+"Working versions of this document can be found at <ulink url=\"&url-d-i-"
+"alioth-manual;\"></ulink>. There you will find a list of all the different "
+"architectures and languages for which this document is available."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:534
 #, no-c-format
-msgid "Source is also available publicly; look in <xref linkend=\"administrivia\"/> for more information concerning how to contribute. We welcome suggestions, comments, patches, and bug reports (use the package <classname>installation-guide</classname> for bugs, but check first to see if the problem is already reported)."
+msgid ""
+"Source is also available publicly; look in <xref linkend=\"administrivia\"/> "
+"for more information concerning how to contribute. We welcome suggestions, "
+"comments, patches, and bug reports (use the package <classname>installation-"
+"guide</classname> for bugs, but check first to see if the problem is already "
+"reported)."
 msgstr ""
 
 #. Tag: title
@@ -406,42 +636,91 @@ msgstr ""
 #. Tag: para
 #: welcome.xml:553
 #, no-c-format
-msgid "We're sure that you've read some of the licenses that come with most commercial software &mdash; they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of &debian-gnu; on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and <emphasis>sell</emphasis> them &mdash; albeit with a few restrictions. Your freedom to install and use the system comes directly from &debian; being based on <emphasis>free software</emphasis>."
+msgid ""
+"We're sure that you've read some of the licenses that come with most "
+"commercial software &mdash; they usually say that you can only use one copy "
+"of the software on a single computer. This system's license isn't like that "
+"at all. We encourage you to put a copy of &debian-gnu; on every computer in "
+"your school or place of business. Lend your installation media to your "
+"friends and help them install it on their computers! You can even make "
+"thousands of copies and <emphasis>sell</emphasis> them &mdash; albeit with a "
+"few restrictions. Your freedom to install and use the system comes directly "
+"from &debian; being based on <emphasis>free software</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:566
 #, no-c-format
-msgid "Calling software <emphasis>free</emphasis> doesn't mean that the software isn't copyrighted, and it doesn't mean that CDs/DVDs containing that software must be distributed at no charge. Free software, in part, means that the licenses of individual programs do not require you to pay for the privilege of distributing or using those programs. Free software also means that not only may anyone extend, adapt, and modify the software, but that they may distribute the results of their work as well."
+msgid ""
+"Calling software <emphasis>free</emphasis> doesn't mean that the software "
+"isn't copyrighted, and it doesn't mean that CDs/DVDs containing that "
+"software must be distributed at no charge. Free software, in part, means "
+"that the licenses of individual programs do not require you to pay for the "
+"privilege of distributing or using those programs. Free software also means "
+"that not only may anyone extend, adapt, and modify the software, but that "
+"they may distribute the results of their work as well."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:577
 #, no-c-format
-msgid "The &debian; project, as a pragmatic concession to its users, does make some packages available that do not meet our criteria for being free. These packages are not part of the official distribution, however, and are only available from the <userinput>contrib</userinput> or <userinput>non-free</userinput> areas of &debian; mirrors or on third-party CD/DVD-ROMs; see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian FTP archives</quote>, for more information about the layout and contents of the archives."
+msgid ""
+"The &debian; project, as a pragmatic concession to its users, does make some "
+"packages available that do not meet our criteria for being free. These "
+"packages are not part of the official distribution, however, and are only "
+"available from the <userinput>contrib</userinput> or <userinput>non-free</"
+"userinput> areas of &debian; mirrors or on third-party CD/DVD-ROMs; see the "
+"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian "
+"FTP archives</quote>, for more information about the layout and contents of "
+"the archives."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:591
 #, no-c-format
-msgid "Many of the programs in the system are licensed under the <emphasis>GNU</emphasis> <emphasis>General Public License</emphasis>, often simply referred to as <quote>the GPL</quote>. The GPL requires you to make the <emphasis>source code</emphasis> of the programs available whenever you distribute a binary copy of the program; that provision of the license ensures that any user will be able to modify the software. Because of this provision, the source code<footnote> <para> For information on how to locate, unpack, and build binaries from &debian; source packages, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of the Debian Package Management System</quote>. </para> </footnote> for all such programs is available in the &debian; system."
+msgid ""
+"Many of the programs in the system are licensed under the <emphasis>GNU</"
+"emphasis> <emphasis>General Public License</emphasis>, often simply referred "
+"to as <quote>the GPL</quote>. The GPL requires you to make the "
+"<emphasis>source code</emphasis> of the programs available whenever you "
+"distribute a binary copy of the program; that provision of the license "
+"ensures that any user will be able to modify the software. Because of this "
+"provision, the source code<footnote> <para> For information on how to "
+"locate, unpack, and build binaries from &debian; source packages, see the "
+"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of "
+"the Debian Package Management System</quote>. </para> </footnote> for all "
+"such programs is available in the &debian; system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:610
 #, no-c-format
-msgid "There are several other forms of copyright statements and software licenses used on the programs in &debian;. You can find the copyrights and licenses for every package installed on your system by looking in the file <filename>/usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> once you've installed a package on your system."
+msgid ""
+"There are several other forms of copyright statements and software licenses "
+"used on the programs in &debian;. You can find the copyrights and licenses "
+"for every package installed on your system by looking in the file <filename>/"
+"usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> "
+"once you've installed a package on your system."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:620
 #, no-c-format
-msgid "For more information about licenses and how &debian; determines whether software is free enough to be included in the main distribution, see the <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>."
+msgid ""
+"For more information about licenses and how &debian; determines whether "
+"software is free enough to be included in the main distribution, see the "
+"<ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>."
 msgstr ""
 
 #. Tag: para
 #: welcome.xml:626
 #, no-c-format
-msgid "The most important legal notice is that this software comes with <emphasis>no warranties</emphasis>. The programmers who have created this software have done so for the benefit of the community. No guarantee is made as to the suitability of the software for any given purpose. However, since the software is free, you are empowered to modify that software to suit your needs &mdash; and to enjoy the benefits of the changes made by others who have extended the software in this way."
+msgid ""
+"The most important legal notice is that this software comes with "
+"<emphasis>no warranties</emphasis>. The programmers who have created this "
+"software have done so for the benefit of the community. No guarantee is made "
+"as to the suitability of the software for any given purpose. However, since "
+"the software is free, you are empowered to modify that software to suit your "
+"needs &mdash; and to enjoy the benefits of the changes made by others who "
+"have extended the software in this way."
 msgstr ""
-
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index fef4c4a2d..997aa861d 100644
--- a/po/pot/boot-installer.pot
+++ b/po/pot/boot-installer.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
@@ -45,19 +45,19 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -69,25 +69,25 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -216,7 +216,7 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398 boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -236,41 +236,41 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:355
 #, no-c-format
-msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+msgid "obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory stick</phrase> installation media as described in <xref linkend=\"official-cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
       "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
@@ -279,7 +279,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
       "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
@@ -290,37 +290,37 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
       "image=/boot/newinstall/vmlinuz\n"
@@ -329,19 +329,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
       "title  New Install\n"
@@ -351,13 +351,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
       "menuentry 'New Install' {\n"
@@ -370,133 +370,133 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid "It could be that your Network Interface Card provides TFTP boot functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
       "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
@@ -513,25 +513,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
       "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
@@ -540,259 +540,259 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
       "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
@@ -805,13 +805,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
       "# cd /var/lib/tftp\n"
@@ -823,37 +823,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
       "After entering the command monitor use <informalexample><screen>\n"
@@ -864,19 +864,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
       "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
@@ -885,79 +885,79 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
       "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
@@ -966,67 +966,67 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
       "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
@@ -1037,31 +1037,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1070,25 +1070,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
       "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
@@ -1101,703 +1101,703 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
 msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
 msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -1806,127 +1806,127 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
       "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
@@ -1936,7 +1936,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -1949,19 +1949,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
       "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
@@ -1974,13 +1974,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
       "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
@@ -1989,7 +1989,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2002,151 +2002,151 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
 msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
       "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
@@ -2156,85 +2156,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
       "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index 596946c2b..d98faeb1a 100644
--- a/po/pot/install-methods.pot
+++ b/po/pot/install-methods.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
@@ -35,203 +35,203 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; for some desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
 msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
 msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
 msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
       "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
@@ -240,187 +240,187 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
       "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -431,13 +431,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
       "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
@@ -445,91 +445,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
 msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
       "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
@@ -540,13 +540,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
       "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
@@ -555,19 +555,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
       "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
@@ -577,19 +577,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
 msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
       "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
@@ -598,13 +598,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
       "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
@@ -617,37 +617,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
       "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
@@ -665,259 +665,259 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
       "option domain-name \"example.com\";\n"
@@ -942,25 +942,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
       "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
@@ -995,19 +995,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
       "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
@@ -1024,43 +1024,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
       "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
@@ -1071,49 +1071,49 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
       "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
@@ -1122,55 +1122,55 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
diff --git a/po/pt/boot-installer.po b/po/pt/boot-installer.po
index bddf3eea8..9ce9b68ec 100644
--- a/po/pt/boot-installer.po
+++ b/po/pt/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-10-27 13:46+0100\n"
 "Last-Translator: Miguel Figueiredo <elmig@debianpt.org>\n"
 "Language-Team: Portuguese <traduz@debianpt.org>\n"
@@ -65,8 +65,8 @@ msgid "Booting from TFTP"
 msgstr "Arrancar de TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -76,8 +76,8 @@ msgstr ""
 "servidor de arranque de rede TFTP (DHCP, RARP ou BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -87,8 +87,8 @@ msgstr ""
 "RBOOT em vez de um servidor BOOTP."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -104,8 +104,8 @@ msgid "Booting from CD-ROM"
 msgstr "Arrancar a partir de CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -122,8 +122,8 @@ msgstr ""
 "proceda para o próximo capítulo."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -139,8 +139,8 @@ msgstr ""
 "para instalar e kernels alternativos que poderão funcionar consigo."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -157,8 +157,8 @@ msgstr ""
 "CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -403,8 +403,8 @@ msgid "The installer will now start as usual."
 msgstr "O instalador irá iniciar como normalmente."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Arrancar a partir de CD-ROM"
@@ -423,17 +423,23 @@ msgstr "A tentar iniciar o instalador a partir do Windows, você pode"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "Obtenha o mídia de instalação para CD-ROM/DVD-ROM ou para pen de memória USB "
 "conforme é descrito em <xref linkend=\"official-cdrom\"/> e em <xref linkend="
 "\"boot-usb-files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -443,7 +449,7 @@ msgstr ""
 "&debian; como tools/win32-loader/stable/win32-loader.exe,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -459,7 +465,7 @@ msgstr ""
 "exe</command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -471,13 +477,13 @@ msgstr ""
 "&debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "A arrancar a partir do DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -487,7 +493,7 @@ msgstr ""
 "arrancar a partir de um disco de recuperação ou de diagnóstico."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -505,7 +511,7 @@ msgstr ""
 ">, e altere o leitor actual se necessário."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -527,7 +533,7 @@ msgstr ""
 "command>. O kernel irá carregar e lançar o sistema de instalação."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -536,7 +542,7 @@ msgstr ""
 "<command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -547,7 +553,7 @@ msgstr ""
 "linkend=\"boot-drive-files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -565,7 +571,7 @@ msgstr ""
 "do qual o instalador arranca, embora deva fazer isto com cuidado."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -584,7 +590,7 @@ msgstr ""
 "rede."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -603,7 +609,7 @@ msgstr ""
 "etc/lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -615,7 +621,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -631,7 +637,7 @@ msgstr ""
 "<userinput>lilo</userinput> e reinicie."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -648,7 +654,7 @@ msgstr ""
 "sistema):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -662,7 +668,7 @@ msgstr ""
 "initrd\t/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -675,7 +681,7 @@ msgstr ""
 "com o exemplo:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -695,7 +701,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -705,13 +711,13 @@ msgstr ""
 "ou o <command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Arrancar a partir de 'pen' USB"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
 "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -730,13 +736,13 @@ msgstr ""
 "opcionais, ou carregar em &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Arrancar a partir de Disquetes"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -747,7 +753,7 @@ msgstr ""
 ">."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -758,7 +764,7 @@ msgstr ""
 "normalmente, e de seguida ligue-o outra vez."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -778,7 +784,7 @@ msgstr ""
 "arranque."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -795,7 +801,7 @@ msgstr ""
 "hard reboot quando arrancar."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -805,7 +811,7 @@ msgstr ""
 "arranque e acaba com a prompt <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -822,7 +828,7 @@ msgstr ""
 "processo de arranque pode ser encontrada na <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -836,26 +842,26 @@ msgstr ""
 "command> é lançado automaticamente."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Arrancar com TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Existem várias maneiras fazer um arranque TFTP em i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "NIC ou Motherboards que suportam PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -870,13 +876,13 @@ msgstr ""
 "através da rede."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "NIC (placa de rede) com Network BootROM"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -886,7 +892,7 @@ msgstr ""
 "arranque por TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -896,13 +902,13 @@ msgstr ""
 "Por favor, refira-se a este documento."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -913,13 +919,13 @@ msgstr ""
 "TFTPboot."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Um Ecrã de Arranque"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -956,7 +962,7 @@ msgstr ""
 "número de opções."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -972,7 +978,7 @@ msgstr ""
 "arrancar o instalador."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -984,7 +990,7 @@ msgstr ""
 "para instalações automatizadas."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1003,7 +1009,7 @@ msgstr ""
 "ecrã de arranque e desfazer quaisquer alterações que tenha feito."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
 "Choosing the <quote>Help</quote> entry will result in the first help screen "
@@ -1038,7 +1044,7 @@ msgstr ""
 "fb=false</userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1057,7 +1063,7 @@ msgstr ""
 "utilizar."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1078,7 +1084,7 @@ msgstr ""
 "Remote Assistant</quote> (IRA) da HP."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1099,13 +1105,13 @@ msgstr ""
 "comandos de arranque, conforme é descrito no texto de ajuda."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Conteúdo do CD"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1129,7 +1135,7 @@ msgstr ""
 "variedade de pacotes sem necessitar de aceder à rede."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1155,7 +1161,7 @@ msgstr ""
 "do simples MBR ou do bloco de arranque em sistemas mais convencionais."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1171,7 +1177,7 @@ msgstr ""
 "necessários são lidos a partir da shell EFI descrita em baixo."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1194,7 +1200,7 @@ msgstr ""
 "presente antes de autorizar a continuação da instalação."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1218,13 +1224,13 @@ msgstr ""
 "segunda opção."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "IMPORTANTE"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1244,14 +1250,14 @@ msgstr ""
 "<command>exit</command> na prompt da shell."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 "Opção 1: Arrancar a partir do Menu de Manutenção das Opções de Arranque"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1263,7 +1269,7 @@ msgstr ""
 "inicialização."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1274,7 +1280,7 @@ msgstr ""
 "mostrar um novo menu."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1293,7 +1299,7 @@ msgstr ""
 "controlador deverá ser a mesma."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1312,7 +1318,7 @@ msgstr ""
 "que proceda para o próximo passo (adicional)."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1328,7 +1334,7 @@ msgstr ""
 "command>. Isto irá iniciar a sequência de arranque."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1340,13 +1346,13 @@ msgstr ""
 "Continue com a selecção do kernel e opções de arranque."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Opção 2: Arrancar a partir de uma Shell EFI"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1360,7 +1366,7 @@ msgstr ""
 "com as seguintes etapas:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1372,7 +1378,7 @@ msgstr ""
 "sistema."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1395,7 +1401,7 @@ msgstr ""
 "alguns segundos extra enquanto inicializa a drive de CD."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1409,7 +1415,7 @@ msgstr ""
 "<filename>fs<replaceable>n</replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1424,7 +1430,7 @@ msgstr ""
 "comandos."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1434,7 +1440,7 @@ msgstr ""
 "Isto irá iniciar a sequência de arranque."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1450,13 +1456,13 @@ msgstr ""
 "Continue para seleccionar o kernel e as opções de arranque."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Instalar utilizando uma Consola Série"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1477,7 +1483,7 @@ msgstr ""
 "ttyS0 são pré-configuradas."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1491,7 +1497,7 @@ msgstr ""
 "command> na shell EFI."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1508,7 +1514,7 @@ msgstr ""
 "</classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1527,7 +1533,7 @@ msgstr ""
 "Modo Texto."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1541,13 +1547,13 @@ msgstr ""
 "instalação."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Escolher o Kernel e Opções de Arranque"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1568,7 +1574,7 @@ msgstr ""
 "comandos."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1592,7 +1598,7 @@ msgstr ""
 "iniciar a instalação:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1602,7 +1608,7 @@ msgstr ""
 "suas necessidades com as teclas com as setas."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1615,7 +1621,7 @@ msgstr ""
 "série)."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1627,7 +1633,7 @@ msgstr ""
 "primeiro ecrã do Instalador &debian;."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1637,7 +1643,7 @@ msgstr ""
 "irá configurar o idioma, rede, e partições de disco."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1657,7 +1663,7 @@ msgstr ""
 "carregados a partir da rede em vez do leitor de CD."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1672,13 +1678,13 @@ msgstr ""
 "para permitir carregar através da rede."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Configurar o Servidor"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1702,7 +1708,7 @@ msgstr ""
 "command> a correr no cliente."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1719,7 +1725,7 @@ msgstr ""
 "IA-64."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1737,7 +1743,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1759,13 +1765,13 @@ msgstr ""
 "a documentação fornecida pelo pacote <classname>elilo</classname>."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Configurar o Cliente"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1796,7 +1802,7 @@ msgstr ""
 "<filename>elilo.efi</filename> via TFTP a partir do servidor."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1812,13 +1818,13 @@ msgstr ""
 "instalar a ele próprio a partir da rede, e irá iniciar o Instalador &debian;."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Iniciar de TFTP em SGI"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1840,13 +1846,13 @@ msgstr ""
 "</screen></informalexample>."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Parâmetros de Arranque"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1856,7 +1862,7 @@ msgstr ""
 "<command>bootp():</command>."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1874,19 +1880,19 @@ msgstr ""
 "passados via <command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Iniciar o Cobalt TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1904,7 +1910,7 @@ msgstr ""
 "estão os dois seguintes métodos de instalação:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1919,7 +1925,7 @@ msgstr ""
 "IP). Quando ligar à máquina com um cliente SSH pode iniciar a instalação."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1931,7 +1937,7 @@ msgstr ""
 "instalação."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1944,13 +1950,13 @@ msgstr ""
 "replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Limitações de s390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1960,7 +1966,7 @@ msgstr ""
 "rede funcional e uma sessão de ssh."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1974,13 +1980,13 @@ msgstr ""
 "instalação standard."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Parâmetros de Arranque de s390"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1993,7 +1999,7 @@ msgstr ""
 "imagens de instalação."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2011,7 +2017,7 @@ msgstr ""
 "para arrancar a partir de CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2029,13 +2035,13 @@ msgstr ""
 "do tipo de leitor interno de CD/DVD predefinido de fábrica."
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2052,7 +2058,7 @@ msgstr ""
 "ficheiros necessários do CD."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2064,19 +2070,19 @@ msgstr ""
 "aparecer a prompt do SmartFirmware digite"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Arrancar a partir de Disco Rígido"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2086,7 +2092,7 @@ msgstr ""
 "para alguns sistemas é a única forma de instalação suportada."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2098,13 +2104,13 @@ msgstr ""
 "conforme é descrito em <xref linkend=\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Arrancar OldWorld PowerMacs a partir de MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2124,13 +2130,13 @@ msgstr ""
 "<guibutton>Linux</guibutton> para desligar o MacOS e o instalador iniciar."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Arrancar Macs NewWorld a partir de OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2173,13 +2179,13 @@ msgstr ""
 "poderá tentar utilizá-lo se <userinput>install</userinput> não funcionar."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Arrancar a partir de uma 'pen' USB"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2187,7 +2193,7 @@ msgstr ""
 "iniciar de USB."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2202,7 +2208,7 @@ msgstr ""
 "Veja <xref linkend=\"invoking-openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2225,7 +2231,7 @@ msgstr ""
 "pci@f2000000/usb@1b,1/hub@1/disk@1</filename> funcionam."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2251,7 +2257,7 @@ msgstr ""
 "abençoada com <command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2263,7 +2269,7 @@ msgstr ""
 "arranque. Aqui pode inserir parâmetros de arranque opcionais."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2276,13 +2282,13 @@ msgstr ""
 "linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr "Actualmente, sistemas PReP e NewWorld PowerMac suportam netbooting."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2315,7 +2321,7 @@ msgstr ""
 "descrição da sintaxe e as opções disponíveis."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2329,7 +2335,7 @@ msgstr ""
 "suportadas para arranque."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2341,7 +2347,7 @@ msgstr ""
 "de o voltar a ligar."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2356,7 +2362,7 @@ msgstr ""
 "rígido pelas quais possa arrancar."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2369,13 +2375,13 @@ msgstr ""
 "memória."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC parâmetros de arranque"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2391,7 +2397,7 @@ msgstr ""
 "isto altera para <userinput>video=aty128fb:vmode:6</userinput> ."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2411,7 +2417,7 @@ msgstr ""
 "&d-i; no final do comando <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2423,13 +2429,13 @@ msgstr ""
 "dispositivo SCSI no ID 6 (ou o master secundário para sistemas IDE)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "Mensagens IDPROM"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2445,13 +2451,13 @@ msgstr ""
 "informação."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Acessibilidade"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2481,13 +2487,13 @@ msgstr ""
 "teclado QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "Ecrãs Braille USB"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2509,13 +2515,13 @@ msgstr ""
 "\"&url-brltty-driver-help;\">website <classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Ecrãs Braille Série"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2556,13 +2562,13 @@ msgstr ""
 "<classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "Software para Sintetizar Voz"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2577,13 +2583,13 @@ msgstr ""
 "no idioma escolhido (se disponível em <classname>espeak</classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Hardware para Sintetizar Voz"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2595,7 +2601,7 @@ msgstr ""
 "entrada <quote>Instalador Gráfico</quote> no menu de arranque."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2618,13 +2624,13 @@ msgstr ""
 "sintetizar voz será automaticamente instalado no sistema alvo."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Dispositivos em Placa"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2641,7 +2647,7 @@ msgstr ""
 "idiomas disponíveis."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2652,13 +2658,13 @@ msgstr ""
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Tema de Alto Contraste"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2670,13 +2676,13 @@ msgstr ""
 "parâmetro de arranque <userinput>theme=dark</userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Preseeding"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2687,7 +2693,7 @@ msgstr ""
 "preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2701,7 +2707,7 @@ msgstr ""
 "Contudo, em alguns casos terá de ajudar o kernel um pouco."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2715,7 +2721,7 @@ msgstr ""
 "e procurar por parâmetros especiais que informam o sistema do seu hardware."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2732,7 +2738,7 @@ msgstr ""
 "troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
 msgid ""
 "If you are booting with a serial console, generally the kernel will "
@@ -2752,7 +2758,7 @@ msgstr ""
 "algo como <filename>ttyS0</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
 msgid ""
 "In order to ensure the terminal type used by the installer matches your "
@@ -2781,7 +2787,7 @@ msgstr ""
 "<literal>vt102</literal>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2795,13 +2801,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Parâmetros de instalação &debian;"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2816,7 +2822,7 @@ msgstr ""
 "poderão ser úteis."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2832,20 +2838,20 @@ msgstr ""
 "Os exemplos neste manual normalmente também irão utilizar a forma abreviada."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (prioridade)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 "Este parâmetro ajusta a prioridade mínima das mensagens a serem mostradas. "
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2859,7 +2865,7 @@ msgstr ""
 "encontrados problemas, o instalador ajusta a prioridade conforme necessário."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2879,13 +2885,13 @@ msgstr ""
 "críticas e tentará optar pelas opções correctas sem grande confusão."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2920,13 +2926,13 @@ msgstr ""
 "utiliza o frontend <userinput>gtk</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2941,49 +2947,49 @@ msgstr ""
 "arranque.)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Isto é por omissão"
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Mais detalhes que o habitual"
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Muita informação de eliminação de erros."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2993,13 +2999,13 @@ msgstr ""
 "permitir um debugging detalhado. Saia para a shell para continuar o arranque."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3011,7 +3017,7 @@ msgstr ""
 "floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3022,19 +3028,19 @@ msgstr ""
 "para apenas olhar para um dispositivo."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3046,13 +3052,13 @@ msgstr ""
 "especificado, o porto é o predefinido para o porto standard do syslog 514."
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3064,13 +3070,13 @@ msgstr ""
 "valores possíveis são 1 e 2. Veja também <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3080,13 +3086,13 @@ msgstr ""
 "para instalações à distância em que a segurança física é limitada."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3105,13 +3111,13 @@ msgstr ""
 "instalação."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Tais problemas foram reportados em hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3130,13 +3136,13 @@ msgstr ""
 "<userinput>fb=true</userinput>, abreviado."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3152,13 +3158,13 @@ msgstr ""
 "com <userinput>theme=<replaceable>dark</replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3172,7 +3178,7 @@ msgstr ""
 "caso do probe DHCP falhar."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3186,13 +3192,13 @@ msgstr ""
 "por DHCP e que a informação seja inserida manualmente."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3203,13 +3209,13 @@ msgstr ""
 "conhecidos por este mau comportamento."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3224,13 +3230,13 @@ msgstr ""
 "do Instalador &debian;</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3241,13 +3247,13 @@ msgstr ""
 "install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3257,13 +3263,13 @@ msgstr ""
 "automatização da instalação. Veja a <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3280,13 +3286,13 @@ msgstr ""
 "\"preseed-seenflag\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3299,13 +3305,13 @@ msgstr ""
 "auto\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3318,13 +3324,13 @@ msgstr ""
 "isto."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3343,7 +3349,7 @@ msgstr ""
 "recarregar automaticamente."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3355,13 +3361,13 @@ msgstr ""
 "automaticamente a partir da drive optical após a instalação inicial."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3375,7 +3381,7 @@ msgstr ""
 "instalado. Veja também <xref linkend=\"di-install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3391,13 +3397,13 @@ msgstr ""
 "apenas deve ser utilizada por utilizadores muito experientes."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3411,13 +3417,13 @@ msgstr ""
 "e não recomendado.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3429,13 +3435,13 @@ msgstr ""
 "ramdisk não pode ser completamente carregado. O valor é em kB."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3445,13 +3451,13 @@ msgstr ""
 "em vez de efectuar uma instalação normal. Veja a <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Utilizar parâmetros de arranque para responder a questões"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3466,25 +3472,25 @@ msgstr ""
 "exemplos específicos estão listados abaixo."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3494,7 +3500,7 @@ msgstr ""
 "instalação e para o sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3513,7 +3519,7 @@ msgstr ""
 "podem ser feitas todas as combinações de idioma, países e locales."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3529,13 +3535,13 @@ msgstr ""
 "Exemplo: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3552,7 +3558,7 @@ msgstr ""
 "\"/>)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3562,13 +3568,13 @@ msgstr ""
 "configuração de rede estática."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3586,13 +3592,13 @@ msgstr ""
 "tem de introduzir manualmente o nome da máquina."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3604,13 +3610,13 @@ msgstr ""
 "literal>. Veja <xref linkend=\"pkgsel\"/> para informações adicionais."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Passagem de argumentos a módulos do kernel"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3635,7 +3641,7 @@ msgstr ""
 "propagarão automaticamente na configuração para o sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3650,7 +3656,7 @@ msgstr ""
 "parâmetros."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3672,19 +3678,19 @@ msgstr ""
 "você deve passar:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Colocar módulos do kernel na 'lista negra'"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3703,7 +3709,7 @@ msgstr ""
 "errado for carregado primeiro."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3719,7 +3725,7 @@ msgstr ""
 "quer para o sistema instalado."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3733,19 +3739,19 @@ msgstr ""
 "durante as fases de detecção de hardware."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Diagnosticar Problemas no Processo de Instalação"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Fiabilidade do CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3760,7 +3766,7 @@ msgstr ""
 "partir deste."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3772,13 +3778,13 @@ msgstr ""
 "acerca de como lidar com eles. O resto é consigo."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Existem duas coisas muito simples que deve tentar primeiro."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3788,7 +3794,7 @@ msgstr ""
 "está sujo."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid ""
 "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3802,7 +3808,7 @@ msgstr ""
 "com DMA em leitores de CD-ROM muito antigos se resolvem desta forma."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3814,7 +3820,7 @@ msgstr ""
 "quer para DVD, mas utilizaremos o termo CD-ROM pela simplicidade."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3824,13 +3830,13 @@ msgstr ""
 "outros métodos de instalação que estão disponíveis."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Problemas usuais"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3840,7 +3846,7 @@ msgstr ""
 "que foram gravados a altas velocidades com um gravador de CDs moderno."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid ""
 "Some very old CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3850,19 +3856,19 @@ msgstr ""
 "<quote>acesso directo à memória</quote> (DMA) estiver activo para eles."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Como investigar e talvez resolver problemas"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr "Se o CD-ROM falhar o arranque, tente as sugestões listadas abaixo."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid ""
 "Check that your BIOS actually supports booting from CD-ROM (only an issue "
@@ -3873,7 +3879,7 @@ msgstr ""
 "ROM está activado na BIOS."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3899,7 +3905,7 @@ msgstr ""
 "tamanho da imagem para ler o número de bytes correcto a partir do CD-ROM."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3921,7 +3927,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3943,7 +3949,7 @@ msgstr ""
 "(VT2) e activar lá a shell."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3955,7 +3961,7 @@ msgstr ""
 "erro específica. Depois disso, veja a saída de <command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3986,7 +3992,7 @@ msgstr ""
 "<command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3998,7 +4004,7 @@ msgstr ""
 "filename>. Deve também existir um <filename>/dev/cdrom</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4015,7 +4021,7 @@ msgstr ""
 "este comando."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4041,7 +4047,7 @@ msgstr ""
 "dispositivo que corresponde ao seu leitor de CD-ROMs."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4055,13 +4061,13 @@ msgstr ""
 "verificar se o CD-ROM pode ser lido com fiabilidade."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Disquetes de confiança"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4071,7 +4077,7 @@ msgstr ""
 "&debian; parece ser a confiança na duração das disquetes."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4089,7 +4095,7 @@ msgstr ""
 "maioria dos casos são indicadas por muitas mensagens de erros I/O."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4107,7 +4113,7 @@ msgstr ""
 "diferente."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4119,7 +4125,7 @@ msgstr ""
 "bem com a terceira disquete."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4131,7 +4137,7 @@ msgstr ""
 "correctamente o download das imagens verificando o seu md5sum."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4144,13 +4150,13 @@ msgstr ""
 "disquetes."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Configuração de arranque"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4164,7 +4170,7 @@ msgstr ""
 "como foi visto na <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4176,7 +4182,7 @@ msgstr ""
 "\"loading-firmware\"/>)."
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4195,37 +4201,37 @@ msgstr ""
 "(e.g., um live CD)."
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Problemas comuns de Instalação em &arch-title;"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4235,7 +4241,7 @@ msgstr ""
 "evitados ao passar alguns parâmetros de arranque ao instalador."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4256,13 +4262,13 @@ msgstr ""
 "<xref linkend=\"boot-parms\"/> para mais detalhes."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Bloqueio do Sistema Durante a Fase de Configuração de PCMCIA"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
 msgid ""
 "Some very old laptop models produced by Dell are known to crash when PCMCIA "
@@ -4283,7 +4289,7 @@ msgstr ""
 "recursos que causa o conflito."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4305,20 +4311,20 @@ msgstr ""
 "introduz estes valores no instalador."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 "Existem alguns problemas de instalação usuais que vale a pena mencionar."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "saída de vídeo direccionada incorrectamente"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4345,7 +4351,7 @@ msgstr ""
 "<userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4359,13 +4365,13 @@ msgstr ""
 "<filename>/etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Falha ao Arrancar ou Instalar a partir de CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4377,7 +4383,7 @@ msgstr ""
 "instalação. A maioria dos problemas foram relatados com sistemas SunBlade."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4385,13 +4391,13 @@ msgstr ""
 "instalador."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Interpretar as Mensagens de Arranque do Kernel"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4430,13 +4436,13 @@ msgstr ""
 "<xref linkend=\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Relatar Problemas de Instalação"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4457,7 +4463,7 @@ msgstr ""
 "ao relatório de erros."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4470,13 +4476,13 @@ msgstr ""
 "instalado."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Submeter Relatórios de Instalação"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4490,7 +4496,7 @@ msgstr ""
 "possível no maior número de configurações de hardware."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4503,7 +4509,7 @@ msgstr ""
 "público."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4523,7 +4529,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/pt/hardware.po b/po/pt/hardware.po
index 64b9f2f12..2a089d56a 100644
--- a/po/pt/hardware.po
+++ b/po/pt/hardware.po
@@ -129,7 +129,6 @@ msgstr "i386"
 #. Tag: entry
 #: hardware.xml:67 hardware.xml:197
 #, no-c-format
-#| msgid "AMD64 &amp; Intel EM64T"
 msgid "AMD64 &amp; Intel 64"
 msgstr "AMD64 &amp; Intel 64"
 
@@ -482,12 +481,6 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-#| msgid ""
-#| "The &arch-title; architecture only supports Intel Itanium processors and "
-#| "not the much more common 64-bit processors from the EM64T family "
-#| "(including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems "
-#| "are supported by the <emphasis>amd64</emphasis> architecture or, if you "
-#| "prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
 msgid ""
 "The &arch-title; architecture only supports Intel Itanium processors and not "
 "the much more common 64-bit processors from the Intel 64 family (including e."
@@ -496,9 +489,9 @@ msgid ""
 "userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 "A arquitectura &arch-title; suporta apenas processadores Intel Itanium e não "
-"os processadores muito mais vulgares de 64-bit da família 64 (incluindo, "
-"p.e., o Pentium&nbsp;D e o Core2&nbsp;Duo). Esses sistemas são suportados "
-"pela arquitectura <emphasis>amd64</emphasis> ou, se preferir 32-bit, a "
+"os processadores muito mais vulgares de 64-bit da família 64 (incluindo, p."
+"e., o Pentium&nbsp;D e o Core2&nbsp;Duo). Esses sistemas são suportados pela "
+"arquitectura <emphasis>amd64</emphasis> ou, se preferir 32-bit, a "
 "arquitectura <emphasis>i386</emphasis>."
 
 #. Tag: para
@@ -535,7 +528,6 @@ msgstr "CPUs Suportados"
 #. Tag: para
 #: hardware.xml:246
 #, no-c-format
-#| msgid "Both AMD64 and Intel EM64T processors are supported."
 msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr "São suportados ambos os processadores AMD64 e Intel 64."
 
@@ -771,18 +763,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-#| msgid ""
-#| "If your system has a 64-bit processor from the AMD64 or Intel EM64T "
-#| "families, you will probably want to use the installer for the amd64 "
-#| "architecture instead of the installer for the (32-bit) i386 architecture."
 msgid ""
 "If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
 "you will probably want to use the installer for the amd64 architecture "
 "instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
-"Se o seu sistema tiver um processador 64-bit das famílias AMD64 ou Intel "
-"64, provavelmente irá desejar utilizar o instalador para a arquitectura "
-"amd64 em vez do instalador para a arquitectura i386 (32-bit)."
+"Se o seu sistema tiver um processador 64-bit das famílias AMD64 ou Intel 64, "
+"provavelmente irá desejar utilizar o instalador para a arquitectura amd64 em "
+"vez do instalador para a arquitectura i386 (32-bit)."
 
 #. Tag: title
 #: hardware.xml:440
diff --git a/po/pt/install-methods.po b/po/pt/install-methods.po
index 3bd288441..0fb644732 100644
--- a/po/pt/install-methods.po
+++ b/po/pt/install-methods.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods.po\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-10-26 20:27+0100\n"
 "Last-Translator: Miguel Figueiredo <elmig@debianpt.org>\n"
 "Language-Team: Portuguese <kde-i18n-doc@kde.org>\n"
@@ -64,14 +64,20 @@ msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "As CDs have a rather limited capacity by today's standards, not all "
+#| "graphical desktop environments are installable with only the first CD; "
+#| "only XFCE (which is the default desktop environment installed by &debian-"
+#| "gnu; &release;) completely fits on the first CD. For all other desktop "
+#| "environments a CD installation requires either network connectivity "
+#| "during the installation to download the remaining files or additional CDs."
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 "Como os CDs têm uma capacidade bastante limitada pelos standards actuais, "
 "nem todos os ambientes de trabalho gráficos são instaláveis apenas como o "
@@ -82,7 +88,7 @@ msgstr ""
 "adicionais."
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
 msgid ""
 "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
@@ -114,7 +120,7 @@ msgstr ""
 "CD."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -124,7 +130,7 @@ msgstr ""
 "outros ficheiros que precisa."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -144,13 +150,13 @@ msgstr ""
 "instalador."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Download dos Ficheiros a partir dos Mirrors &debian;"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -160,7 +166,7 @@ msgstr ""
 "a <ulink url=\"&url-debian-mirrors;\">lista de mirrors Debian</ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -171,13 +177,13 @@ msgstr ""
 "emphasis>, e não em modo de texto ou no modo automático."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Onde Encontrar Imagens de Instalação"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -193,13 +199,13 @@ msgstr ""
 "lista cada imagem e o seu propósito."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Ficheiros de Instalação para Thecus N2100"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -214,13 +220,13 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Ficheiros de Instalação do GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -232,13 +238,13 @@ msgstr ""
 "&glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Ficheiros de Instalação do Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -250,13 +256,13 @@ msgstr ""
 "de &kuroboxpro-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Ficheiros de Instalação para HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -272,13 +278,13 @@ msgstr ""
 "obtida a partir de &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Ficheiros de Instalação para QNAP Turbo"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -292,13 +298,13 @@ msgstr ""
 "TS-41x a partir de &qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Ficheiros de Instalação para Computadores Plug OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
 msgid ""
 "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
@@ -310,13 +316,13 @@ msgstr ""
 "Boot. Pode obter esses ficheiros a partir de &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr "Ficheiros de Instalação de NAS LaCie"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
 msgid ""
 "The installation files for LaCie NASes (Network Space v2, Network Space Max "
@@ -330,13 +336,13 @@ msgstr ""
 "partir de &lacie-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Criar uma tape IPL"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -359,13 +365,13 @@ msgstr ""
 "linkend=\"where-files\"/>,"
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Criar Disquetes a partir de Imagens de Disco"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -375,7 +381,7 @@ msgstr ""
 "iniciar o instalador em hardware que não arranca de CD ou por outros meios."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -385,7 +391,7 @@ msgstr ""
 "disquetes Mac."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -406,7 +412,7 @@ msgstr ""
 "a disquete."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -418,7 +424,7 @@ msgstr ""
 "disco em diferentes plataformas."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -434,7 +440,7 @@ msgstr ""
 "estar incluídas no CD/DVD.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -447,13 +453,13 @@ msgstr ""
 "danificadas."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Escrever Imagens de Disco a partir de um Sistema Linux ou Unix"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -490,7 +496,7 @@ msgstr ""
 "<command>eject</command>, veja a página do manual)</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -524,7 +530,7 @@ msgstr ""
 "sistemas, pergunte ao seu administrador de sistema. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -536,13 +542,13 @@ msgstr ""
 "de o instalar."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Escrever Imagens de Disco a partir de DOS, Windows, ou OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -552,7 +558,7 @@ msgstr ""
 "seguintes programas para copiar imagens para disquetes."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -567,7 +573,7 @@ msgstr ""
 "duplo-click a partir do Explorador do Windows."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -579,7 +585,7 @@ msgstr ""
 "descompactar diskio.dll no mesmo directório."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -589,13 +595,13 @@ msgstr ""
 "directório <filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Escrever Imagens de Disco a partir de MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -618,7 +624,7 @@ msgstr ""
 "continuar com a gravação da imagem para lá."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -633,13 +639,13 @@ msgstr ""
 "da imagem de disquetes com estes utilitários."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Escrever Imagens de Disco com <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -654,7 +660,7 @@ msgstr ""
 "mirror &debian;."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -664,7 +670,7 @@ msgstr ""
 "e utilize-o para abrir o ficheiro <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -676,7 +682,7 @@ msgstr ""
 "são sensíveis à capitalização."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -692,7 +698,7 @@ msgstr ""
 "blocos de arranque se a imagem for acidentalmente montada."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -704,7 +710,7 @@ msgstr ""
 "diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -721,13 +727,13 @@ msgstr ""
 "ejectada."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Escrever Imagens de Disco com <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -740,7 +746,7 @@ msgstr ""
 "<quote>Overwrite Sectors...</quote> do menu <userinput>Special</userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -749,7 +755,7 @@ msgstr ""
 "sector 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -758,7 +764,7 @@ msgstr ""
 "abertura de ficheiro."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -772,7 +778,7 @@ msgstr ""
 "a fora e tente com outra."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -784,13 +790,13 @@ msgstr ""
 "montá-la em MacOS, MacOS irá arruiná-la."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Preparar Ficheiros para iniciar a partir de USB Memory Stick"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -814,7 +820,7 @@ msgstr ""
 "sua 'pen', poderá ter de desligar o botão de protecção de escrita."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -828,13 +834,13 @@ msgstr ""
 "toda a informação no, por exemplo, disco rígido seja perdida."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "Preparar uma pen USB utilizando uma imagem híbrida de CD ou DVD"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -848,7 +854,7 @@ msgstr ""
 "<xref linkend=\"official-cdrom\"/> para obter a imagem de CD ou de DVD."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -862,7 +868,7 @@ msgstr ""
 "linkend=\"where-files\"/>)."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -881,7 +887,7 @@ msgstr ""
 "descompactar o firmware para lá."
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -897,7 +903,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -912,7 +918,7 @@ msgstr ""
 "desmontada:"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -924,7 +930,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -937,13 +943,13 @@ msgstr ""
 "especializadas."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "Copiar manualmente os ficheiros para a pen USB"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -957,7 +963,7 @@ msgstr ""
 "mais reduzidas se seguir a <xref linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -973,7 +979,7 @@ msgstr ""
 "<classname>yaboot</classname> e o seu ficheiro de configuração.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -989,7 +995,7 @@ msgstr ""
 "vez a quiser utilizar para um propósito diferente."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
@@ -997,13 +1003,13 @@ msgstr ""
 "'pen' USB:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1015,13 +1021,13 @@ msgstr ""
 "imagem directamente para lá:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
 msgid ""
 "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1042,13 +1048,13 @@ msgstr ""
 "Desmonte a pen (<userinput>umount /mnt</userinput>) e já está."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Copiar ficheiros manualmente para a pen USB &mdash; a forma flexível"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1064,13 +1070,13 @@ msgstr ""
 "completa de CD para lá."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Particionar a 'pen' USB"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1080,7 +1086,7 @@ msgstr ""
 "partição, em vez de todo o dispositivo."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
 "Since most USB sticks come pre-configured with a single FAT16 partition, you "
@@ -1115,7 +1121,7 @@ msgstr ""
 "no pacote &debian; <classname>dosfstools</classname>."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1135,7 +1141,7 @@ msgstr ""
 "arranque."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1159,13 +1165,13 @@ msgstr ""
 "contém o código do gestor de arranque."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Acrescentar a imagem do instalador"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1191,7 +1197,7 @@ msgstr ""
 "DOS (8.3)."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
 "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1217,7 +1223,7 @@ msgstr ""
 "outros parâmetros conforme for desejado."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1227,7 +1233,7 @@ msgstr ""
 "acrescente uma linha <userinput>prompt 1</userinput>."
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
 msgid ""
 "If you used an <filename>hd-media</filename> image, you should now copy the "
@@ -1247,7 +1253,7 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1277,7 +1283,7 @@ msgstr ""
 "&debian; <classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1294,7 +1300,7 @@ msgstr ""
 "para fazer alterações à configuração do gestor de arranque."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1331,7 +1337,7 @@ msgstr ""
 "ser preparada utilizando os utilitários Unix comuns."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1342,31 +1348,31 @@ msgstr ""
 "instalador:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (binário do kernel)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (imagem ramdisk inicial)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (ficheiro de configuração yaboot)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (mensagem opcional de arranque)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1402,13 +1408,13 @@ msgstr ""
 "está a iniciar."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Preparar Ficheiros para Arrancar a Partir de Disco Rígido."
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1420,7 +1426,7 @@ msgstr ""
 "operativo ou invocando directamente o gestor de arranque da BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1434,7 +1440,7 @@ msgstr ""
 "imagens de disquetes que não são fiáveis."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1457,7 +1463,7 @@ msgstr ""
 "ficheiros de instalação dos quais fez download."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1469,7 +1475,7 @@ msgstr ""
 "<quote>OldWorld</quote>."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1479,7 +1485,7 @@ msgstr ""
 "<command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1490,7 +1496,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1502,7 +1508,7 @@ msgstr ""
 "pode ser utilizado pelo kernel como sistema de ficheiros root."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1515,19 +1521,19 @@ msgstr ""
 "newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (binário kernel)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (imagem ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1537,13 +1543,13 @@ msgstr ""
 "linkend=\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr "Arrancar o Instalador de disco rígido com o <command>loadlin</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1553,7 +1559,7 @@ msgstr ""
 "a partir do DOS utilizando o <command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1563,7 +1569,7 @@ msgstr ""
 "\\</filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1571,19 +1577,19 @@ msgstr ""
 "<filename>/&x86-install-dir;</filename> (binário do kernel e imagem ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (ferramenta loadlin)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Instalador para Disco Rígido para Macs OldWorld"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1606,7 +1612,7 @@ msgstr ""
 "modelo."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1634,13 +1640,13 @@ msgstr ""
 "<filename>Linux Kernels</filename> no directório activo System Folder."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Arrancar o Instalador a partir do Disco Rígido em Macs NewWorld"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1661,7 +1667,7 @@ msgstr ""
 "é suportado e não deve ser utilizado em PowerMacs NewWorld."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1675,31 +1681,31 @@ msgstr ""
 "cada ficheiro para o ícone do disco rígido)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1715,20 +1721,20 @@ msgstr ""
 "Firmware quando iniciar o instalador."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 "Para iniciar o instalador, prossiga para a <xref linkend=\"boot-newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Preparar Ficheiros para Arrancar Através da Rede por TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1745,7 +1751,7 @@ msgstr ""
 "especifica."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1757,7 +1763,7 @@ msgstr ""
 "<phrase condition=\"supports-bootp\">, ou um servidor de BOOTP</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1778,7 +1784,7 @@ msgstr ""
 "apenas podem ser configurados via DHCP."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1790,7 +1796,7 @@ msgstr ""
 "capazes de utilizar BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1800,7 +1806,7 @@ msgstr ""
 "BOOTP. Está disponível um pacote <classname>rbootd</classname> em &debian;."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1815,7 +1821,7 @@ msgstr ""
 "5.x (a.k.a. Solaris), e GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1829,13 +1835,13 @@ msgstr ""
 "problemas. Uma boa alternativa é o <classname>atftpd</classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Configurar o servidor RARP"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1855,7 +1861,7 @@ msgstr ""
 "endereço show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1880,13 +1886,13 @@ msgstr ""
 "SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Configurar um servidor DHCP"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1900,7 +1906,7 @@ msgstr ""
 "dhcpd.conf</filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1944,7 +1950,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1962,7 +1968,7 @@ msgstr ""
 "obtido por TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1972,13 +1978,13 @@ msgstr ""
 "reinicie-o com <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Possibilitar o Arranque PXE na configuração DHCP"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2050,13 +2056,13 @@ msgstr ""
 "abaixo)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Configurar o servidor BOOTP"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2072,7 +2078,7 @@ msgstr ""
 "server</classname>."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2136,7 +2142,7 @@ msgstr ""
 "userinput> é o endereço MAC da máquina. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2160,13 +2166,13 @@ msgstr ""
 "command> com <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Disponibilizar o Servidor TFTP"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2176,7 +2182,7 @@ msgstr ""
 "<command>tftpd</command> está activo."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2192,7 +2198,7 @@ msgstr ""
 "pode ser alterado reconfigurando o pacote."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2211,7 +2217,7 @@ msgstr ""
 "configuração nesta secção."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2228,7 +2234,7 @@ msgstr ""
 "diagnosticar a causa dos erros."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2259,13 +2265,13 @@ msgstr ""
 "servidor TFTP de Linux utiliza."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Mover Imagens TFTP Para o Lugar"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2282,7 +2288,7 @@ msgstr ""
 "determinado pelo cliente TFTP, e não existem standards sólidos."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2298,13 +2304,13 @@ msgstr ""
 "partir do directório <filename>netboot/</filename>:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2321,7 +2327,7 @@ msgstr ""
 "para arrancar."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2338,13 +2344,13 @@ msgstr ""
 "do ficheiro para arrancar."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Arrancar SPARC TFTP"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2376,7 +2382,7 @@ msgstr ""
 "adicionar o nome da sub-arquitectura."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2390,7 +2396,7 @@ msgstr ""
 "nome da imagem que está a ser pedida."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2404,13 +2410,13 @@ msgstr ""
 "directório onde o servidor TFTP procura."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Arrancar por TFTP em SGI"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2424,13 +2430,13 @@ msgstr ""
 "<filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Instalação Automática"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2446,13 +2452,13 @@ msgstr ""
 "a <ulink url=\"http://fai-project.org\">Página do FAI</ulink>."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Instalação Automática Utilizando o Instalador &debian;"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2466,7 +2472,7 @@ msgstr ""
 "respostas às perguntas feitas durante o processo de instalação."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/ro/administrivia.po b/po/ro/administrivia.po
index 29c5f204a..164f2ad70 100644
--- a/po/ro/administrivia.po
+++ b/po/ro/administrivia.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,44 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:11
 #, no-c-format
-msgid "This manual was created for Sarge's debian-installer, based on the Woody installation manual for boot-floppies, which was based on earlier Debian installation manuals, and on the Progeny distribution manual which was released under GPL in 2003."
+msgid ""
+"This manual was created for Sarge's debian-installer, based on the Woody "
+"installation manual for boot-floppies, which was based on earlier Debian "
+"installation manuals, and on the Progeny distribution manual which was "
+"released under GPL in 2003."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:18
 #, no-c-format
-msgid "This document is written in DocBook XML. Output formats are generated by various programs using information from the <classname>docbook-xml</classname> and <classname>docbook-xsl</classname> packages."
+msgid ""
+"This document is written in DocBook XML. Output formats are generated by "
+"various programs using information from the <classname>docbook-xml</"
+"classname> and <classname>docbook-xsl</classname> packages."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:25
 #, no-c-format
-msgid "In order to increase the maintainability of this document, we use a number of XML features, such as entities and profiling attributes. These play a role akin to variables and conditionals in programming languages. The XML source to this document contains information for each different architecture &mdash; profiling attributes are used to isolate certain bits of text as architecture-specific."
+msgid ""
+"In order to increase the maintainability of this document, we use a number "
+"of XML features, such as entities and profiling attributes. These play a "
+"role akin to variables and conditionals in programming languages. The XML "
+"source to this document contains information for each different architecture "
+"&mdash; profiling attributes are used to isolate certain bits of text as "
+"architecture-specific."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:34
 #, no-c-format
-msgid "Translators can use this paragraph to acknowledge the people responsible for the translation of the manual. Translation teams are advised to just mention the coordinator and maybe major contributors and thank everybody else in a phrase like \"all translators and reviewers from the translation team for {your language} at {your l10n mailinglist}\". See build/lang-options/README on how to enable this paragraph. Its condition is \"about-langteam\"."
+msgid ""
+"Translators can use this paragraph to acknowledge the people responsible for "
+"the translation of the manual. Translation teams are advised to just mention "
+"the coordinator and maybe major contributors and thank everybody else in a "
+"phrase like \"all translators and reviewers from the translation team for "
+"{your language} at {your l10n mailinglist}\". See build/lang-options/README "
+"on how to enable this paragraph. Its condition is \"about-langteam\"."
 msgstr ""
 
 #. Tag: title
@@ -58,19 +78,46 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:52
 #, no-c-format
-msgid "If you have problems or suggestions regarding this document, you should probably submit them as a bug report against the package <classname>installation-guide</classname>. See the <classname>reportbug</classname> package or read the online documentation of the <ulink url=\"&url-bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could check the <ulink url=\"&url-bts;installation-guide\">open bugs against installation-guide</ulink> to see whether your problem has already been reported. If so, you can supply additional corroboration or helpful information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, where <replaceable>XXXX</replaceable> is the number for the already-reported bug."
+msgid ""
+"If you have problems or suggestions regarding this document, you should "
+"probably submit them as a bug report against the package "
+"<classname>installation-guide</classname>. See the <classname>reportbug</"
+"classname> package or read the online documentation of the <ulink url=\"&url-"
+"bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could "
+"check the <ulink url=\"&url-bts;installation-guide\">open bugs against "
+"installation-guide</ulink> to see whether your problem has already been "
+"reported. If so, you can supply additional corroboration or helpful "
+"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</"
+"email>, where <replaceable>XXXX</replaceable> is the number for the already-"
+"reported bug."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:68
 #, no-c-format
-msgid "Better yet, get a copy of the DocBook source for this document, and produce patches against it. The DocBook source can be found at the <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with DocBook, don't worry: there is a simple cheatsheet in the manuals directory that will get you started. It's like html, but oriented towards the meaning of the text rather than the presentation. Patches submitted to the debian-boot mailing list (see below) are welcomed. For instructions on how to check out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> from the source root directory."
+msgid ""
+"Better yet, get a copy of the DocBook source for this document, and produce "
+"patches against it. The DocBook source can be found at the <ulink url=\"&url-"
+"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with "
+"DocBook, don't worry: there is a simple cheatsheet in the manuals directory "
+"that will get you started. It's like html, but oriented towards the meaning "
+"of the text rather than the presentation. Patches submitted to the debian-"
+"boot mailing list (see below) are welcomed. For instructions on how to check "
+"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> "
+"from the source root directory."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:82
 #, no-c-format
-msgid "Please do <emphasis>not</emphasis> contact the authors of this document directly. There is also a discussion list for &d-i;, which includes discussions of this manual. The mailing list is <email>debian-boot@lists.debian.org</email>. Instructions for subscribing to this list can be found at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online."
+msgid ""
+"Please do <emphasis>not</emphasis> contact the authors of this document "
+"directly. There is also a discussion list for &d-i;, which includes "
+"discussions of this manual. The mailing list is <email>debian-boot@lists."
+"debian.org</email>. Instructions for subscribing to this list can be found "
+"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List "
+"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-"
+"list-archives;\">Debian Mailing List Archives</ulink> online."
 msgstr ""
 
 #. Tag: title
@@ -82,37 +129,62 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:101
 #, no-c-format
-msgid "This document was originally written by Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the Installation Howto."
+msgid ""
+"This document was originally written by Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the "
+"Installation Howto."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:107
 #, no-c-format
-msgid "Miroslav Kuře has documented a lot of the new functionality in Sarge's debian-installer. Frans Pop was the main editor and release manager during the Etch, Lenny and Squeeze releases."
+msgid ""
+"Miroslav Kuře has documented a lot of the new functionality in Sarge's "
+"debian-installer. Frans Pop was the main editor and release manager during "
+"the Etch, Lenny and Squeeze releases."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:113
 #, no-c-format
-msgid "Many, many Debian users and developers contributed to this document. Particular note must be made of Michael Schmitz (m68k support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. We have to thank Pascal Le Bail for useful information about booting from USB memory sticks."
+msgid ""
+"Many, many Debian users and developers contributed to this document. "
+"Particular note must be made of Michael Schmitz (m68k support), Frank "
+"Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;"
+"\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins "
+"(SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous "
+"edits and text. We have to thank Pascal Le Bail for useful information about "
+"booting from USB memory sticks."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:124
 #, no-c-format
-msgid "Extremely helpful text and information was found in Jim Mintha's HOWTO for network booting (no URL available), the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, amongst others. The maintainers of these freely available and rich sources of information must be recognized."
+msgid ""
+"Extremely helpful text and information was found in Jim Mintha's HOWTO for "
+"network booting (no URL available), the <ulink url=\"&url-debian-faq;"
+"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors "
+"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, "
+"amongst others. The maintainers of these freely available and rich sources "
+"of information must be recognized."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:136
 #, no-c-format
-msgid "The section on chrooted installations in this manual (<xref linkend=\"linux-upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
+msgid ""
+"The section on chrooted installations in this manual (<xref linkend=\"linux-"
+"upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:142
 #, no-c-format
-msgid "The section on installations over plip in this manual (<xref linkend=\"plip\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> by Gilles Lamiral."
+msgid ""
+"The section on installations over plip in this manual (<xref linkend=\"plip"
+"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> by Gilles Lamiral."
 msgstr ""
 
 #. Tag: title
@@ -126,4 +198,3 @@ msgstr ""
 #, no-c-format
 msgid "All trademarks are property of their respective trademark owners."
 msgstr ""
-
diff --git a/po/ro/boot-installer.po b/po/ro/boot-installer.po
index 26928271b..9daaf7e68 100644
--- a/po/ro/boot-installer.po
+++ b/po/ro/boot-installer.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,21 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:15
 #, no-c-format
-msgid "If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly shut down <emphasis>before</emphasis> you boot the installer. Installing an operating system while another operating system is in hibernation (has been suspended to disk) could result in loss of, or damage to the state of the suspended operating system which could cause problems when it is rebooted."
+msgid ""
+"If you have any other operating systems on your system that you wish to keep "
+"(dual boot setup), you should make sure that they have been properly shut "
+"down <emphasis>before</emphasis> you boot the installer. Installing an "
+"operating system while another operating system is in hibernation (has been "
+"suspended to disk) could result in loss of, or damage to the state of the "
+"suspended operating system which could cause problems when it is rebooted."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:26
 #, no-c-format
-msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For information on how to boot the graphical installer, see <xref linkend="
+"\"graphical\"/>."
 msgstr ""
 
 #. Tag: title
@@ -44,21 +53,30 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
-msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
+msgid ""
+"Booting from the network requires that you have a network connection and a "
+"TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
-msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
+msgid ""
+"Older systems such as the 715 might require the use of an RBOOT server "
+"instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
-msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The installation method to support network booting is described in <xref "
+"linkend=\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -68,27 +86,47 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
-msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
+msgid ""
+"The easiest route for most people will be to use a set of &debian; CDs. If "
+"you have a CD set, and if your machine supports booting directly off the CD, "
+"great! Simply <phrase arch=\"x86\"> configure your system for booting off a "
+"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
+"your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
-msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
+msgid ""
+"Note that certain CD drives may require special drivers, and thus be "
+"inaccessible in the early installation stages. If it turns out the standard "
+"way of booting off a CD doesn't work for your hardware, revisit this chapter "
+"and read about alternate kernels and installation methods which may work for "
+"you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
-msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
+msgid ""
+"Even if you cannot boot from CD-ROM, you can probably install the &debian; "
+"system components and any packages you want from CD-ROM. Simply boot using a "
+"different media, such as floppies. When it's time to install the operating "
+"system, base system, and any additional packages, point the installation "
+"system at the CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
-msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
@@ -100,13 +138,20 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:113
 #, no-c-format
-msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines."
+msgid ""
+"There is an increasing number of consumer devices that directly boot from a "
+"flash chip on the device. The installer can be written to flash so it will "
+"automatically start when you reboot your machines."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:119
 #, no-c-format
-msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely."
+msgid ""
+"In many cases, changing the firmware of an embedded device voids your "
+"warranty. Sometimes you are also not able to recover your device if there "
+"are problems during the flashing process. Therefore, please take care and "
+"follow the steps precisely."
 msgstr ""
 
 #. Tag: title
@@ -118,13 +163,28 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:132
 #, no-c-format
-msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>."
+msgid ""
+"Due to limitations in the SS4000-E firmware, it unfortunately is not "
+"possible to boot the installer without the use of a serial port at this "
+"time. To boot the installer, you will need a serial nullmodem cable; a "
+"computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB "
+"serial converter will also work. </para> </footnote>; and a ribbon cable "
+"with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the "
+"other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older "
+"desktop machines with builtin 9-pin serial ports. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:153
 #, no-c-format
-msgid "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a &debian; GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:"
+msgid ""
+"To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable "
+"to connect to the serial port of the SS4000-E, and reboot the machine. You "
+"need to use a serial terminal application to communicate with the machine; a "
+"good option on a &debian; GNU/Linux is to use the <command>cu</command> "
+"program, in the package of the same name. Assuming the serial port on your "
+"computer is to be found on <filename>/dev/ttyS0</filename>, use the "
+"following command line:"
 msgstr ""
 
 #. Tag: screen
@@ -136,7 +196,10 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:167
 #, no-c-format
-msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit."
+msgid ""
+"If using Windows, you may want to consider using the program "
+"<classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word "
+"length, no stop bits, and one parity bit."
 msgstr ""
 
 #. Tag: para
@@ -149,63 +212,86 @@ msgstr ""
 #: boot-installer.xml:179
 #, no-c-format
 msgid ""
-      "No network interfaces found\n"
-      "\n"
-      "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
-      "== Executing boot script in 1.000 seconds - enter ^C to abort"
+"No network interfaces found\n"
+"\n"
+"EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
+"== Executing boot script in 1.000 seconds - enter ^C to abort"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:181
 #, no-c-format
-msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following commands:"
+msgid ""
+"At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-"
+"s4ke-sec\"> <para> Note that you have only one second to do so; if you miss "
+"this window, just powercycle the machine and try again. </para> </footnote>. "
+"This will give you the RedBoot prompt. Enter the following commands:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:194
 #, no-c-format
 msgid ""
-      "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
-      "load -v -r -b 0x01008000 -m ymodem zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
+"load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
+"load -v -r -b 0x01008000 -m ymodem zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:196
 #, no-c-format
-msgid "After every <command>load</command> command, the system will expect a file to be transmitted using the YMODEM protocol. When using cu, make sure you have the package <classname>lrzsz</classname> installed, then hit enter, followed by the <quote>~&lt;</quote> escape sequence to start an external program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</command>."
+msgid ""
+"After every <command>load</command> command, the system will expect a file "
+"to be transmitted using the YMODEM protocol. When using cu, make sure you "
+"have the package <classname>lrzsz</classname> installed, then hit enter, "
+"followed by the <quote>~&lt;</quote> escape sequence to start an external "
+"program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:205
 #, no-c-format
-msgid "Alternatively, it is possible to load the kernel and ramdisk using HTTP rather than YMODEM. This is faster, but requires a working HTTP server on the network. To do so, first switch the bootloader to RAM mode:"
+msgid ""
+"Alternatively, it is possible to load the kernel and ramdisk using HTTP "
+"rather than YMODEM. This is faster, but requires a working HTTP server on "
+"the network. To do so, first switch the bootloader to RAM mode:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:211
 #, no-c-format
 msgid ""
-      "fis load rammode\n"
-      "g"
+"fis load rammode\n"
+"g"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:213
 #, no-c-format
-msgid "This will seemingly restart the machine; but in reality, it loads redboot to RAM and restarts it from there. Not doing this step will cause the system to hang in the necessary ip_address step that comes next."
+msgid ""
+"This will seemingly restart the machine; but in reality, it loads redboot to "
+"RAM and restarts it from there. Not doing this step will cause the system to "
+"hang in the necessary ip_address step that comes next."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:219
 #, no-c-format
 msgid ""
-      "You will need to hit Ctrl-C again to interrupt the boot. Then: <informalexample><screen>\n"
-      "ip_address -l <replaceable>192.168.2.249</replaceable> -h <replaceable>192.168.2.4</replaceable>\n"
-      "load -v -r -b 0x01800000 -m http /initrd.gz\n"
-      "load -v -r -b 0x01008000 -m http /zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000\n"
-      "</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> is the IP address of the installed system and <replaceable>192.168.2.4</replaceable> the IP address of the HTTP server containing the kernel and ramdisk files."
+"You will need to hit Ctrl-C again to interrupt the boot. Then: "
+"<informalexample><screen>\n"
+"ip_address -l <replaceable>192.168.2.249</replaceable> -h "
+"<replaceable>192.168.2.4</replaceable>\n"
+"load -v -r -b 0x01800000 -m http /initrd.gz\n"
+"load -v -r -b 0x01008000 -m http /zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000\n"
+"</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> "
+"is the IP address of the installed system and <replaceable>192.168.2.4</"
+"replaceable> the IP address of the HTTP server containing the kernel and "
+"ramdisk files."
 msgstr ""
 
 #. Tag: para
@@ -215,7 +301,8 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -235,2042 +322,3004 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:355
 #, no-c-format
-msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+msgid ""
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
-msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
+msgid ""
+"download a standalone Windows executable, which is available as tools/win32-"
+"loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
-msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
+msgid ""
+"If you use an installation CD or DVD, a pre-installation program should be "
+"launched automatically when you insert the disc. In case Windows does not "
+"start it automatically, or if you are using a USB memory stick, you can run "
+"it manually by accessing the device and executing <command>setup.exe</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
-msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
+msgid ""
+"After the program has been started, a few preliminary questions will be "
+"asked and the system will be prepared to reboot into the &debian-gnu; "
+"installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
-msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
+msgid ""
+"Boot into DOS (not Windows). To do this, you can for instance boot from a "
+"recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
-      "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
-      "d:\n"
-      "</screen></informalexample> else make sure you have first prepared your hard disk as explained in <xref linkend=\"files-loadlin\"/>, and change the current drive to it if needed."
+"If you can access the installation CD, change the current drive to the CD-"
+"ROM drive, e.g. <informalexample><screen>\n"
+"d:\n"
+"</screen></informalexample> else make sure you have first prepared your hard "
+"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the "
+"current drive to it if needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
-      "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
-      "cd \\&x86-install-dir;\n"
-      "</screen></informalexample> If you prefer using the graphical installer, enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
-      "cd gtk\n"
-      "</screen></informalexample> Next, execute <command>install.bat</command>. The kernel will load and launch the installer system."
+"Enter the subdirectory for the flavor you chose, e.g., "
+"<informalexample><screen>\n"
+"cd \\&x86-install-dir;\n"
+"</screen></informalexample> If you prefer using the graphical installer, "
+"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
+"cd gtk\n"
+"</screen></informalexample> Next, execute <command>install.bat</command>. "
+"The kernel will load and launch the installer system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
-msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
-msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you must first download and place the "
+"needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
-msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
+msgid ""
+"If you intend to use the hard drive only for booting and then download "
+"everything over the network, you should download the <filename>netboot/"
+"debian-installer/&architecture;/initrd.gz</filename> file and its "
+"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
+"linux</filename>. This will allow you to repartition the hard disk from "
+"which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
-msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
+msgid ""
+"Alternatively, if you intend to keep an existing partition on the hard drive "
+"unchanged during the install, you can download the <filename>hd-media/initrd."
+"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
+"drive (make sure the file is named ending in <literal>.iso</literal>). The "
+"installer can then boot from the drive and install from the CD/DVD image, "
+"without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
-msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
+msgid ""
+"For <command>LILO</command>, you will need to configure two essential things "
+"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
+"load the <filename>initrd.gz</filename> installer at boot time; </para></"
+"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
+"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
+"a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
-      "image=/boot/newinstall/vmlinuz\n"
-      "       label=newinstall\n"
-      "       initrd=/boot/newinstall/initrd.gz"
+"image=/boot/newinstall/vmlinuz\n"
+"       label=newinstall\n"
+"       initrd=/boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
-msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
+msgid ""
+"For more details, refer to the <citerefentry><refentrytitle>initrd</"
+"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
+"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
+"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
+"reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
-msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
+msgid ""
+"The procedure for <command>GRUB1</command> is quite similar. Locate your "
+"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
+"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
+"entry for the installer, for example (assuming <filename>/boot</filename> is "
+"on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
-      "title  New Install\n"
-      "root   (hd0,0)\n"
-      "kernel /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz"
+"title  New Install\n"
+"root   (hd0,0)\n"
+"kernel /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
-msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
+msgid ""
+"The procedure for <command>GRUB2</command> is very similar. The file is "
+"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
+"filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
-      "menuentry 'New Install' {\n"
-      "insmod part_msdos\n"
-      "insmod ext2\n"
-      "set root='(hd0,msdos1)'\n"
-      "linux /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz\n"
-      "}"
+"menuentry 'New Install' {\n"
+"insmod part_msdos\n"
+"insmod ext2\n"
+"set root='(hd0,msdos1)'\n"
+"linux /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz\n"
+"}"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
-msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
+msgid ""
+"From here on, there should be no difference between <command>GRUB</command> "
+"or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
-msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
+"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
+"stick into some free USB connector and reboot the computer. The system "
+"should boot up, and unless you have used the flexible way to build the stick "
+"and not enabled it, you should be presented with the <prompt>boot:</prompt> "
+"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
-msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
+msgid ""
+"You will have already downloaded the floppy images you needed and created "
+"floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
-msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
+msgid ""
+"To boot from the installer boot floppy, place it in the primary floppy "
+"drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
-msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
+msgid ""
+"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
+"you need to specify the virtual location for the floppy device. This is done "
+"with the <emphasis>root=</emphasis> boot argument, giving the device that "
+"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
+"is connected as the first IDE device (master) on the second cable, you enter "
+"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
-msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
+msgid ""
+"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
+"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
+"machine, so a <quote>hard</quote> reboot is recommended. If you are "
+"installing from an existing operating system (e.g., from a DOS box) you "
+"don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
-msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
+msgid ""
+"The floppy disk will be accessed, and you should then see a screen that "
+"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
-msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
+msgid ""
+"Once you press &enterkey;, you should see the message "
+"<computeroutput>Loading...</computeroutput>, followed by "
+"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
+"screenfull or so of information about the hardware in your system. More "
+"information on this phase of the boot process can be found below in <xref "
+"linkend=\"kernel-msgs\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
-msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
+msgid ""
+"After booting from the boot floppy, the root floppy is requested. Insert the "
+"root floppy and press &enterkey;, and the contents are loaded into memory. "
+"The installer program <command>debian-installer</command> is automatically "
+"launched."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
-msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
+msgid ""
+"It could be that your Network Interface Card or Motherboard provides PXE "
+"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
+"re-implementation of TFTP boot. If so, you may be able to configure your "
+"BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
-msgid "It could be that your Network Interface Card provides TFTP boot functionality."
+msgid ""
+"It could be that your Network Interface Card provides TFTP boot "
+"functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
-msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
+msgid ""
+"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
+"Please refer to this document."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
-msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
+msgid ""
+"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
+"provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
-      "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
-      "Installer boot menu\n"
-      "\n"
-      "Install\n"
-      "Graphical install\n"
-      "Advanced options             >\n"
-      "Help\n"
-      "Install with speech synthesis\n"
-      "\n"
-      "Press ENTER to boot or TAB to edit a menu entry\n"
-      "</screen></informalexample> Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:658
+"When the installer boots, you should be presented with a friendly graphical "
+"screen showing the &debian; logo and a menu: <informalexample><screen>\n"
+"Installer boot menu\n"
+"\n"
+"Install\n"
+"Graphical install\n"
+"Advanced options             >\n"
+"Help\n"
+"Install with speech synthesis\n"
+"\n"
+"Press ENTER to boot or TAB to edit a menu entry\n"
+"</screen></informalexample> Depending on the installation method you are "
+"using, the <quote>Graphical install</quote> option may not be available. Bi-"
+"arch images additionally have a 64 bit variant for each install option, "
+"right below it, thus almost doubling the number of options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:660
 #, no-c-format
-msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
+msgid ""
+"For a normal installation, select either the <quote>Install</quote> or the "
+"<quote>Graphical install</quote> entry &mdash; using either the arrow keys "
+"on your keyboard or by typing the first (highlighted) letter, the "
+"<quote>Install</quote> entry is already selected by default &mdash; and "
+"press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
-msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
+msgid ""
+"The <quote>Advanced options</quote> entry gives access to a second menu that "
+"allows to boot the installer in expert mode, in rescue mode and for "
+"automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
-msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
+msgid ""
+"If you wish or need to add any boot parameters for either the installer or "
+"the kernel, press &tabkey;. This will display the default boot command for "
+"the selected menu entry and allow to add additional options. The help "
+"screens (see below) list some common possible options. Press &enterkey; to "
+"boot the installer with your options; pressing &escapekey; will return you "
+"to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
-      "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
-      "Press F1 for the help index, or ENTER to boot:\n"
-      "</screen></informalexample> At this boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot command and, optionally, boot parameters. A number of boot parameters which might be useful can be found on the various help screens. If you do add any parameters to the boot command line, be sure to first type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)."
+"Choosing the <quote>Help</quote> entry will result in the first help screen "
+"being displayed which gives an overview of all available help screens. To "
+"return to the boot menu after the help screens have been displayed, type "
+"'menu' at the boot prompt and press &enterkey;. All help screens have a boot "
+"prompt at which the boot command can be typed: <informalexample><screen>\n"
+"Press F1 for the help index, or ENTER to boot:\n"
+"</screen></informalexample> At this boot prompt you can either just press "
+"&enterkey; to boot the installer with default options or enter a specific "
+"boot command and, optionally, boot parameters. A number of boot parameters "
+"which might be useful can be found on the various help screens. If you do "
+"add any parameters to the boot command line, be sure to first type the boot "
+"method (the default is <userinput>install</userinput>) and a space before "
+"the first parameter (e.g., <userinput>install fb=false</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
-msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
+msgid ""
+"The keyboard is assumed to have a default American English layout at this "
+"point. This means that if your keyboard has a different (language-specific) "
+"layout, the characters that appear on the screen may be different from what "
+"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-"
+"keymap;\">schema of the US keyboard layout</ulink> which can be used as a "
+"reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
-msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
+msgid ""
+"If you are using a system that has the BIOS configured to use serial "
+"console, you may not be able to see the initial graphical splash screen upon "
+"booting the installer; you may even not see the boot menu. The same can "
+"happen if you are installing the system via a remote management device that "
+"provides a text interface to the VGA console. Examples of these devices "
+"include the text console of Compaq's <quote>integrated Lights Out</quote> "
+"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
-msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
+msgid ""
+"To bypass the graphical boot screen you can either blindly press &escapekey; "
+"to get a text boot prompt, or (equally blindly) press <quote>H</quote> "
+"followed by &enterkey; to select the <quote>Help</quote> option described "
+"above. After that your keystrokes should be echoed at the prompt. To prevent "
+"the installer from using the framebuffer for the rest of the installation, "
+"you will also want to add <userinput>vga=normal fb=false</userinput> to the "
+"boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
-msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network."
+msgid ""
+"There are three basic variations of &debian; Install CDs. The "
+"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
+"fit on the small form factor CD media. It requires a network connection in "
+"order to install the rest of the base installation and make a usable system. "
+"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
+"base install but requires a network connection to a &debian; mirror site in "
+"order to install the extra packages one would want for a complete system . "
+"The set of &debian; CDs can install a complete system from the wide range of "
+"packages without needing access to the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
-msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
+msgid ""
+"The IA-64 architecture uses the next generation Extensible Firmware "
+"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows "
+"little about the boot device other than the partition table and Master Boot "
+"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted "
+"disk partitions. This simplifies the often arcane process of starting a "
+"system. The system boot loader and the EFI firmware that supports it have a "
+"full filesystem to store the files necessary for booting the machine. This "
+"means that the system disk on an IA-64 system has an additional disk "
+"partition dedicated to EFI instead of the simple MBR or boot block on more "
+"conventional systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
-msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
+msgid ""
+"The &debian; Installer CD contains a small EFI partition where the "
+"<command>ELILO</command> bootloader, its configuration file, the installer's "
+"kernel, and initial filesystem (initrd) are located. The running system also "
+"contains an EFI partition where the necessary files for booting the system "
+"reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
-msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
+msgid ""
+"Most of the details of how <command>ELILO</command> actually loads and "
+"starts a system are transparent to the system installer. However, the "
+"installer must set up an EFI partition prior to installing the base system. "
+"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
+"the system un-bootable. The EFI partition is allocated and formatted in the "
+"partitioning step of the installation prior to loading any packages on the "
+"system disk. The partitioning task also verifies that a suitable EFI "
+"partition is present before allowing the installation to proceed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
-msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
+msgid ""
+"The EFI Boot Manager is presented as the last step of the firmware "
+"initialization. It displays a menu list from which the user can select an "
+"option. Depending on the model of system and what other software has been "
+"loaded on the system, this menu may be different from one system to another. "
+"There should be at least two menu items displayed, <command>Boot Option "
+"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
+"Using the first option is preferred, however, if that option is not "
+"available or the CD for some reason does not boot with it, use the second "
+"option."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
-msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
+msgid ""
+"The EFI Boot Manager will select a default boot action, typically the first "
+"menu choice, within a pre-set number of seconds. This is indicated by a "
+"countdown at the bottom of the screen. Once the timer expires and the "
+"systems starts the default action, you may have to reboot the machine in "
+"order to continue the installation. If the default action is the EFI Shell, "
+"you can return to the Boot Manager by running <command>exit</command> at the "
+"shell prompt."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes its system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
-msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
+msgid ""
+"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
+"keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
-msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
+msgid ""
+"Select <command>Boot From a File</command> from the menu with the arrow keys "
+"and press <command>ENTER</command>. This will display a list of devices "
+"probed by the firmware. You should see two menu lines containing either the "
+"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
+"Boot</command>. If you examine the rest of the menu line, you will notice "
+"that the device and controller information should be the same."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
-msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
+msgid ""
+"You can choose either of the entries that refer to the CD/DVD drive. Select "
+"your choice with the arrow keys and press <command>ENTER</command>. If you "
+"choose <command>Removable Media Boot</command> the machine will immediately "
+"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
+"command> instead, it will display a directory listing of the bootable "
+"portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
-msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
+"command>. The directory listing will also show <command>[Treat like "
+"Removable Media Boot]</command> on the next to the last line. Select this "
+"line with the arrow keys and press <command>ENTER</command>. This will start "
+"the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
-msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
+msgid ""
+"These steps start the &debian; boot loader which will display a menu page "
+"for you to select a boot kernel and options. Proceed to selecting the boot "
+"kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
-msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:"
+msgid ""
+"If, for some reason, option 1 is not successful, reboot the machine and when "
+"the EFI Boot Manager screen appears there should be one option called "
+"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with "
+"the following steps:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
-msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
+msgid ""
+"Select <command>EFI Shell</command> from the menu with the arrow keys and "
+"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
+"devices and display them to the console before displaying its command "
+"prompt. The recognized bootable partitions on devices will show a device "
+"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
+"recognized partitions will be named <filename>blk<replaceable>n</"
+"replaceable>:</filename>. If you inserted the CD just before entering the "
+"shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
-msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
+msgid ""
+"Examine the output from the shell looking for the CDROM drive. It is most "
+"likely the <filename>fs0:</filename> device although other devices with "
+"bootable partitions will also show up as <filename>fs<replaceable>n</"
+"replaceable></filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
-msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
+msgid ""
+"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
+"<command>ENTER</command> to select that device where <replaceable>n</"
+"replaceable> is the partition number for the CDROM. The shell will now "
+"display the partition number as its prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
-msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
+"start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
-msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
+msgid ""
+"As with option 1, these steps start the &debian; boot loader which will "
+"display a menu page for you to select a boot kernel and options. You can "
+"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
+"command> command at the shell prompt. Proceed to selecting the boot kernel "
+"and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
-msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
+msgid ""
+"You may choose to perform an install using a monitor and keyboard or using a "
+"serial connection. To use a monitor/keyboard setup, select an option "
+"containing the string [VGA console]. To install over a serial connection, "
+"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
+"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
+"serial console. Menu items for the most typical baud rate settings on the "
+"ttyS0 device are preconfigured."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
-msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
+msgid ""
+"In most circumstances, you will want the installer to use the same baud rate "
+"as your connection to the EFI console. If you aren't sure what this setting "
+"is, you can obtain it using the command <command>baud</command> at the EFI "
+"shell."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
-msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
+msgid ""
+"If there is not an option available that is configured for the serial device "
+"or baud rate you would like to use, you may override the console setting for "
+"one of the existing menu options. For example, to use a 57600 baud console "
+"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
+"the <classname>Boot:</classname> text window."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
-msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
+msgid ""
+"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
+"setting is rather slow, and the normal installation process will take a "
+"significant time to draw each screen. You should consider either increasing "
+"the baud rate used for performing the installation, or performing a Text "
+"Mode installation. See the <classname>Params</classname> help menu for "
+"instructions on starting the installer in Text Mode."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
-msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
+msgid ""
+"If you select the wrong console type, you will be able to select the kernel "
+"and enter parameters but both the display and your input will go dead as "
+"soon as the kernel starts, requiring you to reboot before you can begin the "
+"installation."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
-msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
+msgid ""
+"The boot loader will display a form with a menu list and a text window with "
+"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
+"the menu and any text typed at the keyboard will appear in the text window. "
+"There are also help screens which can be displayed by pressing the "
+"appropriate function key. The <classname>General</classname> help screen "
+"explains the menu choices and the <classname>Params</classname> screen "
+"explains the common command line options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
-msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
+msgid ""
+"Consult the <classname>General</classname> help screen for the description "
+"of the kernels and install modes most appropriate for your installation. You "
+"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
+"parameters that you may want to set in the <classname>Boot:</classname> text "
+"window. The kernel version you choose selects the kernel version that will "
+"be used for both the installation process and the installed system. If you "
+"encounter kernel problems with the installation, you may also have those "
+"same problems with the system you install. The following two steps will "
+"select and start the install:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
-msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
+msgid ""
+"Select the kernel version and installation mode most appropriate to your "
+"needs with the arrow keys."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
-msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
+msgid ""
+"Enter any boot parameters by typing at the keyboard. The text will be "
+"displayed directly in the text window. This is where kernel parameters (such "
+"as serial console settings) are specified."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
-msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer."
+msgid ""
+"Press <command>ENTER</command>. This will load and start the kernel. The "
+"kernel will display its usual initialization messages followed by the first "
+"screen of the &debian; Installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
-msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
+msgid ""
+"Proceed to the next chapter to continue the installation where you will set "
+"up the language locale, network, and disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
-msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
+msgid ""
+"Booting an IA-64 system from the network is similar to a CD boot. The only "
+"difference is how the installation kernel is loaded. The EFI Boot Manager "
+"can load and start programs from a server on the network. Once the "
+"installation kernel is loaded and starts, the system install will proceed "
+"through the same steps as the CD install with the exception that the "
+"packages of the base install will be loaded from the network rather than the "
+"CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
-msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
+msgid ""
+"Network booting an IA-64 system requires two architecture-specific actions. "
+"On the boot server, DHCP and TFTP must be configured to deliver "
+"<command>elilo</command>. On the client a new boot option must be defined in "
+"the EFI boot manager to enable loading over a network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
-      "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
-      "host mcmuffin {\n"
-      "        hardware ethernet 00:30:6e:1e:0e:83;\n"
-      "        fixed-address 10.0.0.21;\n"
-      "        filename \"debian-installer/ia64/elilo.efi\";\n"
-      "}\n"
-      "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
+"A suitable TFTP entry for network booting an IA-64 system looks something "
+"like this: <informalexample><screen>\n"
+"host mcmuffin {\n"
+"        hardware ethernet 00:30:6e:1e:0e:83;\n"
+"        fixed-address 10.0.0.21;\n"
+"        filename \"debian-installer/ia64/elilo.efi\";\n"
+"}\n"
+"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
+"command> running on the client."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
-msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
+msgid ""
+"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
+"as the root for your tftp server. Typical tftp root directories include "
+"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
+"will create a <filename>debian-installer</filename> directory tree "
+"containing the boot files for an IA-64 system."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
-      "# cd /var/lib/tftp\n"
-      "# tar xvfz /home/user/netboot.tar.gz\n"
-      "./\n"
-      "./debian-installer/\n"
-      "./debian-installer/ia64/\n"
-      "[...]"
+"# cd /var/lib/tftp\n"
+"# tar xvfz /home/user/netboot.tar.gz\n"
+"./\n"
+"./debian-installer/\n"
+"./debian-installer/ia64/\n"
+"[...]"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
-msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
+msgid ""
+"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
+"filename> file that should work for most configurations. However, should you "
+"need to make changes to this file, you can find it in the <filename>debian-"
+"installer/ia64/</filename> directory. It is possible to have different "
+"config files for different clients by naming them using the client's IP "
+"address in hex with the suffix <filename>.conf</filename> instead of "
+"<filename>elilo.conf</filename>. See documentation provided in the "
+"<classname>elilo</classname> package for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
-msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
+msgid ""
+"To configure the client to support TFTP booting, start by booting to EFI and "
+"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
+"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
+"should see one or more lines with the text <guimenuitem>Load File [Acpi"
+"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose "
+"the one containing the MAC address of the interface from which you'll be "
+"booting. Use the arrow keys to highlight your choice, then press enter. </"
+"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
+"userinput> or something similar, save, and exit back to the boot options "
+"menu. </para></listitem> </itemizedlist> You should see the new boot option "
+"you just created, and selecting it should initiate a DHCP query, leading to "
+"a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
-msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer."
+msgid ""
+"The boot loader will display its prompt after it has downloaded and "
+"processed its configuration file. At this point, the installation proceeds "
+"with the same steps as a CD install. Select a boot option as in above and "
+"when the kernel has completed installing itself from the network, it will "
+"start the &debian; Installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
-      "After entering the command monitor use <informalexample><screen>\n"
-      "bootp():\n"
-      "</screen></informalexample> on SGI machines to boot linux and to begin installation of the &debian; Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n"
-      "unsetenv netaddr\n"
-      "</screen></informalexample> in the command monitor to do this."
+"After entering the command monitor use <informalexample><screen>\n"
+"bootp():\n"
+"</screen></informalexample> on SGI machines to boot linux and to begin "
+"installation of the &debian; Software. In order to make this work you may "
+"have to unset the <envar>netaddr</envar> environment variable. Type "
+"<informalexample><screen>\n"
+"unsetenv netaddr\n"
+"</screen></informalexample> in the command monitor to do this."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
-msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
+msgid ""
+"On SGI machines you can append boot parameters to the <command>bootp():</"
+"command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
-      "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
-      "bootp():/boot/tftpboot.img\n"
-      "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
+"Following the <command>bootp():</command> command you can give the path and "
+"name of the file to boot if you did not give an explicit name via your bootp/"
+"dhcp server. Example: <informalexample><screen>\n"
+"bootp():/boot/tftpboot.img\n"
+"</screen></informalexample> Further kernel parameters can be passed via "
+"<command>append</command>:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
-msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
+msgid ""
+"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
+"install an NFS server and put the installer files in <filename>/nfsroot</"
+"filename>. When you boot your Cobalt, you have to press the left and the "
+"right cursor buttons at the same time and the machine will boot via the "
+"network from NFS. It will then display several options on the display. There "
+"are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
-msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
+msgid ""
+"Via SSH (default): In this case, the installer will configure the network "
+"via DHCP and start an SSH server. It will then display a random password and "
+"other login information (such as the IP address) on the Cobalt LCD. When you "
+"connect to the machine with an SSH client you can start with the "
+"installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
-msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
+msgid ""
+"Via serial console: Using a null modem cable, you can connect to the serial "
+"port of your Cobalt machine (using 115200 bps) and perform the installation "
+"this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
-msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
+msgid ""
+"You cannot pass any boot parameters directly. Instead, you have to edit the "
+"<filename>/nfsroot/default.colo</filename> file on the NFS server and add "
+"your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
-msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
+msgid ""
+"In order to run the installation system a working network setup and ssh "
+"session is needed on S/390."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
-msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
+msgid ""
+"The booting process starts with a network setup that prompts you for several "
+"network parameters. If the setup is successful, you will login to the system "
+"by starting an ssh session which will launch the standard installation "
+"system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
-msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
+msgid ""
+"On S/390 you can append boot parameters in the parm file. This file can "
+"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
+"debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
-msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive."
+msgid ""
+"Currently, the only &arch-title; subarchitectures that support CD-ROM "
+"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
+"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
+"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
+"and <keycap>Delete</keycap> keys together while booting to boot from the "
+"factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
-      "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
-      "0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
-      "</screen></informalexample> for an alternative way to boot from the internal factory default CD/DVD drive type"
+"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
+"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
+"type <informalexample><screen>\n"
+"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
+"</screen></informalexample> for an alternative way to boot from the internal "
+"factory default CD/DVD drive type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
-msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
+msgid ""
+"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
+"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
+"software version of this driver is not available. All OldWorld systems have "
+"floppy drives, so use the floppy drive to launch the installer, and then "
+"point the installer to the CD for the needed files."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
-msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
+msgid ""
+"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
+"immediately after pressing the power-on button, when SmartFirmware prompt "
+"appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
-msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
+msgid ""
+"Booting from an existing operating system is often a convenient option; for "
+"some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
-msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you will have already completed "
+"downloading and placing the needed files as described in <xref linkend="
+"\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
-msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
+msgid ""
+"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
+"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
+"application icon. Click on the <guibutton>Options</guibutton> button and "
+"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
+"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
+"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
+"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
+"down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
-      "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
-      "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
-      "</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n"
-      "boot:\n"
-      "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The &debian; installation program should start."
+"You will have already placed the <filename>vmlinux</filename>, "
+"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
+"<filename>yaboot.conf</filename> files at the root level of your HFS "
+"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
+"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
+"prompt, type <informalexample><screen>\n"
+"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
+"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
+"partition number of the HFS partition where the kernel and yaboot files were "
+"placed, followed by a &enterkey;. On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
+"more seconds you will see a yaboot prompt <informalexample><screen>\n"
+"boot:\n"
+"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
+"either <userinput>install</userinput> or <userinput>install video=ofonly</"
+"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
+"argument is for maximum compatibility; you can try it if <userinput>install</"
+"userinput> doesn't work. The &debian; installation program should start."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
-msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
+msgid ""
+"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
+">. To boot a Macintosh system from a USB stick, you will need to use the "
+"Open Firmware prompt, since Open Firmware does not search USB storage "
+"devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
-msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
+msgid ""
+"You will need to work out where the USB storage device appears in the device "
+"tree, since at the moment <command>ofpath</command> cannot work that out "
+"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
+"userinput> at the Open Firmware prompt to get a list of all known devices "
+"and device aliases. On the author's system with various types of USB stick, "
+"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
+"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
+"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
-      "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
-      "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n"
-      "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
+"Having worked out the device path, use a command like this to boot the "
+"installer: <informalexample><screen>\n"
+"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
+"tbxi\n"
+"</screen></informalexample> The <replaceable>2</replaceable> matches the "
+"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
+"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
+"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
+"<command>yaboot</command>) in the directory previously blessed with "
+"<command>hattrib -b</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
-msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"The system should now boot up, and you should be presented with the "
+"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
+"or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
-msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
+msgid ""
+"This boot method is new, and may be difficult to get to work on some "
+"NewWorld systems. If you have problems, please file an installation report, "
+"as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
-      "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
-      "0 &gt; boot enet:0\n"
-      "</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>\n"
-      "0 &gt; boot enet:0,yaboot\n"
-      "</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>\n"
-      "boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>\n"
-      "</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:1676
+"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
+"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
+"<informalexample><screen>\n"
+"0 &gt; boot enet:0\n"
+"</screen></informalexample> If this doesn't work, you might have to add the "
+"filename like this: <informalexample><screen>\n"
+"0 &gt; boot enet:0,yaboot\n"
+"</screen></informalexample> PReP and CHRP boxes may have different ways of "
+"addressing the network. On a PReP machine, you should try "
+"<informalexample><screen>\n"
+"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
+"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
+"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
+"machines) the command <userinput>help boot</userinput> may give a "
+"description of syntax and available options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:1678
 #, no-c-format
-msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
+msgid ""
+"Booting from floppies is supported for &arch-title;, although it is "
+"generally only applicable for OldWorld systems. NewWorld systems are not "
+"equipped with floppy drives, and attached USB floppy drives are not "
+"supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
-msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
+msgid ""
+"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
+"in floppy drive after shutting the system down, and before pressing the "
+"power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
-msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
+msgid ""
+"For those not familiar with Macintosh floppy operations: a floppy placed in "
+"the machine prior to boot will be the first priority for the system to boot "
+"from. A floppy without a valid boot system will be ejected, and the machine "
+"will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
-msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
+msgid ""
+"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
+"the root floppy and press &enterkey;. The installer program is automatically "
+"launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
-msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
+msgid ""
+"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
+"skewed on an older Apple monitor, try appending the boot argument "
+"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
+"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
+"<userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
-msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
+msgid ""
+"On machines with OpenBoot, simply enter the boot monitor on the machine "
+"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
+"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
+"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
+"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
+"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
-msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
+msgid ""
+"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
+"which is simply an alias to boot from the SCSI device on ID 6 (or the "
+"secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
-msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
+msgid ""
+"If you cannot boot because you get messages about a problem with "
+"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
+"holds configuration information for you firmware, has run out. See the "
+"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
+"information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
-msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
+msgid ""
+"Some users may need specific support because of e.g. some visual impairment. "
+"<phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected "
+"automatically (not serial displays connected via a serial-to-USB converter), "
+"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</"
+"phrase> accessibility features have to be enabled manually. <phrase arch="
+"\"x86\">On machines that support it, the boot menu emits a beep when it is "
+"ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch="
+"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
+"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that "
+"on most architectures the boot loader interprets your keyboard as a QWERTY "
+"keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
-msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"USB braille displays should be automatically detected. A textual version of "
+"the installer will then be automatically selected, and support for the "
+"braille display will be automatically installed on the target system. You "
+"can thus just press &enterkey; at the boot menu. Once <classname>brltty</"
+"classname> is started, you can choose a braille table by entering the "
+"preference menu. Documentation on key bindings for braille devices is "
+"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
+"classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
-msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"Serial braille displays cannot safely be automatically detected (since that "
+"may damage some of them). You thus need to append the "
+"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
+"replaceable>,<replaceable>table</replaceable></userinput> boot parameter to "
+"tell <classname>brltty</classname> which driver it should use. "
+"<replaceable>driver</replaceable> should be replaced by the two-letter "
+"driver code for your terminal (see the <ulink url=\"&url-brltty-manual;"
+"\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be "
+"replaced by the name of the serial port the display is connected to, "
+"<userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> "
+"can be typically used when using a serial-to-USB converter. "
+"<replaceable>table</replaceable> is the name of the braille table to be used "
+"(see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the "
+"English table is the default. Note that the table can be changed later by "
+"entering the preference menu. Documentation on key bindings for braille "
+"devices is available on the <ulink url=\"&url-brltty-driver-help;"
+"\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
-msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
+msgid ""
+"Support for software speech synthesis can be activated by selecting it in "
+"the boot menu by typing <userinput>s</userinput> &enterkey;. The first "
+"question (language) is spoken in english, and the remainder of installation "
+"is spoken in the selected language (if available in <classname>espeak</"
+"classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
+msgid ""
+"Support for hardware speech synthesis devices is available only alongside "
+"support for graphical installer. You thus need to select a <quote>Graphical "
+"install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
-msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
+msgid ""
+"Hardware speech synthesis devices cannot be automatically detected. You thus "
+"need to append the <userinput>speakup.synth=<replaceable>driver</"
+"replaceable></userinput> boot parameter to tell <classname>speakup</"
+"classname> which driver it should use. <replaceable>driver</replaceable> "
+"should be replaced by the driver code for your device (see <ulink url=\"&url-"
+"speakup-driver-codes;\">driver code list</ulink>). The textual version of "
+"the installer will then be automatically selected, and support for the "
+"speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
-msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
+msgid ""
+"Some accessibility devices are actual boards that are plugged inside the "
+"machine and that read text directly from the video memory. To get them to "
+"work framebuffer support must be disabled by using the <userinput arch="
+"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot "
+"parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
-msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
+msgid ""
+"If desired a textual version of the bootloader can be activated before "
+"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
-msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
+msgid ""
+"For users with low vision, the installer can use a high-contrast theme that "
+"makes it more readable. To enable it, append the <userinput>theme=dark</"
+"userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
-msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Alternatively, &debian; can be installed completely automatically by using "
+"preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
-msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
+msgid ""
+"Boot parameters are Linux kernel parameters which are generally used to make "
+"sure that peripherals are dealt with properly. For the most part, the kernel "
+"can auto-detect information about your peripherals. However, in some cases "
+"you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
-msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
+msgid ""
+"If this is the first time you're booting the system, try the default boot "
+"parameters (i.e., don't try setting parameters) and see if it works "
+"correctly. It probably will. If not, you can reboot later and look for any "
+"special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
-msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"Information on many boot parameters can be found in the <ulink url=\"http://"
+"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
+"including tips for obscure hardware. This section contains only a sketch of "
+"the most salient parameters. Some common gotchas are included below in <xref "
+"linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
-msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
+msgid ""
+"If you are booting with a serial console, generally the kernel will "
+"autodetect this. If you have a videocard (framebuffer) and a keyboard also "
+"attached to the computer which you wish to boot via serial console, you may "
+"have to pass the <userinput>console=<replaceable>device</replaceable></"
+"userinput> argument to the kernel, where <replaceable>device</replaceable> "
+"is your serial device, which is usually something like <filename>ttyS0</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
-msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
+msgid ""
+"In order to ensure the terminal type used by the installer matches your "
+"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
+"replaceable></userinput> can be added. Note that the installer only supports "
+"the following terminal types: <literal>linux</literal>, <literal>bterm</"
+"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
+"<literal>dumb</literal>. The default for serial console in &d-i; is "
+"<userinput>vt102</userinput>. If you are using a virtualization tool which "
+"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, "
+"you can start it inside a <command>screen</command> session. That will "
+"indeed perform translation into the <literal>screen</literal> terminal type, "
+"which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
-msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
+msgid ""
+"For &arch-title; the serial devices are <filename>ttya</filename> or "
+"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
+"envar> and <envar>output-device</envar> OpenPROM variables to "
+"<filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
+msgid ""
+"The installation system recognizes a few additional boot "
+"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
+"use 32 command line options and 32 environment options. If these numbers are "
+"exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
-msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
+msgid ""
+"A number of parameters have a <quote>short form</quote> that helps avoid the "
+"limitations of the kernel command line options and makes entering the "
+"parameters easier. If a parameter has a short form, it will be listed in "
+"brackets behind the (normal) long form. Examples in this manual will "
+"normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
-msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
+msgid ""
+"The default installation uses <userinput>priority=high</userinput>. This "
+"means that both high and critical priority messages are shown, but medium "
+"and low priority messages are skipped. If problems are encountered, the "
+"installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
-msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
+msgid ""
+"If you add <userinput>priority=medium</userinput> as boot parameter, you "
+"will be shown the installation menu and gain more control over the "
+"installation. When <userinput>priority=low</userinput> is used, all messages "
+"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
+"method). With <userinput>priority=critical</userinput>, the installation "
+"system will display only critical messages and try to do the right thing "
+"without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
-msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
+msgid ""
+"This boot parameter controls the type of user interface used for the "
+"installer. The current possible parameter settings are: <itemizedlist> "
+"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
+"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
+"userinput></para> </listitem><listitem> "
+"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
+"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
+"</listitem> </itemizedlist> The default frontend is "
+"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
+"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
+"console installs. Some specialized types of install media may only offer a "
+"limited selection of frontends, but the <userinput>newt</userinput> and "
+"<userinput>text</userinput> frontends are available on most default install "
+"media. On architectures that support it, the graphical installer uses the "
+"<userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
-msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
+msgid ""
+"Setting this boot parameter to 2 will cause the installer's boot process to "
+"be verbosely logged. Setting it to 3 makes debug shells available at "
+"strategic points in the boot process. (Exit the shells to continue the boot "
+"process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
-msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
+msgid ""
+"Shells are run at various points in the boot process to allow detailed "
+"debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
-msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
+msgid ""
+"The value of the parameter is the path to the device to load the &debian; "
+"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
+"userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
-msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
+msgid ""
+"The boot floppy, which normally scans all floppies it can to find the root "
+"floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
-msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
+msgid ""
+"Causes the installer to send log messages to a remote syslog on the "
+"specified host and port as well as to a local file. If not specified, the "
+"port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
-msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
+msgid ""
+"Can be used to force the installer to a lowmem level higher than the one the "
+"installer sets by default based on available memory. Possible values are 1 "
+"and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
-msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
+msgid ""
+"Prevents the installer from offering interactive shells on tty2 and tty3. "
+"Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
-msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
+msgid ""
+"Some architectures use the kernel framebuffer to offer installation in a "
+"number of languages. If framebuffer causes a problem on your system you can "
+"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</"
+"userinput> <userinput>fb=false</userinput>. Problem symptoms are error "
+"messages about bterm or bogl, a blank screen, or a freeze within a few "
+"minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
-msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
+msgid ""
+"Because of display problems on some systems, framebuffer support is "
+"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
+"in ugly display on systems that do properly support the framebuffer, like "
+"those with ATI graphical cards. If you see display problems in the "
+"installer, you can try booting with parameter <userinput>debian-installer/"
+"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
-msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
+msgid ""
+"A theme determines how the user interface of the installer looks (colors, "
+"icons, etc.). What themes are available differs per frontend. Currently both "
+"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
+"designed for visually impaired users. Set the theme by booting with "
+"<userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
-msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
+msgid ""
+"By default, the &d-i; automatically probes for network configuration via "
+"DHCP. If the probe succeeds, you won't have a chance to review and change "
+"the obtained settings. You can get to the manual network setup only in case "
+"the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
-msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
+msgid ""
+"If you have a DHCP server on your local network, but want to avoid it "
+"because e.g. it gives wrong answers, you can use the parameter "
+"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
+"network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
+msgid ""
+"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
+"that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
+msgid ""
+"Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
+"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note "
+"that this support is currently experimental. Additional information can be "
+"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
-msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the url to a preconfiguration file to download and use for "
+"automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
-msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the path to a preconfiguration file to load for automating the "
+"install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
+msgid ""
+"Set to <userinput>true</userinput> to display questions even if they have "
+"been preseeded. Can be useful for testing or debugging a preconfiguration "
+"file. Note that this will have no effect on parameters that are passed as "
+"boot parameters, but for those a special syntax can be used. See <xref "
+"linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
-msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
+msgid ""
+"Delay questions that are normally asked before preseeding is possible until "
+"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
+"details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
-msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
+msgid ""
+"During installations from serial or management console, the regular virtual "
+"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
+"filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
-msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
+msgid ""
+"By default, before rebooting, &d-i; automatically ejects the optical media "
+"used during the installation. This can be unnecessary if the system does not "
+"automatically boot off the CD. In some cases it may even be undesirable, for "
+"example if the optical drive cannot reinsert the media itself and the user "
+"is not there to do it manually. Many slot loading, slim-line, and caddy "
+"style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
+msgid ""
+"Set to <userinput>false</userinput> to disable automatic ejection, and be "
+"aware that you may need to ensure that the system does not automatically "
+"boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
-msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
+msgid ""
+"By setting this option to <userinput>false</userinput>, the package "
+"management system will be configured to not automatically install "
+"<quote>Recommends</quote>, both during the installation and for the "
+"installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
-msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
+msgid ""
+"Note that this option allows to have a leaner system, but can also result in "
+"features being missing that you might normally expect to be available. You "
+"may have to manually install some of the recommended packages to obtain the "
+"full functionality you want. This option should therefore only be used by "
+"very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
-msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
+msgid ""
+"By default the installer requires that repositories be authenticated using a "
+"known gpg key. Set to <userinput>true</userinput> to disable that "
+"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
+"emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
-msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
+msgid ""
+"This parameter should already be set to a correct value where needed; set it "
+"only it you see errors during the boot that indicate the ramdisk could not "
+"be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
+msgid ""
+"Set to <userinput>true</userinput> to enter rescue mode rather than "
+"performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
-msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
+msgid ""
+"With some exceptions, a value can be set at the boot prompt for any question "
+"asked during the installation, though this is only really useful in specific "
+"cases. General instructions how to do this can be found in <xref linkend="
+"\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
-msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
+msgid ""
+"There are two ways to specify the language, country and locale to use for "
+"the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
-msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
+msgid ""
+"The first and easiest is to pass only the parameter <literal>locale</"
+"literal>. Language and country will then be derived from its value. You can "
+"for example use <userinput>locale=de_CH</userinput> to select German as "
+"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be "
+"set as default locale for the installed system). Limitation is that not all "
+"possible combinations of language, country and locale can be achieved this "
+"way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
-msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
+msgid ""
+"The second, more flexible option is to specify <literal>language</literal> "
+"and <literal>country</literal> separately. In this case <literal>locale</"
+"literal> can optionally be added to specify a specific default locale for "
+"the installed system. Example: <userinput>language=en country=DE "
+"locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
-msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
+msgid ""
+"Can be used to automatically load installer components that are not loaded "
+"by default. Examples of optional components that may be useful are "
+"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
+"command> during the installation)<phrase arch=\"not-s390\"> and "
+"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
-msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
+msgid ""
+"Set to <userinput>true</userinput> if you want to disable DHCP and instead "
+"force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
-msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
+msgid ""
+"By default the installer will use the http protocol to download files from "
+"&debian; mirrors and changing that to ftp is not possible during "
+"installations at normal priority. By setting this parameter to "
+"<userinput>ftp</userinput>, you can force the installer to use that protocol "
+"instead. Note that you cannot select an ftp mirror from a list, you have to "
+"enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
-msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
+msgid ""
+"Can be used to select tasks that are not available from the interactive task "
+"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
+"\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
-msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
+msgid ""
+"If drivers are compiled into the kernel, you can pass parameters to them as "
+"described in the kernel documentation. However, if drivers are compiled as "
+"modules and because kernel modules are loaded a bit differently during an "
+"installation than when booting an installed system, it is not possible to "
+"pass parameters to modules as you would normally do. Instead, you need to "
+"use a special syntax recognized by the installer which will then make sure "
+"that the parameters are saved in the proper configuration files and will "
+"thus be used when the modules are actually loaded. The parameters will also "
+"be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
-msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
+msgid ""
+"Note that it is now quite rare that parameters need to be passed to modules. "
+"In most cases the kernel will be able to probe the hardware present in a "
+"system and set good defaults that way. However, in some situations it may "
+"still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
-      "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
-      "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n"
-      "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:"
+"The syntax to use to set parameters for modules is: "
+"<informalexample><screen>\n"
+"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
+"replaceable>=<replaceable>value</replaceable>\n"
+"</screen></informalexample> If you need to pass multiple parameters to the "
+"same or different modules, just repeat this. For example, to set an old 3Com "
+"network interface card to use the BNC (coax) connector and IRQ 10, you would "
+"pass:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
-msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
+msgid ""
+"Sometimes it may be necessary to blacklist a module to prevent it from being "
+"loaded automatically by the kernel and udev. One reason could be that a "
+"particular module causes problems with your hardware. The kernel also "
+"sometimes lists two different drivers for the same device. This can cause "
+"the device to not work correctly if the drivers conflict or if the wrong "
+"driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
-msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
+msgid ""
+"You can blacklist a module using the following syntax: "
+"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
+"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
+"blacklist.local</filename> both during the installation and for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
-msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
+msgid ""
+"Note that a module may still be loaded by the installation system itself. "
+"You can prevent that from happening by running the installation in expert "
+"mode and unselecting the module from the list of modules displayed during "
+"the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
-msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
+msgid ""
+"Sometimes, especially with older CD-ROM drives, the installer may fail to "
+"boot from a CD-ROM. The installer may also &mdash; even after booting "
+"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
+"errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
-msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
+msgid ""
+"There are many different possible causes for these problems. We can only "
+"list some common issues and provide general suggestions on how to deal with "
+"them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
-msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
+msgid ""
+"If the CD-ROM does not boot, check that it was inserted correctly and that "
+"it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
-msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
+msgid ""
+"If the installer fails to recognize a CD-ROM, try just running the option "
+"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
+"menuchoice> a second time. Some DMA related issues with very old CD-ROM "
+"drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
-msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
+msgid ""
+"If this does not work, then try the suggestions in the subsections below. "
+"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
+"DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
-msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
+msgid ""
+"If you cannot get the installation working from CD-ROM, try one of the other "
+"installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
-msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
+msgid ""
+"Some older CD-ROM drives do not support reading from discs that were burned "
+"at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
-msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
+msgid ""
+"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
+"access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
-msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
+msgid ""
+"Check that your BIOS actually supports booting from CD-ROM (only an issue "
+"for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
-      "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
-      "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM."
+"If you downloaded an iso image, check that the md5sum of that image matches "
+"the one listed for the image in the <filename>MD5SUMS</filename> file that "
+"should be present in the same location as where you downloaded the image "
+"from. <informalexample><screen>\n"
+"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
+"iso</replaceable>\n"
+"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
+"matches as well. The following command should work. It uses the size of the "
+"image to read the correct number of bytes from the CD-ROM."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
-      "$ dd if=/dev/cdrom | \\\n"
-      "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n"
-      "> md5sum\n"
-      "a20391b12f7ff22ef705cee4059c6b92  -\n"
-      "262668+0 records in\n"
-      "262668+0 records out\n"
-      "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
+"$ dd if=/dev/cdrom | \\\n"
+"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
+"replaceable>` | \\\n"
+"> md5sum\n"
+"a20391b12f7ff22ef705cee4059c6b92  -\n"
+"262668+0 records in\n"
+"262668+0 records out\n"
+"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
-msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
+msgid ""
+"If, after the installer has been booted successfully, the CD-ROM is not "
+"detected, sometimes simply trying again may solve the problem. If you have "
+"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
+"that does not work or if the CD-ROM is recognized but there are errors when "
+"reading from it, try the suggestions listed below. Some basic knowledge of "
+"&arch-kernel; is required for this. To execute any of the commands, you "
+"should first switch to the second virtual console (VT2) and activate the "
+"shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
-msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
+msgid ""
+"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
+"(use <command>nano</command> as editor) to check for any specific error "
+"messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
-      "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
-      "Probing IDE interface ide1...\n"
-      "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
-      "ide1 at 0x170-0x177,0x376 on irq 15\n"
-      "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
-      "Uniform CD-ROM driver Revision: 3.20\n"
-      "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using <command>modprobe</command>."
+"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
+"recognized. You should see something like (the lines do not necessarily have "
+"to be consecutive): <informalexample><screen>\n"
+"Probing IDE interface ide1...\n"
+"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
+"ide1 at 0x170-0x177,0x376 on irq 15\n"
+"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
+"Uniform CD-ROM driver Revision: 3.20\n"
+"</screen></informalexample> If you don't see something like that, chances "
+"are the controller your CD-ROM is connected to was not recognized or may be "
+"not supported at all. If you know what driver is needed for the controller, "
+"you can try loading it manually using <command>modprobe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
-msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
+msgid ""
+"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
+"</filename>. In the example above, this would be <filename>/dev/hdc</"
+"filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
-      "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
-      "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
-      "</screen></informalexample> Check if there are any error messages after that command."
+"Use the <command>mount</command> command to check if the CD-ROM is already "
+"mounted; if not, try mounting it manually: <informalexample><screen>\n"
+"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
+"</screen></informalexample> Check if there are any error messages after that "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
-      "Check if DMA is currently enabled: <informalexample><screen>\n"
-      "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
-      "$ grep using_dma settings\n"
-      "using_dma      1       0       1       rw\n"
-      "</screen></informalexample> A <quote>1</quote> in the first column after <literal>using_dma</literal> means it is enabled. If it is, try disabling it: <informalexample><screen>\n"
-      "$ echo -n \"using_dma:0\" >settings\n"
-      "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive."
+"Check if DMA is currently enabled: <informalexample><screen>\n"
+"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
+"$ grep using_dma settings\n"
+"using_dma      1       0       1       rw\n"
+"</screen></informalexample> A <quote>1</quote> in the first column after "
+"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
+"it: <informalexample><screen>\n"
+"$ echo -n \"using_dma:0\" >settings\n"
+"</screen></informalexample> Make sure that you are in the directory for the "
+"device that corresponds to your CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
-msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
+msgid ""
+"If there are any problems during the installation, try checking the "
+"integrity of the CD-ROM using the option near the bottom of the installer's "
+"main menu. This option can also be used as a general test if the CD-ROM can "
+"be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
-msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
+msgid ""
+"The biggest problem for people using floppy disks to install &debian; seems "
+"to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
-msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
+msgid ""
+"The boot floppy is the floppy with the worst problems, because it is read by "
+"the hardware directly, before Linux boots. Often, the hardware doesn't read "
+"as reliably as the Linux floppy disk driver, and may just stop without "
+"printing an error message if it reads incorrect data. There can also be "
+"failures in the driver floppies, most of which indicate themselves with a "
+"flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
-msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
+msgid ""
+"If you are having the installation stall at a particular floppy, the first "
+"thing you should do is write the image to a <emphasis>different</emphasis> "
+"floppy and see if that solves the problem. Simply reformatting the old "
+"floppy may not be sufficient, even if it appears that the floppy was "
+"reformatted and written with no errors. It is sometimes useful to try "
+"writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
-msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
+msgid ""
+"One user reports he had to write the images to floppy <emphasis>three</"
+"emphasis> times before one worked, and then everything was fine with the "
+"third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
-msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
+msgid ""
+"Normally you should not have to download a floppy image again, but if you "
+"are experiencing problems it is always useful to verify that the images were "
+"downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
-msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
+msgid ""
+"Other users have reported that simply rebooting a few times with the same "
+"floppy in the floppy drive can lead to a successful boot. This is all due to "
+"buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
-msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
+msgid ""
+"If you have problems and the kernel hangs during the boot process, doesn't "
+"recognize peripherals you actually have, or drives are not recognized "
+"properly, the first thing to check is the boot parameters, as discussed in "
+"<xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
-msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
+msgid ""
+"In some cases, malfunctions can be caused by missing device firmware (see "
+"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
+">)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
-msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
+msgid ""
+"If software speech synthesis does not work, there is most probably an issue "
+"with your sound board, usually because either the driver for it is not "
+"included in the installer, or because it has unusual mixer level names which "
+"are set to muted by default. You should thus submit a bug report which "
+"includes the output of the following commands, run on the same machine from "
+"a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
-msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
+msgid ""
+"There are some common installation problems that can be solved or avoided by "
+"passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
-msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
+msgid ""
+"If your screen begins to show a weird picture while the kernel boots, eg. "
+"pure white, pure black or colored pixel garbage, your system may contain a "
+"problematic video card which does not switch to the framebuffer mode "
+"properly. Then you can use the boot parameter <userinput>fb=false</"
+"userinput> to disable the framebuffer console. Only a reduced set of "
+"languages will be available during the installation due to limited console "
+"features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
-msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
+msgid ""
+"Some very old laptop models produced by Dell are known to crash when PCMCIA "
+"device detection tries to access some hardware addresses. Other laptops may "
+"display similar problems. If you experience such a problem and you don't "
+"need PCMCIA support during the installation, you can disable PCMCIA using "
+"the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
+"can then configure PCMCIA after the installation is completed and exclude "
+"the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
-msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
+msgid ""
+"Alternatively, you can boot the installer in expert mode. You will then be "
+"asked to enter the resource range options your hardware needs. For example, "
+"if you have one of the Dell laptops mentioned above, you should enter "
+"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
+"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
+"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
+"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
+"commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
-      "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
-      "Remapping the kernel... done\n"
-      "Booting Linux...\n"
-      "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>."
+"It is fairly common for &arch-title; to have two video cards in one machine, "
+"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
+"in the video output getting misdirected soon after the system boots. In "
+"typical cases, the display will only show: <informalexample><screen>\n"
+"Remapping the kernel... done\n"
+"Booting Linux...\n"
+"</screen></informalexample> To work around this, you can either pull out one "
+"of the video cards, or disable the one not used during the OpenProm boot "
+"phase using a kernel parameter. For example, to disable an ATI card, you "
+"should boot the installer with <userinput>video=atyfb:off</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
-msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"Note that you may also have to manually add this parameter to the silo "
+"configuration (edit <filename>/target/etc/silo.conf</filename> before "
+"rebooting) and, if you installed X11, modify the video driver in <filename>/"
+"etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
-msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
+msgid ""
+"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
+"they do boot, there may be inexplicable failures during the installation. "
+"Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
-msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
+msgid ""
+"During the boot sequence, you may see many messages in the form "
+"<computeroutput>can't find <replaceable>something</replaceable></"
+"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
+"present</computeroutput>, <computeroutput>can't initialize "
+"<replaceable>something</replaceable></computeroutput>, or even "
+"<computeroutput>this driver release depends on <replaceable>something</"
+"replaceable></computeroutput>. Most of these messages are harmless. You see "
+"them because the kernel for the installation system is built to run on "
+"computers with many different peripheral devices. Obviously, no one computer "
+"will have every possible peripheral device, so the operating system may emit "
+"a few complaints while it looks for peripherals you don't own. You may also "
+"see the system pause for a while. This happens when it is waiting for a "
+"device to respond, and that device is not present on your system. If you "
+"find the time it takes to boot the system unacceptably long, you can create "
+"a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
+"baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
-msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
+msgid ""
+"If you get through the initial boot phase but cannot complete the install, "
+"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
+"It lets you store system error logs and configuration information from the "
+"installer to a floppy, or download them using a web browser. This "
+"information may provide clues as to what went wrong and how to fix it. If "
+"you are submitting a bug report, you may want to attach this information to "
+"the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
-msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"Other pertinent installation messages may be found in <filename>/var/log/</"
+"filename> during the installation, and <filename>/var/log/installer/</"
+"filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
-msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
+msgid ""
+"If you still have problems, please submit an installation report. We also "
+"encourage installation reports to be sent even if the installation is "
+"successful, so that we can get as much information as possible on the "
+"largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
-msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
+msgid ""
+"Note that your installation report will be published in the Debian Bug "
+"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
+"you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
-msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
+msgid ""
+"If you have a working &debian; system, the easiest way to send an "
+"installation report is to install the <classname>installation-report</"
+"classname> and <classname>reportbug</classname> packages (<command>aptitude "
+"install installation-report reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run the command <command>reportbug installation-reports</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
-      "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
-      "Package: installation-reports\n"
-      "\n"
-      "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
-      "Image version: &lt;Full URL to image you downloaded is best&gt;\n"
-      "Date: &lt;Date and time of the install&gt;\n"
-      "\n"
-      "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
-      "Processor:\n"
-      "Memory:\n"
-      "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
-      "\n"
-      "Output of lspci -knn (or lspci -nn):\n"
-      "\n"
-      "Base System Installation Checklist:\n"
-      "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
-      "\n"
-      "Initial boot:           [ ]\n"
-      "Detect network card:    [ ]\n"
-      "Configure network:      [ ]\n"
-      "Detect CD:              [ ]\n"
-      "Load installer modules: [ ]\n"
-      "Detect hard drives:     [ ]\n"
-      "Partition hard drives:  [ ]\n"
-      "Install base system:    [ ]\n"
-      "Clock/timezone setup:   [ ]\n"
-      "User/password setup:    [ ]\n"
-      "Install tasks:          [ ]\n"
-      "Install boot loader:    [ ]\n"
-      "Overall install:        [ ]\n"
-      "\n"
-      "Comments/Problems:\n"
-      "\n"
-      "&lt;Description of the install, in prose, and any thoughts, comments\n"
-      "      and ideas you had during the initial install.&gt;\n"
-      "</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state."
+"Alternatively you can use this template when filling out installation "
+"reports, and file the report as a bug report against the "
+"<classname>installation-reports</classname> pseudo package, by sending it to "
+"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
+"Package: installation-reports\n"
+"\n"
+"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
+"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
+"Date: &lt;Date and time of the install&gt;\n"
+"\n"
+"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
+"Processor:\n"
+"Memory:\n"
+"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
+"\n"
+"Output of lspci -knn (or lspci -nn):\n"
+"\n"
+"Base System Installation Checklist:\n"
+"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
+"\n"
+"Initial boot:           [ ]\n"
+"Detect network card:    [ ]\n"
+"Configure network:      [ ]\n"
+"Detect CD:              [ ]\n"
+"Load installer modules: [ ]\n"
+"Detect hard drives:     [ ]\n"
+"Partition hard drives:  [ ]\n"
+"Install base system:    [ ]\n"
+"Clock/timezone setup:   [ ]\n"
+"User/password setup:    [ ]\n"
+"Install tasks:          [ ]\n"
+"Install boot loader:    [ ]\n"
+"Overall install:        [ ]\n"
+"\n"
+"Comments/Problems:\n"
+"\n"
+"&lt;Description of the install, in prose, and any thoughts, comments\n"
+"      and ideas you had during the initial install.&gt;\n"
+"</screen></informalexample> In the bug report, describe what the problem is, "
+"including the last visible kernel messages in the event of a kernel hang. "
+"Describe the steps that you did which brought the system into the problem "
+"state."
 msgstr ""
-
diff --git a/po/ro/boot-new.po b/po/ro/boot-new.po
index 202d93271..f4d294cfc 100644
--- a/po/ro/boot-new.po
+++ b/po/ro/boot-new.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,31 +29,59 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:8
 #, no-c-format
-msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>."
+msgid ""
+"Your system's first boot on its own power is what electrical engineers call "
+"the <quote>smoke test</quote>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:13
 #, no-c-format
-msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new &debian; system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu."
+msgid ""
+"If you did a default installation, the first thing you should see when you "
+"boot the system is the menu of the <classname>grub</classname><phrase arch="
+"\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. "
+"The first choices in the menu will be for your new &debian; system. If you "
+"had any other operating systems on your computer (like Windows) that were "
+"detected by the installation system, those will be listed lower down in the "
+"menu."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:23
 #, no-c-format
-msgid "If the system fails to start up correctly, don't panic. If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting &debian;. In most cases such problems can be fixed without having to repeat the installation. One available option to fix boot problems is to use the installer's built-in rescue mode (see <xref linkend=\"rescue\"/>)."
+msgid ""
+"If the system fails to start up correctly, don't panic. If the installation "
+"was successful, chances are good that there is only a relatively minor "
+"problem that is preventing the system from booting &debian;. In most cases "
+"such problems can be fixed without having to repeat the installation. One "
+"available option to fix boot problems is to use the installer's built-in "
+"rescue mode (see <xref linkend=\"rescue\"/>)."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:32
 #, no-c-format
-msgid "If you are new to &debian; and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue."
+msgid ""
+"If you are new to &debian; and &arch-kernel;, you may need some help from "
+"more experienced users. <phrase arch=\"x86\">For direct on-line help you can "
+"try the IRC channels #debian or #debian-boot on the OFTC network. "
+"Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-"
+"user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common "
+"architectures like &arch-title;, your best option is to ask on the <ulink "
+"url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</"
+"phrase> You can also file an installation report as described in <xref "
+"linkend=\"submit-bug\"/>. Please make sure that you describe your problem "
+"clearly and include any messages that are displayed and may help others to "
+"diagnose the issue."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:48
 #, no-c-format
-msgid "If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report."
+msgid ""
+"If you had any other operating systems on your computer that were not "
+"detected or not detected correctly, please file an installation report."
 msgstr ""
 
 #. Tag: title
@@ -64,19 +93,42 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:57
 #, no-c-format
-msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
+msgid ""
+"If the machine fails to boot after completing the installation, and stops "
+"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</"
+"userinput> followed by &enterkey;. (The default boot configuration in "
+"<filename>quik.conf</filename> is labeled Linux). The labels defined in "
+"<filename>quik.conf</filename> will be displayed if you press the "
+"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also "
+"try booting back into the installer, and editing the <filename>/target/etc/"
+"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard "
+"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are "
+"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:71
 #, no-c-format
-msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"To boot back into MacOS without resetting the nvram, type <userinput>bye</"
+"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed "
+"from the machine). To obtain an OpenFirmware prompt, hold down the "
+"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</"
+"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. "
+"If you need to reset the OpenFirmware nvram changes to the MacOS default in "
+"order to boot back to MacOS, hold down the <keycombo> <keycap>command</"
+"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </"
+"keycombo> keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:84
 #, no-c-format
-msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
+msgid ""
+"If you use <command>BootX</command> to boot into the installed system, just "
+"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
+"un-choose the ramdisk option, and add a root device corresponding to your "
+"installation; e.g. <userinput>/dev/hda8</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -88,31 +140,52 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:97
 #, no-c-format
-msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon."
+msgid ""
+"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key "
+"and get a graphical screen with a button for each bootable OS, &debian-gnu; "
+"will be a button with a small penguin icon."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:104
 #, no-c-format
-msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-"
+"device</envar> variable you should reset OpenFirmware to its default "
+"configuration. To do this hold down the <keycombo> <keycap>command</keycap> "
+"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> "
+"keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:112
 #, no-c-format
-msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
+msgid ""
+"The labels defined in <filename>yaboot.conf</filename> will be displayed if "
+"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:118
 #, no-c-format
-msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
+msgid ""
+"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-"
+"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap "
+"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an "
+"IDE disk this may not work and you will have to enter OpenFirmware and set "
+"the <envar>boot-device</envar> variable, <command>ybin</command> normally "
+"does this automatically."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:127
 #, no-c-format
-msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
+msgid ""
+"After you boot &debian-gnu; for the first time you can add any additional "
+"options you desire (such as dual boot options) to <filename>/etc/yaboot."
+"conf</filename> and run <command>ybin</command> to update your boot "
+"partition with the changed configuration. Please read the <ulink url=\"&url-"
+"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
 msgstr ""
 
 #. Tag: title
@@ -124,7 +197,11 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:147
 #, no-c-format
-msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
+msgid ""
+"If you created encrypted volumes during the installation and assigned them "
+"mount points, you will be asked to enter the passphrase for each of these "
+"volumes during the boot. The actual procedure differs slightly between dm-"
+"crypt and loop-AES."
 msgstr ""
 
 #. Tag: title
@@ -137,31 +214,54 @@ msgstr ""
 #: boot-new.xml:159
 #, no-c-format
 msgid ""
-      "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
-      "Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
-      "Enter LUKS passphrase:\n"
-      "</screen></informalexample> In the first line of the prompt, <replaceable>part</replaceable> is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename><replaceable>part</replaceable>_crypt</filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system."
+"For partitions encrypted using dm-crypt you will be shown the following "
+"prompt during the boot: <informalexample><screen>\n"
+"Starting early crypto disks... <replaceable>part</replaceable>_crypt"
+"(starting)\n"
+"Enter LUKS passphrase:\n"
+"</screen></informalexample> In the first line of the prompt, "
+"<replaceable>part</replaceable> is the name of the underlying partition, e."
+"g. sda2 or md0. You are now probably wondering <emphasis>for which volume</"
+"emphasis> you are actually entering the passphrase. Does it relate to your "
+"<filename>/home</filename>? Or to <filename>/var</filename>? Of course, if "
+"you have just one encrypted volume, this is easy and you can just enter the "
+"passphrase you used when setting up this volume. If you set up more than one "
+"encrypted volume during the installation, the notes you wrote down as the "
+"last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did "
+"not make a note of the mapping between <filename><replaceable>part</"
+"replaceable>_crypt</filename> and the mount points before, you can still "
+"find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</"
+"filename> of your new system."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:182
 #, no-c-format
-msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
+msgid ""
+"The prompt may look somewhat different when an encrypted root file system is "
+"mounted. This depends on which initramfs generator was used to generate the "
+"initrd used to boot the system. The example below is for an initrd generated "
+"using <classname>initramfs-tools</classname>:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:189
 #, no-c-format
 msgid ""
-      "Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
-      "Begin: Running /scripts/local-top ...\n"
-      "Enter LUKS passphrase:"
+"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
+"Begin: Running /scripts/local-top ...\n"
+"Enter LUKS passphrase:"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:191 boot-new.xml:216
 #, no-c-format
-msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
+msgid ""
+"No characters (even asterisks) will be shown while entering the passphrase. "
+"If you enter the wrong passphrase, you have two more tries to correct it. "
+"After the third try the boot process will skip this volume and continue to "
+"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting"
+"\"/> for further information."
 msgstr ""
 
 #. Tag: para
@@ -179,16 +279,19 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:209
 #, no-c-format
-msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
+msgid ""
+"For partitions encrypted using loop-AES you will be shown the following "
+"prompt during the boot:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:214
 #, no-c-format
 msgid ""
-      "Checking loop-encrypted file systems.\n"
-      "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
-      "Password:"
+"Checking loop-encrypted file systems.\n"
+"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</"
+"replaceable>)\n"
+"Password:"
 msgstr ""
 
 #. Tag: title
@@ -200,47 +303,77 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:234
 #, no-c-format
-msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
+msgid ""
+"If some of the encrypted volumes could not be mounted because a wrong "
+"passphrase was entered, you will have to mount them manually after the boot. "
+"There are several cases."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:243
 #, no-c-format
-msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
+msgid ""
+"The first case concerns the root partition. When it is not mounted "
+"correctly, the boot process will halt and you will have to reboot the "
+"computer to try again."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:250
 #, no-c-format
 msgid ""
-      "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
-      "<prompt>Password:</prompt>\n"
-      "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
+"The easiest case is for encrypted volumes holding data like <filename>/home</"
+"filename> or <filename>/srv</filename>. You can simply mount them manually "
+"after the boot. For loop-AES this is a one-step operation: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>\n"
+"<prompt>Password:</prompt>\n"
+"</screen></informalexample> where <replaceable>/mount_point</replaceable> "
+"should be replaced by the particular directory (e.g. <filename>/home</"
+"filename>). The only difference from an ordinary mount is that you will be "
+"asked to enter the passphrase for this volume."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:264
 #, no-c-format
 msgid ""
-      "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-      "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
+"For dm-crypt this is a bit trickier. First you need to register the volumes "
+"with <application>device mapper</application> by running: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
+"</screen></informalexample> This will scan all volumes mentioned in "
+"<filename>/etc/crypttab</filename> and will create appropriate devices under "
+"the <filename>/dev</filename> directory after entering the correct "
+"passphrases. (Already registered volumes will be skipped, so you can repeat "
+"this command several times without worrying.) After successful registration "
+"you can simply mount the volumes the usual way:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:279
 #, no-c-format
-msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
+msgid ""
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:282
 #, no-c-format
 msgid ""
-      "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-      "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
+"If any volume holding noncritical system files could not be mounted "
+"(<filename>/usr</filename> or <filename>/var</filename>), the system should "
+"still boot and you should be able to mount the volumes manually like in the "
+"previous case. However, you will also need to (re)start any services usually "
+"running in your default runlevel because it is very likely that they were "
+"not started. The easiest way to achieve this is by switching to the first "
+"runlevel and back by entering <informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>init 1</userinput>\n"
+"</screen></informalexample> at the shell prompt and pressing <keycombo> "
+"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the "
+"root password."
 msgstr ""
 
 #. Tag: title
@@ -252,46 +385,81 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:307
 #, no-c-format
-msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
+msgid ""
+"Once your system boots, you'll be presented with the login prompt. Log in "
+"using the personal login and password you selected during the installation "
+"process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:313
 #, no-c-format
-msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
+msgid ""
+"If you are a new user, you may want to explore the documentation which is "
+"already installed on your system as you start to use it. There are currently "
+"several documentation systems, work is proceeding on integrating the "
+"different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:321
 #, no-c-format
-msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
+msgid ""
+"Documentation accompanying programs you have installed can be found in "
+"<filename>/usr/share/doc/</filename>, under a subdirectory named after the "
+"program (or, more precise, the &debian; package that contains the program). "
+"However, more extensive documentation is often packaged separately in "
+"special documentation packages that are mostly not installed by default. For "
+"example, documentation about the package management tool <command>apt</"
+"command> can be found in the packages <classname>apt-doc</classname> or "
+"<classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:332
 #, no-c-format
-msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
+msgid ""
+"In addition, there are some special folders within the <filename>/usr/share/"
+"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</"
+"emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</"
+"filename>. After installing <classname>dhelp</classname>, you will find a "
+"browsable index of documentation in <filename>/usr/share/doc/HTML/index."
+"html</filename>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:341
 #, no-c-format
 msgid ""
-      "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
-      "$ cd /usr/share/doc/\n"
-      "$ w3m .\n"
-      "</screen></informalexample> The dot after the <command>w3m</command> command tells it to show the contents of the current directory."
+"One easy way to view these documents using a text based browser is to enter "
+"the following commands: <informalexample><screen>\n"
+"$ cd /usr/share/doc/\n"
+"$ w3m .\n"
+"</screen></informalexample> The dot after the <command>w3m</command> command "
+"tells it to show the contents of the current directory."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:351
 #, no-c-format
-msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
+msgid ""
+"If you have a graphical desktop environment installed, you can also use its "
+"web browser. Start the web browser from the application menu and enter "
+"<userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:357
 #, no-c-format
-msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
+msgid ""
+"You can also type <userinput>info <replaceable>command</replaceable></"
+"userinput> or <userinput>man <replaceable>command</replaceable></userinput> "
+"to see documentation on most commands available at the command prompt. "
+"Typing <userinput>help</userinput> will display help on shell commands. And "
+"typing a command followed by <userinput>--help</userinput> will usually "
+"display a short summary of the command's usage. If a command's results "
+"scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> "
+"after the command to cause the results to pause before scrolling past the "
+"top of the screen. To see a list of all commands available which begin with "
+"a certain letter, type the letter and then two tabs."
 msgstr ""
-
diff --git a/po/ro/gpl.po b/po/ro/gpl.po
index 3582cbd8a..5f7616aa6 100644
--- a/po/ro/gpl.po
+++ b/po/ro/gpl.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,35 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:6
 #, no-c-format
-msgid "[[This note, consisting of two paragraphs, should only be included in your translation if you translate the GPL in this appendix. See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English name of your language. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[This note, consisting of two paragraphs, should only be included in your "
+"translation if you translate the GPL in this appendix. See build/lang-"
+"options/README on how to enable this paragraph and for additional "
+"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH "
+"IN ENGLISH! Only replace {language} with the English name of your language. "
+"Do not change the link to the GPL!]] This is an unofficial translation of "
+"the GNU General Public License into {language}. It was not published by the "
+"Free Software Foundation, and does not legally state the distribution terms "
+"for software that uses the GNU GPL &mdash; only the original <ulink url="
+"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. "
+"However, we hope that this translation will help {language} speakers to "
+"better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:22
 #, no-c-format
-msgid "[[See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of your language before translating. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[See build/lang-options/README on how to enable this paragraph and for "
+"additional information. Its condition is \"gpl-unofficial\".]] [[THIS "
+"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of "
+"your language before translating. Do not change the link to the GPL!]] This "
+"is an unofficial translation of the GNU General Public License into "
+"{language}. It was not published by the Free Software Foundation, and does "
+"not legally state the distribution terms for software that uses the GNU GPL "
+"&mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</"
+"ulink> of the GNU GPL does that. However, we hope that this translation will "
+"help {language} speakers to better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
@@ -41,11 +64,11 @@ msgstr ""
 #: gpl.xml:41
 #, no-c-format
 msgid ""
-      "Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
-      "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
-      "\n"
-      "Everyone is permitted to copy and distribute verbatim copies\n"
-      "of this license document, but changing it is not allowed."
+"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
+"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
+"\n"
+"Everyone is permitted to copy and distribute verbatim copies\n"
+"of this license document, but changing it is not allowed."
 msgstr ""
 
 #. Tag: title
@@ -57,49 +80,87 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:46
 #, no-c-format
-msgid "The licenses for most software are designed to take away your freedom to share and change it. By contrast, the gnu General Public License is intended to guarantee your freedom to share and change free software &mdash; to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the gnu Library General Public License instead.) You can apply it to your programs, too."
+msgid ""
+"The licenses for most software are designed to take away your freedom to "
+"share and change it. By contrast, the gnu General Public License is intended "
+"to guarantee your freedom to share and change free software &mdash; to make "
+"sure the software is free for all its users. This General Public License "
+"applies to most of the Free Software Foundation's software and to any other "
+"program whose authors commit to using it. (Some other Free Software "
+"Foundation software is covered by the gnu Library General Public License "
+"instead.) You can apply it to your programs, too."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:58
 #, no-c-format
-msgid "When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+msgid ""
+"When we speak of free software, we are referring to freedom, not price. Our "
+"General Public Licenses are designed to make sure that you have the freedom "
+"to distribute copies of free software (and charge for this service if you "
+"wish), that you receive source code or can get it if you want it, that you "
+"can change the software or use pieces of it in new free programs; and that "
+"you know you can do these things."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:68
 #, no-c-format
-msgid "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it."
+msgid ""
+"To protect your rights, we need to make restrictions that forbid anyone to "
+"deny you these rights or to ask you to surrender the rights. These "
+"restrictions translate to certain responsibilities for you if you distribute "
+"copies of the software, or if you modify it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:75
 #, no-c-format
-msgid "For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
+msgid ""
+"For example, if you distribute copies of such a program, whether gratis or "
+"for a fee, you must give the recipients all the rights that you have. You "
+"must make sure that they, too, receive or can get the source code. And you "
+"must show them these terms so they know their rights."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:83
 #, no-c-format
-msgid "We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
+msgid ""
+"We protect your rights with two steps: (1) copyright the software, and (2) "
+"offer you this license which gives you legal permission to copy, distribute "
+"and/or modify the software."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:89
 #, no-c-format
-msgid "Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations."
+msgid ""
+"Also, for each author's protection and ours, we want to make certain that "
+"everyone understands that there is no warranty for this free software. If "
+"the software is modified by someone else and passed on, we want its "
+"recipients to know that what they have is not the original, so that any "
+"problems introduced by others will not reflect on the original authors' "
+"reputations."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:98
 #, no-c-format
-msgid "Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."
+msgid ""
+"Finally, any free program is threatened constantly by software patents. We "
+"wish to avoid the danger that redistributors of a free program will "
+"individually obtain patent licenses, in effect making the program "
+"proprietary. To prevent this, we have made it clear that any patent must be "
+"licensed for everyone's free use or not licensed at all."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:107
 #, no-c-format
-msgid "The precise terms and conditions for copying, distribution and modification follow."
+msgid ""
+"The precise terms and conditions for copying, distribution and modification "
+"follow."
 msgstr ""
 
 #. Tag: title
@@ -117,163 +178,327 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:121
 #, no-c-format
-msgid "<emphasis role=\"bold\">0.</emphasis> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \"Program\", below, refers to any such program or work, and a \"work based on the Program\" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \"modification\".) Each licensee is addressed as \"you\"."
+msgid ""
+"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or "
+"other work which contains a notice placed by the copyright holder saying it "
+"may be distributed under the terms of this General Public License. The "
+"\"Program\", below, refers to any such program or work, and a \"work based "
+"on the Program\" means either the Program or any derivative work under "
+"copyright law: that is to say, a work containing the Program or a portion of "
+"it, either verbatim or with modifications and/or translated into another "
+"language. (Hereinafter, translation is included without limitation in the "
+"term \"modification\".) Each licensee is addressed as \"you\"."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:134
 #, no-c-format
-msgid "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
+msgid ""
+"Activities other than copying, distribution and modification are not covered "
+"by this License; they are outside its scope. The act of running the Program "
+"is not restricted, and the output from the Program is covered only if its "
+"contents constitute a work based on the Program (independent of having been "
+"made by running the Program). Whether that is true depends on what the "
+"Program does."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:143
 #, no-c-format
-msgid "<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program."
+msgid ""
+"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim "
+"copies of the Program's source code as you receive it, in any medium, "
+"provided that you conspicuously and appropriately publish on each copy an "
+"appropriate copyright notice and disclaimer of warranty; keep intact all the "
+"notices that refer to this License and to the absence of any warranty; and "
+"give any other recipients of the Program a copy of this License along with "
+"the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:154
 #, no-c-format
-msgid "You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
+msgid ""
+"You may charge a fee for the physical act of transferring a copy, and you "
+"may at your option offer warranty protection in exchange for a fee."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:160
 #, no-c-format
-msgid "<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:"
+msgid ""
+"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of "
+"the Program or any portion of it, thus forming a work based on the Program, "
+"and copy and distribute such modifications or work under the terms of "
+"Section 1 above, provided that you also meet all of these conditions:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:169
 #, no-c-format
-msgid "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."
+msgid ""
+"You must cause the modified files to carry prominent notices stating that "
+"you changed the files and the date of any change."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:175
 #, no-c-format
-msgid "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License."
+msgid ""
+"You must cause any work that you distribute or publish, that in whole or in "
+"part contains or is derived from the Program or any part thereof, to be "
+"licensed as a whole at no charge to all third parties under the terms of "
+"this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:183
 #, no-c-format
-msgid "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
+msgid ""
+"If the modified program normally reads commands interactively when run, you "
+"must cause it, when started running for such interactive use in the most "
+"ordinary way, to print or display an announcement including an appropriate "
+"copyright notice and a notice that there is no warranty (or else, saying "
+"that you provide a warranty) and that users may redistribute the program "
+"under these conditions, and telling the user how to view a copy of this "
+"License. (Exception: if the Program itself is interactive but does not "
+"normally print such an announcement, your work based on the Program is not "
+"required to print an announcement.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:197
 #, no-c-format
-msgid "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
+msgid ""
+"These requirements apply to the modified work as a whole. If identifiable "
+"sections of that work are not derived from the Program, and can be "
+"reasonably considered independent and separate works in themselves, then "
+"this License, and its terms, do not apply to those sections when you "
+"distribute them as separate works. But when you distribute the same sections "
+"as part of a whole which is a work based on the Program, the distribution of "
+"the whole must be on the terms of this License, whose permissions for other "
+"licensees extend to the entire whole, and thus to each and every part "
+"regardless of who wrote it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:210
 #, no-c-format
-msgid "Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program."
+msgid ""
+"Thus, it is not the intent of this section to claim rights or contest your "
+"rights to work written entirely by you; rather, the intent is to exercise "
+"the right to control the distribution of derivative or collective works "
+"based on the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:217
 #, no-c-format
-msgid "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
+msgid ""
+"In addition, mere aggregation of another work not based on the Program with "
+"the Program (or with a work based on the Program) on a volume of a storage "
+"or distribution medium does not bring the other work under the scope of this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:224
 #, no-c-format
-msgid "<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:"
+msgid ""
+"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the "
+"Program (or a work based on it, under Section 2) in object code or "
+"executable form under the terms of Sections 1 and 2 above provided that you "
+"also do one of the following:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:233
 #, no-c-format
-msgid "Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with the complete corresponding machine-readable source code, "
+"which must be distributed under the terms of Sections 1 and 2 above on a "
+"medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:241
 #, no-c-format
-msgid "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with a written offer, valid for at least three years, to give "
+"any third party, for a charge no more than your cost of physically "
+"performing source distribution, a complete machine-readable copy of the "
+"corresponding source code, to be distributed under the terms of Sections 1 "
+"and 2 above on a medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:251
 #, no-c-format
-msgid "Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)"
+msgid ""
+"Accompany it with the information you received as to the offer to distribute "
+"corresponding source code. (This alternative is allowed only for "
+"noncommercial distribution and only if you received the program in object "
+"code or executable form with such an offer, in accord with Subsection b "
+"above.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:260
 #, no-c-format
-msgid "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."
+msgid ""
+"The source code for a work means the preferred form of the work for making "
+"modifications to it. For an executable work, complete source code means all "
+"the source code for all modules it contains, plus any associated interface "
+"definition files, plus the scripts used to control compilation and "
+"installation of the executable. However, as a special exception, the source "
+"code distributed need not include anything that is normally distributed (in "
+"either source or binary form) with the major components (compiler, kernel, "
+"and so on) of the operating system on which the executable runs, unless that "
+"component itself accompanies the executable."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:273
 #, no-c-format
-msgid "If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code."
+msgid ""
+"If distribution of executable or object code is made by offering access to "
+"copy from a designated place, then offering equivalent access to copy the "
+"source code from the same place counts as distribution of the source code, "
+"even though third parties are not compelled to copy the source along with "
+"the object code."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:281
 #, no-c-format
-msgid "<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."
+msgid ""
+"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, "
+"or distribute the Program except as expressly provided under this License. "
+"Any attempt otherwise to copy, modify, sublicense or distribute the Program "
+"is void, and will automatically terminate your rights under this License. "
+"However, parties who have received copies, or rights, from you under this "
+"License will not have their licenses terminated so long as such parties "
+"remain in full compliance."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:292
 #, no-c-format
-msgid "<emphasis role=\"bold\">5.</emphasis> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
+msgid ""
+"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this "
+"License, since you have not signed it. However, nothing else grants you "
+"permission to modify or distribute the Program or its derivative works. "
+"These actions are prohibited by law if you do not accept this License. "
+"Therefore, by modifying or distributing the Program (or any work based on "
+"the Program), you indicate your acceptance of this License to do so, and all "
+"its terms and conditions for copying, distributing or modifying the Program "
+"or works based on it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:304
 #, no-c-format
-msgid "<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."
+msgid ""
+"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program "
+"(or any work based on the Program), the recipient automatically receives a "
+"license from the original licensor to copy, distribute or modify the Program "
+"subject to these terms and conditions. You may not impose any further "
+"restrictions on the recipients' exercise of the rights granted herein. You "
+"are not responsible for enforcing compliance by third parties to this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:315
 #, no-c-format
-msgid "<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
+msgid ""
+"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court "
+"judgment or allegation of patent infringement or for any other reason (not "
+"limited to patent issues), conditions are imposed on you (whether by court "
+"order, agreement or otherwise) that contradict the conditions of this "
+"License, they do not excuse you from the conditions of this License. If you "
+"cannot distribute so as to satisfy simultaneously your obligations under "
+"this License and any other pertinent obligations, then as a consequence you "
+"may not distribute the Program at all. For example, if a patent license "
+"would not permit royalty-free redistribution of the Program by all those who "
+"receive copies directly or indirectly through you, then the only way you "
+"could satisfy both it and this License would be to refrain entirely from "
+"distribution of the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:332
 #, no-c-format
-msgid "If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances."
+msgid ""
+"If any portion of this section is held invalid or unenforceable under any "
+"particular circumstance, the balance of the section is intended to apply and "
+"the section as a whole is intended to apply in other circumstances."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:339
 #, no-c-format
-msgid "It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
+msgid ""
+"It is not the purpose of this section to induce you to infringe any patents "
+"or other property right claims or to contest validity of any such claims; "
+"this section has the sole purpose of protecting the integrity of the free "
+"software distribution system, which is implemented by public license "
+"practices. Many people have made generous contributions to the wide range of "
+"software distributed through that system in reliance on consistent "
+"application of that system; it is up to the author/donor to decide if he or "
+"she is willing to distribute software through any other system and a "
+"licensee cannot impose that choice."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:352
 #, no-c-format
-msgid "This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License."
+msgid ""
+"This section is intended to make thoroughly clear what is believed to be a "
+"consequence of the rest of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:357
 #, no-c-format
-msgid "<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License."
+msgid ""
+"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the "
+"Program is restricted in certain countries either by patents or by "
+"copyrighted interfaces, the original copyright holder who places the Program "
+"under this License may add an explicit geographical distribution limitation "
+"excluding those countries, so that distribution is permitted only in or "
+"among countries not thus excluded. In such case, this License incorporates "
+"the limitation as if written in the body of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:368
 #, no-c-format
-msgid "<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \"any later version\", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
+msgid ""
+"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may "
+"publish revised and/or new versions of the General Public License from time "
+"to time. Such new versions will be similar in spirit to the present version, "
+"but may differ in detail to address new problems or concerns. Each version "
+"is given a distinguishing version number. If the Program specifies a version "
+"number of this License which applies to it and \"any later version\", you "
+"have the option of following the terms and conditions either of that version "
+"or of any later version published by the Free Software Foundation. If the "
+"Program does not specify a version number of this License, you may choose "
+"any version ever published by the Free Software Foundation."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:383
 #, no-c-format
-msgid "<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally."
+msgid ""
+"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of "
+"the Program into other free programs whose distribution conditions are "
+"different, write to the author to ask for permission. For software which is "
+"copyrighted by the Free Software Foundation, write to the Free Software "
+"Foundation; we sometimes make exceptions for this. Our decision will be "
+"guided by the two goals of preserving the free status of all derivatives of "
+"our free software and of promoting the sharing and reuse of software "
+"generally."
 msgstr ""
 
 #. Tag: emphasis
@@ -285,13 +510,31 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:399
 #, no-c-format
-msgid "<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION."
+msgid ""
+"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE "
+"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY "
+"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT "
+"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY "
+"OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE "
+"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. "
+"THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH "
+"YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL "
+"NECESSARY SERVICING, REPAIR OR CORRECTION."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:412
 #, no-c-format
-msgid "<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgid ""
+"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY "
+"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY "
+"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED "
+"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, "
+"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO "
+"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING "
+"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE "
+"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR "
+"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
 msgstr ""
 
 #. Tag: emphasis
@@ -309,87 +552,111 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:434
 #, no-c-format
-msgid "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."
+msgid ""
+"If you develop a new program, and you want it to be of the greatest possible "
+"use to the public, the best way to achieve this is to make it free software "
+"which everyone can redistribute and change under these terms."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:441
 #, no-c-format
-msgid "To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \"copyright\" line and a pointer to where the full notice is found."
+msgid ""
+"To do so, attach the following notices to the program. It is safest to "
+"attach them to the start of each source file to most effectively convey the "
+"exclusion of warranty; and each file should have at least the \"copyright\" "
+"line and a pointer to where the full notice is found."
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:448
 #, no-c-format
 msgid ""
-      "<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable>\n"
-      "Copyright (C) <replaceable>year  name of author</replaceable>\n"
-      "\n"
-      "This program is free software; you can redistribute it and/or\n"
-      "modify it under the terms of the GNU General Public License\n"
-      "as published by the Free Software Foundation; either version 2\n"
-      "of the License, or (at your option) any later version.\n"
-      "\n"
-      "This program is distributed in the hope that it will be useful,\n"
-      "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
-      "MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
-      "GNU General Public License for more details.\n"
-      "\n"
-      "You should have received a copy of the GNU General Public License\n"
-      "along with this program; if not, write to the Free Software\n"
-      "Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA."
+"<replaceable>one line to give the program's name and a brief idea of what it "
+"does.</replaceable>\n"
+"Copyright (C) <replaceable>year  name of author</replaceable>\n"
+"\n"
+"This program is free software; you can redistribute it and/or\n"
+"modify it under the terms of the GNU General Public License\n"
+"as published by the Free Software Foundation; either version 2\n"
+"of the License, or (at your option) any later version.\n"
+"\n"
+"This program is distributed in the hope that it will be useful,\n"
+"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
+"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
+"GNU General Public License for more details.\n"
+"\n"
+"You should have received a copy of the GNU General Public License\n"
+"along with this program; if not, write to the Free Software\n"
+"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, "
+"USA."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:450
 #, no-c-format
-msgid "Also add information on how to contact you by electronic and paper mail."
+msgid ""
+"Also add information on how to contact you by electronic and paper mail."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:455
 #, no-c-format
-msgid "If the program is interactive, make it output a short notice like this when it starts in an interactive mode:"
+msgid ""
+"If the program is interactive, make it output a short notice like this when "
+"it starts in an interactive mode:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:460
 #, no-c-format
 msgid ""
-      "Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable>\n"
-      "Gnomovision comes with absolutely no warranty; for details\n"
-      "type `show w'. This is free software, and you are welcome\n"
-      "to redistribute it under certain conditions; type `show c'\n"
-      "for details."
+"Gnomovision version 69, Copyright (C) <replaceable>year name of author</"
+"replaceable>\n"
+"Gnomovision comes with absolutely no warranty; for details\n"
+"type `show w'. This is free software, and you are welcome\n"
+"to redistribute it under certain conditions; type `show c'\n"
+"for details."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:462
 #, no-c-format
-msgid "The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items &mdash; whatever suits your program."
+msgid ""
+"The hypothetical commands `show w' and `show c' should show the appropriate "
+"parts of the General Public License. Of course, the commands you use may be "
+"called something other than `show w' and `show c'; they could even be mouse-"
+"clicks or menu items &mdash; whatever suits your program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:470
 #, no-c-format
-msgid "You should also get your employer (if you work as a programmer) or your school, if any, to sign a \"copyright disclaimer\" for the program, if necessary. Here is a sample; alter the names:"
+msgid ""
+"You should also get your employer (if you work as a programmer) or your "
+"school, if any, to sign a \"copyright disclaimer\" for the program, if "
+"necessary. Here is a sample; alter the names:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:476
 #, no-c-format
 msgid ""
-      "Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
-      "program `Gnomovision' (which makes passes at compilers) written\n"
-      "by James Hacker.\n"
-      "\n"
-      "<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
-      "Ty Coon, President of Vice"
+"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
+"program `Gnomovision' (which makes passes at compilers) written\n"
+"by James Hacker.\n"
+"\n"
+"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
+"Ty Coon, President of Vice"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:478
 #, no-c-format
-msgid "This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
+msgid ""
+"This General Public License does not permit incorporating your program into "
+"proprietary programs. If your program is a subroutine library, you may "
+"consider it more useful to permit linking proprietary applications with the "
+"library. If this is what you want to do, use the GNU Lesser General Public "
+"License instead of this License."
 msgstr ""
-
diff --git a/po/ro/hardware.po b/po/ro/hardware.po
index c3e0c1251..96af36f01 100644
--- a/po/ro/hardware.po
+++ b/po/ro/hardware.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:7
 #, no-c-format
-msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;."
+msgid ""
+"This section contains information about what hardware you need to get "
+"started with &debian;. You will also find links to further information about "
+"hardware supported by GNU and &arch-kernel;."
 msgstr ""
 
 #. Tag: title
@@ -34,13 +38,23 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;."
+msgid ""
+"&debian; does not impose hardware requirements beyond the requirements of "
+"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
+"architecture or platform to which the Linux or kFreeBSD kernel, libc, "
+"<command>gcc</command>, etc. have been ported, and for which a &debian; port "
+"exists, can run &debian;. Please refer to the Ports pages at <ulink url="
+"\"&url-ports;\"></ulink> for more details on &arch-title; architecture "
+"systems which have been tested with &debian-gnu;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:32
 #, no-c-format
-msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found."
+msgid ""
+"Rather than attempting to describe all the different hardware configurations "
+"which are supported for &arch-title;, this section contains general "
+"information and pointers to where additional information can be found."
 msgstr ""
 
 #. Tag: title
@@ -52,7 +66,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid ""
+"&debian; GNU/Linux &release; supports eleven major architectures and several "
+"variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -430,19 +446,38 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:203
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are "
+"looking for information on any of the other &debian;-supported architectures "
+"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-"
+"Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
+msgid ""
+"The &arch-title; architecture only supports Intel Itanium processors and not "
+"the much more common 64-bit processors from the Intel 64 family (including e."
+"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
+"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
+"userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:223
 #, no-c-format
-msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
+msgid ""
+"This is the first official release of &debian-gnu; for the &arch-title; "
+"architecture. We feel that it has proven itself sufficiently to be released. "
+"However, because it has not had the exposure (and hence testing by users) "
+"that some other architectures have had, you may encounter a few bugs. Use "
+"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any "
+"problems; make sure to mention the fact that the bug is on the &arch-title; "
+"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
+"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
@@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
+#: hardware.xml:522 hardware.xml:575
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -466,13 +502,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:273
 #, no-c-format
-msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
+msgid ""
+"Each distinct ARM architecture requires its own kernel. Because of this the "
+"standard &debian; distribution only supports installation on a number of the "
+"most common platforms. The &debian; userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:282
 #, no-c-format
-msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
+msgid ""
+"Most ARM CPUs may be run in either endian mode (big or little). However, the "
+"majority of current system implementation uses little-endian mode. &debian; "
+"currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
@@ -490,7 +533,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:298
 #, no-c-format
-msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
+msgid ""
+"Intel's I/O Processor (IOP) line is found in a number of products related to "
+"data storage and processing. &debian; currently supports the IOP32x "
+"platform, featuring the IOP 80219 and 32x chips commonly found in Network "
+"Attached Storage (NAS) devices. &debian; explicitly supports two such "
+"devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from "
+"IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -502,7 +551,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:312
 #, no-c-format
-msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
+msgid ""
+"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
+"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
+"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
+"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
+"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
+"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
+"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
+"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
@@ -514,7 +571,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:329
 #, no-c-format
-msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
+msgid ""
+"Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, "
+"Ethernet, SATA, USB, and other functionality in one chip. There are many "
+"Network Attached Storage (NAS) devices on the market that are based on an "
+"Orion chip. We currently support the following Orion based devices: <ulink "
+"url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url="
+"\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
+"cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -526,19 +590,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:344
 #, no-c-format
-msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
+msgid ""
+"The Versatile platform is emulated by QEMU and is therefore a nice way to "
+"test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:363
 #, no-c-format
-msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
+msgid ""
+"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-"
+"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit "
+"processors whereas the 2.0 architecture is targeted to the 64-bit "
+"processors. Some systems are able to run either kernel. In both cases, the "
+"userland is 32-bit. There is the possibility of a 64-bit userland in the "
+"future."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:382
 #, no-c-format
-msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
+msgid ""
+"Complete information concerning supported peripherals can be found at <ulink "
+"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. "
+"This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
@@ -550,19 +625,43 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:391
 #, no-c-format
-msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
+msgid ""
+"Nearly all x86-based (IA-32) processors still in use in personal computers "
+"are supported, including all varieties of Intel's \"Pentium\" series. This "
+"also includes 32-bit AMD and VIA (former Cyrix) processors, and processors "
+"like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:398
 #, no-c-format
-msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
+msgid ""
+"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run "
+"on 386 or earlier processors. Despite the architecture name \"i386\", "
+"support for actual 80386 processors (and their clones) was dropped with the "
+"Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to "
+"avoid this, but in the end it was necessary due a unfortunate series of "
+"issues with the compiler and the kernel, starting with an bug in the C++ ABI "
+"provided by GCC. You should still be able to run &debian; GNU/Linux on "
+"actual 80386 processors if you compile your own kernel and compile all "
+"packages from source, but that is beyond the scope of this manual. </para> </"
+"footnote>. (No version of Linux has ever supported the 286 or earlier chips "
+"in the series.) All i486 and later processors are still supported<footnote> "
+"<para> Many &debian; packages will actually run slightly faster on modern "
+"computers as a positive side effect of dropping support for these old chips. "
+"The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) "
+"which the i386, introduced in 1986, did not have. Previously, these could "
+"not be easily used by most &debian; packages; now they can. </para> </"
+"footnote>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+msgid ""
+"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
+"you will probably want to use the installer for the amd64 architecture "
+"instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
@@ -574,31 +673,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:441
 #, no-c-format
-msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
+msgid ""
+"The system bus is the part of the motherboard which allows the CPU to "
+"communicate with peripherals such as storage devices. Your computer must use "
+"the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called "
+"the VL bus). Essentially all personal computers sold in recent years use one "
+"of these."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:465
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, "
+"Indigo 2 and Challenge S. Since these machines are very similar, whenever "
+"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant "
+"as well. </para></listitem> <listitem><para> SGI IP32: this platform is "
+"generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: "
+"this platform is emulated by QEMU and is therefore a nice way to test and "
+"run &debian; on MIPS if you don't have the hardware. </para></listitem> </"
+"itemizedlist> Complete information regarding supported mips/mipsel machines "
+"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</"
+"ulink>. In the following, only the systems supported by the &debian; "
+"installer will be covered. If you are looking for support for other "
+"subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> "
+"debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
+msgid ""
+"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and "
+"R5000 processors are supported by the &debian; installation system on big "
+"endian MIPS. On SGI IP32, currently only systems based on the R5000 are "
+"supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
+msgid ""
+"Some MIPS machines can be operated in both big and little endian mode. For "
+"little endian MIPS, please read the documentation for the mipsel "
+"architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:523
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are "
+"covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway "
+"Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform "
+"is emulated by QEMU and is therefore a nice way to test and run &debian; on "
+"MIPS if you don't have the hardware. </para></listitem> </itemizedlist> "
+"Complete information regarding supported mips/mipsel machines can be found "
+"at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the "
+"following, only the systems supported by the &debian; installer will be "
+"covered. If you are looking for support for other subarchitectures, please "
+"contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; "
+"mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -610,7 +747,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:553
 #, no-c-format
-msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
+msgid ""
+"All MIPS based Cobalt machines are supported with the exception of the Qube "
+"2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
@@ -628,7 +767,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:576
 #, no-c-format
-msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
+msgid ""
+"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
+"PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +781,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:599
 #, no-c-format
-msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
+msgid ""
+"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -652,7 +795,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:607
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid ""
+"Most systems use this kernel flavour, which supports the PowerPC 601, 603, "
+"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and "
+"including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
@@ -670,19 +816,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:622
 #, no-c-format
-msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
+msgid ""
+"The POWER3 processor is used in older IBM 64-bit server systems: known "
+"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, "
+"and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:628
 #, no-c-format
-msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
+msgid ""
+"The POWER4 processor is used in more recent IBM 64-bit server systems: known "
+"models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:633
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid ""
+"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
+"architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
@@ -694,25 +847,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:669
 #, no-c-format
-msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
+msgid ""
+"Apple (and briefly a few other manufacturers &mdash; Power Computing, for "
+"example) made a series of Macintosh computers based on the PowerPC "
+"processor. For purposes of architecture support, they are categorized as "
+"NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:676
 #, no-c-format
-msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
+msgid ""
+"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI "
+"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld "
+"machines. Those pre-iMac PowerPC models from Apple use a four digit naming "
+"scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:684
 #, no-c-format
-msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
+msgid ""
+"The so called NewWorld PowerMacs are any PowerMacs in translucent colored "
+"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, "
+"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. "
+"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</"
+"quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:692
 #, no-c-format
-msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
+msgid ""
+"Specifications for Apple hardware are available at <ulink url=\"http://www."
+"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older "
+"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/"
+"index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
@@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
+#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
+#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
+#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
+#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
+#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
+#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
+#: hardware.xml:825
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -1084,7 +1261,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:933
 #, no-c-format
-msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
+msgid ""
+"NuBus systems are not currently supported by &debian;/powerpc. The "
+"monolithic Linux/PPC kernel architecture does not have support for these "
+"machines; instead, one must use the MkLinux Mach microkernel, which &debian; "
+"does not yet support. These include the following: <itemizedlist> "
+"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> "
+"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> "
+"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> "
+"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </"
+"itemizedlist> A linux kernel for these machines and limited support is "
+"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1096,19 +1283,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:972
 #, no-c-format
-msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
+msgid ""
+"Macintosh computers using the 680x0 series of processors are <emphasis>not</"
+"emphasis> in the PowerPC family but are instead m68k machines. Those models "
+"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> "
+"family, then the Centris series, and culminate in the Quadras and Performas. "
+"These models usually have a Roman numeral or 3-digit model number such as "
+"Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:981
 #, no-c-format
-msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
+msgid ""
+"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, "
+"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, "
+"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra "
+"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the "
+"Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:989
 #, no-c-format
-msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
+msgid ""
+"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs "
+"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, "
+"please see the section above)."
 msgstr ""
 
 #. Tag: title
@@ -1120,7 +1321,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1006
 #, no-c-format
-msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
+msgid ""
+"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
+"Your machine needs to support the z/Architecture, 64-bit support is "
+"mandatory. The userland of the s390 port is still compiled for ESA/390, "
+"though. All zSeries and System z hardware is fully supported. &arch-title; "
+"support software is included from the kernel 3.1 development stream. The "
+"most current information about IBM's Linux support can be found at the "
+"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
+"development_technical.html\"> Linux on <trademark class=\"registered"
+"\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1132,7 +1342,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1024
 #, no-c-format
-msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
+msgid ""
+"PAV and HyperPAV are supported transparently, multipathing is not needed to "
+"take advantage of these storage system features. Be sure to configure the "
+"devices during DASD device selection. The alias devices will not be offered "
+"neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
@@ -1144,7 +1358,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1041
 #, no-c-format
-msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
+msgid ""
+"Sparc-based hardware is divided into a number of different subarchitectures, "
+"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u "
+"or sun4v. The following list describes what machines they include and what "
+"level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
@@ -1156,13 +1374,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1054
 #, no-c-format
-msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
+msgid ""
+"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a "
+"complete list of machines belonging to these subarchitectures, please "
+"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation"
+"\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1061
 #, no-c-format
-msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
+msgid ""
+"The last &debian; release to support sparc32 was Etch, but even then only "
+"for sun4m systems. Support for the other 32-bits subarchitectures had "
+"already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
@@ -1174,7 +1399,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1073
 #, no-c-format
-msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
+msgid ""
+"This subarchitecture includes all 64-bit machines (sparc64) based on the "
+"UltraSparc processor and its clones. Most of the machines are well "
+"supported, even though for some you may experience problems booting from CD "
+"due to firmware or bootloader bugs (this problem may be worked around by "
+"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP "
+"configurations respectively."
 msgstr ""
 
 #. Tag: term
@@ -1186,13 +1417,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1088
 #, no-c-format
-msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
+msgid ""
+"This is the newest addition to the Sparc family, which includes machines "
+"based on the Niagara multi-core CPUs. At the moment such CPUs are only "
+"available in T1000 and T2000 servers by Sun, and are well supported. Use the "
+"sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1099
 #, no-c-format
-msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
+msgid ""
+"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
+"not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
@@ -1204,7 +1441,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1109
 #, no-c-format
-msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
+msgid ""
+"From a technical point of view, laptops are normal PCs, so all information "
+"regarding PC systems applies to laptops as well. Installations on laptops "
+"nowadays usually work out of the box, including things like automatically "
+"suspending the system on closing the lid and laptop specfic hardware buttons "
+"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
+"Nonetheless sometimes the hardware vendors use specialized or proprietary "
+"hardware for some laptop-specific functions which might not be supported. To "
+"see if your particular laptop works well with GNU/Linux, see for example the "
+"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1216,61 +1462,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1127
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. Having multiple "
+"processors in a computer was originally only an issue for high-end server "
+"systems but has become quite common in recent years even for rather low-end "
+"desktop computers and laptops with the introduction of so called "
+"<quote>multi-core</quote> processors. These contain two or more processor "
+"units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1137
 #, no-c-format
-msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
+msgid ""
+"The standard &debian; &release; kernel image has been compiled with SMP "
+"support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1148
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. The standard "
+"&debian; &release; kernel image has been compiled with <firstterm>SMP-"
+"alternatives</firstterm> support. This means that the kernel will detect the "
+"number of processors (or processor cores) and will automatically deactivate "
+"SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1157
 #, no-c-format
-msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Having multiple processors in a computer was originally only an issue for "
+"high-end server systems but has become quite common in recent years even for "
+"rather low-end desktop computers and laptops with the introduction of so "
+"called <quote>multi-core</quote> processors. These contain two or more "
+"processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1165
 #, no-c-format
-msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
+msgid ""
+"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
+"not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1175
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. However, the "
+"standard &debian; &release; kernel image does not support SMP. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1184
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a "
+"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this "
+"time (kernel version &kernelversion;) the way you enable SMP is to select "
+"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</"
+"quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1198
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture, and is supported "
+"by a precompiled &debian; kernel image. Depending on your install media, "
+"this SMP-capable kernel may or may not be installed by default. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1208
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
+msgid ""
+"In order to take advantage of multiple processors, you should check to see "
+"if a kernel package that supports SMP is installed, and if not, choose an "
+"appropriate kernel package."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1214
 #, no-c-format
-msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"You can also build your own customized kernel to support SMP.<phrase arch="
+"\"linux-any\"> You can find a discussion of how to do this in <xref linkend="
+"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way "
+"you enable SMP is to select <quote>&smp-config-option;</quote> in the "
+"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1282,13 +1575,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1226
 #, no-c-format
-msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
+msgid ""
+"&debian;'s support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. On modern PCs, having a graphical "
+"display usually works out of the box. Whether advanced graphics card "
+"features such as 3D-hardware acceleration or hardware-accelerated video are "
+"available, depends on the actual graphics hardware used in the system and in "
+"some cases on the installation of additional <quote>firmware</quote> images "
+"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
+"been reports about hardware on which installation of additional graphics "
+"card firmware was required even for basic graphics support, but these have "
+"been rare exceptions."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1239
 #, no-c-format
-msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
+msgid ""
+"Details on supported graphics cards and pointing devices can be found at "
+"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
+"version &x11ver;."
 msgstr ""
 
 #. Tag: para
@@ -1300,13 +1606,31 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1249
 #, no-c-format
-msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
+msgid ""
+"Most graphics options commonly found on Sparc-based machines are supported. "
+"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, "
+"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), "
+"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards "
+"(glint driver). To use an Elite3D card with X.org you additionally need to "
+"install the <classname>afbinit</classname> package, and read the "
+"documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1259
 #, no-c-format
-msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
+msgid ""
+"It is not uncommon for a Sparc machine to have two graphics cards in a "
+"default configuration. In such a case there is a possibility that the Linux "
+"kernel will not direct its output to the card initially used by the "
+"firmware. The lack of output on the graphical console may then be mistaken "
+"for a hang (usually the last message seen on console is 'Booting Linux...'). "
+"One possible solution is to physically remove one of the video cards; "
+"another option is to disable one of the cards using a kernel boot parameter. "
+"Also, if graphical output is not required or desired, serial console may be "
+"used as an alternative. On some systems use of serial console can be "
+"activated automatically by disconnecting the keyboard before booting the "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -1318,13 +1642,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1282
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
+msgid ""
+"Almost any network interface card (NIC) supported by the &arch-kernel; "
+"kernel should also be supported by the installation system; drivers should "
+"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
+"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
+"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1292
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+msgid ""
+"This includes a lot of generic PCI cards (for systems that have PCI) and the "
+"following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
@@ -1384,7 +1715,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1349
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
+msgid ""
+"On &arch-title;, most built-in Ethernet devices are supported and modules "
+"for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
@@ -1402,31 +1735,52 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1362
 #, no-c-format
-msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
+msgid ""
+"Wireless networking is in general supported as well and a growing number of "
+"wireless adapters are supported by the official &arch-kernel; kernel, "
+"although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1369
 #, no-c-format
-msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
+msgid ""
+"If firmware is needed, the installer will prompt you to load firmware. See "
+"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
+"firmware during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1374
 #, no-c-format
-msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
+msgid ""
+"Wireless NICs that are not supported by the official &arch-kernel; kernel "
+"can generally be made to work under &debian-gnu;, but are not supported "
+"during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1379
 #, no-c-format
-msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
+msgid ""
+"If there is a problem with wireless and there is no other NIC you can use "
+"during the installation, it is still possible to install &debian-gnu; using "
+"a full CD-ROM or DVD image. Select the option to not configure a network and "
+"install using only the packages available from the CD/DVD. You can then "
+"install the driver and firmware you need after the installation is completed "
+"(after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1389
 #, no-c-format
-msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
+msgid ""
+"In some cases the driver you need may not be available as a &debian; "
+"package. You will then have to look if there is source code available in the "
+"internet and compile the driver yourself. How to do this is outside the "
+"scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, "
+"your last resort is to use the <classname>ndiswrapper</classname> package, "
+"which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1438,7 +1792,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1404
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid ""
+"There are a couple of issues with specific network cards that are worth "
+"mentioning here."
 msgstr ""
 
 #. Tag: title
@@ -1450,19 +1806,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1413
 #, no-c-format
-msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
+msgid ""
+"There are various PCI network cards that have the same PCI identification, "
+"but are supported by related, but different drivers. Some cards work with "
+"the <literal>tulip</literal> driver, others with the <literal>dfme</literal> "
+"driver. Because they have the same identification, the kernel cannot "
+"distinguish between them and it is not certain which driver will be loaded. "
+"If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1423
 #, no-c-format
-msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
+msgid ""
+"This is a common problem on Netra systems with a Davicom (DEC-Tulip "
+"compatible) NIC. In that case the <literal>tulip</literal> driver is "
+"probably the correct one. You can prevent this issue by blacklisting the "
+"wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1431
 #, no-c-format
-msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
+msgid ""
+"An alternative solution during the installation is to switch to a shell and "
+"unload the wrong driver module using <userinput>modprobe -r "
+"<replaceable>module</replaceable></userinput> (or both, if they are both "
+"loaded). After that you can load the correct module using "
+"<userinput>modprobe <replaceable>module</replaceable></userinput>. Note that "
+"the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
@@ -1474,7 +1846,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1446
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid ""
+"The <literal>cassini</literal> network driver does not work with Sun B100 "
+"blade systems."
 msgstr ""
 
 #. Tag: title
@@ -1486,7 +1860,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1462
 #, no-c-format
-msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
+msgid ""
+"Support for braille displays is determined by the underlying support found "
+"in <classname>brltty</classname>. Most displays work under "
+"<classname>brltty</classname>, connected via either a serial port, USB or "
+"bluetooth. Details on supported braille devices can be found on the <ulink "
+"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
+"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
@@ -1498,7 +1878,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1477
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
+msgid ""
+"Support for hardware speech synthesis devices is determined by the "
+"underlying support found in <classname>speakup</classname>. "
+"<classname>speakup</classname> only supports integrated boards and external "
+"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
+"are supported). Details on supported hardware speech synthesis devices can "
+"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
+"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
+"classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
@@ -1510,25 +1898,37 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1498
 #, no-c-format
-msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
+msgid ""
+"&arch-kernel; supports a large variety of hardware devices such as mice, "
+"printers, scanners, PCMCIA and USB devices. However, most of these devices "
+"are not required while installing the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1504
 #, no-c-format
-msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
+msgid ""
+"USB hardware generally works fine. On some very old PC systems some USB "
+"keyboards may require additional configuration (see <xref linkend=\"hardware-"
+"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
+"any specific configuration."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1513
 #, no-c-format
-msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
+msgid ""
+"Package installations from XPRAM and tape are not supported by this system. "
+"All packages that you want to install need to be available on a DASD or over "
+"the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1519
 #, no-c-format
-msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Cobalt RaQ has no support for additional devices but the Qube has one "
+"PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -1540,31 +1940,63 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1532
 #, no-c-format
-msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
+msgid ""
+"Besides the availability of a device driver, some hardware also requires so-"
+"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> "
+"to be loaded into the device before it can become operational. This is most "
+"common for network interface cards (especially wireless NICs), but for "
+"example some USB devices and even some hard disk controllers also require "
+"firmware. With many graphics cards, basic functionality is available without "
+"additional firmware, but the use of advanced features requires an "
+"appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1543
 #, no-c-format
-msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
+msgid ""
+"On many older devices which require firmware to work, the firmware file was "
+"permanently placed in an EEPROM/Flash chip on the device itself by the "
+"manufacturer. Nowadays most new devices do not have the firmware embedded "
+"this way anymore, so the firmware file must be uploaded into the device by "
+"the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1551
 #, no-c-format
-msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
+msgid ""
+"In most cases firmware is non-free according to the criteria used by the "
+"&debian-gnu; project and thus cannot be included in the main distribution or "
+"in the installation system. If the device driver itself is included in the "
+"distribution and if &debian-gnu; legally can distribute the firmware, it "
+"will often be available as a separate package from the non-free section of "
+"the archive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1560
 #, no-c-format
-msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
+msgid ""
+"However, this does not mean that such hardware cannot be used during an "
+"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
+"firmware files or packages containing firmware from a removable medium, such "
+"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
+"information on how to load firmware files or packages during the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1569
 #, no-c-format
-msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
+msgid ""
+"If the &d-i; prompts for a firmware file and you do not have this firmware "
+"file available or do not want to install a non-free firmware file on your "
+"system, you can try to proceed without loading the firmware. There are "
+"several cases where a driver prompts for additional firmware because it may "
+"be needed under certain circumstances, but the device does work without it "
+"on most systems (this e.g. happens with certain network cards using the tg3 "
+"driver)."
 msgstr ""
 
 #. Tag: title
@@ -1576,19 +2008,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1588
 #, no-c-format
-msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
+msgid ""
+"There are several vendors, who ship systems with &debian; or other "
+"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</"
+"ulink>. You might pay more for the privilege, but it does buy a level of "
+"peace of mind, since you can be sure that the hardware is well-supported by "
+"GNU/Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1596
 #, no-c-format
-msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
+msgid ""
+"If you do have to buy a machine with Windows bundled, carefully read the "
+"software license that comes with Windows; you may be able to reject the "
+"license and obtain a rebate from your vendor. Searching the Internet for "
+"<quote>windows refund</quote> may get you some useful information to help "
+"with that."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1604
 #, no-c-format
-msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
+"even a used system, it is still important to check that your hardware is "
+"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
+"the references found above. Let your salesperson (if any) know that you're "
+"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
+"vendors."
 msgstr ""
 
 #. Tag: title
@@ -1600,31 +2048,67 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1616
 #, no-c-format
-msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
+msgid ""
+"Some hardware manufacturers simply won't tell us how to write drivers for "
+"their hardware. Others won't allow us access to the documentation without a "
+"non-disclosure agreement that would prevent us from releasing the driver's "
+"source code, which is one of the central elements of free software. Since we "
+"haven't been granted access to usable documentation on these devices, they "
+"simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1626
 #, no-c-format
-msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
+msgid ""
+"In many cases there are standards (or at least some de-facto standards) "
+"describing how an operating system and its device drivers communicate with a "
+"certain class of devices. All devices which comply to such a (de-facto-)"
+"standard can be used with a single generic device driver and no device-"
+"specific drivers are required. With some kinds of hardware (e.g. USB "
+"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
+"mass storage devices like USB flash disks and memory card readers) this "
+"works very well and practically every device sold in the market is standards-"
+"compliant."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1638
 #, no-c-format
-msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
+msgid ""
+"In other fields, among them e.g. printers, this is unfortunately not the "
+"case. While there are many printers which can be addressed via a small set "
+"of (de-facto-)standard control languages and therefore can be made to work "
+"without problems in any operating system, there are quite a few models which "
+"only understand proprietary control commands for which no usable "
+"documentation is available and therefore either cannot be used at all on "
+"free operating systems or can only be used with a vendor-supplied closed-"
+"source driver."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1649
 #, no-c-format
-msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
+msgid ""
+"Even if there is a vendor-provided closed-source driver for such hardware "
+"when purchasing the device, the practical lifespan of the device is limited "
+"by driver availability. Nowadays product cycles have become short and it is "
+"not uncommon that a short time after a consumer device has ceased "
+"production, no driver updates get made available any more by the "
+"manufacturer. If the old closed-source driver does not work anymore after a "
+"system update, an otherwise perfectly working device becomes unusable due to "
+"lacking driver support and there is nothing that can be done in this case. "
+"You should therefore avoid buying closed hardware in the first place, "
+"regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1662
 #, no-c-format
-msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
+msgid ""
+"You can help improve this situation by encouraging manufacturers of closed "
+"hardware to release the documentation and other resources necessary for us "
+"to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
@@ -1636,7 +2120,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1679
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
+msgid ""
+"This section will help you determine which different media types you can use "
+"to install &debian;. There is a whole chapter devoted to media, <xref "
+"linkend=\"install-methods\"/>, which lists the advantages and disadvantages "
+"of each media type. You may want to refer back to this page once you reach "
+"that section."
 msgstr ""
 
 #. Tag: title
@@ -1648,7 +2137,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
+msgid ""
+"In some cases, you'll have to do your first boot from floppy disks. "
+"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch "
+"floppy drive."
 msgstr ""
 
 #. Tag: para
@@ -1666,7 +2158,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1705
 #, no-c-format
-msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
+msgid ""
+"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-"
+"ROMs and DVD-ROMs, because both technologies are really the same from the "
+"operating system's point of view."
 msgstr ""
 
 #. Tag: para
@@ -1684,7 +2179,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1719
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid ""
+"USB CD-ROM drives are also supported, as are FireWire devices that are "
+"supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
@@ -1696,7 +2193,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1728
 #, no-c-format
-msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
+msgid ""
+"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of "
+"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM "
+"drives sold on the PC market do not have this capability. If your CD-ROM "
+"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</"
+"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. "
+"To start the install, simply choose the <quote>System installation</quote> "
+"entry in the firmware."
 msgstr ""
 
 #. Tag: title
@@ -1708,7 +2212,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1744
 #, no-c-format
-msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
+msgid ""
+"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
+"cheap storage device. Most modern computer systems also allow booting the &d-"
+"i; from such a stick. Many modern computer systems, in particular netbooks "
+"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
+"from USB media ist the standard way of installing a new operating system on "
+"them."
 msgstr ""
 
 #. Tag: title
@@ -1720,19 +2230,36 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1758
 #, no-c-format
-msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
+msgid ""
+"The network can be used during the installation to retrieve files needed for "
+"the installation. Whether the network is used or not depends on the "
+"installation method you choose and your answers to certain questions that "
+"will be asked during the installation. The installation system supports most "
+"types of network connections (including PPPoE, but not ISDN or PPP), via "
+"either HTTP or FTP. After the installation is completed, you can also "
+"configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1768
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> the installation system over the "
+"network without needing any local media like CDs/DVDs or USB sticks. If you "
+"already have a netboot-infrastructure available (i.e. you are already "
+"running DHCP and TFTP services in your network), this allows an easy and "
+"fast deployment of a large number of machines. Setting up the necessary "
+"infrastructure requires a certain level of technical experience, so this is "
+"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the "
+"preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1781
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+msgid ""
+"Diskless installation, using network booting from a local area network and "
+"NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
@@ -1744,13 +2271,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1792
 #, no-c-format
-msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
+msgid ""
+"Booting the installation system directly from a hard disk is another option "
+"for many architectures. This will require some other operating system to "
+"load the installer onto the hard disk. This method is only recommended for "
+"special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1799
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid ""
+"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
+"can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
@@ -1762,7 +2295,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1810
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian-gnu; without using the &d-i; described in the rest of this manual. "
+"This kind of install may be useful for users with otherwise unsupported "
+"hardware or on hosts which can't afford downtime. If you are interested in "
+"this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This "
+"installation method is only recommended for advanced users when no other "
+"installation method is available."
 msgstr ""
 
 #. Tag: title
@@ -1774,43 +2314,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1825
 #, no-c-format
-msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
+msgid ""
+"The &debian; installer contains a kernel which is built to maximize the "
+"number of systems it runs on."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1829
 #, no-c-format
-msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+msgid ""
+"Generally, the &debian; installation system includes support for IDE (also "
+"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
+"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
+"(VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1846
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. The following SCSI drivers are supported in the default kernel: "
+"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> "
+"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec "
+"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></"
+"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also "
+"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC "
+"Processors FAQ</ulink> for more information on SPARC hardware supported by "
+"the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1879
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support floppies on "
+"CHRP systems at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support the floppy "
+"drive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1891
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1896
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This means that FBA and ECKD DASDs are supported with the old "
+"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
@@ -1822,12 +2388,22 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1915
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space to perform a normal installation. Note that these are fairly "
+"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-"
+"hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1922
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgid ""
+"Installation on systems with less memory<footnote condition=\"gtk\"> <para> "
+"Installation images that support the graphical installer require more memory "
+"than images that support only the textual installer and should not be used "
+"on systems with less than &minimum-memory; of memory. If there is a choice "
+"between booting the regular and the graphical installer, the former should "
+"be selected. </para> </footnote> or disk space available may be possible but "
+"is only advised for experienced users."
 msgstr ""
-
diff --git a/po/ro/install-methods.po b/po/ro/install-methods.po
index c164d8428..6f56f6790 100644
--- a/po/ro/install-methods.po
+++ b/po/ro/install-methods.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,1149 +29,1719 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian-gnu; is from an Official &debian; CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/DVD-ROM images from a &debian; mirror and make your own set, if you have a fast network connection and a CD/DVD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, which is the case on all modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/>. Much effort has been expended to ensure the most-used files are on the first CDs and DVDs, so that a basic desktop installation can be done with only the first DVD or - to a limited extent - even with only the first CD."
+msgid ""
+"By far the easiest way to install &debian-gnu; is from an Official &debian; "
+"CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-"
+"debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/"
+"DVD-ROM images from a &debian; mirror and make your own set, if you have a "
+"fast network connection and a CD/DVD burner (see the <ulink url=\"&url-"
+"debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;"
+"\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; "
+"CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, "
+"which is the case on all modern PCs</phrase>, you can skip right to <xref "
+"linkend=\"boot-installer\"/>. Much effort has been expended to ensure the "
+"most-used files are on the first CDs and DVDs, so that a basic desktop "
+"installation can be done with only the first DVD or - to a limited extent - "
+"even with only the first CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid ""
+"As CDs have a rather limited capacity by today's standards, not all "
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid ""
+"If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
+"relevant on very old PC systems)</phrase>, but you do have a CD set, you can "
+"use an alternative strategy such as <phrase condition=\"supports-floppy-boot"
+"\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition="
+"\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net "
+"boot,</phrase> or manually loading the kernel from the CD to initially boot "
+"the system installer. The files you need for booting by another means are "
+"also on the CD; the &debian; network archive and CD folder organization are "
+"identical. So when archive file paths are given below for particular files "
+"you need for booting, look for those files in the same directories and "
+"subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
-msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a &debian; mirror using FTP, be sure to download "
+"the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
-msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each &debian; mirror in the directory "
+"<ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
-msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
+msgid ""
+"A firmware image is provided for the Thecus N2100 which will automatically "
+"boot <classname>debian-installer</classname>. This image can be installed "
+"using the Thecus firmware upgrade process. This firmware image can be "
+"obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
-msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
+msgid ""
+"The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
+"on which you intend to install &debian;. These images can be obtained from "
+"&glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
-msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
+msgid ""
+"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
+"disk on which you intend to install &debian;. These images can be obtained "
+"from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
-msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
+msgid ""
+"A firmware image is provided for the HP mv2120 which will automatically boot "
+"<classname>debian-installer</classname>. This image can be installed with "
+"uphpmvault on Linux and other systems and with the HP Media Vault Firmware "
+"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-"
+"firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
-msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
+msgid ""
+"The installation files for the QNAP Turbo Station consist of a kernel and "
+"ramdisk as well as a script to write these images to flash. You can obtain "
+"the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
+"kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
-msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
+msgid ""
+"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
+"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
+"obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
-msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
+msgid ""
+"The installation files for LaCie NASes (Network Space v2, Network Space Max "
+"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
+"consist of a kernel and initrd for U-Boot. You can obtain these files from "
+"&lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
-msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
+msgid ""
+"Bootable floppy disks are generally used as a last resort to boot the "
+"installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
-msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
+msgid ""
+"Booting the installer from floppy disk reportedly fails on Mac USB floppy "
+"drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images. This "
+"section describes how to create floppies from disk images on different "
+"platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
-msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
+msgid ""
+"Before you can create the floppies, you will first need to download them "
+"from one of the &debian; mirrors, as explained in <xref linkend="
+"\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an "
+"installation CD-ROM or DVD, the floppy images may also be included on the CD/"
+"DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
-msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
+msgid ""
+"No matter which method you use to create your floppies, you should remember "
+"to flip the write-protect tab on the floppies once you have written them, to "
+"ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
-      "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
-      "$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-      "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> (on Solaris, use <command>eject</command>, see the manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:337
+"To write the floppy disk image files to the floppy disks, you will probably "
+"need root access to the system. Place a good, blank floppy in the floppy "
+"drive. Next, use the command <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly "
+"used name of the floppy disk device, it may be different on your "
+"workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</"
+"filename>)</phrase>. The command may return to the prompt before Unix has "
+"finished writing the floppy disk, so look for the disk-in-use light on the "
+"floppy drive and be sure that the light is out and the disk has stopped "
+"revolving before you remove it from the drive. On some systems, you'll have "
+"to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> "
+"(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:336
 #, no-c-format
-msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+msgid ""
+"Some systems attempt to automatically mount a floppy disk when you place it "
+"in the drive. You might have to disable this feature before the workstation "
+"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
+"management to get raw access to the floppy. First, make sure that the floppy "
+"is auto-mounted (using <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
-msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 or amd64 machine, you can use one of the "
+"following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> programs can "
+"be used under MS-DOS. To use these programs, first make sure that you are "
+"booted into DOS. Trying to use these programs from within a DOS box in "
+"Windows, or double-clicking on these programs from the Windows Explorer is "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
-msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
+msgid ""
+"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
+"ME, XP and probably later versions. To use it you will need to unpack diskio."
+"dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
-msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official &debian; CD-ROMs under the "
+"<filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
-msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
+msgid ""
+"An AppleScript, <application>Make &debian; Floppy</application>, is "
+"available for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on "
+"your desktop, and then drag any floppy image file to it. You must have "
+"Applescript installed and enabled in your extensions manager. Disk Copy will "
+"ask you to confirm that you wish to erase the floppy and proceed to write "
+"the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> file is an example of a floppy image. Use one of the following "
+"methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian-gnu; CD, then the Type and Creator are already set "
+"correctly. The following <command>Creator-Changer</command> steps are only "
+"necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> image file from the "
+"resulting dialog. It will ask you to insert a floppy, then ask if you really "
+"want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
-msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
+msgid ""
+"To prepare the USB stick, you will need a system where GNU/Linux is already "
+"running and where USB is supported. With current GNU/Linux systems the USB "
+"stick should be automatically recognized when you insert it. If it is not "
+"you should check that the usb-storage kernel module is loaded. When the USB "
+"stick is inserted, it will be mapped to a device named <filename>/dev/sdX</"
+"filename>, where the <quote>X</quote> is a letter in the range a-z. You "
+"should be able to see to which device the USB stick was mapped by running "
+"the command <command>dmesg</command> after inserting it. To write to your "
+"stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
-msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
+msgid ""
+"The procedures described in this section will destroy anything already on "
+"the device! Make very sure that you use the correct device name for your USB "
+"stick. If you use the wrong device the result could be that all information "
+"on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
-msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
+msgid ""
+"Debian CD and DVD images can now be written directly a USB stick, which is a "
+"very easy way to make a bootable USB stick. Simply choose a CD or DVD image "
+"that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to "
+"get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
-msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
+msgid ""
+"Alternatively, for very small USB sticks, only a few megabytes in size, you "
+"can download the <filename>mini.iso</filename> image from the "
+"<filename>netboot</filename> directory (at the location mentioned in <xref "
+"linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
-msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
+msgid ""
+"A special method can be used to add firmware to the <filename>mini.iso</"
+"filename>. First, write the <filename>mini.iso</filename> to the USB stick. "
+"Next obtain the necessary firmware files. See <xref linkend=\"loading-"
+"firmware\"/> for more information about firmware. Now unplug and replug the "
+"USB stick, and two partitions should now be visible on it. You should mount "
+"the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
-      "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
-      "# cd /mnt\n"
-      "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
-      "# cd /\n"
-      "# umount"
+"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
+"# cd /mnt\n"
+"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
+"# cd /\n"
+"# umount"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
-msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
+msgid ""
+"The CD or DVD image you choose should be written directly to the USB stick, "
+"overwriting its current contents. For example, when using an existing GNU/"
+"Linux system, the CD or DVD image file can be written to a USB stick as "
+"follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
-      "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
-      "<prompt>#</prompt> <userinput>sync</userinput>"
+"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
+"<replaceable>sdX</replaceable></userinput>\n"
+"<prompt>#</prompt> <userinput>sync</userinput>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
-msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
+msgid ""
+"Simply writing the CD or DVD image to USB like this should work fine for "
+"most users. The other options below are more complex, mainly for people with "
+"specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
-msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"An alternative way to set up your USB stick is to manually copy the "
+"installer files, and also a CD image to it. Note that the USB stick should "
+"be at least 1 GB in size (smaller setups are possible if you follow <xref "
+"linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
-msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
+msgid ""
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) <phrase arch="
+"\"x86\">as well as <classname>syslinux</classname> and its configuration "
+"file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</"
+"classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
-msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
+msgid ""
+"Note that, although convenient, this method does have one major "
+"disadvantage: the logical size of the device will be limited to 1 GB, even "
+"if the capacity of the USB stick is larger. You will need to repartition the "
+"USB stick and create new file systems to get its full capacity back if you "
+"ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
-msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
+msgid ""
+"Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
+"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract "
+"the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
-msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"After that, mount the USB memory stick <phrase arch=\"x86\">"
+"(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</"
+"phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</"
+"replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch="
+"\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS "
+"filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
+"CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
+"are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
-msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
+msgid ""
+"If you like more flexibility or just want to know what's going on, you "
+"should use the following method to put the files on your stick. One "
+"advantage of using this method is that &mdash; if the capacity of your USB "
+"stick is large enough &mdash; you have the option of copying a full CD ISO "
+"image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
-msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to set up the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
-      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
-      "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
+"Since most USB sticks come pre-configured with a single FAT16 partition, you "
+"probably won't have to repartition or reformat the stick. If you have to do "
+"that anyway, use <command>cfdisk</command> or any other partitioning tool to "
+"create a FAT16 partition<footnote> <para> Don't forget to set the "
+"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR "
+"using: <informalexample><screen>\n"
+"# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+"</screen></informalexample> The <command>install-mbr</command> command is "
+"contained in the <classname>mbr</classname> &debian; package. Then create "
+"the filesystem using: <informalexample><screen>\n"
+"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. Although any boot loader (e.g. <classname>lilo</"
+"classname>) should work, it's convenient to use <classname>syslinux</"
+"classname>, since it uses a FAT16 partition and can be reconfigured by just "
+"editing a text file. Any operating system which supports the FAT file system "
+"can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
-      "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
-      "# syslinux /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>syslinux</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"To put <classname>syslinux</classname> on the FAT16 partition on your USB "
+"stick, install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
+"# syslinux /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>syslinux</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick: "
+"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or "
+"<filename>linux</filename> (kernel binary) </para></listitem> "
+"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </"
+"para></listitem> </itemizedlist> You can choose between either the regular "
+"version or the graphical version of the installer. The latter can be found "
+"in the <filename>gtk</filename> subdirectory. If you want to rename the "
+"files, please note that <classname>syslinux</classname> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
-      "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
-      "default vmlinuz\n"
-      "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
+"Next you should create a <filename>syslinux.cfg</filename> configuration "
+"file, which at a bare minimum should contain the following two lines (change "
+"the name of the kernel binary to <quote><filename>linux</filename></quote> "
+"if you used a <filename>netboot</filename> image): "
+"<informalexample><screen>\n"
+"default vmlinuz\n"
+"append initrd=initrd.gz\n"
+"</screen></informalexample> For the graphical installer you should add "
+"<userinput>vga=788</userinput> to the second line. Other parameters can be "
+"appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
-msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgid ""
+"To enable the boot prompt to permit further parameter appending, add a "
+"<userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
-msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
+msgid ""
+"If you used an <filename>hd-media</filename> image, you should now copy the "
+"ISO file of a &debian; ISO image<footnote> <para> You can use either a "
+"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure "
+"to select one that fits. Note that the <quote>netboot <filename>mini.iso</"
+"filename></quote> image is not usable for this purpose. </para> </footnote> "
+"onto the stick. When you are done, unmount the USB memory stick "
+"(<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
-      "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
-      "$ hformat /dev/<replaceable>sdX2</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> &debian; package."
+"Most USB sticks do not come pre-configured in such a way that Open Firmware "
+"can boot from them, so you will need to repartition the stick. On Mac "
+"systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></"
+"userinput>, initialise a new partition map using the <userinput>i</"
+"userinput> command, and create a new partition of type Apple_Bootstrap using "
+"the <userinput>C</userinput> command. (Note that the first \"partition\" "
+"will always be the partition map itself.) Then type "
+"<informalexample><screen>\n"
+"$ hformat /dev/<replaceable>sdX2</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> boot loader can be "
+"installed on an HFS filesystem and can be reconfigured by just editing a "
+"text file. Any operating system which supports the HFS file system can be "
+"used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
-      "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
-      "$ hmount /dev/<replaceable>sdX2</replaceable>\n"
-      "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
-      "$ hattrib -c UNIX -t tbxi :yaboot\n"
-      "$ hattrib -b :\n"
-      "$ humount\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:857
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
+"$ hmount /dev/<replaceable>sdX2</replaceable>\n"
+"$ hcopy -r /usr/lib/yaboot/yaboot :\n"
+"$ hattrib -c UNIX -t tbxi :yaboot\n"
+"$ hattrib -b :\n"
+"$ humount\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be otherwise mounted during this procedure. "
+"This procedure writes the boot loader to the partition, and uses the HFS "
+"utilities to mark it in such a way that Open Firmware will boot it. Having "
+"done this, the rest of the USB stick may be prepared using the normal Unix "
+"utilities."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:856
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
-      "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
-      "default=install\n"
-      "root=/dev/ram\n"
-      "\n"
-      "message=/boot.msg\n"
-      "\n"
-      "image=/vmlinux\n"
-      "        label=install\n"
-      "        initrd=/initrd.gz\n"
-      "        initrd-size=10000\n"
-      "        read-only\n"
-      "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
+"default=install\n"
+"root=/dev/ram\n"
+"\n"
+"message=/boot.msg\n"
+"\n"
+"image=/vmlinux\n"
+"        label=install\n"
+"        initrd=/initrd.gz\n"
+"        initrd-size=10000\n"
+"        read-only\n"
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
-msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
+msgid ""
+"The installer may be booted using boot files placed on an existing hard "
+"drive partition, either launched from another operating system or by "
+"invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
-msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+msgid ""
+"The installer cannot boot from files on an HFS+ file system. MacOS System "
+"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To "
+"determine whether your existing file system is HFS+, select <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
-msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
+msgid ""
+"At boot time, both bootloaders support loading in memory not only the "
+"kernel, but also a disk image. This RAM disk can be used as the root file-"
+"system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
-msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the &debian; archives to a convenient location "
+"on your hard drive (note that LILO can not boot from files on an NTFS file "
+"system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
-msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
+msgid ""
+"This section explains how to prepare your hard drive for booting the "
+"installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
-msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
+msgid ""
+"Copy the following directories from a &debian; CD image to <filename>c:\\</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
-msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
+msgid ""
+"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your &debian; installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on &debian; http/ftp mirrors and official &debian; CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
-msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+msgid ""
+"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
+"well as loading ELF binaries directly from the hard disk. These machines "
+"will boot Linux directly via <command>yaboot</command>, which supports "
+"loading a kernel and RAMdisk directly from an ext2 partition, as well as "
+"dual-booting with MacOS. Hard disk booting of the installer is particularly "
+"appropriate for newer machines without floppy drives. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (not move) the following four files which you "
+"downloaded earlier from the &debian; archives, onto the root level of your "
+"hard drive (this can be accomplished by <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the <command>L</command> command to check for the partition number. You "
+"will need this partition number for the command you type at the Open "
+"Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
-msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
+msgid ""
+"If your machine is connected to a local area network, you may be able to "
+"boot it over the network from another machine, using TFTP. If you intend to "
+"boot the installation system from another machine, the boot files will need "
+"to be placed in specific locations on that machine, and the machine "
+"configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
-msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
+msgid ""
+"You need to set up a TFTP server, and for many machines a DHCP server<phrase "
+"condition=\"supports-rarp\">, or RARP server</phrase><phrase condition="
+"\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol.</phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image.</phrase> The DHCP "
+"(Dynamic Host Configuration Protocol) is a more flexible, backwards-"
+"compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
-msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
+msgid ""
+"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
+"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
+"boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
-msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
+msgid ""
+"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
+"the client. Theoretically, any server, on any platform, which implements "
+"these protocols, may be used. In the examples in this section, we shall "
+"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
-msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
+msgid ""
+"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
+"It's written by the same author as the <classname>syslinux</classname> "
+"bootloader and is therefore least likely to cause issues. A good alternative "
+"is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
-msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
+msgid ""
+"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>ip addr show dev eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
+msgid ""
+"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
+"you use the <command>rarpd</command> program. You need to ensure that the "
+"Ethernet hardware address for the client is listed in the <quote>ethers</"
+"quote> database (either in the <filename>/etc/ethers</filename> file, or via "
+"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start "
+"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</"
+"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/"
+"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/"
+"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
+"gnu;, the <classname>dhcp3-server</classname> package is recommended. Here "
+"is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</"
+"filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
-      "option domain-name \"example.com\";\n"
-      "option domain-name-servers ns1.example.com;\n"
-      "option subnet-mask 255.255.255.0;\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "server-name \"servername\";\n"
-      "\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option routers 192.168.1.1;\n"
-      "}\n"
-      "\n"
-      "host clientname {\n"
-      "  filename \"/tftpboot.img\";\n"
-      "  server-name \"servername\";\n"
-      "  next-server servername;\n"
-      "  hardware ethernet 01:23:45:67:89:AB;\n"
-      "  fixed-address 192.168.1.90;\n"
-      "}"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1237
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+"  filename \"/tftpboot.img\";\n"
+"  server-name \"servername\";\n"
+"  next-server servername;\n"
+"  hardware ethernet 01:23:45:67:89:AB;\n"
+"  fixed-address 192.168.1.90;\n"
+"}"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1236
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
-#, no-c-format
-msgid ""
-      "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
-      "option domain-name \"example.com\";\n"
-      "\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "\n"
-      "allow booting;\n"
-      "allow bootp;\n"
-      "\n"
-      "# The next paragraph needs to be modified to fit your case\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option broadcast-address 192.168.1.255;\n"
-      "# the gateway address which can be different\n"
-      "# (access to the internet for instance)\n"
-      "  option routers 192.168.1.1;\n"
-      "# indicate the dns you want to use\n"
-      "  option domain-name-servers 192.168.1.3;\n"
-      "}\n"
-      "\n"
-      "group {\n"
-      "  next-server 192.168.1.3;\n"
-      "  host tftpclient {\n"
-      "# tftp client hardware address\n"
-      "  hardware ethernet  00:10:DC:27:6C:15;\n"
-      "  filename \"pxelinux.0\";\n"
-      " }\n"
-      "}\n"
-      "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+#: install-methods.xml:1255
+#, no-c-format
+msgid ""
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different\n"
+"# (access to the internet for instance)\n"
+"  option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+"  option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"group {\n"
+"  next-server 192.168.1.3;\n"
+"  host tftpclient {\n"
+"# tftp client hardware address\n"
+"  hardware ethernet  00:10:DC:27:6C:15;\n"
+"  filename \"pxelinux.0\";\n"
+" }\n"
+"}\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux. The first is CMU "
+"<command>bootpd</command>. The other is actually a DHCP server: ISC "
+"<command>dhcpd</command>. In &debian-gnu; these are contained in the "
+"<classname>bootp</classname> and <classname>dhcp3-server</classname> "
+"packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
-      "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
-      "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-      "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
-      "client:\\\n"
-      "  hd=/tftpboot:\\\n"
-      "  bf=tftpboot.img:\\\n"
-      "  ip=192.168.1.90:\\\n"
-      "  sm=255.255.255.0:\\\n"
-      "  sa=192.168.1.1:\\\n"
-      "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1318
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you "
+"can run <userinput>update-inetd --enable bootps</userinput>, then "
+"<userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your "
+"BOOTP server does not run &debian;, the line in question should look like: "
+"<informalexample><screen>\n"
+"bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
+"client:\\\n"
+"  hd=/tftpboot:\\\n"
+"  bf=tftpboot.img:\\\n"
+"  ip=192.168.1.90:\\\n"
+"  sm=255.255.255.0:\\\n"
+"  sa=192.168.1.1:\\\n"
+"  ha=0123456789AB:\n"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI machines you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1317
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd."
+"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/"
+"init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
-msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
+msgid ""
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
-msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
+msgid ""
+"In the case of <classname>tftpd-hpa</classname> there are two ways the "
+"service can be run. It can be started on demand by the system's "
+"<classname>inetd</classname> daemon, or it can be set up to run as an "
+"independent daemon. Which of these methods is used is selected when the "
+"package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
-msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
+msgid ""
+"Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
+"to serve images from. However, &debian-gnu; packages may use other "
+"directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by "
+"default uses <filename>/srv/tftp</filename>. You may have to adjust the "
+"configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
-msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
+msgid ""
+"All <command>in.tftpd</command> alternatives available in &debian; should "
+"log TFTP requests to the system logs by default. Some of them support a "
+"<userinput>-v</userinput> argument to increase verbosity. It is recommended "
+"to check these log messages in case of boot problems as they are a good "
+"starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
-      "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
-      "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
-      "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-      "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"If you intend to install &debian; on an SGI machine and your TFTP server is "
+"a GNU/Linux box running Linux 2.4, you'll need to set the following on your "
+"server: <informalexample><screen>\n"
+"# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets "
+"are sent from a source port no greater than 32767, or the download will "
+"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
+"the PROM, and you can avoid it by setting <informalexample><screen>\n"
+"# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. You may "
+"have to make a link from that file to the file which <command>tftpd</"
+"command> will use for booting a particular client. Unfortunately, the file "
+"name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. You will need to download the following files from the "
+"<filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
-      "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-      "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
-      "</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"Some SPARC architectures add the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your "
+"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename "
+"would be <filename>C0A80103.SUN4C</filename>. However, there are also "
+"subarchitectures where the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. An easy way to determine the "
+"hexadecimal code for the IP address is to enter the following command in a "
+"shell (assuming the machine's intended IP is 10.0.0.4). "
+"<informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> To get to the correct filename, you will need to "
+"change all letters to uppercase and if necessary append the subarchitecture "
+"name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
-msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
+msgid ""
+"If you've done all this correctly, giving the command <userinput>boot net</"
+"userinput> from the OpenPROM should load the image. If the image cannot be "
+"found, try checking the logs on your tftp server to see which image name is "
+"being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
-msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+msgid ""
+"You can also force some sparc systems to look for a specific file name by "
+"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
-msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI machines you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. &debian; packages intended for this include <classname>fai-"
+"quickstart</classname> (which can use an install server) and the &debian; "
+"Installer itself. Have a look at the <ulink url=\"http://fai-project.org"
+"\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
-msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
+msgid ""
+"The &debian; Installer supports automating installs via preconfiguration "
+"files. A preconfiguration file can be loaded from the network or from "
+"removable media, and used to fill in answers to questions asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
-msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Full documentation on preseeding including a working example that you can "
+"edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-
diff --git a/po/ro/installation-howto.po b/po/ro/installation-howto.po
index 6b8f358e5..369f718c1 100644
--- a/po/ro/installation-howto.po
+++ b/po/ro/installation-howto.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:7
 #, no-c-format
-msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document."
+msgid ""
+"This document describes how to install &debian-gnu; &releasename; for the "
+"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a "
+"quick walkthrough of the installation process which should contain all the "
+"information you will need for most installs. When more information can be "
+"useful, we will link to more detailed explanations in other parts of this "
+"document."
 msgstr ""
 
 #. Tag: title
@@ -34,7 +41,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:20
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)."
+msgid ""
+"<phrase condition=\"unofficial-build\"> The debian-installer is still in a "
+"beta state. </phrase> If you encounter bugs during your install, please "
+"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report "
+"them. If you have questions which cannot be answered by this document, "
+"please direct them to the debian-boot mailing list (&email-debian-boot-"
+"list;) or ask on IRC (#debian-boot on the OFTC network)."
 msgstr ""
 
 #. Tag: title
@@ -46,19 +59,30 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:37
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>."
+msgid ""
+"<phrase condition=\"unofficial-build\"> For some quick links to CD images, "
+"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> "
+"The debian-cd team provides builds of CD images using &d-i; on the <ulink "
+"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on "
+"where to get CDs, see <xref linkend=\"official-cdrom\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:47
 #, no-c-format
-msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on &debian; mirrors."
+msgid ""
+"Some installation methods require other images than CD images. <phrase "
+"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home "
+"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files"
+"\"/> explains how to find images on &debian; mirrors."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:57
 #, no-c-format
-msgid "The subsections below will give the details about which images you should get for each possible means of installation."
+msgid ""
+"The subsections below will give the details about which images you should "
+"get for each possible means of installation."
 msgstr ""
 
 #. Tag: title
@@ -70,13 +94,26 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:67
 #, no-c-format
-msgid "The netinst CD image is a popular image which can be used to install &releasename; with the &d-i;. This image is intended to boot from CD and install additional packages over a network; hence the name 'netinst'. The image has the software components needed to run the installer and the base packages to provide a minimal &releasename; system. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set."
+msgid ""
+"The netinst CD image is a popular image which can be used to install "
+"&releasename; with the &d-i;. This image is intended to boot from CD and "
+"install additional packages over a network; hence the name 'netinst'. The "
+"image has the software components needed to run the installer and the base "
+"packages to provide a minimal &releasename; system. If you'd rather, you can "
+"get a full size CD image which will not need the network to install. You "
+"only need the first CD of the set."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:77
 #, no-c-format
-msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>"
+msgid ""
+"Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-"
+"x86\">To boot the CD, you may need to change your BIOS configuration, as "
+"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc"
+"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while "
+"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -88,31 +125,50 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:92
 #, no-c-format
-msgid "If you can't boot from CD, you can download floppy images to install &debian;. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks."
+msgid ""
+"If you can't boot from CD, you can download floppy images to install "
+"&debian;. You need the <filename>floppy/boot.img</filename>, the "
+"<filename>floppy/root.img</filename> and one or more of the driver disks."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:98
 #, no-c-format
-msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy &mdash; use the one with <filename>root.img</filename> on it."
+msgid ""
+"The boot floppy is the one with <filename>boot.img</filename> on it. This "
+"floppy, when booted, will prompt you to insert a second floppy &mdash; use "
+"the one with <filename>root.img</filename> on it."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:104
 #, no-c-format
-msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>."
+msgid ""
+"If you're planning to install over the network, you will usually need the "
+"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, "
+"and some less common network cards, you will also need a second driver "
+"floppy, <filename>floppy/net-drivers-2.img</filename>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:111
 #, no-c-format
-msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD."
+msgid ""
+"If you have a CD, but cannot boot from it, then boot from floppies and use "
+"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the "
+"install using the CD."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:117
 #, no-c-format
-msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them."
+msgid ""
+"Floppy disks are one of the least reliable media around, so be prepared for "
+"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each "
+"<filename>.img</filename> file you downloaded goes on a single floppy; you "
+"can use the dd command to write it to /dev/fd0 or some other means (see "
+"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than "
+"one floppy, it's a good idea to label them."
 msgstr ""
 
 #. Tag: title
@@ -124,37 +180,62 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:131
 #, no-c-format
-msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy &debian; install medium that you can take with you anywhere."
+msgid ""
+"It's also possible to install from removable USB storage devices. For "
+"example a USB keychain can make a handy &debian; install medium that you can "
+"take with you anywhere."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:137
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download any Debian "
+"CD or DVD image that will fit on it, and write the CD image directly to the "
+"memory stick. Of course this will destroy anything already on the memory "
+"stick. This works because Debian CD images are \"isohybrid\" images that can "
+"boot both from CD and from USB drives."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:145
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from that file. Write this image directly to your memory stick, which must be at least 1 GB in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download <filename>hd-"
+"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from "
+"that file. Write this image directly to your memory stick, which must be at "
+"least 1 GB in size. Of course this will destroy anything already on the "
+"memory stick. Then mount the memory stick, which will now have a FAT "
+"filesystem on it. Next, download a &debian; netinst CD image, and copy that "
+"file to the memory stick; any filename is ok as long as it ends in <literal>."
+"iso</literal>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:156
 #, no-c-format
-msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
+msgid ""
+"There are other, more flexible ways to set up a memory stick to use the "
+"debian-installer, and it's possible to get it to work with smaller memory "
+"sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:162
 #, no-c-format
-msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Some BIOSes can boot USB storage directly, and some cannot. You may need to "
+"configure your BIOS to boot from a <quote>removable drive</quote> or even a "
+"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful "
+"hints and details, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:169
 #, no-c-format
-msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Booting Macintosh systems from USB storage devices involves manual use of "
+"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: title
@@ -166,13 +247,22 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:179
 #, no-c-format
-msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;."
+msgid ""
+"It's also possible to boot &d-i; completely from the net. The various "
+"methods to netboot depend on your architecture and netboot setup. The files "
+"in <filename>netboot/</filename> can be used to netboot &d-i;."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:185
 #, no-c-format
-msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The easiest thing to set up is probably PXE netbooting. Untar the file "
+"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</"
+"filename> or wherever is appropriate for your tftp server. Set up your DHCP "
+"server to pass filename <filename>pxelinux.0</filename> to clients, and with "
+"luck everything will just work. For detailed instructions, see <xref linkend="
+"\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -184,7 +274,15 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:200
 #, no-c-format
-msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>"
+msgid ""
+"It's possible to boot the installer using no removable media, but just an "
+"existing hard disk, which can have a different OS on it. Download "
+"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</"
+"filename>, and a &debian; CD image to the top-level directory of the hard "
+"disk. Make sure that the CD image has a filename ending in <literal>.iso</"
+"literal>. Now it's just a matter of booting linux with the initrd. <phrase "
+"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -196,91 +294,156 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:218
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
+msgid ""
+"Once the installer starts, you will be greeted with an initial screen. Press "
+"&enterkey; to boot, or read the instructions for other boot methods and "
+"parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:224
 #, no-c-format
-msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
+msgid ""
+"After a while you will be asked to select your language. Use the arrow keys "
+"to pick a language and press &enterkey; to continue. Next you'll be asked to "
+"select your country, with the choices including countries where your "
+"language is spoken. If it's not on the short list, a list of all the "
+"countries in the world is available."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:232
 #, no-c-format
-msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
+msgid ""
+"You may be asked to confirm your keyboard layout. Choose the default unless "
+"you know better."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:237
 #, no-c-format
-msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
+msgid ""
+"Now sit back while debian-installer detects some of your hardware, and loads "
+"the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:242
 #, no-c-format
-msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
+msgid ""
+"Next the installer will try to detect your network hardware and set up "
+"networking by DHCP. If you are not on a network or do not have DHCP, you "
+"will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:248
 #, no-c-format
-msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones."
+msgid ""
+"The next step is setting up your clock and time zone. The installer will try "
+"to contact a time server on the Internet to ensure the clock is set "
+"correctly. The time zone is based on the country selected earlier and the "
+"installer will only ask to select one if a country has multiple zones."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:255
 #, no-c-format
-msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"Now it is time to partition your disks. First you will be given the "
+"opportunity to automatically partition either an entire drive, or available "
+"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is "
+"recommended for new users or anyone in a hurry. If you do not want to "
+"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:263
 #, no-c-format
-msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size."
+msgid ""
+"If you have an existing DOS or Windows partition that you want to preserve, "
+"be very careful with automatic partitioning. If you choose manual "
+"partitioning, you can use the installer to resize existing FAT or NTFS "
+"partitions to create room for the &debian; install: simply select the "
+"partition and specify its new size."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:270
 #, no-c-format
-msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning."
+msgid ""
+"On the next screen you will see your partition table, how the partitions "
+"will be formatted, and where they will be mounted. Select a partition to "
+"modify or delete it. If you did automatic partitioning, you should just be "
+"able to choose <guimenuitem>Finish partitioning and write changes to disk</"
+"guimenuitem> from the menu to use what it set up. Remember to assign at "
+"least one partition for swap space and to mount a partition on <filename>/</"
+"filename>. For more detailed information on how to use the partitioner, "
+"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend="
+"\"partitioning\"/> has more general information about partitioning."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:283
 #, no-c-format
-msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
+msgid ""
+"Now &d-i; formats your partitions and starts to install the base system, "
+"which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:288
 #, no-c-format
-msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step."
+msgid ""
+"The base system that was installed earlier is a working, but very minimal "
+"installation. To make the system more functional the next step allows you to "
+"install additional packages by selecting tasks. Before packages can be "
+"installed <classname>apt</classname> needs to be configured as that defines "
+"from where the packages will be retrieved. The <quote>Standard system</"
+"quote> task will be selected by default and should normally be installed. "
+"Select the <quote>Desktop environment</quote> task if you would like to have "
+"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> "
+"for additional information about this step."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:300
 #, no-c-format
-msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account."
+msgid ""
+"Installation of the base system is followed by setting up user accounts. By "
+"default you will need to provide a password for the <quote>root</quote> "
+"(administrator) account and information necessary to create one regular user "
+"account."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:307
 #, no-c-format
-msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
+msgid ""
+"The last step is to install a boot loader. If the installer detects other "
+"operating systems on your computer, it will add them to the boot menu and "
+"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to "
+"the master boot record of the first harddrive, which is generally a good "
+"choice. You'll be given the opportunity to override that choice and install "
+"it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:317
 #, no-c-format
-msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>."
+msgid ""
+"&d-i; will now tell you that the installation has finished. Remove the cdrom "
+"or other boot media and hit &enterkey; to reboot your machine. It should "
+"boot up into the newly installed system and allow you to log in. This is "
+"explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:324
 #, no-c-format
-msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
+msgid ""
+"If you need more information on the install process, see <xref linkend=\"d-i-"
+"intro\"/>."
 msgstr ""
 
 #. Tag: title
@@ -292,13 +455,23 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:334
 #, no-c-format
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>."
+msgid ""
+"If you successfully managed an installation with &d-i;, please take time to "
+"provide us with a report. The simplest way to do so is to install the "
+"reportbug package (<command>aptitude install reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:344
 #, no-c-format
-msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
+msgid ""
+"If you did not complete the install, you probably found a bug in debian-"
+"installer. To improve the installer it is necessary that we know about them, "
+"so please take the time to report them. You can use an installation report "
+"to report problems; if the install completely fails, see <xref linkend="
+"\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
@@ -310,6 +483,7 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:357
 #, no-c-format
-msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read <xref linkend=\"post-install\"/>."
+msgid ""
+"We hope that your &debian; installation is pleasant and that you find "
+"&debian; useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
-
diff --git a/po/ro/partitioning.po b/po/ro/partitioning.po
index 5cab7d795..2be4d60bf 100644
--- a/po/ro/partitioning.po
+++ b/po/ro/partitioning.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,57 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
+msgid ""
+"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can "
+"have a single partition containing the entire operating system, "
+"applications, and your personal files. Most people feel that a separate swap "
+"partition is also a necessity, although it's not strictly true. <quote>Swap</"
+"quote> is scratch space for an operating system, which allows the system to "
+"use disk storage as <quote>virtual memory</quote>. By putting swap on a "
+"separate partition, &arch-kernel; can make much more efficient use of it. It "
+"is possible to force &arch-kernel; to use a regular file as swap, but it is "
+"not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid ""
+"Most people choose to give GNU/&arch-kernel; more than the minimum number of "
+"partitions, however. There are two reasons you might want to break up the "
+"file system into a number of smaller partitions. The first is for safety. If "
+"something happens to corrupt the file system, generally only one partition "
+"is affected. Thus, you only have to replace (from the backups you've been "
+"carefully keeping) a portion of your system. At a bare minimum, you should "
+"consider creating what is commonly called a <quote>root partition</quote>. "
+"This contains the most essential components of the system. If any other "
+"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix "
+"the system. This can save you the trouble of having to reinstall the system "
+"from scratch."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:40
 #, no-c-format
-msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed."
+msgid ""
+"The second reason is generally more important in a business setting, but it "
+"really depends on your use of the machine. For example, a mail server "
+"getting spammed with e-mail can easily fill a partition. If you made "
+"<filename>/var/mail</filename> a separate partition on the mail server, most "
+"of the system will remain working even if you get spammed."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:48
 #, no-c-format
-msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?"
+msgid ""
+"The only real drawback to using more partitions is that it is often "
+"difficult to know in advance what your needs will be. If you make a "
+"partition too small then you will either have to reinstall the system or you "
+"will be constantly moving things around to make room in the undersized "
+"partition. On the other hand, if you make the partition too big, you will be "
+"wasting space that could be used elsewhere. Disk space is cheap nowadays, "
+"but why throw your money away?"
 msgstr ""
 
 #. Tag: title
@@ -58,7 +91,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:68
 #, no-c-format
-msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all &debian; systems include these directories:"
+msgid ""
+"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink> for directory and file naming. This standard "
+"allows users and software programs to predict the location of files and "
+"directories. The root level directory is represented simply by the slash "
+"<filename>/</filename>. At the root level, all &debian; systems include "
+"these directories:"
 msgstr ""
 
 #. Tag: entry
@@ -280,37 +319,77 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:142
 #, no-c-format
-msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
+msgid ""
+"The following is a list of important considerations regarding directories "
+"and partitions. Note that disk usage varies widely given system "
+"configuration and specific usage patterns. The recommendations here are "
+"general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
+msgid ""
+"The root partition <filename>/</filename> must always physically contain "
+"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</"
+"filename>, <filename>/lib</filename> and <filename>/dev</filename>, "
+"otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for "
+"the root partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
+msgid ""
+"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</"
+"filename>), libraries (<filename>/usr/lib</filename>), documentation "
+"(<filename>/usr/share/doc</filename>), etc. This is the part of the file "
+"system that generally takes up most space. You should provide at least 500MB "
+"of disk space. This amount should be increased depending on the number and "
+"type of packages you plan to install. A generous workstation or server "
+"installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid ""
+"<filename>/var</filename>: variable data like news articles, e-mails, web "
+"sites, databases, the packaging system cache, etc. will be placed under this "
+"directory. The size of this directory depends greatly on the usage of your "
+"system, but for most people will be dictated by the package management "
+"tool's overhead. If you are going to do a full installation of just about "
+"everything &debian; has to offer, all in one session, setting aside 2 or 3 "
+"GB of space for <filename>/var</filename> should be sufficient. If you are "
+"going to install in pieces (that is to say, install services and utilities, "
+"followed by text stuff, then X, ...), you can get away with 300&ndash;500 "
+"MB. If hard drive space is at a premium and you don't plan on doing major "
+"system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid ""
+"<filename>/tmp</filename>: temporary data created by programs will most "
+"likely go in this directory. 40&ndash;100MB should usually be enough. Some "
+"applications &mdash; including archive manipulators, CD/DVD authoring tools, "
+"and multimedia software &mdash; may use <filename>/tmp</filename> to "
+"temporarily store image files. If you plan to use such applications, you "
+"should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid ""
+"<filename>/home</filename>: every user will put his personal data into a "
+"subdirectory of this directory. Its size depends on how many users will be "
+"using the system and what files are to be stored in their directories. "
+"Depending on your planned usage you should reserve about 100MB for each "
+"user, but adapt this value to your needs. Reserve a lot more space if you "
+"plan to save a lot of multimedia files (pictures, MP3, movies) in your home "
+"directory."
 msgstr ""
 
 #. Tag: title
@@ -322,49 +401,91 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:223
 #, no-c-format
-msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
+msgid ""
+"For new users, personal &debian; boxes, home systems, and other single-user "
+"setups, a single <filename>/</filename> partition (plus swap) is probably "
+"the easiest, simplest way to go. However, if your partition is larger than "
+"around 6GB, choose ext3 as your partition type. Ext2 partitions need "
+"periodic file system integrity checking, and this can cause delays during "
+"booting when the partition is large."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:232
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid ""
+"For multi-user systems or systems with lots of disk space, it's best to put "
+"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</"
+"filename>, and <filename>/home</filename> each on their own partitions "
+"separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid ""
+"You might need a separate <filename>/usr/local</filename> partition if you "
+"plan to install many programs that are not part of the &debian; "
+"distribution. If your machine will be a mail server, you might need to make "
+"<filename>/var/mail</filename> a separate partition. Often, putting "
+"<filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, "
+"is a good idea. If you are setting up a server with lots of user accounts, "
+"it's generally good to have a separate, large <filename>/home</filename> "
+"partition. In general, the partitioning situation varies from computer to "
+"computer depending on its uses."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:252
 #, no-c-format
-msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
+msgid ""
+"For very complex systems, you should see the <ulink url=\"&url-multidisk-"
+"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, "
+"mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:259
 #, no-c-format
-msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
+msgid ""
+"With respect to the issue of swap partition size, there are many views. One "
+"rule of thumb which works well is to use as much swap as you have system "
+"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, "
+"there are exceptions to these rules. If you are trying to solve 10000 "
+"simultaneous equations on a machine with 256MB of memory, you may need a "
+"gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:268
 #, no-c-format
-msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
+msgid ""
+"On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap "
+"partition is 2GB. That should be enough for nearly any installation. "
+"However, if your swap requirements are this high, you should probably try to "
+"spread the swap across different disks (also called <quote>spindles</quote>) "
+"and, if possible, different SCSI or IDE channels. The kernel will balance "
+"swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:278
 #, no-c-format
-msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
+msgid ""
+"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE "
+"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for "
+"another operating system on <filename>/dev/hda1</filename>, a 32MB swap "
+"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/"
+"dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:287
 #, no-c-format
-msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
+msgid ""
+"For an idea of the space taken by tasks you might be interested in adding "
+"after your system installation is complete, check <xref linkend=\"tasksel-"
+"size-list\"/>."
 msgstr ""
 
 #. Tag: title
@@ -376,7 +497,10 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:304
 #, no-c-format
-msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
+msgid ""
+"Linux disks and partition names may be different from other operating "
+"systems. You need to know the names that Linux uses when you create and "
+"mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
@@ -394,37 +518,51 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:322
 #, no-c-format
-msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
+msgid ""
+"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:328
 #, no-c-format
-msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
+msgid ""
+"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, "
+"and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:334
 #, no-c-format
-msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
+msgid ""
+"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as "
+"<filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:340
 #, no-c-format
-msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
+msgid ""
+"The master disk on IDE primary controller is named <filename>/dev/hda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:346
 #, no-c-format
-msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
+msgid ""
+"The slave disk on IDE primary controller is named <filename>/dev/hdb</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:352
 #, no-c-format
-msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
+msgid ""
+"The master and slave disks of the secondary controller can be called "
+"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, "
+"respectively. Newer IDE controllers can actually have two channels, "
+"effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
@@ -436,43 +574,74 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:369
 #, no-c-format
-msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
+msgid ""
+"The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:377
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>sda1</filename> and <filename>sda2</filename> "
+"represent the first and second partitions of the first SCSI disk drive in "
+"your system."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:384
 #, no-c-format
-msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
+msgid ""
+"Here is a real-life example. Let's assume you have a system with 2 SCSI "
+"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk "
+"(at address 2) is then named <filename>sda</filename>, and the second "
+"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 "
+"partitions on it, these will be named <filename>sda1</filename>, "
+"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies "
+"to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:395
 #, no-c-format
-msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
+msgid ""
+"Note that if you have two SCSI host bus adapters (i.e., controllers), the "
+"order of the drives can get confusing. The best solution in this case is to "
+"watch the boot messages, assuming you know the drive models and/or "
+"capacities."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:402
 #, no-c-format
-msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
+msgid ""
+"Linux represents the primary partitions as the drive name, plus the numbers "
+"1 through 4. For example, the first primary partition on the first IDE drive "
+"is <filename>/dev/hda1</filename>. The logical partitions are numbered "
+"starting at 5, so the first logical partition on that same drive is "
+"<filename>/dev/hda5</filename>. Remember that the extended partition, that "
+"is, the primary partition holding the logical partitions, is not usable by "
+"itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:413
 #, no-c-format
-msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
+msgid ""
+"Sun disk partitions allow for 8 separate partitions (or slices). The third "
+"partition is usually (and is preferred to have) the <quote>Whole Disk</"
+"quote> partition. This partition references all of the sectors of the disk, "
+"and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:420
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> "
+"represent the first and second partitions of the first DASD device in your "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -484,7 +653,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:436
 #, no-c-format
-msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
+msgid ""
+"Several varieties of partitioning programs have been adapted by &debian; "
+"developers to work on various types of hard disks and computer "
+"architectures. Following is a list of the program(s) applicable for your "
+"architecture."
 msgstr ""
 
 #. Tag: command
@@ -496,7 +669,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:449
 #, no-c-format
-msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
+msgid ""
+"Recommended partitioning tool in &debian;. This Swiss army knife can also "
+"resize partitions, create filesystems <phrase arch=\"any-x86\"> "
+"(<quote>format</quote> in Windows speak)</phrase> and assign them to the "
+"mountpoints."
 msgstr ""
 
 #. Tag: command
@@ -514,7 +691,12 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:465
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
+msgid ""
+"Be careful if you have existing FreeBSD partitions on your machine. The "
+"installation kernels include support for these partitions, but the way that "
+"<command>fdisk</command> represents them (or not) can make the device names "
+"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</"
+"ulink>."
 msgstr ""
 
 #. Tag: command
@@ -532,7 +714,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:482
 #, no-c-format
-msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
+msgid ""
+"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at "
+"all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
@@ -580,7 +764,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:519
 #, no-c-format
-msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
+msgid ""
+"PowerMac-aware version of <command>fdisk</command>, also used by BVM and "
+"Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
@@ -592,13 +778,21 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:529
 #, no-c-format
-msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
+msgid ""
+"&arch-title; version of <command>fdisk</command>; Please read the fdasd "
+"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/"
+"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and "
+"Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:540
 #, no-c-format
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
+msgid ""
+"One of these programs will be run by default when you select "
+"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible "
+"to use a different partitioning tool from the command line on VT2, but this "
+"is not recommended."
 msgstr ""
 
 #. Tag: para
@@ -610,11 +804,18 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:550
 #, no-c-format
-msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
+msgid ""
+"One key point when partitioning for Mac type disks is that the swap "
+"partition is identified by its name; it must be named <quote>swap</quote>. "
+"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. "
+"Please read the fine manual. We also suggest reading the <ulink url=\"&url-"
+"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you "
+"should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686
+#: partitioning.xml:800 partitioning.xml:877
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
@@ -622,61 +823,138 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:567
 #, no-c-format
-msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
+msgid ""
+"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> "
+"somewhere in the first 2GB. This is where the boot loader and an optional "
+"kernel and RAMdisk will be stored, so make it big enough for that &mdash; at "
+"least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware "
+"is that the Linux kernel must reside within the first 2GB of the disk. This "
+"is typically achieved by making the root ext2 partition fit entirely within "
+"the first 2GB of the disk. Alternatively you can create a small ext2 "
+"partition near the start of the disk and mount that on <filename>/boot</"
+"filename>, since that is the directory where the Linux kernel(s) will be "
+"stored. <filename>/boot</filename> needs to be big enough to hold whatever "
+"kernels (and backups) you might wish to load; 25&ndash;50MB is generally "
+"sufficient."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:591
 #, no-c-format
-msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
+msgid ""
+"If you have an existing other operating system such as DOS or Windows and "
+"you want to preserve that operating system while installing &debian;, you "
+"may need to resize its partition to free up space for the &debian; "
+"installation. The installer supports resizing of both FAT and NTFS "
+"filesystems; when you get to the installer's partitioning step, select the "
+"option <guimenuitem>Manual</guimenuitem> and then simply select an existing "
+"partition and change its size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:601
 #, no-c-format
-msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
+msgid ""
+"The PC BIOS generally adds additional constraints for disk partitioning. "
+"There is a limit to how many <quote>primary</quote> and <quote>logical</"
+"quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 "
+"BIOSes, there are limits to where on the drive the BIOS can boot from. More "
+"information can be found in the <ulink url=\"&url-partition-howto;\">Linux "
+"Partition HOWTO</ulink>, but this section will include a brief overview to "
+"help you plan most situations."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:611
 #, no-c-format
-msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
+msgid ""
+"<quote>Primary</quote> partitions are the original partitioning scheme for "
+"PC disks. However, there can only be four of them. To get past this "
+"limitation, <quote>extended</quote> and <quote>logical</quote> partitions "
+"were invented. By setting one of your primary partitions as an extended "
+"partition, you can subdivide all the space allocated to that partition into "
+"logical partitions. You can create up to 60 logical partitions per extended "
+"partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:622
 #, no-c-format
-msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
+msgid ""
+"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 "
+"usable primary partitions, 252 logical partitions), and 63 partitions on an "
+"IDE drive (3 usable primary partitions, 60 logical partitions). However the "
+"normal &debian-gnu; system provides only 20 devices for partitions, so you "
+"may not install on partitions higher than 20 unless you first manually "
+"create devices for those partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:632
 #, no-c-format
-msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
+msgid ""
+"If you have a large IDE disk, and are using neither LBA addressing, nor "
+"overlay drivers (sometimes provided by hard disk manufacturers), then the "
+"boot partition (the partition containing your kernel image) must be placed "
+"within the first 1024 cylinders of your hard drive (usually around 524 "
+"megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:640
 #, no-c-format
-msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
+msgid ""
+"This restriction doesn't apply if you have a BIOS newer than around "
+"1995&ndash;98 (depending on the manufacturer) that supports the "
+"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the "
+"Linux loader, and &debian;'s alternative <command>mbr</command> must use the "
+"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large "
+"disk access extensions are found to be present, they will be utilized. "
+"Otherwise, the legacy disk access interface is used as a fall-back, and it "
+"cannot be used to address any location on the disk higher than the 1023rd "
+"cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer "
+"has, these restrictions no longer apply, since &arch-kernel; does not use "
+"the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:654
 #, no-c-format
-msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
+msgid ""
+"If you have a large disk, you might have to use cylinder translation "
+"techniques, which you can set from your BIOS setup program, such as LBA "
+"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). "
+"More information about issues with large disks can be found in the <ulink "
+"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a "
+"cylinder translation scheme, and the BIOS does not support the large disk "
+"access extensions, then your boot partition has to fit within the "
+"<emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:666
 #, no-c-format
-msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
+msgid ""
+"The recommended way of accomplishing this is to create a small "
+"(25&ndash;50MB should suffice) partition at the beginning of the disk to be "
+"used as the boot partition, and then create whatever other partitions you "
+"wish to have, in the remaining area. This boot partition <emphasis>must</"
+"emphasis> be mounted on <filename>/boot</filename>, since that is the "
+"directory where the &arch-kernel; kernel(s) will be stored. This "
+"configuration will work on any system, regardless of whether LBA or large "
+"disk CHS translation is used, and regardless of whether your BIOS supports "
+"the large disk access extensions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:687
 #, no-c-format
-msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
+msgid ""
+"The <command>partman</command> disk partitioner is the default partitioning "
+"tool for the installer. It manages the set of partitions and their mount "
+"points to ensure that the disks and filesystems are properly configured for "
+"a successful installation. It actually uses <command>parted</command> to do "
+"the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
@@ -688,28 +966,52 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:700
 #, no-c-format
-msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+msgid ""
+"The IA-64 EFI firmware supports two partition table (or disk label) formats, "
+"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer "
+"recommended for IA-64 systems. Although the installer also provides "
+"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> "
+"<command>parted</command></ulink> because only it can manage both GPT and MS-"
+"DOS tables correctly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:712
 #, no-c-format
-msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
+msgid ""
+"The automatic partitioning recipes for <command>partman</command> allocate "
+"an EFI partition as the first partition on the disk. You can also set up the "
+"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the "
+"main menu in a manner similar to setting up a <emphasis>swap</emphasis> "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:720
 #, no-c-format
 msgid ""
-      "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
-      "      mklabel gpt\n"
-      "      mkpartfs primary fat 0 50\n"
-      "      mkpartfs primary linux-swap 51 1000\n"
-      "      mkpartfs primary ext2 1001 3000\n"
-      "      set 1 boot on\n"
-      "      print\n"
-      "      quit\n"
-      "</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks."
+"The <command>partman</command> partitioner will handle most disk layouts. "
+"For those rare cases where it is necessary to manually set up a disk, you "
+"can use the shell as described above and run the <command>parted</command> "
+"utility directly using its command line interface. Assuming that you want to "
+"erase your whole disk and create a GPT table and some partitions, then "
+"something similar to the following command sequence could be used: "
+"<informalexample><screen>\n"
+"      mklabel gpt\n"
+"      mkpartfs primary fat 0 50\n"
+"      mkpartfs primary linux-swap 51 1000\n"
+"      mkpartfs primary ext2 1001 3000\n"
+"      set 1 boot on\n"
+"      print\n"
+"      quit\n"
+"</screen></informalexample> This creates a new partition table, and three "
+"partitions to be used as an EFI boot partition, swap space, and a root file "
+"system. Finally it sets the boot flag on the EFI partition. Partitions are "
+"specified in Megabytes, with start and end offsets from the beginning of the "
+"disk. So, for example, above we created a 1999MB ext2 file system starting "
+"at offset 1001MB from the start of the disk. Note that formatting swap space "
+"with <command>parted</command> can take a few minutes to complete, as it "
+"scans the partition for bad blocks."
 msgstr ""
 
 #. Tag: title
@@ -721,19 +1023,36 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:746
 #, no-c-format
-msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
+msgid ""
+"ELILO, the IA-64 boot loader, requires a partition containing a FAT file "
+"system with the <userinput>boot</userinput> flag set. The partition must be "
+"big enough to hold the boot loader and any kernels or RAMdisks you may wish "
+"to boot. A minimum size would be about 20MB, but if you expect to run with "
+"multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:755
 #, no-c-format
-msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
+msgid ""
+"The EFI Boot Manager and the EFI Shell fully support the GPT table so the "
+"boot partition does not necessarily have to be the first partition or even "
+"on the same disk. This is convenient if you should forget to allocate the "
+"partition and only find out after you have formatted the other partitions on "
+"your disk(s). The <command>partman</command> partitioner checks for an EFI "
+"partition at the same time it checks for a properly set up <emphasis>root</"
+"emphasis> partition. This gives you an opportunity to correct the disk "
+"layout before the package install begins. The easiest way to correct this "
+"omission is to shrink the last partition of the disk to make enough free "
+"space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:770
 #, no-c-format
-msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
+msgid ""
+"It is strongly recommended that you allocate the EFI boot partition on the "
+"same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -745,13 +1064,27 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:779
 #, no-c-format
-msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
+msgid ""
+"The EFI firmware is significantly more sophisticated than the usual BIOS "
+"seen on most x86 PCs. Some system vendors take advantage of the ability of "
+"the EFI to access files and run programs from a hard disk filesystem to "
+"store diagnostics and EFI based system management utilities on the hard "
+"disk. This is a separate FAT format filesystem on the system disk. Consult "
+"the system documentation and accessories that come with the system for "
+"details. The easiest time to set up a diagnostics partition is at the same "
+"time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:801
 #, no-c-format
-msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
+msgid ""
+"SGI machines require an SGI disk label in order to make the system bootable "
+"from hard disk. It can be created in the fdisk expert menu. The thereby "
+"created volume header (partition number 9) should be at least 3MB large. If "
+"the volume header created is too small, you can simply delete partition "
+"number 9 and re-add it with a different size. Note that the volume header "
+"must start at sector 0."
 msgstr ""
 
 #. Tag: title
@@ -763,48 +1096,94 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:819
 #, no-c-format
-msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
+msgid ""
+"If you are installing onto a NewWorld PowerMac you must create a special "
+"bootstrap partition to hold the boot loader. The size of this partition must "
+"have at least 819200 bytes and its partition type must be "
+"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not "
+"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine "
+"cannot be made bootable from the hard disk. This partition can easily be "
+"created by creating a new partition in <command>partman</command> and "
+"telling it to use it as a <quote>NewWorld boot partition</quote>, or in "
+"<command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:832
 #, no-c-format
-msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
+msgid ""
+"The special partition type Apple_Bootstrap is required to prevent MacOS from "
+"mounting and damaging the bootstrap partition, as there are special "
+"modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:839
 #, no-c-format
-msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
+msgid ""
+"Note that the bootstrap partition is only meant to hold 3 very small files: "
+"the <command>yaboot</command> binary, its configuration <filename>yaboot."
+"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</"
+"command>. It need not and must not be mounted on your file system nor have "
+"kernels or anything else copied to it. The <command>ybin</command> and "
+"<command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:849
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
+msgid ""
+"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap "
+"partition should appear before other boot partitions on the disk, especially "
+"MacOS boot partitions. The bootstrap partition should be the first one you "
+"create. However, if you add a bootstrap partition later, you can use "
+"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder "
+"the partition map so the bootstrap partition comes right after the map "
+"(which is always partition 1). It's the logical map order, not the physical "
+"address order, that counts."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:861
 #, no-c-format
-msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
+msgid ""
+"Apple disks normally have several small driver partitions. If you intend to "
+"dual boot your machine with MacOSX, you should retain these partitions and a "
+"small HFS partition (800k is the minimum size). That is because MacOSX, on "
+"every boot, offers to initialize any disks which do not have active MacOS "
+"partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:878
 #, no-c-format
-msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
+msgid ""
+"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This "
+"is the only kind of partition scheme that the OpenBoot PROM understands, and "
+"so it's the only scheme from which you can boot. The <keycap>s</keycap> key "
+"is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:886
 #, no-c-format
-msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
+msgid ""
+"Furthermore, on &arch-title; disks, make sure your first partition on your "
+"boot disk starts at cylinder 0. While this is required, it also means that "
+"the first partition will contain the partition table and the boot block, "
+"which are the first two sectors of the disk. You must <emphasis>not</"
+"emphasis> put swap on the first partition of the boot drive, since swap "
+"partitions do not preserve the first few sectors of the partition. You can "
+"put Ext2 or UFS partitions there; these will leave the partition table and "
+"the boot block alone."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:897
 #, no-c-format
-msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
+msgid ""
+"It is also advised that the third partition should be of type <quote>Whole "
+"disk</quote> (type 5), and contain the entire disk (from the first cylinder "
+"to the last). This is simply a convention of Sun disk labels, and helps the "
+"<command>SILO</command> boot loader keep its bearings."
 msgstr ""
-
diff --git a/po/ro/post-install.po b/po/ro/post-install.po
index 8367ac28c..e22aac91d 100644
--- a/po/ro/post-install.po
+++ b/po/ro/post-install.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,27 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:15
 #, no-c-format
-msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system."
+msgid ""
+"To shut down a running &debian-gnu; system, you must not reboot with the "
+"reset switch on the front or back of your computer, or just turn off the "
+"computer. &debian-gnu; should be shut down in a controlled manner, otherwise "
+"files might get lost and/or disk damage might occur. If you run a desktop "
+"environment, there is usually an option to <quote>log out</quote> available "
+"from the application menu that allows you to shutdown (or reboot) the system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:25
 #, no-c-format
-msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system."
+msgid ""
+"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</"
+"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch="
+"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> "
+"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last "
+"option is to log in as root and type one of the commands <command>poweroff</"
+"command>, <command>halt</command> or <command>shutdown -h now</command> if "
+"either of the key combinations do not work or you prefer to type commands; "
+"use <command>reboot</command> to reboot the system."
 msgstr ""
 
 #. Tag: title
@@ -46,13 +61,26 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:47
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:55
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as &debian; packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as &debian; "
+"packages."
 msgstr ""
 
 #. Tag: title
@@ -64,7 +92,13 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:77
 #, no-c-format
-msgid "&debian; is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about &debian; to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use &debian;, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"&debian; is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about &debian; to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use &debian;, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -76,13 +110,32 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:89
 #, no-c-format
-msgid "The most important concept to grasp is the &debian; packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the &debian; packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:130
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
@@ -94,7 +147,12 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:142
 #, no-c-format
-msgid "There are official and unofficial software repositories that are not enabled in the default &debian; install. These contain software which many find important and expect to have. Information on these additional repositories can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-software;\">The Software Available for &debian;'s Stable Release</ulink>."
+msgid ""
+"There are official and unofficial software repositories that are not enabled "
+"in the default &debian; install. These contain software which many find "
+"important and expect to have. Information on these additional repositories "
+"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-"
+"software;\">The Software Available for &debian;'s Stable Release</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,7 +164,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:155
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
@@ -118,19 +179,34 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:166
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:175
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user account under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:184
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -142,25 +218,50 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:200
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:206
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about &debian;-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about &debian;-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:217
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about &debian;. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more &debian; documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The &debian; community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on &debian;."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about &debian;. In particular, see the "
+"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> "
+"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference"
+"\">Debian Reference</ulink>. An index of more &debian; documentation is "
+"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian "
+"Documentation Project</ulink>. The &debian; community is self-supporting; to "
+"subscribe to one or more of the Debian mailing lists, see the <ulink url="
+"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</"
+"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/"
+"\">Debian Mailing List Archives</ulink> contain a wealth of information on "
+"&debian;."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:235
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
@@ -172,31 +273,59 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:252
 #, no-c-format
-msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some &debian; utilities, we will try to cover the basics in this section."
+msgid ""
+"Today, email is an important part of many people's life. As there are many "
+"options as to how to set it up, and as having it set up correctly is "
+"important for some &debian; utilities, we will try to cover the basics in "
+"this section."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:259
 #, no-c-format
-msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox."
+msgid ""
+"There are three main functions that make up an e-mail system. First there is "
+"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user "
+"actually uses to compose and read mails. Then there is the <firstterm>Mail "
+"Transfer Agent</firstterm> (MTA) that takes care of transferring messages "
+"from one computer to another. And last there is the <firstterm>Mail Delivery "
+"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the "
+"user's inbox."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:269
 #, no-c-format
-msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail."
+msgid ""
+"These three functions can be performed by separate programs, but they can "
+"also be combined in one or two programs. It is also possible to have "
+"different programs handle these functions for different types of mail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:275
 #, no-c-format
-msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA."
+msgid ""
+"On Linux and Unix systems <command>mutt</command> is historically a very "
+"popular MUA. Like most traditional Linux programs it is text based. It is "
+"often used in combination with <command>exim</command> or <command>sendmail</"
+"command> as MTA and <command>procmail</command> as MDA."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:282
 #, no-c-format
-msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in &debian; available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in &debian; has to do with licensing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can &mdash; and often are &mdash; also be used in combination with the traditional Linux tools."
+msgid ""
+"With the increasing popularity of graphical desktop systems, the use of "
+"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's "
+"<command>kmail</command> or Mozilla's <command>thunderbird</command> (in "
+"&debian; available as <command>icedove</command><footnote> <para> The reason "
+"that <command>thunderbird</command> has been renamed to <command>icedove</"
+"command> in &debian; has to do with licensing issues. Details are outside "
+"the scope of this manual. </para> </footnote>) is becoming more popular. "
+"These programs combine the function of a MUA, MTA and MDA, but can &mdash; "
+"and often are &mdash; also be used in combination with the traditional Linux "
+"tools."
 msgstr ""
 
 #. Tag: title
@@ -208,19 +337,40 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:303
 #, no-c-format
-msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, &hellip; </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes."
+msgid ""
+"Even if you are planning to use a graphical mail program, it is important "
+"that a traditional MTA/MDA is also installed and correctly set up on your "
+"&debian-gnu; system. Reason is that various utilities running on the "
+"system<footnote> <para> Examples are: <command>cron</command>, "
+"<command>quota</command>, <command>logcheck</command>, <command>aide</"
+"command>, &hellip; </para> </footnote> can send important notices by e-mail "
+"to inform the system administrator of (potential) problems or changes."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:318
 #, no-c-format
-msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>."
+msgid ""
+"For this reason the packages <classname>exim4</classname> and "
+"<classname>mutt</classname> will be installed by default (provided you did "
+"not unselect the <quote>standard</quote> task during the installation). "
+"<classname>exim4</classname> is a combination MTA/MDA that is relatively "
+"small but very flexible. By default it will be configured to only handle e-"
+"mail local to the system itself and e-mails addressed to the system "
+"administrator (root account) will be delivered to the regular user account "
+"created during the installation<footnote> <para> The forwarding of mail for "
+"root to the regular user account is configured in <filename>/etc/aliases</"
+"filename>. If no regular user account was created, the mail will of course "
+"be delivered to the root account itself. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:337
 #, no-c-format
-msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>."
+msgid ""
+"When system e-mails are delivered they are added to a file in <filename>/var/"
+"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be "
+"read using <command>mutt</command>."
 msgstr ""
 
 #. Tag: title
@@ -232,31 +382,51 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:348
 #, no-c-format
-msgid "As mentioned earlier, the installed &debian; system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others."
+msgid ""
+"As mentioned earlier, the installed &debian; system is only set up to handle "
+"e-mail local to the system, not for sending mail to others nor for receiving "
+"mail from others."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:354
 #, no-c-format
-msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly."
+msgid ""
+"If you would like <classname>exim4</classname> to handle external e-mail, "
+"please refer to the next subsection for the basic available configuration "
+"options. Make sure to test that mail can be sent and received correctly."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:360
 #, no-c-format
-msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)."
+msgid ""
+"If you intend to use a graphical mail program and use a mail server of your "
+"Internet Service Provider (ISP) or your company, there is not really any "
+"need to configure <classname>exim4</classname> for handling external e-mail. "
+"Just configure your favorite graphical mail program to use the correct "
+"servers to send and receive e-mail (how is outside the scope of this manual)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:369
 #, no-c-format
-msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against &debian; packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports."
+msgid ""
+"However, in that case you may need to configure individual utilities to "
+"correctly send e-mails. One such utility is <command>reportbug</command>, a "
+"program that facilitates submitting bug reports against &debian; packages. "
+"By default it expects to be able to use <classname>exim4</classname> to "
+"submit bug reports."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:377
 #, no-c-format
-msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports."
+msgid ""
+"To correctly set up <command>reportbug</command> to use an external mail "
+"server, please run the command <command>reportbug --configure</command> and "
+"answer <quote>no</quote> to the question if an MTA is available. You will "
+"then be asked for the SMTP server to be used for submitting bug reports."
 msgstr ""
 
 #. Tag: title
@@ -268,7 +438,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:389
 #, no-c-format
-msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:"
+msgid ""
+"If you would like your system to also handle external e-mail, you will need "
+"to reconfigure the <classname>exim4</classname> package<footnote> <para> You "
+"can of course also remove <classname>exim4</classname> and replace it with "
+"an alternative MTA/MDA. </para> </footnote>:"
 msgstr ""
 
 #. Tag: screen
@@ -280,13 +454,18 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:403
 #, no-c-format
-msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option."
+msgid ""
+"After entering that command (as root), you will be asked if you want split "
+"the configuration into small files. If you are unsure, select the default "
+"option."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:409
 #, no-c-format
-msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs."
+msgid ""
+"Next you will be presented with several common mail scenarios. Choose the "
+"one that most closely resembles your needs."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +477,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:419
 #, no-c-format
-msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
+msgid ""
+"Your system is connected to a network and your mail is sent and received "
+"directly using SMTP. On the following screens you will be asked a few basic "
+"questions, like your machine's mail name, or a list of domains for which you "
+"accept or relay mail."
 msgstr ""
 
 #. Tag: term
@@ -310,13 +493,22 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:431
 #, no-c-format
-msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which takes care of sending the message on to its destination. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail."
+msgid ""
+"In this scenario your outgoing mail is forwarded to another machine, called "
+"a <quote>smarthost</quote>, which takes care of sending the message on to "
+"its destination. The smarthost also usually stores incoming mail addressed "
+"to your computer, so you don't need to be permanently online. That also "
+"means you have to download your mail from the smarthost via programs like "
+"fetchmail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:441
 #, no-c-format
-msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network."
+msgid ""
+"In a lot of cases the smarthost will be your ISP's mail server, which makes "
+"this option very suitable for dial-up users. It can also be a company mail "
+"server, or even another system on your own network."
 msgstr ""
 
 #. Tag: term
@@ -328,7 +520,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:452
 #, no-c-format
-msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled."
+msgid ""
+"This option is basically the same as the previous one except that the system "
+"will not be set up to handle mail for a local e-mail domain. Mail on the "
+"system itself (e.g. for the system administrator) will still be handled."
 msgstr ""
 
 #. Tag: term
@@ -352,19 +547,37 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:473
 #, no-c-format
-msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
+msgid ""
+"Choose this if you are absolutely convinced you know what you are doing. "
+"This will leave you with an unconfigured mail system &mdash; until you "
+"configure it, you won't be able to send or receive any mail and you may miss "
+"some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:484
 #, no-c-format
-msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has further details about configuring <classname>exim4</classname> and explains where to find additional documentation."
+msgid ""
+"If none of these scenarios suits your needs, or if you need a finer grained "
+"setup, you will need to edit configuration files under the <filename>/etc/"
+"exim4</filename> directory after the installation is complete. More "
+"information about <classname>exim4</classname> may be found under <filename>/"
+"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</"
+"filename> has further details about configuring <classname>exim4</classname> "
+"and explains where to find additional documentation."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:495
 #, no-c-format
-msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>."
+msgid ""
+"Note that sending mail directly to the Internet when you don't have an "
+"official domain name, can result in your mail being rejected because of anti-"
+"spam measures on receiving servers. Using your ISP's mail server is "
+"preferred. If you still do want to send out mail directly, you may want to "
+"use a different e-mail address than is generated by default. If you use "
+"<classname>exim4</classname> as your MTA, this is possible by adding an "
+"entry in <filename>/etc/email-addresses</filename>."
 msgstr ""
 
 #. Tag: title
@@ -376,19 +589,29 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:514
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with &debian; handles most configurations. Also, &debian; often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with &debian; handles most configurations. "
+"Also, &debian; often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:524
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:530
 #, no-c-format
-msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
@@ -430,67 +653,135 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:565
 #, no-c-format
-msgid "To compile a kernel the &debian; way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the &debian; way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<classname>linux-source-2.6</classname> and a few others which are probably "
+"already installed (see <filename>/usr/share/doc/kernel-package/README.gz</"
+"filename> for the complete list)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:574
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:582
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>&debian; way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>&debian; way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <classname>linux-source-2.6</"
+"classname>, yet still use the <classname>kernel-package</classname> "
+"compilation method."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:591
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:598
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/"
+"linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory "
+"<filename>linux-source-&kernelversion;</filename> that will have been "
+"created."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:618
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your &debian; installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your &debian; installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:633
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:638
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --"
+"revision=custom.1.0 kernel_image</userinput>. The version number of "
+"<quote>1.0</quote> can be changed at will; this is just a version number "
+"that you will use to track your kernel builds. Likewise, you can put any "
+"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel "
+"compilation may take quite a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:648
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well."
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../&kernelpackage;-"
+"&kernelversion;-<replaceable>subarchitecture</"
+"replaceable>_custom.1.0_&architecture;.deb</userinput>. The "
+"<replaceable>subarchitecture</replaceable> part is an optional sub-"
+"architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> "
+"depending on what kernel options you set. <userinput>dpkg -i</userinput> "
+"will install the kernel, along with some other nice supporting files. For "
+"instance, the <filename>System.map</filename> will be properly installed "
+"(helpful for debugging kernel problems), and <filename>/boot/config-"
+"&kernelversion;</filename> will be installed, containing your current "
+"configuration set. Your new kernel package is also clever enough to "
+"automatically update your boot loader to use the new kernel. If you have "
+"created a modules package, you'll need to install that package as well."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:668
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:673
 #, no-c-format
-msgid "For more information on &debian; kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"For more information on &debian; kernels and kernel compilation, see the "
+"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. "
+"For more information on <classname>kernel-package</classname>, read the fine "
+"documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
@@ -502,31 +793,63 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:690
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:700
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:715
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:723
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:735
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
@@ -538,6 +861,8 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:748
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/ro/preparing.po b/po/ro/preparing.po
index 9378d6304..86a142b74 100644
--- a/po/ro/preparing.po
+++ b/po/ro/preparing.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:6
 #, no-c-format
-msgid "This chapter deals with the preparation for installing &debian; before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information."
+msgid ""
+"This chapter deals with the preparation for installing &debian; before you "
+"even boot the installer. This includes backing up your data, gathering "
+"information about your hardware, and locating any necessary information."
 msgstr ""
 
 #. Tag: title
@@ -34,37 +38,59 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:20
 #, no-c-format
-msgid "First, just a note about re-installations. With &debian;, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case."
+msgid ""
+"First, just a note about re-installations. With &debian;, a circumstance "
+"that will require a complete re-installation of your system is very rare; "
+"perhaps mechanical failure of the hard disk would be the most common case."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:27
 #, no-c-format
-msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS."
+msgid ""
+"Many common operating systems may require a complete installation to be "
+"performed when critical failures take place or for upgrades to new OS "
+"versions. Even if a completely new installation isn't required, often the "
+"programs you use must be re-installed to operate properly in the new OS."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:35
 #, no-c-format
-msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the &debian; packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system."
+msgid ""
+"Under &debian-gnu;, it is much more likely that your OS can be repaired "
+"rather than replaced if things go wrong. Upgrades never require a wholesale "
+"installation; you can always upgrade in-place. And the programs are almost "
+"always compatible with successive OS releases. If a new program version "
+"requires newer supporting software, the &debian; packaging system ensures "
+"that all the necessary software is automatically identified and installed. "
+"The point is, much effort has been put into avoiding the need for re-"
+"installation, so think of it as your very last option. The installer is "
+"<emphasis>not</emphasis> designed to re-install over an existing system."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:48
 #, no-c-format
-msgid "Here's a road map for the steps you will take during the installation process."
+msgid ""
+"Here's a road map for the steps you will take during the installation "
+"process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:56
 #, no-c-format
-msgid "Back up any existing data or documents on the hard disk where you plan to install."
+msgid ""
+"Back up any existing data or documents on the hard disk where you plan to "
+"install."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:62
 #, no-c-format
-msgid "Gather information about your computer and any needed documentation, before starting the installation."
+msgid ""
+"Gather information about your computer and any needed documentation, before "
+"starting the installation."
 msgstr ""
 
 #. Tag: para
@@ -76,13 +102,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-msgid "Locate and/or download the installer software and any specialized driver or firmware files your machine requires."
+msgid ""
+"Locate and/or download the installer software and any specialized driver or "
+"firmware files your machine requires."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:79
 #, no-c-format
-msgid "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot infrastructure from which the installer can be booted."
+msgid ""
+"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
+"infrastructure from which the installer can be booted."
 msgstr ""
 
 #. Tag: para
@@ -124,7 +154,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:117
 #, no-c-format
-msgid "If necessary, resize existing partitions on your target harddisk to make space for the installation."
+msgid ""
+"If necessary, resize existing partitions on your target harddisk to make "
+"space for the installation."
 msgstr ""
 
 #. Tag: para
@@ -136,13 +168,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:127
 #, no-c-format
-msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>."
+msgid ""
+"Watch the automatic download/install/setup of the <firstterm>base system</"
+"firstterm>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:133
 #, no-c-format
-msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system."
+msgid ""
+"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
+"and/or your existing system."
 msgstr ""
 
 #. Tag: para
@@ -154,37 +190,68 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
+"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
+"of the installation system. For more information about this graphical "
+"installer, see <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:154
 #, no-c-format
-msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
+msgid ""
+"If you have problems during the installation, it helps to know which "
+"packages are involved in which steps. Introducing the leading software "
+"actors in this installation drama:"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:160
 #, no-c-format
-msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
+msgid ""
+"The installer software, <classname>debian-installer</classname>, is the "
+"primary concern of this manual. It detects hardware and loads appropriate "
+"drivers, uses <classname>dhcp-client</classname> to set up the network "
+"connection, runs <classname>debootstrap</classname> to install the base "
+"system packages, and runs <classname>tasksel</classname> to allow you to "
+"install certain additional software. Many more actors play smaller parts in "
+"this process, but <classname>debian-installer</classname> has completed its "
+"task when you load the new system for the first time."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:172
 #, no-c-format
-msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
+msgid ""
+"To tune the system to your needs, <classname>tasksel</classname> allows you "
+"to choose to install various predefined bundles of software like a Web "
+"server or a Desktop environment."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because in relation to a text-mode-only system it requires a comparatively large amount of disk space and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid ""
+"One important option during the installation is whether or not to install a "
+"graphical desktop environment, consisting of the X Window System and one of "
+"the available graphical desktop environments. If you choose not to select "
+"the <quote>Desktop environment</quote> task, you will only have a relatively "
+"basic, command line driven system. Installing the Desktop environment task "
+"is optional because in relation to a text-mode-only system it requires a "
+"comparatively large amount of disk space and because many &debian-gnu; "
+"systems are servers which don't really have any need for a graphical user "
+"interface to do their job."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Troubleshooting of the X Window System is not within the scope of this manual."
+msgid ""
+"Just be aware that the X Window System is completely separate from "
+"<classname>debian-installer</classname>, and in fact is much more "
+"complicated. Troubleshooting of the X Window System is not within the scope "
+"of this manual."
 msgstr ""
 
 #. Tag: title
@@ -196,13 +263,29 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system is going to be installed on your computer, it is quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in the installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
+msgid ""
+"Before you start, make sure to back up every file that is now on your "
+"system. If this is the first time a non-native operating system is going to "
+"be installed on your computer, it is quite likely you will need to re-"
+"partition your disk to make room for &debian-gnu;. Anytime you partition "
+"your disk, you run a risk of losing everything on the disk, no matter what "
+"program you use to do it. The programs used in the installation are quite "
+"reliable and most have seen years of use; but they are also quite powerful "
+"and a false move can cost you. Even after backing up, be careful and think "
+"about your answers and actions. Two minutes of thinking can save hours of "
+"unnecessary work."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Even though this is normally not necessary, there might be situations in which you could be required to reinstall your operating system's boot loader to make the system boot or in a worst case even have to reinstall the complete operating system and restore your previously made backup."
+msgid ""
+"If you are creating a multi-boot system, make sure that you have the "
+"distribution media of any other present operating systems on hand. Even "
+"though this is normally not necessary, there might be situations in which "
+"you could be required to reinstall your operating system's boot loader to "
+"make the system boot or in a worst case even have to reinstall the complete "
+"operating system and restore your previously made backup."
 msgstr ""
 
 #. Tag: title
@@ -238,13 +321,20 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:259
 #, no-c-format
-msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of &debian;; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is the official version of the "
+"Installation Guide for the &releasename; release of &debian;; available in "
+"<ulink url=\"&url-release-area;/installmanual\">various formats and "
+"translations</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:268
 #, no-c-format
-msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of &debian;; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is a development version of the "
+"Installation Guide for the next release of &debian;; available in <ulink url="
+"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -256,7 +346,8 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:281
 #, no-c-format
-msgid "Often contains useful information on configuring or using your hardware."
+msgid ""
+"Often contains useful information on configuring or using your hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -286,7 +377,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:314
 #, no-c-format
-msgid "Documentation of &arch-title;-specific boot sequence, commands and device drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
+msgid ""
+"Documentation of &arch-title;-specific boot sequence, commands and device "
+"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
 msgstr ""
 
 #. Tag: ulink
@@ -298,7 +391,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:330
 #, no-c-format
-msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
+msgid ""
+"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
+"&arch-title; hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -310,7 +405,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:346
 #, no-c-format
-msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about &debian; but the basic installation concepts are the same across all &arch-title; distributions."
+msgid ""
+"IBM Redbook describing the Linux distributions available for the mainframe. "
+"It has no chapter about &debian; but the basic installation concepts are the "
+"same across all &arch-title; distributions."
 msgstr ""
 
 #. Tag: ulink
@@ -328,7 +426,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:368
 #, no-c-format
-msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
+msgid ""
+"In many cases, the installer will be able to automatically detect your "
+"hardware. But to be prepared, we do recommend familiarizing yourself with "
+"your hardware before the install."
 msgstr ""
 
 #. Tag: para
@@ -346,7 +447,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys or key combinations. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
+msgid ""
+"The BIOS setup screens of your computer. You can view these screens when you "
+"start your computer by pressing a combination of keys. Check your manual for "
+"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
+"keycap> key, but some manufacturers use other keys or key combinations. "
+"Usually upon starting the computer there will be a message stating which key "
+"to press to enter the setup screen."
 msgstr ""
 
 #. Tag: para
@@ -364,13 +471,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:408
 #, no-c-format
-msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
+msgid ""
+"System commands or tools in another operating system, including file manager "
+"displays. This source is especially useful for information about RAM and "
+"hard drive memory."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:415
 #, no-c-format
-msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
+msgid ""
+"Your system administrator or Internet Service Provider. These sources can "
+"tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
 #. Tag: title
@@ -514,61 +626,115 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-msgid "Many products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems."
+msgid ""
+"Many products work without trouble on &arch-kernel;. Moreover, hardware "
+"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
+"does not run as many different types of hardware as some operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:516
 #, no-c-format
-msgid "Drivers in &arch-kernel; in most cases are not written for a certain <quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names."
+msgid ""
+"Drivers in &arch-kernel; in most cases are not written for a certain "
+"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
+"but for a certain hardware/chipset. Many seemingly different products/brands "
+"are based on the same hardware design; it is not uncommon that chip "
+"manufacturers provide so-called <quote>reference designs</quote> for "
+"products based on their chips which are then used by several different "
+"device manufacturers and sold under lots of different product or brand names."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:527
 #, no-c-format
-msgid "This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them."
+msgid ""
+"This has advantages and disadvantages. An advantage is that a driver for one "
+"chipset works with lots of different products from different manufacturers, "
+"as long as their product is based on the same chipset. The disadvantage is "
+"that it is not always easy to see which actual chipset is used in a certain "
+"product/brand. Unfortunately sometimes device manufacturers change the "
+"hardware base of their product without changing the product name or at least "
+"the product version number, so that when having two items of the same brand/"
+"product name bought at different times, they can sometimes be based on two "
+"different chipsets and therefore use two different drivers or there might be "
+"no driver at all for one of them."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:540
 #, no-c-format
-msgid "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and <quote>product</quote> IDs, and the combination of these two is usually the same for any product based on the same chipset."
+msgid ""
+"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
+"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
+"Express/ExpressCard devices have so called <quote>vendor</quote> and "
+"<quote>product</quote> IDs, and the combination of these two is usually the "
+"same for any product based on the same chipset."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:548
 #, no-c-format
-msgid "On Linux systems, these IDs can be read with the <command>lsusb</command> command for USB devices and with the <command>lspci -nn</command> command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as <quote>1d6b:0001</quote>."
+msgid ""
+"On Linux systems, these IDs can be read with the <command>lsusb</command> "
+"command for USB devices and with the <command>lspci -nn</command> command "
+"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
+"usually given in the form of two hexadecimal numbers, seperated by a colon, "
+"such as <quote>1d6b:0001</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:556
 #, no-c-format
-msgid "An example for the output of <command>lsusb</command>: <quote>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the vendor ID and 0002 is the product ID."
+msgid ""
+"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
+"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
+"vendor ID and 0002 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:562
 #, no-c-format
-msgid "An example for the output of <command>lspci -nn</command> for an Ethernet card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID."
+msgid ""
+"An example for the output of <command>lspci -nn</command> for an Ethernet "
+"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
+"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
+"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
+"here 10ec is the vendor- and 8168 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:570
 #, no-c-format
-msgid "As another example, a graphics card could give the following output: <quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
+msgid ""
+"As another example, a graphics card could give the following output: "
+"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
+"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:576
 #, no-c-format
-msgid "On Windows systems, the IDs for a device can be found in the Windows device manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the device manager's details tab to actually see the IDs, as they are not displayed by default."
+msgid ""
+"On Windows systems, the IDs for a device can be found in the Windows device "
+"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
+"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
+"you have to select the property <quote>Hardware IDs</quote> in the device "
+"manager's details tab to actually see the IDs, as they are not displayed by "
+"default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:586
 #, no-c-format
-msgid "Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and <quote>driver</quote> as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the graphics card example), can help."
+msgid ""
+"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
+"quote> and <quote>driver</quote> as the search terms often results in "
+"information regarding the driver support status for a certain chipset. If a "
+"search for the vendor/product ID does not yield usable results, a search for "
+"the chip code names, which are also often provided by lsusb and lspci "
+"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
+"and <quote>RV710</quote> in the graphics card example), can help."
 msgstr ""
 
 #. Tag: title
@@ -580,19 +746,42 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:601
 #, no-c-format
-msgid "&debian-gnu; is also available as a so-called <quote>live system</quote> for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by &debian-gnu;, the easiest way is to run a &debian; live system on it and try it out."
+msgid ""
+"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
+"certain architectures. A live system is a preconfigured ready-to-use system "
+"in a compressed format that can be booted and used from a read-only medium "
+"like a CD or DVD. Using it by default does not create any permanent changes "
+"on your computer. You can change user settings and install additional "
+"programs from within the live system, but all this only happens in the "
+"computer's RAM, i.e. if you turn off the computer and boot the live system "
+"again, everything is reset to its defaults. If you want to see whether your "
+"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
+"live system on it and try it out."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:614
 #, no-c-format
-msgid "There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official &debian-gnu; live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the &d-i;, so installation of non-free components must be done manually if needed."
+msgid ""
+"There are a few limitations in using a live system. The first is that as all "
+"changes you do within the live system must be held in your computer's RAM, "
+"this only works on systems with enough RAM to do that, so installing "
+"additional large software packages may fail due to memory constraints. "
+"Another limitation with regards to hardware compatibility testing is that "
+"the official &debian-gnu; live system contains only free components, i.e. "
+"there are no non-free firmware files included in it. Such non-free packages "
+"can of course be installed manually within the system, but there is no "
+"automatic detection of required firmware files like in the &d-i;, so "
+"installation of non-free components must be done manually if needed."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:627
 #, no-c-format
-msgid "Information about the available variants of the &debian; live images can be found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</ulink>."
+msgid ""
+"Information about the available variants of the &debian; live images can be "
+"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
+"ulink>."
 msgstr ""
 
 #. Tag: title
@@ -604,7 +793,11 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-msgid "If your computer is connected to a fixed network (i.e. an Ethernet or equivalent connection &mdash; not a dialup/PPP connection) which is administered by somebody else, you should ask your network's system administrator for this information:"
+msgid ""
+"If your computer is connected to a fixed network (i.e. an Ethernet or "
+"equivalent connection &mdash; not a dialup/PPP connection) which is "
+"administered by somebody else, you should ask your network's system "
+"administrator for this information:"
 msgstr ""
 
 #. Tag: para
@@ -634,31 +827,47 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:671
 #, no-c-format
-msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
+msgid ""
+"The IP address of the default gateway system you should route to, if your "
+"network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:677
 #, no-c-format
-msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
+msgid ""
+"The system on your network that you should use as a DNS (Domain Name "
+"Service) server."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-msgid "If the network you are connected to uses DHCP (Dynamic Host Configuration Protocol) for configuring network settings, you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
+msgid ""
+"If the network you are connected to uses DHCP (Dynamic Host Configuration "
+"Protocol) for configuring network settings, you don't need this information "
+"because the DHCP server will provide it directly to your computer during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:692
 #, no-c-format
-msgid "If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default."
+msgid ""
+"If you have internet access via DSL or cable modem (i.e. over a cable tv "
+"network) and have a router (often provided preconfigured by your phone or "
+"catv provider) which handles your network connectivity, DHCP is usually "
+"available by default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:700
 #, no-c-format
-msgid "As a rule of thumb: if you run a Windows system in your home network and did not have to manually perform any network settings there to achieve Internet access, network connectivity in &debian-gnu; will also be configured automatically."
+msgid ""
+"As a rule of thumb: if you run a Windows system in your home network and did "
+"not have to manually perform any network settings there to achieve Internet "
+"access, network connectivity in &debian-gnu; will also be configured "
+"automatically."
 msgstr ""
 
 #. Tag: para
@@ -688,19 +897,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:735
 #, no-c-format
-msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
+msgid ""
+"Once you have gathered information about your computer's hardware, check "
+"that your hardware will let you do the type of installation that you want to "
+"do."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:741
 #, no-c-format
-msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
+msgid ""
+"Depending on your needs, you might manage with less than some of the "
+"recommended hardware listed in the table below. However, most users risk "
+"being frustrated if they ignore these suggestions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:747
 #, no-c-format
-msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
+msgid ""
+"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
 msgstr ""
 
 #. Tag: para
@@ -790,31 +1006,58 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:785
 #, no-c-format
-msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
+msgid ""
+"The actual minimum memory requirements are a lot less then the numbers "
+"listed in this table. Depending on the architecture, it is possible to "
+"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
+"same goes for the disk space requirements, especially if you pick and choose "
+"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
+"additional information on disk space requirements."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:795
 #, no-c-format
-msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
+msgid ""
+"It is possible to run a graphical desktop environment on older or low-end "
+"systems, but in that case it is recommended to install a window manager that "
+"is less resource-hungry than those of the GNOME or KDE desktop environments; "
+"alternatives include <classname>xfce4</classname>, <classname>icewm</"
+"classname> and <classname>wmaker</classname>, but there are others to choose "
+"from."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:804
 #, no-c-format
-msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
+msgid ""
+"It is practically impossible to give general memory or disk space "
+"requirements for server installations as those very much depend on what the "
+"server is to be used for."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:810
 #, no-c-format
-msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
+msgid ""
+"Remember that these sizes don't include all the other materials which are "
+"usually to be found, such as user files, mail, and data. It is always best "
+"to be generous when considering the space for your own files and data."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:817
 #, no-c-format
-msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to &debian; in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
+msgid ""
+"Disk space required for the smooth operation of the &debian-gnu; system "
+"itself is taken into account in these recommended system requirements. "
+"Notably, the <filename>/var</filename> partition contains a lot of state "
+"information specific to &debian; in addition to its regular contents, like "
+"logfiles. The <command>dpkg</command> files (with information on all "
+"installed packages) can easily consume 40MB. Also, <command>apt-get</"
+"command> puts downloaded packages here before they are installed. You should "
+"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
+"more if you install a graphical desktop environment."
 msgstr ""
 
 #. Tag: title
@@ -826,43 +1069,83 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:842
 #, no-c-format
-msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
+msgid ""
+"Partitioning your disk simply refers to the act of breaking up your disk "
+"into sections. Each section is then independent of the others. It's roughly "
+"equivalent to putting up walls inside a house; if you add furniture to one "
+"room it doesn't affect any other room."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:849
 #, no-c-format
-msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
+msgid ""
+"Whenever this section talks about <quote>disks</quote> you should translate "
+"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
+"means an LPAR or VM guest in this case."
 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 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."
 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 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
 #: preparing.xml:884
 #, no-c-format
-msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
+msgid ""
+"In general, changing a partition with a file system already on it will "
+"destroy any information there. Thus you should always make backups before "
+"doing any repartitioning. Using the analogy of the house, you would probably "
+"want to move all the furniture out of the way before moving a wall or you "
+"risk destroying it."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:892
 #, no-c-format
-msgid "Several modern operating systems offer the ability to move and resize certain existing partitions without destroying their contents. This allows making space for additional partitions without losing existing data. Even though this works quite well in most cases, making changes to the partitioning of a disk is an inherently dangerous action and should only be done after having made a full backup of all data. <phrase arch=\"any-x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, the ability to move and resize them losslessly is provided both by &d-i; as well as by the integrated Disk Manager of Windows 7. </phrase>"
+msgid ""
+"Several modern operating systems offer the ability to move and resize "
+"certain existing partitions without destroying their contents. This allows "
+"making space for additional partitions without losing existing data. Even "
+"though this works quite well in most cases, making changes to the "
+"partitioning of a disk is an inherently dangerous action and should only be "
+"done after having made a full backup of all data. <phrase arch=\"any-"
+"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
+"the ability to move and resize them losslessly is provided both by &d-i; as "
+"well as by the integrated Disk Manager of Windows 7. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:907
 #, no-c-format
-msgid "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size."
+msgid ""
+"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
+"to the partitioning step, select the option for manual partitioning, select "
+"the partition to resize, and simply specify its new size."
 msgstr ""
 
 #. Tag: emphasis
@@ -874,25 +1157,50 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:917
 #, no-c-format
-msgid "Creating and deleting partitions can be done from within &d-i; as well as from an existing operating system. As a rule of thumb, partitions should be created by the system for which they are to be used, i.e. partitions to be used by &debian-gnu; should be created from within &d-i; and partitions to be used from another operating system should be created from there. &d-i; is capable of creating non-&arch-kernel; partitions, and partitions created this way usually work without problems when used in other operating systems, but there are a few rare corner cases in which this could cause problems, so if you want to be sure, use the native partitioning tools to create partitions for use by other operating systems."
+msgid ""
+"Creating and deleting partitions can be done from within &d-i; as well as "
+"from an existing operating system. As a rule of thumb, partitions should be "
+"created by the system for which they are to be used, i.e. partitions to be "
+"used by &debian-gnu; should be created from within &d-i; and partitions to "
+"be used from another operating system should be created from there. &d-i; is "
+"capable of creating non-&arch-kernel; partitions, and partitions created "
+"this way usually work without problems when used in other operating systems, "
+"but there are a few rare corner cases in which this could cause problems, so "
+"if you want to be sure, use the native partitioning tools to create "
+"partitions for use by other operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with the &debian; installation. Windows and other OS installations may destroy your ability to start &debian;, or encourage you to reformat non-native partitions."
+msgid ""
+"If you are going to install more than one operating system on the same "
+"machine, you should install all other system(s) before proceeding with the "
+"&debian; installation. Windows and other OS installations may destroy your "
+"ability to start &debian;, or encourage you to reformat non-native "
+"partitions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:938
 #, no-c-format
-msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
+msgid ""
+"You can recover from these actions or avoid them, but installing the native "
+"system first saves you trouble."
 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 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."
 msgstr ""
 
 #. Tag: title
@@ -904,7 +1212,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1021
 #, no-c-format
-msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and &debian; on the same machine, it is recommended that you partition using SunOS prior to installing &debian;. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
+msgid ""
+"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
+"both SunOS and &debian; on the same machine, it is recommended that you "
+"partition using SunOS prior to installing &debian;. The Linux kernel "
+"understands Sun disk labels, so there are no problems there. SILO supports "
+"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
+"iso9660 (CDROM) partitions."
 msgstr ""
 
 #. Tag: title
@@ -916,13 +1230,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1035
 #, no-c-format
-msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
+msgid ""
+"Whatever system you are using to partition, make sure you create a "
+"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
+"partition scheme that the OpenBoot PROM understands, and so it's the only "
+"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
+"keycap> key is used to create Sun disk labels. You only need to do this on "
+"drives that do not already have a Sun disk label. If you are using a drive "
+"that was previously formatted using a PC (or other architecture) you must "
+"create a new disk label, or problems with the disk geometry will most likely "
+"occur."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1047
 #, no-c-format
-msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
+msgid ""
+"You will probably be using <command>SILO</command> as your boot loader (the "
+"small program which runs the operating system kernel). <command>SILO</"
+"command> has certain requirements for partition sizes and location; see "
+"<xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: title
@@ -934,25 +1261,49 @@ 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>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>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1071
 #, 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."
+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
 #, 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 ""
+"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."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1090
 #, 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 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."
 msgstr ""
 
 #. Tag: title
@@ -964,7 +1315,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1111
 #, 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)."
+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
@@ -976,7 +1333,15 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1128
 #, 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."
+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
@@ -988,31 +1353,63 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1144
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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>"
+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: title
@@ -1024,29 +1421,53 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1204
 #, 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."
+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:1212
 #, 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."
+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:1220
 #, no-c-format
 msgid ""
-      "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
-      "ok\n"
-      "0 &gt;\n"
-      "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
+"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
+"ok\n"
+"0 &gt;\n"
+"</screen></informalexample> Note that on older model &arch-title; Macs, the "
+"default and sometimes hardwired I/O for OpenFirmware user interaction is "
+"through the serial (modem) port. If you invoke OpenFirmware on one of these "
+"machines, you will just see a black screen. In that case, a terminal program "
+"running on another computer, connected to the modem port, is needed to "
+"interact with OpenFirmware."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1233
 #, 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."
+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
@@ -1058,45 +1479,90 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1255
 #, 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."
+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:1263
 #, 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."
+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:1275
 #, 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."
+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:1288
 #, 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>."
+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:1298
 #, 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"
-      "<replaceable>driver-name</replaceable>@\n"
-      "<replaceable>unit-address</replaceable>:\n"
-      "<replaceable>device-arguments</replaceable>\n"
-      "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
+"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"
+"<replaceable>driver-name</replaceable>@\n"
+"<replaceable>unit-address</replaceable>:\n"
+"<replaceable>device-arguments</replaceable>\n"
+"</screen></informalexample> In older revisions of OpenBoot, device naming is "
+"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
+"disk devices are of the form <quote>sd(<replaceable>controller</"
+"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
+"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
+"newer OpenBoot revisions is useful for viewing the currently configured "
+"devices. For full information, whatever your revision, see the <ulink url="
+"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1321
 #, 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"
-      "# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
-      "</screen></informalexample> and under Solaris:"
+"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"
+"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
+"</screen></informalexample> and under Solaris:"
 msgstr ""
 
 #. Tag: screen
@@ -1114,19 +1580,45 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1351
 #, 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."
+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:1363
 #, 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."
+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:1373
 #, 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."
+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
@@ -1138,7 +1630,12 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1391
 #, 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."
+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
@@ -1150,13 +1647,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1407
 #, 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."
+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:1417
 #, 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."
+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
@@ -1168,13 +1678,21 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1436
 #, 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."
+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:1444
 #, 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."
+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
@@ -1198,7 +1716,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1464
 #, 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."
+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
@@ -1210,6 +1734,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1479
 #, 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>."
+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 ""
-
diff --git a/po/ro/preseed.po b/po/ro/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/ro/preseed.po
+++ b/po/ro/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-
diff --git a/po/ro/random-bits.po b/po/ro/random-bits.po
index ff94f432b..26dbb7c32 100644
--- a/po/ro/random-bits.po
+++ b/po/ro/random-bits.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,7 +29,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:12
 #, no-c-format
-msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below."
+msgid ""
+"In Linux various special files can be found under the directory <filename>/"
+"dev</filename>. These files are called device files and behave unlike "
+"ordinary files. The most common types of device files are for block devices "
+"and character devices. These files are an interface to the actual driver "
+"(part of the Linux kernel) which in turn accesses the hardware. Another, "
+"less common, type of device file is the named <firstterm>pipe</firstterm>. "
+"The most important device files are listed in the tables below."
 msgstr ""
 
 #. Tag: filename
@@ -316,33 +324,62 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:126
 #, no-c-format
-msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. Normally, this is a simple matter of installing <filename>gpm</"
+"filename> and the X server itself. Both should be configured to use "
+"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse "
+"protocol is named <userinput>exps2</userinput> in gpm, and "
+"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files "
+"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:137
 #, no-c-format
-msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>."
+msgid ""
+"Certain kernel modules must be loaded in order for your mouse to work. In "
+"most cases the correct modules are autodetected, but not always for old-"
+"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole "
+"D-shaped connector; bus mice have an 8-pin round connector, not to be "
+"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round "
+"connector of an ADB mouse. </para> </footnote>, which are quite rare except "
+"on very old computers. Summary of Linux kernel modules needed for different "
+"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</"
+"entry> <entry>Description</entry> </row> </thead><tbody> <row> "
+"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </"
+"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</"
+"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> "
+"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech "
+"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse "
+"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></"
+"informaltable> To load a mouse driver module, you can use the "
+"<command>modconf</command> command (from the package with the same name) and "
+"look in the category <userinput>kernel/drivers/input/mouse</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:184
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:191
 #, no-c-format
 msgid ""
-      "# 3-button mouse emulation\n"
-      "# turn on emulation\n"
-      "/dev/mac_hid/mouse_button_emulation = 1\n"
-      "# Send middle mouse button signal with the F11 key\n"
-      "/dev/mac_hid/mouse_button2_keycode = 87\n"
-      "# Send right mouse button signal with the F12 key\n"
-      "/dev/mac_hid/mouse_button3_keycode = 88\n"
-      "# For different keys, use showkey to tell you what the code is."
+"# 3-button mouse emulation\n"
+"# turn on emulation\n"
+"/dev/mac_hid/mouse_button_emulation = 1\n"
+"# Send middle mouse button signal with the F11 key\n"
+"/dev/mac_hid/mouse_button2_keycode = 87\n"
+"# Send right mouse button signal with the F12 key\n"
+"/dev/mac_hid/mouse_button3_keycode = 88\n"
+"# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
 #. Tag: title
@@ -354,31 +391,54 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "A standard installation for the amd64 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB."
+msgid ""
+"A standard installation for the amd64 architecture, including all standard "
+"packages and using the default 2.6 kernel, takes up &std-system-size;MB of "
+"disk space. A minimal base installation, without the <quote>Standard system</"
+"quote> task selected, will take &base-system-size;MB."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:207
 #, no-c-format
-msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use."
+msgid ""
+"In both cases this is the actual disk space used <emphasis>after</emphasis> "
+"the installation is finished and any temporary files deleted. It also does "
+"not take into account overhead used by the file system, for example for "
+"journal files. This means that significantly more disk space is needed both "
+"<emphasis>during</emphasis> the installation and for normal system use."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:216
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:223
 #, no-c-format
-msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)."
+msgid ""
+"By default the installer will install the GNOME desktop environment, but "
+"alternative desktop environments can be selected either by using one of the "
+"special CD images, or by specifying the desired desktop environment when the "
+"installer is booted (see <xref linkend=\"pkgsel\"/>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:230
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the standard installation when determining the size of partitions. Most of "
+"the size listed as <quote>Installed size</quote> will end up in <filename>/"
+"usr</filename> and in <filename>/lib</filename>; the size listed as "
+"<quote>Download size</quote> is (temporarily) required in <filename>/var</"
+"filename>."
 msgstr ""
 
 #. Tag: entry
@@ -522,7 +582,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid ""
+"There is some overlap of the Laptop task with the Desktop environment task. "
+"If you install both, the Laptop task will only require a few MB additional "
+"disk space."
 msgstr ""
 
 #. Tag: entry
@@ -714,7 +777,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:350
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -726,19 +793,40 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:367
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
+msgid ""
+"This section explains how to install &debian-gnu; from an existing Unix or "
+"Linux system, without using the menu-driven installer as explained in the "
+"rest of the manual. This <quote>cross-install</quote> HOWTO has been "
+"requested by users switching to &debian-gnu; from Red Hat, Mandriva, and "
+"SUSE. In this section some familiarity with entering *nix commands and "
+"navigating the file system is assumed. In this section, <prompt>$</prompt> "
+"symbolizes a command to be entered in the user's current system, while "
+"<prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:379
 #, no-c-format
-msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new &debian; system configured to your preference, you "
+"can migrate your existing user data (if any) to it, and keep on rolling. "
+"This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's "
+"also a clever way for dealing with hardware that otherwise doesn't play "
+"friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:390
 #, no-c-format
-msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
+msgid ""
+"As this is a mostly manual procedure, you should bear in mind that you will "
+"need to do a lot of basic configuration of the system yourself, which will "
+"also require more knowledge of &debian; and of &arch-kernel; in general than "
+"performing a regular installation. You cannot expect this procedure to "
+"result in a system that is identical to a system from a regular "
+"installation. You should also keep in mind that this procedure only gives "
+"the basic steps to set up a system. Additional installation and/or "
+"configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
@@ -750,41 +838,56 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:405
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need around &base-"
+"system-size;MB of space available for a console only install, or about &task-"
+"desktop-lxde-inst;MB if you plan to install X (more if you intend to install "
+"desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:413
 #, no-c-format
 msgid ""
-      "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
-      "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
-      "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"Next, create file systems on the partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
+"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:423
 #, no-c-format
 msgid ""
-      "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
-      "# mkswap /dev/<replaceable>hda5</replaceable>\n"
-      "# sync; sync; sync\n"
-      "# swapon /dev/<replaceable>hda5</replaceable>\n"
-      "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"Initialize and activate swap (substitute the partition number for your "
+"intended &debian; swap partition): <informalexample><screen>\n"
+"# mkswap /dev/<replaceable>hda5</replaceable>\n"
+"# sync; sync; sync\n"
+"# swapon /dev/<replaceable>hda5</replaceable>\n"
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:435
 #, no-c-format
 msgid ""
-      "# mkdir /mnt/debinst\n"
-      "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
+"# mkdir /mnt/debinst\n"
+"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:438
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
@@ -796,26 +899,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:449
 #, no-c-format
-msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The utility used by the &debian; installer, and recognized as the official "
+"way to install a &debian; base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname> and basic Unix/Linux "
+"tools<footnote> <para> These include the GNU core utilities and commands "
+"like <command>sed</command>, <command>grep</command>, <command>tar</command> "
+"and <command>gzip</command>. </para> </footnote>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:479
 #, no-c-format
 msgid ""
-      "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
-      "# mkdir work\n"
-      "# cd work\n"
-      "</screen></informalexample> The <command>debootstrap</command> binary is located in the &debian; archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files."
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
+"# mkdir work\n"
+"# cd work\n"
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the &debian; archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the files from it. "
+"You will need to have root privileges to install the files."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:494
 #, no-c-format
 msgid ""
-      "# ar -x debootstrap_0.X.X_all.deb\n"
-      "# cd /\n"
-      "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
+"# ar -x debootstrap_0.X.X_all.deb\n"
+"# cd /\n"
+"# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
 #. Tag: title
@@ -827,27 +945,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any &debian; archive mirror "
+"for <userinput>&archive-mirror;/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:510
 #, no-c-format
-msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>amd64</userinput>, "
+"<userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, "
+"<userinput>mipsel</userinput>, <userinput>powerpc</userinput>, "
+"<userinput>s390</userinput>, <userinput>s390x</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:533
 #, no-c-format
 msgid ""
-      "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
-      "     /mnt/debinst http://ftp.us.debian.org/debian"
+"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
+"     /mnt/debinst http://ftp.us.debian.org/debian"
 msgstr ""
 
 #. Tag: title
@@ -860,9 +993,11 @@ msgstr ""
 #: random-bits.xml:540
 #, no-c-format
 msgid ""
-      "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
-      "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
-      "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:"
+"Now you've got a real &debian; system, though rather lean, on disk. "
+"<command>chroot</command> into it: <informalexample><screen>\n"
+"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
+"</screen></informalexample> After chrooting you may need to set the terminal "
+"definition to be compatible with the &debian; base system, for example:"
 msgstr ""
 
 #. Tag: screen
@@ -880,7 +1015,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:556
 #, no-c-format
-msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
+msgid ""
+"At this point <filename>/dev/</filename> only contains very basic device "
+"files. For the next steps of the installation additional device files may be "
+"needed. There are different ways to go about this and which method you "
+"should use depends on the host system you are using for the installation, on "
+"whether you intend to use a modular kernel or not, and on whether you intend "
+"to use dynamic (e.g. using <classname>udev</classname>) or static device "
+"files for the new system."
 msgstr ""
 
 #. Tag: para
@@ -892,28 +1034,34 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:571
 #, no-c-format
-msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
+msgid ""
+"install the makedev package, and create a default set of static device files "
+"using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:575
 #, no-c-format
 msgid ""
-      "# apt-get install makedev\n"
-      "# cd /dev\n"
-      "# MAKEDEV generic"
+"# apt-get install makedev\n"
+"# cd /dev\n"
+"# MAKEDEV generic"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:578
 #, no-c-format
-msgid "manually create only specific device files using <command>MAKEDEV</command>"
+msgid ""
+"manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:583
 #, no-c-format
-msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
+msgid ""
+"bind mount /dev from your host system on top of /dev in the target system; "
+"note that the postinst scripts of some packages may try to create device "
+"files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
@@ -926,34 +1074,44 @@ msgstr ""
 #: random-bits.xml:597
 #, no-c-format
 msgid ""
-      "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
-      "# editor /etc/fstab\n"
-      "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
-      "# /etc/fstab: static file system information.\n"
-      "#\n"
-      "# file system    mount point   type    options                  dump pass\n"
-      "/dev/XXX         /             ext3    defaults                 0    1\n"
-      "/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
-      "\n"
-      "/dev/XXX         none          swap    sw                       0    0\n"
-      "proc             /proc         proc    defaults                 0    0\n"
-      "\n"
-      "/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
-      "/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
-      "\n"
-      "/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
-      "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-      "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n"
-      "# mount /path   # e.g.: mount /usr\n"
-      "</screen></informalexample> Current &debian; systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n"
-      "# cd /media\n"
-      "# mkdir cdrom0\n"
-      "# ln -s cdrom0 cdrom\n"
-      "# cd /\n"
-      "# ln -s media/cdrom\n"
-      "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
+"# editor /etc/fstab\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
+"# /etc/fstab: static file system information.\n"
+"#\n"
+"# file system    mount point   type    options                  dump pass\n"
+"/dev/XXX         /             ext3    defaults                 0    1\n"
+"/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
+"\n"
+"/dev/XXX         none          swap    sw                       0    0\n"
+"proc             /proc         proc    defaults                 0    0\n"
+"\n"
+"/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
+"/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
+"\n"
+"/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
+"/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or, to mount file systems individually, use: <informalexample><screen>\n"
+"# mount /path   # e.g.: mount /usr\n"
+"</screen></informalexample> Current &debian; systems have mountpoints for "
+"removable media under <filename>/media</filename>, but keep compatibility "
+"symlinks in <filename>/</filename>. Create these as as needed, for example: "
+"<informalexample><screen>\n"
+"# cd /media\n"
+"# mkdir cdrom0\n"
+"# ln -s cdrom0 cdrom\n"
+"# cd /\n"
+"# ln -s media/cdrom\n"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -965,7 +1123,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:625
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -983,15 +1144,19 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:638
 #, no-c-format
-msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
+msgid ""
+"An option in the file <filename>/etc/default/rcS</filename> determines "
+"whether the system will interpret the hardware clock as being set to UTC or "
+"local time. The following command allows you to set that and choose your "
+"timezone."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:645
 #, no-c-format
 msgid ""
-      "# editor /etc/default/rcS\n"
-      "# dpkg-reconfigure tzdata"
+"# editor /etc/default/rcS\n"
+"# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
@@ -1004,54 +1169,64 @@ msgstr ""
 #: random-bits.xml:652
 #, no-c-format
 msgid ""
-      "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
-      "# editor /etc/network/interfaces\n"
-      "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
-      "######################################################################\n"
-      "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
-      "# See the interfaces(5) manpage for information on what options are\n"
-      "# available.\n"
-      "######################################################################\n"
-      "\n"
-      "# We always want the loopback interface.\n"
-      "#\n"
-      "auto lo\n"
-      "iface lo inet loopback\n"
-      "\n"
-      "# To use dhcp:\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet dhcp\n"
-      "\n"
-      "# An example static IP setup: (broadcast and gateway are optional)\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet static\n"
-      "#     address 192.168.0.42\n"
-      "#     network 192.168.0.0\n"
-      "#     netmask 255.255.255.0\n"
-      "#     broadcast 192.168.0.255\n"
-      "#     gateway 192.168.0.1\n"
-      "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "# editor /etc/resolv.conf\n"
-      "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "search hqdom.local\n"
-      "nameserver 10.1.1.36\n"
-      "nameserver 192.168.9.100\n"
-      "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
-      "# echo DebianHostName &gt; /etc/hostname\n"
-      "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n"
-      "127.0.0.1 localhost\n"
-      "127.0.1.1 DebianHostName\n"
-      "\n"
-      "# The following lines are desirable for IPv6 capable hosts\n"
-      "::1     ip6-localhost ip6-loopback\n"
-      "fe00::0 ip6-localnet\n"
-      "ff00::0 ip6-mcastprefix\n"
-      "ff02::1 ip6-allnodes\n"
-      "ff02::2 ip6-allrouters\n"
-      "ff02::3 ip6-allhosts\n"
-      "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> "
+"and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
+"# editor /etc/network/interfaces\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"######################################################################\n"
+"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
+"# See the interfaces(5) manpage for information on what options are\n"
+"# available.\n"
+"######################################################################\n"
+"\n"
+"# We always want the loopback interface.\n"
+"#\n"
+"auto lo\n"
+"iface lo inet loopback\n"
+"\n"
+"# To use dhcp:\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet dhcp\n"
+"\n"
+"# An example static IP setup: (broadcast and gateway are optional)\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet static\n"
+"#     address 192.168.0.42\n"
+"#     network 192.168.0.0\n"
+"#     netmask 255.255.255.0\n"
+"#     broadcast 192.168.0.255\n"
+"#     gateway 192.168.0.1\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"# editor /etc/resolv.conf\n"
+"</screen></informalexample> A simple example <filename>/etc/resolv.conf</"
+"filename>: <informalexample><screen>\n"
+"search hqdom.local\n"
+"nameserver 10.1.1.36\n"
+"nameserver 192.168.9.100\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
+"# echo DebianHostName &gt; /etc/hostname\n"
+"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with "
+"IPv6 support: <informalexample><screen>\n"
+"127.0.0.1 localhost\n"
+"127.0.1.1 DebianHostName\n"
+"\n"
+"# The following lines are desirable for IPv6 capable hosts\n"
+"::1     ip6-localhost ip6-loopback\n"
+"fe00::0 ip6-localnet\n"
+"ff00::0 ip6-mcastprefix\n"
+"ff02::1 ip6-allnodes\n"
+"ff02::2 ip6-allrouters\n"
+"ff02::3 ip6-allhosts\n"
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1064,12 +1239,16 @@ msgstr ""
 #: random-bits.xml:694
 #, no-c-format
 msgid ""
-      "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
-      "deb-src http://ftp.us.debian.org/debian &releasename; main\n"
-      "\n"
-      "deb http://security.debian.org/ &releasename;/updates main\n"
-      "deb-src http://security.debian.org/ &releasename;/updates main\n"
-      "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list."
+"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</"
+"filename> that will allow installing additional packages. However, you may "
+"want to add some additional sources, for example for source packages and "
+"security updates: <informalexample><screen>\n"
+"deb-src http://ftp.us.debian.org/debian &releasename; main\n"
+"\n"
+"deb http://security.debian.org/ &releasename;/updates main\n"
+"deb-src http://security.debian.org/ &releasename;/updates main\n"
+"</screen></informalexample> Make sure to run <userinput>aptitude update</"
+"userinput> after you have made changes to the sources list."
 msgstr ""
 
 #. Tag: title
@@ -1082,24 +1261,29 @@ msgstr ""
 #: random-bits.xml:711
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
-      "# aptitude install locales\n"
-      "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> To configure your keyboard (if needed):"
+"To configure your locale settings to use a language other than English, "
+"install the <classname>locales</classname> support package and configure it. "
+"Currently the use of UTF-8 locales is recommended. "
+"<informalexample><screen>\n"
+"# aptitude install locales\n"
+"# dpkg-reconfigure locales\n"
+"</screen></informalexample> To configure your keyboard (if needed):"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:721
 #, no-c-format
 msgid ""
-      "# aptitude install console-setup\n"
-      "# dpkg-reconfigure keyboard-configuration"
+"# aptitude install console-setup\n"
+"# dpkg-reconfigure keyboard-configuration"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:723
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1111,7 +1295,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:734
 #, no-c-format
-msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
+msgid ""
+"If you intend to boot this system, you probably want a &arch-kernel; kernel "
+"and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
@@ -1129,7 +1315,9 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:745
 #, no-c-format
-msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid ""
+"# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</"
+"replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1141,30 +1329,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:752
 #, no-c-format
-msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
+msgid ""
+"To make your &debian-gnu; system bootable, set up your boot loader to load "
+"the installed kernel with your new root partition. Note that "
+"<command>debootstrap</command> does not install a boot loader, though you "
+"can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:759
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
+msgid ""
+"Check <userinput>info grub</userinput> <phrase arch=\"x86\">or "
+"<userinput>man lilo.conf</userinput></phrase> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing grub2 "
+"<filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</"
+"filename>. For <filename>lilo.conf</filename>, you could also copy it to the "
+"new system and edit it there. After you are done editing, call "
+"<command>lilo</command> (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:771
 #, no-c-format
 msgid ""
-      "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
-      "# aptitude install grub-pc\n"
-      "# grub-install /dev/<replaceable>hda</replaceable>\n"
-      "# update-grub\n"
-      "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>."
+"Installing and setting up <classname>grub2</classname> is as easy as: "
+"<informalexample><screen>\n"
+"# aptitude install grub-pc\n"
+"# grub-install /dev/<replaceable>hda</replaceable>\n"
+"# update-grub\n"
+"</screen></informalexample> The second command will install <command>grub2</"
+"command> (in this case in the MBR of <literal>hda</literal>). The last "
+"command will create a sane and working <filename>/boot/grub/grub.cfg</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:781
 #, no-c-format
-msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
+msgid ""
+"Note that this assumes that a <filename>/dev/hda</filename> device file has "
+"been created. There are alternative methods to install <command>grub2</"
+"command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
@@ -1177,36 +1385,44 @@ msgstr ""
 #: random-bits.xml:791
 #, no-c-format
 msgid ""
-      "boot=/dev/<replaceable>hda6</replaceable>\n"
-      "root=/dev/<replaceable>hda6</replaceable>\n"
-      "install=menu\n"
-      "delay=20\n"
-      "lba32\n"
-      "image=/vmlinuz\n"
-      "initrd=/initrd.img\n"
-      "label=Debian"
+"boot=/dev/<replaceable>hda6</replaceable>\n"
+"root=/dev/<replaceable>hda6</replaceable>\n"
+"install=menu\n"
+"delay=20\n"
+"lba32\n"
+"image=/vmlinuz\n"
+"initrd=/initrd.img\n"
+"label=Debian"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:793
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:803
 #, no-c-format
 msgid ""
-      "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
-      "boot=/dev/hda2\n"
-      "device=hd:\n"
-      "partition=6\n"
-      "root=/dev/hda6\n"
-      "magicboot=/usr/lib/yaboot/ofboot\n"
-      "timeout=50\n"
-      "image=/vmlinux\n"
-      "label=Debian\n"
-      "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
+"boot=/dev/hda2\n"
+"device=hd:\n"
+"partition=6\n"
+"root=/dev/hda6\n"
+"magicboot=/usr/lib/yaboot/ofboot\n"
+"timeout=50\n"
+"image=/vmlinux\n"
+"label=Debian\n"
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1218,15 +1434,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:817
 #, no-c-format
-msgid "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set a password for root:"
+msgid ""
+"In case you can login to the system via console, you can skip this section. "
+"If the system should be accessible via the network later on, you need to "
+"install SSH and set a password for root:"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:823
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+"# aptitude install ssh\n"
+"# passwd"
 msgstr ""
 
 #. Tag: title
@@ -1239,15 +1458,22 @@ msgstr ""
 #: random-bits.xml:829
 #, no-c-format
 msgid ""
-      "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
-      "# tasksel install standard\n"
-      "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually."
+"As mentioned earlier, the installed system will be very basic. If you would "
+"like to make the system a bit more mature, there is an easy method to "
+"install all packages with <quote>standard</quote> priority: "
+"<informalexample><screen>\n"
+"# tasksel install standard\n"
+"</screen></informalexample> Of course, you can also just use "
+"<command>aptitude</command> to install packages individually."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:840
 #, no-c-format
-msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
+msgid ""
+"After the installation there will be a lot of downloaded packages in "
+"<filename>/var/cache/apt/archives/</filename>. You can free up some "
+"diskspace by running:"
 msgstr ""
 
 #. Tag: screen
@@ -1265,25 +1491,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:859
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian-gnu; on a computer without an "
+"Ethernet card, but with just a remote gateway computer attached via a Null-"
+"Modem cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a &debian; mirror on it (e.g. to the "
+"Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:867
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:875
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:880
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1295,7 +1538,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:893
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where &debian; will "
+"be installed."
 msgstr ""
 
 #. Tag: para
@@ -1307,13 +1552,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:904
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:910
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
@@ -1325,28 +1575,33 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:923
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:928
 #, no-c-format
 msgid ""
-      "#!/bin/sh\n"
-      "\n"
-      "# We remove running modules from kernel to avoid conflicts and to\n"
-      "# reconfigure them manually.\n"
-      "modprobe -r lp parport_pc\n"
-      "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
-      "modprobe plip\n"
-      "\n"
-      "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-      "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
-      "\n"
-      "# Configure gateway\n"
-      "modprobe iptable_nat\n"
-      "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
-      "echo 1 > /proc/sys/net/ipv4/ip_forward"
+"#!/bin/sh\n"
+"\n"
+"# We remove running modules from kernel to avoid conflicts and to\n"
+"# reconfigure them manually.\n"
+"modprobe -r lp parport_pc\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
+"modprobe plip\n"
+"\n"
+"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"\n"
+"# Configure gateway\n"
+"modprobe iptable_nat\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
+"echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
 #. Tag: title
@@ -1359,9 +1614,16 @@ msgstr ""
 #: random-bits.xml:935
 #, no-c-format
 msgid ""
-      "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
-      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
-      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to "
+"set parameters for kernel modules, you also need to do this at the boot "
+"prompt. For example, to boot the installer and set values for the <quote>io</"
+"quote> and <quote>irq</quote> options for the parport_pc module, enter the "
+"following at the boot prompt: <informalexample><screen>\n"
+"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc."
+"irq=<replaceable>7</replaceable>\n"
+"</screen></informalexample> Below are the answers that should be given "
+"during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1373,7 +1635,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:956
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1385,13 +1649,20 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:969
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:978
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1409,19 +1680,24 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:998
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1003
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1009
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
@@ -1433,67 +1709,112 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1030
 #, no-c-format
-msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
+msgid ""
+"In some countries PPP over Ethernet (PPPoE) is a common protocol for "
+"broadband (ADSL or cable) connections to an Internet Service Provider. "
+"Setting up a network connection using PPPoE is not supported by default in "
+"the installer, but can be made to work very simply. This section explains "
+"how."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1038
 #, no-c-format
-msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PPPoE connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1043
 #, no-c-format
-msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
+msgid ""
+"To have the option of setting up and using PPPoE during the installation, "
+"you will need to install using one of the CD-ROM/DVD images that are "
+"available. It is not supported for other installation methods (e.g. "
+"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1050
 #, no-c-format
-msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
+msgid ""
+"Installing over PPPoE is mostly the same as any other installation. The "
+"following steps explain the differences."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1058
 #, no-c-format
-msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
+msgid ""
+"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</"
+"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> "
+"for information on how to add a boot parameter. </para> </footnote>. This "
+"will ensure the component responsible for the setup of PPPoE (<classname>ppp-"
+"udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1073
 #, no-c-format
-msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
+msgid ""
+"Follow the regular initial steps of the installation (language, country and "
+"keyboard selection; the loading of additional installer components<footnote> "
+"<para> The <classname>ppp-udeb</classname> component is loaded as one of the "
+"additional components in this step. If you want to install at medium or low "
+"priority (expert mode), you can also manually select the <classname>ppp-"
+"udeb</classname> instead of entering the <quote>modules</quote> parameter at "
+"the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1092
 #, no-c-format
-msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
+msgid ""
+"The next step is the detection of network hardware, in order to identify any "
+"Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1098
 #, no-c-format
-msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
+msgid ""
+"After this the actual setup of PPPoE is started. The installer will probe "
+"all the detected Ethernet interfaces in an attempt to find a PPPoE "
+"concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1104
 #, no-c-format
-msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
+msgid ""
+"It is possible that the concentrator will not to be found at the first "
+"attempt. This can happen occasionally on slow or loaded networks or with "
+"faulty servers. In most cases a second attempt to detect the concentrator "
+"will be successful; to retry, select <guimenuitem>Configure and start a "
+"PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1113
 #, no-c-format
-msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
+msgid ""
+"After a concentrator is found, the user will be prompted to type the login "
+"information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1119
 #, no-c-format
-msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
+msgid ""
+"At this point the installer will use the provided information to establish "
+"the PPPoE connection. If the correct information was provided, the PPPoE "
+"connection should be configured and the installer should be able to use it "
+"to connect to the Internet and retrieve packages over it (if needed). If the "
+"login information is not correct or some error appears, the installer will "
+"stop, but the configuration can be attempted again by selecting the menu "
+"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
@@ -1505,49 +1826,89 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1140
 #, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
+msgid ""
+"The graphical version of the installer is only available for a limited "
+"number of architectures, including &arch-title;. The functionality of the "
+"graphical installer is essentially the same as that of the regular installer "
+"as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1148
 #, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
+msgid ""
+"Although the functionality is identical, the graphical installer still has a "
+"few significant advantages. The main advantage is that it supports more "
+"languages, namely those that use a character set that cannot be displayed "
+"with the regular <quote>newt</quote> frontend. It also has a few usability "
+"advantages such as the option to use a mouse, and in some cases several "
+"questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1157
 #, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
+msgid ""
+"The graphical installer is available with all CD images and with the hd-"
+"media installation method. To boot the graphical installer simply select the "
+"relevant option from the boot menu. Expert and rescue mode for the graphical "
+"installer can be selected from the <quote>Advanced options</quote> menu. The "
+"previously used boot methods <userinput>installgui</userinput>, "
+"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
+"still be used from the boot prompt which is shown after selecting the "
+"<quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1168
 #, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
+msgid ""
+"There is also a graphical installer image that can be netbooted. And there "
+"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> "
+"<para> The mini ISO image can be downloaded from a &debian; mirror as "
+"described in <xref linkend=\"downloading-files\"/>. Look for "
+"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
+"mainly useful for testing."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1181
 #, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
+msgid ""
+"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
+"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image "
+"can be downloaded from a &debian; mirror as described in <xref linkend="
+"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
+"</para> </footnote>. It should work on almost all PowerPC systems that have "
+"an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1195
 #, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
+msgid ""
+"Just as with the regular installer it is possible to add boot parameters "
+"when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1201
 #, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
+msgid ""
+"The graphical installer requires significantly more memory to run than the "
+"regular installer: &minimum-memory-gtk;. If insufficient memory is "
+"available, it will automatically fall back to the regular <quote>newt</"
+"quote> frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1208
 #, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
+msgid ""
+"If the amount of memory in your system is below &minimum-memory;, the "
+"graphical installer may fail to boot at all while booting the regular "
+"installer would still work. Using the regular installer is recommended for "
+"systems with little available memory."
 msgstr ""
 
 #. Tag: title
@@ -1559,24 +1920,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1219
 #, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
+msgid ""
+"As already mentioned, the graphical installer basically works the same as "
+"the regular installer and thus the rest of this manual can be used to guide "
+"you through the installation process."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1225
 #, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgid ""
+"If you prefer using the keyboard over the mouse, there are two things you "
+"need to know. To expand a collapsed list (used for example for the selection "
+"of countries within continents), you can use the <keycap>+</keycap> and "
+"<keycap>-</keycap> keys. For questions where more than one item can be "
+"selected (e.g. task selection), you first need to tab to the &BTN-CONT; "
+"button after making your selections; hitting enter will toggle a selection, "
+"not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1235
 #, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgid ""
+"If a dialog offers additional help information, a <guibutton>Help</"
+"guibutton> button will be displayed. The help information can be accessed "
+"either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1241
 #, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgid ""
+"To switch to another console, you will also need to use the <keycap>Ctrl</"
+"keycap> key, just as with the X Window System. For example, to switch to VT2 "
+"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> "
+"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical "
+"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</"
+"keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""
-
diff --git a/po/ru/boot-installer.po b/po/ru/boot-installer.po
index 1a0dcf645..9694baa84 100644
--- a/po/ru/boot-installer.po
+++ b/po/ru/boot-installer.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-10-27 09:54+0400\n"
 "Last-Translator: Yuri Kozlov <yuray@komyakino.ru>\n"
 "Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
@@ -68,8 +68,8 @@ msgstr "Загрузка по TFTP"
 
 # index.docbook:427, index.docbook:872, index.docbook:1420, index.docbook:1892, index.docbook:2246, index.docbook:2354
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -80,8 +80,8 @@ msgstr ""
 
 # index.docbook:432, index.docbook:877, index.docbook:1425, index.docbook:1897, index.docbook:2251, index.docbook:2359
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -92,8 +92,8 @@ msgstr ""
 
 # index.docbook:437, index.docbook:882, index.docbook:1430, index.docbook:1902, index.docbook:2256, index.docbook:2364
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -110,8 +110,8 @@ msgstr "Загрузка с CD-ROM"
 
 # index.docbook:526, index.docbook:578, index.docbook:1043, index.docbook:1849, index.docbook:2090, index.docbook:2394
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -129,8 +129,8 @@ msgstr ""
 
 # index.docbook:537, index.docbook:589, index.docbook:1054, index.docbook:1860, index.docbook:2101, index.docbook:2405
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -147,8 +147,8 @@ msgstr ""
 
 # index.docbook:545, index.docbook:597, index.docbook:1062, index.docbook:1868, index.docbook:2109, index.docbook:2413
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -165,8 +165,8 @@ msgstr ""
 
 # index.docbook:553, index.docbook:605, index.docbook:1070, index.docbook:1876, index.docbook:2117, index.docbook:2421
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -413,8 +413,8 @@ msgstr "Программа установки будет запущена как
 
 # index.docbook:572, index.docbook:1037, index.docbook:1837, index.docbook:2084, index.docbook:2388
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Загрузка с CD-ROM"
@@ -435,17 +435,23 @@ msgstr "Чтобы запустить программу установки из
 # index.docbook:1670, index.docbook:2168
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "получить установочный носитель CD-ROM/DVD-ROM или карту памяти USB, как "
 "описано в<xref linkend=\"official-cdrom\"/> и <xref linkend=\"boot-usb-files"
 "\"/>, или "
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -455,7 +461,7 @@ msgstr ""
 "loader/stable/win32-loader.exe,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -470,7 +476,7 @@ msgstr ""
 "<command>setup.exe</command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -481,13 +487,13 @@ msgstr ""
 "и система будет подготовлена для запуска программы установки &debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Загрузка из DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -497,7 +503,7 @@ msgstr ""
 "восстановления или диагностики."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -515,7 +521,7 @@ msgstr ""
 "текущий диск на его, если потребуется."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -538,7 +544,7 @@ msgstr ""
 "Будет загружено ядро и запущена система установки."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -548,7 +554,7 @@ msgstr ""
 
 # index.docbook:1670, index.docbook:2168
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -559,7 +565,7 @@ msgstr ""
 "<xref linkend=\"boot-drive-files\"/>)."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -577,7 +583,7 @@ msgstr ""
 "должны делать это осторожно."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -595,7 +601,7 @@ msgstr ""
 "DVD без использования сети."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -613,7 +619,7 @@ msgstr ""
 "<filename>/etc/lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -625,7 +631,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -641,7 +647,7 @@ msgstr ""
 "<userinput>lilo</userinput> и перезагрузите машину."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -657,7 +663,7 @@ msgstr ""
 "filename> находится на первом разделе первого жёсткого диска системы):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -671,7 +677,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -683,7 +689,7 @@ msgstr ""
 "filename>. Запись для программы установки может выглядеть так:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -703,7 +709,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -713,13 +719,13 @@ msgstr ""
 "<command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Загрузка с карты памяти USB"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
 "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -738,14 +744,14 @@ msgstr ""
 
 # index.docbook:807, index.docbook:1949, index.docbook:2282, index.docbook:2442
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Загрузка с дискет"
 
 # index.docbook:808, index.docbook:2290
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -755,7 +761,7 @@ msgstr ""
 "загрузочные дискеты как описано в <xref linkend=\"create-floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -765,7 +771,7 @@ msgstr ""
 "дисковод, выключите систему как обычно и включите питание."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -783,7 +789,7 @@ msgstr ""
 "<userinput>install root=/dev/hdc</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -800,7 +806,7 @@ msgstr ""
 "нет выбора. Иначе, выполните аппаратную перезагрузку перед загрузкой."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -811,7 +817,7 @@ msgstr ""
 "<prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -828,7 +834,7 @@ msgstr ""
 "этапе процесса загрузки можно найти в <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -843,26 +849,26 @@ msgstr ""
 
 # index.docbook:254, index.docbook:866, index.docbook:1402, index.docbook:1886, index.docbook:1969, index.docbook:2240, index.docbook:2348
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Загрузка по TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Есть несколько возможностей выполнить загрузку по TFTP на i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "Сетевая карта или материнская плата с поддержкой PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -876,13 +882,13 @@ msgstr ""
 "можете настроить BIOS на загрузку по сети."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "Сетевая карта с сетевым BootROM"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -891,7 +897,7 @@ msgstr ""
 "Возможно, что сетевая карта (NIC) предоставляет возможность загрузки по TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -901,13 +907,13 @@ msgstr ""
 "сделать это. Пожалуйста, упомяните в заголовке этот документ."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -918,13 +924,13 @@ msgstr ""
 
 # index.docbook:2012, index.docbook:2491
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Экран запуска"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -960,7 +966,7 @@ msgstr ""
 "установки, что почти удваивает количество пунктов."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -975,7 +981,7 @@ msgstr ""
 "запуска программы установки достаточно нажать &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -987,7 +993,7 @@ msgstr ""
 "для автоматизации установки."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1006,7 +1012,7 @@ msgstr ""
 "вами изменения, нажмите &escapekey;."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
 "Choosing the <quote>Help</quote> entry will result in the first help screen "
@@ -1040,7 +1046,7 @@ msgstr ""
 "fb=false</userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1058,7 +1064,7 @@ msgstr ""
 "использовать для поиска нужных клавиш."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1079,7 +1085,7 @@ msgstr ""
 "<quote>Integrated Remote Assistant</quote> (IRA)."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1099,13 +1105,13 @@ msgstr ""
 "<userinput>vga=normal fb=false</userinput>, который описан в справке."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Содержимое компакт-диска"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1130,7 +1136,7 @@ msgstr ""
 "всякого доступа к сети."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1156,7 +1162,7 @@ msgstr ""
 "вместо простой MBR или загрузочного сектора на обычных системах."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1173,7 +1179,7 @@ msgstr ""
 "командной оболочки EFI Shell, как описано ниже."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1196,7 +1202,7 @@ msgstr ""
 "разрешить установке продолжиться."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1219,13 +1225,13 @@ msgstr ""
 "используйте второй."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "ВАЖНО"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1244,13 +1250,13 @@ msgstr ""
 "загрузчик выполнив <command>exit</command> из командной строки."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Вариант 1: Загрузка из Boot Option Maintenance Menu"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1262,7 +1268,7 @@ msgstr ""
 "меню."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1273,7 +1279,7 @@ msgstr ""
 "следующее меню."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1292,7 +1298,7 @@ msgstr ""
 "будет одинаковой."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1311,7 +1317,7 @@ msgstr ""
 "шаг."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1327,7 +1333,7 @@ msgstr ""
 "загрузки."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1339,13 +1345,13 @@ msgstr ""
 "ядро и параметры."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Вариант 2: Загрузка из EFI Shell"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1359,7 +1365,7 @@ msgstr ""
 "установки &debian; с помощью следующих шагов:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1371,7 +1377,7 @@ msgstr ""
 "меню."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1394,7 +1400,7 @@ msgstr ""
 "дополнительных секунд для инициализации привода компакт-дисков."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1408,7 +1414,7 @@ msgstr ""
 "<filename>fs<replaceable>n</replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1422,7 +1428,7 @@ msgstr ""
 "своём приглашении."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1432,7 +1438,7 @@ msgstr ""
 "запустит процедуру начальной загрузки."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1448,13 +1454,13 @@ msgstr ""
 "параметры."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Установка с консоли на последовательном порту"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1475,7 +1481,7 @@ msgstr ""
 "меню."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1489,7 +1495,7 @@ msgstr ""
 "shell."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1505,7 +1511,7 @@ msgstr ""
 "command> в текстовом окне с приглашением <classname>Boot:</classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1523,7 +1529,7 @@ msgstr ""
 "инструкции по запуску программы установки в текстовом режиме."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1536,13 +1542,13 @@ msgstr ""
 "невозможно работать и потребуется перезапуск перед началом установки."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Выбор загружаемого ядра и параметров"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1562,7 +1568,7 @@ msgstr ""
 "об общих параметрах командной строки."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1585,7 +1591,7 @@ msgstr ""
 "системе. В следующих двух шагах выбирается и запускается установка:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1595,7 +1601,7 @@ msgstr ""
 "ядра и режим установки."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1607,7 +1613,7 @@ msgstr ""
 "на последовательном порту)."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1619,7 +1625,7 @@ msgstr ""
 "установки &debian;."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1629,7 +1635,7 @@ msgstr ""
 "настроите язык, сеть и дисковые разделы."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1647,7 +1653,7 @@ msgstr ""
 "того, что пакеты базовой установки будут получены по сети, а не с привода CD."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1661,13 +1667,13 @@ msgstr ""
 "параметр загрузки в менеджере загрузки EFI, включающий загрузку по сети."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Настройка сервера"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1691,7 +1697,7 @@ msgstr ""
 "<command>elilo.efi</command> на клиенте."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1707,7 +1713,7 @@ msgstr ""
 "файлы для системы IA-64."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1725,7 +1731,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1746,13 +1752,13 @@ msgstr ""
 "Подробней смотрите документацию в пакете <classname>elilo</classname>."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Настройка клиента"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1782,7 +1788,7 @@ msgstr ""
 "<filename>elilo.efi</filename> с сервера."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1798,13 +1804,13 @@ msgstr ""
 
 # index.docbook:1972, index.docbook:2015
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Загрузка SGI с сервера TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1827,13 +1833,13 @@ msgstr ""
 
 # index.docbook:2012, index.docbook:2491
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Параметры загрузки"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1843,7 +1849,7 @@ msgstr ""
 "<command>bootp():</command> в мониторе команд."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1861,20 +1867,20 @@ msgstr ""
 "через <command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 # index.docbook:1972, index.docbook:2015
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Загрузка Cobalt с сервера TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1892,7 +1898,7 @@ msgstr ""
 "два метода установки:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1907,7 +1913,7 @@ msgstr ""
 "подключения к машине с помощью SSH клиента, вы можете начать установку."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1919,7 +1925,7 @@ msgstr ""
 "выполнить установку."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1931,13 +1937,13 @@ msgstr ""
 "сервере и добавить параметры в переменную <replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Ограничения s390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1947,7 +1953,7 @@ msgstr ""
 "и ssh-сессия."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1961,13 +1967,13 @@ msgstr ""
 
 # index.docbook:2012, index.docbook:2491
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Параметры загрузки s390"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1979,7 +1985,7 @@ msgstr ""
 "parm файла &mdash; <filename>parmfile.debian</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1997,7 +2003,7 @@ msgstr ""
 "с CD/DVD."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2015,13 +2021,13 @@ msgstr ""
 "с внешнего привода CD/DVD по умолчанию введите"
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2038,7 +2044,7 @@ msgstr ""
 "диск с нужными файлами."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2050,20 +2056,20 @@ msgstr ""
 "появится приглашение SmartFirmware, введите"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Загрузка с жёсткого диска"
 
 # index.docbook:1664, index.docbook:2162
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2074,7 +2080,7 @@ msgstr ""
 
 # index.docbook:1670, index.docbook:2168
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2086,13 +2092,13 @@ msgstr ""
 "linkend=\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Загрузка OldWorld PowerMac из MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2115,13 +2121,13 @@ msgstr ""
 "установки."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Загрузка NewWorld Mac из OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2164,20 +2170,20 @@ msgstr ""
 "сработает. После должна запуститься программа установки &debian;."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Загрузка с карты памяти USB"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 "В настоящий момент системы NewWorld PowerMac можно загружать с USB устройств."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2192,7 +2198,7 @@ msgstr ""
 "\"invoking-openfirmware\"/>)."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2215,7 +2221,7 @@ msgstr ""
 "pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2240,7 +2246,7 @@ msgstr ""
 "из каталога ранее установленного с помощью <command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2252,7 +2258,7 @@ msgstr ""
 "просто нажать &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2264,7 +2270,7 @@ msgstr ""
 "отчёт об установке, как описано в <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2272,7 +2278,7 @@ msgstr ""
 "загрузка по сети."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2308,7 +2314,7 @@ msgstr ""
 "получить описание синтаксиса и допустимые параметры."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2321,7 +2327,7 @@ msgstr ""
 "а с подключённых по USB приводов гибких дисков загрузка не поддерживается."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2332,7 +2338,7 @@ msgstr ""
 "вставьте её в дисковод после выключения системы и перед включением питания."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2346,7 +2352,7 @@ msgstr ""
 "проверит на загружаемость разделы жёсткого диска."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2359,13 +2365,13 @@ msgstr ""
 
 # index.docbook:2012, index.docbook:2491
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "Параметры загрузки PowerPC"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2381,7 +2387,7 @@ msgstr ""
 "нужно использовать параметр <userinput>video=aty128fb:vmode:6</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2401,7 +2407,7 @@ msgstr ""
 "записав их в конец команды <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2413,13 +2419,13 @@ msgstr ""
 "с ID 6 (или вторичного мастера для систем с IDE)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "Сообщения IDPROM"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2434,13 +2440,13 @@ msgstr ""
 "<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Лёгкость управления"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2470,13 +2476,13 @@ msgstr ""
 "клавиатура с раскладкой QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB-дисплеи Брайля"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2498,13 +2504,13 @@ msgstr ""
 "classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Дисплеи Брайля, подключаемые к последовательному порту"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2545,13 +2551,13 @@ msgstr ""
 "classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "ПО речевого синтеза"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2566,13 +2572,13 @@ msgstr ""
 "на выбранном языке (если он доступен в <classname>espeak</classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Устройства речевого синтеза"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2584,7 +2590,7 @@ msgstr ""
 "нужно выбрать <quote>Graphical install</quote>."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2607,13 +2613,13 @@ msgstr ""
 "речевого синтеза."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Встраиваемые устройства"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2630,7 +2636,7 @@ msgstr ""
 "языков установки."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2641,13 +2647,13 @@ msgstr ""
 "&enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Тема с высокой контрастностью"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2660,13 +2666,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Список ответов"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2676,7 +2682,7 @@ msgstr ""
 "списка ответов. Это описано в <xref linkend=\"appendix-preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2690,7 +2696,7 @@ msgstr ""
 "автоматически. Однако, иногда вы должны немного помочь ядру."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2705,7 +2711,7 @@ msgstr ""
 "определить аппаратуру вашего компьютера."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2722,7 +2728,7 @@ msgstr ""
 "troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
 msgid ""
 "If you are booting with a serial console, generally the kernel will "
@@ -2742,7 +2748,7 @@ msgstr ""
 "последовательного порта, обычно <filename>ttyS0</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
 msgid ""
 "In order to ensure the terminal type used by the installer matches your "
@@ -2771,7 +2777,7 @@ msgstr ""
 "<literal>vt102</literal>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2785,13 +2791,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Параметры программы установки &debian;"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2805,7 +2811,7 @@ msgstr ""
 "</footnote>, что может быть полезно."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2821,19 +2827,19 @@ msgstr ""
 "используется сокращённая форма."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "Этот параметр задаёт низший приоритет отображаемых сообщений."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2848,7 +2854,7 @@ msgstr ""
 "приоритета."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2868,13 +2874,13 @@ msgstr ""
 "всё сделать правильно самостоятельно."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2911,13 +2917,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2932,49 +2938,49 @@ msgstr ""
 "продолжению процесса загрузки.)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Значение по умолчанию."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Подробней чем обычно."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Много отладочной информации."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2985,13 +2991,13 @@ msgstr ""
 "загрузка продолжится."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3003,7 +3009,7 @@ msgstr ""
 "floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3014,19 +3020,19 @@ msgstr ""
 "дискету только на избранном устройстве."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3039,13 +3045,13 @@ msgstr ""
 "syslog."
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3057,13 +3063,13 @@ msgstr ""
 "памяти. Возможные значения 1 и 2. Смотрите также <xref linkend=\"lowmem\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3074,13 +3080,13 @@ msgstr ""
 "безопасность."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3098,13 +3104,13 @@ msgstr ""
 "замирание на несколько минут в начале установки."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Подобные проблемы замечены на hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3123,13 +3129,13 @@ msgstr ""
 "для краткости <userinput>fb=true</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3146,13 +3152,13 @@ msgstr ""
 "replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3166,7 +3172,7 @@ msgstr ""
 "случае ошибок при работе с DHCP."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3180,13 +3186,13 @@ msgstr ""
 "отключить настройку сети по DHCP и ввести информацию вручную."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3196,13 +3202,13 @@ msgstr ""
 "PCMCIA, если это вызывает проблемы. Особенно полезно для некоторых ноутбуков."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3217,13 +3223,13 @@ msgstr ""
 "wiki;\">вики &debian; Installer</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3233,13 +3239,13 @@ msgstr ""
 "установки. Смотрите <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3249,13 +3255,13 @@ msgstr ""
 "Смотрите <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3272,13 +3278,13 @@ msgstr ""
 "\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3290,13 +3296,13 @@ msgstr ""
 "установки смотрите в <xref linkend=\"preseed-auto\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3308,13 +3314,13 @@ msgstr ""
 "установить в значение <userinput>true</userinput>, то этого не случится."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3333,7 +3339,7 @@ msgstr ""
 "способны загружать носитель автоматически."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3345,13 +3351,13 @@ msgstr ""
 "диска после начальной установки."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3364,7 +3370,7 @@ msgstr ""
 "quote> пакетов, как во время установки так и в установленной системе."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3380,13 +3386,13 @@ msgstr ""
 "должен использоваться только очень опытными пользователями."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3401,13 +3407,13 @@ msgstr ""
 "emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3419,13 +3425,13 @@ msgstr ""
 "загружен полностью. Значение задаётся в килобайтах."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3435,13 +3441,13 @@ msgstr ""
 "вместо обычного режима установки. Смотрите <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Использование параметров загрузки для ответов на вопросы"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3455,25 +3461,25 @@ msgstr ""
 "\"preseed-bootparms\"/>. Некоторые специальные примеры даны ниже."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3483,7 +3489,7 @@ msgstr ""
 "в установленной системе."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3503,7 +3509,7 @@ msgstr ""
 "локали."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3519,13 +3525,13 @@ msgstr ""
 "locale=en_GB.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3542,7 +3548,7 @@ msgstr ""
 "udeb</classname> (на настройки PPPoE)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3552,13 +3558,13 @@ msgstr ""
 "задать настройки сети статически."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3576,13 +3582,13 @@ msgstr ""
 "зеркало ftp из списка, вам придётся вводить имя вручную."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3594,13 +3600,13 @@ msgstr ""
 "Подробней смотрите в <xref linkend=\"pkgsel\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Передача параметров модулям ядра"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3624,7 +3630,7 @@ msgstr ""
 "системы."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3638,7 +3644,7 @@ msgstr ""
 "установка параметров вручную."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3659,19 +3665,19 @@ msgstr ""
 "вы должны написать:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Внесение модулей ядра в чёрный список"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3689,7 +3695,7 @@ msgstr ""
 "сперва загружается неправильный драйвер."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3704,7 +3710,7 @@ msgstr ""
 "blacklist.local</filename> на время установки и в установленной системе."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3718,19 +3724,19 @@ msgstr ""
 "оборудования."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Диагностика проблем процесса установки"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Надёжность CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3744,7 +3750,7 @@ msgstr ""
 "время установки."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3755,7 +3761,7 @@ msgstr ""
 "общие из них и предложить общие решения. Остальное зависит от вас."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
@@ -3763,7 +3769,7 @@ msgstr ""
 "очередь."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3773,7 +3779,7 @@ msgstr ""
 "правильно и что диск не грязный."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid ""
 "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3787,7 +3793,7 @@ msgstr ""
 "проблемы с DMA на очень старых приводах CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3799,7 +3805,7 @@ msgstr ""
 "простоты мы будем использовать термин CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3809,13 +3815,13 @@ msgstr ""
 "попробуйте, если возможно, другой метод установки."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Общие причины"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3825,7 +3831,7 @@ msgstr ""
 "были записаны на высоких скоростях в современных устройствах записи CD."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid ""
 "Some very old CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3835,20 +3841,20 @@ msgstr ""
 "<quote>прямой доступ к памяти</quote> (DMA)."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Как изучать и может быть решить проблему"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 "Если с CD-ROM не удаётся загрузиться, попробуйте способы указанные ниже."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid ""
 "Check that your BIOS actually supports booting from CD-ROM (only an issue "
@@ -3859,7 +3865,7 @@ msgstr ""
 "носителя."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3884,7 +3890,7 @@ msgstr ""
 "прочитанных с CD-ROM байт, составляющих образ."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3906,7 +3912,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3928,7 +3934,7 @@ msgstr ""
 "командной строки."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3941,7 +3947,7 @@ msgstr ""
 "<command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3972,7 +3978,7 @@ msgstr ""
 "<command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3985,7 +3991,7 @@ msgstr ""
 "cdrom0</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4002,7 +4008,7 @@ msgstr ""
 "команды."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4027,7 +4033,7 @@ msgstr ""
 "устройства, соответствующего приводу CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4040,13 +4046,13 @@ msgstr ""
 "можно провести общую проверку надёжности чтения CD-ROM."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Надёжность дискет"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4056,7 +4062,7 @@ msgstr ""
 "устанавливающих &debian;."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4074,7 +4080,7 @@ msgstr ""
 "сообщений об ошибках ввода-вывода (disk I/O error)."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4091,7 +4097,7 @@ msgstr ""
 "записать дискету на другой системе."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4102,7 +4108,7 @@ msgstr ""
 "emphasis> раза, прежде чем она заработала, и затем всё пошло нормально."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4114,7 +4120,7 @@ msgstr ""
 "их md5sum."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4126,13 +4132,13 @@ msgstr ""
 "случается из-за плохо работающих дисководов и их микропрограмм."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Настройка загрузки"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4145,7 +4151,7 @@ msgstr ""
 "параметры загрузки, как это обсуждается в <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4157,7 +4163,7 @@ msgstr ""
 "<xref linkend=\"loading-firmware\"/>)."
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4176,37 +4182,37 @@ msgstr ""
 "загрузившись с live-CD)."
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Распространённые проблемы установки на &arch-title;"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4217,7 +4223,7 @@ msgstr ""
 "установки."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4237,13 +4243,13 @@ msgstr ""
 "Подробней см. <xref linkend=\"boot-parms\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Система подвисает во время настройки PCMCIA"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
 msgid ""
 "Some very old laptop models produced by Dell are known to crash when PCMCIA "
@@ -4264,7 +4270,7 @@ msgstr ""
 "возникают проблемы."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4287,7 +4293,7 @@ msgstr ""
 "они есть."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
@@ -4295,13 +4301,13 @@ msgstr ""
 "рассказать."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Вывод видео не на то устройство"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4327,7 +4333,7 @@ msgstr ""
 "программу установки с параметром <userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4341,13 +4347,13 @@ msgstr ""
 "<filename>/etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Не удаётся загрузиться или установить ядро с CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4359,19 +4365,19 @@ msgstr ""
 "Большинство сообщений о таких проблемах относилось к системам SunBlade."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr "Для таких систем мы рекомендуем загружать программу установки по сети."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Интерпретация загрузочных сообщений ядра"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4409,13 +4415,13 @@ msgstr ""
 "baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Сообщение о проблемах при установке"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4435,7 +4441,7 @@ msgstr ""
 "приложить эту информацию к отчёту."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4447,13 +4453,13 @@ msgstr ""
 "filename> после того, как компьютер загрузит установленную систему."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Отправка отчётов об ошибках установки"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4466,7 +4472,7 @@ msgstr ""
 "получить побольше информации о разных аппаратных конфигурациях."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4478,7 +4484,7 @@ msgstr ""
 "используете адрес электронной почты, который не жалко опубликовывать."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4497,7 +4503,7 @@ msgstr ""
 "запустить команду <command>reportbug installation-reports</command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/ru/install-methods.po b/po/ru/install-methods.po
index 123a76687..e7faa7850 100644
--- a/po/ru/install-methods.po
+++ b/po/ru/install-methods.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-10-27 09:59+0400\n"
 "Last-Translator: Yuri Kozlov <yuray@komyakino.ru>\n"
 "Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
@@ -66,14 +66,20 @@ msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "As CDs have a rather limited capacity by today's standards, not all "
+#| "graphical desktop environments are installable with only the first CD; "
+#| "only XFCE (which is the default desktop environment installed by &debian-"
+#| "gnu; &release;) completely fits on the first CD. For all other desktop "
+#| "environments a CD installation requires either network connectivity "
+#| "during the installation to download the remaining files or additional CDs."
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 "При сегодняшних объёмах, на CD-диск можно не так много уместить, например, "
 "не каждое окружение рабочего стола можно установить имея только первый CD; "
@@ -83,7 +89,7 @@ msgstr ""
 "подключение к сети, или дополнительные диски."
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
 msgid ""
 "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
@@ -113,7 +119,7 @@ msgstr ""
 "подкаталогах на ваших CD."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -123,7 +129,7 @@ msgstr ""
 "файлы с компакт-дисков."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -142,13 +148,13 @@ msgstr ""
 "использовать их для загрузки программы установки."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Скачивание файлов с серверов-зеркал &debian;"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -159,7 +165,7 @@ msgstr ""
 "ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -170,13 +176,13 @@ msgstr ""
 "автоматическом режиме."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Где искать установочные образы"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -192,13 +198,13 @@ msgstr ""
 "предназначен каждый образ."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Файлы установки для Thecus N2100"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -212,13 +218,13 @@ msgstr ""
 "микропрограммы можно получить из &n2100-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Файлы установки для GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -230,13 +236,13 @@ msgstr ""
 "получить из &glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Файлы установки для Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -248,13 +254,13 @@ msgstr ""
 "получить из &kuroboxpro-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Файлы установки для HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -270,13 +276,13 @@ msgstr ""
 "можно получить из &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Файлы установки для QNAP Turbo Station"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -290,13 +296,13 @@ msgstr ""
 "TS-41x из &qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Файлы установки для Plug Computer и OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
 msgid ""
 "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
@@ -308,13 +314,13 @@ msgstr ""
 "можете получить эти файлы из &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr "Файлы установки для серверов сетевого доступа LaCie"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
 msgid ""
 "The installation files for LaCie NASes (Network Space v2, Network Space Max "
@@ -328,13 +334,13 @@ msgstr ""
 "получить эти файлы из &lacie-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Создание ленты IPL"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -356,13 +362,13 @@ msgstr ""
 "<xref linkend=\"where-files\"/>."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Создание дискет из образов дисков"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -373,7 +379,7 @@ msgstr ""
 "загружаться с CD или каким-то другим способом."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -382,7 +388,7 @@ msgstr ""
 "Загрузка программы установки с дискет не работает в дисководах Mac USB."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -403,7 +409,7 @@ msgstr ""
 "копирования</emphasis> данных из файла на дискету."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -415,7 +421,7 @@ msgstr ""
 "различных платформах."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -430,7 +436,7 @@ msgstr ""
 "образы дискет могут быть уже на этих CD/DVD.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -442,13 +448,13 @@ msgstr ""
 "непреднамеренно не повредить их."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Запись образов дисков из систем Linux или Unix"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -484,7 +490,7 @@ msgstr ""
 "смотрите страницу руководства)</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -519,7 +525,7 @@ msgstr ""
 "спросите вашего системного администратора. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -531,13 +537,13 @@ msgstr ""
 "потребоваться её установка."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Запись образов дисков из DOS, Windows или OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -547,7 +553,7 @@ msgstr ""
 "на дискеты вы можете воспользоваться одной из программ, упомянутых ниже."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -563,7 +569,7 @@ msgstr ""
 "emphasis> сработает."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -575,7 +581,7 @@ msgstr ""
 "распаковать diskio.dll в тот же самый каталог."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -585,13 +591,13 @@ msgstr ""
 "<filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Запись образов дисков из MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -612,7 +618,7 @@ msgstr ""
 "стереть дискету и записать на неё образ файла."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -626,13 +632,13 @@ msgstr ""
 "следующих методов для создания дискеты из образа."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Запись образов дисков с помощью <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -646,7 +652,7 @@ msgstr ""
 "файлы образов с сервера-зеркала &debian;."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -656,7 +662,7 @@ msgstr ""
 "ulink> и используйте его для открытия файла <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -668,7 +674,7 @@ msgstr ""
 "данных важен."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -684,7 +690,7 @@ msgstr ""
 "смонтирован."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -696,7 +702,7 @@ msgstr ""
 "diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -713,13 +719,13 @@ msgstr ""
 "вылезет из дисковода."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Запись образов дисков с помощью <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -732,14 +738,14 @@ msgstr ""
 "<quote>Overwrite Sectors...</quote> из меню <userinput>Special</userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr "Вставьте дискету, нажмите &enterkey; (начало с сектора 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
@@ -747,7 +753,7 @@ msgstr ""
 "Выберите файл <filename>root.bin</filename> в появившемся диалоговом окне."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -760,7 +766,7 @@ msgstr ""
 "ошибки при записи дискеты, просто выньте эту и вставьте другую дискету."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -772,13 +778,13 @@ msgstr ""
 "просто испортит её."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Подготовка файлов для загрузки с карты памяти USB"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -801,7 +807,7 @@ msgstr ""
 "Также выключите защиту от записи на карту."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -815,13 +821,13 @@ msgstr ""
 "например, на жёстком диске."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "Подготовка карты памяти USB из гибридного образа CD или DVD"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -835,7 +841,7 @@ msgstr ""
 "получить образ CD или DVD, читайте <xref linkend=\"official-cdrom\"/>."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -849,7 +855,7 @@ msgstr ""
 "files\"/>)."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -867,7 +873,7 @@ msgstr ""
 "нужно смонтировать второй и распаковать микропрограмму на него."
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -883,7 +889,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -897,7 +903,7 @@ msgstr ""
 "(предварительно отмонтировав):"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -909,7 +915,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -921,13 +927,13 @@ msgstr ""
 "предназначены для людей, у которых есть дополнительные требования."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "Копирование файлов на карту памяти USB вручную"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -941,7 +947,7 @@ msgstr ""
 "<xref linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -957,7 +963,7 @@ msgstr ""
 "classname> и его файл настройки</phrase>."
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -973,20 +979,20 @@ msgstr ""
 "другой цели."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 "Чтобы использовать образ, просто распакуйте его прямо на карту памяти USB:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -998,13 +1004,13 @@ msgstr ""
 "образ на этот раздел:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
 msgid ""
 "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1026,13 +1032,13 @@ msgstr ""
 "всё готово."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Копирование файлов на карту памяти USB вручную &mdash; гибкий путь"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1048,13 +1054,13 @@ msgstr ""
 "образ CD ISO."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Разметка карты памяти USB"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1064,7 +1070,7 @@ msgstr ""
 "устройство."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
 "Since most USB sticks come pre-configured with a single FAT16 partition, you "
@@ -1099,7 +1105,7 @@ msgstr ""
 "&debian; <classname>dosfstools</classname>."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1118,7 +1124,7 @@ msgstr ""
 "поддерживает файловую систему FAT."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1141,13 +1147,13 @@ msgstr ""
 "<filename>ldlinux.sys</filename>, который содержит код системного загрузчика."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Добавление образа программы установки"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1173,7 +1179,7 @@ msgstr ""
 "именами DOS (8.3)."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
 "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1198,7 +1204,7 @@ msgstr ""
 "добавлять и другие параметры."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1208,7 +1214,7 @@ msgstr ""
 "параметров, добавьте строку <userinput>prompt 1</userinput>."
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
 msgid ""
 "If you used an <filename>hd-media</filename> image, you should now copy the "
@@ -1228,7 +1234,7 @@ msgstr ""
 "карту памяти USB (<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1257,7 +1263,7 @@ msgstr ""
 "<classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1274,7 +1280,7 @@ msgstr ""
 "поддерживает файловую систему HFS."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1310,7 +1316,7 @@ msgstr ""
 "Unix."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1321,31 +1327,31 @@ msgstr ""
 "карту:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (файл ядра)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (образ ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (файл настройки yaboot)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (необязательное загрузочное сообщение)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1380,13 +1386,13 @@ msgstr ""
 "образа."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Подготовка файлов для загрузки с жёсткого диска"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1398,7 +1404,7 @@ msgstr ""
 "системы или вызовом системного загрузчика прямо из BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1411,7 +1417,7 @@ msgstr ""
 "например, поиск и прожиг CD образов или борьбы с кучей нечитаемых дискет."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1433,7 +1439,7 @@ msgstr ""
 "Linux, в особенности, для загрузки файлов установки."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1445,7 +1451,7 @@ msgstr ""
 "<quote>OldWorld</quote>."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1455,7 +1461,7 @@ msgstr ""
 "command> или <command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1465,7 +1471,7 @@ msgstr ""
 "linux с помощью <command>LILO</command> или <command>GRUB</command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1477,7 +1483,7 @@ msgstr ""
 "качестве корневой файловой системы."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1489,19 +1495,19 @@ msgstr ""
 "NTFS), например, в <filename>/boot/newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (файл ядра)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (образ ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1511,7 +1517,7 @@ msgstr ""
 ">."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
@@ -1519,7 +1525,7 @@ msgstr ""
 "command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1529,7 +1535,7 @@ msgstr ""
 "установки из DOS с помощью <command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1539,26 +1545,26 @@ msgstr ""
 "filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr "<filename>/&x86-install-dir;</filename> (файл ядра и образ ramdisk)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (утилита loadlin)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Загрузка программы установки с жёсткого диска для OldWorld Mac"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1582,7 +1588,7 @@ msgstr ""
 "модели нужно использовать <application>BootX</application>."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1610,13 +1616,13 @@ msgstr ""
 "активный System Folder."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Загрузка программы установки с жёсткого диска для NewWorld Mac"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1637,7 +1643,7 @@ msgstr ""
 "использоваться на NewWorld PowerMac."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1651,31 +1657,31 @@ msgstr ""
 "перетаскивания каждого файла на значок жёсткого диска)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1691,7 +1697,7 @@ msgstr ""
 "установки."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1699,13 +1705,13 @@ msgstr ""
 "newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Подготовка файлов для загрузки по TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1720,7 +1726,7 @@ msgstr ""
 "поддержку загрузки вашей машины."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1732,7 +1738,7 @@ msgstr ""
 "\"supports-dhcp\"> или BOOTP сервер</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1753,7 +1759,7 @@ msgstr ""
 "через DHCP."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1765,7 +1771,7 @@ msgstr ""
 "загрузить с помощью BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1775,7 +1781,7 @@ msgstr ""
 "BOOTP. Пакет <classname>rbootd</classname> доступен в &debian;."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1790,7 +1796,7 @@ msgstr ""
 "Solaris) и GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1804,13 +1810,13 @@ msgstr ""
 "classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Настройка RARP сервера"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1830,7 +1836,7 @@ msgstr ""
 "ip addr show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1854,13 +1860,13 @@ msgstr ""
 "или <userinput>/usr/etc/rarpd -a</userinput> в SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Настройка DHCP сервера"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1874,7 +1880,7 @@ msgstr ""
 "filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1918,7 +1924,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1935,7 +1941,7 @@ msgstr ""
 "содержать имя файла, который нужно получить по TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1946,13 +1952,13 @@ msgstr ""
 "userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Включение загрузки PXE в конфигурацию DHCP"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2023,13 +2029,13 @@ msgstr ""
 "(смотрите ниже <xref linkend=\"tftp-images\"/>)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Настройка BOOTP сервера"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2045,7 +2051,7 @@ msgstr ""
 "соответственно."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2108,7 +2114,7 @@ msgstr ""
 "userinput> содержит MAC адрес машины.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2132,13 +2138,13 @@ msgstr ""
 "restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Включение TFTP сервера"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2148,7 +2154,7 @@ msgstr ""
 "<command>tftpd</command>."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2164,7 +2170,7 @@ msgstr ""
 "перенастройку пакета."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2182,7 +2188,7 @@ msgstr ""
 "изменить примеры конфигурации для соответствия."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2199,7 +2205,7 @@ msgstr ""
 "точка при поиске причин ошибок."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2229,13 +2235,13 @@ msgstr ""
 "используемого TFTP-сервером Linux."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Копирование TFTP образов в каталог TFTP сервера"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2251,7 +2257,7 @@ msgstr ""
 "зависит от клиента TFTP и никак не стандартизовано."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2266,13 +2272,13 @@ msgstr ""
 "следующие файлы из каталога <filename>netboot/</filename>:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2288,7 +2294,7 @@ msgstr ""
 "имени загружаемого файла."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2304,13 +2310,13 @@ msgstr ""
 "command> в качестве имени загружаемого файла."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Загрузка SPARC по TFTP"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2342,7 +2348,7 @@ msgstr ""
 "заглавными и если нужно, добавить имя субархитектуры."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2355,7 +2361,7 @@ msgstr ""
 "сообщения в логах сервера tftp, какое имя образа было запрошено."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2369,13 +2375,13 @@ msgstr ""
 "в котором его будет искать TFTP сервер."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Загрузка SGI по TFTP"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2389,13 +2395,13 @@ msgstr ""
 "<filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Автоматическая установка"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2411,13 +2417,13 @@ msgstr ""
 "fai-project.org\">домашней странице FAI</ulink>."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Автоматическая установка с помощью программы установки &debian;"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2431,7 +2437,7 @@ msgstr ""
 "вопросы, задаваемые во время процесса установки."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/sv/boot-installer.po b/po/sv/boot-installer.po
index c9d5f3997..66c0e28ba 100644
--- a/po/sv/boot-installer.po
+++ b/po/sv/boot-installer.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: installation-guide 20051025 boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2011-04-25 09:52+0100\n"
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n"
@@ -63,8 +63,8 @@ msgid "Booting from TFTP"
 msgstr "Uppstart från TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -74,8 +74,8 @@ msgstr ""
 "server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -85,8 +85,8 @@ msgstr ""
 "BOOTP-server."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -102,8 +102,8 @@ msgid "Booting from CD-ROM"
 msgstr "Uppstart från cd-rom"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -120,8 +120,8 @@ msgstr ""
 "fortsätt till nästa kapitel."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -137,8 +137,8 @@ msgstr ""
 "installationsmetoder som kan fungera för dig."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -154,8 +154,8 @@ msgstr ""
 "installationssystemet till cd-rom-enheten."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -396,8 +396,8 @@ msgid "The installer will now start as usual."
 msgstr "Installationsprogrammet kommer nu att starta som vanligt."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Uppstart från en cd-rom"
@@ -422,8 +422,10 @@ msgstr ""
 #| "or USB memory stick installation media as described in <xref linkend="
 #| "\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>."
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "För att starta upp installationsprogrammet från Windows måste du första "
 "hämta installationsmedia på cd-rom/dvd-rom eller USB-minnespinne som "
@@ -431,7 +433,7 @@ msgstr ""
 "files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -439,7 +441,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -455,7 +457,7 @@ msgstr ""
 "starta <command>setup.exe</command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After the program has been started, a few preliminary questions will be "
@@ -470,13 +472,13 @@ msgstr ""
 "installationsprogrammet för &debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Starta upp från DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -484,7 +486,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -496,7 +498,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -510,7 +512,7 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -518,7 +520,7 @@ msgstr ""
 "Uppstart från Linux med <command>LILO</command> eller <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -529,7 +531,7 @@ msgstr ""
 "drive-files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -547,7 +549,7 @@ msgstr ""
 "installationsprogrammet, dock bör du göra med försiktighet."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -565,7 +567,7 @@ msgstr ""
 "enheten och installera från cd-avbildningen, utan behov av nätverk."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -583,7 +585,7 @@ msgstr ""
 "exempel på en <filename>/etc/lilo.conf</filename>:"
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -595,7 +597,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -611,7 +613,7 @@ msgstr ""
 "<userinput>lilo</userinput> och starta om."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The procedure for <command>GRUB</command> is quite similar. Locate your "
@@ -633,7 +635,7 @@ msgstr ""
 "filename> finns på första partitionen av första disken i systemet):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -647,7 +649,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The procedure for <command>GRUB</command> is quite similar. Locate your "
@@ -667,7 +669,7 @@ msgstr ""
 "filename> finns på första partitionen av första disken i systemet):"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, fuzzy, no-c-format
 #| msgid ""
 #| "title  New Install\n"
@@ -689,7 +691,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -699,13 +701,13 @@ msgstr ""
 "command> och <command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Uppstart från USB-minne"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -729,13 +731,13 @@ msgstr ""
 "uppstartsargument eller bara trycka &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Uppstart från startdisketter"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -745,7 +747,7 @@ msgstr ""
 "disketterna från avbildningarna i <xref linkend=\"create-floppy\"/>."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -755,7 +757,7 @@ msgstr ""
 "primära diskettenheten, stäng av datorn som vanligt och starta upp den igen."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -774,7 +776,7 @@ msgstr ""
 "uppstartsprompten."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -790,7 +792,7 @@ msgstr ""
 "installerat) har du inget val. Om inte, gör en hård omstart vid uppstart."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -800,7 +802,7 @@ msgstr ""
 "introducerar startdisketten och slutar med prompten <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -817,7 +819,7 @@ msgstr ""
 "hittas under i <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -831,26 +833,26 @@ msgstr ""
 "startas automatiskt."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Uppstart via TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Det finns olika sätt att göra en TFTP-uppstart på i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "Nätverkskort eller moderkort med stöd för PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -864,13 +866,13 @@ msgstr ""
 "kan du konfigurera ditt BIOS att starta upp från nätverket."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "Nätverkskort med Network BootROM"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -880,7 +882,7 @@ msgstr ""
 "upp via TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -890,13 +892,13 @@ msgstr ""
 "Referera till det här dokumentet."
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -906,13 +908,13 @@ msgstr ""
 "startdisketter och även ROM-filer som kan göra uppstarter via TFTP."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Uppstartsskärmen"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, fuzzy, no-c-format
 #| msgid ""
 #| "When the installer boots, you should be presented with a friendly "
@@ -960,7 +962,7 @@ msgstr ""
 "tillgänglig."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, fuzzy, no-c-format
 #| msgid ""
 #| "For a normal installation, select either the <quote>Install</quote> or "
@@ -981,7 +983,7 @@ msgstr ""
 "upp installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -993,7 +995,7 @@ msgstr ""
 "räddningsläge och för automatiserade installationer."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -1013,7 +1015,7 @@ msgstr ""
 "gjort."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1066,7 +1068,7 @@ msgstr ""
 "userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1085,7 +1087,7 @@ msgstr ""
 "tangenterna."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1105,7 +1107,7 @@ msgstr ""
 "quote> (iLO) och HP:s <quote>Integrated Remote Assistant</quote> (IRA)."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, fuzzy, no-c-format
 #| msgid ""
 #| "To bypass the graphical boot screen you can either blindly press "
@@ -1134,13 +1136,13 @@ msgstr ""
 "uppstartsprompten, som beskrivet i hjälptexten."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Cd-innehåll"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1164,7 +1166,7 @@ msgstr ""
 "en mängd olika paket utan behov av tillgång till nätverket."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1190,7 +1192,7 @@ msgstr ""
 "uppstartsblock på mer konventionella system."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1207,7 +1209,7 @@ msgstr ""
 "som beskrivs nedan."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1230,7 +1232,7 @@ msgstr ""
 "före den tillåter installationen att fortsätta."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1254,13 +1256,13 @@ msgstr ""
 "andra alternativet."
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "VIKTIGT"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1280,13 +1282,13 @@ msgstr ""
 "skalprompten."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Alternativ 1: Starta upp från Boot Option Maintenance Menu"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1298,7 +1300,7 @@ msgstr ""
 "färdigställt sin systeminitiering."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1308,7 +1310,7 @@ msgstr ""
 "och tryck <command>ENTER</command>. Det här kommer att visa en ny meny."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1327,7 +1329,7 @@ msgstr ""
 "samma."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1346,7 +1348,7 @@ msgstr ""
 "steg."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1362,7 +1364,7 @@ msgstr ""
 "inläsningssekvensen för uppstarten."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1374,13 +1376,13 @@ msgstr ""
 "uppstartskärna och flaggor."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Alternativ 2: Starta upp från EFI-skalet"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1394,7 +1396,7 @@ msgstr ""
 "skivan med följande steg:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1406,7 +1408,7 @@ msgstr ""
 "färdigställer systeminitieringen."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1428,7 +1430,7 @@ msgstr ""
 "kommer det ta några extra sekunder när den initierar cd-enheten."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1442,7 +1444,7 @@ msgstr ""
 "replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1456,7 +1458,7 @@ msgstr ""
 "partitionsnumret som sin prompt."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1466,7 +1468,7 @@ msgstr ""
 "kommer att påbörja uppstartssekvensen."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1482,13 +1484,13 @@ msgstr ""
 "Fortsätt till att välja uppstartskärna och alternativ."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Installation med en seriekonsoll"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1509,7 +1511,7 @@ msgstr ""
 "förkonfigurerade."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1523,7 +1525,7 @@ msgstr ""
 "kommandot <command>baud</command> i EFI-skalet."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1540,7 +1542,7 @@ msgstr ""
 "classname>."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1559,7 +1561,7 @@ msgstr ""
 "startar installationsprogrammet i textläge."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1572,13 +1574,13 @@ msgstr ""
 "startat och kräver att du startar om före du kan påbörjar installationen."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Välj uppstartskärna och inställningar"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1598,7 +1600,7 @@ msgstr ""
 "vanliga kommandoradsflaggorna."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1623,7 +1625,7 @@ msgstr ""
 "installationen:"
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1633,7 +1635,7 @@ msgstr ""
 "med piltangenterna."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1645,7 +1647,7 @@ msgstr ""
 "inställningar för seriekonsoll) anges."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1657,7 +1659,7 @@ msgstr ""
 "skärmen av &debian; Installer."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1667,7 +1669,7 @@ msgstr ""
 "att ställa in språkanpassning, nätverk och diskpartitioner."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1687,7 +1689,7 @@ msgstr ""
 "cd-enheten."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1702,13 +1704,13 @@ msgstr ""
 "nätverk."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Konfiguration av servern"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1732,7 +1734,7 @@ msgstr ""
 "efi</command> att köra på klienten."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1748,7 +1750,7 @@ msgstr ""
 "uppstartsfilerna för ett IA-64-system."
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1766,7 +1768,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1788,13 +1790,13 @@ msgstr ""
 "tillhandahålls av paketet <classname>elilo</classname> för detaljer."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Konfiguration av klienten"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1825,7 +1827,7 @@ msgstr ""
 "<filename>elilo.efi</filename> från TFTP-servern."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1841,13 +1843,13 @@ msgstr ""
 "starta &debian; Installer."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Uppstart för SGI via TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1869,13 +1871,13 @@ msgstr ""
 "</screen></informalexample> i kommandomonitorn för att göra det."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Uppstartsparametrar"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1885,7 +1887,7 @@ msgstr ""
 "<command>bootp():</command> i kommandomonitorn."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1903,19 +1905,19 @@ msgstr ""
 "<command>append</command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Starta upp Cobalt via TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1933,7 +1935,7 @@ msgstr ""
 "finns följande installationsmetoder:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1949,7 +1951,7 @@ msgstr ""
 "klient kan du påbörja installationen."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1961,7 +1963,7 @@ msgstr ""
 "sätt."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1973,13 +1975,13 @@ msgstr ""
 "lägga till dina parametrar till variabeln <replaceable>args</replaceable>."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Begränsningar för s390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1989,7 +1991,7 @@ msgstr ""
 "nätverkskonfiguration och en ssh-session."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -2003,13 +2005,13 @@ msgstr ""
 "standardinstallationssystemet."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Uppstartsparametrar för s390"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -2022,7 +2024,7 @@ msgstr ""
 "installationsavbildningarna."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2047,7 +2049,7 @@ msgstr ""
 "för att starta upp från cd-rom."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2059,13 +2061,13 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2082,7 +2084,7 @@ msgstr ""
 "sedan installationsprogrammet till cd-enheten för de nödvändiga filerna."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2091,19 +2093,19 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Starta upp från hårddisk"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2113,7 +2115,7 @@ msgstr ""
 "för vissa system är det den enda installationsmetoden som stöds."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2125,13 +2127,13 @@ msgstr ""
 "\"boot-drive-files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Starta upp OldWorld PowerMac från MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2154,13 +2156,13 @@ msgstr ""
 "starta upp installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Starta upp NewWorld Mac från OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2203,13 +2205,13 @@ msgstr ""
 "installationprogram ska nu starta."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Starta upp från USB-minne"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2217,7 +2219,7 @@ msgstr ""
 "via USB."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2231,7 +2233,7 @@ msgstr ""
 "lagringsenheter som standard. Se <xref linkend=\"invoking-openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2253,7 +2255,7 @@ msgstr ""
 "filename> och <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2279,7 +2281,7 @@ msgstr ""
 "med <command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2290,7 +2292,7 @@ msgstr ""
 "Här kan du ange ytterligare uppstartsargument, eller bara trycka &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2302,7 +2304,7 @@ msgstr ""
 "förklaras i <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2310,7 +2312,7 @@ msgstr ""
 "via nätverk."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2346,7 +2348,7 @@ msgstr ""
 "över syntaxen och tillgängliga flaggor."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2359,7 +2361,7 @@ msgstr ""
 "diskettenheter, och USB-diskettenheter stöds inte för uppstart."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2371,7 +2373,7 @@ msgstr ""
 "sedan på systemet."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2386,7 +2388,7 @@ msgstr ""
 "hårddiskpartitioner."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2398,13 +2400,13 @@ msgstr ""
 "automatiskt efter att rotsystemet har lästs in i minnet."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "Uppstartsparametrar för PowerPC"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2420,7 +2422,7 @@ msgstr ""
 "skall <userinput>video=aty128fb:vmode:6</userinput> användas."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2440,7 +2442,7 @@ msgstr ""
 "på slutet av kommandot <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2452,13 +2454,13 @@ msgstr ""
 "enheten på ID 6 (eller sekundär master för IDE-baserade system)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM-meddelanden"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2474,13 +2476,13 @@ msgstr ""
 "för mer information."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Hjälpmedel"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some users may need specific support because of e.g. some visual "
@@ -2517,13 +2519,13 @@ msgstr ""
 "QWERTY-tangentbord."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "Punktskriftsskärmar med USB"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2546,13 +2548,13 @@ msgstr ""
 "ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Punktskriftsskärmar med seriekabel"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Serial braille displays cannot safely be automatically detected (since "
@@ -2609,14 +2611,14 @@ msgstr ""
 "ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, fuzzy, no-c-format
 #| msgid "Hardware Speech Synthesis"
 msgid "Software Speech Synthesis"
 msgstr "Talsynteser (maskinvara)"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2627,13 +2629,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Talsynteser (maskinvara)"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Support for hardware speech synthesis devices is available only alongside "
@@ -2649,7 +2651,7 @@ msgstr ""
 "välja <quote>Grafisk installation</quote> i uppstartsmenyn."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2672,13 +2674,13 @@ msgstr ""
 "installeras på målsystemet."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Brädenheter"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some accessibility devices are actual boards that are plugged inside the "
@@ -2700,7 +2702,7 @@ msgstr ""
 "tillgängliga språk."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2708,13 +2710,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Tema med hög kontrast"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2726,13 +2728,13 @@ msgstr ""
 "till uppstartsparametern <userinput>theme=dark</userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2740,7 +2742,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2754,7 +2756,7 @@ msgstr ""
 "Ibland behöver du dock hjälpa kärnan en bit på vägen."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2769,7 +2771,7 @@ msgstr ""
 "systemet om din maskinvara."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2785,7 +2787,7 @@ msgstr ""
 "beskrivna i <xref linkend=\"boot-troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2827,7 +2829,7 @@ msgstr ""
 "userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2873,7 +2875,7 @@ msgstr ""
 "userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2887,13 +2889,13 @@ msgstr ""
 "<filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Parametrar för &debian; Installer"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2908,7 +2910,7 @@ msgstr ""
 "användbara."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2924,20 +2926,20 @@ msgstr ""
 "kommer vanligtvis att använda den korta formen också."
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 "Den här parametern ställer in så att meddelanden med lägst prioritet visas."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2951,7 +2953,7 @@ msgstr ""
 "påträffas justerar installationsprogrammet prioriteten efter behov."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2972,13 +2974,13 @@ msgstr ""
 "till det."
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, fuzzy, no-c-format
 #| msgid ""
 #| "This boot parameter controls the type of user interface used for the "
@@ -3028,13 +3030,13 @@ msgstr ""
 "installationsprogrammet gränssnittet <userinput>gtk</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -3049,49 +3051,49 @@ msgstr ""
 "för att fortsätta uppstartsprocessen.)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Det här är standardinställningen."
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Mer information än normalt."
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Mycket felsökningsinformation."
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -3101,13 +3103,13 @@ msgstr ""
 "felsökning. Avsluta skalet för att fortsätta uppstarten."
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3119,7 +3121,7 @@ msgstr ""
 "userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3130,19 +3132,19 @@ msgstr ""
 "en enhet."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3151,13 +3153,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3170,13 +3172,13 @@ msgstr ""
 "\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3187,14 +3189,14 @@ msgstr ""
 "begränsad."
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 # Framebuffer. Bättre ord!
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3218,13 +3220,13 @@ msgstr ""
 "efter påbörjad installation."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Liknande problem har blivit rapporterats för hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3243,13 +3245,13 @@ msgstr ""
 "<userinput>fb=true</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3266,13 +3268,13 @@ msgstr ""
 "<userinput>theme=<replaceable>dark</replaceable></userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3286,7 +3288,7 @@ msgstr ""
 "sökningen misslyckas."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3300,13 +3302,13 @@ msgstr ""
 "nätverket konfigureras med DHCP och att informationen matas in manuellt."
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3317,13 +3319,13 @@ msgstr ""
 "det här problemet."
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3338,13 +3340,13 @@ msgstr ""
 "wiki;\">&debian; Installer Wiki</ulink>."
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3354,13 +3356,13 @@ msgstr ""
 "att automatisera installationen. Se <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3370,13 +3372,13 @@ msgstr ""
 "automatisera installationen. Se <xref linkend=\"automatic-install\"/>."
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3392,13 +3394,13 @@ msgstr ""
 "syntax användas. Se <xref linkend=\"preseed-seenflag\"/> för detaljer."
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3410,13 +3412,13 @@ msgstr ""
 "detaljer om hur man automatiserar installationer."
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3429,13 +3431,13 @@ msgstr ""
 "förhindra detta."
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3453,7 +3455,7 @@ msgstr ""
 "media automatiskt."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3465,13 +3467,13 @@ msgstr ""
 "upp automatiskt från den optiska enheten efter den initiala installationen."
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3486,7 +3488,7 @@ msgstr ""
 "install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3503,13 +3505,13 @@ msgstr ""
 "användare."
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3523,13 +3525,13 @@ msgstr ""
 "rekommenderas inte.</emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3541,13 +3543,13 @@ msgstr ""
 "ramdisken inte fullständigt gick att läsa in. Värdet är i kB."
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3558,13 +3560,13 @@ msgstr ""
 "\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Använding av uppstartsparametrar för att besvara frågor"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3579,25 +3581,25 @@ msgstr ""
 "exempel listas här nedan."
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3607,7 +3609,7 @@ msgstr ""
 "installationen och det installerade systemet."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3627,7 +3629,7 @@ msgstr ""
 "lokal kan uppnås på detta sätt."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3643,13 +3645,13 @@ msgstr ""
 "locale=sv_SE.UTF-8</userinput>."
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3666,7 +3668,7 @@ msgstr ""
 "phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3676,13 +3678,13 @@ msgstr ""
 "istället tvinga fram statisk nätverkskonfiguration."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3701,13 +3703,13 @@ msgstr ""
 "manuellt."
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3719,13 +3721,13 @@ msgstr ""
 "literal>. Se <xref linkend=\"pkgsel\"/> för ytterligare information."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Skicka parametrar till kärnmoduler"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3750,7 +3752,7 @@ msgstr ""
 "konfigurationen för det installerade systemet."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3764,7 +3766,7 @@ msgstr ""
 "i vissa fall, kan det fortfarande krävas att parametrar ställs in manuellt."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3786,19 +3788,19 @@ msgstr ""
 "(coax) och IRQ 10, skulle du skicka:"
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Svartlistning av kärnmoduler"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3816,7 +3818,7 @@ msgstr ""
 "drivrutin läses in först."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3832,7 +3834,7 @@ msgstr ""
 "installerade systemet."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3846,19 +3848,19 @@ msgstr ""
 "som visas under maskinvaruidentifieringsfaserna."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Felsök installationsprocessen"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Tillförlitlighet för cd-rom"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3873,7 +3875,7 @@ msgstr ""
 "installationen."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3885,13 +3887,13 @@ msgstr ""
 "hanterar dem. Resten är upp till dig."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Det finns två mycket enkla saker som du bör prova först."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3901,7 +3903,7 @@ msgstr ""
 "att den inte är smutsig."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3920,7 +3922,7 @@ msgstr ""
 "äldre cd-rom-enheter kan lösas på detta sätt."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3932,7 +3934,7 @@ msgstr ""
 "termen cd-rom för enkelhet."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3942,13 +3944,13 @@ msgstr ""
 "andra installationsmetoderna som finns tillgängliga."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Vanliga problem"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3958,7 +3960,7 @@ msgstr ""
 "brända med höga hastigheter med en modern cd-brännare."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3971,20 +3973,20 @@ msgstr ""
 "minnesåtkomst</quote> (DMA) är aktiverat."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Hur man undersöker och kanske även löser problem"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 "Prova förslagen som listas här nedan om uppstart med cd-rom misslyckas."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -3999,7 +4001,7 @@ msgstr ""
 "som du använder."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -4026,7 +4028,7 @@ msgstr ""
 "skivan."
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -4048,7 +4050,7 @@ msgstr ""
 "134486016 bytes (134 MB) kopierade, 97.474 sekunder, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -4070,7 +4072,7 @@ msgstr ""
 "och aktivera skalet där."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -4083,7 +4085,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -4113,7 +4115,7 @@ msgstr ""
 "kan du prova att läsa in den manuellt med <command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -4125,7 +4127,7 @@ msgstr ""
 "filename>. Det bör även finnas en <filename>/dev/cdrom</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4142,7 +4144,7 @@ msgstr ""
 "körning av kommandot."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4168,7 +4170,7 @@ msgstr ""
 "motsvarar din cd-rom-enhet."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4182,13 +4184,13 @@ msgstr ""
 "som ett allmänt test för att se om cd-skivan kan läsas tillförlitligt."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Tillförlitlighet för disketter"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4198,7 +4200,7 @@ msgstr ""
 "&debian; verkar vara pålitligheten för disketterna."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4216,7 +4218,7 @@ msgstr ""
 "som stora mängder av meddelanden om in/ut-fel."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4234,7 +4236,7 @@ msgstr ""
 "användbart att försöka att skriva disketten på en annan dator."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4246,7 +4248,7 @@ msgstr ""
 "allt bra med den tredje disketten."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4258,7 +4260,7 @@ msgstr ""
 "hämtades är korrekta genom att validera deras md5-kontrollsummor."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4271,13 +4273,13 @@ msgstr ""
 "<quote>fasta programvaran</quote>."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Uppstartskonfiguration"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4291,7 +4293,7 @@ msgstr ""
 "kontrollera, vilket diskuteras i <xref linkend=\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4300,7 +4302,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4312,37 +4314,37 @@ msgid ""
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Vanliga installationsproblem på &arch-title;"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4352,7 +4354,7 @@ msgstr ""
 "genom att skicka med vissa uppstartsparametrar till installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4372,13 +4374,13 @@ msgstr ""
 "konsollfunktioner. Se <xref linkend=\"boot-parms\"/> för detaljer."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Systemet fryser under konfigurationsfasen för PCMCIA"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4407,7 +4409,7 @@ msgstr ""
 "problemen."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4430,19 +4432,19 @@ msgstr ""
 "värdet i installationsprogrammet."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "Det finns några vanliga installationsproblem som är värda att nämna."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Felriktad videoutmatning"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4470,7 +4472,7 @@ msgstr ""
 "installationsprogrammet med <userinput>video=atyfb:off</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4484,13 +4486,13 @@ msgstr ""
 "i <filename>/etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Misslyckad uppstart eller installation från cd-rom"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4502,7 +4504,7 @@ msgstr ""
 "flesta problemen har rapporterats med SunBlade-system."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4510,13 +4512,13 @@ msgstr ""
 "installationsprogrammet."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Tolkning av kärnans uppstartsmeddelanden"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4554,13 +4556,13 @@ msgstr ""
 "<xref linkend=\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Rapportering av installationsproblem"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4580,7 +4582,7 @@ msgstr ""
 "in en felrapport kan du bifoga den här informationen i felrapporten."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4592,13 +4594,13 @@ msgstr ""
 "efter datorn har startats om till det nyligen installerade systemet."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Skicka installationsrapporter"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4612,7 +4614,7 @@ msgstr ""
 "maskinvarukonfigurationer."
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4625,7 +4627,7 @@ msgstr ""
 "den används publikt."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4645,7 +4647,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/sv/install-methods.po b/po/sv/install-methods.po
index af67eac0c..287ef1b68 100644
--- a/po/sv/install-methods.po
+++ b/po/sv/install-methods.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2011-04-25 09:50+0100\n"
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n"
@@ -80,15 +80,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -130,7 +129,7 @@ msgstr ""
 "kataloger och underkataloger på din cd."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -140,7 +139,7 @@ msgstr ""
 "den behöver från cd-skivan."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -159,13 +158,13 @@ msgstr ""
 "användas för att starta upp installationsprogrammet."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Hämta filer från &debian;-speglar"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -175,7 +174,7 @@ msgstr ""
 "<ulink url=\"&url-debian-mirrors;\">Hämta &debian; från Internet</ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -186,13 +185,13 @@ msgstr ""
 "automatiskt läge."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Var man får tag på installationsavbildningar"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -208,13 +207,13 @@ msgstr ""
 "dess funktion."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Installationsfiler för Thecus N2100"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -229,13 +228,13 @@ msgstr ""
 "från &n2100-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Installationsfiler för GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -247,13 +246,13 @@ msgstr ""
 "&glantank-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Installationsfiler för Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -265,13 +264,13 @@ msgstr ""
 "&kuroboxpro-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Installationsfiler för HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -287,13 +286,13 @@ msgstr ""
 "programvaruavbildningen kan hämtas från &mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Installationsfiler för QNAP Turbo Station"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -314,14 +313,14 @@ msgstr ""
 "&qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, fuzzy, no-c-format
 #| msgid "SheevaPlug and OpenRD Installation Files"
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Installationsfiler för SheevaPlug och OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the Marvell SheevaPlug and OpenRD devices "
@@ -337,14 +336,14 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "CATS Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "Installationsfiler för CATS"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for the Marvell SheevaPlug and OpenRD devices "
@@ -361,13 +360,13 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Skapa ett IPL-band"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -389,13 +388,13 @@ msgstr ""
 "underkatalogen <filename>tape</filename>, se <xref linkend=\"where-files\"/>."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Skapa startdisketter från diskettavbildningar"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -406,7 +405,7 @@ msgstr ""
 "på andra sätt."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -416,7 +415,7 @@ msgstr ""
 "diskettenheter enligt rapporter."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -436,7 +435,7 @@ msgstr ""
 "en <emphasis>sektorkopiering</emphasis> av data från filen till disketten."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -448,7 +447,7 @@ msgstr ""
 "diskettavbildningar på olika plattformar."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -463,7 +462,7 @@ msgstr ""
 "diskettavbildningarna finnas inkluderade på skivan.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -475,13 +474,13 @@ msgstr ""
 "att vara säker på att de inte oavsiktligt ändras."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Skriva diskettavbildningar från ett Linux eller Unix-system"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -517,7 +516,7 @@ msgstr ""
 "<command>eject</command>, se manualsidan)</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -551,7 +550,7 @@ msgstr ""
 "systemadministratör. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -563,13 +562,13 @@ msgstr ""
 "installera det."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Skriva diskettavbildningar från DOS, Windows eller OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -579,7 +578,7 @@ msgstr ""
 "följande program för att kopiera avbildningar till disketter."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -595,7 +594,7 @@ msgstr ""
 "Utforskaren i Windows kommer <emphasis>inte</emphasis> att fungera."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -607,7 +606,7 @@ msgstr ""
 "packa upp diskio.dll i samma katalog."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -617,13 +616,13 @@ msgstr ""
 "katalogen <filename>/tools</filename>."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Skriva diskettavbildningar från MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -645,7 +644,7 @@ msgstr ""
 "fortsätta att skriva filavbildningen till den."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -660,13 +659,13 @@ msgstr ""
 "verktygen."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Skriva diskettavbildningar med <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -680,7 +679,7 @@ msgstr ""
 "du hämtade avbildningsfilerna från en &debian;-spegel."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -690,7 +689,7 @@ msgstr ""
 "ulink> och använd den för att öppna filen <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -702,7 +701,7 @@ msgstr ""
 "skiftkänsliga."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -717,7 +716,7 @@ msgstr ""
 "MacOS inte kan ta bort startblocken om avbildningen monteras av misstag."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -729,7 +728,7 @@ msgstr ""
 "diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -745,13 +744,13 @@ msgstr ""
 "vill radera den. När den är klar ska den mata ut disketten."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Skriva diskettavbildningar med <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -765,7 +764,7 @@ msgstr ""
 "userinput>."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -773,14 +772,14 @@ msgstr ""
 "Mata in disketten enligt begäran, tryck sedan &enterkey; (start på sektor 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr "Välj filen <filename>root.bin</filename> i filöppningsdialogen."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -794,7 +793,7 @@ msgstr ""
 "annan."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -805,13 +804,13 @@ msgstr ""
 "emphasis>! Om du av misstag monterar den i MacOS kommer MacOS förstöra den."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Förbereda filer för uppstart med USB-minne"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -835,7 +834,7 @@ msgstr ""
 "minne så måste du stänga av dess skrivskydd (om sådant finns)."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -849,13 +848,13 @@ msgstr ""
 "information går förlorad på till exempel en hårddisk."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -865,7 +864,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -875,7 +874,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -887,7 +886,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -903,7 +902,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -913,7 +912,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -922,7 +921,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -931,14 +930,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, fuzzy, no-c-format
 #| msgid "Booting the USB stick"
 msgid "Manually copying files to the USB stick"
 msgstr "Starta upp på USB-minne"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note that the USB stick should be at least 256 MB in size (smaller setups "
@@ -953,7 +952,7 @@ msgstr ""
 "är möjliga om du följer <xref linkend=\"usb-copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, fuzzy, no-c-format
 #| msgid ""
 #| "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> "
@@ -975,7 +974,7 @@ msgstr ""
 "<command>yaboot</command> och dess konfigurationsfil.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note that, although convenient, this method does have one major "
@@ -1002,7 +1001,7 @@ msgstr ""
 "eller nätinstallation."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
@@ -1010,13 +1009,13 @@ msgstr ""
 "till ditt USB-minne:"
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1028,13 +1027,13 @@ msgstr ""
 "extrahera avbildningen direkt till den:"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1065,14 +1064,14 @@ msgstr ""
 "färdig."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, fuzzy, no-c-format
 #| msgid "Copying the files &mdash; the flexible way"
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Kopiera filerna &mdash; det flexibla sättet"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1088,13 +1087,13 @@ msgstr ""
 "avbildning till det."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Partitionera USB-minnet"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1104,7 +1103,7 @@ msgstr ""
 "partitionen, istället för hela enheten."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1147,7 +1146,7 @@ msgstr ""
 "i &debian;-paketet <classname>dosfstools</classname>."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1166,7 +1165,7 @@ msgstr ""
 "konfigurationen av starthanteraren."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1191,13 +1190,13 @@ msgstr ""
 "starthanterarens programkod."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Lägg till installationsavbildningen"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1223,7 +1222,7 @@ msgstr ""
 "behandla DOS-filnamn (8.3 tecken)."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1257,7 +1256,7 @@ msgstr ""
 "du lägga till <userinput>vga=788</userinput> på den andra raden."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1265,7 +1264,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy a "
@@ -1294,7 +1293,7 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1324,7 +1323,7 @@ msgstr ""
 "i &debian;-paketet <classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1340,7 +1339,7 @@ msgstr ""
 "för att göra ändringar i konfigurationen för starthanteraren."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1376,7 +1375,7 @@ msgstr ""
 "de vanliga Unix-verktygen."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1387,31 +1386,31 @@ msgstr ""
 "minnet:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (kärnbinär)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (initiell ramdiskavbildning)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yaboots konfigurationsfil)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (valfritt uppstartsmeddelande)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1446,13 +1445,13 @@ msgstr ""
 "userinput> kan behöva ökas, beroende på avbildningen du startar upp."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Förbereda filer för uppstart med hårddisk"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1464,7 +1463,7 @@ msgstr ""
 "eller genom att kalla upp en starthanterare direkt från BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1478,7 +1477,7 @@ msgstr ""
 "disketter."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1500,7 +1499,7 @@ msgstr ""
 "installationsfilerna du hämtade."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1512,7 +1511,7 @@ msgstr ""
 "<quote>OldWorld</quote>-modell."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1522,7 +1521,7 @@ msgstr ""
 "<command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1533,7 +1532,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1545,7 +1544,7 @@ msgstr ""
 "av kärnan."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1557,19 +1556,19 @@ msgstr ""
 "filsystem), exempelvis till <filename>/boot/newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (kärnbinär)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (ramdiskavbildning)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1579,13 +1578,13 @@ msgstr ""
 "linkend=\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr "Starta upp hårddiskinstalleraren med <command>loadlin</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1595,7 +1594,7 @@ msgstr ""
 "upp installationsprogrammet från DOS med <command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1605,7 +1604,7 @@ msgstr ""
 "<filename>c:\\</filename>."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1614,19 +1613,19 @@ msgstr ""
 "avbildning)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (loadlin-verktyg)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Uppstart av hårddiskinstallerare på OldWorld Mac"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1650,7 +1649,7 @@ msgstr ""
 "<application>BootX</application> krävs på den modellen."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1678,13 +1677,13 @@ msgstr ""
 "i den aktiva Systemmappen."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Uppstart av hårddiskinstallerare på NewWorld Mac"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1705,7 +1704,7 @@ msgstr ""
 "NewWorld PowerMac."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1719,31 +1718,31 @@ msgstr ""
 "till hårddisksikonen)."
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1759,7 +1758,7 @@ msgstr ""
 "prompten när du startar upp installationsprogrammet."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1767,13 +1766,13 @@ msgstr ""
 "\"boot-newworld\"/>."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Förbered filerna för nätverksuppstart via TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1789,7 +1788,7 @@ msgstr ""
 "att få stöd för uppstart av din specifika maskin."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1801,7 +1800,7 @@ msgstr ""
 "phrase><phrase condition=\"supports-bootp\">, eller BOOTP-server</phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1822,7 +1821,7 @@ msgstr ""
 "konfigureras via DHCP."
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1834,7 +1833,7 @@ msgstr ""
 "starta upp via BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1845,7 +1844,7 @@ msgstr ""
 "tillgängligt i &debian;."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1860,7 +1859,7 @@ msgstr ""
 "SunOS 5.x (även kallad Solaris) och GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1874,13 +1873,13 @@ msgstr ""
 "problem. Ett bra alternativ är <classname>atftpd</classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Konfigurering av RARP-server"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1900,7 +1899,7 @@ msgstr ""
 "kommandot <userinput>ip addr show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1924,13 +1923,13 @@ msgstr ""
 "eller <userinput>/usr/etc/rarpd -a</userinput> på SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Konfigurering av DHCP-server"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1944,7 +1943,7 @@ msgstr ""
 "filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1988,7 +1987,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -2006,7 +2005,7 @@ msgstr ""
 "hämtas via TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -2016,13 +2015,13 @@ msgstr ""
 "starta om den med <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Aktivera PXE-uppstart i DHCP-konfigurationen"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2093,13 +2092,13 @@ msgstr ""
 "kärnavbildning (se <xref linkend=\"tftp-images\"/> nedan)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Konfigurera en BOOTP-server"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2114,7 +2113,7 @@ msgstr ""
 "<classname>bootp</classname> respektive <classname>dhcp3-server</classname>."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2177,7 +2176,7 @@ msgstr ""
 "MAC-adress. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2201,13 +2200,13 @@ msgstr ""
 "<userinput>/etc/init.d/dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Aktivering av TFTP-server"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2217,7 +2216,7 @@ msgstr ""
 "<command>tftpd</command> är aktiverad."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2233,7 +2232,7 @@ msgstr ""
 "paketet installeras och kan ändras genom att konfigurera om paketet."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2251,7 +2250,7 @@ msgstr ""
 "konfigurationsexemplen i det här avsnittet."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2268,7 +2267,7 @@ msgstr ""
 "felen."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2299,13 +2298,13 @@ msgstr ""
 "Linux TFTP-server använder."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Flytta TFTP-avbildningarna till rätt plats"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2322,7 +2321,7 @@ msgstr ""
 "finns inga riktiga standarder."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2338,13 +2337,13 @@ msgstr ""
 "filename>:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2361,7 +2360,7 @@ msgstr ""
 "uppstart."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2377,13 +2376,13 @@ msgstr ""
 "efi</filename> till <command>tftpd</command> som filnamnet att starta upp på."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Uppstart via TFTP för SPARC"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2415,7 +2414,7 @@ msgstr ""
 "underarkitekturens namn."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2429,7 +2428,7 @@ msgstr ""
 "avbildningsnamn som efterfrågas."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2443,13 +2442,13 @@ msgstr ""
 "i katalogen som TFTP-servern letar i."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Uppstart via TFTP för SGI"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2463,13 +2462,13 @@ msgstr ""
 "<userinput>filename=</userinput> i <filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Automatisk installation"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, fuzzy, no-c-format
 #| msgid ""
 #| "For installing on multiple computers it's possible to do fully automatic "
@@ -2491,13 +2490,13 @@ msgstr ""
 "<classname>autoinstall</classname>, och själva &debian; Installer."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Automatisk installation med &debian; Installer"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2511,7 +2510,7 @@ msgstr ""
 "ställs under installationsprocessen."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/tl/administrivia.po b/po/tl/administrivia.po
index 29c5f204a..164f2ad70 100644
--- a/po/tl/administrivia.po
+++ b/po/tl/administrivia.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,44 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:11
 #, no-c-format
-msgid "This manual was created for Sarge's debian-installer, based on the Woody installation manual for boot-floppies, which was based on earlier Debian installation manuals, and on the Progeny distribution manual which was released under GPL in 2003."
+msgid ""
+"This manual was created for Sarge's debian-installer, based on the Woody "
+"installation manual for boot-floppies, which was based on earlier Debian "
+"installation manuals, and on the Progeny distribution manual which was "
+"released under GPL in 2003."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:18
 #, no-c-format
-msgid "This document is written in DocBook XML. Output formats are generated by various programs using information from the <classname>docbook-xml</classname> and <classname>docbook-xsl</classname> packages."
+msgid ""
+"This document is written in DocBook XML. Output formats are generated by "
+"various programs using information from the <classname>docbook-xml</"
+"classname> and <classname>docbook-xsl</classname> packages."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:25
 #, no-c-format
-msgid "In order to increase the maintainability of this document, we use a number of XML features, such as entities and profiling attributes. These play a role akin to variables and conditionals in programming languages. The XML source to this document contains information for each different architecture &mdash; profiling attributes are used to isolate certain bits of text as architecture-specific."
+msgid ""
+"In order to increase the maintainability of this document, we use a number "
+"of XML features, such as entities and profiling attributes. These play a "
+"role akin to variables and conditionals in programming languages. The XML "
+"source to this document contains information for each different architecture "
+"&mdash; profiling attributes are used to isolate certain bits of text as "
+"architecture-specific."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:34
 #, no-c-format
-msgid "Translators can use this paragraph to acknowledge the people responsible for the translation of the manual. Translation teams are advised to just mention the coordinator and maybe major contributors and thank everybody else in a phrase like \"all translators and reviewers from the translation team for {your language} at {your l10n mailinglist}\". See build/lang-options/README on how to enable this paragraph. Its condition is \"about-langteam\"."
+msgid ""
+"Translators can use this paragraph to acknowledge the people responsible for "
+"the translation of the manual. Translation teams are advised to just mention "
+"the coordinator and maybe major contributors and thank everybody else in a "
+"phrase like \"all translators and reviewers from the translation team for "
+"{your language} at {your l10n mailinglist}\". See build/lang-options/README "
+"on how to enable this paragraph. Its condition is \"about-langteam\"."
 msgstr ""
 
 #. Tag: title
@@ -58,19 +78,46 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:52
 #, no-c-format
-msgid "If you have problems or suggestions regarding this document, you should probably submit them as a bug report against the package <classname>installation-guide</classname>. See the <classname>reportbug</classname> package or read the online documentation of the <ulink url=\"&url-bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could check the <ulink url=\"&url-bts;installation-guide\">open bugs against installation-guide</ulink> to see whether your problem has already been reported. If so, you can supply additional corroboration or helpful information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, where <replaceable>XXXX</replaceable> is the number for the already-reported bug."
+msgid ""
+"If you have problems or suggestions regarding this document, you should "
+"probably submit them as a bug report against the package "
+"<classname>installation-guide</classname>. See the <classname>reportbug</"
+"classname> package or read the online documentation of the <ulink url=\"&url-"
+"bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could "
+"check the <ulink url=\"&url-bts;installation-guide\">open bugs against "
+"installation-guide</ulink> to see whether your problem has already been "
+"reported. If so, you can supply additional corroboration or helpful "
+"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</"
+"email>, where <replaceable>XXXX</replaceable> is the number for the already-"
+"reported bug."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:68
 #, no-c-format
-msgid "Better yet, get a copy of the DocBook source for this document, and produce patches against it. The DocBook source can be found at the <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with DocBook, don't worry: there is a simple cheatsheet in the manuals directory that will get you started. It's like html, but oriented towards the meaning of the text rather than the presentation. Patches submitted to the debian-boot mailing list (see below) are welcomed. For instructions on how to check out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> from the source root directory."
+msgid ""
+"Better yet, get a copy of the DocBook source for this document, and produce "
+"patches against it. The DocBook source can be found at the <ulink url=\"&url-"
+"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with "
+"DocBook, don't worry: there is a simple cheatsheet in the manuals directory "
+"that will get you started. It's like html, but oriented towards the meaning "
+"of the text rather than the presentation. Patches submitted to the debian-"
+"boot mailing list (see below) are welcomed. For instructions on how to check "
+"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> "
+"from the source root directory."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:82
 #, no-c-format
-msgid "Please do <emphasis>not</emphasis> contact the authors of this document directly. There is also a discussion list for &d-i;, which includes discussions of this manual. The mailing list is <email>debian-boot@lists.debian.org</email>. Instructions for subscribing to this list can be found at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online."
+msgid ""
+"Please do <emphasis>not</emphasis> contact the authors of this document "
+"directly. There is also a discussion list for &d-i;, which includes "
+"discussions of this manual. The mailing list is <email>debian-boot@lists."
+"debian.org</email>. Instructions for subscribing to this list can be found "
+"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List "
+"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-"
+"list-archives;\">Debian Mailing List Archives</ulink> online."
 msgstr ""
 
 #. Tag: title
@@ -82,37 +129,62 @@ msgstr ""
 #. Tag: para
 #: administrivia.xml:101
 #, no-c-format
-msgid "This document was originally written by Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the Installation Howto."
+msgid ""
+"This document was originally written by Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the "
+"Installation Howto."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:107
 #, no-c-format
-msgid "Miroslav Kuře has documented a lot of the new functionality in Sarge's debian-installer. Frans Pop was the main editor and release manager during the Etch, Lenny and Squeeze releases."
+msgid ""
+"Miroslav Kuře has documented a lot of the new functionality in Sarge's "
+"debian-installer. Frans Pop was the main editor and release manager during "
+"the Etch, Lenny and Squeeze releases."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:113
 #, no-c-format
-msgid "Many, many Debian users and developers contributed to this document. Particular note must be made of Michael Schmitz (m68k support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. We have to thank Pascal Le Bail for useful information about booting from USB memory sticks."
+msgid ""
+"Many, many Debian users and developers contributed to this document. "
+"Particular note must be made of Michael Schmitz (m68k support), Frank "
+"Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;"
+"\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins "
+"(SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous "
+"edits and text. We have to thank Pascal Le Bail for useful information about "
+"booting from USB memory sticks."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:124
 #, no-c-format
-msgid "Extremely helpful text and information was found in Jim Mintha's HOWTO for network booting (no URL available), the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, amongst others. The maintainers of these freely available and rich sources of information must be recognized."
+msgid ""
+"Extremely helpful text and information was found in Jim Mintha's HOWTO for "
+"network booting (no URL available), the <ulink url=\"&url-debian-faq;"
+"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors "
+"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, "
+"amongst others. The maintainers of these freely available and rich sources "
+"of information must be recognized."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:136
 #, no-c-format
-msgid "The section on chrooted installations in this manual (<xref linkend=\"linux-upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
+msgid ""
+"The section on chrooted installations in this manual (<xref linkend=\"linux-"
+"upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:142
 #, no-c-format
-msgid "The section on installations over plip in this manual (<xref linkend=\"plip\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> by Gilles Lamiral."
+msgid ""
+"The section on installations over plip in this manual (<xref linkend=\"plip"
+"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> by Gilles Lamiral."
 msgstr ""
 
 #. Tag: title
@@ -126,4 +198,3 @@ msgstr ""
 #, no-c-format
 msgid "All trademarks are property of their respective trademark owners."
 msgstr ""
-
diff --git a/po/tl/boot-installer.po b/po/tl/boot-installer.po
index 26928271b..9daaf7e68 100644
--- a/po/tl/boot-installer.po
+++ b/po/tl/boot-installer.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,21 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:15
 #, no-c-format
-msgid "If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly shut down <emphasis>before</emphasis> you boot the installer. Installing an operating system while another operating system is in hibernation (has been suspended to disk) could result in loss of, or damage to the state of the suspended operating system which could cause problems when it is rebooted."
+msgid ""
+"If you have any other operating systems on your system that you wish to keep "
+"(dual boot setup), you should make sure that they have been properly shut "
+"down <emphasis>before</emphasis> you boot the installer. Installing an "
+"operating system while another operating system is in hibernation (has been "
+"suspended to disk) could result in loss of, or damage to the state of the "
+"suspended operating system which could cause problems when it is rebooted."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:26
 #, no-c-format
-msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For information on how to boot the graphical installer, see <xref linkend="
+"\"graphical\"/>."
 msgstr ""
 
 #. Tag: title
@@ -44,21 +53,30 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
-msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
+msgid ""
+"Booting from the network requires that you have a network connection and a "
+"TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
-msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
+msgid ""
+"Older systems such as the 715 might require the use of an RBOOT server "
+"instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
-msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The installation method to support network booting is described in <xref "
+"linkend=\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -68,27 +86,47 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
-msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
+msgid ""
+"The easiest route for most people will be to use a set of &debian; CDs. If "
+"you have a CD set, and if your machine supports booting directly off the CD, "
+"great! Simply <phrase arch=\"x86\"> configure your system for booting off a "
+"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
+"your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
-msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
+msgid ""
+"Note that certain CD drives may require special drivers, and thus be "
+"inaccessible in the early installation stages. If it turns out the standard "
+"way of booting off a CD doesn't work for your hardware, revisit this chapter "
+"and read about alternate kernels and installation methods which may work for "
+"you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
-msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
+msgid ""
+"Even if you cannot boot from CD-ROM, you can probably install the &debian; "
+"system components and any packages you want from CD-ROM. Simply boot using a "
+"different media, such as floppies. When it's time to install the operating "
+"system, base system, and any additional packages, point the installation "
+"system at the CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
-msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
@@ -100,13 +138,20 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:113
 #, no-c-format
-msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines."
+msgid ""
+"There is an increasing number of consumer devices that directly boot from a "
+"flash chip on the device. The installer can be written to flash so it will "
+"automatically start when you reboot your machines."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:119
 #, no-c-format
-msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely."
+msgid ""
+"In many cases, changing the firmware of an embedded device voids your "
+"warranty. Sometimes you are also not able to recover your device if there "
+"are problems during the flashing process. Therefore, please take care and "
+"follow the steps precisely."
 msgstr ""
 
 #. Tag: title
@@ -118,13 +163,28 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:132
 #, no-c-format
-msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>."
+msgid ""
+"Due to limitations in the SS4000-E firmware, it unfortunately is not "
+"possible to boot the installer without the use of a serial port at this "
+"time. To boot the installer, you will need a serial nullmodem cable; a "
+"computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB "
+"serial converter will also work. </para> </footnote>; and a ribbon cable "
+"with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the "
+"other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older "
+"desktop machines with builtin 9-pin serial ports. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:153
 #, no-c-format
-msgid "To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a &debian; GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:"
+msgid ""
+"To boot the SS4000-E, use your serial nullmodem cable and the ribbon cable "
+"to connect to the serial port of the SS4000-E, and reboot the machine. You "
+"need to use a serial terminal application to communicate with the machine; a "
+"good option on a &debian; GNU/Linux is to use the <command>cu</command> "
+"program, in the package of the same name. Assuming the serial port on your "
+"computer is to be found on <filename>/dev/ttyS0</filename>, use the "
+"following command line:"
 msgstr ""
 
 #. Tag: screen
@@ -136,7 +196,10 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:167
 #, no-c-format
-msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit."
+msgid ""
+"If using Windows, you may want to consider using the program "
+"<classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word "
+"length, no stop bits, and one parity bit."
 msgstr ""
 
 #. Tag: para
@@ -149,63 +212,86 @@ msgstr ""
 #: boot-installer.xml:179
 #, no-c-format
 msgid ""
-      "No network interfaces found\n"
-      "\n"
-      "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
-      "== Executing boot script in 1.000 seconds - enter ^C to abort"
+"No network interfaces found\n"
+"\n"
+"EM-7210 ver.T04 2005-12-12 (For ver.AA)\n"
+"== Executing boot script in 1.000 seconds - enter ^C to abort"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:181
 #, no-c-format
-msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following commands:"
+msgid ""
+"At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-"
+"s4ke-sec\"> <para> Note that you have only one second to do so; if you miss "
+"this window, just powercycle the machine and try again. </para> </footnote>. "
+"This will give you the RedBoot prompt. Enter the following commands:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:194
 #, no-c-format
 msgid ""
-      "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
-      "load -v -r -b 0x01008000 -m ymodem zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000"
+"load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n"
+"load -v -r -b 0x01008000 -m ymodem zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:196
 #, no-c-format
-msgid "After every <command>load</command> command, the system will expect a file to be transmitted using the YMODEM protocol. When using cu, make sure you have the package <classname>lrzsz</classname> installed, then hit enter, followed by the <quote>~&lt;</quote> escape sequence to start an external program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</command>."
+msgid ""
+"After every <command>load</command> command, the system will expect a file "
+"to be transmitted using the YMODEM protocol. When using cu, make sure you "
+"have the package <classname>lrzsz</classname> installed, then hit enter, "
+"followed by the <quote>~&lt;</quote> escape sequence to start an external "
+"program, and run <command>sb initrd.gz</command> or <command>sb vmlinuz</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:205
 #, no-c-format
-msgid "Alternatively, it is possible to load the kernel and ramdisk using HTTP rather than YMODEM. This is faster, but requires a working HTTP server on the network. To do so, first switch the bootloader to RAM mode:"
+msgid ""
+"Alternatively, it is possible to load the kernel and ramdisk using HTTP "
+"rather than YMODEM. This is faster, but requires a working HTTP server on "
+"the network. To do so, first switch the bootloader to RAM mode:"
 msgstr ""
 
 #. Tag: screen
 #: boot-installer.xml:211
 #, no-c-format
 msgid ""
-      "fis load rammode\n"
-      "g"
+"fis load rammode\n"
+"g"
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:213
 #, no-c-format
-msgid "This will seemingly restart the machine; but in reality, it loads redboot to RAM and restarts it from there. Not doing this step will cause the system to hang in the necessary ip_address step that comes next."
+msgid ""
+"This will seemingly restart the machine; but in reality, it loads redboot to "
+"RAM and restarts it from there. Not doing this step will cause the system to "
+"hang in the necessary ip_address step that comes next."
 msgstr ""
 
 #. Tag: para
 #: boot-installer.xml:219
 #, no-c-format
 msgid ""
-      "You will need to hit Ctrl-C again to interrupt the boot. Then: <informalexample><screen>\n"
-      "ip_address -l <replaceable>192.168.2.249</replaceable> -h <replaceable>192.168.2.4</replaceable>\n"
-      "load -v -r -b 0x01800000 -m http /initrd.gz\n"
-      "load -v -r -b 0x01008000 -m http /zImage\n"
-      "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r 0x01800000\n"
-      "</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> is the IP address of the installed system and <replaceable>192.168.2.4</replaceable> the IP address of the HTTP server containing the kernel and ramdisk files."
+"You will need to hit Ctrl-C again to interrupt the boot. Then: "
+"<informalexample><screen>\n"
+"ip_address -l <replaceable>192.168.2.249</replaceable> -h "
+"<replaceable>192.168.2.4</replaceable>\n"
+"load -v -r -b 0x01800000 -m http /initrd.gz\n"
+"load -v -r -b 0x01008000 -m http /zImage\n"
+"exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r "
+"0x01800000\n"
+"</screen></informalexample> Where <replaceable>192.168.2.249</replaceable> "
+"is the IP address of the installed system and <replaceable>192.168.2.4</"
+"replaceable> the IP address of the HTTP server containing the kernel and "
+"ramdisk files."
 msgstr ""
 
 #. Tag: para
@@ -215,7 +301,8 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -235,2042 +322,3004 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:355
 #, no-c-format
-msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+msgid ""
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
-msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
+msgid ""
+"download a standalone Windows executable, which is available as tools/win32-"
+"loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
-msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
+msgid ""
+"If you use an installation CD or DVD, a pre-installation program should be "
+"launched automatically when you insert the disc. In case Windows does not "
+"start it automatically, or if you are using a USB memory stick, you can run "
+"it manually by accessing the device and executing <command>setup.exe</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
-msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
+msgid ""
+"After the program has been started, a few preliminary questions will be "
+"asked and the system will be prepared to reboot into the &debian-gnu; "
+"installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
-msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
+msgid ""
+"Boot into DOS (not Windows). To do this, you can for instance boot from a "
+"recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
-      "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
-      "d:\n"
-      "</screen></informalexample> else make sure you have first prepared your hard disk as explained in <xref linkend=\"files-loadlin\"/>, and change the current drive to it if needed."
+"If you can access the installation CD, change the current drive to the CD-"
+"ROM drive, e.g. <informalexample><screen>\n"
+"d:\n"
+"</screen></informalexample> else make sure you have first prepared your hard "
+"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the "
+"current drive to it if needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
-      "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
-      "cd \\&x86-install-dir;\n"
-      "</screen></informalexample> If you prefer using the graphical installer, enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
-      "cd gtk\n"
-      "</screen></informalexample> Next, execute <command>install.bat</command>. The kernel will load and launch the installer system."
+"Enter the subdirectory for the flavor you chose, e.g., "
+"<informalexample><screen>\n"
+"cd \\&x86-install-dir;\n"
+"</screen></informalexample> If you prefer using the graphical installer, "
+"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
+"cd gtk\n"
+"</screen></informalexample> Next, execute <command>install.bat</command>. "
+"The kernel will load and launch the installer system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
-msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
-msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you must first download and place the "
+"needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
-msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
+msgid ""
+"If you intend to use the hard drive only for booting and then download "
+"everything over the network, you should download the <filename>netboot/"
+"debian-installer/&architecture;/initrd.gz</filename> file and its "
+"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
+"linux</filename>. This will allow you to repartition the hard disk from "
+"which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
-msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
+msgid ""
+"Alternatively, if you intend to keep an existing partition on the hard drive "
+"unchanged during the install, you can download the <filename>hd-media/initrd."
+"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
+"drive (make sure the file is named ending in <literal>.iso</literal>). The "
+"installer can then boot from the drive and install from the CD/DVD image, "
+"without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
-msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
+msgid ""
+"For <command>LILO</command>, you will need to configure two essential things "
+"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
+"load the <filename>initrd.gz</filename> installer at boot time; </para></"
+"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
+"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
+"a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
-      "image=/boot/newinstall/vmlinuz\n"
-      "       label=newinstall\n"
-      "       initrd=/boot/newinstall/initrd.gz"
+"image=/boot/newinstall/vmlinuz\n"
+"       label=newinstall\n"
+"       initrd=/boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
-msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
+msgid ""
+"For more details, refer to the <citerefentry><refentrytitle>initrd</"
+"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
+"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
+"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
+"reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
-msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
+msgid ""
+"The procedure for <command>GRUB1</command> is quite similar. Locate your "
+"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
+"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
+"entry for the installer, for example (assuming <filename>/boot</filename> is "
+"on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
-      "title  New Install\n"
-      "root   (hd0,0)\n"
-      "kernel /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz"
+"title  New Install\n"
+"root   (hd0,0)\n"
+"kernel /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
-msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
+msgid ""
+"The procedure for <command>GRUB2</command> is very similar. The file is "
+"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
+"filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
-      "menuentry 'New Install' {\n"
-      "insmod part_msdos\n"
-      "insmod ext2\n"
-      "set root='(hd0,msdos1)'\n"
-      "linux /boot/newinstall/vmlinuz\n"
-      "initrd /boot/newinstall/initrd.gz\n"
-      "}"
+"menuentry 'New Install' {\n"
+"insmod part_msdos\n"
+"insmod ext2\n"
+"set root='(hd0,msdos1)'\n"
+"linux /boot/newinstall/vmlinuz\n"
+"initrd /boot/newinstall/initrd.gz\n"
+"}"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
-msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
+msgid ""
+"From here on, there should be no difference between <command>GRUB</command> "
+"or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, no-c-format
-msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
+"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
+"stick into some free USB connector and reboot the computer. The system "
+"should boot up, and unless you have used the flexible way to build the stick "
+"and not enabled it, you should be presented with the <prompt>boot:</prompt> "
+"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
-msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
+msgid ""
+"You will have already downloaded the floppy images you needed and created "
+"floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
-msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
+msgid ""
+"To boot from the installer boot floppy, place it in the primary floppy "
+"drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
-msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt."
+msgid ""
+"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
+"you need to specify the virtual location for the floppy device. This is done "
+"with the <emphasis>root=</emphasis> boot argument, giving the device that "
+"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
+"is connected as the first IDE device (master) on the second cable, you enter "
+"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
-msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
+msgid ""
+"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
+"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
+"machine, so a <quote>hard</quote> reboot is recommended. If you are "
+"installing from an existing operating system (e.g., from a DOS box) you "
+"don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
-msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
+msgid ""
+"The floppy disk will be accessed, and you should then see a screen that "
+"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
-msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
+msgid ""
+"Once you press &enterkey;, you should see the message "
+"<computeroutput>Loading...</computeroutput>, followed by "
+"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
+"screenfull or so of information about the hardware in your system. More "
+"information on this phase of the boot process can be found below in <xref "
+"linkend=\"kernel-msgs\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
-msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
+msgid ""
+"After booting from the boot floppy, the root floppy is requested. Insert the "
+"root floppy and press &enterkey;, and the contents are loaded into memory. "
+"The installer program <command>debian-installer</command> is automatically "
+"launched."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
-msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
+msgid ""
+"It could be that your Network Interface Card or Motherboard provides PXE "
+"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
+"re-implementation of TFTP boot. If so, you may be able to configure your "
+"BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
-msgid "It could be that your Network Interface Card provides TFTP boot functionality."
+msgid ""
+"It could be that your Network Interface Card provides TFTP boot "
+"functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
-msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
+msgid ""
+"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
+"Please refer to this document."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
-msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
+msgid ""
+"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
+"provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
-      "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
-      "Installer boot menu\n"
-      "\n"
-      "Install\n"
-      "Graphical install\n"
-      "Advanced options             >\n"
-      "Help\n"
-      "Install with speech synthesis\n"
-      "\n"
-      "Press ENTER to boot or TAB to edit a menu entry\n"
-      "</screen></informalexample> Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:658
+"When the installer boots, you should be presented with a friendly graphical "
+"screen showing the &debian; logo and a menu: <informalexample><screen>\n"
+"Installer boot menu\n"
+"\n"
+"Install\n"
+"Graphical install\n"
+"Advanced options             >\n"
+"Help\n"
+"Install with speech synthesis\n"
+"\n"
+"Press ENTER to boot or TAB to edit a menu entry\n"
+"</screen></informalexample> Depending on the installation method you are "
+"using, the <quote>Graphical install</quote> option may not be available. Bi-"
+"arch images additionally have a 64 bit variant for each install option, "
+"right below it, thus almost doubling the number of options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:660
 #, no-c-format
-msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
+msgid ""
+"For a normal installation, select either the <quote>Install</quote> or the "
+"<quote>Graphical install</quote> entry &mdash; using either the arrow keys "
+"on your keyboard or by typing the first (highlighted) letter, the "
+"<quote>Install</quote> entry is already selected by default &mdash; and "
+"press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
-msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
+msgid ""
+"The <quote>Advanced options</quote> entry gives access to a second menu that "
+"allows to boot the installer in expert mode, in rescue mode and for "
+"automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
-msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
+msgid ""
+"If you wish or need to add any boot parameters for either the installer or "
+"the kernel, press &tabkey;. This will display the default boot command for "
+"the selected menu entry and allow to add additional options. The help "
+"screens (see below) list some common possible options. Press &enterkey; to "
+"boot the installer with your options; pressing &escapekey; will return you "
+"to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
-      "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
-      "Press F1 for the help index, or ENTER to boot:\n"
-      "</screen></informalexample> At this boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot command and, optionally, boot parameters. A number of boot parameters which might be useful can be found on the various help screens. If you do add any parameters to the boot command line, be sure to first type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)."
+"Choosing the <quote>Help</quote> entry will result in the first help screen "
+"being displayed which gives an overview of all available help screens. To "
+"return to the boot menu after the help screens have been displayed, type "
+"'menu' at the boot prompt and press &enterkey;. All help screens have a boot "
+"prompt at which the boot command can be typed: <informalexample><screen>\n"
+"Press F1 for the help index, or ENTER to boot:\n"
+"</screen></informalexample> At this boot prompt you can either just press "
+"&enterkey; to boot the installer with default options or enter a specific "
+"boot command and, optionally, boot parameters. A number of boot parameters "
+"which might be useful can be found on the various help screens. If you do "
+"add any parameters to the boot command line, be sure to first type the boot "
+"method (the default is <userinput>install</userinput>) and a space before "
+"the first parameter (e.g., <userinput>install fb=false</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
-msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
+msgid ""
+"The keyboard is assumed to have a default American English layout at this "
+"point. This means that if your keyboard has a different (language-specific) "
+"layout, the characters that appear on the screen may be different from what "
+"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-"
+"keymap;\">schema of the US keyboard layout</ulink> which can be used as a "
+"reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
-msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
+msgid ""
+"If you are using a system that has the BIOS configured to use serial "
+"console, you may not be able to see the initial graphical splash screen upon "
+"booting the installer; you may even not see the boot menu. The same can "
+"happen if you are installing the system via a remote management device that "
+"provides a text interface to the VGA console. Examples of these devices "
+"include the text console of Compaq's <quote>integrated Lights Out</quote> "
+"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
-msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
+msgid ""
+"To bypass the graphical boot screen you can either blindly press &escapekey; "
+"to get a text boot prompt, or (equally blindly) press <quote>H</quote> "
+"followed by &enterkey; to select the <quote>Help</quote> option described "
+"above. After that your keystrokes should be echoed at the prompt. To prevent "
+"the installer from using the framebuffer for the rest of the installation, "
+"you will also want to add <userinput>vga=normal fb=false</userinput> to the "
+"boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
-msgid "There are three basic variations of &debian; Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a &debian; mirror site in order to install the extra packages one would want for a complete system . The set of &debian; CDs can install a complete system from the wide range of packages without needing access to the network."
+msgid ""
+"There are three basic variations of &debian; Install CDs. The "
+"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
+"fit on the small form factor CD media. It requires a network connection in "
+"order to install the rest of the base installation and make a usable system. "
+"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
+"base install but requires a network connection to a &debian; mirror site in "
+"order to install the extra packages one would want for a complete system . "
+"The set of &debian; CDs can install a complete system from the wide range of "
+"packages without needing access to the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
-msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
+msgid ""
+"The IA-64 architecture uses the next generation Extensible Firmware "
+"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows "
+"little about the boot device other than the partition table and Master Boot "
+"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted "
+"disk partitions. This simplifies the often arcane process of starting a "
+"system. The system boot loader and the EFI firmware that supports it have a "
+"full filesystem to store the files necessary for booting the machine. This "
+"means that the system disk on an IA-64 system has an additional disk "
+"partition dedicated to EFI instead of the simple MBR or boot block on more "
+"conventional systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
-msgid "The &debian; Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
+msgid ""
+"The &debian; Installer CD contains a small EFI partition where the "
+"<command>ELILO</command> bootloader, its configuration file, the installer's "
+"kernel, and initial filesystem (initrd) are located. The running system also "
+"contains an EFI partition where the necessary files for booting the system "
+"reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
-msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
+msgid ""
+"Most of the details of how <command>ELILO</command> actually loads and "
+"starts a system are transparent to the system installer. However, the "
+"installer must set up an EFI partition prior to installing the base system. "
+"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
+"the system un-bootable. The EFI partition is allocated and formatted in the "
+"partitioning step of the installation prior to loading any packages on the "
+"system disk. The partitioning task also verifies that a suitable EFI "
+"partition is present before allowing the installation to proceed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
-msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
+msgid ""
+"The EFI Boot Manager is presented as the last step of the firmware "
+"initialization. It displays a menu list from which the user can select an "
+"option. Depending on the model of system and what other software has been "
+"loaded on the system, this menu may be different from one system to another. "
+"There should be at least two menu items displayed, <command>Boot Option "
+"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
+"Using the first option is preferred, however, if that option is not "
+"available or the CD for some reason does not boot with it, use the second "
+"option."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
-msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
+msgid ""
+"The EFI Boot Manager will select a default boot action, typically the first "
+"menu choice, within a pre-set number of seconds. This is indicated by a "
+"countdown at the bottom of the screen. Once the timer expires and the "
+"systems starts the default action, you may have to reboot the machine in "
+"order to continue the installation. If the default action is the EFI Shell, "
+"you can return to the Boot Manager by running <command>exit</command> at the "
+"shell prompt."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes its system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
-msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
+msgid ""
+"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
+"keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
-msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
+msgid ""
+"Select <command>Boot From a File</command> from the menu with the arrow keys "
+"and press <command>ENTER</command>. This will display a list of devices "
+"probed by the firmware. You should see two menu lines containing either the "
+"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
+"Boot</command>. If you examine the rest of the menu line, you will notice "
+"that the device and controller information should be the same."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
-msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
+msgid ""
+"You can choose either of the entries that refer to the CD/DVD drive. Select "
+"your choice with the arrow keys and press <command>ENTER</command>. If you "
+"choose <command>Removable Media Boot</command> the machine will immediately "
+"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
+"command> instead, it will display a directory listing of the bootable "
+"portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
-msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
+"command>. The directory listing will also show <command>[Treat like "
+"Removable Media Boot]</command> on the next to the last line. Select this "
+"line with the arrow keys and press <command>ENTER</command>. This will start "
+"the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
-msgid "These steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
+msgid ""
+"These steps start the &debian; boot loader which will display a menu page "
+"for you to select a boot kernel and options. Proceed to selecting the boot "
+"kernel and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
-msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with the following steps:"
+msgid ""
+"If, for some reason, option 1 is not successful, reboot the machine and when "
+"the EFI Boot Manager screen appears there should be one option called "
+"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with "
+"the following steps:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
-msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
+msgid ""
+"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
+"display the EFI Boot Manager page and menu after it completes system "
+"initialization."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
-msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
+msgid ""
+"Select <command>EFI Shell</command> from the menu with the arrow keys and "
+"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
+"devices and display them to the console before displaying its command "
+"prompt. The recognized bootable partitions on devices will show a device "
+"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
+"recognized partitions will be named <filename>blk<replaceable>n</"
+"replaceable>:</filename>. If you inserted the CD just before entering the "
+"shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
-msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
+msgid ""
+"Examine the output from the shell looking for the CDROM drive. It is most "
+"likely the <filename>fs0:</filename> device although other devices with "
+"bootable partitions will also show up as <filename>fs<replaceable>n</"
+"replaceable></filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
-msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
+msgid ""
+"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
+"<command>ENTER</command> to select that device where <replaceable>n</"
+"replaceable> is the partition number for the CDROM. The shell will now "
+"display the partition number as its prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
-msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
+msgid ""
+"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
+"start the boot load sequence."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
-msgid "As with option 1, these steps start the &debian; boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
+msgid ""
+"As with option 1, these steps start the &debian; boot loader which will "
+"display a menu page for you to select a boot kernel and options. You can "
+"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
+"command> command at the shell prompt. Proceed to selecting the boot kernel "
+"and options."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
-msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
+msgid ""
+"You may choose to perform an install using a monitor and keyboard or using a "
+"serial connection. To use a monitor/keyboard setup, select an option "
+"containing the string [VGA console]. To install over a serial connection, "
+"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
+"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
+"serial console. Menu items for the most typical baud rate settings on the "
+"ttyS0 device are preconfigured."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
-msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
+msgid ""
+"In most circumstances, you will want the installer to use the same baud rate "
+"as your connection to the EFI console. If you aren't sure what this setting "
+"is, you can obtain it using the command <command>baud</command> at the EFI "
+"shell."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
-msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
+msgid ""
+"If there is not an option available that is configured for the serial device "
+"or baud rate you would like to use, you may override the console setting for "
+"one of the existing menu options. For example, to use a 57600 baud console "
+"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
+"the <classname>Boot:</classname> text window."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
-msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
+msgid ""
+"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
+"setting is rather slow, and the normal installation process will take a "
+"significant time to draw each screen. You should consider either increasing "
+"the baud rate used for performing the installation, or performing a Text "
+"Mode installation. See the <classname>Params</classname> help menu for "
+"instructions on starting the installer in Text Mode."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
-msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
+msgid ""
+"If you select the wrong console type, you will be able to select the kernel "
+"and enter parameters but both the display and your input will go dead as "
+"soon as the kernel starts, requiring you to reboot before you can begin the "
+"installation."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
-msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
+msgid ""
+"The boot loader will display a form with a menu list and a text window with "
+"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
+"the menu and any text typed at the keyboard will appear in the text window. "
+"There are also help screens which can be displayed by pressing the "
+"appropriate function key. The <classname>General</classname> help screen "
+"explains the menu choices and the <classname>Params</classname> screen "
+"explains the common command line options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
-msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
+msgid ""
+"Consult the <classname>General</classname> help screen for the description "
+"of the kernels and install modes most appropriate for your installation. You "
+"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
+"parameters that you may want to set in the <classname>Boot:</classname> text "
+"window. The kernel version you choose selects the kernel version that will "
+"be used for both the installation process and the installed system. If you "
+"encounter kernel problems with the installation, you may also have those "
+"same problems with the system you install. The following two steps will "
+"select and start the install:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
-msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
+msgid ""
+"Select the kernel version and installation mode most appropriate to your "
+"needs with the arrow keys."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
-msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
+msgid ""
+"Enter any boot parameters by typing at the keyboard. The text will be "
+"displayed directly in the text window. This is where kernel parameters (such "
+"as serial console settings) are specified."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
-msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the &debian; Installer."
+msgid ""
+"Press <command>ENTER</command>. This will load and start the kernel. The "
+"kernel will display its usual initialization messages followed by the first "
+"screen of the &debian; Installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
-msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
+msgid ""
+"Proceed to the next chapter to continue the installation where you will set "
+"up the language locale, network, and disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
-msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
+msgid ""
+"Booting an IA-64 system from the network is similar to a CD boot. The only "
+"difference is how the installation kernel is loaded. The EFI Boot Manager "
+"can load and start programs from a server on the network. Once the "
+"installation kernel is loaded and starts, the system install will proceed "
+"through the same steps as the CD install with the exception that the "
+"packages of the base install will be loaded from the network rather than the "
+"CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
-msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
+msgid ""
+"Network booting an IA-64 system requires two architecture-specific actions. "
+"On the boot server, DHCP and TFTP must be configured to deliver "
+"<command>elilo</command>. On the client a new boot option must be defined in "
+"the EFI boot manager to enable loading over a network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
-      "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
-      "host mcmuffin {\n"
-      "        hardware ethernet 00:30:6e:1e:0e:83;\n"
-      "        fixed-address 10.0.0.21;\n"
-      "        filename \"debian-installer/ia64/elilo.efi\";\n"
-      "}\n"
-      "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
+"A suitable TFTP entry for network booting an IA-64 system looks something "
+"like this: <informalexample><screen>\n"
+"host mcmuffin {\n"
+"        hardware ethernet 00:30:6e:1e:0e:83;\n"
+"        fixed-address 10.0.0.21;\n"
+"        filename \"debian-installer/ia64/elilo.efi\";\n"
+"}\n"
+"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
+"command> running on the client."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
-msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
+msgid ""
+"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
+"as the root for your tftp server. Typical tftp root directories include "
+"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
+"will create a <filename>debian-installer</filename> directory tree "
+"containing the boot files for an IA-64 system."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
-      "# cd /var/lib/tftp\n"
-      "# tar xvfz /home/user/netboot.tar.gz\n"
-      "./\n"
-      "./debian-installer/\n"
-      "./debian-installer/ia64/\n"
-      "[...]"
+"# cd /var/lib/tftp\n"
+"# tar xvfz /home/user/netboot.tar.gz\n"
+"./\n"
+"./debian-installer/\n"
+"./debian-installer/ia64/\n"
+"[...]"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
-msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
+msgid ""
+"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
+"filename> file that should work for most configurations. However, should you "
+"need to make changes to this file, you can find it in the <filename>debian-"
+"installer/ia64/</filename> directory. It is possible to have different "
+"config files for different clients by naming them using the client's IP "
+"address in hex with the suffix <filename>.conf</filename> instead of "
+"<filename>elilo.conf</filename>. See documentation provided in the "
+"<classname>elilo</classname> package for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
-msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
+msgid ""
+"To configure the client to support TFTP booting, start by booting to EFI and "
+"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
+"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
+"should see one or more lines with the text <guimenuitem>Load File [Acpi"
+"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose "
+"the one containing the MAC address of the interface from which you'll be "
+"booting. Use the arrow keys to highlight your choice, then press enter. </"
+"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
+"userinput> or something similar, save, and exit back to the boot options "
+"menu. </para></listitem> </itemizedlist> You should see the new boot option "
+"you just created, and selecting it should initiate a DHCP query, leading to "
+"a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
-msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the &debian; Installer."
+msgid ""
+"The boot loader will display its prompt after it has downloaded and "
+"processed its configuration file. At this point, the installation proceeds "
+"with the same steps as a CD install. Select a boot option as in above and "
+"when the kernel has completed installing itself from the network, it will "
+"start the &debian; Installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
-      "After entering the command monitor use <informalexample><screen>\n"
-      "bootp():\n"
-      "</screen></informalexample> on SGI machines to boot linux and to begin installation of the &debian; Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n"
-      "unsetenv netaddr\n"
-      "</screen></informalexample> in the command monitor to do this."
+"After entering the command monitor use <informalexample><screen>\n"
+"bootp():\n"
+"</screen></informalexample> on SGI machines to boot linux and to begin "
+"installation of the &debian; Software. In order to make this work you may "
+"have to unset the <envar>netaddr</envar> environment variable. Type "
+"<informalexample><screen>\n"
+"unsetenv netaddr\n"
+"</screen></informalexample> in the command monitor to do this."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
-msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
+msgid ""
+"On SGI machines you can append boot parameters to the <command>bootp():</"
+"command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
-      "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n"
-      "bootp():/boot/tftpboot.img\n"
-      "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
+"Following the <command>bootp():</command> command you can give the path and "
+"name of the file to boot if you did not give an explicit name via your bootp/"
+"dhcp server. Example: <informalexample><screen>\n"
+"bootp():/boot/tftpboot.img\n"
+"</screen></informalexample> Further kernel parameters can be passed via "
+"<command>append</command>:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
-msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
+msgid ""
+"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
+"install an NFS server and put the installer files in <filename>/nfsroot</"
+"filename>. When you boot your Cobalt, you have to press the left and the "
+"right cursor buttons at the same time and the machine will boot via the "
+"network from NFS. It will then display several options on the display. There "
+"are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
-msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
+msgid ""
+"Via SSH (default): In this case, the installer will configure the network "
+"via DHCP and start an SSH server. It will then display a random password and "
+"other login information (such as the IP address) on the Cobalt LCD. When you "
+"connect to the machine with an SSH client you can start with the "
+"installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
-msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way."
+msgid ""
+"Via serial console: Using a null modem cable, you can connect to the serial "
+"port of your Cobalt machine (using 115200 bps) and perform the installation "
+"this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
-msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
+msgid ""
+"You cannot pass any boot parameters directly. Instead, you have to edit the "
+"<filename>/nfsroot/default.colo</filename> file on the NFS server and add "
+"your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
-msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
+msgid ""
+"In order to run the installation system a working network setup and ssh "
+"session is needed on S/390."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
-msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
+msgid ""
+"The booting process starts with a network setup that prompts you for several "
+"network parameters. If the setup is successful, you will login to the system "
+"by starting an ssh session which will launch the standard installation "
+"system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
-msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
+msgid ""
+"On S/390 you can append boot parameters in the parm file. This file can "
+"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
+"debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
-msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive."
+msgid ""
+"Currently, the only &arch-title; subarchitectures that support CD-ROM "
+"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
+"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
+"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
+"and <keycap>Delete</keycap> keys together while booting to boot from the "
+"factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
-      "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
-      "0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
-      "</screen></informalexample> for an alternative way to boot from the internal factory default CD/DVD drive type"
+"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
+"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
+"type <informalexample><screen>\n"
+"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
+"</screen></informalexample> for an alternative way to boot from the internal "
+"factory default CD/DVD drive type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
-msgid "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
+msgid ""
+"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
+"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
+"software version of this driver is not available. All OldWorld systems have "
+"floppy drives, so use the floppy drive to launch the installer, and then "
+"point the installer to the CD for the needed files."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
-msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
+msgid ""
+"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
+"immediately after pressing the power-on button, when SmartFirmware prompt "
+"appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
-msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
+msgid ""
+"Booting from an existing operating system is often a convenient option; for "
+"some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
-msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
+msgid ""
+"To boot the installer from hard disk, you will have already completed "
+"downloading and placing the needed files as described in <xref linkend="
+"\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
-msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
+msgid ""
+"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
+"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
+"application icon. Click on the <guibutton>Options</guibutton> button and "
+"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
+"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
+"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
+"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
+"down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
-      "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
-      "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
-      "</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n"
-      "boot:\n"
-      "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The &debian; installation program should start."
+"You will have already placed the <filename>vmlinux</filename>, "
+"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
+"<filename>yaboot.conf</filename> files at the root level of your HFS "
+"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
+"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
+"prompt, type <informalexample><screen>\n"
+"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
+"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
+"partition number of the HFS partition where the kernel and yaboot files were "
+"placed, followed by a &enterkey;. On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
+"more seconds you will see a yaboot prompt <informalexample><screen>\n"
+"boot:\n"
+"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
+"either <userinput>install</userinput> or <userinput>install video=ofonly</"
+"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
+"argument is for maximum compatibility; you can try it if <userinput>install</"
+"userinput> doesn't work. The &debian; installation program should start."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
-msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
+msgid ""
+"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
+">. To boot a Macintosh system from a USB stick, you will need to use the "
+"Open Firmware prompt, since Open Firmware does not search USB storage "
+"devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
-msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
+msgid ""
+"You will need to work out where the USB storage device appears in the device "
+"tree, since at the moment <command>ofpath</command> cannot work that out "
+"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
+"userinput> at the Open Firmware prompt to get a list of all known devices "
+"and device aliases. On the author's system with various types of USB stick, "
+"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
+"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
+"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
-      "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
-      "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n"
-      "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
+"Having worked out the device path, use a command like this to boot the "
+"installer: <informalexample><screen>\n"
+"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
+"tbxi\n"
+"</screen></informalexample> The <replaceable>2</replaceable> matches the "
+"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
+"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
+"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
+"<command>yaboot</command>) in the directory previously blessed with "
+"<command>hattrib -b</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
-msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
+msgid ""
+"The system should now boot up, and you should be presented with the "
+"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
+"or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
-msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
+msgid ""
+"This boot method is new, and may be difficult to get to work on some "
+"NewWorld systems. If you have problems, please file an installation report, "
+"as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
-      "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
-      "0 &gt; boot enet:0\n"
-      "</screen></informalexample> If this doesn't work, you might have to add the filename like this: <informalexample><screen>\n"
-      "0 &gt; boot enet:0,yaboot\n"
-      "</screen></informalexample> PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <informalexample><screen>\n"
-      "boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>\n"
-      "</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
-msgstr ""
-
-#. Tag: para
-#: boot-installer.xml:1676
+"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
+"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
+"<informalexample><screen>\n"
+"0 &gt; boot enet:0\n"
+"</screen></informalexample> If this doesn't work, you might have to add the "
+"filename like this: <informalexample><screen>\n"
+"0 &gt; boot enet:0,yaboot\n"
+"</screen></informalexample> PReP and CHRP boxes may have different ways of "
+"addressing the network. On a PReP machine, you should try "
+"<informalexample><screen>\n"
+"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
+"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
+"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
+"machines) the command <userinput>help boot</userinput> may give a "
+"description of syntax and available options."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:1678
 #, no-c-format
-msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
+msgid ""
+"Booting from floppies is supported for &arch-title;, although it is "
+"generally only applicable for OldWorld systems. NewWorld systems are not "
+"equipped with floppy drives, and attached USB floppy drives are not "
+"supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
-msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
+msgid ""
+"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
+"in floppy drive after shutting the system down, and before pressing the "
+"power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
-msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
+msgid ""
+"For those not familiar with Macintosh floppy operations: a floppy placed in "
+"the machine prior to boot will be the first priority for the system to boot "
+"from. A floppy without a valid boot system will be ejected, and the machine "
+"will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
-msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
+msgid ""
+"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
+"the root floppy and press &enterkey;. The installer program is automatically "
+"launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
-msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
+msgid ""
+"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
+"skewed on an older Apple monitor, try appending the boot argument "
+"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
+"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
+"<userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
-msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
+msgid ""
+"On machines with OpenBoot, simply enter the boot monitor on the machine "
+"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
+"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
+"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
+"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
+"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
-msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
+msgid ""
+"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
+"which is simply an alias to boot from the SCSI device on ID 6 (or the "
+"secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
-msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
+msgid ""
+"If you cannot boot because you get messages about a problem with "
+"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
+"holds configuration information for you firmware, has run out. See the "
+"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
+"information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
-msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
+msgid ""
+"Some users may need specific support because of e.g. some visual impairment. "
+"<phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected "
+"automatically (not serial displays connected via a serial-to-USB converter), "
+"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</"
+"phrase> accessibility features have to be enabled manually. <phrase arch="
+"\"x86\">On machines that support it, the boot menu emits a beep when it is "
+"ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch="
+"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
+"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that "
+"on most architectures the boot loader interprets your keyboard as a QWERTY "
+"keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
-msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"USB braille displays should be automatically detected. A textual version of "
+"the installer will then be automatically selected, and support for the "
+"braille display will be automatically installed on the target system. You "
+"can thus just press &enterkey; at the boot menu. Once <classname>brltty</"
+"classname> is started, you can choose a braille table by entering the "
+"preference menu. Documentation on key bindings for braille devices is "
+"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
+"classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
-msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
+msgid ""
+"Serial braille displays cannot safely be automatically detected (since that "
+"may damage some of them). You thus need to append the "
+"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
+"replaceable>,<replaceable>table</replaceable></userinput> boot parameter to "
+"tell <classname>brltty</classname> which driver it should use. "
+"<replaceable>driver</replaceable> should be replaced by the two-letter "
+"driver code for your terminal (see the <ulink url=\"&url-brltty-manual;"
+"\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be "
+"replaced by the name of the serial port the display is connected to, "
+"<userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> "
+"can be typically used when using a serial-to-USB converter. "
+"<replaceable>table</replaceable> is the name of the braille table to be used "
+"(see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the "
+"English table is the default. Note that the table can be changed later by "
+"entering the preference menu. Documentation on key bindings for braille "
+"devices is available on the <ulink url=\"&url-brltty-driver-help;"
+"\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
-msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
+msgid ""
+"Support for software speech synthesis can be activated by selecting it in "
+"the boot menu by typing <userinput>s</userinput> &enterkey;. The first "
+"question (language) is spoken in english, and the remainder of installation "
+"is spoken in the selected language (if available in <classname>espeak</"
+"classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
+msgid ""
+"Support for hardware speech synthesis devices is available only alongside "
+"support for graphical installer. You thus need to select a <quote>Graphical "
+"install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
-msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
+msgid ""
+"Hardware speech synthesis devices cannot be automatically detected. You thus "
+"need to append the <userinput>speakup.synth=<replaceable>driver</"
+"replaceable></userinput> boot parameter to tell <classname>speakup</"
+"classname> which driver it should use. <replaceable>driver</replaceable> "
+"should be replaced by the driver code for your device (see <ulink url=\"&url-"
+"speakup-driver-codes;\">driver code list</ulink>). The textual version of "
+"the installer will then be automatically selected, and support for the "
+"speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
-msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
+msgid ""
+"Some accessibility devices are actual boards that are plugged inside the "
+"machine and that read text directly from the video memory. To get them to "
+"work framebuffer support must be disabled by using the <userinput arch="
+"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot "
+"parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
-msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
+msgid ""
+"If desired a textual version of the bootloader can be activated before "
+"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
-msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
+msgid ""
+"For users with low vision, the installer can use a high-contrast theme that "
+"makes it more readable. To enable it, append the <userinput>theme=dark</"
+"userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
-msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Alternatively, &debian; can be installed completely automatically by using "
+"preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
-msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
+msgid ""
+"Boot parameters are Linux kernel parameters which are generally used to make "
+"sure that peripherals are dealt with properly. For the most part, the kernel "
+"can auto-detect information about your peripherals. However, in some cases "
+"you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
-msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
+msgid ""
+"If this is the first time you're booting the system, try the default boot "
+"parameters (i.e., don't try setting parameters) and see if it works "
+"correctly. It probably will. If not, you can reboot later and look for any "
+"special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
-msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
+msgid ""
+"Information on many boot parameters can be found in the <ulink url=\"http://"
+"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
+"including tips for obscure hardware. This section contains only a sketch of "
+"the most salient parameters. Some common gotchas are included below in <xref "
+"linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, no-c-format
-msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
+msgid ""
+"If you are booting with a serial console, generally the kernel will "
+"autodetect this. If you have a videocard (framebuffer) and a keyboard also "
+"attached to the computer which you wish to boot via serial console, you may "
+"have to pass the <userinput>console=<replaceable>device</replaceable></"
+"userinput> argument to the kernel, where <replaceable>device</replaceable> "
+"is your serial device, which is usually something like <filename>ttyS0</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, no-c-format
-msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
+msgid ""
+"In order to ensure the terminal type used by the installer matches your "
+"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
+"replaceable></userinput> can be added. Note that the installer only supports "
+"the following terminal types: <literal>linux</literal>, <literal>bterm</"
+"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
+"<literal>dumb</literal>. The default for serial console in &d-i; is "
+"<userinput>vt102</userinput>. If you are using a virtualization tool which "
+"does not provide conversion into such terminals types itself, e.g. QEMU/KVM, "
+"you can start it inside a <command>screen</command> session. That will "
+"indeed perform translation into the <literal>screen</literal> terminal type, "
+"which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
-msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
+msgid ""
+"For &arch-title; the serial devices are <filename>ttya</filename> or "
+"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
+"envar> and <envar>output-device</envar> OpenPROM variables to "
+"<filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
+msgid ""
+"The installation system recognizes a few additional boot "
+"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
+"use 32 command line options and 32 environment options. If these numbers are "
+"exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
-msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
+msgid ""
+"A number of parameters have a <quote>short form</quote> that helps avoid the "
+"limitations of the kernel command line options and makes entering the "
+"parameters easier. If a parameter has a short form, it will be listed in "
+"brackets behind the (normal) long form. Examples in this manual will "
+"normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
-msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
+msgid ""
+"The default installation uses <userinput>priority=high</userinput>. This "
+"means that both high and critical priority messages are shown, but medium "
+"and low priority messages are skipped. If problems are encountered, the "
+"installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
-msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
+msgid ""
+"If you add <userinput>priority=medium</userinput> as boot parameter, you "
+"will be shown the installation menu and gain more control over the "
+"installation. When <userinput>priority=low</userinput> is used, all messages "
+"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
+"method). With <userinput>priority=critical</userinput>, the installation "
+"system will display only critical messages and try to do the right thing "
+"without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
-msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
+msgid ""
+"This boot parameter controls the type of user interface used for the "
+"installer. The current possible parameter settings are: <itemizedlist> "
+"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
+"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
+"userinput></para> </listitem><listitem> "
+"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
+"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
+"</listitem> </itemizedlist> The default frontend is "
+"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
+"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
+"console installs. Some specialized types of install media may only offer a "
+"limited selection of frontends, but the <userinput>newt</userinput> and "
+"<userinput>text</userinput> frontends are available on most default install "
+"media. On architectures that support it, the graphical installer uses the "
+"<userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
-msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
+msgid ""
+"Setting this boot parameter to 2 will cause the installer's boot process to "
+"be verbosely logged. Setting it to 3 makes debug shells available at "
+"strategic points in the boot process. (Exit the shells to continue the boot "
+"process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
-msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
+msgid ""
+"Shells are run at various points in the boot process to allow detailed "
+"debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
-msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
+msgid ""
+"The value of the parameter is the path to the device to load the &debian; "
+"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
+"userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
-msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
+msgid ""
+"The boot floppy, which normally scans all floppies it can to find the root "
+"floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
-msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
+msgid ""
+"Causes the installer to send log messages to a remote syslog on the "
+"specified host and port as well as to a local file. If not specified, the "
+"port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
-msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
+msgid ""
+"Can be used to force the installer to a lowmem level higher than the one the "
+"installer sets by default based on available memory. Possible values are 1 "
+"and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
-msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
+msgid ""
+"Prevents the installer from offering interactive shells on tty2 and tty3. "
+"Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
-msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
+msgid ""
+"Some architectures use the kernel framebuffer to offer installation in a "
+"number of languages. If framebuffer causes a problem on your system you can "
+"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</"
+"userinput> <userinput>fb=false</userinput>. Problem symptoms are error "
+"messages about bterm or bogl, a blank screen, or a freeze within a few "
+"minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
-msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
+msgid ""
+"Because of display problems on some systems, framebuffer support is "
+"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
+"in ugly display on systems that do properly support the framebuffer, like "
+"those with ATI graphical cards. If you see display problems in the "
+"installer, you can try booting with parameter <userinput>debian-installer/"
+"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
-msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
+msgid ""
+"A theme determines how the user interface of the installer looks (colors, "
+"icons, etc.). What themes are available differs per frontend. Currently both "
+"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
+"designed for visually impaired users. Set the theme by booting with "
+"<userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
-msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
+msgid ""
+"By default, the &d-i; automatically probes for network configuration via "
+"DHCP. If the probe succeeds, you won't have a chance to review and change "
+"the obtained settings. You can get to the manual network setup only in case "
+"the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
-msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
+msgid ""
+"If you have a DHCP server on your local network, but want to avoid it "
+"because e.g. it gives wrong answers, you can use the parameter "
+"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
+"network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
+msgid ""
+"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
+"that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
+msgid ""
+"Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
+"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note "
+"that this support is currently experimental. Additional information can be "
+"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
-msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the url to a preconfiguration file to download and use for "
+"automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
-msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
+msgid ""
+"Specify the path to a preconfiguration file to load for automating the "
+"install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
+msgid ""
+"Set to <userinput>true</userinput> to display questions even if they have "
+"been preseeded. Can be useful for testing or debugging a preconfiguration "
+"file. Note that this will have no effect on parameters that are passed as "
+"boot parameters, but for those a special syntax can be used. See <xref "
+"linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
-msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
+msgid ""
+"Delay questions that are normally asked before preseeding is possible until "
+"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
+"details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
-msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
+msgid ""
+"During installations from serial or management console, the regular virtual "
+"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
+"filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
-msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
+msgid ""
+"By default, before rebooting, &d-i; automatically ejects the optical media "
+"used during the installation. This can be unnecessary if the system does not "
+"automatically boot off the CD. In some cases it may even be undesirable, for "
+"example if the optical drive cannot reinsert the media itself and the user "
+"is not there to do it manually. Many slot loading, slim-line, and caddy "
+"style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
-msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
+msgid ""
+"Set to <userinput>false</userinput> to disable automatic ejection, and be "
+"aware that you may need to ensure that the system does not automatically "
+"boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
-msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
+msgid ""
+"By setting this option to <userinput>false</userinput>, the package "
+"management system will be configured to not automatically install "
+"<quote>Recommends</quote>, both during the installation and for the "
+"installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
-msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
+msgid ""
+"Note that this option allows to have a leaner system, but can also result in "
+"features being missing that you might normally expect to be available. You "
+"may have to manually install some of the recommended packages to obtain the "
+"full functionality you want. This option should therefore only be used by "
+"very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
-msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
+msgid ""
+"By default the installer requires that repositories be authenticated using a "
+"known gpg key. Set to <userinput>true</userinput> to disable that "
+"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
+"emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
-msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
+msgid ""
+"This parameter should already be set to a correct value where needed; set it "
+"only it you see errors during the boot that indicate the ramdisk could not "
+"be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
-msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
+msgid ""
+"Set to <userinput>true</userinput> to enter rescue mode rather than "
+"performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
-msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
+msgid ""
+"With some exceptions, a value can be set at the boot prompt for any question "
+"asked during the installation, though this is only really useful in specific "
+"cases. General instructions how to do this can be found in <xref linkend="
+"\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
-msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
+msgid ""
+"There are two ways to specify the language, country and locale to use for "
+"the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
-msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
+msgid ""
+"The first and easiest is to pass only the parameter <literal>locale</"
+"literal>. Language and country will then be derived from its value. You can "
+"for example use <userinput>locale=de_CH</userinput> to select German as "
+"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be "
+"set as default locale for the installed system). Limitation is that not all "
+"possible combinations of language, country and locale can be achieved this "
+"way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
-msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
+msgid ""
+"The second, more flexible option is to specify <literal>language</literal> "
+"and <literal>country</literal> separately. In this case <literal>locale</"
+"literal> can optionally be added to specify a specific default locale for "
+"the installed system. Example: <userinput>language=en country=DE "
+"locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
-msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
+msgid ""
+"Can be used to automatically load installer components that are not loaded "
+"by default. Examples of optional components that may be useful are "
+"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
+"command> during the installation)<phrase arch=\"not-s390\"> and "
+"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
-msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
+msgid ""
+"Set to <userinput>true</userinput> if you want to disable DHCP and instead "
+"force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
-msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
+msgid ""
+"By default the installer will use the http protocol to download files from "
+"&debian; mirrors and changing that to ftp is not possible during "
+"installations at normal priority. By setting this parameter to "
+"<userinput>ftp</userinput>, you can force the installer to use that protocol "
+"instead. Note that you cannot select an ftp mirror from a list, you have to "
+"enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
-msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
+msgid ""
+"Can be used to select tasks that are not available from the interactive task "
+"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
+"\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
-msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
+msgid ""
+"If drivers are compiled into the kernel, you can pass parameters to them as "
+"described in the kernel documentation. However, if drivers are compiled as "
+"modules and because kernel modules are loaded a bit differently during an "
+"installation than when booting an installed system, it is not possible to "
+"pass parameters to modules as you would normally do. Instead, you need to "
+"use a special syntax recognized by the installer which will then make sure "
+"that the parameters are saved in the proper configuration files and will "
+"thus be used when the modules are actually loaded. The parameters will also "
+"be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
-msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
+msgid ""
+"Note that it is now quite rare that parameters need to be passed to modules. "
+"In most cases the kernel will be able to probe the hardware present in a "
+"system and set good defaults that way. However, in some situations it may "
+"still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
-      "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
-      "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n"
-      "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:"
+"The syntax to use to set parameters for modules is: "
+"<informalexample><screen>\n"
+"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
+"replaceable>=<replaceable>value</replaceable>\n"
+"</screen></informalexample> If you need to pass multiple parameters to the "
+"same or different modules, just repeat this. For example, to set an old 3Com "
+"network interface card to use the BNC (coax) connector and IRQ 10, you would "
+"pass:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
-msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
+msgid ""
+"Sometimes it may be necessary to blacklist a module to prevent it from being "
+"loaded automatically by the kernel and udev. One reason could be that a "
+"particular module causes problems with your hardware. The kernel also "
+"sometimes lists two different drivers for the same device. This can cause "
+"the device to not work correctly if the drivers conflict or if the wrong "
+"driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
-msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
+msgid ""
+"You can blacklist a module using the following syntax: "
+"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
+"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
+"blacklist.local</filename> both during the installation and for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
-msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
+msgid ""
+"Note that a module may still be loaded by the installation system itself. "
+"You can prevent that from happening by running the installation in expert "
+"mode and unselecting the module from the list of modules displayed during "
+"the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
-msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
+msgid ""
+"Sometimes, especially with older CD-ROM drives, the installer may fail to "
+"boot from a CD-ROM. The installer may also &mdash; even after booting "
+"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
+"errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
-msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
+msgid ""
+"There are many different possible causes for these problems. We can only "
+"list some common issues and provide general suggestions on how to deal with "
+"them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
-msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
+msgid ""
+"If the CD-ROM does not boot, check that it was inserted correctly and that "
+"it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
-msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
+msgid ""
+"If the installer fails to recognize a CD-ROM, try just running the option "
+"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
+"menuchoice> a second time. Some DMA related issues with very old CD-ROM "
+"drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
-msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
+msgid ""
+"If this does not work, then try the suggestions in the subsections below. "
+"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
+"DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
-msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
+msgid ""
+"If you cannot get the installation working from CD-ROM, try one of the other "
+"installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
-msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
+msgid ""
+"Some older CD-ROM drives do not support reading from discs that were burned "
+"at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
-msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
+msgid ""
+"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
+"access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
-msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
+msgid ""
+"Check that your BIOS actually supports booting from CD-ROM (only an issue "
+"for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
-      "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
-      "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
-      "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM."
+"If you downloaded an iso image, check that the md5sum of that image matches "
+"the one listed for the image in the <filename>MD5SUMS</filename> file that "
+"should be present in the same location as where you downloaded the image "
+"from. <informalexample><screen>\n"
+"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
+"iso</replaceable>\n"
+"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
+"matches as well. The following command should work. It uses the size of the "
+"image to read the correct number of bytes from the CD-ROM."
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
-      "$ dd if=/dev/cdrom | \\\n"
-      "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n"
-      "> md5sum\n"
-      "a20391b12f7ff22ef705cee4059c6b92  -\n"
-      "262668+0 records in\n"
-      "262668+0 records out\n"
-      "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
+"$ dd if=/dev/cdrom | \\\n"
+"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
+"replaceable>` | \\\n"
+"> md5sum\n"
+"a20391b12f7ff22ef705cee4059c6b92  -\n"
+"262668+0 records in\n"
+"262668+0 records out\n"
+"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
-msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
+msgid ""
+"If, after the installer has been booted successfully, the CD-ROM is not "
+"detected, sometimes simply trying again may solve the problem. If you have "
+"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
+"that does not work or if the CD-ROM is recognized but there are errors when "
+"reading from it, try the suggestions listed below. Some basic knowledge of "
+"&arch-kernel; is required for this. To execute any of the commands, you "
+"should first switch to the second virtual console (VT2) and activate the "
+"shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
-msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
+msgid ""
+"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
+"(use <command>nano</command> as editor) to check for any specific error "
+"messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
-      "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
-      "Probing IDE interface ide1...\n"
-      "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
-      "ide1 at 0x170-0x177,0x376 on irq 15\n"
-      "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
-      "Uniform CD-ROM driver Revision: 3.20\n"
-      "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using <command>modprobe</command>."
+"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
+"recognized. You should see something like (the lines do not necessarily have "
+"to be consecutive): <informalexample><screen>\n"
+"Probing IDE interface ide1...\n"
+"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
+"ide1 at 0x170-0x177,0x376 on irq 15\n"
+"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
+"Uniform CD-ROM driver Revision: 3.20\n"
+"</screen></informalexample> If you don't see something like that, chances "
+"are the controller your CD-ROM is connected to was not recognized or may be "
+"not supported at all. If you know what driver is needed for the controller, "
+"you can try loading it manually using <command>modprobe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
-msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
+msgid ""
+"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
+"</filename>. In the example above, this would be <filename>/dev/hdc</"
+"filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
-      "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
-      "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
-      "</screen></informalexample> Check if there are any error messages after that command."
+"Use the <command>mount</command> command to check if the CD-ROM is already "
+"mounted; if not, try mounting it manually: <informalexample><screen>\n"
+"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
+"</screen></informalexample> Check if there are any error messages after that "
+"command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
-      "Check if DMA is currently enabled: <informalexample><screen>\n"
-      "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
-      "$ grep using_dma settings\n"
-      "using_dma      1       0       1       rw\n"
-      "</screen></informalexample> A <quote>1</quote> in the first column after <literal>using_dma</literal> means it is enabled. If it is, try disabling it: <informalexample><screen>\n"
-      "$ echo -n \"using_dma:0\" >settings\n"
-      "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive."
+"Check if DMA is currently enabled: <informalexample><screen>\n"
+"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
+"$ grep using_dma settings\n"
+"using_dma      1       0       1       rw\n"
+"</screen></informalexample> A <quote>1</quote> in the first column after "
+"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
+"it: <informalexample><screen>\n"
+"$ echo -n \"using_dma:0\" >settings\n"
+"</screen></informalexample> Make sure that you are in the directory for the "
+"device that corresponds to your CD-ROM drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
-msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
+msgid ""
+"If there are any problems during the installation, try checking the "
+"integrity of the CD-ROM using the option near the bottom of the installer's "
+"main menu. This option can also be used as a general test if the CD-ROM can "
+"be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
-msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
+msgid ""
+"The biggest problem for people using floppy disks to install &debian; seems "
+"to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
-msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
+msgid ""
+"The boot floppy is the floppy with the worst problems, because it is read by "
+"the hardware directly, before Linux boots. Often, the hardware doesn't read "
+"as reliably as the Linux floppy disk driver, and may just stop without "
+"printing an error message if it reads incorrect data. There can also be "
+"failures in the driver floppies, most of which indicate themselves with a "
+"flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
-msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
+msgid ""
+"If you are having the installation stall at a particular floppy, the first "
+"thing you should do is write the image to a <emphasis>different</emphasis> "
+"floppy and see if that solves the problem. Simply reformatting the old "
+"floppy may not be sufficient, even if it appears that the floppy was "
+"reformatted and written with no errors. It is sometimes useful to try "
+"writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
-msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
+msgid ""
+"One user reports he had to write the images to floppy <emphasis>three</"
+"emphasis> times before one worked, and then everything was fine with the "
+"third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
-msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
+msgid ""
+"Normally you should not have to download a floppy image again, but if you "
+"are experiencing problems it is always useful to verify that the images were "
+"downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
-msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
+msgid ""
+"Other users have reported that simply rebooting a few times with the same "
+"floppy in the floppy drive can lead to a successful boot. This is all due to "
+"buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
-msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
+msgid ""
+"If you have problems and the kernel hangs during the boot process, doesn't "
+"recognize peripherals you actually have, or drives are not recognized "
+"properly, the first thing to check is the boot parameters, as discussed in "
+"<xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
-msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
+msgid ""
+"In some cases, malfunctions can be caused by missing device firmware (see "
+"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
+">)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
-msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
+msgid ""
+"If software speech synthesis does not work, there is most probably an issue "
+"with your sound board, usually because either the driver for it is not "
+"included in the installer, or because it has unusual mixer level names which "
+"are set to muted by default. You should thus submit a bug report which "
+"includes the output of the following commands, run on the same machine from "
+"a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
-msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
+msgid ""
+"There are some common installation problems that can be solved or avoided by "
+"passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
-msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
+msgid ""
+"If your screen begins to show a weird picture while the kernel boots, eg. "
+"pure white, pure black or colored pixel garbage, your system may contain a "
+"problematic video card which does not switch to the framebuffer mode "
+"properly. Then you can use the boot parameter <userinput>fb=false</"
+"userinput> to disable the framebuffer console. Only a reduced set of "
+"languages will be available during the installation due to limited console "
+"features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, no-c-format
-msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
+msgid ""
+"Some very old laptop models produced by Dell are known to crash when PCMCIA "
+"device detection tries to access some hardware addresses. Other laptops may "
+"display similar problems. If you experience such a problem and you don't "
+"need PCMCIA support during the installation, you can disable PCMCIA using "
+"the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
+"can then configure PCMCIA after the installation is completed and exclude "
+"the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
-msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
+msgid ""
+"Alternatively, you can boot the installer in expert mode. You will then be "
+"asked to enter the resource range options your hardware needs. For example, "
+"if you have one of the Dell laptops mentioned above, you should enter "
+"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
+"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
+"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
+"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
+"commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
-      "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
-      "Remapping the kernel... done\n"
-      "Booting Linux...\n"
-      "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>."
+"It is fairly common for &arch-title; to have two video cards in one machine, "
+"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
+"in the video output getting misdirected soon after the system boots. In "
+"typical cases, the display will only show: <informalexample><screen>\n"
+"Remapping the kernel... done\n"
+"Booting Linux...\n"
+"</screen></informalexample> To work around this, you can either pull out one "
+"of the video cards, or disable the one not used during the OpenProm boot "
+"phase using a kernel parameter. For example, to disable an ATI card, you "
+"should boot the installer with <userinput>video=atyfb:off</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
-msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"Note that you may also have to manually add this parameter to the silo "
+"configuration (edit <filename>/target/etc/silo.conf</filename> before "
+"rebooting) and, if you installed X11, modify the video driver in <filename>/"
+"etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
-msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
+msgid ""
+"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
+"they do boot, there may be inexplicable failures during the installation. "
+"Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
-msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
+msgid ""
+"During the boot sequence, you may see many messages in the form "
+"<computeroutput>can't find <replaceable>something</replaceable></"
+"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
+"present</computeroutput>, <computeroutput>can't initialize "
+"<replaceable>something</replaceable></computeroutput>, or even "
+"<computeroutput>this driver release depends on <replaceable>something</"
+"replaceable></computeroutput>. Most of these messages are harmless. You see "
+"them because the kernel for the installation system is built to run on "
+"computers with many different peripheral devices. Obviously, no one computer "
+"will have every possible peripheral device, so the operating system may emit "
+"a few complaints while it looks for peripherals you don't own. You may also "
+"see the system pause for a while. This happens when it is waiting for a "
+"device to respond, and that device is not present on your system. If you "
+"find the time it takes to boot the system unacceptably long, you can create "
+"a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
+"baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
-msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
+msgid ""
+"If you get through the initial boot phase but cannot complete the install, "
+"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
+"It lets you store system error logs and configuration information from the "
+"installer to a floppy, or download them using a web browser. This "
+"information may provide clues as to what went wrong and how to fix it. If "
+"you are submitting a bug report, you may want to attach this information to "
+"the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
-msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"Other pertinent installation messages may be found in <filename>/var/log/</"
+"filename> during the installation, and <filename>/var/log/installer/</"
+"filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
-msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
+msgid ""
+"If you still have problems, please submit an installation report. We also "
+"encourage installation reports to be sent even if the installation is "
+"successful, so that we can get as much information as possible on the "
+"largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
-msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
+msgid ""
+"Note that your installation report will be published in the Debian Bug "
+"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
+"you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
-msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
+msgid ""
+"If you have a working &debian; system, the easiest way to send an "
+"installation report is to install the <classname>installation-report</"
+"classname> and <classname>reportbug</classname> packages (<command>aptitude "
+"install installation-report reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run the command <command>reportbug installation-reports</"
+"command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
-      "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
-      "Package: installation-reports\n"
-      "\n"
-      "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
-      "Image version: &lt;Full URL to image you downloaded is best&gt;\n"
-      "Date: &lt;Date and time of the install&gt;\n"
-      "\n"
-      "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
-      "Processor:\n"
-      "Memory:\n"
-      "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
-      "\n"
-      "Output of lspci -knn (or lspci -nn):\n"
-      "\n"
-      "Base System Installation Checklist:\n"
-      "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
-      "\n"
-      "Initial boot:           [ ]\n"
-      "Detect network card:    [ ]\n"
-      "Configure network:      [ ]\n"
-      "Detect CD:              [ ]\n"
-      "Load installer modules: [ ]\n"
-      "Detect hard drives:     [ ]\n"
-      "Partition hard drives:  [ ]\n"
-      "Install base system:    [ ]\n"
-      "Clock/timezone setup:   [ ]\n"
-      "User/password setup:    [ ]\n"
-      "Install tasks:          [ ]\n"
-      "Install boot loader:    [ ]\n"
-      "Overall install:        [ ]\n"
-      "\n"
-      "Comments/Problems:\n"
-      "\n"
-      "&lt;Description of the install, in prose, and any thoughts, comments\n"
-      "      and ideas you had during the initial install.&gt;\n"
-      "</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state."
+"Alternatively you can use this template when filling out installation "
+"reports, and file the report as a bug report against the "
+"<classname>installation-reports</classname> pseudo package, by sending it to "
+"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
+"Package: installation-reports\n"
+"\n"
+"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
+"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
+"Date: &lt;Date and time of the install&gt;\n"
+"\n"
+"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
+"Processor:\n"
+"Memory:\n"
+"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
+"\n"
+"Output of lspci -knn (or lspci -nn):\n"
+"\n"
+"Base System Installation Checklist:\n"
+"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
+"\n"
+"Initial boot:           [ ]\n"
+"Detect network card:    [ ]\n"
+"Configure network:      [ ]\n"
+"Detect CD:              [ ]\n"
+"Load installer modules: [ ]\n"
+"Detect hard drives:     [ ]\n"
+"Partition hard drives:  [ ]\n"
+"Install base system:    [ ]\n"
+"Clock/timezone setup:   [ ]\n"
+"User/password setup:    [ ]\n"
+"Install tasks:          [ ]\n"
+"Install boot loader:    [ ]\n"
+"Overall install:        [ ]\n"
+"\n"
+"Comments/Problems:\n"
+"\n"
+"&lt;Description of the install, in prose, and any thoughts, comments\n"
+"      and ideas you had during the initial install.&gt;\n"
+"</screen></informalexample> In the bug report, describe what the problem is, "
+"including the last visible kernel messages in the event of a kernel hang. "
+"Describe the steps that you did which brought the system into the problem "
+"state."
 msgstr ""
-
diff --git a/po/tl/boot-new.po b/po/tl/boot-new.po
index 202d93271..f4d294cfc 100644
--- a/po/tl/boot-new.po
+++ b/po/tl/boot-new.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,31 +29,59 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:8
 #, no-c-format
-msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>."
+msgid ""
+"Your system's first boot on its own power is what electrical engineers call "
+"the <quote>smoke test</quote>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:13
 #, no-c-format
-msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new &debian; system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu."
+msgid ""
+"If you did a default installation, the first thing you should see when you "
+"boot the system is the menu of the <classname>grub</classname><phrase arch="
+"\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. "
+"The first choices in the menu will be for your new &debian; system. If you "
+"had any other operating systems on your computer (like Windows) that were "
+"detected by the installation system, those will be listed lower down in the "
+"menu."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:23
 #, no-c-format
-msgid "If the system fails to start up correctly, don't panic. If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting &debian;. In most cases such problems can be fixed without having to repeat the installation. One available option to fix boot problems is to use the installer's built-in rescue mode (see <xref linkend=\"rescue\"/>)."
+msgid ""
+"If the system fails to start up correctly, don't panic. If the installation "
+"was successful, chances are good that there is only a relatively minor "
+"problem that is preventing the system from booting &debian;. In most cases "
+"such problems can be fixed without having to repeat the installation. One "
+"available option to fix boot problems is to use the installer's built-in "
+"rescue mode (see <xref linkend=\"rescue\"/>)."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:32
 #, no-c-format
-msgid "If you are new to &debian; and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue."
+msgid ""
+"If you are new to &debian; and &arch-kernel;, you may need some help from "
+"more experienced users. <phrase arch=\"x86\">For direct on-line help you can "
+"try the IRC channels #debian or #debian-boot on the OFTC network. "
+"Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-"
+"user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common "
+"architectures like &arch-title;, your best option is to ask on the <ulink "
+"url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</"
+"phrase> You can also file an installation report as described in <xref "
+"linkend=\"submit-bug\"/>. Please make sure that you describe your problem "
+"clearly and include any messages that are displayed and may help others to "
+"diagnose the issue."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:48
 #, no-c-format
-msgid "If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report."
+msgid ""
+"If you had any other operating systems on your computer that were not "
+"detected or not detected correctly, please file an installation report."
 msgstr ""
 
 #. Tag: title
@@ -64,19 +93,42 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:57
 #, no-c-format
-msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
+msgid ""
+"If the machine fails to boot after completing the installation, and stops "
+"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</"
+"userinput> followed by &enterkey;. (The default boot configuration in "
+"<filename>quik.conf</filename> is labeled Linux). The labels defined in "
+"<filename>quik.conf</filename> will be displayed if you press the "
+"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also "
+"try booting back into the installer, and editing the <filename>/target/etc/"
+"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard "
+"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are "
+"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:71
 #, no-c-format
-msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"To boot back into MacOS without resetting the nvram, type <userinput>bye</"
+"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed "
+"from the machine). To obtain an OpenFirmware prompt, hold down the "
+"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</"
+"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. "
+"If you need to reset the OpenFirmware nvram changes to the MacOS default in "
+"order to boot back to MacOS, hold down the <keycombo> <keycap>command</"
+"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </"
+"keycombo> keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:84
 #, no-c-format
-msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
+msgid ""
+"If you use <command>BootX</command> to boot into the installed system, just "
+"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
+"un-choose the ramdisk option, and add a root device corresponding to your "
+"installation; e.g. <userinput>/dev/hda8</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -88,31 +140,52 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:97
 #, no-c-format
-msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon."
+msgid ""
+"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key "
+"and get a graphical screen with a button for each bootable OS, &debian-gnu; "
+"will be a button with a small penguin icon."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:104
 #, no-c-format
-msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
+msgid ""
+"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-"
+"device</envar> variable you should reset OpenFirmware to its default "
+"configuration. To do this hold down the <keycombo> <keycap>command</keycap> "
+"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> "
+"keys while cold booting the machine."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:112
 #, no-c-format
-msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
+msgid ""
+"The labels defined in <filename>yaboot.conf</filename> will be displayed if "
+"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:118
 #, no-c-format
-msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
+msgid ""
+"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-"
+"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap "
+"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an "
+"IDE disk this may not work and you will have to enter OpenFirmware and set "
+"the <envar>boot-device</envar> variable, <command>ybin</command> normally "
+"does this automatically."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:127
 #, no-c-format
-msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
+msgid ""
+"After you boot &debian-gnu; for the first time you can add any additional "
+"options you desire (such as dual boot options) to <filename>/etc/yaboot."
+"conf</filename> and run <command>ybin</command> to update your boot "
+"partition with the changed configuration. Please read the <ulink url=\"&url-"
+"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
 msgstr ""
 
 #. Tag: title
@@ -124,7 +197,11 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:147
 #, no-c-format
-msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
+msgid ""
+"If you created encrypted volumes during the installation and assigned them "
+"mount points, you will be asked to enter the passphrase for each of these "
+"volumes during the boot. The actual procedure differs slightly between dm-"
+"crypt and loop-AES."
 msgstr ""
 
 #. Tag: title
@@ -137,31 +214,54 @@ msgstr ""
 #: boot-new.xml:159
 #, no-c-format
 msgid ""
-      "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
-      "Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
-      "Enter LUKS passphrase:\n"
-      "</screen></informalexample> In the first line of the prompt, <replaceable>part</replaceable> is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename><replaceable>part</replaceable>_crypt</filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system."
+"For partitions encrypted using dm-crypt you will be shown the following "
+"prompt during the boot: <informalexample><screen>\n"
+"Starting early crypto disks... <replaceable>part</replaceable>_crypt"
+"(starting)\n"
+"Enter LUKS passphrase:\n"
+"</screen></informalexample> In the first line of the prompt, "
+"<replaceable>part</replaceable> is the name of the underlying partition, e."
+"g. sda2 or md0. You are now probably wondering <emphasis>for which volume</"
+"emphasis> you are actually entering the passphrase. Does it relate to your "
+"<filename>/home</filename>? Or to <filename>/var</filename>? Of course, if "
+"you have just one encrypted volume, this is easy and you can just enter the "
+"passphrase you used when setting up this volume. If you set up more than one "
+"encrypted volume during the installation, the notes you wrote down as the "
+"last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did "
+"not make a note of the mapping between <filename><replaceable>part</"
+"replaceable>_crypt</filename> and the mount points before, you can still "
+"find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</"
+"filename> of your new system."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:182
 #, no-c-format
-msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
+msgid ""
+"The prompt may look somewhat different when an encrypted root file system is "
+"mounted. This depends on which initramfs generator was used to generate the "
+"initrd used to boot the system. The example below is for an initrd generated "
+"using <classname>initramfs-tools</classname>:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:189
 #, no-c-format
 msgid ""
-      "Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
-      "Begin: Running /scripts/local-top ...\n"
-      "Enter LUKS passphrase:"
+"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
+"Begin: Running /scripts/local-top ...\n"
+"Enter LUKS passphrase:"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:191 boot-new.xml:216
 #, no-c-format
-msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
+msgid ""
+"No characters (even asterisks) will be shown while entering the passphrase. "
+"If you enter the wrong passphrase, you have two more tries to correct it. "
+"After the third try the boot process will skip this volume and continue to "
+"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting"
+"\"/> for further information."
 msgstr ""
 
 #. Tag: para
@@ -179,16 +279,19 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:209
 #, no-c-format
-msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
+msgid ""
+"For partitions encrypted using loop-AES you will be shown the following "
+"prompt during the boot:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:214
 #, no-c-format
 msgid ""
-      "Checking loop-encrypted file systems.\n"
-      "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
-      "Password:"
+"Checking loop-encrypted file systems.\n"
+"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</"
+"replaceable>)\n"
+"Password:"
 msgstr ""
 
 #. Tag: title
@@ -200,47 +303,77 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:234
 #, no-c-format
-msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
+msgid ""
+"If some of the encrypted volumes could not be mounted because a wrong "
+"passphrase was entered, you will have to mount them manually after the boot. "
+"There are several cases."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:243
 #, no-c-format
-msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
+msgid ""
+"The first case concerns the root partition. When it is not mounted "
+"correctly, the boot process will halt and you will have to reboot the "
+"computer to try again."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:250
 #, no-c-format
 msgid ""
-      "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
-      "<prompt>Password:</prompt>\n"
-      "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
+"The easiest case is for encrypted volumes holding data like <filename>/home</"
+"filename> or <filename>/srv</filename>. You can simply mount them manually "
+"after the boot. For loop-AES this is a one-step operation: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>\n"
+"<prompt>Password:</prompt>\n"
+"</screen></informalexample> where <replaceable>/mount_point</replaceable> "
+"should be replaced by the particular directory (e.g. <filename>/home</"
+"filename>). The only difference from an ordinary mount is that you will be "
+"asked to enter the passphrase for this volume."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:264
 #, no-c-format
 msgid ""
-      "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
-      "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
+"For dm-crypt this is a bit trickier. First you need to register the volumes "
+"with <application>device mapper</application> by running: "
+"<informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
+"</screen></informalexample> This will scan all volumes mentioned in "
+"<filename>/etc/crypttab</filename> and will create appropriate devices under "
+"the <filename>/dev</filename> directory after entering the correct "
+"passphrases. (Already registered volumes will be skipped, so you can repeat "
+"this command several times without worrying.) After successful registration "
+"you can simply mount the volumes the usual way:"
 msgstr ""
 
 #. Tag: screen
 #: boot-new.xml:279
 #, no-c-format
-msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
+msgid ""
+"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:282
 #, no-c-format
 msgid ""
-      "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-      "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
+"If any volume holding noncritical system files could not be mounted "
+"(<filename>/usr</filename> or <filename>/var</filename>), the system should "
+"still boot and you should be able to mount the volumes manually like in the "
+"previous case. However, you will also need to (re)start any services usually "
+"running in your default runlevel because it is very likely that they were "
+"not started. The easiest way to achieve this is by switching to the first "
+"runlevel and back by entering <informalexample><screen>\n"
+"<prompt>#</prompt> <userinput>init 1</userinput>\n"
+"</screen></informalexample> at the shell prompt and pressing <keycombo> "
+"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the "
+"root password."
 msgstr ""
 
 #. Tag: title
@@ -252,46 +385,81 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:307
 #, no-c-format
-msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
+msgid ""
+"Once your system boots, you'll be presented with the login prompt. Log in "
+"using the personal login and password you selected during the installation "
+"process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:313
 #, no-c-format
-msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
+msgid ""
+"If you are a new user, you may want to explore the documentation which is "
+"already installed on your system as you start to use it. There are currently "
+"several documentation systems, work is proceeding on integrating the "
+"different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:321
 #, no-c-format
-msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
+msgid ""
+"Documentation accompanying programs you have installed can be found in "
+"<filename>/usr/share/doc/</filename>, under a subdirectory named after the "
+"program (or, more precise, the &debian; package that contains the program). "
+"However, more extensive documentation is often packaged separately in "
+"special documentation packages that are mostly not installed by default. For "
+"example, documentation about the package management tool <command>apt</"
+"command> can be found in the packages <classname>apt-doc</classname> or "
+"<classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:332
 #, no-c-format
-msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
+msgid ""
+"In addition, there are some special folders within the <filename>/usr/share/"
+"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</"
+"emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</"
+"filename>. After installing <classname>dhelp</classname>, you will find a "
+"browsable index of documentation in <filename>/usr/share/doc/HTML/index."
+"html</filename>."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:341
 #, no-c-format
 msgid ""
-      "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
-      "$ cd /usr/share/doc/\n"
-      "$ w3m .\n"
-      "</screen></informalexample> The dot after the <command>w3m</command> command tells it to show the contents of the current directory."
+"One easy way to view these documents using a text based browser is to enter "
+"the following commands: <informalexample><screen>\n"
+"$ cd /usr/share/doc/\n"
+"$ w3m .\n"
+"</screen></informalexample> The dot after the <command>w3m</command> command "
+"tells it to show the contents of the current directory."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:351
 #, no-c-format
-msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
+msgid ""
+"If you have a graphical desktop environment installed, you can also use its "
+"web browser. Start the web browser from the application menu and enter "
+"<userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
 #: boot-new.xml:357
 #, no-c-format
-msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
+msgid ""
+"You can also type <userinput>info <replaceable>command</replaceable></"
+"userinput> or <userinput>man <replaceable>command</replaceable></userinput> "
+"to see documentation on most commands available at the command prompt. "
+"Typing <userinput>help</userinput> will display help on shell commands. And "
+"typing a command followed by <userinput>--help</userinput> will usually "
+"display a short summary of the command's usage. If a command's results "
+"scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> "
+"after the command to cause the results to pause before scrolling past the "
+"top of the screen. To see a list of all commands available which begin with "
+"a certain letter, type the letter and then two tabs."
 msgstr ""
-
diff --git a/po/tl/gpl.po b/po/tl/gpl.po
index 3582cbd8a..5f7616aa6 100644
--- a/po/tl/gpl.po
+++ b/po/tl/gpl.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,35 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:6
 #, no-c-format
-msgid "[[This note, consisting of two paragraphs, should only be included in your translation if you translate the GPL in this appendix. See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English name of your language. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[This note, consisting of two paragraphs, should only be included in your "
+"translation if you translate the GPL in this appendix. See build/lang-"
+"options/README on how to enable this paragraph and for additional "
+"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH "
+"IN ENGLISH! Only replace {language} with the English name of your language. "
+"Do not change the link to the GPL!]] This is an unofficial translation of "
+"the GNU General Public License into {language}. It was not published by the "
+"Free Software Foundation, and does not legally state the distribution terms "
+"for software that uses the GNU GPL &mdash; only the original <ulink url="
+"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. "
+"However, we hope that this translation will help {language} speakers to "
+"better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:22
 #, no-c-format
-msgid "[[See build/lang-options/README on how to enable this paragraph and for additional information. Its condition is \"gpl-unofficial\".]] [[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of your language before translating. Do not change the link to the GPL!]] This is an unofficial translation of the GNU General Public License into {language}. It was not published by the Free Software Foundation, and does not legally state the distribution terms for software that uses the GNU GPL &mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. However, we hope that this translation will help {language} speakers to better understand the GNU GPL."
+msgid ""
+"[[See build/lang-options/README on how to enable this paragraph and for "
+"additional information. Its condition is \"gpl-unofficial\".]] [[THIS "
+"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of "
+"your language before translating. Do not change the link to the GPL!]] This "
+"is an unofficial translation of the GNU General Public License into "
+"{language}. It was not published by the Free Software Foundation, and does "
+"not legally state the distribution terms for software that uses the GNU GPL "
+"&mdash; only the original <ulink url=\"&url-gnu-copyleft;\">English text</"
+"ulink> of the GNU GPL does that. However, we hope that this translation will "
+"help {language} speakers to better understand the GNU GPL."
 msgstr ""
 
 #. Tag: para
@@ -41,11 +64,11 @@ msgstr ""
 #: gpl.xml:41
 #, no-c-format
 msgid ""
-      "Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
-      "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
-      "\n"
-      "Everyone is permitted to copy and distribute verbatim copies\n"
-      "of this license document, but changing it is not allowed."
+"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n"
+"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n"
+"\n"
+"Everyone is permitted to copy and distribute verbatim copies\n"
+"of this license document, but changing it is not allowed."
 msgstr ""
 
 #. Tag: title
@@ -57,49 +80,87 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:46
 #, no-c-format
-msgid "The licenses for most software are designed to take away your freedom to share and change it. By contrast, the gnu General Public License is intended to guarantee your freedom to share and change free software &mdash; to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the gnu Library General Public License instead.) You can apply it to your programs, too."
+msgid ""
+"The licenses for most software are designed to take away your freedom to "
+"share and change it. By contrast, the gnu General Public License is intended "
+"to guarantee your freedom to share and change free software &mdash; to make "
+"sure the software is free for all its users. This General Public License "
+"applies to most of the Free Software Foundation's software and to any other "
+"program whose authors commit to using it. (Some other Free Software "
+"Foundation software is covered by the gnu Library General Public License "
+"instead.) You can apply it to your programs, too."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:58
 #, no-c-format
-msgid "When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things."
+msgid ""
+"When we speak of free software, we are referring to freedom, not price. Our "
+"General Public Licenses are designed to make sure that you have the freedom "
+"to distribute copies of free software (and charge for this service if you "
+"wish), that you receive source code or can get it if you want it, that you "
+"can change the software or use pieces of it in new free programs; and that "
+"you know you can do these things."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:68
 #, no-c-format
-msgid "To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it."
+msgid ""
+"To protect your rights, we need to make restrictions that forbid anyone to "
+"deny you these rights or to ask you to surrender the rights. These "
+"restrictions translate to certain responsibilities for you if you distribute "
+"copies of the software, or if you modify it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:75
 #, no-c-format
-msgid "For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
+msgid ""
+"For example, if you distribute copies of such a program, whether gratis or "
+"for a fee, you must give the recipients all the rights that you have. You "
+"must make sure that they, too, receive or can get the source code. And you "
+"must show them these terms so they know their rights."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:83
 #, no-c-format
-msgid "We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software."
+msgid ""
+"We protect your rights with two steps: (1) copyright the software, and (2) "
+"offer you this license which gives you legal permission to copy, distribute "
+"and/or modify the software."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:89
 #, no-c-format
-msgid "Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations."
+msgid ""
+"Also, for each author's protection and ours, we want to make certain that "
+"everyone understands that there is no warranty for this free software. If "
+"the software is modified by someone else and passed on, we want its "
+"recipients to know that what they have is not the original, so that any "
+"problems introduced by others will not reflect on the original authors' "
+"reputations."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:98
 #, no-c-format
-msgid "Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all."
+msgid ""
+"Finally, any free program is threatened constantly by software patents. We "
+"wish to avoid the danger that redistributors of a free program will "
+"individually obtain patent licenses, in effect making the program "
+"proprietary. To prevent this, we have made it clear that any patent must be "
+"licensed for everyone's free use or not licensed at all."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:107
 #, no-c-format
-msgid "The precise terms and conditions for copying, distribution and modification follow."
+msgid ""
+"The precise terms and conditions for copying, distribution and modification "
+"follow."
 msgstr ""
 
 #. Tag: title
@@ -117,163 +178,327 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:121
 #, no-c-format
-msgid "<emphasis role=\"bold\">0.</emphasis> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The \"Program\", below, refers to any such program or work, and a \"work based on the Program\" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term \"modification\".) Each licensee is addressed as \"you\"."
+msgid ""
+"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or "
+"other work which contains a notice placed by the copyright holder saying it "
+"may be distributed under the terms of this General Public License. The "
+"\"Program\", below, refers to any such program or work, and a \"work based "
+"on the Program\" means either the Program or any derivative work under "
+"copyright law: that is to say, a work containing the Program or a portion of "
+"it, either verbatim or with modifications and/or translated into another "
+"language. (Hereinafter, translation is included without limitation in the "
+"term \"modification\".) Each licensee is addressed as \"you\"."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:134
 #, no-c-format
-msgid "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does."
+msgid ""
+"Activities other than copying, distribution and modification are not covered "
+"by this License; they are outside its scope. The act of running the Program "
+"is not restricted, and the output from the Program is covered only if its "
+"contents constitute a work based on the Program (independent of having been "
+"made by running the Program). Whether that is true depends on what the "
+"Program does."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:143
 #, no-c-format
-msgid "<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program."
+msgid ""
+"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim "
+"copies of the Program's source code as you receive it, in any medium, "
+"provided that you conspicuously and appropriately publish on each copy an "
+"appropriate copyright notice and disclaimer of warranty; keep intact all the "
+"notices that refer to this License and to the absence of any warranty; and "
+"give any other recipients of the Program a copy of this License along with "
+"the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:154
 #, no-c-format
-msgid "You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee."
+msgid ""
+"You may charge a fee for the physical act of transferring a copy, and you "
+"may at your option offer warranty protection in exchange for a fee."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:160
 #, no-c-format
-msgid "<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:"
+msgid ""
+"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of "
+"the Program or any portion of it, thus forming a work based on the Program, "
+"and copy and distribute such modifications or work under the terms of "
+"Section 1 above, provided that you also meet all of these conditions:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:169
 #, no-c-format
-msgid "You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change."
+msgid ""
+"You must cause the modified files to carry prominent notices stating that "
+"you changed the files and the date of any change."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:175
 #, no-c-format
-msgid "You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License."
+msgid ""
+"You must cause any work that you distribute or publish, that in whole or in "
+"part contains or is derived from the Program or any part thereof, to be "
+"licensed as a whole at no charge to all third parties under the terms of "
+"this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:183
 #, no-c-format
-msgid "If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)"
+msgid ""
+"If the modified program normally reads commands interactively when run, you "
+"must cause it, when started running for such interactive use in the most "
+"ordinary way, to print or display an announcement including an appropriate "
+"copyright notice and a notice that there is no warranty (or else, saying "
+"that you provide a warranty) and that users may redistribute the program "
+"under these conditions, and telling the user how to view a copy of this "
+"License. (Exception: if the Program itself is interactive but does not "
+"normally print such an announcement, your work based on the Program is not "
+"required to print an announcement.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:197
 #, no-c-format
-msgid "These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
+msgid ""
+"These requirements apply to the modified work as a whole. If identifiable "
+"sections of that work are not derived from the Program, and can be "
+"reasonably considered independent and separate works in themselves, then "
+"this License, and its terms, do not apply to those sections when you "
+"distribute them as separate works. But when you distribute the same sections "
+"as part of a whole which is a work based on the Program, the distribution of "
+"the whole must be on the terms of this License, whose permissions for other "
+"licensees extend to the entire whole, and thus to each and every part "
+"regardless of who wrote it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:210
 #, no-c-format
-msgid "Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program."
+msgid ""
+"Thus, it is not the intent of this section to claim rights or contest your "
+"rights to work written entirely by you; rather, the intent is to exercise "
+"the right to control the distribution of derivative or collective works "
+"based on the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:217
 #, no-c-format
-msgid "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License."
+msgid ""
+"In addition, mere aggregation of another work not based on the Program with "
+"the Program (or with a work based on the Program) on a volume of a storage "
+"or distribution medium does not bring the other work under the scope of this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:224
 #, no-c-format
-msgid "<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:"
+msgid ""
+"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the "
+"Program (or a work based on it, under Section 2) in object code or "
+"executable form under the terms of Sections 1 and 2 above provided that you "
+"also do one of the following:"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:233
 #, no-c-format
-msgid "Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with the complete corresponding machine-readable source code, "
+"which must be distributed under the terms of Sections 1 and 2 above on a "
+"medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:241
 #, no-c-format
-msgid "Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,"
+msgid ""
+"Accompany it with a written offer, valid for at least three years, to give "
+"any third party, for a charge no more than your cost of physically "
+"performing source distribution, a complete machine-readable copy of the "
+"corresponding source code, to be distributed under the terms of Sections 1 "
+"and 2 above on a medium customarily used for software interchange; or,"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:251
 #, no-c-format
-msgid "Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)"
+msgid ""
+"Accompany it with the information you received as to the offer to distribute "
+"corresponding source code. (This alternative is allowed only for "
+"noncommercial distribution and only if you received the program in object "
+"code or executable form with such an offer, in accord with Subsection b "
+"above.)"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:260
 #, no-c-format
-msgid "The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."
+msgid ""
+"The source code for a work means the preferred form of the work for making "
+"modifications to it. For an executable work, complete source code means all "
+"the source code for all modules it contains, plus any associated interface "
+"definition files, plus the scripts used to control compilation and "
+"installation of the executable. However, as a special exception, the source "
+"code distributed need not include anything that is normally distributed (in "
+"either source or binary form) with the major components (compiler, kernel, "
+"and so on) of the operating system on which the executable runs, unless that "
+"component itself accompanies the executable."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:273
 #, no-c-format
-msgid "If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code."
+msgid ""
+"If distribution of executable or object code is made by offering access to "
+"copy from a designated place, then offering equivalent access to copy the "
+"source code from the same place counts as distribution of the source code, "
+"even though third parties are not compelled to copy the source along with "
+"the object code."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:281
 #, no-c-format
-msgid "<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance."
+msgid ""
+"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, "
+"or distribute the Program except as expressly provided under this License. "
+"Any attempt otherwise to copy, modify, sublicense or distribute the Program "
+"is void, and will automatically terminate your rights under this License. "
+"However, parties who have received copies, or rights, from you under this "
+"License will not have their licenses terminated so long as such parties "
+"remain in full compliance."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:292
 #, no-c-format
-msgid "<emphasis role=\"bold\">5.</emphasis> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it."
+msgid ""
+"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this "
+"License, since you have not signed it. However, nothing else grants you "
+"permission to modify or distribute the Program or its derivative works. "
+"These actions are prohibited by law if you do not accept this License. "
+"Therefore, by modifying or distributing the Program (or any work based on "
+"the Program), you indicate your acceptance of this License to do so, and all "
+"its terms and conditions for copying, distributing or modifying the Program "
+"or works based on it."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:304
 #, no-c-format
-msgid "<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License."
+msgid ""
+"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program "
+"(or any work based on the Program), the recipient automatically receives a "
+"license from the original licensor to copy, distribute or modify the Program "
+"subject to these terms and conditions. You may not impose any further "
+"restrictions on the recipients' exercise of the rights granted herein. You "
+"are not responsible for enforcing compliance by third parties to this "
+"License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:315
 #, no-c-format
-msgid "<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
+msgid ""
+"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court "
+"judgment or allegation of patent infringement or for any other reason (not "
+"limited to patent issues), conditions are imposed on you (whether by court "
+"order, agreement or otherwise) that contradict the conditions of this "
+"License, they do not excuse you from the conditions of this License. If you "
+"cannot distribute so as to satisfy simultaneously your obligations under "
+"this License and any other pertinent obligations, then as a consequence you "
+"may not distribute the Program at all. For example, if a patent license "
+"would not permit royalty-free redistribution of the Program by all those who "
+"receive copies directly or indirectly through you, then the only way you "
+"could satisfy both it and this License would be to refrain entirely from "
+"distribution of the Program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:332
 #, no-c-format
-msgid "If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances."
+msgid ""
+"If any portion of this section is held invalid or unenforceable under any "
+"particular circumstance, the balance of the section is intended to apply and "
+"the section as a whole is intended to apply in other circumstances."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:339
 #, no-c-format
-msgid "It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice."
+msgid ""
+"It is not the purpose of this section to induce you to infringe any patents "
+"or other property right claims or to contest validity of any such claims; "
+"this section has the sole purpose of protecting the integrity of the free "
+"software distribution system, which is implemented by public license "
+"practices. Many people have made generous contributions to the wide range of "
+"software distributed through that system in reliance on consistent "
+"application of that system; it is up to the author/donor to decide if he or "
+"she is willing to distribute software through any other system and a "
+"licensee cannot impose that choice."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:352
 #, no-c-format
-msgid "This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License."
+msgid ""
+"This section is intended to make thoroughly clear what is believed to be a "
+"consequence of the rest of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:357
 #, no-c-format
-msgid "<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License."
+msgid ""
+"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the "
+"Program is restricted in certain countries either by patents or by "
+"copyrighted interfaces, the original copyright holder who places the Program "
+"under this License may add an explicit geographical distribution limitation "
+"excluding those countries, so that distribution is permitted only in or "
+"among countries not thus excluded. In such case, this License incorporates "
+"the limitation as if written in the body of this License."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:368
 #, no-c-format
-msgid "<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and \"any later version\", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
+msgid ""
+"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may "
+"publish revised and/or new versions of the General Public License from time "
+"to time. Such new versions will be similar in spirit to the present version, "
+"but may differ in detail to address new problems or concerns. Each version "
+"is given a distinguishing version number. If the Program specifies a version "
+"number of this License which applies to it and \"any later version\", you "
+"have the option of following the terms and conditions either of that version "
+"or of any later version published by the Free Software Foundation. If the "
+"Program does not specify a version number of this License, you may choose "
+"any version ever published by the Free Software Foundation."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:383
 #, no-c-format
-msgid "<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally."
+msgid ""
+"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of "
+"the Program into other free programs whose distribution conditions are "
+"different, write to the author to ask for permission. For software which is "
+"copyrighted by the Free Software Foundation, write to the Free Software "
+"Foundation; we sometimes make exceptions for this. Our decision will be "
+"guided by the two goals of preserving the free status of all derivatives of "
+"our free software and of promoting the sharing and reuse of software "
+"generally."
 msgstr ""
 
 #. Tag: emphasis
@@ -285,13 +510,31 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:399
 #, no-c-format
-msgid "<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION."
+msgid ""
+"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE "
+"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY "
+"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT "
+"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY "
+"OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE "
+"IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. "
+"THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH "
+"YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL "
+"NECESSARY SERVICING, REPAIR OR CORRECTION."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:412
 #, no-c-format
-msgid "<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
+msgid ""
+"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY "
+"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY "
+"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED "
+"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, "
+"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO "
+"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING "
+"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE "
+"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR "
+"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES."
 msgstr ""
 
 #. Tag: emphasis
@@ -309,87 +552,111 @@ msgstr ""
 #. Tag: para
 #: gpl.xml:434
 #, no-c-format
-msgid "If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms."
+msgid ""
+"If you develop a new program, and you want it to be of the greatest possible "
+"use to the public, the best way to achieve this is to make it free software "
+"which everyone can redistribute and change under these terms."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:441
 #, no-c-format
-msgid "To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the \"copyright\" line and a pointer to where the full notice is found."
+msgid ""
+"To do so, attach the following notices to the program. It is safest to "
+"attach them to the start of each source file to most effectively convey the "
+"exclusion of warranty; and each file should have at least the \"copyright\" "
+"line and a pointer to where the full notice is found."
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:448
 #, no-c-format
 msgid ""
-      "<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable>\n"
-      "Copyright (C) <replaceable>year  name of author</replaceable>\n"
-      "\n"
-      "This program is free software; you can redistribute it and/or\n"
-      "modify it under the terms of the GNU General Public License\n"
-      "as published by the Free Software Foundation; either version 2\n"
-      "of the License, or (at your option) any later version.\n"
-      "\n"
-      "This program is distributed in the hope that it will be useful,\n"
-      "but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
-      "MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
-      "GNU General Public License for more details.\n"
-      "\n"
-      "You should have received a copy of the GNU General Public License\n"
-      "along with this program; if not, write to the Free Software\n"
-      "Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA."
+"<replaceable>one line to give the program's name and a brief idea of what it "
+"does.</replaceable>\n"
+"Copyright (C) <replaceable>year  name of author</replaceable>\n"
+"\n"
+"This program is free software; you can redistribute it and/or\n"
+"modify it under the terms of the GNU General Public License\n"
+"as published by the Free Software Foundation; either version 2\n"
+"of the License, or (at your option) any later version.\n"
+"\n"
+"This program is distributed in the hope that it will be useful,\n"
+"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
+"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n"
+"GNU General Public License for more details.\n"
+"\n"
+"You should have received a copy of the GNU General Public License\n"
+"along with this program; if not, write to the Free Software\n"
+"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, "
+"USA."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:450
 #, no-c-format
-msgid "Also add information on how to contact you by electronic and paper mail."
+msgid ""
+"Also add information on how to contact you by electronic and paper mail."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:455
 #, no-c-format
-msgid "If the program is interactive, make it output a short notice like this when it starts in an interactive mode:"
+msgid ""
+"If the program is interactive, make it output a short notice like this when "
+"it starts in an interactive mode:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:460
 #, no-c-format
 msgid ""
-      "Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable>\n"
-      "Gnomovision comes with absolutely no warranty; for details\n"
-      "type `show w'. This is free software, and you are welcome\n"
-      "to redistribute it under certain conditions; type `show c'\n"
-      "for details."
+"Gnomovision version 69, Copyright (C) <replaceable>year name of author</"
+"replaceable>\n"
+"Gnomovision comes with absolutely no warranty; for details\n"
+"type `show w'. This is free software, and you are welcome\n"
+"to redistribute it under certain conditions; type `show c'\n"
+"for details."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:462
 #, no-c-format
-msgid "The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items &mdash; whatever suits your program."
+msgid ""
+"The hypothetical commands `show w' and `show c' should show the appropriate "
+"parts of the General Public License. Of course, the commands you use may be "
+"called something other than `show w' and `show c'; they could even be mouse-"
+"clicks or menu items &mdash; whatever suits your program."
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:470
 #, no-c-format
-msgid "You should also get your employer (if you work as a programmer) or your school, if any, to sign a \"copyright disclaimer\" for the program, if necessary. Here is a sample; alter the names:"
+msgid ""
+"You should also get your employer (if you work as a programmer) or your "
+"school, if any, to sign a \"copyright disclaimer\" for the program, if "
+"necessary. Here is a sample; alter the names:"
 msgstr ""
 
 #. Tag: screen
 #: gpl.xml:476
 #, no-c-format
 msgid ""
-      "Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
-      "program `Gnomovision' (which makes passes at compilers) written\n"
-      "by James Hacker.\n"
-      "\n"
-      "<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
-      "Ty Coon, President of Vice"
+"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n"
+"program `Gnomovision' (which makes passes at compilers) written\n"
+"by James Hacker.\n"
+"\n"
+"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n"
+"Ty Coon, President of Vice"
 msgstr ""
 
 #. Tag: para
 #: gpl.xml:478
 #, no-c-format
-msgid "This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
+msgid ""
+"This General Public License does not permit incorporating your program into "
+"proprietary programs. If your program is a subroutine library, you may "
+"consider it more useful to permit linking proprietary applications with the "
+"library. If this is what you want to do, use the GNU Lesser General Public "
+"License instead of this License."
 msgstr ""
-
diff --git a/po/tl/hardware.po b/po/tl/hardware.po
index c3e0c1251..96af36f01 100644
--- a/po/tl/hardware.po
+++ b/po/tl/hardware.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:7
 #, no-c-format
-msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;."
+msgid ""
+"This section contains information about what hardware you need to get "
+"started with &debian;. You will also find links to further information about "
+"hardware supported by GNU and &arch-kernel;."
 msgstr ""
 
 #. Tag: title
@@ -34,13 +38,23 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;."
+msgid ""
+"&debian; does not impose hardware requirements beyond the requirements of "
+"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any "
+"architecture or platform to which the Linux or kFreeBSD kernel, libc, "
+"<command>gcc</command>, etc. have been ported, and for which a &debian; port "
+"exists, can run &debian;. Please refer to the Ports pages at <ulink url="
+"\"&url-ports;\"></ulink> for more details on &arch-title; architecture "
+"systems which have been tested with &debian-gnu;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:32
 #, no-c-format
-msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found."
+msgid ""
+"Rather than attempting to describe all the different hardware configurations "
+"which are supported for &arch-title;, this section contains general "
+"information and pointers to where additional information can be found."
 msgstr ""
 
 #. Tag: title
@@ -52,7 +66,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid ""
+"&debian; GNU/Linux &release; supports eleven major architectures and several "
+"variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -430,19 +446,38 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:203
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are "
+"looking for information on any of the other &debian;-supported architectures "
+"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-"
+"Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:213
 #, no-c-format
-msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
+msgid ""
+"The &arch-title; architecture only supports Intel Itanium processors and not "
+"the much more common 64-bit processors from the Intel 64 family (including e."
+"g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported "
+"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit "
+"userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:223
 #, no-c-format
-msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
+msgid ""
+"This is the first official release of &debian-gnu; for the &arch-title; "
+"architecture. We feel that it has proven itself sufficiently to be released. "
+"However, because it has not had the exposure (and hence testing by users) "
+"that some other architectures have had, you may encounter a few bugs. Use "
+"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any "
+"problems; make sure to mention the fact that the bug is on the &arch-title; "
+"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be "
+"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
@@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464
+#: hardware.xml:522 hardware.xml:575
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -466,13 +502,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:273
 #, no-c-format
-msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
+msgid ""
+"Each distinct ARM architecture requires its own kernel. Because of this the "
+"standard &debian; distribution only supports installation on a number of the "
+"most common platforms. The &debian; userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:282
 #, no-c-format
-msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
+msgid ""
+"Most ARM CPUs may be run in either endian mode (big or little). However, the "
+"majority of current system implementation uses little-endian mode. &debian; "
+"currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
@@ -490,7 +533,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:298
 #, no-c-format
-msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
+msgid ""
+"Intel's I/O Processor (IOP) line is found in a number of products related to "
+"data storage and processing. &debian; currently supports the IOP32x "
+"platform, featuring the IOP 80219 and 32x chips commonly found in Network "
+"Attached Storage (NAS) devices. &debian; explicitly supports two such "
+"devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from "
+"IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -502,7 +551,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:312
 #, no-c-format
-msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
+msgid ""
+"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM "
+"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently "
+"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-"
+"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug "
+"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-"
+"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x "
+"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, "
+"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
@@ -514,7 +571,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:329
 #, no-c-format
-msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
+msgid ""
+"Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, "
+"Ethernet, SATA, USB, and other functionality in one chip. There are many "
+"Network Attached Storage (NAS) devices on the market that are based on an "
+"Orion chip. We currently support the following Orion based devices: <ulink "
+"url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url="
+"\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-"
+"cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
@@ -526,19 +590,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:344
 #, no-c-format
-msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
+msgid ""
+"The Versatile platform is emulated by QEMU and is therefore a nice way to "
+"test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:363
 #, no-c-format
-msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
+msgid ""
+"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-"
+"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit "
+"processors whereas the 2.0 architecture is targeted to the 64-bit "
+"processors. Some systems are able to run either kernel. In both cases, the "
+"userland is 32-bit. There is the possibility of a 64-bit userland in the "
+"future."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:382
 #, no-c-format
-msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
+msgid ""
+"Complete information concerning supported peripherals can be found at <ulink "
+"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. "
+"This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
@@ -550,19 +625,43 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:391
 #, no-c-format
-msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
+msgid ""
+"Nearly all x86-based (IA-32) processors still in use in personal computers "
+"are supported, including all varieties of Intel's \"Pentium\" series. This "
+"also includes 32-bit AMD and VIA (former Cyrix) processors, and processors "
+"like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:398
 #, no-c-format
-msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
+msgid ""
+"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run "
+"on 386 or earlier processors. Despite the architecture name \"i386\", "
+"support for actual 80386 processors (and their clones) was dropped with the "
+"Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to "
+"avoid this, but in the end it was necessary due a unfortunate series of "
+"issues with the compiler and the kernel, starting with an bug in the C++ ABI "
+"provided by GCC. You should still be able to run &debian; GNU/Linux on "
+"actual 80386 processors if you compile your own kernel and compile all "
+"packages from source, but that is beyond the scope of this manual. </para> </"
+"footnote>. (No version of Linux has ever supported the 286 or earlier chips "
+"in the series.) All i486 and later processors are still supported<footnote> "
+"<para> Many &debian; packages will actually run slightly faster on modern "
+"computers as a positive side effect of dropping support for these old chips. "
+"The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) "
+"which the i386, introduced in 1986, did not have. Previously, these could "
+"not be easily used by most &debian; packages; now they can. </para> </"
+"footnote>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:431
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+msgid ""
+"If your system has a 64-bit processor from the AMD64 or Intel 64 families, "
+"you will probably want to use the installer for the amd64 architecture "
+"instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
@@ -574,31 +673,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:441
 #, no-c-format
-msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
+msgid ""
+"The system bus is the part of the motherboard which allows the CPU to "
+"communicate with peripherals such as storage devices. Your computer must use "
+"the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called "
+"the VL bus). Essentially all personal computers sold in recent years use one "
+"of these."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:465
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, "
+"Indigo 2 and Challenge S. Since these machines are very similar, whenever "
+"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant "
+"as well. </para></listitem> <listitem><para> SGI IP32: this platform is "
+"generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: "
+"this platform is emulated by QEMU and is therefore a nice way to test and "
+"run &debian; on MIPS if you don't have the hardware. </para></listitem> </"
+"itemizedlist> Complete information regarding supported mips/mipsel machines "
+"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</"
+"ulink>. In the following, only the systems supported by the &debian; "
+"installer will be covered. If you are looking for support for other "
+"subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> "
+"debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
+msgid ""
+"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and "
+"R5000 processors are supported by the &debian; installation system on big "
+"endian MIPS. On SGI IP32, currently only systems based on the R5000 are "
+"supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
+msgid ""
+"Some MIPS machines can be operated in both big and little endian mode. For "
+"little endian MIPS, please read the documentation for the mipsel "
+"architecture."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:523
 #, no-c-format
-msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
+msgid ""
+"&debian; on &arch-title; supports the following platforms: <itemizedlist> "
+"<listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are "
+"covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway "
+"Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform "
+"is emulated by QEMU and is therefore a nice way to test and run &debian; on "
+"MIPS if you don't have the hardware. </para></listitem> </itemizedlist> "
+"Complete information regarding supported mips/mipsel machines can be found "
+"at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the "
+"following, only the systems supported by the &debian; installer will be "
+"covered. If you are looking for support for other subarchitectures, please "
+"contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; "
+"mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -610,7 +747,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:553
 #, no-c-format
-msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
+msgid ""
+"All MIPS based Cobalt machines are supported with the exception of the Qube "
+"2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
@@ -628,7 +767,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:576
 #, no-c-format
-msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
+msgid ""
+"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and "
+"PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +781,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:599
 #, no-c-format
-msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
+msgid ""
+"There are two flavours of the powerpc kernel in &debian;, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -652,7 +795,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:607
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid ""
+"Most systems use this kernel flavour, which supports the PowerPC 601, 603, "
+"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and "
+"including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
@@ -670,19 +816,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:622
 #, no-c-format
-msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
+msgid ""
+"The POWER3 processor is used in older IBM 64-bit server systems: known "
+"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, "
+"and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:628
 #, no-c-format
-msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
+msgid ""
+"The POWER4 processor is used in more recent IBM 64-bit server systems: known "
+"models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:633
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid ""
+"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 "
+"architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
@@ -694,25 +847,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:669
 #, no-c-format
-msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
+msgid ""
+"Apple (and briefly a few other manufacturers &mdash; Power Computing, for "
+"example) made a series of Macintosh computers based on the PowerPC "
+"processor. For purposes of architecture support, they are categorized as "
+"NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:676
 #, no-c-format
-msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
+msgid ""
+"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI "
+"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld "
+"machines. Those pre-iMac PowerPC models from Apple use a four digit naming "
+"scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:684
 #, no-c-format
-msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
+msgid ""
+"The so called NewWorld PowerMacs are any PowerMacs in translucent colored "
+"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, "
+"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. "
+"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</"
+"quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:692
 #, no-c-format
-msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
+msgid ""
+"Specifications for Apple hardware are available at <ulink url=\"http://www."
+"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older "
+"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/"
+"index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
@@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726
+#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738
+#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750
+#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774
+#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786
+#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798
+#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819
+#: hardware.xml:825
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -1084,7 +1261,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:933
 #, no-c-format
-msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
+msgid ""
+"NuBus systems are not currently supported by &debian;/powerpc. The "
+"monolithic Linux/PPC kernel architecture does not have support for these "
+"machines; instead, one must use the MkLinux Mach microkernel, which &debian; "
+"does not yet support. These include the following: <itemizedlist> "
+"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> "
+"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> "
+"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> "
+"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </"
+"itemizedlist> A linux kernel for these machines and limited support is "
+"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1096,19 +1283,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:972
 #, no-c-format
-msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
+msgid ""
+"Macintosh computers using the 680x0 series of processors are <emphasis>not</"
+"emphasis> in the PowerPC family but are instead m68k machines. Those models "
+"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> "
+"family, then the Centris series, and culminate in the Quadras and Performas. "
+"These models usually have a Roman numeral or 3-digit model number such as "
+"Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:981
 #, no-c-format
-msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
+msgid ""
+"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, "
+"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, "
+"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra "
+"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the "
+"Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:989
 #, no-c-format
-msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
+msgid ""
+"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs "
+"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, "
+"please see the section above)."
 msgstr ""
 
 #. Tag: title
@@ -1120,7 +1321,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1006
 #, no-c-format
-msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
+msgid ""
+"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. "
+"Your machine needs to support the z/Architecture, 64-bit support is "
+"mandatory. The userland of the s390 port is still compiled for ESA/390, "
+"though. All zSeries and System z hardware is fully supported. &arch-title; "
+"support software is included from the kernel 3.1 development stream. The "
+"most current information about IBM's Linux support can be found at the "
+"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/"
+"development_technical.html\"> Linux on <trademark class=\"registered"
+"\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1132,7 +1342,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1024
 #, no-c-format
-msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
+msgid ""
+"PAV and HyperPAV are supported transparently, multipathing is not needed to "
+"take advantage of these storage system features. Be sure to configure the "
+"devices during DASD device selection. The alias devices will not be offered "
+"neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
@@ -1144,7 +1358,11 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1041
 #, no-c-format
-msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
+msgid ""
+"Sparc-based hardware is divided into a number of different subarchitectures, "
+"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u "
+"or sun4v. The following list describes what machines they include and what "
+"level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
@@ -1156,13 +1374,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1054
 #, no-c-format
-msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
+msgid ""
+"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a "
+"complete list of machines belonging to these subarchitectures, please "
+"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation"
+"\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1061
 #, no-c-format
-msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
+msgid ""
+"The last &debian; release to support sparc32 was Etch, but even then only "
+"for sun4m systems. Support for the other 32-bits subarchitectures had "
+"already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
@@ -1174,7 +1399,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1073
 #, no-c-format
-msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
+msgid ""
+"This subarchitecture includes all 64-bit machines (sparc64) based on the "
+"UltraSparc processor and its clones. Most of the machines are well "
+"supported, even though for some you may experience problems booting from CD "
+"due to firmware or bootloader bugs (this problem may be worked around by "
+"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP "
+"configurations respectively."
 msgstr ""
 
 #. Tag: term
@@ -1186,13 +1417,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1088
 #, no-c-format
-msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
+msgid ""
+"This is the newest addition to the Sparc family, which includes machines "
+"based on the Niagara multi-core CPUs. At the moment such CPUs are only "
+"available in T1000 and T2000 servers by Sun, and are well supported. Use the "
+"sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1099
 #, no-c-format
-msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
+msgid ""
+"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are "
+"not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
@@ -1204,7 +1441,16 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1109
 #, no-c-format
-msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
+msgid ""
+"From a technical point of view, laptops are normal PCs, so all information "
+"regarding PC systems applies to laptops as well. Installations on laptops "
+"nowadays usually work out of the box, including things like automatically "
+"suspending the system on closing the lid and laptop specfic hardware buttons "
+"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). "
+"Nonetheless sometimes the hardware vendors use specialized or proprietary "
+"hardware for some laptop-specific functions which might not be supported. To "
+"see if your particular laptop works well with GNU/Linux, see for example the "
+"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -1216,61 +1462,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1127
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. Having multiple "
+"processors in a computer was originally only an issue for high-end server "
+"systems but has become quite common in recent years even for rather low-end "
+"desktop computers and laptops with the introduction of so called "
+"<quote>multi-core</quote> processors. These contain two or more processor "
+"units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1137
 #, no-c-format
-msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
+msgid ""
+"The standard &debian; &release; kernel image has been compiled with SMP "
+"support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1148
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. The standard "
+"&debian; &release; kernel image has been compiled with <firstterm>SMP-"
+"alternatives</firstterm> support. This means that the kernel will detect the "
+"number of processors (or processor cores) and will automatically deactivate "
+"SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1157
 #, no-c-format
-msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
+msgid ""
+"Having multiple processors in a computer was originally only an issue for "
+"high-end server systems but has become quite common in recent years even for "
+"rather low-end desktop computers and laptops with the introduction of so "
+"called <quote>multi-core</quote> processors. These contain two or more "
+"processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1165
 #, no-c-format
-msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
+msgid ""
+"The 486 flavour of the &debian; kernel image packages for &arch-title; is "
+"not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1175
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture. However, the "
+"standard &debian; &release; kernel image does not support SMP. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1184
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a "
+"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this "
+"time (kernel version &kernelversion;) the way you enable SMP is to select "
+"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</"
+"quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1198
 #, no-c-format
-msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
+msgid ""
+"Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</"
+"quote> or SMP &mdash; is available for this architecture, and is supported "
+"by a precompiled &debian; kernel image. Depending on your install media, "
+"this SMP-capable kernel may or may not be installed by default. This should "
+"not prevent installation, since the standard, non-SMP kernel should boot on "
+"SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1208
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
+msgid ""
+"In order to take advantage of multiple processors, you should check to see "
+"if a kernel package that supports SMP is installed, and if not, choose an "
+"appropriate kernel package."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1214
 #, no-c-format
-msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
+msgid ""
+"You can also build your own customized kernel to support SMP.<phrase arch="
+"\"linux-any\"> You can find a discussion of how to do this in <xref linkend="
+"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way "
+"you enable SMP is to select <quote>&smp-config-option;</quote> in the "
+"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1282,13 +1575,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1226
 #, no-c-format
-msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
+msgid ""
+"&debian;'s support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. On modern PCs, having a graphical "
+"display usually works out of the box. Whether advanced graphics card "
+"features such as 3D-hardware acceleration or hardware-accelerated video are "
+"available, depends on the actual graphics hardware used in the system and in "
+"some cases on the installation of additional <quote>firmware</quote> images "
+"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have "
+"been reports about hardware on which installation of additional graphics "
+"card firmware was required even for basic graphics support, but these have "
+"been rare exceptions."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1239
 #, no-c-format
-msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
+msgid ""
+"Details on supported graphics cards and pointing devices can be found at "
+"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org "
+"version &x11ver;."
 msgstr ""
 
 #. Tag: para
@@ -1300,13 +1606,31 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1249
 #, no-c-format
-msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
+msgid ""
+"Most graphics options commonly found on Sparc-based machines are supported. "
+"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, "
+"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), "
+"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards "
+"(glint driver). To use an Elite3D card with X.org you additionally need to "
+"install the <classname>afbinit</classname> package, and read the "
+"documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1259
 #, no-c-format
-msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
+msgid ""
+"It is not uncommon for a Sparc machine to have two graphics cards in a "
+"default configuration. In such a case there is a possibility that the Linux "
+"kernel will not direct its output to the card initially used by the "
+"firmware. The lack of output on the graphical console may then be mistaken "
+"for a hang (usually the last message seen on console is 'Booting Linux...'). "
+"One possible solution is to physically remove one of the video cards; "
+"another option is to disable one of the cards using a kernel boot parameter. "
+"Also, if graphical output is not required or desired, serial console may be "
+"used as an alternative. On some systems use of serial console can be "
+"activated automatically by disconnecting the keyboard before booting the "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -1318,13 +1642,20 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1282
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
+msgid ""
+"Almost any network interface card (NIC) supported by the &arch-kernel; "
+"kernel should also be supported by the installation system; drivers should "
+"normally be loaded automatically. <phrase arch=\"x86\">This includes most "
+"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> "
+"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1292
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+msgid ""
+"This includes a lot of generic PCI cards (for systems that have PCI) and the "
+"following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
@@ -1384,7 +1715,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1349
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
+msgid ""
+"On &arch-title;, most built-in Ethernet devices are supported and modules "
+"for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
@@ -1402,31 +1735,52 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1362
 #, no-c-format
-msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
+msgid ""
+"Wireless networking is in general supported as well and a growing number of "
+"wireless adapters are supported by the official &arch-kernel; kernel, "
+"although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1369
 #, no-c-format
-msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
+msgid ""
+"If firmware is needed, the installer will prompt you to load firmware. See "
+"<xref linkend=\"loading-firmware\"/> for detailed information on how to load "
+"firmware during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1374
 #, no-c-format
-msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
+msgid ""
+"Wireless NICs that are not supported by the official &arch-kernel; kernel "
+"can generally be made to work under &debian-gnu;, but are not supported "
+"during the installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1379
 #, no-c-format
-msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
+msgid ""
+"If there is a problem with wireless and there is no other NIC you can use "
+"during the installation, it is still possible to install &debian-gnu; using "
+"a full CD-ROM or DVD image. Select the option to not configure a network and "
+"install using only the packages available from the CD/DVD. You can then "
+"install the driver and firmware you need after the installation is completed "
+"(after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1389
 #, no-c-format
-msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
+msgid ""
+"In some cases the driver you need may not be available as a &debian; "
+"package. You will then have to look if there is source code available in the "
+"internet and compile the driver yourself. How to do this is outside the "
+"scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, "
+"your last resort is to use the <classname>ndiswrapper</classname> package, "
+"which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -1438,7 +1792,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1404
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid ""
+"There are a couple of issues with specific network cards that are worth "
+"mentioning here."
 msgstr ""
 
 #. Tag: title
@@ -1450,19 +1806,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1413
 #, no-c-format
-msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
+msgid ""
+"There are various PCI network cards that have the same PCI identification, "
+"but are supported by related, but different drivers. Some cards work with "
+"the <literal>tulip</literal> driver, others with the <literal>dfme</literal> "
+"driver. Because they have the same identification, the kernel cannot "
+"distinguish between them and it is not certain which driver will be loaded. "
+"If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1423
 #, no-c-format
-msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
+msgid ""
+"This is a common problem on Netra systems with a Davicom (DEC-Tulip "
+"compatible) NIC. In that case the <literal>tulip</literal> driver is "
+"probably the correct one. You can prevent this issue by blacklisting the "
+"wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1431
 #, no-c-format
-msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
+msgid ""
+"An alternative solution during the installation is to switch to a shell and "
+"unload the wrong driver module using <userinput>modprobe -r "
+"<replaceable>module</replaceable></userinput> (or both, if they are both "
+"loaded). After that you can load the correct module using "
+"<userinput>modprobe <replaceable>module</replaceable></userinput>. Note that "
+"the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
@@ -1474,7 +1846,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1446
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid ""
+"The <literal>cassini</literal> network driver does not work with Sun B100 "
+"blade systems."
 msgstr ""
 
 #. Tag: title
@@ -1486,7 +1860,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1462
 #, no-c-format
-msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
+msgid ""
+"Support for braille displays is determined by the underlying support found "
+"in <classname>brltty</classname>. Most displays work under "
+"<classname>brltty</classname>, connected via either a serial port, USB or "
+"bluetooth. Details on supported braille devices can be found on the <ulink "
+"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-"
+"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
@@ -1498,7 +1878,15 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1477
 #, no-c-format
-msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
+msgid ""
+"Support for hardware speech synthesis devices is determined by the "
+"underlying support found in <classname>speakup</classname>. "
+"<classname>speakup</classname> only supports integrated boards and external "
+"devices connected to a serial port (no USB, serial-to-USB or PCI adapters "
+"are supported). Details on supported hardware speech synthesis devices can "
+"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> "
+"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</"
+"classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
@@ -1510,25 +1898,37 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1498
 #, no-c-format
-msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
+msgid ""
+"&arch-kernel; supports a large variety of hardware devices such as mice, "
+"printers, scanners, PCMCIA and USB devices. However, most of these devices "
+"are not required while installing the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1504
 #, no-c-format
-msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
+msgid ""
+"USB hardware generally works fine. On some very old PC systems some USB "
+"keyboards may require additional configuration (see <xref linkend=\"hardware-"
+"issues\"/>). On modern PCs, USB keyboards and mice work without requiring "
+"any specific configuration."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1513
 #, no-c-format
-msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
+msgid ""
+"Package installations from XPRAM and tape are not supported by this system. "
+"All packages that you want to install need to be available on a DASD or over "
+"the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1519
 #, no-c-format
-msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Cobalt RaQ has no support for additional devices but the Qube has one "
+"PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -1540,31 +1940,63 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1532
 #, no-c-format
-msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
+msgid ""
+"Besides the availability of a device driver, some hardware also requires so-"
+"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> "
+"to be loaded into the device before it can become operational. This is most "
+"common for network interface cards (especially wireless NICs), but for "
+"example some USB devices and even some hard disk controllers also require "
+"firmware. With many graphics cards, basic functionality is available without "
+"additional firmware, but the use of advanced features requires an "
+"appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1543
 #, no-c-format
-msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
+msgid ""
+"On many older devices which require firmware to work, the firmware file was "
+"permanently placed in an EEPROM/Flash chip on the device itself by the "
+"manufacturer. Nowadays most new devices do not have the firmware embedded "
+"this way anymore, so the firmware file must be uploaded into the device by "
+"the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1551
 #, no-c-format
-msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
+msgid ""
+"In most cases firmware is non-free according to the criteria used by the "
+"&debian-gnu; project and thus cannot be included in the main distribution or "
+"in the installation system. If the device driver itself is included in the "
+"distribution and if &debian-gnu; legally can distribute the firmware, it "
+"will often be available as a separate package from the non-free section of "
+"the archive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1560
 #, no-c-format
-msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
+msgid ""
+"However, this does not mean that such hardware cannot be used during an "
+"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading "
+"firmware files or packages containing firmware from a removable medium, such "
+"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed "
+"information on how to load firmware files or packages during the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1569
 #, no-c-format
-msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
+msgid ""
+"If the &d-i; prompts for a firmware file and you do not have this firmware "
+"file available or do not want to install a non-free firmware file on your "
+"system, you can try to proceed without loading the firmware. There are "
+"several cases where a driver prompts for additional firmware because it may "
+"be needed under certain circumstances, but the device does work without it "
+"on most systems (this e.g. happens with certain network cards using the tg3 "
+"driver)."
 msgstr ""
 
 #. Tag: title
@@ -1576,19 +2008,35 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1588
 #, no-c-format
-msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
+msgid ""
+"There are several vendors, who ship systems with &debian; or other "
+"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</"
+"ulink>. You might pay more for the privilege, but it does buy a level of "
+"peace of mind, since you can be sure that the hardware is well-supported by "
+"GNU/Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1596
 #, no-c-format
-msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
+msgid ""
+"If you do have to buy a machine with Windows bundled, carefully read the "
+"software license that comes with Windows; you may be able to reject the "
+"license and obtain a rebate from your vendor. Searching the Internet for "
+"<quote>windows refund</quote> may get you some useful information to help "
+"with that."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1604
 #, no-c-format
-msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with &arch-kernel; bundled, or "
+"even a used system, it is still important to check that your hardware is "
+"supported by the &arch-kernel; kernel. Check if your hardware is listed in "
+"the references found above. Let your salesperson (if any) know that you're "
+"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware "
+"vendors."
 msgstr ""
 
 #. Tag: title
@@ -1600,31 +2048,67 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1616
 #, no-c-format
-msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
+msgid ""
+"Some hardware manufacturers simply won't tell us how to write drivers for "
+"their hardware. Others won't allow us access to the documentation without a "
+"non-disclosure agreement that would prevent us from releasing the driver's "
+"source code, which is one of the central elements of free software. Since we "
+"haven't been granted access to usable documentation on these devices, they "
+"simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1626
 #, no-c-format
-msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
+msgid ""
+"In many cases there are standards (or at least some de-facto standards) "
+"describing how an operating system and its device drivers communicate with a "
+"certain class of devices. All devices which comply to such a (de-facto-)"
+"standard can be used with a single generic device driver and no device-"
+"specific drivers are required. With some kinds of hardware (e.g. USB "
+"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB "
+"mass storage devices like USB flash disks and memory card readers) this "
+"works very well and practically every device sold in the market is standards-"
+"compliant."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1638
 #, no-c-format
-msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
+msgid ""
+"In other fields, among them e.g. printers, this is unfortunately not the "
+"case. While there are many printers which can be addressed via a small set "
+"of (de-facto-)standard control languages and therefore can be made to work "
+"without problems in any operating system, there are quite a few models which "
+"only understand proprietary control commands for which no usable "
+"documentation is available and therefore either cannot be used at all on "
+"free operating systems or can only be used with a vendor-supplied closed-"
+"source driver."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1649
 #, no-c-format
-msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
+msgid ""
+"Even if there is a vendor-provided closed-source driver for such hardware "
+"when purchasing the device, the practical lifespan of the device is limited "
+"by driver availability. Nowadays product cycles have become short and it is "
+"not uncommon that a short time after a consumer device has ceased "
+"production, no driver updates get made available any more by the "
+"manufacturer. If the old closed-source driver does not work anymore after a "
+"system update, an otherwise perfectly working device becomes unusable due to "
+"lacking driver support and there is nothing that can be done in this case. "
+"You should therefore avoid buying closed hardware in the first place, "
+"regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1662
 #, no-c-format
-msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
+msgid ""
+"You can help improve this situation by encouraging manufacturers of closed "
+"hardware to release the documentation and other resources necessary for us "
+"to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
@@ -1636,7 +2120,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1679
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
+msgid ""
+"This section will help you determine which different media types you can use "
+"to install &debian;. There is a whole chapter devoted to media, <xref "
+"linkend=\"install-methods\"/>, which lists the advantages and disadvantages "
+"of each media type. You may want to refer back to this page once you reach "
+"that section."
 msgstr ""
 
 #. Tag: title
@@ -1648,7 +2137,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
+msgid ""
+"In some cases, you'll have to do your first boot from floppy disks. "
+"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch "
+"floppy drive."
 msgstr ""
 
 #. Tag: para
@@ -1666,7 +2158,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1705
 #, no-c-format
-msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
+msgid ""
+"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-"
+"ROMs and DVD-ROMs, because both technologies are really the same from the "
+"operating system's point of view."
 msgstr ""
 
 #. Tag: para
@@ -1684,7 +2179,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1719
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid ""
+"USB CD-ROM drives are also supported, as are FireWire devices that are "
+"supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
@@ -1696,7 +2193,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1728
 #, no-c-format
-msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
+msgid ""
+"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of "
+"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM "
+"drives sold on the PC market do not have this capability. If your CD-ROM "
+"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</"
+"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. "
+"To start the install, simply choose the <quote>System installation</quote> "
+"entry in the firmware."
 msgstr ""
 
 #. Tag: title
@@ -1708,7 +2212,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1744
 #, no-c-format
-msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
+msgid ""
+"USB flash disks a.k.a. USB memory sticks have become a commonly used and "
+"cheap storage device. Most modern computer systems also allow booting the &d-"
+"i; from such a stick. Many modern computer systems, in particular netbooks "
+"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting "
+"from USB media ist the standard way of installing a new operating system on "
+"them."
 msgstr ""
 
 #. Tag: title
@@ -1720,19 +2230,36 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1758
 #, no-c-format
-msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
+msgid ""
+"The network can be used during the installation to retrieve files needed for "
+"the installation. Whether the network is used or not depends on the "
+"installation method you choose and your answers to certain questions that "
+"will be asked during the installation. The installation system supports most "
+"types of network connections (including PPPoE, but not ISDN or PPP), via "
+"either HTTP or FTP. After the installation is completed, you can also "
+"configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1768
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> the installation system over the "
+"network without needing any local media like CDs/DVDs or USB sticks. If you "
+"already have a netboot-infrastructure available (i.e. you are already "
+"running DHCP and TFTP services in your network), this allows an easy and "
+"fast deployment of a large number of machines. Setting up the necessary "
+"infrastructure requires a certain level of technical experience, so this is "
+"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the "
+"preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1781
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+msgid ""
+"Diskless installation, using network booting from a local area network and "
+"NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
@@ -1744,13 +2271,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1792
 #, no-c-format
-msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
+msgid ""
+"Booting the installation system directly from a hard disk is another option "
+"for many architectures. This will require some other operating system to "
+"load the installer onto the hard disk. This method is only recommended for "
+"special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1799
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid ""
+"Although the &arch-title; does not allow booting from SunOS (Solaris), you "
+"can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
@@ -1762,7 +2295,14 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1810
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian-gnu; without using the &d-i; described in the rest of this manual. "
+"This kind of install may be useful for users with otherwise unsupported "
+"hardware or on hosts which can't afford downtime. If you are interested in "
+"this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This "
+"installation method is only recommended for advanced users when no other "
+"installation method is available."
 msgstr ""
 
 #. Tag: title
@@ -1774,43 +2314,69 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1825
 #, no-c-format
-msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
+msgid ""
+"The &debian; installer contains a kernel which is built to maximize the "
+"number of systems it runs on."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1829
 #, no-c-format
-msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+msgid ""
+"Generally, the &debian; installation system includes support for IDE (also "
+"known as PATA) drives, SATA and SCSI controllers and drives, USB, and "
+"FireWire. The supported file systems include FAT, Win-32 FAT extensions "
+"(VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1846
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. The following SCSI drivers are supported in the default kernel: "
+"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> "
+"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec "
+"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></"
+"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also "
+"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC "
+"Processors FAQ</ulink> for more information on SPARC hardware supported by "
+"the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1879
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support floppies on "
+"CHRP systems at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. Note that the current Linux kernel does not support the floppy "
+"drive."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1891
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1896
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This means that FBA and ECKD DASDs are supported with the old "
+"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
@@ -1822,12 +2388,22 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1915
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space to perform a normal installation. Note that these are fairly "
+"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-"
+"hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1922
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgid ""
+"Installation on systems with less memory<footnote condition=\"gtk\"> <para> "
+"Installation images that support the graphical installer require more memory "
+"than images that support only the textual installer and should not be used "
+"on systems with less than &minimum-memory; of memory. If there is a choice "
+"between booting the regular and the graphical installer, the former should "
+"be selected. </para> </footnote> or disk space available may be possible but "
+"is only advised for experienced users."
 msgstr ""
-
diff --git a/po/tl/install-methods.po b/po/tl/install-methods.po
index c164d8428..6f56f6790 100644
--- a/po/tl/install-methods.po
+++ b/po/tl/install-methods.po
@@ -5,10 +5,11 @@ msgid ""
 msgstr ""
 "Project-Id-Version: d-i-manual_install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+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"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,1149 +29,1719 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian-gnu; is from an Official &debian; CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/DVD-ROM images from a &debian; mirror and make your own set, if you have a fast network connection and a CD/DVD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, which is the case on all modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/>. Much effort has been expended to ensure the most-used files are on the first CDs and DVDs, so that a basic desktop installation can be done with only the first DVD or - to a limited extent - even with only the first CD."
+msgid ""
+"By far the easiest way to install &debian-gnu; is from an Official &debian; "
+"CD/DVD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-"
+"debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD/"
+"DVD-ROM images from a &debian; mirror and make your own set, if you have a "
+"fast network connection and a CD/DVD burner (see the <ulink url=\"&url-"
+"debian-cd;\">Debian CD page</ulink> and <ulink url=\"&url-debian-cd-faq;"
+"\">Debian CD FAQ</ulink> for detailed instructions). If you have a &debian; "
+"CD/DVD set and CDs/DVDs are bootable on your machine<phrase arch=\"x86\">, "
+"which is the case on all modern PCs</phrase>, you can skip right to <xref "
+"linkend=\"boot-installer\"/>. Much effort has been expended to ensure the "
+"most-used files are on the first CDs and DVDs, so that a basic desktop "
+"installation can be done with only the first DVD or - to a limited extent - "
+"even with only the first CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs."
+msgid ""
+"As CDs have a rather limited capacity by today's standards, not all "
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid ""
+"If your machine doesn't support CD booting<phrase arch=\"x86\"> (only "
+"relevant on very old PC systems)</phrase>, but you do have a CD set, you can "
+"use an alternative strategy such as <phrase condition=\"supports-floppy-boot"
+"\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition="
+"\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net "
+"boot,</phrase> or manually loading the kernel from the CD to initially boot "
+"the system installer. The files you need for booting by another means are "
+"also on the CD; the &debian; network archive and CD folder organization are "
+"identical. So when archive file paths are given below for particular files "
+"you need for booting, look for those files in the same directories and "
+"subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
-msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a &debian; mirror using FTP, be sure to download "
+"the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
-msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each &debian; mirror in the directory "
+"<ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
-msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;."
+msgid ""
+"A firmware image is provided for the Thecus N2100 which will automatically "
+"boot <classname>debian-installer</classname>. This image can be installed "
+"using the Thecus firmware upgrade process. This firmware image can be "
+"obtained from &n2100-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
-msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;."
+msgid ""
+"The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
+"on which you intend to install &debian;. These images can be obtained from "
+"&glantank-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
-msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;."
+msgid ""
+"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
+"disk on which you intend to install &debian;. These images can be obtained "
+"from &kuroboxpro-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
-msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;."
+msgid ""
+"A firmware image is provided for the HP mv2120 which will automatically boot "
+"<classname>debian-installer</classname>. This image can be installed with "
+"uphpmvault on Linux and other systems and with the HP Media Vault Firmware "
+"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-"
+"firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
-msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;."
+msgid ""
+"The installation files for the QNAP Turbo Station consist of a kernel and "
+"ramdisk as well as a script to write these images to flash. You can obtain "
+"the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-"
+"kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
-msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;."
+msgid ""
+"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
+"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can "
+"obtain these files from &kirkwood-marvell-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, no-c-format
 msgid "LaCie NASes Installation Files"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
-msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;."
+msgid ""
+"The installation files for LaCie NASes (Network Space v2, Network Space Max "
+"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) "
+"consist of a kernel and initrd for U-Boot. You can obtain these files from "
+"&lacie-kirkwood-firmware-img;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
-msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
+msgid ""
+"Bootable floppy disks are generally used as a last resort to boot the "
+"installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
-msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
+msgid ""
+"Booting the installer from floppy disk reportedly fails on Mac USB floppy "
+"drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images. This "
+"section describes how to create floppies from disk images on different "
+"platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
-msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
+msgid ""
+"Before you can create the floppies, you will first need to download them "
+"from one of the &debian; mirrors, as explained in <xref linkend="
+"\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an "
+"installation CD-ROM or DVD, the floppy images may also be included on the CD/"
+"DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
-msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
+msgid ""
+"No matter which method you use to create your floppies, you should remember "
+"to flip the write-protect tab on the floppies once you have written them, to "
+"ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
-      "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
-      "$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-      "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> (on Solaris, use <command>eject</command>, see the manual page)</phrase>."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:337
+"To write the floppy disk image files to the floppy disks, you will probably "
+"need root access to the system. Place a good, blank floppy in the floppy "
+"drive. Next, use the command <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files. <filename>/dev/fd0</filename> is a commonly "
+"used name of the floppy disk device, it may be different on your "
+"workstation<phrase arch=\"sparc\"> (on Solaris, it is <filename>/dev/fd/0</"
+"filename>)</phrase>. The command may return to the prompt before Unix has "
+"finished writing the floppy disk, so look for the disk-in-use light on the "
+"floppy drive and be sure that the light is out and the disk has stopped "
+"revolving before you remove it from the drive. On some systems, you'll have "
+"to run a command to eject the floppy from the drive <phrase arch=\"sparc\"> "
+"(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:336
 #, no-c-format
-msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+msgid ""
+"Some systems attempt to automatically mount a floppy disk when you place it "
+"in the drive. You might have to disable this feature before the workstation "
+"will allow you to write a floppy in <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume "
+"management to get raw access to the floppy. First, make sure that the floppy "
+"is auto-mounted (using <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
-msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 or amd64 machine, you can use one of the "
+"following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> programs can "
+"be used under MS-DOS. To use these programs, first make sure that you are "
+"booted into DOS. Trying to use these programs from within a DOS box in "
+"Windows, or double-clicking on these programs from the Windows Explorer is "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
-msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
+msgid ""
+"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
+"ME, XP and probably later versions. To use it you will need to unpack diskio."
+"dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
-msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official &debian; CD-ROMs under the "
+"<filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
-msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
+msgid ""
+"An AppleScript, <application>Make &debian; Floppy</application>, is "
+"available for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on "
+"your desktop, and then drag any floppy image file to it. You must have "
+"Applescript installed and enabled in your extensions manager. Disk Copy will "
+"ask you to confirm that you wish to erase the floppy and proceed to write "
+"the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> file is an example of a floppy image. Use one of the following "
+"methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian-gnu; CD, then the Type and Creator are already set "
+"correctly. The following <command>Creator-Changer</command> steps are only "
+"necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> image file from the "
+"resulting dialog. It will ask you to insert a floppy, then ask if you really "
+"want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
-msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
+msgid ""
+"To prepare the USB stick, you will need a system where GNU/Linux is already "
+"running and where USB is supported. With current GNU/Linux systems the USB "
+"stick should be automatically recognized when you insert it. If it is not "
+"you should check that the usb-storage kernel module is loaded. When the USB "
+"stick is inserted, it will be mapped to a device named <filename>/dev/sdX</"
+"filename>, where the <quote>X</quote> is a letter in the range a-z. You "
+"should be able to see to which device the USB stick was mapped by running "
+"the command <command>dmesg</command> after inserting it. To write to your "
+"stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
-msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
+msgid ""
+"The procedures described in this section will destroy anything already on "
+"the device! Make very sure that you use the correct device name for your USB "
+"stick. If you use the wrong device the result could be that all information "
+"on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
-msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
+msgid ""
+"Debian CD and DVD images can now be written directly a USB stick, which is a "
+"very easy way to make a bootable USB stick. Simply choose a CD or DVD image "
+"that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to "
+"get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
-msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
+msgid ""
+"Alternatively, for very small USB sticks, only a few megabytes in size, you "
+"can download the <filename>mini.iso</filename> image from the "
+"<filename>netboot</filename> directory (at the location mentioned in <xref "
+"linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
-msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it."
+msgid ""
+"A special method can be used to add firmware to the <filename>mini.iso</"
+"filename>. First, write the <filename>mini.iso</filename> to the USB stick. "
+"Next obtain the necessary firmware files. See <xref linkend=\"loading-"
+"firmware\"/> for more information about firmware. Now unplug and replug the "
+"USB stick, and two partitions should now be visible on it. You should mount "
+"the second of the two partitions, and unpack the firmware onto it."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
-      "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
-      "# cd /mnt\n"
-      "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
-      "# cd /\n"
-      "# umount"
+"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
+"# cd /mnt\n"
+"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n"
+"# cd /\n"
+"# umount"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
-msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
+msgid ""
+"The CD or DVD image you choose should be written directly to the USB stick, "
+"overwriting its current contents. For example, when using an existing GNU/"
+"Linux system, the CD or DVD image file can be written to a USB stick as "
+"follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
-      "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
-      "<prompt>#</prompt> <userinput>sync</userinput>"
+"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
+"<replaceable>sdX</replaceable></userinput>\n"
+"<prompt>#</prompt> <userinput>sync</userinput>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
-msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
+msgid ""
+"Simply writing the CD or DVD image to USB like this should work fine for "
+"most users. The other options below are more complex, mainly for people with "
+"specialised needs."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
-msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"An alternative way to set up your USB stick is to manually copy the "
+"installer files, and also a CD image to it. Note that the USB stick should "
+"be at least 1 GB in size (smaller setups are possible if you follow <xref "
+"linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
-msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
+msgid ""
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) <phrase arch="
+"\"x86\">as well as <classname>syslinux</classname> and its configuration "
+"file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</"
+"classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
-msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
+msgid ""
+"Note that, although convenient, this method does have one major "
+"disadvantage: the logical size of the device will be limited to 1 GB, even "
+"if the capacity of the USB stick is larger. You will need to repartition the "
+"USB stick and create new file systems to get its full capacity back if you "
+"ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
-msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
+msgid ""
+"Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
+"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract "
+"the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, no-c-format
-msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"After that, mount the USB memory stick <phrase arch=\"x86\">"
+"(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</"
+"phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</"
+"replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch="
+"\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS "
+"filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full "
+"CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you "
+"are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
-msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
+msgid ""
+"If you like more flexibility or just want to know what's going on, you "
+"should use the following method to put the files on your stick. One "
+"advantage of using this method is that &mdash; if the capacity of your USB "
+"stick is large enough &mdash; you have the option of copying a full CD ISO "
+"image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
-msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to set up the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
-      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
-      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
-      "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
+"Since most USB sticks come pre-configured with a single FAT16 partition, you "
+"probably won't have to repartition or reformat the stick. If you have to do "
+"that anyway, use <command>cfdisk</command> or any other partitioning tool to "
+"create a FAT16 partition<footnote> <para> Don't forget to set the "
+"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR "
+"using: <informalexample><screen>\n"
+"# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+"</screen></informalexample> The <command>install-mbr</command> command is "
+"contained in the <classname>mbr</classname> &debian; package. Then create "
+"the filesystem using: <informalexample><screen>\n"
+"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. Although any boot loader (e.g. <classname>lilo</"
+"classname>) should work, it's convenient to use <classname>syslinux</"
+"classname>, since it uses a FAT16 partition and can be reconfigured by just "
+"editing a text file. Any operating system which supports the FAT file system "
+"can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
-      "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
-      "# syslinux /dev/<replaceable>sdX1</replaceable>\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>syslinux</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"To put <classname>syslinux</classname> on the FAT16 partition on your USB "
+"stick, install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
+"# syslinux /dev/<replaceable>sdX1</replaceable>\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>syslinux</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick: "
+"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or "
+"<filename>linux</filename> (kernel binary) </para></listitem> "
+"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </"
+"para></listitem> </itemizedlist> You can choose between either the regular "
+"version or the graphical version of the installer. The latter can be found "
+"in the <filename>gtk</filename> subdirectory. If you want to rename the "
+"files, please note that <classname>syslinux</classname> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, no-c-format
 msgid ""
-      "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
-      "default vmlinuz\n"
-      "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
+"Next you should create a <filename>syslinux.cfg</filename> configuration "
+"file, which at a bare minimum should contain the following two lines (change "
+"the name of the kernel binary to <quote><filename>linux</filename></quote> "
+"if you used a <filename>netboot</filename> image): "
+"<informalexample><screen>\n"
+"default vmlinuz\n"
+"append initrd=initrd.gz\n"
+"</screen></informalexample> For the graphical installer you should add "
+"<userinput>vga=788</userinput> to the second line. Other parameters can be "
+"appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
-msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgid ""
+"To enable the boot prompt to permit further parameter appending, add a "
+"<userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
-msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
+msgid ""
+"If you used an <filename>hd-media</filename> image, you should now copy the "
+"ISO file of a &debian; ISO image<footnote> <para> You can use either a "
+"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure "
+"to select one that fits. Note that the <quote>netboot <filename>mini.iso</"
+"filename></quote> image is not usable for this purpose. </para> </footnote> "
+"onto the stick. When you are done, unmount the USB memory stick "
+"(<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
-      "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
-      "$ hformat /dev/<replaceable>sdX2</replaceable>\n"
-      "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> &debian; package."
+"Most USB sticks do not come pre-configured in such a way that Open Firmware "
+"can boot from them, so you will need to repartition the stick. On Mac "
+"systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></"
+"userinput>, initialise a new partition map using the <userinput>i</"
+"userinput> command, and create a new partition of type Apple_Bootstrap using "
+"the <userinput>C</userinput> command. (Note that the first \"partition\" "
+"will always be the partition map itself.) Then type "
+"<informalexample><screen>\n"
+"$ hformat /dev/<replaceable>sdX2</replaceable>\n"
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> boot loader can be "
+"installed on an HFS filesystem and can be reconfigured by just editing a "
+"text file. Any operating system which supports the HFS file system can be "
+"used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
-      "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
-      "$ hmount /dev/<replaceable>sdX2</replaceable>\n"
-      "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
-      "$ hattrib -c UNIX -t tbxi :yaboot\n"
-      "$ hattrib -b :\n"
-      "$ humount\n"
-      "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:857
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
+"$ hmount /dev/<replaceable>sdX2</replaceable>\n"
+"$ hcopy -r /usr/lib/yaboot/yaboot :\n"
+"$ hattrib -c UNIX -t tbxi :yaboot\n"
+"$ hattrib -b :\n"
+"$ humount\n"
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be otherwise mounted during this procedure. "
+"This procedure writes the boot loader to the partition, and uses the HFS "
+"utilities to mark it in such a way that Open Firmware will boot it. Having "
+"done this, the rest of the USB stick may be prepared using the normal Unix "
+"utilities."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:856
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
+"mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
-      "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
-      "default=install\n"
-      "root=/dev/ram\n"
-      "\n"
-      "message=/boot.msg\n"
-      "\n"
-      "image=/vmlinux\n"
-      "        label=install\n"
-      "        initrd=/initrd.gz\n"
-      "        initrd-size=10000\n"
-      "        read-only\n"
-      "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
+"default=install\n"
+"root=/dev/ram\n"
+"\n"
+"message=/boot.msg\n"
+"\n"
+"image=/vmlinux\n"
+"        label=install\n"
+"        initrd=/initrd.gz\n"
+"        initrd-size=10000\n"
+"        read-only\n"
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
-msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
+msgid ""
+"The installer may be booted using boot files placed on an existing hard "
+"drive partition, either launched from another operating system or by "
+"invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
-msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+msgid ""
+"The installer cannot boot from files on an HFS+ file system. MacOS System "
+"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To "
+"determine whether your existing file system is HFS+, select <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
-msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
+msgid ""
+"At boot time, both bootloaders support loading in memory not only the "
+"kernel, but also a disk image. This RAM disk can be used as the root file-"
+"system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
-msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the &debian; archives to a convenient location "
+"on your hard drive (note that LILO can not boot from files on an NTFS file "
+"system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
-msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
+msgid ""
+"This section explains how to prepare your hard drive for booting the "
+"installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
-msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
+msgid ""
+"Copy the following directories from a &debian; CD image to <filename>c:\\</"
+"filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
-msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
+msgid ""
+"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your &debian; installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on &debian; http/ftp mirrors and official &debian; CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
-msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+msgid ""
+"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
+"well as loading ELF binaries directly from the hard disk. These machines "
+"will boot Linux directly via <command>yaboot</command>, which supports "
+"loading a kernel and RAMdisk directly from an ext2 partition, as well as "
+"dual-booting with MacOS. Hard disk booting of the installer is particularly "
+"appropriate for newer machines without floppy drives. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (not move) the following four files which you "
+"downloaded earlier from the &debian; archives, onto the root level of your "
+"hard drive (this can be accomplished by <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the <command>L</command> command to check for the partition number. You "
+"will need this partition number for the command you type at the Open "
+"Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
-msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
+msgid ""
+"If your machine is connected to a local area network, you may be able to "
+"boot it over the network from another machine, using TFTP. If you intend to "
+"boot the installation system from another machine, the boot files will need "
+"to be placed in specific locations on that machine, and the machine "
+"configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
-msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
+msgid ""
+"You need to set up a TFTP server, and for many machines a DHCP server<phrase "
+"condition=\"supports-rarp\">, or RARP server</phrase><phrase condition="
+"\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol.</phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image.</phrase> The DHCP "
+"(Dynamic Host Configuration Protocol) is a more flexible, backwards-"
+"compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
-msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
+msgid ""
+"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
+"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to "
+"boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
-msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
+msgid ""
+"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
+"the client. Theoretically, any server, on any platform, which implements "
+"these protocols, may be used. In the examples in this section, we shall "
+"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
-msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
+msgid ""
+"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
+"It's written by the same author as the <classname>syslinux</classname> "
+"bootloader and is therefore least likely to cause issues. A good alternative "
+"is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
-msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
+msgid ""
+"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
+"address) of the client computers to be installed. If you don't know this "
+"information, you can <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>ip addr show dev eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
+msgid ""
+"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
+"you use the <command>rarpd</command> program. You need to ensure that the "
+"Ethernet hardware address for the client is listed in the <quote>ethers</"
+"quote> database (either in the <filename>/etc/ethers</filename> file, or via "
+"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start "
+"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</"
+"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/"
+"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/"
+"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid ""
+"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
+"gnu;, the <classname>dhcp3-server</classname> package is recommended. Here "
+"is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</"
+"filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
-      "option domain-name \"example.com\";\n"
-      "option domain-name-servers ns1.example.com;\n"
-      "option subnet-mask 255.255.255.0;\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "server-name \"servername\";\n"
-      "\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option routers 192.168.1.1;\n"
-      "}\n"
-      "\n"
-      "host clientname {\n"
-      "  filename \"/tftpboot.img\";\n"
-      "  server-name \"servername\";\n"
-      "  next-server servername;\n"
-      "  hardware ethernet 01:23:45:67:89:AB;\n"
-      "  fixed-address 192.168.1.90;\n"
-      "}"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1237
+"option domain-name \"example.com\";\n"
+"option domain-name-servers ns1.example.com;\n"
+"option subnet-mask 255.255.255.0;\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"server-name \"servername\";\n"
+"\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option routers 192.168.1.1;\n"
+"}\n"
+"\n"
+"host clientname {\n"
+"  filename \"/tftpboot.img\";\n"
+"  server-name \"servername\";\n"
+"  next-server servername;\n"
+"  hardware ethernet 01:23:45:67:89:AB;\n"
+"  fixed-address 192.168.1.90;\n"
+"}"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1236
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1256
-#, no-c-format
-msgid ""
-      "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
-      "option domain-name \"example.com\";\n"
-      "\n"
-      "default-lease-time 600;\n"
-      "max-lease-time 7200;\n"
-      "\n"
-      "allow booting;\n"
-      "allow bootp;\n"
-      "\n"
-      "# The next paragraph needs to be modified to fit your case\n"
-      "subnet 192.168.1.0 netmask 255.255.255.0 {\n"
-      "  range 192.168.1.200 192.168.1.253;\n"
-      "  option broadcast-address 192.168.1.255;\n"
-      "# the gateway address which can be different\n"
-      "# (access to the internet for instance)\n"
-      "  option routers 192.168.1.1;\n"
-      "# indicate the dns you want to use\n"
-      "  option domain-name-servers 192.168.1.3;\n"
-      "}\n"
-      "\n"
-      "group {\n"
-      "  next-server 192.168.1.3;\n"
-      "  host tftpclient {\n"
-      "# tftp client hardware address\n"
-      "  hardware ethernet  00:10:DC:27:6C:15;\n"
-      "  filename \"pxelinux.0\";\n"
-      " }\n"
-      "}\n"
-      "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+#: install-methods.xml:1255
+#, no-c-format
+msgid ""
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"option domain-name \"example.com\";\n"
+"\n"
+"default-lease-time 600;\n"
+"max-lease-time 7200;\n"
+"\n"
+"allow booting;\n"
+"allow bootp;\n"
+"\n"
+"# The next paragraph needs to be modified to fit your case\n"
+"subnet 192.168.1.0 netmask 255.255.255.0 {\n"
+"  range 192.168.1.200 192.168.1.253;\n"
+"  option broadcast-address 192.168.1.255;\n"
+"# the gateway address which can be different\n"
+"# (access to the internet for instance)\n"
+"  option routers 192.168.1.1;\n"
+"# indicate the dns you want to use\n"
+"  option domain-name-servers 192.168.1.3;\n"
+"}\n"
+"\n"
+"group {\n"
+"  next-server 192.168.1.3;\n"
+"  host tftpclient {\n"
+"# tftp client hardware address\n"
+"  hardware ethernet  00:10:DC:27:6C:15;\n"
+"  filename \"pxelinux.0\";\n"
+" }\n"
+"}\n"
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux. The first is CMU "
+"<command>bootpd</command>. The other is actually a DHCP server: ISC "
+"<command>dhcpd</command>. In &debian-gnu; these are contained in the "
+"<classname>bootp</classname> and <classname>dhcp3-server</classname> "
+"packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
-      "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
-      "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-      "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
-      "client:\\\n"
-      "  hd=/tftpboot:\\\n"
-      "  bf=tftpboot.img:\\\n"
-      "  ip=192.168.1.90:\\\n"
-      "  sm=255.255.255.0:\\\n"
-      "  sa=192.168.1.1:\\\n"
-      "  ha=0123456789AB:\n"
-      "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:1318
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you "
+"can run <userinput>update-inetd --enable bootps</userinput>, then "
+"<userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your "
+"BOOTP server does not run &debian;, the line in question should look like: "
+"<informalexample><screen>\n"
+"bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
+"client:\\\n"
+"  hd=/tftpboot:\\\n"
+"  bf=tftpboot.img:\\\n"
+"  ip=192.168.1.90:\\\n"
+"  sm=255.255.255.0:\\\n"
+"  sa=192.168.1.1:\\\n"
+"  ha=0123456789AB:\n"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI machines you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:1317
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd."
+"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/"
+"init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
-msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
+msgid ""
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
-msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
+msgid ""
+"In the case of <classname>tftpd-hpa</classname> there are two ways the "
+"service can be run. It can be started on demand by the system's "
+"<classname>inetd</classname> daemon, or it can be set up to run as an "
+"independent daemon. Which of these methods is used is selected when the "
+"package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
-msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
+msgid ""
+"Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
+"to serve images from. However, &debian-gnu; packages may use other "
+"directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by "
+"default uses <filename>/srv/tftp</filename>. You may have to adjust the "
+"configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
-msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
+msgid ""
+"All <command>in.tftpd</command> alternatives available in &debian; should "
+"log TFTP requests to the system logs by default. Some of them support a "
+"<userinput>-v</userinput> argument to increase verbosity. It is recommended "
+"to check these log messages in case of boot problems as they are a good "
+"starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
-      "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
-      "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-      "</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n"
-      "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-      "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"If you intend to install &debian; on an SGI machine and your TFTP server is "
+"a GNU/Linux box running Linux 2.4, you'll need to set the following on your "
+"server: <informalexample><screen>\n"
+"# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets "
+"are sent from a source port no greater than 32767, or the download will "
+"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in "
+"the PROM, and you can avoid it by setting <informalexample><screen>\n"
+"# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. You may "
+"have to make a link from that file to the file which <command>tftpd</"
+"command> will use for booting a particular client. Unfortunately, the file "
+"name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. You will need to download the following files from the "
+"<filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
-      "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-      "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
-      "</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"Some SPARC architectures add the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your "
+"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename "
+"would be <filename>C0A80103.SUN4C</filename>. However, there are also "
+"subarchitectures where the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. An easy way to determine the "
+"hexadecimal code for the IP address is to enter the following command in a "
+"shell (assuming the machine's intended IP is 10.0.0.4). "
+"<informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> To get to the correct filename, you will need to "
+"change all letters to uppercase and if necessary append the subarchitecture "
+"name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
-msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
+msgid ""
+"If you've done all this correctly, giving the command <userinput>boot net</"
+"userinput> from the OpenPROM should load the image. If the image cannot be "
+"found, try checking the logs on your tftp server to see which image name is "
+"being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
-msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+msgid ""
+"You can also force some sparc systems to look for a specific file name by "
+"adding it to the end of the OpenPROM boot command, such as <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
-msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI machines you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. &debian; packages intended for this include <classname>fai-"
+"quickstart</classname> (which can use an install server) and the &debian; "
+"Installer itself. Have a look at the <ulink url=\"http://fai-project.org"
+"\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
-msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
+msgid ""
+"The &debian; Installer supports automating installs via preconfiguration "
+"files. A preconfiguration file can be loaded from the network or from "
+"removable media, and used to fill in answers to questions asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
-msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
+msgid ""
+"Full documentation on preseeding including a working example that you can "
+"edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
-
diff --git a/po/tl/installation-howto.po b/po/tl/installation-howto.po
index 6b8f358e5..369f718c1 100644
--- a/po/tl/installation-howto.po
+++ b/po/tl/installation-howto.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:7
 #, no-c-format
-msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document."
+msgid ""
+"This document describes how to install &debian-gnu; &releasename; for the "
+"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a "
+"quick walkthrough of the installation process which should contain all the "
+"information you will need for most installs. When more information can be "
+"useful, we will link to more detailed explanations in other parts of this "
+"document."
 msgstr ""
 
 #. Tag: title
@@ -34,7 +41,13 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:20
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)."
+msgid ""
+"<phrase condition=\"unofficial-build\"> The debian-installer is still in a "
+"beta state. </phrase> If you encounter bugs during your install, please "
+"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report "
+"them. If you have questions which cannot be answered by this document, "
+"please direct them to the debian-boot mailing list (&email-debian-boot-"
+"list;) or ask on IRC (#debian-boot on the OFTC network)."
 msgstr ""
 
 #. Tag: title
@@ -46,19 +59,30 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:37
 #, no-c-format
-msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>."
+msgid ""
+"<phrase condition=\"unofficial-build\"> For some quick links to CD images, "
+"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> "
+"The debian-cd team provides builds of CD images using &d-i; on the <ulink "
+"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on "
+"where to get CDs, see <xref linkend=\"official-cdrom\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:47
 #, no-c-format
-msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on &debian; mirrors."
+msgid ""
+"Some installation methods require other images than CD images. <phrase "
+"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home "
+"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files"
+"\"/> explains how to find images on &debian; mirrors."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:57
 #, no-c-format
-msgid "The subsections below will give the details about which images you should get for each possible means of installation."
+msgid ""
+"The subsections below will give the details about which images you should "
+"get for each possible means of installation."
 msgstr ""
 
 #. Tag: title
@@ -70,13 +94,26 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:67
 #, no-c-format
-msgid "The netinst CD image is a popular image which can be used to install &releasename; with the &d-i;. This image is intended to boot from CD and install additional packages over a network; hence the name 'netinst'. The image has the software components needed to run the installer and the base packages to provide a minimal &releasename; system. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set."
+msgid ""
+"The netinst CD image is a popular image which can be used to install "
+"&releasename; with the &d-i;. This image is intended to boot from CD and "
+"install additional packages over a network; hence the name 'netinst'. The "
+"image has the software components needed to run the installer and the base "
+"packages to provide a minimal &releasename; system. If you'd rather, you can "
+"get a full size CD image which will not need the network to install. You "
+"only need the first CD of the set."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:77
 #, no-c-format
-msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>"
+msgid ""
+"Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-"
+"x86\">To boot the CD, you may need to change your BIOS configuration, as "
+"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc"
+"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while "
+"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -88,31 +125,50 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:92
 #, no-c-format
-msgid "If you can't boot from CD, you can download floppy images to install &debian;. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks."
+msgid ""
+"If you can't boot from CD, you can download floppy images to install "
+"&debian;. You need the <filename>floppy/boot.img</filename>, the "
+"<filename>floppy/root.img</filename> and one or more of the driver disks."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:98
 #, no-c-format
-msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy &mdash; use the one with <filename>root.img</filename> on it."
+msgid ""
+"The boot floppy is the one with <filename>boot.img</filename> on it. This "
+"floppy, when booted, will prompt you to insert a second floppy &mdash; use "
+"the one with <filename>root.img</filename> on it."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:104
 #, no-c-format
-msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>."
+msgid ""
+"If you're planning to install over the network, you will usually need the "
+"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, "
+"and some less common network cards, you will also need a second driver "
+"floppy, <filename>floppy/net-drivers-2.img</filename>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:111
 #, no-c-format
-msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD."
+msgid ""
+"If you have a CD, but cannot boot from it, then boot from floppies and use "
+"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the "
+"install using the CD."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:117
 #, no-c-format
-msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them."
+msgid ""
+"Floppy disks are one of the least reliable media around, so be prepared for "
+"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each "
+"<filename>.img</filename> file you downloaded goes on a single floppy; you "
+"can use the dd command to write it to /dev/fd0 or some other means (see "
+"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than "
+"one floppy, it's a good idea to label them."
 msgstr ""
 
 #. Tag: title
@@ -124,37 +180,62 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:131
 #, no-c-format
-msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy &debian; install medium that you can take with you anywhere."
+msgid ""
+"It's also possible to install from removable USB storage devices. For "
+"example a USB keychain can make a handy &debian; install medium that you can "
+"take with you anywhere."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:137
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download any Debian "
+"CD or DVD image that will fit on it, and write the CD image directly to the "
+"memory stick. Of course this will destroy anything already on the memory "
+"stick. This works because Debian CD images are \"isohybrid\" images that can "
+"boot both from CD and from USB drives."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:145
 #, no-c-format
-msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from that file. Write this image directly to your memory stick, which must be at least 1 GB in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>."
+msgid ""
+"The easiest way to prepare your USB memory stick is to download <filename>hd-"
+"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from "
+"that file. Write this image directly to your memory stick, which must be at "
+"least 1 GB in size. Of course this will destroy anything already on the "
+"memory stick. Then mount the memory stick, which will now have a FAT "
+"filesystem on it. Next, download a &debian; netinst CD image, and copy that "
+"file to the memory stick; any filename is ok as long as it ends in <literal>."
+"iso</literal>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:156
 #, no-c-format
-msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
+msgid ""
+"There are other, more flexible ways to set up a memory stick to use the "
+"debian-installer, and it's possible to get it to work with smaller memory "
+"sticks. For details, see <xref linkend=\"boot-usb-files\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:162
 #, no-c-format
-msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Some BIOSes can boot USB storage directly, and some cannot. You may need to "
+"configure your BIOS to boot from a <quote>removable drive</quote> or even a "
+"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful "
+"hints and details, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:169
 #, no-c-format
-msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
+msgid ""
+"Booting Macintosh systems from USB storage devices involves manual use of "
+"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>."
 msgstr ""
 
 #. Tag: title
@@ -166,13 +247,22 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:179
 #, no-c-format
-msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;."
+msgid ""
+"It's also possible to boot &d-i; completely from the net. The various "
+"methods to netboot depend on your architecture and netboot setup. The files "
+"in <filename>netboot/</filename> can be used to netboot &d-i;."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:185
 #, no-c-format
-msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>."
+msgid ""
+"The easiest thing to set up is probably PXE netbooting. Untar the file "
+"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</"
+"filename> or wherever is appropriate for your tftp server. Set up your DHCP "
+"server to pass filename <filename>pxelinux.0</filename> to clients, and with "
+"luck everything will just work. For detailed instructions, see <xref linkend="
+"\"install-tftp\"/>."
 msgstr ""
 
 #. Tag: title
@@ -184,7 +274,15 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:200
 #, no-c-format
-msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>"
+msgid ""
+"It's possible to boot the installer using no removable media, but just an "
+"existing hard disk, which can have a different OS on it. Download "
+"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</"
+"filename>, and a &debian; CD image to the top-level directory of the hard "
+"disk. Make sure that the CD image has a filename ending in <literal>.iso</"
+"literal>. Now it's just a matter of booting linux with the initrd. <phrase "
+"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </"
+"phrase>"
 msgstr ""
 
 #. Tag: title
@@ -196,91 +294,156 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:218
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
+msgid ""
+"Once the installer starts, you will be greeted with an initial screen. Press "
+"&enterkey; to boot, or read the instructions for other boot methods and "
+"parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:224
 #, no-c-format
-msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
+msgid ""
+"After a while you will be asked to select your language. Use the arrow keys "
+"to pick a language and press &enterkey; to continue. Next you'll be asked to "
+"select your country, with the choices including countries where your "
+"language is spoken. If it's not on the short list, a list of all the "
+"countries in the world is available."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:232
 #, no-c-format
-msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
+msgid ""
+"You may be asked to confirm your keyboard layout. Choose the default unless "
+"you know better."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:237
 #, no-c-format
-msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
+msgid ""
+"Now sit back while debian-installer detects some of your hardware, and loads "
+"the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:242
 #, no-c-format
-msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
+msgid ""
+"Next the installer will try to detect your network hardware and set up "
+"networking by DHCP. If you are not on a network or do not have DHCP, you "
+"will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:248
 #, no-c-format
-msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones."
+msgid ""
+"The next step is setting up your clock and time zone. The installer will try "
+"to contact a time server on the Internet to ensure the clock is set "
+"correctly. The time zone is based on the country selected earlier and the "
+"installer will only ask to select one if a country has multiple zones."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:255
 #, no-c-format
-msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"Now it is time to partition your disks. First you will be given the "
+"opportunity to automatically partition either an entire drive, or available "
+"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is "
+"recommended for new users or anyone in a hurry. If you do not want to "
+"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:263
 #, no-c-format
-msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size."
+msgid ""
+"If you have an existing DOS or Windows partition that you want to preserve, "
+"be very careful with automatic partitioning. If you choose manual "
+"partitioning, you can use the installer to resize existing FAT or NTFS "
+"partitions to create room for the &debian; install: simply select the "
+"partition and specify its new size."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:270
 #, no-c-format
-msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning."
+msgid ""
+"On the next screen you will see your partition table, how the partitions "
+"will be formatted, and where they will be mounted. Select a partition to "
+"modify or delete it. If you did automatic partitioning, you should just be "
+"able to choose <guimenuitem>Finish partitioning and write changes to disk</"
+"guimenuitem> from the menu to use what it set up. Remember to assign at "
+"least one partition for swap space and to mount a partition on <filename>/</"
+"filename>. For more detailed information on how to use the partitioner, "
+"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend="
+"\"partitioning\"/> has more general information about partitioning."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:283
 #, no-c-format
-msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
+msgid ""
+"Now &d-i; formats your partitions and starts to install the base system, "
+"which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:288
 #, no-c-format
-msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step."
+msgid ""
+"The base system that was installed earlier is a working, but very minimal "
+"installation. To make the system more functional the next step allows you to "
+"install additional packages by selecting tasks. Before packages can be "
+"installed <classname>apt</classname> needs to be configured as that defines "
+"from where the packages will be retrieved. The <quote>Standard system</"
+"quote> task will be selected by default and should normally be installed. "
+"Select the <quote>Desktop environment</quote> task if you would like to have "
+"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> "
+"for additional information about this step."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:300
 #, no-c-format
-msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account."
+msgid ""
+"Installation of the base system is followed by setting up user accounts. By "
+"default you will need to provide a password for the <quote>root</quote> "
+"(administrator) account and information necessary to create one regular user "
+"account."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:307
 #, no-c-format
-msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
+msgid ""
+"The last step is to install a boot loader. If the installer detects other "
+"operating systems on your computer, it will add them to the boot menu and "
+"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to "
+"the master boot record of the first harddrive, which is generally a good "
+"choice. You'll be given the opportunity to override that choice and install "
+"it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:317
 #, no-c-format
-msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>."
+msgid ""
+"&d-i; will now tell you that the installation has finished. Remove the cdrom "
+"or other boot media and hit &enterkey; to reboot your machine. It should "
+"boot up into the newly installed system and allow you to log in. This is "
+"explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:324
 #, no-c-format
-msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
+msgid ""
+"If you need more information on the install process, see <xref linkend=\"d-i-"
+"intro\"/>."
 msgstr ""
 
 #. Tag: title
@@ -292,13 +455,23 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:334
 #, no-c-format
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>."
+msgid ""
+"If you successfully managed an installation with &d-i;, please take time to "
+"provide us with a report. The simplest way to do so is to install the "
+"reportbug package (<command>aptitude install reportbug</command>), configure "
+"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
+"outgoing\"/>, and run <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
 #: installation-howto.xml:344
 #, no-c-format
-msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
+msgid ""
+"If you did not complete the install, you probably found a bug in debian-"
+"installer. To improve the installer it is necessary that we know about them, "
+"so please take the time to report them. You can use an installation report "
+"to report problems; if the install completely fails, see <xref linkend="
+"\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
@@ -310,6 +483,7 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:357
 #, no-c-format
-msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read <xref linkend=\"post-install\"/>."
+msgid ""
+"We hope that your &debian; installation is pleasant and that you find "
+"&debian; useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
-
diff --git a/po/tl/partitioning.po b/po/tl/partitioning.po
index 5cab7d795..2be4d60bf 100644
--- a/po/tl/partitioning.po
+++ b/po/tl/partitioning.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,25 +29,57 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
+msgid ""
+"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can "
+"have a single partition containing the entire operating system, "
+"applications, and your personal files. Most people feel that a separate swap "
+"partition is also a necessity, although it's not strictly true. <quote>Swap</"
+"quote> is scratch space for an operating system, which allows the system to "
+"use disk storage as <quote>virtual memory</quote>. By putting swap on a "
+"separate partition, &arch-kernel; can make much more efficient use of it. It "
+"is possible to force &arch-kernel; to use a regular file as swap, but it is "
+"not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid ""
+"Most people choose to give GNU/&arch-kernel; more than the minimum number of "
+"partitions, however. There are two reasons you might want to break up the "
+"file system into a number of smaller partitions. The first is for safety. If "
+"something happens to corrupt the file system, generally only one partition "
+"is affected. Thus, you only have to replace (from the backups you've been "
+"carefully keeping) a portion of your system. At a bare minimum, you should "
+"consider creating what is commonly called a <quote>root partition</quote>. "
+"This contains the most essential components of the system. If any other "
+"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix "
+"the system. This can save you the trouble of having to reinstall the system "
+"from scratch."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:40
 #, no-c-format
-msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed."
+msgid ""
+"The second reason is generally more important in a business setting, but it "
+"really depends on your use of the machine. For example, a mail server "
+"getting spammed with e-mail can easily fill a partition. If you made "
+"<filename>/var/mail</filename> a separate partition on the mail server, most "
+"of the system will remain working even if you get spammed."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:48
 #, no-c-format
-msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?"
+msgid ""
+"The only real drawback to using more partitions is that it is often "
+"difficult to know in advance what your needs will be. If you make a "
+"partition too small then you will either have to reinstall the system or you "
+"will be constantly moving things around to make room in the undersized "
+"partition. On the other hand, if you make the partition too big, you will be "
+"wasting space that could be used elsewhere. Disk space is cheap nowadays, "
+"but why throw your money away?"
 msgstr ""
 
 #. Tag: title
@@ -58,7 +91,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:68
 #, no-c-format
-msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all &debian; systems include these directories:"
+msgid ""
+"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem "
+"Hierarchy Standard</ulink> for directory and file naming. This standard "
+"allows users and software programs to predict the location of files and "
+"directories. The root level directory is represented simply by the slash "
+"<filename>/</filename>. At the root level, all &debian; systems include "
+"these directories:"
 msgstr ""
 
 #. Tag: entry
@@ -280,37 +319,77 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:142
 #, no-c-format
-msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
+msgid ""
+"The following is a list of important considerations regarding directories "
+"and partitions. Note that disk usage varies widely given system "
+"configuration and specific usage patterns. The recommendations here are "
+"general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
+msgid ""
+"The root partition <filename>/</filename> must always physically contain "
+"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</"
+"filename>, <filename>/lib</filename> and <filename>/dev</filename>, "
+"otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for "
+"the root partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
+msgid ""
+"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</"
+"filename>), libraries (<filename>/usr/lib</filename>), documentation "
+"(<filename>/usr/share/doc</filename>), etc. This is the part of the file "
+"system that generally takes up most space. You should provide at least 500MB "
+"of disk space. This amount should be increased depending on the number and "
+"type of packages you plan to install. A generous workstation or server "
+"installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid ""
+"<filename>/var</filename>: variable data like news articles, e-mails, web "
+"sites, databases, the packaging system cache, etc. will be placed under this "
+"directory. The size of this directory depends greatly on the usage of your "
+"system, but for most people will be dictated by the package management "
+"tool's overhead. If you are going to do a full installation of just about "
+"everything &debian; has to offer, all in one session, setting aside 2 or 3 "
+"GB of space for <filename>/var</filename> should be sufficient. If you are "
+"going to install in pieces (that is to say, install services and utilities, "
+"followed by text stuff, then X, ...), you can get away with 300&ndash;500 "
+"MB. If hard drive space is at a premium and you don't plan on doing major "
+"system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid ""
+"<filename>/tmp</filename>: temporary data created by programs will most "
+"likely go in this directory. 40&ndash;100MB should usually be enough. Some "
+"applications &mdash; including archive manipulators, CD/DVD authoring tools, "
+"and multimedia software &mdash; may use <filename>/tmp</filename> to "
+"temporarily store image files. If you plan to use such applications, you "
+"should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid ""
+"<filename>/home</filename>: every user will put his personal data into a "
+"subdirectory of this directory. Its size depends on how many users will be "
+"using the system and what files are to be stored in their directories. "
+"Depending on your planned usage you should reserve about 100MB for each "
+"user, but adapt this value to your needs. Reserve a lot more space if you "
+"plan to save a lot of multimedia files (pictures, MP3, movies) in your home "
+"directory."
 msgstr ""
 
 #. Tag: title
@@ -322,49 +401,91 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:223
 #, no-c-format
-msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
+msgid ""
+"For new users, personal &debian; boxes, home systems, and other single-user "
+"setups, a single <filename>/</filename> partition (plus swap) is probably "
+"the easiest, simplest way to go. However, if your partition is larger than "
+"around 6GB, choose ext3 as your partition type. Ext2 partitions need "
+"periodic file system integrity checking, and this can cause delays during "
+"booting when the partition is large."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:232
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid ""
+"For multi-user systems or systems with lots of disk space, it's best to put "
+"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</"
+"filename>, and <filename>/home</filename> each on their own partitions "
+"separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid ""
+"You might need a separate <filename>/usr/local</filename> partition if you "
+"plan to install many programs that are not part of the &debian; "
+"distribution. If your machine will be a mail server, you might need to make "
+"<filename>/var/mail</filename> a separate partition. Often, putting "
+"<filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, "
+"is a good idea. If you are setting up a server with lots of user accounts, "
+"it's generally good to have a separate, large <filename>/home</filename> "
+"partition. In general, the partitioning situation varies from computer to "
+"computer depending on its uses."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:252
 #, no-c-format
-msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
+msgid ""
+"For very complex systems, you should see the <ulink url=\"&url-multidisk-"
+"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, "
+"mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:259
 #, no-c-format
-msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
+msgid ""
+"With respect to the issue of swap partition size, there are many views. One "
+"rule of thumb which works well is to use as much swap as you have system "
+"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, "
+"there are exceptions to these rules. If you are trying to solve 10000 "
+"simultaneous equations on a machine with 256MB of memory, you may need a "
+"gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:268
 #, no-c-format
-msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
+msgid ""
+"On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap "
+"partition is 2GB. That should be enough for nearly any installation. "
+"However, if your swap requirements are this high, you should probably try to "
+"spread the swap across different disks (also called <quote>spindles</quote>) "
+"and, if possible, different SCSI or IDE channels. The kernel will balance "
+"swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:278
 #, no-c-format
-msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
+msgid ""
+"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE "
+"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for "
+"another operating system on <filename>/dev/hda1</filename>, a 32MB swap "
+"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/"
+"dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:287
 #, no-c-format
-msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
+msgid ""
+"For an idea of the space taken by tasks you might be interested in adding "
+"after your system installation is complete, check <xref linkend=\"tasksel-"
+"size-list\"/>."
 msgstr ""
 
 #. Tag: title
@@ -376,7 +497,10 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:304
 #, no-c-format
-msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
+msgid ""
+"Linux disks and partition names may be different from other operating "
+"systems. You need to know the names that Linux uses when you create and "
+"mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
@@ -394,37 +518,51 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:322
 #, no-c-format
-msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
+msgid ""
+"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:328
 #, no-c-format
-msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
+msgid ""
+"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, "
+"and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:334
 #, no-c-format
-msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
+msgid ""
+"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as "
+"<filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:340
 #, no-c-format
-msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
+msgid ""
+"The master disk on IDE primary controller is named <filename>/dev/hda</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:346
 #, no-c-format
-msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
+msgid ""
+"The slave disk on IDE primary controller is named <filename>/dev/hdb</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:352
 #, no-c-format
-msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
+msgid ""
+"The master and slave disks of the secondary controller can be called "
+"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, "
+"respectively. Newer IDE controllers can actually have two channels, "
+"effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
@@ -436,43 +574,74 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:369
 #, no-c-format
-msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
+msgid ""
+"The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:377
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>sda1</filename> and <filename>sda2</filename> "
+"represent the first and second partitions of the first SCSI disk drive in "
+"your system."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:384
 #, no-c-format
-msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
+msgid ""
+"Here is a real-life example. Let's assume you have a system with 2 SCSI "
+"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk "
+"(at address 2) is then named <filename>sda</filename>, and the second "
+"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 "
+"partitions on it, these will be named <filename>sda1</filename>, "
+"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies "
+"to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:395
 #, no-c-format
-msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
+msgid ""
+"Note that if you have two SCSI host bus adapters (i.e., controllers), the "
+"order of the drives can get confusing. The best solution in this case is to "
+"watch the boot messages, assuming you know the drive models and/or "
+"capacities."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:402
 #, no-c-format
-msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
+msgid ""
+"Linux represents the primary partitions as the drive name, plus the numbers "
+"1 through 4. For example, the first primary partition on the first IDE drive "
+"is <filename>/dev/hda1</filename>. The logical partitions are numbered "
+"starting at 5, so the first logical partition on that same drive is "
+"<filename>/dev/hda5</filename>. Remember that the extended partition, that "
+"is, the primary partition holding the logical partitions, is not usable by "
+"itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:413
 #, no-c-format
-msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
+msgid ""
+"Sun disk partitions allow for 8 separate partitions (or slices). The third "
+"partition is usually (and is preferred to have) the <quote>Whole Disk</"
+"quote> partition. This partition references all of the sectors of the disk, "
+"and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:420
 #, no-c-format
-msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
+msgid ""
+"The partitions on each disk are represented by appending a decimal number to "
+"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> "
+"represent the first and second partitions of the first DASD device in your "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -484,7 +653,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:436
 #, no-c-format
-msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
+msgid ""
+"Several varieties of partitioning programs have been adapted by &debian; "
+"developers to work on various types of hard disks and computer "
+"architectures. Following is a list of the program(s) applicable for your "
+"architecture."
 msgstr ""
 
 #. Tag: command
@@ -496,7 +669,11 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:449
 #, no-c-format
-msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
+msgid ""
+"Recommended partitioning tool in &debian;. This Swiss army knife can also "
+"resize partitions, create filesystems <phrase arch=\"any-x86\"> "
+"(<quote>format</quote> in Windows speak)</phrase> and assign them to the "
+"mountpoints."
 msgstr ""
 
 #. Tag: command
@@ -514,7 +691,12 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:465
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
+msgid ""
+"Be careful if you have existing FreeBSD partitions on your machine. The "
+"installation kernels include support for these partitions, but the way that "
+"<command>fdisk</command> represents them (or not) can make the device names "
+"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</"
+"ulink>."
 msgstr ""
 
 #. Tag: command
@@ -532,7 +714,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:482
 #, no-c-format
-msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
+msgid ""
+"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at "
+"all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
@@ -580,7 +764,9 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:519
 #, no-c-format
-msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
+msgid ""
+"PowerMac-aware version of <command>fdisk</command>, also used by BVM and "
+"Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
@@ -592,13 +778,21 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:529
 #, no-c-format
-msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
+msgid ""
+"&arch-title; version of <command>fdisk</command>; Please read the fdasd "
+"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/"
+"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and "
+"Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:540
 #, no-c-format
-msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
+msgid ""
+"One of these programs will be run by default when you select "
+"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible "
+"to use a different partitioning tool from the command line on VT2, but this "
+"is not recommended."
 msgstr ""
 
 #. Tag: para
@@ -610,11 +804,18 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:550
 #, no-c-format
-msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
+msgid ""
+"One key point when partitioning for Mac type disks is that the swap "
+"partition is identified by its name; it must be named <quote>swap</quote>. "
+"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. "
+"Please read the fine manual. We also suggest reading the <ulink url=\"&url-"
+"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you "
+"should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686
+#: partitioning.xml:800 partitioning.xml:877
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
@@ -622,61 +823,138 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:567
 #, no-c-format
-msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
+msgid ""
+"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> "
+"somewhere in the first 2GB. This is where the boot loader and an optional "
+"kernel and RAMdisk will be stored, so make it big enough for that &mdash; at "
+"least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware "
+"is that the Linux kernel must reside within the first 2GB of the disk. This "
+"is typically achieved by making the root ext2 partition fit entirely within "
+"the first 2GB of the disk. Alternatively you can create a small ext2 "
+"partition near the start of the disk and mount that on <filename>/boot</"
+"filename>, since that is the directory where the Linux kernel(s) will be "
+"stored. <filename>/boot</filename> needs to be big enough to hold whatever "
+"kernels (and backups) you might wish to load; 25&ndash;50MB is generally "
+"sufficient."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:591
 #, no-c-format
-msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
+msgid ""
+"If you have an existing other operating system such as DOS or Windows and "
+"you want to preserve that operating system while installing &debian;, you "
+"may need to resize its partition to free up space for the &debian; "
+"installation. The installer supports resizing of both FAT and NTFS "
+"filesystems; when you get to the installer's partitioning step, select the "
+"option <guimenuitem>Manual</guimenuitem> and then simply select an existing "
+"partition and change its size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:601
 #, no-c-format
-msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
+msgid ""
+"The PC BIOS generally adds additional constraints for disk partitioning. "
+"There is a limit to how many <quote>primary</quote> and <quote>logical</"
+"quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 "
+"BIOSes, there are limits to where on the drive the BIOS can boot from. More "
+"information can be found in the <ulink url=\"&url-partition-howto;\">Linux "
+"Partition HOWTO</ulink>, but this section will include a brief overview to "
+"help you plan most situations."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:611
 #, no-c-format
-msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
+msgid ""
+"<quote>Primary</quote> partitions are the original partitioning scheme for "
+"PC disks. However, there can only be four of them. To get past this "
+"limitation, <quote>extended</quote> and <quote>logical</quote> partitions "
+"were invented. By setting one of your primary partitions as an extended "
+"partition, you can subdivide all the space allocated to that partition into "
+"logical partitions. You can create up to 60 logical partitions per extended "
+"partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:622
 #, no-c-format
-msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
+msgid ""
+"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 "
+"usable primary partitions, 252 logical partitions), and 63 partitions on an "
+"IDE drive (3 usable primary partitions, 60 logical partitions). However the "
+"normal &debian-gnu; system provides only 20 devices for partitions, so you "
+"may not install on partitions higher than 20 unless you first manually "
+"create devices for those partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:632
 #, no-c-format
-msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
+msgid ""
+"If you have a large IDE disk, and are using neither LBA addressing, nor "
+"overlay drivers (sometimes provided by hard disk manufacturers), then the "
+"boot partition (the partition containing your kernel image) must be placed "
+"within the first 1024 cylinders of your hard drive (usually around 524 "
+"megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:640
 #, no-c-format
-msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
+msgid ""
+"This restriction doesn't apply if you have a BIOS newer than around "
+"1995&ndash;98 (depending on the manufacturer) that supports the "
+"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the "
+"Linux loader, and &debian;'s alternative <command>mbr</command> must use the "
+"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large "
+"disk access extensions are found to be present, they will be utilized. "
+"Otherwise, the legacy disk access interface is used as a fall-back, and it "
+"cannot be used to address any location on the disk higher than the 1023rd "
+"cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer "
+"has, these restrictions no longer apply, since &arch-kernel; does not use "
+"the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:654
 #, no-c-format
-msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
+msgid ""
+"If you have a large disk, you might have to use cylinder translation "
+"techniques, which you can set from your BIOS setup program, such as LBA "
+"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). "
+"More information about issues with large disks can be found in the <ulink "
+"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a "
+"cylinder translation scheme, and the BIOS does not support the large disk "
+"access extensions, then your boot partition has to fit within the "
+"<emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:666
 #, no-c-format
-msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
+msgid ""
+"The recommended way of accomplishing this is to create a small "
+"(25&ndash;50MB should suffice) partition at the beginning of the disk to be "
+"used as the boot partition, and then create whatever other partitions you "
+"wish to have, in the remaining area. This boot partition <emphasis>must</"
+"emphasis> be mounted on <filename>/boot</filename>, since that is the "
+"directory where the &arch-kernel; kernel(s) will be stored. This "
+"configuration will work on any system, regardless of whether LBA or large "
+"disk CHS translation is used, and regardless of whether your BIOS supports "
+"the large disk access extensions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:687
 #, no-c-format
-msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
+msgid ""
+"The <command>partman</command> disk partitioner is the default partitioning "
+"tool for the installer. It manages the set of partitions and their mount "
+"points to ensure that the disks and filesystems are properly configured for "
+"a successful installation. It actually uses <command>parted</command> to do "
+"the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
@@ -688,28 +966,52 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:700
 #, no-c-format
-msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+msgid ""
+"The IA-64 EFI firmware supports two partition table (or disk label) formats, "
+"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer "
+"recommended for IA-64 systems. Although the installer also provides "
+"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> "
+"<command>parted</command></ulink> because only it can manage both GPT and MS-"
+"DOS tables correctly."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:712
 #, no-c-format
-msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
+msgid ""
+"The automatic partitioning recipes for <command>partman</command> allocate "
+"an EFI partition as the first partition on the disk. You can also set up the "
+"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the "
+"main menu in a manner similar to setting up a <emphasis>swap</emphasis> "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:720
 #, no-c-format
 msgid ""
-      "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
-      "      mklabel gpt\n"
-      "      mkpartfs primary fat 0 50\n"
-      "      mkpartfs primary linux-swap 51 1000\n"
-      "      mkpartfs primary ext2 1001 3000\n"
-      "      set 1 boot on\n"
-      "      print\n"
-      "      quit\n"
-      "</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks."
+"The <command>partman</command> partitioner will handle most disk layouts. "
+"For those rare cases where it is necessary to manually set up a disk, you "
+"can use the shell as described above and run the <command>parted</command> "
+"utility directly using its command line interface. Assuming that you want to "
+"erase your whole disk and create a GPT table and some partitions, then "
+"something similar to the following command sequence could be used: "
+"<informalexample><screen>\n"
+"      mklabel gpt\n"
+"      mkpartfs primary fat 0 50\n"
+"      mkpartfs primary linux-swap 51 1000\n"
+"      mkpartfs primary ext2 1001 3000\n"
+"      set 1 boot on\n"
+"      print\n"
+"      quit\n"
+"</screen></informalexample> This creates a new partition table, and three "
+"partitions to be used as an EFI boot partition, swap space, and a root file "
+"system. Finally it sets the boot flag on the EFI partition. Partitions are "
+"specified in Megabytes, with start and end offsets from the beginning of the "
+"disk. So, for example, above we created a 1999MB ext2 file system starting "
+"at offset 1001MB from the start of the disk. Note that formatting swap space "
+"with <command>parted</command> can take a few minutes to complete, as it "
+"scans the partition for bad blocks."
 msgstr ""
 
 #. Tag: title
@@ -721,19 +1023,36 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:746
 #, no-c-format
-msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
+msgid ""
+"ELILO, the IA-64 boot loader, requires a partition containing a FAT file "
+"system with the <userinput>boot</userinput> flag set. The partition must be "
+"big enough to hold the boot loader and any kernels or RAMdisks you may wish "
+"to boot. A minimum size would be about 20MB, but if you expect to run with "
+"multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:755
 #, no-c-format
-msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
+msgid ""
+"The EFI Boot Manager and the EFI Shell fully support the GPT table so the "
+"boot partition does not necessarily have to be the first partition or even "
+"on the same disk. This is convenient if you should forget to allocate the "
+"partition and only find out after you have formatted the other partitions on "
+"your disk(s). The <command>partman</command> partitioner checks for an EFI "
+"partition at the same time it checks for a properly set up <emphasis>root</"
+"emphasis> partition. This gives you an opportunity to correct the disk "
+"layout before the package install begins. The easiest way to correct this "
+"omission is to shrink the last partition of the disk to make enough free "
+"space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:770
 #, no-c-format
-msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
+msgid ""
+"It is strongly recommended that you allocate the EFI boot partition on the "
+"same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -745,13 +1064,27 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:779
 #, no-c-format
-msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
+msgid ""
+"The EFI firmware is significantly more sophisticated than the usual BIOS "
+"seen on most x86 PCs. Some system vendors take advantage of the ability of "
+"the EFI to access files and run programs from a hard disk filesystem to "
+"store diagnostics and EFI based system management utilities on the hard "
+"disk. This is a separate FAT format filesystem on the system disk. Consult "
+"the system documentation and accessories that come with the system for "
+"details. The easiest time to set up a diagnostics partition is at the same "
+"time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:801
 #, no-c-format
-msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
+msgid ""
+"SGI machines require an SGI disk label in order to make the system bootable "
+"from hard disk. It can be created in the fdisk expert menu. The thereby "
+"created volume header (partition number 9) should be at least 3MB large. If "
+"the volume header created is too small, you can simply delete partition "
+"number 9 and re-add it with a different size. Note that the volume header "
+"must start at sector 0."
 msgstr ""
 
 #. Tag: title
@@ -763,48 +1096,94 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:819
 #, no-c-format
-msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
+msgid ""
+"If you are installing onto a NewWorld PowerMac you must create a special "
+"bootstrap partition to hold the boot loader. The size of this partition must "
+"have at least 819200 bytes and its partition type must be "
+"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not "
+"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine "
+"cannot be made bootable from the hard disk. This partition can easily be "
+"created by creating a new partition in <command>partman</command> and "
+"telling it to use it as a <quote>NewWorld boot partition</quote>, or in "
+"<command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:832
 #, no-c-format
-msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
+msgid ""
+"The special partition type Apple_Bootstrap is required to prevent MacOS from "
+"mounting and damaging the bootstrap partition, as there are special "
+"modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:839
 #, no-c-format
-msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
+msgid ""
+"Note that the bootstrap partition is only meant to hold 3 very small files: "
+"the <command>yaboot</command> binary, its configuration <filename>yaboot."
+"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</"
+"command>. It need not and must not be mounted on your file system nor have "
+"kernels or anything else copied to it. The <command>ybin</command> and "
+"<command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:849
 #, no-c-format
-msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
+msgid ""
+"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap "
+"partition should appear before other boot partitions on the disk, especially "
+"MacOS boot partitions. The bootstrap partition should be the first one you "
+"create. However, if you add a bootstrap partition later, you can use "
+"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder "
+"the partition map so the bootstrap partition comes right after the map "
+"(which is always partition 1). It's the logical map order, not the physical "
+"address order, that counts."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:861
 #, no-c-format
-msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
+msgid ""
+"Apple disks normally have several small driver partitions. If you intend to "
+"dual boot your machine with MacOSX, you should retain these partitions and a "
+"small HFS partition (800k is the minimum size). That is because MacOSX, on "
+"every boot, offers to initialize any disks which do not have active MacOS "
+"partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:878
 #, no-c-format
-msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
+msgid ""
+"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This "
+"is the only kind of partition scheme that the OpenBoot PROM understands, and "
+"so it's the only scheme from which you can boot. The <keycap>s</keycap> key "
+"is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:886
 #, no-c-format
-msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
+msgid ""
+"Furthermore, on &arch-title; disks, make sure your first partition on your "
+"boot disk starts at cylinder 0. While this is required, it also means that "
+"the first partition will contain the partition table and the boot block, "
+"which are the first two sectors of the disk. You must <emphasis>not</"
+"emphasis> put swap on the first partition of the boot drive, since swap "
+"partitions do not preserve the first few sectors of the partition. You can "
+"put Ext2 or UFS partitions there; these will leave the partition table and "
+"the boot block alone."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:897
 #, no-c-format
-msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
+msgid ""
+"It is also advised that the third partition should be of type <quote>Whole "
+"disk</quote> (type 5), and contain the entire disk (from the first cylinder "
+"to the last). This is simply a convention of Sun disk labels, and helps the "
+"<command>SILO</command> boot loader keep its bearings."
 msgstr ""
-
diff --git a/po/tl/post-install.po b/po/tl/post-install.po
index 8367ac28c..e22aac91d 100644
--- a/po/tl/post-install.po
+++ b/po/tl/post-install.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,13 +29,27 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:15
 #, no-c-format
-msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system."
+msgid ""
+"To shut down a running &debian-gnu; system, you must not reboot with the "
+"reset switch on the front or back of your computer, or just turn off the "
+"computer. &debian-gnu; should be shut down in a controlled manner, otherwise "
+"files might get lost and/or disk damage might occur. If you run a desktop "
+"environment, there is usually an option to <quote>log out</quote> available "
+"from the application menu that allows you to shutdown (or reboot) the system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:25
 #, no-c-format
-msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system."
+msgid ""
+"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</"
+"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch="
+"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> "
+"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last "
+"option is to log in as root and type one of the commands <command>poweroff</"
+"command>, <command>halt</command> or <command>shutdown -h now</command> if "
+"either of the key combinations do not work or you prefer to type commands; "
+"use <command>reboot</command> to reboot the system."
 msgstr ""
 
 #. Tag: title
@@ -46,13 +61,26 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:47
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:55
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as &debian; packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as &debian; "
+"packages."
 msgstr ""
 
 #. Tag: title
@@ -64,7 +92,13 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:77
 #, no-c-format
-msgid "&debian; is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about &debian; to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use &debian;, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"&debian; is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about &debian; to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use &debian;, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -76,13 +110,32 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:89
 #, no-c-format
-msgid "The most important concept to grasp is the &debian; packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the &debian; packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:130
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
@@ -94,7 +147,12 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:142
 #, no-c-format
-msgid "There are official and unofficial software repositories that are not enabled in the default &debian; install. These contain software which many find important and expect to have. Information on these additional repositories can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-software;\">The Software Available for &debian;'s Stable Release</ulink>."
+msgid ""
+"There are official and unofficial software repositories that are not enabled "
+"in the default &debian; install. These contain software which many find "
+"important and expect to have. Information on these additional repositories "
+"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-"
+"software;\">The Software Available for &debian;'s Stable Release</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -106,7 +164,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:155
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
@@ -118,19 +179,34 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:166
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:175
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user account under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:184
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -142,25 +218,50 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:200
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:206
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about &debian;-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about &debian;-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:217
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about &debian;. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more &debian; documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The &debian; community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on &debian;."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about &debian;. In particular, see the "
+"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> "
+"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference"
+"\">Debian Reference</ulink>. An index of more &debian; documentation is "
+"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian "
+"Documentation Project</ulink>. The &debian; community is self-supporting; to "
+"subscribe to one or more of the Debian mailing lists, see the <ulink url="
+"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</"
+"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/"
+"\">Debian Mailing List Archives</ulink> contain a wealth of information on "
+"&debian;."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:235
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
@@ -172,31 +273,59 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:252
 #, no-c-format
-msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some &debian; utilities, we will try to cover the basics in this section."
+msgid ""
+"Today, email is an important part of many people's life. As there are many "
+"options as to how to set it up, and as having it set up correctly is "
+"important for some &debian; utilities, we will try to cover the basics in "
+"this section."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:259
 #, no-c-format
-msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox."
+msgid ""
+"There are three main functions that make up an e-mail system. First there is "
+"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user "
+"actually uses to compose and read mails. Then there is the <firstterm>Mail "
+"Transfer Agent</firstterm> (MTA) that takes care of transferring messages "
+"from one computer to another. And last there is the <firstterm>Mail Delivery "
+"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the "
+"user's inbox."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:269
 #, no-c-format
-msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail."
+msgid ""
+"These three functions can be performed by separate programs, but they can "
+"also be combined in one or two programs. It is also possible to have "
+"different programs handle these functions for different types of mail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:275
 #, no-c-format
-msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA."
+msgid ""
+"On Linux and Unix systems <command>mutt</command> is historically a very "
+"popular MUA. Like most traditional Linux programs it is text based. It is "
+"often used in combination with <command>exim</command> or <command>sendmail</"
+"command> as MTA and <command>procmail</command> as MDA."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:282
 #, no-c-format
-msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in &debian; available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in &debian; has to do with licensing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can &mdash; and often are &mdash; also be used in combination with the traditional Linux tools."
+msgid ""
+"With the increasing popularity of graphical desktop systems, the use of "
+"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's "
+"<command>kmail</command> or Mozilla's <command>thunderbird</command> (in "
+"&debian; available as <command>icedove</command><footnote> <para> The reason "
+"that <command>thunderbird</command> has been renamed to <command>icedove</"
+"command> in &debian; has to do with licensing issues. Details are outside "
+"the scope of this manual. </para> </footnote>) is becoming more popular. "
+"These programs combine the function of a MUA, MTA and MDA, but can &mdash; "
+"and often are &mdash; also be used in combination with the traditional Linux "
+"tools."
 msgstr ""
 
 #. Tag: title
@@ -208,19 +337,40 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:303
 #, no-c-format
-msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, &hellip; </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes."
+msgid ""
+"Even if you are planning to use a graphical mail program, it is important "
+"that a traditional MTA/MDA is also installed and correctly set up on your "
+"&debian-gnu; system. Reason is that various utilities running on the "
+"system<footnote> <para> Examples are: <command>cron</command>, "
+"<command>quota</command>, <command>logcheck</command>, <command>aide</"
+"command>, &hellip; </para> </footnote> can send important notices by e-mail "
+"to inform the system administrator of (potential) problems or changes."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:318
 #, no-c-format
-msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>."
+msgid ""
+"For this reason the packages <classname>exim4</classname> and "
+"<classname>mutt</classname> will be installed by default (provided you did "
+"not unselect the <quote>standard</quote> task during the installation). "
+"<classname>exim4</classname> is a combination MTA/MDA that is relatively "
+"small but very flexible. By default it will be configured to only handle e-"
+"mail local to the system itself and e-mails addressed to the system "
+"administrator (root account) will be delivered to the regular user account "
+"created during the installation<footnote> <para> The forwarding of mail for "
+"root to the regular user account is configured in <filename>/etc/aliases</"
+"filename>. If no regular user account was created, the mail will of course "
+"be delivered to the root account itself. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:337
 #, no-c-format
-msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>."
+msgid ""
+"When system e-mails are delivered they are added to a file in <filename>/var/"
+"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be "
+"read using <command>mutt</command>."
 msgstr ""
 
 #. Tag: title
@@ -232,31 +382,51 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:348
 #, no-c-format
-msgid "As mentioned earlier, the installed &debian; system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others."
+msgid ""
+"As mentioned earlier, the installed &debian; system is only set up to handle "
+"e-mail local to the system, not for sending mail to others nor for receiving "
+"mail from others."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:354
 #, no-c-format
-msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly."
+msgid ""
+"If you would like <classname>exim4</classname> to handle external e-mail, "
+"please refer to the next subsection for the basic available configuration "
+"options. Make sure to test that mail can be sent and received correctly."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:360
 #, no-c-format
-msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)."
+msgid ""
+"If you intend to use a graphical mail program and use a mail server of your "
+"Internet Service Provider (ISP) or your company, there is not really any "
+"need to configure <classname>exim4</classname> for handling external e-mail. "
+"Just configure your favorite graphical mail program to use the correct "
+"servers to send and receive e-mail (how is outside the scope of this manual)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:369
 #, no-c-format
-msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against &debian; packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports."
+msgid ""
+"However, in that case you may need to configure individual utilities to "
+"correctly send e-mails. One such utility is <command>reportbug</command>, a "
+"program that facilitates submitting bug reports against &debian; packages. "
+"By default it expects to be able to use <classname>exim4</classname> to "
+"submit bug reports."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:377
 #, no-c-format
-msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports."
+msgid ""
+"To correctly set up <command>reportbug</command> to use an external mail "
+"server, please run the command <command>reportbug --configure</command> and "
+"answer <quote>no</quote> to the question if an MTA is available. You will "
+"then be asked for the SMTP server to be used for submitting bug reports."
 msgstr ""
 
 #. Tag: title
@@ -268,7 +438,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:389
 #, no-c-format
-msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:"
+msgid ""
+"If you would like your system to also handle external e-mail, you will need "
+"to reconfigure the <classname>exim4</classname> package<footnote> <para> You "
+"can of course also remove <classname>exim4</classname> and replace it with "
+"an alternative MTA/MDA. </para> </footnote>:"
 msgstr ""
 
 #. Tag: screen
@@ -280,13 +454,18 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:403
 #, no-c-format
-msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option."
+msgid ""
+"After entering that command (as root), you will be asked if you want split "
+"the configuration into small files. If you are unsure, select the default "
+"option."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:409
 #, no-c-format
-msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs."
+msgid ""
+"Next you will be presented with several common mail scenarios. Choose the "
+"one that most closely resembles your needs."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +477,11 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:419
 #, no-c-format
-msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
+msgid ""
+"Your system is connected to a network and your mail is sent and received "
+"directly using SMTP. On the following screens you will be asked a few basic "
+"questions, like your machine's mail name, or a list of domains for which you "
+"accept or relay mail."
 msgstr ""
 
 #. Tag: term
@@ -310,13 +493,22 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:431
 #, no-c-format
-msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which takes care of sending the message on to its destination. The smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail."
+msgid ""
+"In this scenario your outgoing mail is forwarded to another machine, called "
+"a <quote>smarthost</quote>, which takes care of sending the message on to "
+"its destination. The smarthost also usually stores incoming mail addressed "
+"to your computer, so you don't need to be permanently online. That also "
+"means you have to download your mail from the smarthost via programs like "
+"fetchmail."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:441
 #, no-c-format
-msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network."
+msgid ""
+"In a lot of cases the smarthost will be your ISP's mail server, which makes "
+"this option very suitable for dial-up users. It can also be a company mail "
+"server, or even another system on your own network."
 msgstr ""
 
 #. Tag: term
@@ -328,7 +520,10 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:452
 #, no-c-format
-msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled."
+msgid ""
+"This option is basically the same as the previous one except that the system "
+"will not be set up to handle mail for a local e-mail domain. Mail on the "
+"system itself (e.g. for the system administrator) will still be handled."
 msgstr ""
 
 #. Tag: term
@@ -352,19 +547,37 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:473
 #, no-c-format
-msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
+msgid ""
+"Choose this if you are absolutely convinced you know what you are doing. "
+"This will leave you with an unconfigured mail system &mdash; until you "
+"configure it, you won't be able to send or receive any mail and you may miss "
+"some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:484
 #, no-c-format
-msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has further details about configuring <classname>exim4</classname> and explains where to find additional documentation."
+msgid ""
+"If none of these scenarios suits your needs, or if you need a finer grained "
+"setup, you will need to edit configuration files under the <filename>/etc/"
+"exim4</filename> directory after the installation is complete. More "
+"information about <classname>exim4</classname> may be found under <filename>/"
+"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</"
+"filename> has further details about configuring <classname>exim4</classname> "
+"and explains where to find additional documentation."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:495
 #, no-c-format
-msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>."
+msgid ""
+"Note that sending mail directly to the Internet when you don't have an "
+"official domain name, can result in your mail being rejected because of anti-"
+"spam measures on receiving servers. Using your ISP's mail server is "
+"preferred. If you still do want to send out mail directly, you may want to "
+"use a different e-mail address than is generated by default. If you use "
+"<classname>exim4</classname> as your MTA, this is possible by adding an "
+"entry in <filename>/etc/email-addresses</filename>."
 msgstr ""
 
 #. Tag: title
@@ -376,19 +589,29 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:514
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with &debian; handles most configurations. Also, &debian; often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with &debian; handles most configurations. "
+"Also, &debian; often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:524
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:530
 #, no-c-format
-msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
@@ -430,67 +653,135 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:565
 #, no-c-format
-msgid "To compile a kernel the &debian; way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the &debian; way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<classname>linux-source-2.6</classname> and a few others which are probably "
+"already installed (see <filename>/usr/share/doc/kernel-package/README.gz</"
+"filename> for the complete list)."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:574
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:582
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>&debian; way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>&debian; way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <classname>linux-source-2.6</"
+"classname>, yet still use the <classname>kernel-package</classname> "
+"compilation method."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:591
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:598
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/"
+"linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory "
+"<filename>linux-source-&kernelversion;</filename> that will have been "
+"created."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:618
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your &debian; installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your &debian; installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:633
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:638
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --"
+"revision=custom.1.0 kernel_image</userinput>. The version number of "
+"<quote>1.0</quote> can be changed at will; this is just a version number "
+"that you will use to track your kernel builds. Likewise, you can put any "
+"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel "
+"compilation may take quite a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:648
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well."
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../&kernelpackage;-"
+"&kernelversion;-<replaceable>subarchitecture</"
+"replaceable>_custom.1.0_&architecture;.deb</userinput>. The "
+"<replaceable>subarchitecture</replaceable> part is an optional sub-"
+"architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> "
+"depending on what kernel options you set. <userinput>dpkg -i</userinput> "
+"will install the kernel, along with some other nice supporting files. For "
+"instance, the <filename>System.map</filename> will be properly installed "
+"(helpful for debugging kernel problems), and <filename>/boot/config-"
+"&kernelversion;</filename> will be installed, containing your current "
+"configuration set. Your new kernel package is also clever enough to "
+"automatically update your boot loader to use the new kernel. If you have "
+"created a modules package, you'll need to install that package as well."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:668
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:673
 #, no-c-format
-msgid "For more information on &debian; kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"For more information on &debian; kernels and kernel compilation, see the "
+"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. "
+"For more information on <classname>kernel-package</classname>, read the fine "
+"documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
@@ -502,31 +793,63 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:690
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:700
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:715
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:723
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:735
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
@@ -538,6 +861,8 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:748
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/tl/preparing.po b/po/tl/preparing.po
index 9378d6304..86a142b74 100644
--- a/po/tl/preparing.po
+++ b/po/tl/preparing.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,7 +23,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:6
 #, no-c-format
-msgid "This chapter deals with the preparation for installing &debian; before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information."
+msgid ""
+"This chapter deals with the preparation for installing &debian; before you "
+"even boot the installer. This includes backing up your data, gathering "
+"information about your hardware, and locating any necessary information."
 msgstr ""
 
 #. Tag: title
@@ -34,37 +38,59 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:20
 #, no-c-format
-msgid "First, just a note about re-installations. With &debian;, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case."
+msgid ""
+"First, just a note about re-installations. With &debian;, a circumstance "
+"that will require a complete re-installation of your system is very rare; "
+"perhaps mechanical failure of the hard disk would be the most common case."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:27
 #, no-c-format
-msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS."
+msgid ""
+"Many common operating systems may require a complete installation to be "
+"performed when critical failures take place or for upgrades to new OS "
+"versions. Even if a completely new installation isn't required, often the "
+"programs you use must be re-installed to operate properly in the new OS."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:35
 #, no-c-format
-msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the &debian; packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system."
+msgid ""
+"Under &debian-gnu;, it is much more likely that your OS can be repaired "
+"rather than replaced if things go wrong. Upgrades never require a wholesale "
+"installation; you can always upgrade in-place. And the programs are almost "
+"always compatible with successive OS releases. If a new program version "
+"requires newer supporting software, the &debian; packaging system ensures "
+"that all the necessary software is automatically identified and installed. "
+"The point is, much effort has been put into avoiding the need for re-"
+"installation, so think of it as your very last option. The installer is "
+"<emphasis>not</emphasis> designed to re-install over an existing system."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:48
 #, no-c-format
-msgid "Here's a road map for the steps you will take during the installation process."
+msgid ""
+"Here's a road map for the steps you will take during the installation "
+"process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:56
 #, no-c-format
-msgid "Back up any existing data or documents on the hard disk where you plan to install."
+msgid ""
+"Back up any existing data or documents on the hard disk where you plan to "
+"install."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:62
 #, no-c-format
-msgid "Gather information about your computer and any needed documentation, before starting the installation."
+msgid ""
+"Gather information about your computer and any needed documentation, before "
+"starting the installation."
 msgstr ""
 
 #. Tag: para
@@ -76,13 +102,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:73
 #, no-c-format
-msgid "Locate and/or download the installer software and any specialized driver or firmware files your machine requires."
+msgid ""
+"Locate and/or download the installer software and any specialized driver or "
+"firmware files your machine requires."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:79
 #, no-c-format
-msgid "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot infrastructure from which the installer can be booted."
+msgid ""
+"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
+"infrastructure from which the installer can be booted."
 msgstr ""
 
 #. Tag: para
@@ -124,7 +154,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:117
 #, no-c-format
-msgid "If necessary, resize existing partitions on your target harddisk to make space for the installation."
+msgid ""
+"If necessary, resize existing partitions on your target harddisk to make "
+"space for the installation."
 msgstr ""
 
 #. Tag: para
@@ -136,13 +168,17 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:127
 #, no-c-format
-msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>."
+msgid ""
+"Watch the automatic download/install/setup of the <firstterm>base system</"
+"firstterm>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:133
 #, no-c-format
-msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system."
+msgid ""
+"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
+"and/or your existing system."
 msgstr ""
 
 #. Tag: para
@@ -154,37 +190,68 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:146
 #, no-c-format
-msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
+msgid ""
+"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
+"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
+"of the installation system. For more information about this graphical "
+"installer, see <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:154
 #, no-c-format
-msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
+msgid ""
+"If you have problems during the installation, it helps to know which "
+"packages are involved in which steps. Introducing the leading software "
+"actors in this installation drama:"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:160
 #, no-c-format
-msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
+msgid ""
+"The installer software, <classname>debian-installer</classname>, is the "
+"primary concern of this manual. It detects hardware and loads appropriate "
+"drivers, uses <classname>dhcp-client</classname> to set up the network "
+"connection, runs <classname>debootstrap</classname> to install the base "
+"system packages, and runs <classname>tasksel</classname> to allow you to "
+"install certain additional software. Many more actors play smaller parts in "
+"this process, but <classname>debian-installer</classname> has completed its "
+"task when you load the new system for the first time."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:172
 #, no-c-format
-msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
+msgid ""
+"To tune the system to your needs, <classname>tasksel</classname> allows you "
+"to choose to install various predefined bundles of software like a Web "
+"server or a Desktop environment."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:178
 #, no-c-format
-msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because in relation to a text-mode-only system it requires a comparatively large amount of disk space and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid ""
+"One important option during the installation is whether or not to install a "
+"graphical desktop environment, consisting of the X Window System and one of "
+"the available graphical desktop environments. If you choose not to select "
+"the <quote>Desktop environment</quote> task, you will only have a relatively "
+"basic, command line driven system. Installing the Desktop environment task "
+"is optional because in relation to a text-mode-only system it requires a "
+"comparatively large amount of disk space and because many &debian-gnu; "
+"systems are servers which don't really have any need for a graphical user "
+"interface to do their job."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:191
 #, no-c-format
-msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Troubleshooting of the X Window System is not within the scope of this manual."
+msgid ""
+"Just be aware that the X Window System is completely separate from "
+"<classname>debian-installer</classname>, and in fact is much more "
+"complicated. Troubleshooting of the X Window System is not within the scope "
+"of this manual."
 msgstr ""
 
 #. Tag: title
@@ -196,13 +263,29 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:207
 #, no-c-format
-msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system is going to be installed on your computer, it is quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in the installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
+msgid ""
+"Before you start, make sure to back up every file that is now on your "
+"system. If this is the first time a non-native operating system is going to "
+"be installed on your computer, it is quite likely you will need to re-"
+"partition your disk to make room for &debian-gnu;. Anytime you partition "
+"your disk, you run a risk of losing everything on the disk, no matter what "
+"program you use to do it. The programs used in the installation are quite "
+"reliable and most have seen years of use; but they are also quite powerful "
+"and a false move can cost you. Even after backing up, be careful and think "
+"about your answers and actions. Two minutes of thinking can save hours of "
+"unnecessary work."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:220
 #, no-c-format
-msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Even though this is normally not necessary, there might be situations in which you could be required to reinstall your operating system's boot loader to make the system boot or in a worst case even have to reinstall the complete operating system and restore your previously made backup."
+msgid ""
+"If you are creating a multi-boot system, make sure that you have the "
+"distribution media of any other present operating systems on hand. Even "
+"though this is normally not necessary, there might be situations in which "
+"you could be required to reinstall your operating system's boot loader to "
+"make the system boot or in a worst case even have to reinstall the complete "
+"operating system and restore your previously made backup."
 msgstr ""
 
 #. Tag: title
@@ -238,13 +321,20 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:259
 #, no-c-format
-msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of &debian;; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is the official version of the "
+"Installation Guide for the &releasename; release of &debian;; available in "
+"<ulink url=\"&url-release-area;/installmanual\">various formats and "
+"translations</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:268
 #, no-c-format
-msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of &debian;; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
+msgid ""
+"The document you are now reading, which is a development version of the "
+"Installation Guide for the next release of &debian;; available in <ulink url="
+"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -256,7 +346,8 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:281
 #, no-c-format
-msgid "Often contains useful information on configuring or using your hardware."
+msgid ""
+"Often contains useful information on configuring or using your hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -286,7 +377,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:314
 #, no-c-format
-msgid "Documentation of &arch-title;-specific boot sequence, commands and device drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
+msgid ""
+"Documentation of &arch-title;-specific boot sequence, commands and device "
+"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
 msgstr ""
 
 #. Tag: ulink
@@ -298,7 +391,9 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:330
 #, no-c-format
-msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
+msgid ""
+"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
+"&arch-title; hardware."
 msgstr ""
 
 #. Tag: ulink
@@ -310,7 +405,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:346
 #, no-c-format
-msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about &debian; but the basic installation concepts are the same across all &arch-title; distributions."
+msgid ""
+"IBM Redbook describing the Linux distributions available for the mainframe. "
+"It has no chapter about &debian; but the basic installation concepts are the "
+"same across all &arch-title; distributions."
 msgstr ""
 
 #. Tag: ulink
@@ -328,7 +426,10 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:368
 #, no-c-format
-msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
+msgid ""
+"In many cases, the installer will be able to automatically detect your "
+"hardware. But to be prepared, we do recommend familiarizing yourself with "
+"your hardware before the install."
 msgstr ""
 
 #. Tag: para
@@ -346,7 +447,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:386
 #, no-c-format
-msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> key, but some manufacturers use other keys or key combinations. Usually upon starting the computer there will be a message stating which key to press to enter the setup screen."
+msgid ""
+"The BIOS setup screens of your computer. You can view these screens when you "
+"start your computer by pressing a combination of keys. Check your manual for "
+"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
+"keycap> key, but some manufacturers use other keys or key combinations. "
+"Usually upon starting the computer there will be a message stating which key "
+"to press to enter the setup screen."
 msgstr ""
 
 #. Tag: para
@@ -364,13 +471,18 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:408
 #, no-c-format
-msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
+msgid ""
+"System commands or tools in another operating system, including file manager "
+"displays. This source is especially useful for information about RAM and "
+"hard drive memory."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:415
 #, no-c-format
-msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
+msgid ""
+"Your system administrator or Internet Service Provider. These sources can "
+"tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
 #. Tag: title
@@ -514,61 +626,115 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:510
 #, no-c-format
-msgid "Many products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems."
+msgid ""
+"Many products work without trouble on &arch-kernel;. Moreover, hardware "
+"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
+"does not run as many different types of hardware as some operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:516
 #, no-c-format
-msgid "Drivers in &arch-kernel; in most cases are not written for a certain <quote>product</quote> or <quote>brand</quote> from a specific manufacturer, but for a certain hardware/chipset. Many seemingly different products/brands are based on the same hardware design; it is not uncommon that chip manufacturers provide so-called <quote>reference designs</quote> for products based on their chips which are then used by several different device manufacturers and sold under lots of different product or brand names."
+msgid ""
+"Drivers in &arch-kernel; in most cases are not written for a certain "
+"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
+"but for a certain hardware/chipset. Many seemingly different products/brands "
+"are based on the same hardware design; it is not uncommon that chip "
+"manufacturers provide so-called <quote>reference designs</quote> for "
+"products based on their chips which are then used by several different "
+"device manufacturers and sold under lots of different product or brand names."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:527
 #, no-c-format
-msgid "This has advantages and disadvantages. An advantage is that a driver for one chipset works with lots of different products from different manufacturers, as long as their product is based on the same chipset. The disadvantage is that it is not always easy to see which actual chipset is used in a certain product/brand. Unfortunately sometimes device manufacturers change the hardware base of their product without changing the product name or at least the product version number, so that when having two items of the same brand/product name bought at different times, they can sometimes be based on two different chipsets and therefore use two different drivers or there might be no driver at all for one of them."
+msgid ""
+"This has advantages and disadvantages. An advantage is that a driver for one "
+"chipset works with lots of different products from different manufacturers, "
+"as long as their product is based on the same chipset. The disadvantage is "
+"that it is not always easy to see which actual chipset is used in a certain "
+"product/brand. Unfortunately sometimes device manufacturers change the "
+"hardware base of their product without changing the product name or at least "
+"the product version number, so that when having two items of the same brand/"
+"product name bought at different times, they can sometimes be based on two "
+"different chipsets and therefore use two different drivers or there might be "
+"no driver at all for one of them."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:540
 #, no-c-format
-msgid "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on which chipset they are based is to look at their device IDs. All USB/PCI/PCI-Express/ExpressCard devices have so called <quote>vendor</quote> and <quote>product</quote> IDs, and the combination of these two is usually the same for any product based on the same chipset."
+msgid ""
+"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
+"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
+"Express/ExpressCard devices have so called <quote>vendor</quote> and "
+"<quote>product</quote> IDs, and the combination of these two is usually the "
+"same for any product based on the same chipset."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:548
 #, no-c-format
-msgid "On Linux systems, these IDs can be read with the <command>lsusb</command> command for USB devices and with the <command>lspci -nn</command> command for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are usually given in the form of two hexadecimal numbers, seperated by a colon, such as <quote>1d6b:0001</quote>."
+msgid ""
+"On Linux systems, these IDs can be read with the <command>lsusb</command> "
+"command for USB devices and with the <command>lspci -nn</command> command "
+"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
+"usually given in the form of two hexadecimal numbers, seperated by a colon, "
+"such as <quote>1d6b:0001</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:556
 #, no-c-format
-msgid "An example for the output of <command>lsusb</command>: <quote>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the vendor ID and 0002 is the product ID."
+msgid ""
+"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
+"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
+"vendor ID and 0002 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:562
 #, no-c-format
-msgid "An example for the output of <command>lspci -nn</command> for an Ethernet card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)</quote>. The IDs are given inside the rightmost square brackets, i.e. here 10ec is the vendor- and 8168 is the product ID."
+msgid ""
+"An example for the output of <command>lspci -nn</command> for an Ethernet "
+"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
+"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
+"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
+"here 10ec is the vendor- and 8168 is the product ID."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:570
 #, no-c-format
-msgid "As another example, a graphics card could give the following output: <quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
+msgid ""
+"As another example, a graphics card could give the following output: "
+"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
+"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:576
 #, no-c-format
-msgid "On Windows systems, the IDs for a device can be found in the Windows device manager on the tab <quote>details</quote>, where the vendor ID is prefixed with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, you have to select the property <quote>Hardware IDs</quote> in the device manager's details tab to actually see the IDs, as they are not displayed by default."
+msgid ""
+"On Windows systems, the IDs for a device can be found in the Windows device "
+"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
+"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
+"you have to select the property <quote>Hardware IDs</quote> in the device "
+"manager's details tab to actually see the IDs, as they are not displayed by "
+"default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:586
 #, no-c-format
-msgid "Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</quote> and <quote>driver</quote> as the search terms often results in information regarding the driver support status for a certain chipset. If a search for the vendor/product ID does not yield usable results, a search for the chip code names, which are also often provided by lsusb and lspci (<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example and <quote>RV710</quote> in the graphics card example), can help."
+msgid ""
+"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
+"quote> and <quote>driver</quote> as the search terms often results in "
+"information regarding the driver support status for a certain chipset. If a "
+"search for the vendor/product ID does not yield usable results, a search for "
+"the chip code names, which are also often provided by lsusb and lspci "
+"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
+"and <quote>RV710</quote> in the graphics card example), can help."
 msgstr ""
 
 #. Tag: title
@@ -580,19 +746,42 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:601
 #, no-c-format
-msgid "&debian-gnu; is also available as a so-called <quote>live system</quote> for certain architectures. A live system is a preconfigured ready-to-use system in a compressed format that can be booted and used from a read-only medium like a CD or DVD. Using it by default does not create any permanent changes on your computer. You can change user settings and install additional programs from within the live system, but all this only happens in the computer's RAM, i.e. if you turn off the computer and boot the live system again, everything is reset to its defaults. If you want to see whether your hardware is supported by &debian-gnu;, the easiest way is to run a &debian; live system on it and try it out."
+msgid ""
+"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
+"certain architectures. A live system is a preconfigured ready-to-use system "
+"in a compressed format that can be booted and used from a read-only medium "
+"like a CD or DVD. Using it by default does not create any permanent changes "
+"on your computer. You can change user settings and install additional "
+"programs from within the live system, but all this only happens in the "
+"computer's RAM, i.e. if you turn off the computer and boot the live system "
+"again, everything is reset to its defaults. If you want to see whether your "
+"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
+"live system on it and try it out."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:614
 #, no-c-format
-msgid "There are a few limitations in using a live system. The first is that as all changes you do within the live system must be held in your computer's RAM, this only works on systems with enough RAM to do that, so installing additional large software packages may fail due to memory constraints. Another limitation with regards to hardware compatibility testing is that the official &debian-gnu; live system contains only free components, i.e. there are no non-free firmware files included in it. Such non-free packages can of course be installed manually within the system, but there is no automatic detection of required firmware files like in the &d-i;, so installation of non-free components must be done manually if needed."
+msgid ""
+"There are a few limitations in using a live system. The first is that as all "
+"changes you do within the live system must be held in your computer's RAM, "
+"this only works on systems with enough RAM to do that, so installing "
+"additional large software packages may fail due to memory constraints. "
+"Another limitation with regards to hardware compatibility testing is that "
+"the official &debian-gnu; live system contains only free components, i.e. "
+"there are no non-free firmware files included in it. Such non-free packages "
+"can of course be installed manually within the system, but there is no "
+"automatic detection of required firmware files like in the &d-i;, so "
+"installation of non-free components must be done manually if needed."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:627
 #, no-c-format
-msgid "Information about the available variants of the &debian; live images can be found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</ulink>."
+msgid ""
+"Information about the available variants of the &debian; live images can be "
+"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
+"ulink>."
 msgstr ""
 
 #. Tag: title
@@ -604,7 +793,11 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:643
 #, no-c-format
-msgid "If your computer is connected to a fixed network (i.e. an Ethernet or equivalent connection &mdash; not a dialup/PPP connection) which is administered by somebody else, you should ask your network's system administrator for this information:"
+msgid ""
+"If your computer is connected to a fixed network (i.e. an Ethernet or "
+"equivalent connection &mdash; not a dialup/PPP connection) which is "
+"administered by somebody else, you should ask your network's system "
+"administrator for this information:"
 msgstr ""
 
 #. Tag: para
@@ -634,31 +827,47 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:671
 #, no-c-format
-msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
+msgid ""
+"The IP address of the default gateway system you should route to, if your "
+"network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:677
 #, no-c-format
-msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
+msgid ""
+"The system on your network that you should use as a DNS (Domain Name "
+"Service) server."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:685
 #, no-c-format
-msgid "If the network you are connected to uses DHCP (Dynamic Host Configuration Protocol) for configuring network settings, you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
+msgid ""
+"If the network you are connected to uses DHCP (Dynamic Host Configuration "
+"Protocol) for configuring network settings, you don't need this information "
+"because the DHCP server will provide it directly to your computer during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:692
 #, no-c-format
-msgid "If you have internet access via DSL or cable modem (i.e. over a cable tv network) and have a router (often provided preconfigured by your phone or catv provider) which handles your network connectivity, DHCP is usually available by default."
+msgid ""
+"If you have internet access via DSL or cable modem (i.e. over a cable tv "
+"network) and have a router (often provided preconfigured by your phone or "
+"catv provider) which handles your network connectivity, DHCP is usually "
+"available by default."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:700
 #, no-c-format
-msgid "As a rule of thumb: if you run a Windows system in your home network and did not have to manually perform any network settings there to achieve Internet access, network connectivity in &debian-gnu; will also be configured automatically."
+msgid ""
+"As a rule of thumb: if you run a Windows system in your home network and did "
+"not have to manually perform any network settings there to achieve Internet "
+"access, network connectivity in &debian-gnu; will also be configured "
+"automatically."
 msgstr ""
 
 #. Tag: para
@@ -688,19 +897,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:735
 #, no-c-format
-msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
+msgid ""
+"Once you have gathered information about your computer's hardware, check "
+"that your hardware will let you do the type of installation that you want to "
+"do."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:741
 #, no-c-format
-msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
+msgid ""
+"Depending on your needs, you might manage with less than some of the "
+"recommended hardware listed in the table below. However, most users risk "
+"being frustrated if they ignore these suggestions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:747
 #, no-c-format
-msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
+msgid ""
+"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
 msgstr ""
 
 #. Tag: para
@@ -790,31 +1006,58 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:785
 #, no-c-format
-msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
+msgid ""
+"The actual minimum memory requirements are a lot less then the numbers "
+"listed in this table. Depending on the architecture, it is possible to "
+"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
+"same goes for the disk space requirements, especially if you pick and choose "
+"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
+"additional information on disk space requirements."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:795
 #, no-c-format
-msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
+msgid ""
+"It is possible to run a graphical desktop environment on older or low-end "
+"systems, but in that case it is recommended to install a window manager that "
+"is less resource-hungry than those of the GNOME or KDE desktop environments; "
+"alternatives include <classname>xfce4</classname>, <classname>icewm</"
+"classname> and <classname>wmaker</classname>, but there are others to choose "
+"from."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:804
 #, no-c-format
-msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
+msgid ""
+"It is practically impossible to give general memory or disk space "
+"requirements for server installations as those very much depend on what the "
+"server is to be used for."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:810
 #, no-c-format
-msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
+msgid ""
+"Remember that these sizes don't include all the other materials which are "
+"usually to be found, such as user files, mail, and data. It is always best "
+"to be generous when considering the space for your own files and data."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:817
 #, no-c-format
-msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to &debian; in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
+msgid ""
+"Disk space required for the smooth operation of the &debian-gnu; system "
+"itself is taken into account in these recommended system requirements. "
+"Notably, the <filename>/var</filename> partition contains a lot of state "
+"information specific to &debian; in addition to its regular contents, like "
+"logfiles. The <command>dpkg</command> files (with information on all "
+"installed packages) can easily consume 40MB. Also, <command>apt-get</"
+"command> puts downloaded packages here before they are installed. You should "
+"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
+"more if you install a graphical desktop environment."
 msgstr ""
 
 #. Tag: title
@@ -826,43 +1069,83 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:842
 #, no-c-format
-msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
+msgid ""
+"Partitioning your disk simply refers to the act of breaking up your disk "
+"into sections. Each section is then independent of the others. It's roughly "
+"equivalent to putting up walls inside a house; if you add furniture to one "
+"room it doesn't affect any other room."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:849
 #, no-c-format
-msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
+msgid ""
+"Whenever this section talks about <quote>disks</quote> you should translate "
+"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
+"means an LPAR or VM guest in this case."
 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 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."
 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 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
 #: preparing.xml:884
 #, no-c-format
-msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
+msgid ""
+"In general, changing a partition with a file system already on it will "
+"destroy any information there. Thus you should always make backups before "
+"doing any repartitioning. Using the analogy of the house, you would probably "
+"want to move all the furniture out of the way before moving a wall or you "
+"risk destroying it."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:892
 #, no-c-format
-msgid "Several modern operating systems offer the ability to move and resize certain existing partitions without destroying their contents. This allows making space for additional partitions without losing existing data. Even though this works quite well in most cases, making changes to the partitioning of a disk is an inherently dangerous action and should only be done after having made a full backup of all data. <phrase arch=\"any-x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, the ability to move and resize them losslessly is provided both by &d-i; as well as by the integrated Disk Manager of Windows 7. </phrase>"
+msgid ""
+"Several modern operating systems offer the ability to move and resize "
+"certain existing partitions without destroying their contents. This allows "
+"making space for additional partitions without losing existing data. Even "
+"though this works quite well in most cases, making changes to the "
+"partitioning of a disk is an inherently dangerous action and should only be "
+"done after having made a full backup of all data. <phrase arch=\"any-"
+"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
+"the ability to move and resize them losslessly is provided both by &d-i; as "
+"well as by the integrated Disk Manager of Windows 7. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:907
 #, no-c-format
-msgid "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go to the partitioning step, select the option for manual partitioning, select the partition to resize, and simply specify its new size."
+msgid ""
+"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
+"to the partitioning step, select the option for manual partitioning, select "
+"the partition to resize, and simply specify its new size."
 msgstr ""
 
 #. Tag: emphasis
@@ -874,25 +1157,50 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:917
 #, no-c-format
-msgid "Creating and deleting partitions can be done from within &d-i; as well as from an existing operating system. As a rule of thumb, partitions should be created by the system for which they are to be used, i.e. partitions to be used by &debian-gnu; should be created from within &d-i; and partitions to be used from another operating system should be created from there. &d-i; is capable of creating non-&arch-kernel; partitions, and partitions created this way usually work without problems when used in other operating systems, but there are a few rare corner cases in which this could cause problems, so if you want to be sure, use the native partitioning tools to create partitions for use by other operating systems."
+msgid ""
+"Creating and deleting partitions can be done from within &d-i; as well as "
+"from an existing operating system. As a rule of thumb, partitions should be "
+"created by the system for which they are to be used, i.e. partitions to be "
+"used by &debian-gnu; should be created from within &d-i; and partitions to "
+"be used from another operating system should be created from there. &d-i; is "
+"capable of creating non-&arch-kernel; partitions, and partitions created "
+"this way usually work without problems when used in other operating systems, "
+"but there are a few rare corner cases in which this could cause problems, so "
+"if you want to be sure, use the native partitioning tools to create "
+"partitions for use by other operating systems."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:930
 #, no-c-format
-msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with the &debian; installation. Windows and other OS installations may destroy your ability to start &debian;, or encourage you to reformat non-native partitions."
+msgid ""
+"If you are going to install more than one operating system on the same "
+"machine, you should install all other system(s) before proceeding with the "
+"&debian; installation. Windows and other OS installations may destroy your "
+"ability to start &debian;, or encourage you to reformat non-native "
+"partitions."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:938
 #, no-c-format
-msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
+msgid ""
+"You can recover from these actions or avoid them, but installing the native "
+"system first saves you trouble."
 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 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."
 msgstr ""
 
 #. Tag: title
@@ -904,7 +1212,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1021
 #, no-c-format
-msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and &debian; on the same machine, it is recommended that you partition using SunOS prior to installing &debian;. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
+msgid ""
+"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
+"both SunOS and &debian; on the same machine, it is recommended that you "
+"partition using SunOS prior to installing &debian;. The Linux kernel "
+"understands Sun disk labels, so there are no problems there. SILO supports "
+"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
+"iso9660 (CDROM) partitions."
 msgstr ""
 
 #. Tag: title
@@ -916,13 +1230,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1035
 #, no-c-format
-msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
+msgid ""
+"Whatever system you are using to partition, make sure you create a "
+"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
+"partition scheme that the OpenBoot PROM understands, and so it's the only "
+"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
+"keycap> key is used to create Sun disk labels. You only need to do this on "
+"drives that do not already have a Sun disk label. If you are using a drive "
+"that was previously formatted using a PC (or other architecture) you must "
+"create a new disk label, or problems with the disk geometry will most likely "
+"occur."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1047
 #, no-c-format
-msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
+msgid ""
+"You will probably be using <command>SILO</command> as your boot loader (the "
+"small program which runs the operating system kernel). <command>SILO</"
+"command> has certain requirements for partition sizes and location; see "
+"<xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: title
@@ -934,25 +1261,49 @@ 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>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>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1071
 #, 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."
+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
 #, 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 ""
+"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."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1090
 #, 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 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."
 msgstr ""
 
 #. Tag: title
@@ -964,7 +1315,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1111
 #, 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)."
+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
@@ -976,7 +1333,15 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1128
 #, 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."
+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
@@ -988,31 +1353,63 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1144
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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."
+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
 #, 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>"
+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: title
@@ -1024,29 +1421,53 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1204
 #, 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."
+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:1212
 #, 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."
+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:1220
 #, no-c-format
 msgid ""
-      "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
-      "ok\n"
-      "0 &gt;\n"
-      "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
+"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
+"ok\n"
+"0 &gt;\n"
+"</screen></informalexample> Note that on older model &arch-title; Macs, the "
+"default and sometimes hardwired I/O for OpenFirmware user interaction is "
+"through the serial (modem) port. If you invoke OpenFirmware on one of these "
+"machines, you will just see a black screen. In that case, a terminal program "
+"running on another computer, connected to the modem port, is needed to "
+"interact with OpenFirmware."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1233
 #, 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."
+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
@@ -1058,45 +1479,90 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1255
 #, 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."
+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:1263
 #, 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."
+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:1275
 #, 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."
+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:1288
 #, 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>."
+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:1298
 #, 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"
-      "<replaceable>driver-name</replaceable>@\n"
-      "<replaceable>unit-address</replaceable>:\n"
-      "<replaceable>device-arguments</replaceable>\n"
-      "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
+"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"
+"<replaceable>driver-name</replaceable>@\n"
+"<replaceable>unit-address</replaceable>:\n"
+"<replaceable>device-arguments</replaceable>\n"
+"</screen></informalexample> In older revisions of OpenBoot, device naming is "
+"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
+"disk devices are of the form <quote>sd(<replaceable>controller</"
+"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
+"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
+"newer OpenBoot revisions is useful for viewing the currently configured "
+"devices. For full information, whatever your revision, see the <ulink url="
+"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
 #: preparing.xml:1321
 #, 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"
-      "# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
-      "</screen></informalexample> and under Solaris:"
+"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"
+"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
+"</screen></informalexample> and under Solaris:"
 msgstr ""
 
 #. Tag: screen
@@ -1114,19 +1580,45 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1351
 #, 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."
+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:1363
 #, 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."
+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:1373
 #, 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."
+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
@@ -1138,7 +1630,12 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1391
 #, 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."
+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
@@ -1150,13 +1647,26 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1407
 #, 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."
+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:1417
 #, 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."
+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
@@ -1168,13 +1678,21 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1436
 #, 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."
+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:1444
 #, 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."
+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
@@ -1198,7 +1716,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1464
 #, 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."
+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
@@ -1210,6 +1734,13 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1479
 #, 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>."
+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 ""
-
diff --git a/po/tl/preseed.po b/po/tl/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/tl/preseed.po
+++ b/po/tl/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-
diff --git a/po/tl/random-bits.po b/po/tl/random-bits.po
index ff94f432b..26dbb7c32 100644
--- a/po/tl/random-bits.po
+++ b/po/tl/random-bits.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,7 +29,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:12
 #, no-c-format
-msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below."
+msgid ""
+"In Linux various special files can be found under the directory <filename>/"
+"dev</filename>. These files are called device files and behave unlike "
+"ordinary files. The most common types of device files are for block devices "
+"and character devices. These files are an interface to the actual driver "
+"(part of the Linux kernel) which in turn accesses the hardware. Another, "
+"less common, type of device file is the named <firstterm>pipe</firstterm>. "
+"The most important device files are listed in the tables below."
 msgstr ""
 
 #. Tag: filename
@@ -316,33 +324,62 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:126
 #, no-c-format
-msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>."
+msgid ""
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. Normally, this is a simple matter of installing <filename>gpm</"
+"filename> and the X server itself. Both should be configured to use "
+"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse "
+"protocol is named <userinput>exps2</userinput> in gpm, and "
+"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files "
+"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:137
 #, no-c-format
-msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>."
+msgid ""
+"Certain kernel modules must be loaded in order for your mouse to work. In "
+"most cases the correct modules are autodetected, but not always for old-"
+"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole "
+"D-shaped connector; bus mice have an 8-pin round connector, not to be "
+"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round "
+"connector of an ADB mouse. </para> </footnote>, which are quite rare except "
+"on very old computers. Summary of Linux kernel modules needed for different "
+"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</"
+"entry> <entry>Description</entry> </row> </thead><tbody> <row> "
+"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </"
+"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</"
+"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> "
+"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech "
+"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse "
+"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></"
+"informaltable> To load a mouse driver module, you can use the "
+"<command>modconf</command> command (from the package with the same name) and "
+"look in the category <userinput>kernel/drivers/input/mouse</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:184
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:191
 #, no-c-format
 msgid ""
-      "# 3-button mouse emulation\n"
-      "# turn on emulation\n"
-      "/dev/mac_hid/mouse_button_emulation = 1\n"
-      "# Send middle mouse button signal with the F11 key\n"
-      "/dev/mac_hid/mouse_button2_keycode = 87\n"
-      "# Send right mouse button signal with the F12 key\n"
-      "/dev/mac_hid/mouse_button3_keycode = 88\n"
-      "# For different keys, use showkey to tell you what the code is."
+"# 3-button mouse emulation\n"
+"# turn on emulation\n"
+"/dev/mac_hid/mouse_button_emulation = 1\n"
+"# Send middle mouse button signal with the F11 key\n"
+"/dev/mac_hid/mouse_button2_keycode = 87\n"
+"# Send right mouse button signal with the F12 key\n"
+"/dev/mac_hid/mouse_button3_keycode = 88\n"
+"# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
 #. Tag: title
@@ -354,31 +391,54 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "A standard installation for the amd64 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB."
+msgid ""
+"A standard installation for the amd64 architecture, including all standard "
+"packages and using the default 2.6 kernel, takes up &std-system-size;MB of "
+"disk space. A minimal base installation, without the <quote>Standard system</"
+"quote> task selected, will take &base-system-size;MB."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:207
 #, no-c-format
-msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use."
+msgid ""
+"In both cases this is the actual disk space used <emphasis>after</emphasis> "
+"the installation is finished and any temporary files deleted. It also does "
+"not take into account overhead used by the file system, for example for "
+"journal files. This means that significantly more disk space is needed both "
+"<emphasis>during</emphasis> the installation and for normal system use."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:216
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:223
 #, no-c-format
-msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)."
+msgid ""
+"By default the installer will install the GNOME desktop environment, but "
+"alternative desktop environments can be selected either by using one of the "
+"special CD images, or by specifying the desired desktop environment when the "
+"installer is booted (see <xref linkend=\"pkgsel\"/>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:230
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the standard installation when determining the size of partitions. Most of "
+"the size listed as <quote>Installed size</quote> will end up in <filename>/"
+"usr</filename> and in <filename>/lib</filename>; the size listed as "
+"<quote>Download size</quote> is (temporarily) required in <filename>/var</"
+"filename>."
 msgstr ""
 
 #. Tag: entry
@@ -522,7 +582,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid ""
+"There is some overlap of the Laptop task with the Desktop environment task. "
+"If you install both, the Laptop task will only require a few MB additional "
+"disk space."
 msgstr ""
 
 #. Tag: entry
@@ -714,7 +777,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:350
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -726,19 +793,40 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:367
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
+msgid ""
+"This section explains how to install &debian-gnu; from an existing Unix or "
+"Linux system, without using the menu-driven installer as explained in the "
+"rest of the manual. This <quote>cross-install</quote> HOWTO has been "
+"requested by users switching to &debian-gnu; from Red Hat, Mandriva, and "
+"SUSE. In this section some familiarity with entering *nix commands and "
+"navigating the file system is assumed. In this section, <prompt>$</prompt> "
+"symbolizes a command to be entered in the user's current system, while "
+"<prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:379
 #, no-c-format
-msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new &debian; system configured to your preference, you "
+"can migrate your existing user data (if any) to it, and keep on rolling. "
+"This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's "
+"also a clever way for dealing with hardware that otherwise doesn't play "
+"friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:390
 #, no-c-format
-msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
+msgid ""
+"As this is a mostly manual procedure, you should bear in mind that you will "
+"need to do a lot of basic configuration of the system yourself, which will "
+"also require more knowledge of &debian; and of &arch-kernel; in general than "
+"performing a regular installation. You cannot expect this procedure to "
+"result in a system that is identical to a system from a regular "
+"installation. You should also keep in mind that this procedure only gives "
+"the basic steps to set up a system. Additional installation and/or "
+"configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
@@ -750,41 +838,56 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:405
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need around &base-"
+"system-size;MB of space available for a console only install, or about &task-"
+"desktop-lxde-inst;MB if you plan to install X (more if you intend to install "
+"desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:413
 #, no-c-format
 msgid ""
-      "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
-      "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
-      "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"Next, create file systems on the partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
+"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n"
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:423
 #, no-c-format
 msgid ""
-      "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
-      "# mkswap /dev/<replaceable>hda5</replaceable>\n"
-      "# sync; sync; sync\n"
-      "# swapon /dev/<replaceable>hda5</replaceable>\n"
-      "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"Initialize and activate swap (substitute the partition number for your "
+"intended &debian; swap partition): <informalexample><screen>\n"
+"# mkswap /dev/<replaceable>hda5</replaceable>\n"
+"# sync; sync; sync\n"
+"# swapon /dev/<replaceable>hda5</replaceable>\n"
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:435
 #, no-c-format
 msgid ""
-      "# mkdir /mnt/debinst\n"
-      "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
+"# mkdir /mnt/debinst\n"
+"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:438
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
@@ -796,26 +899,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:449
 #, no-c-format
-msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The utility used by the &debian; installer, and recognized as the official "
+"way to install a &debian; base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname> and basic Unix/Linux "
+"tools<footnote> <para> These include the GNU core utilities and commands "
+"like <command>sed</command>, <command>grep</command>, <command>tar</command> "
+"and <command>gzip</command>. </para> </footnote>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:479
 #, no-c-format
 msgid ""
-      "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
-      "# mkdir work\n"
-      "# cd work\n"
-      "</screen></informalexample> The <command>debootstrap</command> binary is located in the &debian; archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files."
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
+"# mkdir work\n"
+"# cd work\n"
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the &debian; archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the files from it. "
+"You will need to have root privileges to install the files."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:494
 #, no-c-format
 msgid ""
-      "# ar -x debootstrap_0.X.X_all.deb\n"
-      "# cd /\n"
-      "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
+"# ar -x debootstrap_0.X.X_all.deb\n"
+"# cd /\n"
+"# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
 #. Tag: title
@@ -827,27 +945,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any &debian; archive mirror "
+"for <userinput>&archive-mirror;/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:510
 #, no-c-format
-msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>amd64</userinput>, "
+"<userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, "
+"<userinput>mipsel</userinput>, <userinput>powerpc</userinput>, "
+"<userinput>s390</userinput>, <userinput>s390x</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:533
 #, no-c-format
 msgid ""
-      "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
-      "     /mnt/debinst http://ftp.us.debian.org/debian"
+"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
+"     /mnt/debinst http://ftp.us.debian.org/debian"
 msgstr ""
 
 #. Tag: title
@@ -860,9 +993,11 @@ msgstr ""
 #: random-bits.xml:540
 #, no-c-format
 msgid ""
-      "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
-      "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
-      "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:"
+"Now you've got a real &debian; system, though rather lean, on disk. "
+"<command>chroot</command> into it: <informalexample><screen>\n"
+"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n"
+"</screen></informalexample> After chrooting you may need to set the terminal "
+"definition to be compatible with the &debian; base system, for example:"
 msgstr ""
 
 #. Tag: screen
@@ -880,7 +1015,14 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:556
 #, no-c-format
-msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
+msgid ""
+"At this point <filename>/dev/</filename> only contains very basic device "
+"files. For the next steps of the installation additional device files may be "
+"needed. There are different ways to go about this and which method you "
+"should use depends on the host system you are using for the installation, on "
+"whether you intend to use a modular kernel or not, and on whether you intend "
+"to use dynamic (e.g. using <classname>udev</classname>) or static device "
+"files for the new system."
 msgstr ""
 
 #. Tag: para
@@ -892,28 +1034,34 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:571
 #, no-c-format
-msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
+msgid ""
+"install the makedev package, and create a default set of static device files "
+"using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:575
 #, no-c-format
 msgid ""
-      "# apt-get install makedev\n"
-      "# cd /dev\n"
-      "# MAKEDEV generic"
+"# apt-get install makedev\n"
+"# cd /dev\n"
+"# MAKEDEV generic"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:578
 #, no-c-format
-msgid "manually create only specific device files using <command>MAKEDEV</command>"
+msgid ""
+"manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:583
 #, no-c-format
-msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
+msgid ""
+"bind mount /dev from your host system on top of /dev in the target system; "
+"note that the postinst scripts of some packages may try to create device "
+"files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
@@ -926,34 +1074,44 @@ msgstr ""
 #: random-bits.xml:597
 #, no-c-format
 msgid ""
-      "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
-      "# editor /etc/fstab\n"
-      "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
-      "# /etc/fstab: static file system information.\n"
-      "#\n"
-      "# file system    mount point   type    options                  dump pass\n"
-      "/dev/XXX         /             ext3    defaults                 0    1\n"
-      "/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
-      "\n"
-      "/dev/XXX         none          swap    sw                       0    0\n"
-      "proc             /proc         proc    defaults                 0    0\n"
-      "\n"
-      "/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
-      "/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
-      "\n"
-      "/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
-      "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
-      "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-      "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n"
-      "# mount /path   # e.g.: mount /usr\n"
-      "</screen></informalexample> Current &debian; systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n"
-      "# cd /media\n"
-      "# mkdir cdrom0\n"
-      "# ln -s cdrom0 cdrom\n"
-      "# cd /\n"
-      "# ln -s media/cdrom\n"
-      "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
+"# editor /etc/fstab\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
+"# /etc/fstab: static file system information.\n"
+"#\n"
+"# file system    mount point   type    options                  dump pass\n"
+"/dev/XXX         /             ext3    defaults                 0    1\n"
+"/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2\n"
+"\n"
+"/dev/XXX         none          swap    sw                       0    0\n"
+"proc             /proc         proc    defaults                 0    0\n"
+"\n"
+"/dev/fd0         /media/floppy auto    noauto,rw,sync,user,exec 0    0\n"
+"/dev/cdrom       /media/cdrom  iso9660 noauto,ro,user,exec      0    0\n"
+"\n"
+"/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
+"/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
+"/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or, to mount file systems individually, use: <informalexample><screen>\n"
+"# mount /path   # e.g.: mount /usr\n"
+"</screen></informalexample> Current &debian; systems have mountpoints for "
+"removable media under <filename>/media</filename>, but keep compatibility "
+"symlinks in <filename>/</filename>. Create these as as needed, for example: "
+"<informalexample><screen>\n"
+"# cd /media\n"
+"# mkdir cdrom0\n"
+"# ln -s cdrom0 cdrom\n"
+"# cd /\n"
+"# ln -s media/cdrom\n"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -965,7 +1123,10 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:625
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -983,15 +1144,19 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:638
 #, no-c-format
-msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
+msgid ""
+"An option in the file <filename>/etc/default/rcS</filename> determines "
+"whether the system will interpret the hardware clock as being set to UTC or "
+"local time. The following command allows you to set that and choose your "
+"timezone."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:645
 #, no-c-format
 msgid ""
-      "# editor /etc/default/rcS\n"
-      "# dpkg-reconfigure tzdata"
+"# editor /etc/default/rcS\n"
+"# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
@@ -1004,54 +1169,64 @@ msgstr ""
 #: random-bits.xml:652
 #, no-c-format
 msgid ""
-      "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
-      "# editor /etc/network/interfaces\n"
-      "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
-      "######################################################################\n"
-      "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
-      "# See the interfaces(5) manpage for information on what options are\n"
-      "# available.\n"
-      "######################################################################\n"
-      "\n"
-      "# We always want the loopback interface.\n"
-      "#\n"
-      "auto lo\n"
-      "iface lo inet loopback\n"
-      "\n"
-      "# To use dhcp:\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet dhcp\n"
-      "\n"
-      "# An example static IP setup: (broadcast and gateway are optional)\n"
-      "#\n"
-      "# auto eth0\n"
-      "# iface eth0 inet static\n"
-      "#     address 192.168.0.42\n"
-      "#     network 192.168.0.0\n"
-      "#     netmask 255.255.255.0\n"
-      "#     broadcast 192.168.0.255\n"
-      "#     gateway 192.168.0.1\n"
-      "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "# editor /etc/resolv.conf\n"
-      "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
-      "search hqdom.local\n"
-      "nameserver 10.1.1.36\n"
-      "nameserver 192.168.9.100\n"
-      "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
-      "# echo DebianHostName &gt; /etc/hostname\n"
-      "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n"
-      "127.0.0.1 localhost\n"
-      "127.0.1.1 DebianHostName\n"
-      "\n"
-      "# The following lines are desirable for IPv6 capable hosts\n"
-      "::1     ip6-localhost ip6-loopback\n"
-      "fe00::0 ip6-localnet\n"
-      "ff00::0 ip6-mcastprefix\n"
-      "ff02::1 ip6-allnodes\n"
-      "ff02::2 ip6-allrouters\n"
-      "ff02::3 ip6-allhosts\n"
-      "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> "
+"and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
+"# editor /etc/network/interfaces\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"######################################################################\n"
+"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
+"# See the interfaces(5) manpage for information on what options are\n"
+"# available.\n"
+"######################################################################\n"
+"\n"
+"# We always want the loopback interface.\n"
+"#\n"
+"auto lo\n"
+"iface lo inet loopback\n"
+"\n"
+"# To use dhcp:\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet dhcp\n"
+"\n"
+"# An example static IP setup: (broadcast and gateway are optional)\n"
+"#\n"
+"# auto eth0\n"
+"# iface eth0 inet static\n"
+"#     address 192.168.0.42\n"
+"#     network 192.168.0.0\n"
+"#     netmask 255.255.255.0\n"
+"#     broadcast 192.168.0.255\n"
+"#     gateway 192.168.0.1\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"# editor /etc/resolv.conf\n"
+"</screen></informalexample> A simple example <filename>/etc/resolv.conf</"
+"filename>: <informalexample><screen>\n"
+"search hqdom.local\n"
+"nameserver 10.1.1.36\n"
+"nameserver 192.168.9.100\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
+"# echo DebianHostName &gt; /etc/hostname\n"
+"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with "
+"IPv6 support: <informalexample><screen>\n"
+"127.0.0.1 localhost\n"
+"127.0.1.1 DebianHostName\n"
+"\n"
+"# The following lines are desirable for IPv6 capable hosts\n"
+"::1     ip6-localhost ip6-loopback\n"
+"fe00::0 ip6-localnet\n"
+"ff00::0 ip6-mcastprefix\n"
+"ff02::1 ip6-allnodes\n"
+"ff02::2 ip6-allrouters\n"
+"ff02::3 ip6-allhosts\n"
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1064,12 +1239,16 @@ msgstr ""
 #: random-bits.xml:694
 #, no-c-format
 msgid ""
-      "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
-      "deb-src http://ftp.us.debian.org/debian &releasename; main\n"
-      "\n"
-      "deb http://security.debian.org/ &releasename;/updates main\n"
-      "deb-src http://security.debian.org/ &releasename;/updates main\n"
-      "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list."
+"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</"
+"filename> that will allow installing additional packages. However, you may "
+"want to add some additional sources, for example for source packages and "
+"security updates: <informalexample><screen>\n"
+"deb-src http://ftp.us.debian.org/debian &releasename; main\n"
+"\n"
+"deb http://security.debian.org/ &releasename;/updates main\n"
+"deb-src http://security.debian.org/ &releasename;/updates main\n"
+"</screen></informalexample> Make sure to run <userinput>aptitude update</"
+"userinput> after you have made changes to the sources list."
 msgstr ""
 
 #. Tag: title
@@ -1082,24 +1261,29 @@ msgstr ""
 #: random-bits.xml:711
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
-      "# aptitude install locales\n"
-      "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> To configure your keyboard (if needed):"
+"To configure your locale settings to use a language other than English, "
+"install the <classname>locales</classname> support package and configure it. "
+"Currently the use of UTF-8 locales is recommended. "
+"<informalexample><screen>\n"
+"# aptitude install locales\n"
+"# dpkg-reconfigure locales\n"
+"</screen></informalexample> To configure your keyboard (if needed):"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:721
 #, no-c-format
 msgid ""
-      "# aptitude install console-setup\n"
-      "# dpkg-reconfigure keyboard-configuration"
+"# aptitude install console-setup\n"
+"# dpkg-reconfigure keyboard-configuration"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:723
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1111,7 +1295,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:734
 #, no-c-format
-msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
+msgid ""
+"If you intend to boot this system, you probably want a &arch-kernel; kernel "
+"and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
@@ -1129,7 +1315,9 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:745
 #, no-c-format
-msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid ""
+"# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</"
+"replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1141,30 +1329,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:752
 #, no-c-format
-msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
+msgid ""
+"To make your &debian-gnu; system bootable, set up your boot loader to load "
+"the installed kernel with your new root partition. Note that "
+"<command>debootstrap</command> does not install a boot loader, though you "
+"can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:759
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
+msgid ""
+"Check <userinput>info grub</userinput> <phrase arch=\"x86\">or "
+"<userinput>man lilo.conf</userinput></phrase> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing grub2 "
+"<filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</"
+"filename>. For <filename>lilo.conf</filename>, you could also copy it to the "
+"new system and edit it there. After you are done editing, call "
+"<command>lilo</command> (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:771
 #, no-c-format
 msgid ""
-      "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
-      "# aptitude install grub-pc\n"
-      "# grub-install /dev/<replaceable>hda</replaceable>\n"
-      "# update-grub\n"
-      "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>."
+"Installing and setting up <classname>grub2</classname> is as easy as: "
+"<informalexample><screen>\n"
+"# aptitude install grub-pc\n"
+"# grub-install /dev/<replaceable>hda</replaceable>\n"
+"# update-grub\n"
+"</screen></informalexample> The second command will install <command>grub2</"
+"command> (in this case in the MBR of <literal>hda</literal>). The last "
+"command will create a sane and working <filename>/boot/grub/grub.cfg</"
+"filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:781
 #, no-c-format
-msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
+msgid ""
+"Note that this assumes that a <filename>/dev/hda</filename> device file has "
+"been created. There are alternative methods to install <command>grub2</"
+"command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
@@ -1177,36 +1385,44 @@ msgstr ""
 #: random-bits.xml:791
 #, no-c-format
 msgid ""
-      "boot=/dev/<replaceable>hda6</replaceable>\n"
-      "root=/dev/<replaceable>hda6</replaceable>\n"
-      "install=menu\n"
-      "delay=20\n"
-      "lba32\n"
-      "image=/vmlinuz\n"
-      "initrd=/initrd.img\n"
-      "label=Debian"
+"boot=/dev/<replaceable>hda6</replaceable>\n"
+"root=/dev/<replaceable>hda6</replaceable>\n"
+"install=menu\n"
+"delay=20\n"
+"lba32\n"
+"image=/vmlinuz\n"
+"initrd=/initrd.img\n"
+"label=Debian"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:793
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install &debian;, "
+"just add an entry for the &debian; install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:803
 #, no-c-format
 msgid ""
-      "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
-      "boot=/dev/hda2\n"
-      "device=hd:\n"
-      "partition=6\n"
-      "root=/dev/hda6\n"
-      "magicboot=/usr/lib/yaboot/ofboot\n"
-      "timeout=50\n"
-      "image=/vmlinux\n"
-      "label=Debian\n"
-      "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
+"boot=/dev/hda2\n"
+"device=hd:\n"
+"partition=6\n"
+"root=/dev/hda6\n"
+"magicboot=/usr/lib/yaboot/ofboot\n"
+"timeout=50\n"
+"image=/vmlinux\n"
+"label=Debian\n"
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1218,15 +1434,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:817
 #, no-c-format
-msgid "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set a password for root:"
+msgid ""
+"In case you can login to the system via console, you can skip this section. "
+"If the system should be accessible via the network later on, you need to "
+"install SSH and set a password for root:"
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:823
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+"# aptitude install ssh\n"
+"# passwd"
 msgstr ""
 
 #. Tag: title
@@ -1239,15 +1458,22 @@ msgstr ""
 #: random-bits.xml:829
 #, no-c-format
 msgid ""
-      "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
-      "# tasksel install standard\n"
-      "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually."
+"As mentioned earlier, the installed system will be very basic. If you would "
+"like to make the system a bit more mature, there is an easy method to "
+"install all packages with <quote>standard</quote> priority: "
+"<informalexample><screen>\n"
+"# tasksel install standard\n"
+"</screen></informalexample> Of course, you can also just use "
+"<command>aptitude</command> to install packages individually."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:840
 #, no-c-format
-msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
+msgid ""
+"After the installation there will be a lot of downloaded packages in "
+"<filename>/var/cache/apt/archives/</filename>. You can free up some "
+"diskspace by running:"
 msgstr ""
 
 #. Tag: screen
@@ -1265,25 +1491,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:859
 #, no-c-format
-msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian-gnu; on a computer without an "
+"Ethernet card, but with just a remote gateway computer attached via a Null-"
+"Modem cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a &debian; mirror on it (e.g. to the "
+"Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:867
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:875
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:880
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1295,7 +1538,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:893
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where &debian; will "
+"be installed."
 msgstr ""
 
 #. Tag: para
@@ -1307,13 +1552,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:904
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:910
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
@@ -1325,28 +1575,33 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:923
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
 #: random-bits.xml:928
 #, no-c-format
 msgid ""
-      "#!/bin/sh\n"
-      "\n"
-      "# We remove running modules from kernel to avoid conflicts and to\n"
-      "# reconfigure them manually.\n"
-      "modprobe -r lp parport_pc\n"
-      "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
-      "modprobe plip\n"
-      "\n"
-      "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-      "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
-      "\n"
-      "# Configure gateway\n"
-      "modprobe iptable_nat\n"
-      "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
-      "echo 1 > /proc/sys/net/ipv4/ip_forward"
+"#!/bin/sh\n"
+"\n"
+"# We remove running modules from kernel to avoid conflicts and to\n"
+"# reconfigure them manually.\n"
+"modprobe -r lp parport_pc\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
+"modprobe plip\n"
+"\n"
+"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"\n"
+"# Configure gateway\n"
+"modprobe iptable_nat\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
+"echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
 #. Tag: title
@@ -1359,9 +1614,16 @@ msgstr ""
 #: random-bits.xml:935
 #, no-c-format
 msgid ""
-      "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
-      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
-      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to "
+"set parameters for kernel modules, you also need to do this at the boot "
+"prompt. For example, to boot the installer and set values for the <quote>io</"
+"quote> and <quote>irq</quote> options for the parport_pc module, enter the "
+"following at the boot prompt: <informalexample><screen>\n"
+"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc."
+"irq=<replaceable>7</replaceable>\n"
+"</screen></informalexample> Below are the answers that should be given "
+"during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1373,7 +1635,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:956
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1385,13 +1649,20 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:969
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:978
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1409,19 +1680,24 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:998
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1003
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1009
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
@@ -1433,67 +1709,112 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1030
 #, no-c-format
-msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
+msgid ""
+"In some countries PPP over Ethernet (PPPoE) is a common protocol for "
+"broadband (ADSL or cable) connections to an Internet Service Provider. "
+"Setting up a network connection using PPPoE is not supported by default in "
+"the installer, but can be made to work very simply. This section explains "
+"how."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1038
 #, no-c-format
-msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PPPoE connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1043
 #, no-c-format
-msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
+msgid ""
+"To have the option of setting up and using PPPoE during the installation, "
+"you will need to install using one of the CD-ROM/DVD images that are "
+"available. It is not supported for other installation methods (e.g. "
+"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1050
 #, no-c-format
-msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
+msgid ""
+"Installing over PPPoE is mostly the same as any other installation. The "
+"following steps explain the differences."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1058
 #, no-c-format
-msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
+msgid ""
+"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</"
+"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> "
+"for information on how to add a boot parameter. </para> </footnote>. This "
+"will ensure the component responsible for the setup of PPPoE (<classname>ppp-"
+"udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1073
 #, no-c-format
-msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
+msgid ""
+"Follow the regular initial steps of the installation (language, country and "
+"keyboard selection; the loading of additional installer components<footnote> "
+"<para> The <classname>ppp-udeb</classname> component is loaded as one of the "
+"additional components in this step. If you want to install at medium or low "
+"priority (expert mode), you can also manually select the <classname>ppp-"
+"udeb</classname> instead of entering the <quote>modules</quote> parameter at "
+"the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1092
 #, no-c-format
-msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
+msgid ""
+"The next step is the detection of network hardware, in order to identify any "
+"Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1098
 #, no-c-format
-msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
+msgid ""
+"After this the actual setup of PPPoE is started. The installer will probe "
+"all the detected Ethernet interfaces in an attempt to find a PPPoE "
+"concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1104
 #, no-c-format
-msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
+msgid ""
+"It is possible that the concentrator will not to be found at the first "
+"attempt. This can happen occasionally on slow or loaded networks or with "
+"faulty servers. In most cases a second attempt to detect the concentrator "
+"will be successful; to retry, select <guimenuitem>Configure and start a "
+"PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1113
 #, no-c-format
-msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
+msgid ""
+"After a concentrator is found, the user will be prompted to type the login "
+"information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1119
 #, no-c-format
-msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
+msgid ""
+"At this point the installer will use the provided information to establish "
+"the PPPoE connection. If the correct information was provided, the PPPoE "
+"connection should be configured and the installer should be able to use it "
+"to connect to the Internet and retrieve packages over it (if needed). If the "
+"login information is not correct or some error appears, the installer will "
+"stop, but the configuration can be attempted again by selecting the menu "
+"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
@@ -1505,49 +1826,89 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1140
 #, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
+msgid ""
+"The graphical version of the installer is only available for a limited "
+"number of architectures, including &arch-title;. The functionality of the "
+"graphical installer is essentially the same as that of the regular installer "
+"as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1148
 #, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
+msgid ""
+"Although the functionality is identical, the graphical installer still has a "
+"few significant advantages. The main advantage is that it supports more "
+"languages, namely those that use a character set that cannot be displayed "
+"with the regular <quote>newt</quote> frontend. It also has a few usability "
+"advantages such as the option to use a mouse, and in some cases several "
+"questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1157
 #, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
+msgid ""
+"The graphical installer is available with all CD images and with the hd-"
+"media installation method. To boot the graphical installer simply select the "
+"relevant option from the boot menu. Expert and rescue mode for the graphical "
+"installer can be selected from the <quote>Advanced options</quote> menu. The "
+"previously used boot methods <userinput>installgui</userinput>, "
+"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
+"still be used from the boot prompt which is shown after selecting the "
+"<quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1168
 #, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
+msgid ""
+"There is also a graphical installer image that can be netbooted. And there "
+"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> "
+"<para> The mini ISO image can be downloaded from a &debian; mirror as "
+"described in <xref linkend=\"downloading-files\"/>. Look for "
+"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
+"mainly useful for testing."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1181
 #, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
+msgid ""
+"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
+"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image "
+"can be downloaded from a &debian; mirror as described in <xref linkend="
+"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
+"</para> </footnote>. It should work on almost all PowerPC systems that have "
+"an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1195
 #, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
+msgid ""
+"Just as with the regular installer it is possible to add boot parameters "
+"when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1201
 #, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
+msgid ""
+"The graphical installer requires significantly more memory to run than the "
+"regular installer: &minimum-memory-gtk;. If insufficient memory is "
+"available, it will automatically fall back to the regular <quote>newt</"
+"quote> frontend."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1208
 #, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
+msgid ""
+"If the amount of memory in your system is below &minimum-memory;, the "
+"graphical installer may fail to boot at all while booting the regular "
+"installer would still work. Using the regular installer is recommended for "
+"systems with little available memory."
 msgstr ""
 
 #. Tag: title
@@ -1559,24 +1920,42 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:1219
 #, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
+msgid ""
+"As already mentioned, the graphical installer basically works the same as "
+"the regular installer and thus the rest of this manual can be used to guide "
+"you through the installation process."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1225
 #, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgid ""
+"If you prefer using the keyboard over the mouse, there are two things you "
+"need to know. To expand a collapsed list (used for example for the selection "
+"of countries within continents), you can use the <keycap>+</keycap> and "
+"<keycap>-</keycap> keys. For questions where more than one item can be "
+"selected (e.g. task selection), you first need to tab to the &BTN-CONT; "
+"button after making your selections; hitting enter will toggle a selection, "
+"not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1235
 #, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgid ""
+"If a dialog offers additional help information, a <guibutton>Help</"
+"guibutton> button will be displayed. The help information can be accessed "
+"either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:1241
 #, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgid ""
+"To switch to another console, you will also need to use the <keycap>Ctrl</"
+"keycap> key, just as with the X Window System. For example, to switch to VT2 "
+"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> "
+"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical "
+"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</"
+"keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""
-
diff --git a/po/tl/using-d-i.po b/po/tl/using-d-i.po
index bbba423e4..85197cce6 100644
--- a/po/tl/using-d-i.po
+++ b/po/tl/using-d-i.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -28,79 +29,147 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:8
 #, no-c-format
-msgid "The &debian; Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started."
+msgid ""
+"The &debian; Installer consists of a number of special-purpose components to "
+"perform each installation task. Each component performs its task, asking the "
+"user questions as necessary to do its job. The questions themselves are "
+"given priorities, and the priority of questions to be asked is set when the "
+"installer is started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:16
 #, no-c-format
-msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked."
+msgid ""
+"When a default installation is performed, only essential (high priority) "
+"questions will be asked. This results in a highly automated installation "
+"process with little user interaction. Components are automatically run in "
+"sequence; which components are run depends mainly on the installation method "
+"you use and on your hardware. The installer will use default values for "
+"questions that are not asked."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:25
 #, no-c-format
-msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified."
+msgid ""
+"If there is a problem, the user will see an error screen, and the installer "
+"menu may be shown in order to select some alternative action. If there are "
+"no problems, the user will never see the installer menu, but will simply "
+"answer questions for each component in turn. Serious error notifications are "
+"set to priority <quote>critical</quote> so the user will always be notified."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:34
 #, no-c-format
-msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
+msgid ""
+"Some of the defaults that the installer uses can be influenced by passing "
+"boot arguments when &d-i; is started. If, for example, you wish to force "
+"static network configuration (DHCP is used by default if available), you "
+"could add the boot parameter <userinput>netcfg/disable_dhcp=true</"
+"userinput>. See <xref linkend=\"installer-args\"/> for available options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:42
 #, no-c-format
-msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>."
+msgid ""
+"Power users may be more comfortable with a menu-driven interface, where each "
+"step is controlled by the user rather than the installer performing each "
+"step automatically in sequence. To use the installer in a manual, menu-"
+"driven way, add the boot argument <userinput>priority=medium</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:50
 #, no-c-format
-msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;."
+msgid ""
+"If your hardware requires you to pass options to kernel modules as they are "
+"installed, you will need to start the installer in <quote>expert</quote> "
+"mode. This can be done by either using the <command>expert</command> command "
+"to start the installer or by adding the boot argument "
+"<userinput>priority=low</userinput>. Expert mode gives you full control over "
+"&d-i;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:59
 #, no-c-format
-msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgid ""
+"For this architecture the &d-i; supports two different user interfaces: a "
+"character-based one and a graphical one. The character-based interface is "
+"used by default unless you selected the <quote>Graphical install</quote> "
+"option in the initial boot menu. For more information about the graphical "
+"installer, please refer to <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:67
 #, no-c-format
-msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
+msgid ""
+"For this architecture the installer uses a character-based user interface. A "
+"graphical user interface is currently not available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:72
 #, no-c-format
-msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
+msgid ""
+"In the character-based environment the use of a mouse is not supported. Here "
+"are the keys you can use to navigate within the various dialogs. The "
+"<keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move "
+"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> "
+"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move "
+"<quote>backward</quote> between displayed buttons and selections. The "
+"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items "
+"within a scrollable list, and also scroll the list itself. In addition, in "
+"long lists, you can type a letter to cause the list to scroll directly to "
+"the section with items starting with the letter you typed and use <keycap>Pg-"
+"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The "
+"<keycap>space bar</keycap> selects an item such as a checkbox. Use "
+"&enterkey; to activate choices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:89
 #, no-c-format
-msgid "Some dialogs may offer additional help information. If help is available this will be indicated on the bottom line of the screen by displaying that help information can be accessed by pressing the <keycap>F1</keycap> key."
+msgid ""
+"Some dialogs may offer additional help information. If help is available "
+"this will be indicated on the bottom line of the screen by displaying that "
+"help information can be accessed by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:95
 #, no-c-format
-msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
+msgid ""
+"S/390 does not support virtual consoles. You may open a second and third ssh "
+"session to view the logs described below."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:100
 #, no-c-format
-msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"Error messages and logs are redirected to the fourth console. You can access "
+"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</"
+"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing "
+"the <keycap>F4</keycap> function key); get back to the main installer "
+"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></"
+"keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:110
 #, no-c-format
-msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
+msgid ""
+"These messages can also be found in <filename>/var/log/syslog</filename>. "
+"After installation, this log is copied to <filename>/var/log/installer/"
+"syslog</filename> on your new system. Other installation messages may be "
+"found in <filename>/var/log/</filename> during the installation, and "
+"<filename>/var/log/installer/</filename> after the computer has been booted "
+"into the installed system."
 msgstr ""
 
 #. Tag: title
@@ -112,7 +181,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:125
 #, no-c-format
-msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
+msgid ""
+"Here is a list of installer components with a brief description of each "
+"component's purpose. Details you might need to know about using a particular "
+"component are in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: term
@@ -124,13 +196,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:136
 #, no-c-format
-msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
+msgid ""
+"Shows the list of components to the user during installer operation, and "
+"starts a component when it is selected. Main-menu's questions are set to "
+"priority medium, so if your priority is set to high or critical (high is the "
+"default), you will not see the menu. On the other hand, if there is an error "
+"which requires your intervention, the question priority may be downgraded "
+"temporarily to allow you to resolve the problem, and in that case the menu "
+"may appear."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:146
 #, no-c-format
-msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
+msgid ""
+"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly "
+"to back all the way out of the currently running component."
 msgstr ""
 
 #. Tag: term
@@ -142,7 +223,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:155
 #, no-c-format
-msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
+msgid ""
+"Allows the user to select localization options for the installation and the "
+"installed system: language, country and locales. The installer will display "
+"messages in the selected language, unless the translation for that language "
+"is not complete in which case some messages may be shown in English."
 msgstr ""
 
 #. Tag: term
@@ -154,7 +239,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:167
 #, no-c-format
-msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
+msgid ""
+"Shows a list of keyboards, from which the user chooses the model which "
+"matches his own."
 msgstr ""
 
 #. Tag: term
@@ -166,7 +253,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:176
 #, no-c-format
-msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
+msgid ""
+"Automatically detects most of the system's hardware, including network "
+"cards, disk drives, and PCMCIA."
 msgstr ""
 
 #. Tag: term
@@ -190,7 +279,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:193
 #, no-c-format
-msgid "Configures the computer's network connections so it can communicate over the internet."
+msgid ""
+"Configures the computer's network connections so it can communicate over the "
+"internet."
 msgstr ""
 
 #. Tag: term
@@ -202,7 +293,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:202
 #, no-c-format
-msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
+msgid ""
+"Searches for ISO images (<filename>.iso</filename> files) on hard drives."
 msgstr ""
 
 #. Tag: term
@@ -214,7 +306,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:210
 #, no-c-format
-msgid "Presents a list of &debian; archive mirrors. The user may choose the source of his installation packages."
+msgid ""
+"Presents a list of &debian; archive mirrors. The user may choose the source "
+"of his installation packages."
 msgstr ""
 
 #. Tag: term
@@ -226,7 +320,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:219
 #, no-c-format
-msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
+msgid ""
+"Checks integrity of a CD-ROM. This way, the user may assure him/herself that "
+"the installation CD-ROM was not corrupted."
 msgstr ""
 
 #. Tag: term
@@ -238,7 +334,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:228
 #, no-c-format
-msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
+msgid ""
+"Lowmem tries to detect systems with low memory and then does various tricks "
+"to remove unnecessary parts of &d-i; from the memory (at the cost of some "
+"features)."
 msgstr ""
 
 #. Tag: term
@@ -250,7 +349,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:238
 #, no-c-format
-msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
+msgid ""
+"Anna's Not Nearly APT. Installs packages which have been retrieved from the "
+"chosen mirror or CD."
 msgstr ""
 
 #. Tag: term
@@ -274,7 +375,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:255
 #, no-c-format
-msgid "Updates the system clock and determines whether the clock is set to UTC or not."
+msgid ""
+"Updates the system clock and determines whether the clock is set to UTC or "
+"not."
 msgstr ""
 
 #. Tag: term
@@ -298,7 +401,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:272
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
+msgid ""
+"Allows the user to partition disks attached to the system, create file "
+"systems on the selected partitions, and attach them to the mountpoints. "
+"Included are also interesting features like a fully automatic mode or LVM "
+"support. This is the preferred partitioning tool in &debian;."
 msgstr ""
 
 #. Tag: term
@@ -310,7 +417,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:284
 #, no-c-format
-msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
+msgid ""
+"Allows the user to partition disks attached to the system. A partitioning "
+"program appropriate to your computer's architecture is chosen."
 msgstr ""
 
 #. Tag: term
@@ -322,7 +431,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:294
 #, no-c-format
-msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
+msgid ""
+"Displays a list of partitions, and creates file systems on the selected "
+"partitions according to user instructions."
 msgstr ""
 
 #. Tag: term
@@ -334,7 +445,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:303
 #, no-c-format
-msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
+msgid ""
+"Helps the user with the configuration of the <firstterm>LVM</firstterm> "
+"(Logical Volume Manager)."
 msgstr ""
 
 #. Tag: term
@@ -346,7 +459,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:312
 #, no-c-format
-msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
+msgid ""
+"Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant "
+"Array of Inexpensive Disks). This Software RAID is usually superior to the "
+"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
 #. Tag: term
@@ -358,7 +474,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:323
 #, no-c-format
-msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
+msgid ""
+"Installs the most basic set of packages which would allow the computer to "
+"operate under &debian-gnu; when rebooted."
 msgstr ""
 
 #. Tag: term
@@ -370,7 +488,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:332
 #, no-c-format
-msgid "Configures apt, mostly automatically, based on what media the installer is running from."
+msgid ""
+"Configures apt, mostly automatically, based on what media the installer is "
+"running from."
 msgstr ""
 
 #. Tag: term
@@ -382,7 +502,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:341
 #, no-c-format
-msgid "Uses <classname>tasksel</classname> to select and install additional software."
+msgid ""
+"Uses <classname>tasksel</classname> to select and install additional "
+"software."
 msgstr ""
 
 #. Tag: term
@@ -394,7 +516,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:349
 #, no-c-format
-msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
+msgid ""
+"Detects currently installed operating systems on the computer and passes "
+"this information to the bootloader-installer, which may offer you an ability "
+"to add discovered operating systems to the bootloader's start menu. This way "
+"the user could easily choose at the boot time which operating system to "
+"start."
 msgstr ""
 
 #. Tag: term
@@ -406,7 +533,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:361
 #, no-c-format
-msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
+msgid ""
+"The various bootloader installers each install a boot loader program on the "
+"hard disk, which is necessary for the computer to start up using &arch-"
+"kernel; without using a floppy or CD-ROM. Many boot loaders allow the user "
+"to choose an alternate operating system each time the computer boots."
 msgstr ""
 
 #. Tag: term
@@ -418,7 +549,8 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:372
 #, no-c-format
-msgid "Allows the user to execute a shell from the menu, or in the second console."
+msgid ""
+"Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
 #. Tag: term
@@ -430,7 +562,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:381
 #, no-c-format
-msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to &debian; developers later."
+msgid ""
+"Provides a way for the user to record information on a floppy disk, network, "
+"hard disk, or other media when trouble is encountered, in order to "
+"accurately report installer software problems to &debian; developers later."
 msgstr ""
 
 #. Tag: title
@@ -442,7 +577,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:400
 #, no-c-format
-msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
+msgid ""
+"In this section we will describe each installer component in detail. The "
+"components have been grouped into stages that should be recognizable for "
+"users. They are presented in the order they appear during the install. Note "
+"that not all modules will be used for every installation; which modules are "
+"actually used depends on the installation method you use and on your "
+"hardware."
 msgstr ""
 
 #. Tag: title
@@ -454,19 +595,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:413
 #, no-c-format
-msgid "Let's assume the &debian; Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
+msgid ""
+"Let's assume the &debian; Installer has booted and you are facing its first "
+"screen. At this time, the capabilities of &d-i; are still quite limited. It "
+"doesn't know much about your hardware, preferred language, or even the task "
+"it should perform. Don't worry. Because &d-i; is quite clever, it can "
+"automatically probe your hardware, locate the rest of its components and "
+"upgrade itself to a capable installation system. However, you still need to "
+"help &d-i; with some information it can't determine automatically (like "
+"selecting your preferred language, keyboard layout or desired network "
+"mirror)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:426
 #, no-c-format
-msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
+msgid ""
+"You will notice that &d-i; performs <firstterm>hardware detection</"
+"firstterm> several times during this stage. The first time is targeted "
+"specifically at the hardware needed to load installer components (e.g. your "
+"CD-ROM or network card). As not all drivers may be available during this "
+"first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:434
 #, no-c-format
-msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
+msgid ""
+"During hardware detection &d-i; checks if any of the drivers for the "
+"hardware devices in your system require firmware to be loaded. If any "
+"firmware is requested but unavailable, a dialog will be displayed that "
+"allows the missing firmware to be loaded from a removable medium. See <xref "
+"linkend=\"loading-firmware\"/> for further details."
 msgstr ""
 
 #. Tag: title
@@ -478,43 +638,75 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:451
 #, no-c-format
-msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system."
+msgid ""
+"One of the first things &d-i; does, is to check available memory. If the "
+"available memory is limited, this component will make some changes in the "
+"installation process which hopefully will allow you to install &debian-gnu; "
+"on your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:458
 #, no-c-format
-msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
+msgid ""
+"The first measure taken to reduce memory consumption by the installer is to "
+"disable translations, which means that the installation can only be done in "
+"English. Of course, you can still localize the installed system after the "
+"installation has completed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:465
 #, no-c-format
-msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
+msgid ""
+"If that is not sufficient, the installer will further reduce memory "
+"consumption by loading only those components essential to complete a basic "
+"installation. This reduces the functionality of the installation system. You "
+"will be given the opportunity to load additional components manually, but "
+"you should be aware that each component you select will use additional "
+"memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:474
 #, no-c-format
-msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
+msgid ""
+"If the installer runs in low memory mode, it is recommended to create a "
+"relatively large swap partition (64&ndash;128MB). The swap partition will be "
+"used as virtual memory and thus increases the amount of memory available to "
+"the system. The installer will activate the swap partition as early as "
+"possible in the installation process. Note that heavy use of swap will "
+"reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:484
 #, no-c-format
-msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
+msgid ""
+"Despite these measures, it is still possible that your system freezes, that "
+"unexpected errors occur or that processes are killed by the kernel because "
+"the system runs out of memory (which will result in <quote>Out of memory</"
+"quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:491
 #, no-c-format
-msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
+msgid ""
+"For example, it has been reported that creating a big ext3 file system fails "
+"in low memory mode when there is insufficient swap space. If a larger swap "
+"doesn't help, try creating the file system as ext2 (which is an essential "
+"component of the installer) instead. It is possible to change an ext2 "
+"partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:499
 #, no-c-format
-msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
+msgid ""
+"It is possible to force the installer to use a higher lowmem level than the "
+"one based on available memory by using the boot parameter <quote>lowmem</"
+"quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
@@ -526,61 +718,116 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:516
 #, no-c-format
-msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, location and locales."
+msgid ""
+"In most cases the first questions you will be asked concern the selection of "
+"localization options to be used both for the installation and for the "
+"installed system. The localization options consist of language, location and "
+"locales."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:523
 #, no-c-format
-msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
+msgid ""
+"The language you choose will be used for the rest of the installation "
+"process, provided a translation of the different dialogs is available. If no "
+"valid translation is available for the selected language, the installer will "
+"default to English."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:530
 #, no-c-format
-msgid "The selected geographic location (in most cases a country) will be used later in the installation process to select the correct time zone and a &debian; mirror appropriate for that country. Language and country together will help determine the default locale for your system and select the correct keyboard layout."
+msgid ""
+"The selected geographic location (in most cases a country) will be used "
+"later in the installation process to select the correct time zone and a "
+"&debian; mirror appropriate for that country. Language and country together "
+"will help determine the default locale for your system and select the "
+"correct keyboard layout."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:538
 #, no-c-format
-msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
+msgid ""
+"You will first be asked to select your preferred language. The language "
+"names are listed both in English (left side) and in the language itself "
+"(right side); the names on the right side are also shown in the proper "
+"script for the language. The list is sorted on the English names. At the top "
+"of the list is an extra option that allows you to select the <quote>C</"
+"quote> locale instead of a language. Choosing the <quote>C</quote> locale "
+"will result in the installation proceding in English; the installed system "
+"will have no localization support as the <classname>locales</classname> "
+"package will not be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:550
 #, no-c-format
-msgid "Next you will be asked to select your geographic location. If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
+msgid ""
+"Next you will be asked to select your geographic location. If you selected a "
+"language that is recognized as an official language for more than one "
+"country<footnote> <para> In technical terms: where multiple locales exist "
+"for that language with differing country codes. </para> </footnote>, you "
+"will be shown a list of only those countries. To select a country that is "
+"not in that list, choose <guimenuitem>other</guimenuitem> (the last option). "
+"You will then be presented with a list of continents; selecting a continent "
+"will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:567
 #, no-c-format
-msgid "If the language has only one country associated with it, a list of countries will be displayed for the continent or region the country belongs to, with that country selected as the default. Use the <guibutton>Go Back</guibutton> option to select countries on a different continent."
+msgid ""
+"If the language has only one country associated with it, a list of countries "
+"will be displayed for the continent or region the country belongs to, with "
+"that country selected as the default. Use the <guibutton>Go Back</guibutton> "
+"option to select countries on a different continent."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:574
 #, no-c-format
-msgid "It is important to select the country where you live or where you are located as it determines the time zone that will be configured for the installed system."
+msgid ""
+"It is important to select the country where you live or where you are "
+"located as it determines the time zone that will be configured for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:580
 #, no-c-format
-msgid "If you selected a combination of language and country for which no locale is defined and there exist multiple locales for the language, then the installer will allow you to choose which of those locales you prefer as the default locale for the installed system<footnote> <para> At medium and low priority you can always select your preferred locale from those available for the selected language (if there's more than one). </para> </footnote>. In all other cases a default locale will be selected based on the selected language and country."
+msgid ""
+"If you selected a combination of language and country for which no locale is "
+"defined and there exist multiple locales for the language, then the "
+"installer will allow you to choose which of those locales you prefer as the "
+"default locale for the installed system<footnote> <para> At medium and low "
+"priority you can always select your preferred locale from those available "
+"for the selected language (if there's more than one). </para> </footnote>. "
+"In all other cases a default locale will be selected based on the selected "
+"language and country."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:595
 #, no-c-format
-msgid "Any default locale selected as described in the previous paragraph will use <firstterm>UTF-8</firstterm> as character encoding."
+msgid ""
+"Any default locale selected as described in the previous paragraph will use "
+"<firstterm>UTF-8</firstterm> as character encoding."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:600
 #, no-c-format
-msgid "If you are installing at low priority, you will have the option of selecting additional locales, including so-called <quote>legacy</quote> locales<footnote> <para> Legacy locales are locales which do not use UTF-8, but one of the older standards for character encoding such as ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by Japanese). </para> </footnote>, to be generated for the installed system; if you do, you will be asked which of the selected locales should be the default for the installed system."
+msgid ""
+"If you are installing at low priority, you will have the option of selecting "
+"additional locales, including so-called <quote>legacy</quote> "
+"locales<footnote> <para> Legacy locales are locales which do not use UTF-8, "
+"but one of the older standards for character encoding such as "
+"ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by "
+"Japanese). </para> </footnote>, to be generated for the installed system; if "
+"you do, you will be asked which of the selected locales should be the "
+"default for the installed system."
 msgstr ""
 
 #. Tag: title
@@ -592,13 +839,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:626
 #, no-c-format
-msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>dpkg-reconfigure keyboard-configuration</command> as root after you have completed the installation)."
+msgid ""
+"Keyboards are often tailored to the characters used in a language. Select a "
+"layout that conforms to the keyboard you are using, or select something "
+"close if the keyboard layout you want isn't represented. Once the system "
+"installation is complete, you'll be able to select a keyboard layout from a "
+"wider range of choices (run <command>dpkg-reconfigure keyboard-"
+"configuration</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:636
 #, no-c-format
-msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration."
+msgid ""
+"Move the highlight to the keyboard selection you desire and press "
+"&enterkey;. Use the arrow keys to move the highlight &mdash; they are in the "
+"same place in all national language keyboard layouts, so they are "
+"independent of the keyboard configuration."
 msgstr ""
 
 #. Tag: title
@@ -610,25 +867,51 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:664
 #, no-c-format
-msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the &debian; Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
+msgid ""
+"When installing via the <emphasis>hd-media</emphasis> method, there will be "
+"a moment where you need to find and mount the &debian; Installer iso image "
+"in order to get the rest of the installation files. The component "
+"<command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:671
 #, no-c-format
-msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid &debian; iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
+msgid ""
+"At first, <command>iso-scan</command> automatically mounts all block devices "
+"(e.g. partitions) which have some known filesystem on them and sequentially "
+"searches for filenames ending with <filename>.iso</filename> (or <filename>."
+"ISO</filename> for that matter). Beware that the first attempt scans only "
+"files in the root directory and in the first level of subdirectories (i.e. "
+"it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, "
+"<filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not "
+"<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). "
+"After an iso image has been found, <command>iso-scan</command> checks its "
+"content to determine if the image is a valid &debian; iso image or not. In "
+"the former case we are done, in the latter <command>iso-scan</command> seeks "
+"for another image."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:688
 #, no-c-format
-msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
+msgid ""
+"In case the previous attempt to find an installer iso image fails, "
+"<command>iso-scan</command> will ask you whether you would like to perform a "
+"more thorough search. This pass doesn't just look into the topmost "
+"directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:695
 #, no-c-format
-msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
+msgid ""
+"If <command>iso-scan</command> does not discover your installer iso image, "
+"reboot back to your original operating system and check if the image is "
+"named correctly (ending in <filename>.iso</filename>), if it is placed on a "
+"filesystem recognizable by &d-i;, and if it is not corrupted (verify the "
+"checksum). Experienced Unix users could do this without rebooting on the "
+"second console."
 msgstr ""
 
 #. Tag: title
@@ -640,7 +923,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:718
 #, no-c-format
-msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
+msgid ""
+"As you enter this step, if the system detects that you have more than one "
+"network device, you'll be asked to choose which device will be your "
+"<emphasis>primary</emphasis> network interface, i.e. the one which you want "
+"to use for installation. The other interfaces won't be configured at this "
+"time. You may configure additional interfaces after installation is "
+"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> "
+"<manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: title
@@ -652,7 +942,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:733
 #, no-c-format
-msgid "By default, &d-i; tries to configure your computer's network automatically as far as possible. If the automatic configuration fails, that may be caused by many factors ranging from an unplugged network cable to missing infrastructure for automatic configuration. For further explanation in case of errors, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. Sometimes the network services used for autoconfiguration can be slow in their responses, so if you are sure everything is in place, simply start the autoconfiguration attempt again. If autoconfiguration fails repeatedly, you can instead choose the manual network setup."
+msgid ""
+"By default, &d-i; tries to configure your computer's network automatically "
+"as far as possible. If the automatic configuration fails, that may be caused "
+"by many factors ranging from an unplugged network cable to missing "
+"infrastructure for automatic configuration. For further explanation in case "
+"of errors, check the error messages on the fourth console. In any case, you "
+"will be asked if you want to retry, or if you want to perform a manual "
+"setup. Sometimes the network services used for autoconfiguration can be slow "
+"in their responses, so if you are sure everything is in place, simply start "
+"the autoconfiguration attempt again. If autoconfiguration fails repeatedly, "
+"you can instead choose the manual network setup."
 msgstr ""
 
 #. Tag: title
@@ -664,13 +964,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:753
 #, no-c-format
-msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network name</quote>) and a <computeroutput>WEP key</computeroutput> or <computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
+msgid ""
+"The manual network setup in turn asks you a number of questions about your "
+"network, notably <computeroutput>IP address</computeroutput>, "
+"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</"
+"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and "
+"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a "
+"wireless network interface, you will be asked to provide your "
+"<computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network "
+"name</quote>) and a <computeroutput>WEP key</computeroutput> or "
+"<computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers "
+"from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:769
 #, no-c-format
-msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
+msgid ""
+"Some technical details you might, or might not, find handy: the program "
+"assumes the network IP address is the bitwise-AND of your system's IP "
+"address and your netmask. The default broadcast address is calculated as the "
+"bitwise OR of your system's IP address with the bitwise negation of the "
+"netmask. It will also guess your gateway. If you can't find any of these "
+"answers, use the offered defaults &mdash; if necessary, you can change them "
+"by editing <filename>/etc/network/interfaces</filename> once the system has "
+"been installed."
 msgstr ""
 
 #. Tag: title
@@ -682,13 +1000,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:785
 #, no-c-format
-msgid "From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
+msgid ""
+"From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 "
+"as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and "
+"IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:791
 #, no-c-format
-msgid "Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration using NDP (Neighbor Discovery Protocol, including recursive DNS server (RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed stateless/stateful autoconfiguration (address configuration via NDP, additional parameters via DHCPv6)."
+msgid ""
+"Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration "
+"Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration "
+"using NDP (Neighbor Discovery Protocol, including recursive DNS server "
+"(RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed "
+"stateless/stateful autoconfiguration (address configuration via NDP, "
+"additional parameters via DHCPv6)."
 msgstr ""
 
 #. Tag: title
@@ -700,7 +1027,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:839
 #, no-c-format
-msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
+msgid ""
+"The installer will first attempt to connect to a time server on the Internet "
+"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set "
+"the system time. If this does not succeed, the installer will assume the "
+"time and date obtained from the system clock when the installation system "
+"was booted are correct. It is not possible to manually set the system time "
+"during the installation process."
 msgstr ""
 
 #. Tag: para
@@ -712,25 +1045,38 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:861
 #, no-c-format
-msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone."
+msgid ""
+"Depending on the location selected earlier in the installation process, you "
+"may be shown a list of time zones relevant for that location. If your "
+"location has only one time zone and you are doing a default installation, "
+"you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:869
 #, no-c-format
-msgid "In expert mode or when installing at medium priority, you will have the additional option to select <quote>Coordinated Universal Time</quote> (UTC) as time zone."
+msgid ""
+"In expert mode or when installing at medium priority, you will have the "
+"additional option to select <quote>Coordinated Universal Time</quote> (UTC) "
+"as time zone."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:875
 #, no-c-format
-msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
+msgid ""
+"If for some reason you wish to set a time zone for the installed system that "
+"does <emphasis>not</emphasis> match the selected location, there are two "
+"options."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:886
 #, no-c-format
-msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:"
+msgid ""
+"The simplest option is to just select a different time zone after the "
+"installation has been completed and you've booted into the new system. The "
+"command to do this is:"
 msgstr ""
 
 #. Tag: screen
@@ -742,13 +1088,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:898
 #, no-c-format
-msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
+msgid ""
+"Alternatively, the time zone can be set at the very start of the "
+"installation by passing the parameter <userinput>time/"
+"zone=<replaceable>value</replaceable></userinput> when you boot the "
+"installation system. The value should of course be a valid time zone, for "
+"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:912
 #, no-c-format
-msgid "For automated installations the time zone can be set to any desired value using preseeding."
+msgid ""
+"For automated installations the time zone can be set to any desired value "
+"using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -760,7 +1113,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:927
 #, no-c-format
-msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
+msgid ""
+"Just before configuring the clock, the installer will allow you to set up "
+"the <quote>root</quote> account and/or an account for the first user. Other "
+"user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
@@ -772,19 +1128,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:945
 #, no-c-format
-msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
+msgid ""
+"The <emphasis>root</emphasis> account is also called the <emphasis>super-"
+"user</emphasis>; it is a login that bypasses all security protection on your "
+"system. The root account should only be used to perform system "
+"administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:953
 #, no-c-format
-msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
+msgid ""
+"Any password you create should contain at least 6 characters, and should "
+"contain both upper- and lower-case characters, as well as punctuation "
+"characters. Take extra care when setting your root password, since it is "
+"such a powerful account. Avoid dictionary words or use of any personal "
+"information which could be guessed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:961
 #, no-c-format
-msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
+msgid ""
+"If anyone ever tells you they need your root password, be extremely wary. "
+"You should normally never give your root password out, unless you are "
+"administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
@@ -796,25 +1164,42 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:973
 #, no-c-format
-msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
+msgid ""
+"The system will ask you whether you wish to create an ordinary user account "
+"at this point. This account should be your main personal log-in. You should "
+"<emphasis>not</emphasis> use the root account for daily use or as your "
+"personal login."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:982
 #, no-c-format
-msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
+msgid ""
+"Why not? Well, one reason to avoid using root's privileges is that it is "
+"very easy to do irreparable damage as root. Another reason is that you might "
+"be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; "
+"that is a program that takes advantage of your super-user powers to "
+"compromise the security of your system behind your back. Any good book on "
+"Unix system administration will cover this topic in more detail &mdash; "
+"consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:992
 #, no-c-format
-msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
+msgid ""
+"You will first be prompted for the user's full name. Then you'll be asked "
+"for a name for the user account; generally your first name or something "
+"similar will suffice and indeed will be the default. Finally, you will be "
+"prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:999
 #, no-c-format
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgid ""
+"If at any point after installation you would like to create another account, "
+"use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
@@ -826,28 +1211,45 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1011
 #, no-c-format
-msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
+msgid ""
+"At this time, after hardware detection has been executed a final time, &d-i; "
+"should be at its full strength, customized for the user's needs and ready to "
+"do some real work. As the title of this section indicates, the main task of "
+"the next few components lies in partitioning your disks, creating "
+"filesystems, assigning mountpoints and optionally configuring closely "
+"related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1032
 #, no-c-format
-msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
+msgid ""
+"If you are uncomfortable with partitioning, or just want to know more "
+"details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1038
 #, no-c-format
 msgid ""
-      "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
-      "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n"
-      "</screen></informalexample> Note that this will make any existing data on that disk inaccessible."
+"If a hard disk has previously used under Solaris, the partitioner may not "
+"detect the size of the drive correctly. Creating a new partition table does "
+"not fix this issue. What does help, is to <quote>zero</quote> the first few "
+"sectors of the drive: <informalexample><screen>\n"
+"# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; "
+"sync\n"
+"</screen></informalexample> Note that this will make any existing data on "
+"that disk inaccessible."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1051
 #, no-c-format
-msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
+msgid ""
+"First you will be given the opportunity to automatically partition either an "
+"entire drive, or available free space on a drive. This is also called "
+"<quote>guided</quote> partitioning. If you do not want to autopartition, "
+"choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
@@ -859,19 +1261,31 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1062
 #, no-c-format
-msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
+msgid ""
+"The partitioner used in &d-i; is fairly versatile. It allows to create many "
+"different partitioning schemes, using various partition tables, file systems "
+"and advanced block devices."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1068
 #, no-c-format
-msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
+msgid ""
+"Exactly which options are available depends mainly on the architecture, but "
+"also on other factors. For example, on systems with limited internal memory "
+"some options may not be available. Defaults may vary as well. The type of "
+"partition table used by default can for example be different for large "
+"capacity hard disks than for smaller hard disks. Some options can only be "
+"changed when installing at medium or low debconf priority; at higher "
+"priorities sensible defaults will be used."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1079
 #, no-c-format
-msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
+msgid ""
+"The installer supports various forms of advanced partitioning and use of "
+"storage devices, which in many cases can be used in combination."
 msgstr ""
 
 #. Tag: emphasis
@@ -901,13 +1315,18 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1096
 #, no-c-format
-msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
+msgid ""
+"<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1098
 #, no-c-format
-msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
+msgid ""
+"Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support "
+"for Serial ATA RAID is currently only available if enabled when the "
+"installer is booted. Further information is available on <ulink url=\"&url-d-"
+"i-sataraid;\">our Wiki</ulink>."
 msgstr ""
 
 #. Tag: para
@@ -919,7 +1338,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1106
 #, no-c-format
-msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
+msgid ""
+"See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. "
+"Support for multipath is currently only available if enabled when the "
+"installer is booted."
 msgstr ""
 
 #. Tag: para
@@ -931,13 +1353,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1118
 #, no-c-format
-msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></phrase>"
+msgid ""
+"<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> "
+"<emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</"
+"emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></"
+"phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1123
 #, no-c-format
-msgid "The default file system selected in most cases is ext3; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
+msgid ""
+"The default file system selected in most cases is ext3; for <filename>/boot</"
+"filename> partitions ext2 will be selected by default when guided "
+"partitioning is used."
 msgstr ""
 
 #. Tag: para
@@ -973,37 +1402,59 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1141
 #, no-c-format
-msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:"
+msgid ""
+"As ZFS support in the installer is still in development, only a basic subset "
+"of ZFS features are supported. Some of them can be enabled manually after "
+"the initial install, but there are some caveats:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1146
 #, no-c-format
-msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the <quote>zfs create</quote> command."
+msgid ""
+"Each ZFS pool will host only one filesystem. After install is finished, more "
+"filesystems can be created on this pool by using the <quote>zfs create</"
+"quote> command."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1151
 #, no-c-format
-msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the <quote>zpool add</quote> command, or into a mirrored pool by using the <quote>zpool attach</quote> command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system."
+msgid ""
+"Each ZFS pool will be composed of exactly one partition. After install is "
+"finished, a single-device ZFS pool can be converted into a multi-device pool "
+"by using the <quote>zpool add</quote> command, or into a mirrored pool by "
+"using the <quote>zpool attach</quote> command. However, you shouldn't do "
+"this on the pool that hosts root filesystem, as it would prevent GRUB from "
+"booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1159
 #, no-c-format
-msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the <quote>compression</quote> property via the <quote>zfs set</quote> command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system."
+msgid ""
+"Compression is not currently supported. After the install is finished, "
+"compression can be enabled by setting the <quote>compression</quote> "
+"property via the <quote>zfs set</quote> command. However, if a compression "
+"algorithm other than the default (lzjb) is used on the pool that hosts your "
+"root filesystem, this may prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1168
 #, no-c-format
-msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
+msgid ""
+"<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1170
 #, no-c-format
-msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
+msgid ""
+"Support for the Reiser file system is no longer available by default. When "
+"the installer is running at medium or low debconf priority it can be enabled "
+"by selecting the <classname>partman-reiserfs</classname> component. Only "
+"version 3 of the file system is supported."
 msgstr ""
 
 #. Tag: emphasis
@@ -1015,7 +1466,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1178
 #, no-c-format
-msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
+msgid ""
+"Used on some systems to read flash memory. It is not possible to create new "
+"jffs2 partitions."
 msgstr ""
 
 #. Tag: emphasis
@@ -1027,7 +1480,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1184
 #, no-c-format
-msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
+msgid ""
+"Existing partitions will be recognized and it is possible to assign mount "
+"points for them. It is not possible to create new qnx4 partitions."
 msgstr ""
 
 #. Tag: para
@@ -1045,7 +1500,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1193
 #, no-c-format
-msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
+msgid ""
+"Existing NTFS partitions can be resized and it is possible to assign mount "
+"points for them. It is not possible to create new NTFS partitions."
 msgstr ""
 
 #. Tag: title
@@ -1057,49 +1514,89 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1204
 #, no-c-format
-msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
+msgid ""
+"If you choose guided partitioning, you may have three options: to create "
+"partitions directly on the hard disk (classic method), or to create them "
+"using Logical Volume Management (LVM), or to create them using encrypted "
+"LVM<footnote> <para> The installer will encrypt the LVM volume group using a "
+"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> "
+"support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1219
 #, no-c-format
-msgid "The option to use (encrypted) LVM may not be available on all architectures."
+msgid ""
+"The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1224
 #, no-c-format
-msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
+msgid ""
+"When using LVM or encrypted LVM, the installer will create most partitions "
+"inside one big partition; the advantage of this method is that partitions "
+"inside this big partition can be resized relatively easily later. In the "
+"case of encrypted LVM the big partition will not be readable without knowing "
+"a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1233
 #, no-c-format
-msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
+msgid ""
+"When using encrypted LVM, the installer will also automatically erase the "
+"disk by writing random data to it. This further improves security (as it "
+"makes it impossible to tell which parts of the disk are in use and also "
+"makes sure that any traces of previous installations are erased), but may "
+"take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1242
 #, no-c-format
-msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
+msgid ""
+"If you choose guided partitioning using LVM or encrypted LVM, some changes "
+"in the partition table will need to be written to the selected disk while "
+"LVM is being set up. These changes effectively erase all data that is "
+"currently on the selected hard disk and you will not be able to undo them "
+"later. However, the installer will ask you to confirm these changes before "
+"they are written to disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1252
 #, no-c-format
-msgid "If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
+msgid ""
+"If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic "
+"or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked "
+"to select the disk you want to use. Check that all your disks are listed "
+"and, if you have several disks, make sure you select the correct one. The "
+"order they are listed in may differ from what you are used to. The size of "
+"the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1261
 #, no-c-format
-msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. <phrase arch=\"linux-any\"> If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. </phrase>"
+msgid ""
+"Any data on the disk you select will eventually be lost, but you will always "
+"be asked to confirm any changes before they are written to the disk. <phrase "
+"arch=\"linux-any\"> If you have selected the classic method of partitioning, "
+"you will be able to undo any changes right until the end; when using "
+"(encrypted) LVM this is not possible. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1271
 #, no-c-format
-msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
+msgid ""
+"Next, you will be able to choose from the schemes listed in the table below. "
+"All schemes have their pros and cons, some of which are discussed in <xref "
+"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in "
+"mind that guided partitioning needs a certain minimal amount of free space "
+"to operate with. If you don't give it at least about 1GB of space (depends "
+"on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
@@ -1171,54 +1668,79 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1307
 #, no-c-format
-msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
+msgid ""
+"<filename>/</filename>, <filename>/home</filename>, <filename>/usr</"
+"filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1316
 #, no-c-format
-msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
+msgid ""
+"If you choose guided partitioning using (encrypted) LVM, the installer will "
+"also create a separate <filename>/boot</filename> partition. The other "
+"partitions, including the swap partition, will be created inside the LVM "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1322
 #, no-c-format
-msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
+msgid ""
+"If you choose guided partitioning for your IA-64 system, there will be an "
+"additional partition, formatted as a FAT16 bootable filesystem, for the EFI "
+"boot loader. There is also an additional menu item in the formatting menu to "
+"manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1330
 #, no-c-format
-msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
+msgid ""
+"After selecting a scheme, the next screen will show your new partition "
+"table, including information on whether and how partitions will be formatted "
+"and where they will be mounted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1336
 #, no-c-format
 msgid ""
-      "The list of partitions might look like this: <informalexample><screen>\n"
-      "  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
-      "        #1 primary   16.4 MB  B f ext2       /boot\n"
-      "        #2 primary  551.0 MB      swap       swap\n"
-      "        #3 primary    5.8 GB      ntfs\n"
-      "           pri/log    8.2 MB      FREE SPACE\n"
-      "\n"
-      "  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
-      "        #1 primary   15.9 MB      ext3\n"
-      "        #2 primary  996.0 MB      fat16\n"
-      "        #3 primary    3.9 GB      xfs        /home\n"
-      "        #5 logical    6.0 GB    f ext3       /\n"
-      "        #6 logical    1.0 GB    f ext3       /var\n"
-      "        #7 logical  498.8 MB      ext3\n"
-      "        #8 logical  551.5 MB      swap       swap\n"
-      "        #9 logical   65.8 GB      ext2\n"
-      "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning."
+"The list of partitions might look like this: <informalexample><screen>\n"
+"  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
+"        #1 primary   16.4 MB  B f ext2       /boot\n"
+"        #2 primary  551.0 MB      swap       swap\n"
+"        #3 primary    5.8 GB      ntfs\n"
+"           pri/log    8.2 MB      FREE SPACE\n"
+"\n"
+"  IDE1 slave (hdb) - 80.0 GB ST380021A\n"
+"        #1 primary   15.9 MB      ext3\n"
+"        #2 primary  996.0 MB      fat16\n"
+"        #3 primary    3.9 GB      xfs        /home\n"
+"        #5 logical    6.0 GB    f ext3       /\n"
+"        #6 logical    1.0 GB    f ext3       /var\n"
+"        #7 logical  498.8 MB      ext3\n"
+"        #8 logical  551.5 MB      swap       swap\n"
+"        #9 logical   65.8 GB      ext2\n"
+"</screen></informalexample> This example shows two IDE harddrives divided "
+"into several partitions; the first disk has some free space. Each partition "
+"line consists of the partition number, its type, size, optional flags, file "
+"system, and mountpoint (if any). Note: this particular setup cannot be "
+"created using guided partitioning but it does show possible variation that "
+"can be achieved using manual partitioning."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1349
 #, no-c-format
-msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
+msgid ""
+"This concludes the guided partitioning. If you are satisfied with the "
+"generated partition table, you can choose <guimenuitem>Finish partitioning "
+"and write changes to disk</guimenuitem> from the menu to implement the new "
+"partition table (as described at the end of this section). If you are not "
+"happy, you can choose to <guimenuitem>Undo changes to partitions</"
+"guimenuitem> and run guided partitioning again, or modify the proposed "
+"changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
@@ -1230,49 +1752,101 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1364
 #, no-c-format
-msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
+msgid ""
+"A similar screen to the one shown just above will be displayed if you choose "
+"manual partitioning except that your existing partition table will be shown "
+"and without the mount points. How to manually set up your partition table "
+"and the usage of partitions by your new &debian; system will be covered in "
+"the remainder of this section."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1372
 #, no-c-format
-msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
+msgid ""
+"If you select a pristine disk which has neither partitions nor free space on "
+"it, you will be asked if a new partition table should be created (this is "
+"needed so you can create new partitions). After this, a new line entitled "
+"<quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1380
 #, no-c-format
-msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file system,</phrase> or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap,<phrase arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
+msgid ""
+"If you select some free space, you will have the opportunity to create a new "
+"partition. You will have to answer a quick series of questions about its "
+"size, type (primary or logical), and location (beginning or end of the free "
+"space). After this, you will be presented with a detailed overview of your "
+"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which "
+"determines if the partition will have a file system on it, or be used for "
+"swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file "
+"system,</phrase> or not be used at all. Other settings include mountpoint, "
+"mount options, and bootable flag; which settings are shown depends on how "
+"the partition is to be used. If you don't like the preselected defaults, "
+"feel free to change them to your liking. E.g. by selecting the option "
+"<guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem "
+"for this partition, including options to use the partition for swap,<phrase "
+"arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. "
+"Another nice feature is the ability to copy data from an existing partition "
+"onto this one. When you are satisfied with your new partition, select "
+"<guimenuitem>Done setting up the partition</guimenuitem> and you will return "
+"to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1402
 #, no-c-format
-msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
+msgid ""
+"If you decide you want to change something about your partition, simply "
+"select the partition, which will bring you to the partition configuration "
+"menu. This is the same screen as is used when creating a new partition, so "
+"you can change the same settings. One thing that may not be very obvious at "
+"a first glance is that you can resize the partition by selecting the item "
+"displaying the size of the partition. Filesystems known to work are at least "
+"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1413
 #, no-c-format
-msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
+msgid ""
+"Be sure to create at least two partitions: one for the <emphasis>root</"
+"emphasis> filesystem (which must be mounted as <filename>/</filename>) and "
+"one for <emphasis>swap</emphasis>. If you forget to mount the root "
+"filesystem, <command>partman</command> won't let you continue until you "
+"correct this issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1421
 #, no-c-format
-msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
+msgid ""
+"If you forget to select and format an EFI boot partition, <command>partman</"
+"command> will detect this and will not let you continue until you allocate "
+"one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1427
 #, no-c-format
-msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
+msgid ""
+"Capabilities of <command>partman</command> can be extended with installer "
+"modules, but are dependent on your system's architecture. So if you can't "
+"see all promised goodies, check if you have loaded all required modules (e."
+"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or "
+"<filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1435
 #, no-c-format
-msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
+msgid ""
+"After you are satisfied with partitioning, select <guimenuitem>Finish "
+"partitioning and write changes to disk</guimenuitem> from the partitioning "
+"menu. You will be presented with a summary of changes made to the disks and "
+"asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
@@ -1284,19 +1858,82 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1464
 #, no-c-format
-msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
+msgid ""
+"If you have more than one harddrive<footnote><para> To be honest, you can "
+"construct an MD device even from partitions residing on single physical "
+"drive, but that won't give any benefits. </para></footnote> in your "
+"computer, you can use <command>mdcfg</command> to set up your drives for "
+"increased performance and/or better reliability of your data. The result is "
+"called <firstterm>Multidisk Device</firstterm> (or after its most famous "
+"variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1477
 #, no-c-format
-msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
+msgid ""
+"MD is basically a bunch of partitions located on different disks and "
+"combined together to form a <emphasis>logical</emphasis> device. This device "
+"can then be used like an ordinary partition (i.e. in <command>partman</"
+"command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1485
 #, no-c-format
-msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
+msgid ""
+"What benefits this brings depends on the type of MD device you are creating. "
+"Currently supported are: <variablelist> <varlistentry> <term>RAID0</"
+"term><listitem><para> Is mainly aimed at performance. RAID0 splits all "
+"incoming data into <firstterm>stripes</firstterm> and distributes them "
+"equally over each disk in the array. This can increase the speed of read/"
+"write operations, but when one of the disks fails, you will lose "
+"<emphasis>everything</emphasis> (part of the information is still on the "
+"healthy disk(s), the other part <emphasis>was</emphasis> on the failed "
+"disk). </para><para> The typical use for RAID0 is a partition for video "
+"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</"
+"term><listitem><para> Is suitable for setups where reliability is the first "
+"concern. It consists of several (usually two) equally-sized partitions where "
+"every partition contains exactly the same data. This essentially means three "
+"things. First, if one of your disks fails, you still have the data mirrored "
+"on the remaining disks. Second, you can use only a fraction of the available "
+"capacity (more precisely, it is the size of the smallest partition in the "
+"RAID). Third, file-reads are load-balanced among the disks, which can "
+"improve performance on a server, such as a file server, that tends to be "
+"loaded with more disk reads than writes. </para><para> Optionally you can "
+"have a spare disk in the array which will take the place of the failed disk "
+"in the case of failure. </para></listitem> </varlistentry> <varlistentry> "
+"<term>RAID5</term><listitem><para> Is a good compromise between speed, "
+"reliability and data redundancy. RAID5 splits all incoming data into stripes "
+"and distributes them equally on all but one disk (similar to RAID0). Unlike "
+"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which "
+"gets written on the remaining disk. The parity disk is not static (that "
+"would be called RAID4), but is changing periodically, so the parity "
+"information is distributed equally on all disks. When one of the disks "
+"fails, the missing part of information can be computed from remaining data "
+"and its parity. RAID5 must consist of at least three active partitions. "
+"Optionally you can have a spare disk in the array which will take the place "
+"of the failed disk in the case of failure. </para><para> As you can see, "
+"RAID5 has a similar degree of reliability to RAID1 while achieving less "
+"redundancy. On the other hand, it might be a bit slower on write operations "
+"than RAID0 due to computation of parity information. </para></listitem> </"
+"varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar "
+"to RAID5 except that it uses two parity devices instead of one. </"
+"para><para> A RAID6 array can survive up to two disk failures. </para></"
+"listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> "
+"RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It "
+"creates <replaceable>n</replaceable> copies of incoming data and distributes "
+"them across the partitions so that none of the copies of the same data are "
+"on the same device. The default value of <replaceable>n</replaceable> is 2, "
+"but it can be set to something else in expert mode. The number of partitions "
+"used must be at least <replaceable>n</replaceable>. RAID10 has different "
+"layouts for distributing the copies. The default is near copies. Near copies "
+"have all of the copies at about the same offset on all of the disks. Far "
+"copies have the copies at different offsets on the disks. Offset copies copy "
+"the stripe, not the individual copies. </para><para> RAID10 can be used to "
+"achieve reliability and redundancy without the drawback of having to "
+"calculate parity. </para></listitem> </varlistentry> </variablelist> To sum "
+"it up:"
 msgstr ""
 
 #. Tag: entry
@@ -1392,7 +2029,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1629
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus one)"
 msgstr ""
 
 #. Tag: entry
@@ -1410,7 +2049,9 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1640
 #, no-c-format
-msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
+msgid ""
+"Size of the smallest partition multiplied by (number of devices in RAID "
+"minus two)"
 msgstr ""
 
 #. Tag: entry
@@ -1422,79 +2063,140 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1651
 #, no-c-format
-msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
+msgid ""
+"Total of all partitions divided by the number of chunk copies (defaults to "
+"two)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1658
 #, no-c-format
-msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
+msgid ""
+"If you want to know more about Software RAID, have a look at <ulink url="
+"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1663
 #, no-c-format
-msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
+msgid ""
+"To create an MD device, you need to have the desired partitions it should "
+"consist of marked for use in a RAID. (This is done in <command>partman</"
+"command> in the <guimenu>Partition settings</guimenu> menu where you should "
+"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume "
+"for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1672
 #, no-c-format
-msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
+msgid ""
+"Make sure that the system can be booted with the partitioning scheme you are "
+"planning. In general it will be necessary to create a separate file system "
+"for <filename>/boot</filename> when using RAID for the root (<filename>/</"
+"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including "
+"lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using "
+"for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</"
+"filename> can be an option."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1684
 #, no-c-format
-msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
+msgid ""
+"Support for MD is a relatively new addition to the installer. You may "
+"experience problems for some RAID levels and in combination with some "
+"bootloaders if you try to use MD for the root (<filename>/</filename>) file "
+"system. For experienced users, it may be possible to work around some of "
+"these problems by executing some configuration or installation steps "
+"manually from a shell."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1693
 #, no-c-format
-msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
+msgid ""
+"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> "
+"from the main <command>partman</command> menu. (The menu will only appear "
+"after you mark at least one partition for use as <guimenuitem>physical "
+"volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</"
+"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will "
+"be presented with a list of supported types of MD devices, from which you "
+"should choose one (e.g. RAID1). What follows depends on the type of MD you "
+"selected."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1706
 #, no-c-format
-msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
+msgid ""
+"RAID0 is simple &mdash; you will be issued with the list of available RAID "
+"partitions and your only task is to select the partitions which will form "
+"the MD."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1713
 #, no-c-format
-msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
+msgid ""
+"RAID1 is a bit more tricky. First, you will be asked to enter the number of "
+"active devices and the number of spare devices which will form the MD. Next, "
+"you need to select from the list of available RAID partitions those that "
+"will be active and then those that will be spare. The count of selected "
+"partitions must be equal to the number provided earlier. Don't worry. If you "
+"make a mistake and select a different number of partitions, &d-i; won't let "
+"you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1725
 #, no-c-format
-msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+msgid ""
+"RAID5 has a setup procedure similar to RAID1 with the exception that you "
+"need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1731
 #, no-c-format
-msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
+msgid ""
+"RAID6 also has a setup procedure similar to RAID1 except that at least "
+"<emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1737
 #, no-c-format
-msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
+msgid ""
+"RAID10 again has a setup procedure similar to RAID1 except in expert mode. "
+"In expert mode, &d-i; will ask you for the layout. The layout has two parts. "
+"The first part is the layout type. It is either <literal>n</literal> (for "
+"near copies), <literal>f</literal> (for far copies), or <literal>o</literal> "
+"(for offset copies). The second part is the number of copies to make of the "
+"data. There must be at least that many active devices so that all of the "
+"copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1751
 #, no-c-format
-msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
+msgid ""
+"It is perfectly possible to have several types of MD at once. For example, "
+"if you have three 200 GB hard drives dedicated to MD, each containing two "
+"100 GB partitions, you can combine the first partitions on all three disks "
+"into the RAID0 (fast 300 GB video editing partition) and use the other three "
+"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition "
+"for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1760
 #, no-c-format
-msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
+msgid ""
+"After you set up MD devices to your liking, you can <guimenuitem>Finish</"
+"guimenuitem> <command>mdcfg</command> to return back to the "
+"<command>partman</command> to create filesystems on your new MD devices and "
+"assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
@@ -1506,37 +2208,70 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1776
 #, no-c-format
-msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
+msgid ""
+"If you are working with computers at the level of system administrator or "
+"<quote>advanced</quote> user, you have surely seen the situation where some "
+"disk partition (usually the most important one) was short on space, while "
+"some other partition was grossly underused and you had to manage this "
+"situation by moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1784
 #, no-c-format
-msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
+msgid ""
+"To avoid the described situation you can use Logical Volume Manager (LVM). "
+"Simply said, with LVM you can combine your partitions (<firstterm>physical "
+"volumes</firstterm> in LVM lingo) to form a virtual disk (so called "
+"<firstterm>volume group</firstterm>), which can then be divided into virtual "
+"partitions (<firstterm>logical volumes</firstterm>). The point is that "
+"logical volumes (and of course underlying volume groups) can span across "
+"several physical disks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1794
 #, no-c-format
-msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
+msgid ""
+"Now when you realize you need more space for your old 160GB <filename>/home</"
+"filename> partition, you can simply add a new 300GB disk to the computer, "
+"join it with your existing volume group and then resize the logical volume "
+"which holds your <filename>/home</filename> filesystem and voila &mdash; "
+"your users have some room again on their renewed 460GB partition. This "
+"example is of course a bit oversimplified. If you haven't read it yet, you "
+"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1805
 #, no-c-format
-msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
+msgid ""
+"LVM setup in &d-i; is quite simple and completely supported inside "
+"<command>partman</command>. First, you have to mark the partition(s) to be "
+"used as physical volumes for LVM. This is done in the <guimenu>Partition "
+"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:"
+"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1814
 #, no-c-format
-msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
+msgid ""
+"When you return to the main <command>partman</command> screen, you will see "
+"a new option <guimenuitem>Configure the Logical Volume Manager</"
+"guimenuitem>. When you select that, you will first be asked to confirm "
+"pending changes to the partition table (if any) and after that the LVM "
+"configuration menu will be shown. Above the menu a summary of the LVM "
+"configuration is shown. The menu itself is context sensitive and only shows "
+"valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1825
 #, no-c-format
-msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
+msgid ""
+"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device "
+"structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1578,19 +2313,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1847
 #, no-c-format
-msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
+msgid ""
+"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</"
+"command> screen"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1853
 #, no-c-format
-msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
+msgid ""
+"Use the options in that menu to first create a volume group and then create "
+"your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1858
 #, no-c-format
-msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
+msgid ""
+"After you return to the main <command>partman</command> screen, any created "
+"logical volumes will be displayed in the same way as ordinary partitions "
+"(and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
@@ -1602,37 +2344,76 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1873
 #, no-c-format
-msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
+msgid ""
+"&d-i; allows you to set up encrypted partitions. Every file you write to "
+"such a partition is immediately saved to the device in encrypted form. "
+"Access to the encrypted data is granted only after entering the "
+"<firstterm>passphrase</firstterm> used when the encrypted partition was "
+"originally created. This feature is useful to protect sensitive data in case "
+"your laptop or hard drive gets stolen. The thief might get physical access "
+"to the hard drive, but without knowing the right passphrase, the data on the "
+"hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1885
 #, no-c-format
-msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+msgid ""
+"The two most important partitions to encrypt are: the home partition, where "
+"your private data resides, and the swap partition, where sensitive data "
+"might be stored temporarily during operation. Of course, nothing prevents "
+"you from encrypting any other partitions that might be of interest. For "
+"example <filename>/var</filename> where database servers, mail servers or "
+"print servers store their data, or <filename>/tmp</filename> which is used "
+"by various programs to store potentially interesting temporary files. Some "
+"people may even want to encrypt their whole system. The only exception is "
+"the <filename>/boot</filename> partition which must remain unencrypted, "
+"because currently there is no way to load the kernel from an encrypted "
+"partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1900
 #, no-c-format
-msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
+msgid ""
+"Please note that the performance of encrypted partitions will be less than "
+"that of unencrypted ones because the data needs to be decrypted or encrypted "
+"for every read or write. The performance impact depends on your CPU speed, "
+"chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1907
 #, no-c-format
-msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
+msgid ""
+"To use encryption, you have to create a new partition by selecting some free "
+"space in the main partitioning menu. Another option is to choose an existing "
+"partition (e.g. a regular partition, an LVM logical volume or a RAID "
+"volume). In the <guimenu>Partition settings</guimenu> menu, you need to "
+"select <guimenuitem>physical volume for encryption</guimenuitem> at the "
+"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will "
+"then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1918
 #, no-c-format
-msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+msgid ""
+"&d-i; supports several encryption methods. The default method is "
+"<firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to "
+"host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> "
+"(older, maintained separately from the Linux kernel tree). Unless you have "
+"compelling reasons to do otherwise, it is recommended to use the default."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1930
 #, no-c-format
-msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid ""
+"First, let's have a look at the options available when you select "
+"<userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As "
+"always: when in doubt, use the defaults, because they have been carefully "
+"chosen with security in mind."
 msgstr ""
 
 #. Tag: term
@@ -1644,7 +2425,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1942
 #, no-c-format
-msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
+msgid ""
+"This option lets you select the encryption algorithm (<firstterm>cipher</"
+"firstterm>) which will be used to encrypt the data on the partition. &d-i; "
+"currently supports the following block ciphers: <firstterm>aes</firstterm>, "
+"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and "
+"<firstterm>twofish</firstterm>. It is beyond the scope of this document to "
+"discuss the qualities of these different algorithms, however, it might help "
+"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by "
+"the American National Institute of Standards and Technology as the standard "
+"encryption algorithm for protecting sensitive information in the 21st "
+"century."
 msgstr ""
 
 #. Tag: term
@@ -1656,7 +2447,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1962
 #, no-c-format
-msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
+msgid ""
+"Here you can specify the length of the encryption key. With a larger key "
+"size, the strength of the encryption is generally improved. On the other "
+"hand, increasing the length of the key usually has a negative impact on "
+"performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
@@ -1668,13 +2463,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1976
 #, no-c-format
-msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
+msgid ""
+"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</"
+"firstterm> algorithm is used in cryptography to ensure that applying the "
+"cipher on the same <firstterm>clear text</firstterm> data with the same key "
+"always produces a unique <firstterm>cipher text</firstterm>. The idea is to "
+"prevent the attacker from deducing information from repeated patterns in the "
+"encrypted data."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:1986
 #, no-c-format
-msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
+msgid ""
+"From the provided alternatives, the default <userinput>cbc-essiv:sha256</"
+"userinput> is currently the least vulnerable to known attacks. Use the other "
+"alternatives only when you need to ensure compatibility with some previously "
+"installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
@@ -1698,7 +2503,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2007
 #, no-c-format
-msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
+msgid ""
+"The encryption key will be computed<footnote> <para> Using a passphrase as "
+"the key currently means that the partition will be set up using <ulink url="
+"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase "
+"which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
@@ -1710,13 +2519,26 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2023
 #, no-c-format
-msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
+msgid ""
+"A new encryption key will be generated from random data each time you try to "
+"bring up the encrypted partition. In other words: on every shutdown the "
+"content of the partition will be lost as the key is deleted from memory. (Of "
+"course, you could try to guess the key with a brute force attack, but unless "
+"there is an unknown weakness in the cipher algorithm, it is not achievable "
+"in our lifetime.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2032
 #, no-c-format
-msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
+msgid ""
+"Random keys are useful for swap partitions because you do not need to bother "
+"yourself with remembering the passphrase or wiping sensitive information "
+"from the swap partition before shutting down your computer. However, it also "
+"means that you will <emphasis>not</emphasis> be able to use the "
+"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels "
+"as it will be impossible (during a subsequent boot) to recover the suspended "
+"data written to the swap partition."
 msgstr ""
 
 #. Tag: term
@@ -1728,13 +2550,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2053
 #, no-c-format
-msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
+msgid ""
+"Determines whether the content of this partition should be overwritten with "
+"random data before setting up the encryption. This is recommended because it "
+"might otherwise be possible for an attacker to discern which parts of the "
+"partition are in use and which are not. In addition, this will make it "
+"harder to recover any leftover data from previous "
+"installations<footnote><para> It is believed that the guys from three-letter "
+"agencies can restore the data even after several rewrites of the "
+"magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2073
 #, no-c-format
-msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
+msgid ""
+"If you select <menuchoice> <guimenu>Encryption method:</guimenu> "
+"<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu "
+"changes to provide the following options:"
 msgstr ""
 
 #. Tag: term
@@ -1746,7 +2579,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2084
 #, no-c-format
-msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
+msgid ""
+"For loop-AES, unlike dm-crypt, the options for cipher and key size are "
+"combined, so you can select both at the same time. Please see the above "
+"sections on ciphers and key sizes for further information."
 msgstr ""
 
 #. Tag: term
@@ -1770,7 +2606,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2103
 #, no-c-format
-msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
+msgid ""
+"The encryption key will be generated from random data during the "
+"installation. Moreover this key will be encrypted with <application>GnuPG</"
+"application>, so to use it, you will need to enter the proper passphrase "
+"(you will be asked to provide one later in the process)."
 msgstr ""
 
 #. Tag: para
@@ -1788,50 +2628,93 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2139
 #, no-c-format
-msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
+msgid ""
+"After you have selected the desired parameters for your encrypted "
+"partitions, return back to the main partitioning menu. There should now be a "
+"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After "
+"you select it, you will be asked to confirm the deletion of data on "
+"partitions marked to be erased and possibly other actions such as writing a "
+"new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2149
 #, no-c-format
-msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
+msgid ""
+"Next you will be asked to enter a passphrase for partitions configured to "
+"use one. Good passphrases should be longer than 8 characters, should be a "
+"mixture of letters, numbers and other characters and should not contain "
+"common dictionary words or information easily associable with you (such as "
+"birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2158
 #, no-c-format
-msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
+msgid ""
+"Before you input any passphrases, you should have made sure that your "
+"keyboard is configured correctly and generates the expected characters. If "
+"you are unsure, you can switch to the second virtual console and type some "
+"text at the prompt. This ensures that you won't be surprised later, e.g. by "
+"trying to input a passphrase using a qwerty keyboard layout when you used an "
+"azerty layout during the installation. This situation can have several "
+"causes. Maybe you switched to another keyboard layout during the "
+"installation, or the selected keyboard layout might not have been set up yet "
+"when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2171
 #, no-c-format
-msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
+msgid ""
+"If you selected to use methods other than a passphrase to create encryption "
+"keys, they will be generated now. Because the kernel may not have gathered a "
+"sufficient amount of entropy at this early stage of the installation, the "
+"process may take a long time. You can help speed up the process by "
+"generating entropy: e.g. by pressing random keys, or by switching to the "
+"shell on the second virtual console and generating some network and disk "
+"traffic (downloading some files, feeding big files into <filename>/dev/null</"
+"filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2187
 #, no-c-format
 msgid ""
-      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
-      "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
-      "     #1 115.1 GB  F ext3\n"
-      "\n"
-      "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-      "     #1 515.2 MB  F ext3\n"
-      "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you."
+"After returning to the main partitioning menu, you will see all encrypted "
+"volumes as additional partitions which can be configured in the same way as "
+"ordinary partitions. The following example shows two different volumes. The "
+"first one is encrypted via dm-crypt, the second one via loop-AES. "
+"<informalexample><screen>\n"
+"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux "
+"device-mapper\n"
+"     #1 115.1 GB  F ext3\n"
+"\n"
+"Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
+"     #1 515.2 MB  F ext3\n"
+"</screen></informalexample> Now is the time to assign mount points to the "
+"volumes and optionally change the file system types if the defaults do not "
+"suit you."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2200
 #, no-c-format
-msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+msgid ""
+"Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</"
+"replaceable> and <replaceable>loop0</replaceable> in this case) and the "
+"mount points you assigned to each encrypted volume. You will need this "
+"information later when booting the new system. The differences between the "
+"ordinary boot process and the boot process with encryption involved will be "
+"covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2210
 #, no-c-format
-msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
+msgid ""
+"Once you are satisfied with the partitioning scheme, continue with the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -1843,37 +2726,63 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2222
 #, no-c-format
-msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
+msgid ""
+"Although this stage is the least problematic, it consumes a significant "
+"fraction of the install because it downloads, verifies and unpacks the whole "
+"base system. If you have a slow computer or network connection, this could "
+"take some time."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2235
 #, no-c-format
-msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid ""
+"During installation of the base system, package unpacking and setup messages "
+"are redirected to <userinput>tty4</userinput>. You can access this terminal "
+"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></"
+"keycombo>; get back to the main installer process with "
+"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2244
 #, no-c-format
-msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
+msgid ""
+"The unpack/setup messages generated during this phase are also saved in "
+"<filename>/var/log/syslog</filename>. You can check them there if the "
+"installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2250
 #, no-c-format
-msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
+msgid ""
+"As part of the installation, a &arch-kernel; kernel will be installed. At "
+"the default priority, the installer will choose one for you that best "
+"matches your hardware. In lower priority modes, you will be able to choose "
+"from a list of available kernels."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2257
 #, no-c-format
-msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
+msgid ""
+"When packages are installed using the package management system, it will by "
+"default also install packages that are recommended by those packages. "
+"Recommended packages are not strictly required for the core functionality of "
+"the selected software, but they do enhance that software and should, in the "
+"view of the package maintainers, normally be installed together with that "
+"software."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2267
 #, no-c-format
-msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
+msgid ""
+"For technical reasons packages installed during the installation of the base "
+"system are installed without their <quote>Recommends</quote>. The rule "
+"described above only takes effect after this point in the installation "
+"process."
 msgstr ""
 
 #. Tag: title
@@ -1885,7 +2794,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2280
 #, no-c-format
-msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
+msgid ""
+"At this point you have a usable but limited system. Most users will want to "
+"install additional software on the system to tune it to their needs, and the "
+"installer allows you do so. This step can take even longer than installing "
+"the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
@@ -1897,25 +2810,55 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2297
 #, no-c-format
-msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
+msgid ""
+"One of the tools used to install packages on a &debian-gnu; system is a "
+"program called <command>apt-get</command>, from the <classname>apt</"
+"classname> package<footnote> <para> Note that the program which actually "
+"installs the packages is called <command>dpkg</command>. However, this "
+"program is more of a low-level tool. <command>apt-get</command> is a higher-"
+"level tool, which will invoke <command>dpkg</command> as appropriate. It "
+"knows how to retrieve packages from your CD, the network, or wherever. It is "
+"also able to automatically install other packages which are required to make "
+"the package you're trying to install work correctly. </para> </footnote>. "
+"Other front-ends for package management, like <command>aptitude</command> "
+"and <command>synaptic</command>, are also in use. These front-ends are "
+"recommended for new users, since they integrate some additional features "
+"(package searching and status checks) in a nice user interface. In fact, "
+"<command>aptitude</command> is now the recommended utility for package "
+"management."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2321
 #, no-c-format
-msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
+msgid ""
+"<command>apt</command> must be configured so that it knows from where to "
+"retrieve packages. The results of this configuration are written to the file "
+"<filename>/etc/apt/sources.list</filename>. You can examine and edit this "
+"file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2328
 #, no-c-format
-msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
+msgid ""
+"If you are installing at default priority, the installer will largely take "
+"care of the configuration automatically, based on the installation method "
+"you are using and possibly using choices made earlier in the installation. "
+"In most cases the installer will automatically add a security mirror and, if "
+"you are installing the stable distribution, a mirror for the "
+"<quote>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2337
 #, no-c-format
-msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
+msgid ""
+"If you are installing at a lower priority (e.g. in expert mode), you will be "
+"able to make more decisions yourself. You can choose whether or not to use "
+"the security and/or volatile update services, and you can choose to add "
+"packages from the <quote>contrib</quote> and <quote>non-free</quote> "
+"sections of the archive."
 msgstr ""
 
 #. Tag: title
@@ -1927,37 +2870,64 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2350
 #, no-c-format
-msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
+msgid ""
+"If you are installing from a CD or a DVD that is part of a larger set, the "
+"installer will ask if you want to scan additional CDs or DVDs. If you have "
+"additional CDs or DVDs available, you probably want to do this so the "
+"installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2357
 #, no-c-format
-msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
+msgid ""
+"If you do not have any additional CDs or DVDs, that is no problem: using "
+"them is not required. If you also do not use a network mirror (as explained "
+"in the next section), it can mean that not all packages belonging to the "
+"tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2365
 #, no-c-format
-msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
+msgid ""
+"Packages are included on CDs (and DVDs) in the order of their popularity. "
+"This means that for most uses only the first CDs in a set are needed and "
+"that only very few people actually use any of the packages included on the "
+"last CDs in a set."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2372
 #, no-c-format
-msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
+msgid ""
+"It also means that buying or downloading and burning a full CD set is just a "
+"waste of money as you'll never use most of them. In most cases you are "
+"better off getting only the first 3 to 8 CDs and installing any additional "
+"packages you may need from the Internet by using a mirror. The same goes for "
+"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2381
 #, no-c-format
-msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
+msgid ""
+"A good rule of thumb is that for a regular desktop installation (using the "
+"GNOME desktop environment) only the first three CDs are needed. For the "
+"alternative desktop environments (KDE or Xfce), additional CDs are needed. "
+"The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2389
 #, no-c-format
-msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
+msgid ""
+"If you do scan multiple CDs or DVDs, the installer will prompt you to "
+"exchange them when it needs packages from another CD/DVD than the one "
+"currently in the drive. Note that only CDs or DVDs that belong to the same "
+"set should be scanned. The order in which they are scanned does not really "
+"matter, but scanning them in ascending order will reduce the chance of "
+"mistakes."
 msgstr ""
 
 #. Tag: title
@@ -1969,37 +2939,67 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2404
 #, no-c-format
-msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
+msgid ""
+"One question that will be asked during most installs is whether or not to "
+"use a network mirror as a source for packages. In most cases the default "
+"answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2410
 #, no-c-format
-msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
+msgid ""
+"If you are <emphasis>not</emphasis> installing from a full CD or DVD or "
+"using a full CD/DVD image, you really should use a network mirror as "
+"otherwise you will end up with only a very minimal system. However, if you "
+"have a limited Internet connection it is best <emphasis>not</emphasis> to "
+"select the <literal>desktop</literal> task in the next step of the "
+"installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2419
 #, no-c-format
-msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
+msgid ""
+"If you are installing from a single full CD or using a full CD image, using "
+"a network mirror is not required, but is still strongly recommended because "
+"a single CD contains only a fairly limited number of packages. If you have a "
+"limited Internet connection it may still be best to <emphasis>not</emphasis> "
+"select a network mirror here, but to finish the installation using only "
+"what's available on the CD and selectively install additional packages after "
+"the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2430
 #, no-c-format
-msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
+msgid ""
+"If you are installing from a DVD or using a DVD image, any packages needed "
+"during the installation should be present on the first DVD. The same is true "
+"if you have scanned multiple CDs as explained in the previous section. Use "
+"of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2437
 #, no-c-format
-msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
+msgid ""
+"One advantage of adding a network mirror is that updates that have occurred "
+"since the CD/DVD set was created and have been included in a point release, "
+"will become available for installation, thus extending the life of your CD/"
+"DVD set without compromising the security or stability of the installed "
+"system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2444
 #, no-c-format
-msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
+msgid ""
+"In summary: selecting a network mirror is generally a good idea, except if "
+"you do not have a good Internet connection. If the current version of a "
+"package is available from CD/DVD, the installer will always use that. The "
+"amount of data that will be downloaded if you do select a mirror thus "
+"depends on"
 msgstr ""
 
 #. Tag: para
@@ -2017,19 +3017,27 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2463
 #, no-c-format
-msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
+msgid ""
+"which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2468
 #, no-c-format
-msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
+msgid ""
+"whether any updated versions of packages included on the CDs or DVDs are "
+"available from a mirror (either a regular package mirror, or a mirror for "
+"security or volatile updates)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2477
 #, no-c-format
-msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
+msgid ""
+"Note that the last point means that, even if you choose not to use a network "
+"mirror, some packages may still be downloaded from the Internet if there is "
+"a security or volatile update available for them and those services have "
+"been configured."
 msgstr ""
 
 #. Tag: title
@@ -2041,19 +3049,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2489
 #, no-c-format
-msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine."
+msgid ""
+"If you have selected to use a network mirror during the installation "
+"(optional for CD/DVD installs, required for netboot images), you will be "
+"presented with a list of geographically nearby (and therefore hopefully "
+"fast) network mirrors, based upon your country selection earlier in the "
+"installation process. Choosing the offered default is usually fine."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2497
 #, no-c-format
-msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one."
+msgid ""
+"If your computer is on an IPv6-only network (which is probably not the case "
+"for the vast majority of users), using the default mirror for your country "
+"might not work. All the mirrors in the list are reachable via IPv4, but only "
+"some of them can be used via IPv6. As connectivity of individual mirrors can "
+"change over time, this information is not available in the installer. If "
+"there is no IPv6 connectivity for the default mirror for your country, you "
+"can either try some of the other mirrors offered to you or choose the "
+"<quote>enter information manually</quote> option. You can then specify "
+"<quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for "
+"a mirror available via IPv6, although it will probably not be the fastest "
+"possible one."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2511
 #, no-c-format
-msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
+msgid ""
+"Another option when choosing to specify the mirror manually is to use "
+"<quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</"
+"quote> is not a physical mirror but a mirror redirection service, i.e. it "
+"automatically refers your system to a real mirror near you in terms of "
+"network topology. It takes into account by which protocol you connect to it, "
+"i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
 msgstr ""
 
 #. Tag: title
@@ -2065,85 +3095,165 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2532
 #, no-c-format
-msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
+msgid ""
+"During the installation process, you are given the opportunity to select "
+"additional software to install. Rather than picking individual software "
+"packages from the &num-of-distrib-pkgs; available packages, this stage of "
+"the installation process focuses on selecting and installing predefined "
+"collections of software to quickly set up your computer to perform various "
+"tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2541
 #, no-c-format
-msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
+msgid ""
+"So, you have the ability to choose <emphasis>tasks</emphasis> first, and "
+"then add on more individual packages later. These tasks loosely represent a "
+"number of different jobs or things you want to do with your computer, such "
+"as <quote>Desktop environment</quote>, <quote>Web server</quote>, or "
+"<quote>Print server</quote><footnote> <para> You should know that to present "
+"this list, the installer is merely invoking the <command>tasksel</command> "
+"program. It can be run at any time after installation to install more "
+"packages (or remove them), or you can use a more fine-grained tool such as "
+"<command>aptitude</command>. If you are looking for a specific single "
+"package, after installation is complete, simply run <userinput>aptitude "
+"install <replaceable>package</replaceable></userinput>, where "
+"<replaceable>package</replaceable> is the name of the package you are "
+"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> "
+"lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2568
 #, no-c-format
-msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
+msgid ""
+"Some tasks may be pre-selected based on the characteristics of the computer "
+"you are installing. If you disagree with these selections you can deselect "
+"them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2575
 #, no-c-format
-msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+msgid ""
+"In the standard user interface of the installer, you can use the space bar "
+"to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2581
 #, no-c-format
-msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
+msgid ""
+"Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop "
+"environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2586
 #, no-c-format
-msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using <literal>desktop=xfce</literal> or <literal>desktop=lxde</literal>."
+msgid ""
+"It is not possible to interactively select a different desktop during the "
+"installation. However, it <emphasis>is</emphasis> possible to get &d-i; to "
+"install a KDE desktop environment instead of GNOME by using preseeding (see "
+"<xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter "
+"<literal>desktop=kde</literal> at the boot prompt when starting the "
+"installer. Alternatively the more lightweight Xfce and LXDE desktop "
+"environments can be selected by using <literal>desktop=xfce</literal> or "
+"<literal>desktop=lxde</literal>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2597
 #, no-c-format
-msgid "Some CD images (netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>."
+msgid ""
+"Some CD images (netinst and DVD) also allow selection of the desired desktop "
+"environment from the graphical boot menu. Select the <quote>Advanced "
+"options</quote> option in the main menu and look for <quote>Alternative "
+"desktop environments</quote>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2604
 #, no-c-format
-msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method."
+msgid ""
+"Note that this will only work if the packages needed for the desired desktop "
+"environment are actually available. If you are installing using a single "
+"full CD image, they will need to be downloaded from a mirror as most needed "
+"packages are only included on later CDs; installing KDE, Xfce or LXDE this "
+"way should work fine if you are using a DVD image or any other installation "
+"method."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2614
 #, no-c-format
-msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
+msgid ""
+"The various server tasks will install software roughly as follows. DNS "
+"server: <classname>bind9</classname>; File server: <classname>samba</"
+"classname>, <classname>nfs</classname>; Mail server: <classname>exim4</"
+"classname>, <classname>spamassassin</classname>, <classname>uw-imap</"
+"classname>; Print server: <classname>cups</classname>; SQL database: "
+"<classname>postgresql</classname>; Web server: <classname>apache2</"
+"classname>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2625
 #, no-c-format
-msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system."
+msgid ""
+"The <quote>Standard system</quote> task will install any package that has a "
+"priority <quote>standard</quote>. This includes a lot of common utilities "
+"that are normally available on any Linux or Unix system. You should leave "
+"this task selected unless you know what you are doing and want a really "
+"minimal system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2633
 #, no-c-format
-msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)."
+msgid ""
+"If during language selection a default locale other than the <quote>C</"
+"quote> locale was selected, <command>tasksel</command> will check if any "
+"localization tasks are defined for that locale and will automatically try to "
+"install relevant localization packages. This includes for example packages "
+"containing word lists or special fonts for your language. If a desktop "
+"environment was selected, it will also install appropriate localization "
+"packages for that (if available)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2643
 #, no-c-format
-msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
+msgid ""
+"Once you've selected your tasks, select &BTN-CONT;. At this point, "
+"<command>aptitude</command> will install the packages that are part of the "
+"selected tasks. If a particular program needs more information from the "
+"user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2650
 #, no-c-format
-msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
+msgid ""
+"You should be aware that especially the Desktop task is very large. "
+"Especially when installing from a normal CD-ROM in combination with a mirror "
+"for packages not on the CD-ROM, the installer may want to retrieve a lot of "
+"packages over the network. If you have a relatively slow Internet "
+"connection, this can take a long time. There is no option to cancel the "
+"installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2659
 #, no-c-format
-msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
+msgid ""
+"Even when packages are included on the CD-ROM, the installer may still "
+"retrieve them from the mirror if the version available on the mirror is more "
+"recent than the one included on the CD-ROM. If you are installing the stable "
+"distribution, this can happen after a point release (an update of the "
+"original stable release); if you are installing the testing distribution "
+"this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: title
@@ -2155,7 +3265,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2676
 #, no-c-format
-msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
+msgid ""
+"If you are installing a diskless workstation, obviously, booting off the "
+"local disk isn't a meaningful option, and this step will be skipped. <phrase "
+"arch=\"sparc\">You may wish to set OpenBoot to boot from the network by "
+"default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
@@ -2167,13 +3281,23 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2693
 #, no-c-format
-msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;."
+msgid ""
+"Before a boot loader is installed, the installer will attempt to probe for "
+"other operating systems which are installed on the machine. If it finds a "
+"supported operating system, you will be informed of this during the boot "
+"loader installation step, and the computer will be configured to boot this "
+"other operating system in addition to &debian;."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2701
 #, no-c-format
-msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
+msgid ""
+"Note that multiple operating systems booting on a single machine is still "
+"something of a black art. The automatic support for detecting and setting up "
+"boot loaders to boot other operating systems varies by architecture and even "
+"by subarchitecture. If it does not work you should consult your boot "
+"manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
@@ -2185,7 +3309,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2720
 #, no-c-format
-msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
+msgid ""
+"The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is "
+"similar in configuration and usage to <command>LILO</command>, with a few "
+"exceptions. First of all, <command>PALO</command> allows you to boot any "
+"kernel image on your boot partition. This is because <command>PALO</command> "
+"can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
@@ -2203,19 +3332,28 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2743
 #, no-c-format
-msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
+msgid ""
+"The main &architecture; boot loader is called <quote>grub</quote>. Grub is a "
+"flexible and robust boot loader and a good default choice for new users and "
+"old hands alike."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2749
 #, no-c-format
-msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
+msgid ""
+"By default, grub will be installed into the Master Boot Record (MBR), where "
+"it will take over complete control of the boot process. If you prefer, you "
+"can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2755
 #, no-c-format
-msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
+msgid ""
+"If you do not want to install grub, use the &BTN-GOBACK; button to get to "
+"the main menu, and from there select whatever bootloader you would like to "
+"use."
 msgstr ""
 
 #. Tag: title
@@ -2227,19 +3365,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2770
 #, no-c-format
-msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
+msgid ""
+"The second &architecture; boot loader is called <quote>LILO</quote>. It is "
+"an old complex program which offers lots of functionality, including DOS, "
+"Windows, and OS/2 boot management. Please carefully read the instructions in "
+"the directory <filename>/usr/share/doc/lilo/</filename> if you have special "
+"needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2780
 #, no-c-format
-msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
+msgid ""
+"Currently the LILO installation will only create menu entries for other "
+"operating systems if these can be <firstterm>chainloaded</firstterm>. This "
+"means you may have to manually add a menu entry for operating systems like "
+"GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2788
 #, no-c-format
-msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
+msgid ""
+"&d-i; offers you three choices on where to install the <command>LILO</"
+"command> boot loader:"
 msgstr ""
 
 #. Tag: term
@@ -2251,7 +3400,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2795
 #, no-c-format
-msgid "This way the <command>LILO</command> will take complete control of the boot process."
+msgid ""
+"This way the <command>LILO</command> will take complete control of the boot "
+"process."
 msgstr ""
 
 #. Tag: term
@@ -2263,7 +3414,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2802
 #, no-c-format
-msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader."
+msgid ""
+"Choose this if you want to use another boot manager. <command>LILO</command> "
+"will install itself at the beginning of the new &debian; partition and it "
+"will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
@@ -2275,13 +3429,22 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2811
 #, no-c-format
-msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+msgid ""
+"Useful for advanced users who want to install <command>LILO</command> "
+"somewhere else. In this case you will be asked for desired location. You can "
+"use traditional device names such as <filename>/dev/hda</filename> or "
+"<filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2821
 #, no-c-format
-msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into &debian;!"
+msgid ""
+"If you can no longer boot into Windows 9x (or DOS) after this step, you'll "
+"need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /"
+"mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; "
+"however, this means that you'll need to use some other way to get back into "
+"&debian;!"
 msgstr ""
 
 #. Tag: title
@@ -2293,13 +3456,30 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2839
 #, no-c-format
-msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
+msgid ""
+"The &architecture; boot loader is called <quote>elilo</quote>. It is modeled "
+"on the <quote>lilo</quote> boot loader for the x86 architecture and uses a "
+"similar configuration file. However, instead of writing an MBR or partition "
+"boot record to the disk, it copies the necessary files to a separate FAT "
+"formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</"
+"guimenuitem> menu in the firmware to point to the files in the EFI "
+"partition. The <command>elilo</command> boot loader is really in two parts. "
+"The <filename>/usr/sbin/elilo</filename> command manages the partition and "
+"copies files into it. The <filename>elilo.efi</filename> program is copied "
+"into the EFI partition and then run by the <quote>EFI Boot Manager</quote> "
+"to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2855
 #, no-c-format
-msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
+msgid ""
+"The <quote>elilo</quote> configuration and installation is done as the last "
+"step of installing the packages of the base installation. &d-i; will present "
+"you with a list of potential disk partitions that it has found suitable for "
+"an EFI partition. Select the partition you set up earlier in the "
+"installation, typically a partition on the same disk that contains your "
+"<emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2311,7 +3491,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2869
 #, no-c-format
-msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
+msgid ""
+"The criterion for selecting a partition is that it must be a FAT format "
+"filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show "
+"multiple choices depending on what it finds from scanning all of the disks "
+"of the system including EFI partitions of other system disks and EFI "
+"diagnostic partitions. Remember, <command>elilo</command> may format the "
+"partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
@@ -2323,7 +3509,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2886
 #, no-c-format
-msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
+msgid ""
+"The EFI partition is a FAT filesystem format partition on one of the hard "
+"disks of the system, usually the same disk that contains the <emphasis>root</"
+"emphasis> filesystem. It is normally not mounted on a running system as it "
+"is only needed by the <quote>EFI Boot Manager</quote> to load the system and "
+"the installer part of the <command>elilo</command> writes to the filesystem "
+"directly. The <command>/usr/sbin/elilo</command> utility writes the "
+"following files into the <filename>efi/debian</filename> directory of the "
+"EFI partition during the installation. Note that the <quote>EFI Boot "
+"Manager</quote> would find these files using the path "
+"<filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may "
+"be other files in this filesystem as well over time as the system is updated "
+"or re-configured."
 msgstr ""
 
 #. Tag: filename
@@ -2335,7 +3533,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2909
 #, no-c-format
-msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
+msgid ""
+"This is the configuration file read by the boot loader when it starts. It is "
+"a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-"
+"written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
@@ -2347,7 +3548,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2919
 #, no-c-format
-msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
+msgid ""
+"This is the boot loader program that the <quote>EFI Boot Manager</quote> "
+"runs to boot the system. It is the program behind the <guimenuitem>&debian; "
+"GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> "
+"command menu."
 msgstr ""
 
 #. Tag: filename
@@ -2359,7 +3564,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2930
 #, no-c-format
-msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
+msgid ""
+"This is the initial root filesystem used to boot the kernel. It is a copy of "
+"the file referenced in the <filename>/etc/elilo.conf</filename>. In a "
+"standard &debian; installation it would be the file in <filename>/boot</"
+"filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
@@ -2371,7 +3580,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2943
 #, no-c-format
-msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
+msgid ""
+"This is a small text file warning you that the contents of the directory are "
+"managed by the <command>elilo</command> and that any local changes would be "
+"lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
@@ -2383,7 +3595,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2954
 #, no-c-format
-msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
+msgid ""
+"This is the compressed kernel itself. It is a copy of the file referenced in "
+"the <filename>/etc/elilo.conf</filename>. In a standard &debian; "
+"installation it would be the file in <filename>/boot</filename> pointed to "
+"by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
@@ -2396,13 +3612,25 @@ msgstr ""
 #: using-d-i.xml:2975
 #, no-c-format
 msgid ""
-      "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
-      "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
-      "<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n"
-      "<userinput> setenv OSLoader arcboot</userinput>\n"
-      "<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n"
-      "<userinput> setenv AutoLoad yes</userinput>\n"
-      "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
+"The boot loader on SGI machines is <command>arcboot</command>. It has to be "
+"installed on the same hard disk as the kernel (this is done automatically by "
+"the installer). Arcboot supports different configurations which are set up "
+"in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique "
+"name, the default setup as created by the installer is <quote>linux</quote>. "
+"After arcboot has been installed, the system can be booted from hard disk by "
+"setting some firmware environment variables entering "
+"<informalexample><screen>\n"
+"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
+"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk"
+"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</"
+"replaceable>)</userinput>\n"
+"<userinput> setenv OSLoader arcboot</userinput>\n"
+"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></"
+"userinput>\n"
+"<userinput> setenv AutoLoad yes</userinput>\n"
+"</screen></informalexample> on the firmware prompt, and then typing "
+"<command>boot</command>."
 msgstr ""
 
 #. Tag: replaceable
@@ -2414,7 +3642,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2995
 #, no-c-format
-msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
+msgid ""
+"is the SCSI bus to be booted from, this is <userinput>0</userinput> for the "
+"onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
@@ -2426,7 +3656,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3004
 #, no-c-format
-msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
+msgid ""
+"is the SCSI ID of the hard disk on which <command>arcboot</command> is "
+"installed"
 msgstr ""
 
 #. Tag: replaceable
@@ -2438,7 +3670,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3013
 #, no-c-format
-msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
+msgid ""
+"is the number of the partition on which <filename>/etc/arcboot.conf</"
+"filename> resides"
 msgstr ""
 
 #. Tag: replaceable
@@ -2450,7 +3684,9 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3022
 #, no-c-format
-msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
+msgid ""
+"is the name of the configuration entry in <filename>/etc/arcboot.conf</"
+"filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
@@ -2462,7 +3698,14 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3044
 #, no-c-format
-msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;."
+msgid ""
+"Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their "
+"boot loader. The installer will set up <command>yaboot</command> "
+"automatically, so all you need is a small 820k partition named "
+"<quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> "
+"created back in the partitioning component. If this step completes "
+"successfully then your disk should now be bootable and OpenFirmware will be "
+"set to boot &debian-gnu;."
 msgstr ""
 
 #. Tag: title
@@ -2474,7 +3717,11 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3063
 #, no-c-format
-msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
+msgid ""
+"The boot loader for OldWorld Power Macintosh machines is <command>quik</"
+"command>. You can also use it on CHRP. The installer will attempt to set up "
+"<command>quik</command> automatically. The setup has been known to work on "
+"7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
@@ -2486,7 +3733,12 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3080
 #, no-c-format
-msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
+msgid ""
+"The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. Please take a look at <quote>LINUX for &arch-title; "
+"Device Drivers and Installation Commands</quote> from IBM's developerWorks "
+"web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
@@ -2498,7 +3750,19 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3099
 #, no-c-format
-msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
+msgid ""
+"The standard &architecture; boot loader is called <quote>silo</quote>. It is "
+"documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</"
+"command> is similar in configuration and usage to <command>LILO</command>, "
+"with a few exceptions. First of all, <command>SILO</command> allows you to "
+"boot any kernel image on your drive, even if it is not listed in <filename>/"
+"etc/silo.conf</filename>. This is because <command>SILO</command> can "
+"actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is "
+"read at boot time, so there is no need to rerun <command>silo</command> "
+"after installing a new kernel like you would with <command>LILO</command>. "
+"<command>SILO</command> can also read UFS partitions, which means it can "
+"boot SunOS/Solaris partitions as well. This is useful if you want to install "
+"GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
@@ -2510,13 +3774,24 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3126
 #, no-c-format
-msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)."
+msgid ""
+"This option can be used to complete the installation even when no boot "
+"loader is to be installed, either because the arch/subarch doesn't provide "
+"one, or because none is desired (e.g. you will use existing boot loader)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3133
 #, no-c-format
-msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
+msgid ""
+"If you plan to manually configure your bootloader, you should check the name "
+"of the installed kernel in <filename>/target/boot</filename>. You should "
+"also check that directory for the presence of an <firstterm>initrd</"
+"firstterm>; if one is present, you will probably have to instruct your "
+"bootloader to use it. Other information you will need are the disk and "
+"partition you selected for your <filename>/</filename> filesystem and, if "
+"you chose to install <filename>/boot</filename> on a separate partition, "
+"also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
@@ -2528,7 +3803,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3151
 #, no-c-format
-msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
+msgid ""
+"This is the last step in the &debian; installation process during which the "
+"installer will do any last minute tasks. It mostly consists of tidying up "
+"after the &d-i;."
 msgstr ""
 
 #. Tag: title
@@ -2540,19 +3818,32 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3166
 #, no-c-format
-msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
+msgid ""
+"The installer may ask you if the computer's clock is set to UTC. Normally "
+"this question is avoided if possible and the installer tries to work out "
+"whether the clock is set to UTC based on things like what other operating "
+"systems are installed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3173
 #, no-c-format
-msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
+msgid ""
+"In expert mode you will always be able to choose whether or not the clock is "
+"set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally "
+"set to local time. If you want to dual-boot, select local time instead of "
+"UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or "
+"Windows are normally set to local time. If you want to dual-boot, select "
+"local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3184
 #, no-c-format
-msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
+msgid ""
+"At this point &d-i; will also attempt to save the current time to the "
+"system's hardware clock. This will be done either in UTC or local time, "
+"depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
@@ -2564,13 +3855,20 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3201
 #, no-c-format
-msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system."
+msgid ""
+"You will be prompted to remove the boot media (CD, floppy, etc) that you "
+"used to boot the installer. After that the system will be rebooted into your "
+"new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3207
 #, no-c-format
-msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation."
+msgid ""
+"After a final prompt the system will be halted because rebooting is not "
+"supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD "
+"which you selected for the root filesystem during the first steps of the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2582,7 +3880,10 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3221
 #, no-c-format
-msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
+msgid ""
+"The components listed in this section are usually not involved in the "
+"installation process, but are waiting in the background to help the user in "
+"case something goes wrong."
 msgstr ""
 
 #. Tag: title
@@ -2594,13 +3895,21 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3236
 #, no-c-format
-msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system."
+msgid ""
+"If the installation is successful, the logfiles created during the "
+"installation process will be automatically saved to <filename>/var/log/"
+"installer/</filename> on your new &debian; system."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3243
 #, no-c-format
-msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
+msgid ""
+"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu "
+"allows you to save the log files to a floppy disk, network, hard disk, or "
+"other media. This can be useful if you encounter fatal problems during the "
+"installation and wish to study the logs on another system or attach them to "
+"an installation report."
 msgstr ""
 
 #. Tag: title
@@ -2612,7 +3921,17 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3265
 #, no-c-format
-msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
+msgid ""
+"There are several methods you can use to get a shell while running an "
+"installation. On most systems, and if you are not installing over serial "
+"console, the easiest method is to switch to the second <emphasis>virtual "
+"console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> "
+"<keycap>F2</keycap></keycombo><footnote> <para> That is: press the "
+"<keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</"
+"keycap> and the <keycap>F2</keycap> function key at the same time. </para> </"
+"footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</"
+"keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</"
+"keycap></keycombo> to switch back to the installer itself."
 msgstr ""
 
 #. Tag: para
@@ -2624,31 +3943,52 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3287
 #, no-c-format
-msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
+msgid ""
+"If you cannot switch consoles, there is also an <guimenuitem>Execute a "
+"Shell</guimenuitem> item on the main menu that can be used to start a shell. "
+"You can get to the main menu from most dialogs by using the &BTN-GOBACK; "
+"button one or more times. Type <userinput>exit</userinput> to close the "
+"shell and return to the installer."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3295
 #, no-c-format
-msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
+msgid ""
+"At this point you are booted from the RAM disk, and there is a limited set "
+"of Unix utilities available for your use. You can see what programs are "
+"available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</"
+"command> and by typing <command>help</command>. The shell is a Bourne shell "
+"clone called <command>ash</command> and has some nice features like "
+"autocompletion and history."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3304
 #, no-c-format
-msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
+msgid ""
+"To edit and view files, use the text editor <command>nano</command>. Log "
+"files for the installation system can be found in the <filename>/var/log</"
+"filename> directory."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3311
 #, no-c-format
-msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
+msgid ""
+"Although you can do basically anything in a shell that the available "
+"commands allow you to do, the option to use a shell is really only there in "
+"case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3317
 #, no-c-format
-msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
+msgid ""
+"Doing things manually from the shell may interfere with the installation "
+"process and result in errors or an incomplete installation. In particular, "
+"you should always use let the installer activate your swap partition and not "
+"do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
@@ -2660,70 +4000,146 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3335
 #, no-c-format
-msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
+msgid ""
+"One of the more interesting components is <firstterm>network-console</"
+"firstterm>. It allows you to do a large part of the installation over the "
+"network via SSH. The use of the network implies you will have to perform the "
+"first steps of the installation from the console, at least to the point of "
+"setting up the networking. (Although you can automate that part with <xref "
+"linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3345
 #, no-c-format
-msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
+msgid ""
+"This component is not loaded into the main installation menu by default, so "
+"you have to explicitly ask for it. If you are installing from CD, you need "
+"to boot with medium priority or otherwise invoke the main installation menu "
+"and choose <guimenuitem>Load installer components from CD</guimenuitem> and "
+"from the list of additional components select <guimenuitem>network-console: "
+"Continue installation remotely using SSH</guimenuitem>. Successful load is "
+"indicated by a new menu entry called <guimenuitem>Continue installation "
+"remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3358
 #, no-c-format
-msgid "For installations on &arch-title;, this is the default method after setting up the network."
+msgid ""
+"For installations on &arch-title;, this is the default method after setting "
+"up the network."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3363
 #, no-c-format
-msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely."
+msgid ""
+"<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> "
+"<phrase arch=\"s390\">You</phrase> will be asked for a new password to be "
+"used for connecting to the installation system and for its confirmation. "
+"That's all. Now you should see a screen which instructs you to login "
+"remotely as the user <emphasis>installer</emphasis> with the password you "
+"just provided. Another important detail to notice on this screen is the "
+"fingerprint of this system. You need to transfer the fingerprint securely to "
+"the person who will continue the installation remotely."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3375
 #, no-c-format
-msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
+msgid ""
+"Should you decide to continue with the installation locally, you can always "
+"press &enterkey;, which will bring you back to the main menu, where you can "
+"select another component."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3381
 #, no-c-format
 msgid ""
-      "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
-      "<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n"
-      "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct."
+"Now let's switch to the other side of the wire. As a prerequisite, you need "
+"to configure your terminal for UTF-8 encoding, because that is what the "
+"installation system uses. If you do not, remote installation will be still "
+"possible, but you may encounter strange display artefacts like destroyed "
+"dialog borders or unreadable non-ascii characters. Establishing a connection "
+"with the installation system is as simple as typing: "
+"<informalexample><screen>\n"
+"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</"
+"replaceable></userinput>\n"
+"</screen></informalexample> Where <replaceable>install_host</replaceable> is "
+"either the name or IP address of the computer being installed. Before the "
+"actual login the fingerprint of the remote system will be displayed and you "
+"will have to confirm that it is correct."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3398
 #, no-c-format
-msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
+msgid ""
+"The <command>ssh</command> server in the installer uses a default "
+"configuration that does not send keep-alive packets. In principle, a "
+"connection to the system being installed should be kept open indefinitely. "
+"However, in some situations &mdash; depending on your local network setup "
+"&mdash; the connection may be lost after some period of inactivity. One "
+"common case where this can happen is when there is some form of Network "
+"Address Translation (NAT) somewhere between the client and the system being "
+"installed. Depending on at which point of the installation the connection "
+"was lost, you may or may not be able to resume the installation after "
+"reconnecting."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3411
 #, no-c-format
-msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
+msgid ""
+"You may be able to avoid the connection being dropped by adding the option "
+"<userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></"
+"userinput> when starting the <command>ssh</command> connection, or by adding "
+"that option in your <command>ssh</command> configuration file. Note however "
+"that in some cases adding this option may also <emphasis>cause</emphasis> a "
+"connection to be dropped (for example if keep-alive packets are sent during "
+"a brief network outage, from which <command>ssh</command> would otherwise "
+"have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3424
 #, no-c-format
-msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
+msgid ""
+"If you install several computers in turn and they happen to have the same IP "
+"address or hostname, <command>ssh</command> will refuse to connect to such "
+"host. The reason is that it will have different fingerprint, which is "
+"usually a sign of a spoofing attack. If you are sure this is not the case, "
+"you will need to delete the relevant line from <filename>~/.ssh/known_hosts</"
+"filename><footnote> <para> The following command will remove an existing "
+"entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</"
+"replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </"
+"para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3440
 #, no-c-format
-msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
+msgid ""
+"After the login you will be presented with an initial screen where you have "
+"two possibilities called <guimenuitem>Start menu</guimenuitem> and "
+"<guimenuitem>Start shell</guimenuitem>. The former brings you to the main "
+"installer menu, where you can continue with the installation as usual. The "
+"latter starts a shell from which you can examine and possibly fix the remote "
+"system. You should only start one SSH session for the installation menu, but "
+"may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3450
 #, no-c-format
-msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
+msgid ""
+"After you have started the installation remotely over SSH, you should not go "
+"back to the installation session running on the local console. Doing so may "
+"corrupt the database that holds the configuration of the new system. This in "
+"turn may result in a failed installation or problems with the installed "
+"system."
 msgstr ""
 
 #. Tag: title
@@ -2735,25 +4151,44 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3470
 #, no-c-format
-msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
+msgid ""
+"As described in <xref linkend=\"hardware-firmware\"/>, some devices require "
+"firmware to be loaded. In most cases the device will not work at all if the "
+"firmware is not available; sometimes basic functionality is not impaired if "
+"it is missing and the firmware is only needed to enable additional features."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3478
 #, no-c-format
-msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
+msgid ""
+"If a device driver requests firmware that is not available, &d-i; will "
+"display a dialog offering to load the missing firmware. If this option is "
+"selected, &d-i; will scan available devices for either loose firmware files "
+"or packages containing firmware. If found, the firmware will be copied to "
+"the correct location (<filename>/lib/firmware</filename>) and the driver "
+"module will be reloaded."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3488
 #, no-c-format
-msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
+msgid ""
+"Which devices are scanned and which file systems are supported depends on "
+"the architecture, the installation method and the stage of the installation. "
+"Especially during the early stages of the installation, loading the firmware "
+"is most likely to succeed from a FAT-formatted floppy disk or USB stick. "
+"<phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an "
+"MMC or SD card.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3498
 #, no-c-format
-msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
+msgid ""
+"Note that it is possible to skip loading the firmware if you know the device "
+"will also function without it, or if the device is not needed during the "
+"installation."
 msgstr ""
 
 #. Tag: title
@@ -2765,25 +4200,47 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3507
 #, no-c-format
-msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
+msgid ""
+"Official CD images do not include non-free firmware. The most common method "
+"to load such firmware is from some removable medium such as a USB stick. "
+"Alternatively, unofficial CD builds containing non-free firmware can be "
+"found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick "
+"(or other medium like a hard drive partition, or floppy disk), the firmware "
+"files or packages must be placed in either the root directory or a directory "
+"named <filename>/firmware</filename> of the file system on the medium. The "
+"recommended file system to use is FAT as that is most certain to be "
+"supported during the early stages of the installation."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3520
 #, no-c-format
-msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
+msgid ""
+"Tarballs and zip files containing current packages for the most common "
+"firmware are available from: <itemizedlist> <listitem><para> <ulink url="
+"\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just "
+"download the tarball or zip file for the correct release and unpack it to "
+"the file system on the medium."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3534
 #, no-c-format
-msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
+msgid ""
+"If the firmware you need is not included in the tarball, you can also "
+"download specific firmware packages from the (non-free section of the) "
+"archive. The following overview should list most available firmware packages "
+"but is not guaranteed to be complete and may also contain non-firmware "
+"packages:"
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3548
 #, no-c-format
-msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
+msgid ""
+"It is also possible to copy individual firmware files to the medium. Loose "
+"firmware could be obtained for example from an already installed system or "
+"from a hardware vendor."
 msgstr ""
 
 #. Tag: title
@@ -2795,24 +4252,41 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:3558
 #, no-c-format
-msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
+msgid ""
+"Any firmware loaded during the installation will be copied automatically to "
+"the installed system. In most cases this will ensure that the device that "
+"requires the firmware will also work correctly after the system is rebooted "
+"into the installed system. However, if the installed system runs a different "
+"kernel version from the installer there is a slight chance that the firmware "
+"cannot be loaded due to version skew."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3567
 #, no-c-format
-msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
+msgid ""
+"If the firmware was loaded from a firmware package, &d-i; will also install "
+"this package for the installed system and will automatically add the non-"
+"free section of the package archive in APT's <filename>sources.list</"
+"filename>. This has the advantage that the firmware should be updated "
+"automatically if a new version becomes available."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3575
 #, no-c-format
-msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
+msgid ""
+"If loading the firmware was skipped during the installation, the relevant "
+"device will probably not work with the installed system until the firmware "
+"(package) is installed manually."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:3582
 #, no-c-format
-msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
+msgid ""
+"If the firmware was loaded from loose firmware files, the firmware copied to "
+"the installed system will <emphasis>not</emphasis> be automatically updated "
+"unless the corresponding firmware package (if available) is installed after "
+"the installation is completed."
 msgstr ""
-
diff --git a/po/vi/boot-installer.po b/po/vi/boot-installer.po
index 0ed2bff2f..e13b1e8a6 100644
--- a/po/vi/boot-installer.po
+++ b/po/vi/boot-installer.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: boot-installer\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-08-05 14:24+0700\n"
 "Last-Translator: hailang <hailangvn@gmail.com>\n"
 "Language-Team: MOST Project <du-an-most@lists.hanoilug.org>\n"
@@ -64,8 +64,8 @@ msgid "Booting from TFTP"
 msgstr "Khởi động từ TFTP"
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -75,8 +75,8 @@ msgstr ""
 "động mạng kiểu TFTP (DHCP, RARP, hay BOOTP)."
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -86,8 +86,8 @@ msgstr ""
 "thay cho BOOTP."
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -103,8 +103,8 @@ msgid "Booting from CD-ROM"
 msgstr "Khởi động từ đĩa CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -121,8 +121,8 @@ msgstr ""
 "lại, và đi đến chương kế tiếp."
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -138,8 +138,8 @@ msgstr ""
 "thể là thích hợp hơn."
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -155,8 +155,8 @@ msgstr ""
 "bổ sung nào, hãy chỉ hệ thống cài đặt tới ổ đĩa CD-ROM."
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -402,8 +402,8 @@ msgid "The installer will now start as usual."
 msgstr "Vậy trình cài đặt khởi chạy như bình thường."
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "Khởi động từ đĩa CD-ROM"
@@ -422,17 +422,23 @@ msgstr "Để bắt đầu trình cài đặt từ Windows, bạn có thể"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "lấy đĩa CD/DVD hoặc thanh USB chứa phần mềm cài đặt như được diễn tả trong "
 "<xref linkend=\"official-cdrom\"/> và <xref linkend=\"boot-usb-files\"/>, "
 "hoặc"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -442,7 +448,7 @@ msgstr ""
 "loader.exe trên các gương &debian;,"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -458,7 +464,7 @@ msgstr ""
 "<command>setup.exe</command>."
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -469,13 +475,13 @@ msgstr ""
 "thống để khởi động lại vào tiến trình cài đặt &debian-gnu;."
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "Khởi động từ DOS"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -485,7 +491,7 @@ msgstr ""
 "một đĩa phục hồi hay địa chẩn đoán."
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -503,7 +509,7 @@ msgstr ""
 "hiện thời nếu cần thiết."
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -524,7 +530,7 @@ msgstr ""
 "command>. Việc này nạp hạt nhân và khởi chạy hệ thống cài đặt."
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
@@ -532,7 +538,7 @@ msgstr ""
 "Khởi động từ Linux bằng <command>LILO</command> hay <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -543,7 +549,7 @@ msgstr ""
 "files\"/>."
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -561,7 +567,7 @@ msgstr ""
 "cách cẩn thận."
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -579,7 +585,7 @@ msgstr ""
 "DVD mà không cần chạy mạng."
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -599,7 +605,7 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -611,7 +617,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -627,7 +633,7 @@ msgstr ""
 "<userinput>lilo</userinput> rồi khởi động lại."
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -645,7 +651,7 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -659,7 +665,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -671,7 +677,7 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -691,7 +697,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -701,13 +707,13 @@ msgstr ""
 "<command>GRUB</command> và <command>LILO</command>."
 
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "Khởi động từ thanh bộ nhớ USB"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -731,13 +737,13 @@ msgstr ""
 "nhập các đối số khởi động tùy chọn, hoặc chỉ bấm phím &enterkey;."
 
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "Khởi động từ đĩa mềm"
 
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -747,7 +753,7 @@ msgstr ""
 "cần thiết và tạo đĩa mềm từ ảnh đó."
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -757,7 +763,7 @@ msgstr ""
 "chính, tắt hệ thống một cách bình thường, rồi mở nó lần nữa."
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -776,7 +782,7 @@ msgstr ""
 "dấu nhắc khởi động."
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -793,7 +799,7 @@ msgstr ""
 "động máy."
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -803,7 +809,7 @@ msgstr ""
 "mềm khởi động mà kết thúc bằng dấu nhắc khởi động <prompt>boot:</prompt>."
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -821,7 +827,7 @@ msgstr ""
 "dưới trong <xref linkend=\"kernel-msgs\"/>."
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -835,26 +841,26 @@ msgstr ""
 "tự động."
 
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "Khởi động bằng TFTP"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "Có vài cách khác nhau để khởi động qua TFTP trên i386."
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "NIC hay bo mạch chủ có hỗ trợ PXE"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -868,13 +874,13 @@ msgstr ""
 "chức năng này, có lẽ bạn có khả năng cấu hình BIOS để khởi động qua mạng."
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "NIC với BootROM mạng"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -883,7 +889,7 @@ msgstr ""
 "Có lẽ thẻ giao diện mạng (NIC) của bạn cung cấp chức năng khởi động qua TFTP."
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -894,13 +900,13 @@ msgstr ""
 
 # Name: don't translate / Tên: đừng dịch
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -910,14 +916,14 @@ msgstr ""
 "mềm khởi động, ngay cả bộ nhớ ROM khởi động, mà khởi động được qua TFTP."
 
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "Màn hình khởi động"
 
 # Don't translate the screen example text / Đừng dịch đoạn mẫu màn hình
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -950,7 +956,7 @@ msgstr ""
 "chọn « Cài đặt đồ họa » có thể không sẵn sàng."
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -966,7 +972,7 @@ msgstr ""
 "khởi động trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -978,7 +984,7 @@ msgstr ""
 "cứu và để tự động cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -997,7 +1003,7 @@ msgstr ""
 "bạn đã làm."
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -1049,7 +1055,7 @@ msgstr ""
 "số đầu tiên (v.d. <userinput>install fb=false</userinput>)."
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -1067,7 +1073,7 @@ msgstr ""
 "ulink> đến đó bạn có thể tham chiếu để tìm những phím đúng cần gõ."
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1088,7 +1094,7 @@ msgstr ""
 "<quote>Integrated Remote Assistant</quote> (IRA) của công ty HP."
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1108,13 +1114,13 @@ msgstr ""
 "nhắc khởi động, như được diễn tả trong đoạn văn trợ giúp."
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "Nội dung đĩa CD"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1138,7 +1144,7 @@ msgstr ""
 "hoàn toàn từ phạm vị gói rộng rãi mà không cần truy cập đến mạng."
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1164,7 +1170,7 @@ msgstr ""
 "giản trên hệ thống quy ước hơn."
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1180,7 +1186,7 @@ msgstr ""
 "này có thể được đọc từ trình bao EFI như được diễn tả bên dưới."
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1202,7 +1208,7 @@ msgstr ""
 "hợp, trước khi cho phép tiến trình cài đặt tiếp tục lại."
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1226,13 +1232,13 @@ msgstr ""
 "nào không khởi động được với nó, hãy bật tùy chọn thứ hai. "
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "QUAN TRỌNG"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1251,13 +1257,13 @@ msgstr ""
 "bằng cách chạy lệnh <command>exit</command> (thoát) tại dấu nhắc trình bao."
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "Tùy chọn 1: khởi động từ Trình đơn bảo dưỡng tùy chọn khởi động"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1269,7 +1275,7 @@ msgstr ""
 "thống."
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1280,7 +1286,7 @@ msgstr ""
 "này sẽ hiển thị một trình đơn mới."
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1299,7 +1305,7 @@ msgstr ""
 "thiết bị và thông tin về trình điều khiển là trùng."
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1317,7 +1323,7 @@ msgstr ""
 "năng khởi động, cần thiết bạn tiếp tục đến bước kế tiếp (thêm)."
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1333,7 +1339,7 @@ msgstr ""
 "phím &enterkey;. Việc này sẽ khởi chạy tiến trình tải khởi động."
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1345,13 +1351,13 @@ msgstr ""
 "tục tới giai đoạn đó."
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "Tùy chọn 2: khởi động từ trình bao EFI"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1365,7 +1371,7 @@ msgstr ""
 "đĩa CD cài đặt &debian; bằng cách theo những bước này:"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1377,7 +1383,7 @@ msgstr ""
 "thống."
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1400,7 +1406,7 @@ msgstr ""
 "sơ khởi ổ đĩa CD."
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1413,7 +1419,7 @@ msgstr ""
 "cũng hiển thị như là <filename>fs<replaceable>n</replaceable></filename>."
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1427,7 +1433,7 @@ msgstr ""
 "vùng như là dấu nhắc."
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1437,7 +1443,7 @@ msgstr ""
 "tiến trình tải khởi động."
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1453,13 +1459,13 @@ msgstr ""
 "đoạn chọn hạt nhân khởi động và các tùy chọn tương ứng."
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "Cài đặt bằng bàn điều khiển nối tiếp"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1480,7 +1486,7 @@ msgstr ""
 "độ truyền thường nhất đã được định sẵn."
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1494,7 +1500,7 @@ msgstr ""
 "trình bao EFI."
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1511,7 +1517,7 @@ msgstr ""
 "</classname> (khởi động)."
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1529,7 +1535,7 @@ msgstr ""
 "số) để tìm hướng dẫn về cách khởi chạy trình cài đặt trong Chế Độ Nhập Thô."
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1543,13 +1549,13 @@ msgstr ""
 "bất đầu cài đặt."
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "Chọn hát nhân khởi động và các tùy chọn tương ứng"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1570,7 +1576,7 @@ msgstr ""
 "chọn dòng lệnh thường dùng."
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1593,7 +1599,7 @@ msgstr ""
 "hệ thống được cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1603,7 +1609,7 @@ msgstr ""
 "nhất với điều kiện của máy tính của bạn."
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1615,7 +1621,7 @@ msgstr ""
 "thể xác định tham số hạt nhân như thiết lập bàn điều khiển nối tiếp."
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1627,7 +1633,7 @@ msgstr ""
 "cài đặt &debian;."
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1637,7 +1643,7 @@ msgstr ""
 "thiết lập miền địa phương (gồm ngôn ngữ), mạng và phân vùng đĩa."
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1657,7 +1663,7 @@ msgstr ""
 "đĩa CD."
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1672,13 +1678,13 @@ msgstr ""
 "lực khả năng nạp qua mạng."
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "Cấu hình máy phục vụ"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1702,7 +1708,7 @@ msgstr ""
 "efi</command> chạy được trên máy khách."
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1719,7 +1725,7 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1737,7 +1743,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1759,13 +1765,13 @@ msgstr ""
 "<classname>elilo</classname> để tìm chi tiết."
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "Cấu hình máy khách"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1797,7 +1803,7 @@ msgstr ""
 "phục vụ."
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1813,13 +1819,13 @@ msgstr ""
 "&debian;."
 
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Khởi động SGI qua TFTP"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1841,13 +1847,13 @@ msgstr ""
 "</screen></informalexample> trong bộ theo dõi lệnh."
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "Tham số khởi động"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1857,7 +1863,7 @@ msgstr ""
 "lệnh <command>bootp():</command> trong bộ theo dõi lệnh."
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1876,19 +1882,19 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Khởi động TFTP Cobalt"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1906,7 +1912,7 @@ msgstr ""
 "trên màn hình. Có những phương pháp cài đặt này:"
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1922,7 +1928,7 @@ msgstr ""
 "dụng khách SSH, bạn có thể khởi chạy tiến trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1934,7 +1940,7 @@ msgstr ""
 "bps) và thực hiện tiến trình cài đặt bằng cách này này."
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1947,13 +1953,13 @@ msgstr ""
 "replaceable> (đối số) trong nó."
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "Hạn chế S/390"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1963,7 +1969,7 @@ msgstr ""
 "và phiên chạy SSH hoạt động."
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1977,13 +1983,13 @@ msgstr ""
 "chuẩn."
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "Tham số khởi động S/390"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1995,7 +2001,7 @@ msgstr ""
 "Một tập tin parm mẫu được cung cấp cùng với ảnh cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -2013,7 +2019,7 @@ msgstr ""
 "động, để khởi động từ ổ đĩa CD-ROM mặc định."
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -2032,13 +2038,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -2055,7 +2061,7 @@ msgstr ""
 "tập tin cần thiết."
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -2067,19 +2073,19 @@ msgstr ""
 "hiện, gõ vào"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "Khởi động từ đĩa cứng"
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -2090,7 +2096,7 @@ msgstr ""
 "trợ."
 
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -2102,13 +2108,13 @@ msgstr ""
 "files\"/>."
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "Khởi động PowerMac kiểu cũ từ MacOS"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -2132,13 +2138,13 @@ msgstr ""
 "trình cài đặt &d-i;."
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "Khởi động Mac kiểu mới từ OpenFirmware"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2182,13 +2188,13 @@ msgstr ""
 "không đủ. Chương trình cài đặt &debian; nên khởi chạy."
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "Khởi động từ thanh bộ nhớ USB"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
@@ -2196,7 +2202,7 @@ msgstr ""
 "USB."
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2210,7 +2216,7 @@ msgstr ""
 "lưu trữ USB theo mặc định. Xem <xref linkend=\"invoking-openfirmware\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2233,7 +2239,7 @@ msgstr ""
 "pci@f2000000/usb@1b,1/hub@1/disk@1</filename> hoạt động được."
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2259,7 +2265,7 @@ msgstr ""
 "trong thư mục đã được hiệu lực bằng lệnh <command>hattrib -b</command>."
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2271,7 +2277,7 @@ msgstr ""
 "chọn, hoặc chỉ bấm phím &enterkey;."
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2283,7 +2289,7 @@ msgstr ""
 "gởi báo cáo cài đặt, như được diễn tả trong <xref linkend=\"submit-bug\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
@@ -2291,7 +2297,7 @@ msgstr ""
 "động qua mạng."
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2327,7 +2333,7 @@ msgstr ""
 "diễn tả cú pháp và các tùy chọn sẵn sàng."
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2340,7 +2346,7 @@ msgstr ""
 "mềm, và khả năng khởi động từ ổ đĩa mềm USB đã gắn kết không được hỗ trợ."
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2351,7 +2357,7 @@ msgstr ""
 "vào ổ đĩa mềm sau khi tắt hệ thống, còn trước khi bấm cái nút mở điện."
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2365,7 +2371,7 @@ msgstr ""
 "có khả năng khởi động."
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2377,13 +2383,13 @@ msgstr ""
 "chạy tự động sau khi hệ thống gốc đã được tải vào bộ nhớ."
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "Tham số khởi động máy PowerPC"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2400,7 +2406,7 @@ msgstr ""
 "userinput> ."
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2420,7 +2426,7 @@ msgstr ""
 "kết thúc của lệnh <userinput>boot</userinput>."
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2432,13 +2438,13 @@ msgstr ""
 "trên ID 6 (hay cái chủ phụ trên máy dựa vào IDE)."
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "Thông điệp IDPROM"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2453,13 +2459,13 @@ msgstr ""
 "thêm."
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "Khả năng truy cập"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2488,13 +2494,13 @@ msgstr ""
 "bàn phím kiểu QWERTY."
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "Thiết bị chữ nổi USB"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2516,13 +2522,13 @@ msgstr ""
 "driver-help;\"><classname>brltty</classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "Thiết bị chữ nổi nối tiếp"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2561,13 +2567,13 @@ msgstr ""
 "classname></ulink>."
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "Phần mềm tổng hợp giọng nói"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2583,13 +2589,13 @@ msgstr ""
 "classname>)."
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "Phần cứng tổng hợp giọng nói"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2601,7 +2607,7 @@ msgstr ""
 "quote> trong trình đơn khởi động."
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2622,13 +2628,13 @@ msgstr ""
 "driver-codes;\">danh sách các mã trình điều khiển</ulink>)."
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "Thiết bị bảng"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2645,7 +2651,7 @@ msgstr ""
 "ngữ sẵn sàng."
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2656,13 +2662,13 @@ msgstr ""
 "userinput> &enterkey; »."
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "Sắc thái cao tương phản"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2674,13 +2680,13 @@ msgstr ""
 "tham số khởi động <userinput>theme=dark</userinput>."
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "Việc chèn sẵn"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2690,7 +2696,7 @@ msgstr ""
 "chèn sẵn. Tài liệu có ở <xref linkend=\"appendix-preseed\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2704,7 +2710,7 @@ msgstr ""
 "số trường hợp, bạn cần phải giúp đỡ hạt nhân một ít."
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2719,7 +2725,7 @@ msgstr ""
 "thống biết về phần cứng đó."
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2736,7 +2742,7 @@ msgstr ""
 "troubleshooting\"/>."
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2778,7 +2784,7 @@ msgstr ""
 "tiếp trong &d-i; là <userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2824,7 +2830,7 @@ msgstr ""
 "tiếp trong &d-i; là <userinput>vt102</userinput>. </para> </footnote>."
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2838,13 +2844,13 @@ msgstr ""
 "envar> thành <filename>ttya</filename>."
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "Tham số trình cài đặt &debian;"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2858,7 +2864,7 @@ msgstr ""
 "nhân không thể phục hồi.</para> </footnote> có thể hữu ích."
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2874,19 +2880,19 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "Tham số này đặt ưu tiên thấp nhất cho những thông điệp cần hiển thị."
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2900,7 +2906,7 @@ msgstr ""
 "đặt điều chỉnh ưu tiên như cần thiết."
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2922,13 +2928,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2965,13 +2971,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2987,52 +2993,52 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "Đây là giá trị mặc định."
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "Chi tiết hơn cấp thường."
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "Xuất rất nhiều thông tin gỡ lỗi."
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -3044,13 +3050,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -3062,7 +3068,7 @@ msgstr ""
 "<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -3072,19 +3078,19 @@ msgstr ""
 "thể bị lọc bởi tham số này để phát hiện chỉ một thiết bị thôi."
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -3097,13 +3103,13 @@ msgstr ""
 
 # Name: don't translate/Tên: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -3116,13 +3122,13 @@ msgstr ""
 
 # nghĩa chữ ?
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -3134,13 +3140,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -3159,13 +3165,13 @@ msgstr ""
 "đặc trong vòng vài phút sau khi khởi chạy tiến trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "Lỗi như vậy đã được thông báo trên máy kiểu hppa."
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -3185,13 +3191,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -3208,13 +3214,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -3228,7 +3234,7 @@ msgstr ""
 "thăm dò DCHP."
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -3243,13 +3249,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -3261,13 +3267,13 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ : đừng dịch
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3283,13 +3289,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3300,13 +3306,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3317,13 +3323,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3340,13 +3346,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3359,13 +3365,13 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3379,13 +3385,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3404,7 +3410,7 @@ msgstr ""
 "động vật chứa."
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3417,13 +3423,13 @@ msgstr ""
 
 # nghĩa chữ ?
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (khuyến khích)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3437,7 +3443,7 @@ msgstr ""
 "cho hệ thống được cài đặt. Xem thêm <xref linkend=\"di-install-base\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3454,13 +3460,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3475,13 +3481,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3494,13 +3500,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3510,13 +3516,13 @@ msgstr ""
 "hơn là chạy tiến trình cài đặt chuẩn. Xem <xref linkend=\"rescue\"/>."
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "Dùng tham số khởi động để trả lời câu hỏi"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3530,27 +3536,27 @@ msgstr ""
 
 # nghĩa chữ ?
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (ngôn ngữ)"
 
 # nghĩa chữ ?
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (quốc gia)"
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3560,7 +3566,7 @@ msgstr ""
 "tiến trình cài đặt và hệ thống được cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3580,7 +3586,7 @@ msgstr ""
 "trong hệ thống thôi."
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3597,13 +3603,13 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ : đừng dịch
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3619,7 +3625,7 @@ msgstr ""
 "udeb</classname> (xem <xref linkend=\"pppoe\"/>)</phrase>."
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3629,13 +3635,13 @@ msgstr ""
 "và ép buộc cấu hình mạng tĩnh thay thế."
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3654,13 +3660,13 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ : đừng dịch
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3672,13 +3678,13 @@ msgstr ""
 "linkend=\"pkgsel\"/> để tìm thông tin thêm."
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "Gửi tham số cho mô-đun hạt nhân"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3702,7 +3708,7 @@ msgstr ""
 "trong cấu hình cho hệ thống đã cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3716,7 +3722,7 @@ msgstr ""
 "cần phải tự đặt tham số."
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3738,19 +3744,19 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ : đừng dịch
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "Cấm mô-đun hạt nhân"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3768,7 +3774,7 @@ msgstr ""
 "khiển không đúng được nạp trước."
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3784,7 +3790,7 @@ msgstr ""
 "thống được cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3798,19 +3804,19 @@ msgstr ""
 "được hiển thị trong những giải đoạn phát hiện phần cứng."
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "Giải đáp thắc mắc trong tiến trình cài đặt"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "Sự đáng tin cậy của đĩa CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3824,7 +3830,7 @@ msgstr ""
 "trong khi đọc nó trong tiến trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3836,13 +3842,13 @@ msgstr ""
 "định chúng. Theo bạn sửa."
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "Khuyên bạn trước tiên thử hai việc rất đơn giản."
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3852,7 +3858,7 @@ msgstr ""
 "nó không dơ bẩn."
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3871,7 +3877,7 @@ msgstr ""
 "đến DMA đã được quyết định bằng cách này."
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3883,7 +3889,7 @@ msgstr ""
 "cho cả hai đĩa CD và DVD, nhưng nói về đĩa CD-ROM vì đơn giản hơn."
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3893,13 +3899,13 @@ msgstr ""
 "đặt khác sẵn sàng."
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "Vấn đề thường gặp"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3909,7 +3915,7 @@ msgstr ""
 "tốc độ cao bằng bộ ghi CD hiện đại."
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3922,20 +3928,20 @@ msgstr ""
 "nhớ trực tiếp</quote> (DMA) được hiệu lực."
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "Cách xem xét và có thể quyết định vấn đề"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 "Đĩa CD-ROM không khởi động được thì hãy thử những lời đề nghị bên dưới."
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -3949,7 +3955,7 @@ msgstr ""
 "thống cũ không phải) và ổ đĩa CD-ROM hỗ trợ kiểu vật chứa đang được dùng."
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3976,7 +3982,7 @@ msgstr ""
 
 # Literal: don't translate/Nghĩa chữ : đừng dịch
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -4002,7 +4008,7 @@ msgstr ""
 "seconds\t\tgiây]"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -4023,7 +4029,7 @@ msgstr ""
 "bản giao tiếp ảo thứ hai (VT2) rồi kích hoạt trình bao ở đó."
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -4036,7 +4042,7 @@ msgstr ""
 "<command>dmesg</command>."
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -4072,7 +4078,7 @@ msgstr ""
 "nối, bạn có thể thử tự nạp nó bằng <command>modprobe</command>."
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -4085,7 +4091,7 @@ msgstr ""
 "dev/cdroms/cdrom0</filename>."
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -4101,7 +4107,7 @@ msgstr ""
 "lệnh đó."
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -4127,7 +4133,7 @@ msgstr ""
 "tương ứng với ổ đĩa CD-ROM đó."
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -4141,13 +4147,13 @@ msgstr ""
 "đọc đáng tin cây."
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "Sự đáng tin cậy của đĩa mềm"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -4157,7 +4163,7 @@ msgstr ""
 "đáng tin cậy của đĩa mềm."
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -4175,7 +4181,7 @@ msgstr ""
 "điệp về lỗi nhập/xuất trên đĩa."
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -4193,7 +4199,7 @@ msgstr ""
 "khác."
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -4205,7 +4211,7 @@ msgstr ""
 "còn sau đó, mọi thứ thì tốt với đĩa mềm thứ ba."
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -4217,7 +4223,7 @@ msgstr ""
 "tổng MD5SUM của nó."
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -4229,13 +4235,13 @@ msgstr ""
 "này do lỗi trong trình điều khiển đĩa mềm kiểu phần vững hay phần cứng."
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "Cấu hình khởi động"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -4249,7 +4255,7 @@ msgstr ""
 "\"boot-parms\"/>."
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -4258,7 +4264,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -4276,37 +4282,37 @@ msgstr ""
 "máy (ví dụ từ một đĩa CD)"
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "Vấn đề cài đặt &arch-title; thường"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -4316,7 +4322,7 @@ msgstr ""
 "cách gởi đối số khởi động riêng cho trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -4337,13 +4343,13 @@ msgstr ""
 "tiết."
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "Hệ thống đông đặc trong giai đoạn cấu hình PCMCIA"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -4371,7 +4377,7 @@ msgstr ""
 "bạn có thể cấu hình PCMCIA, và loại trừ phạm vị tài nguyên gây ra lỗi đó."
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4394,19 +4400,19 @@ msgstr ""
 "trị này vào trình cài đặt."
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "Một số vấn đề cài đặt thường gặp."
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "Kết xuất ảnh động bị hướng sai"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4434,7 +4440,7 @@ msgstr ""
 "(ảnh động=atyfb:tắt)."
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4448,13 +4454,13 @@ msgstr ""
 "cấu hình <filename>/etc/X11/xorg.conf</filename>."
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "Lỗi khởi động hay cài đặt từ đĩa CD-ROM"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4467,7 +4473,7 @@ msgstr ""
 "SunBlade."
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
@@ -4475,13 +4481,13 @@ msgstr ""
 "mạng."
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "Giải thích thông điệp khởi chạy hạt nhân"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4518,13 +4524,13 @@ msgstr ""
 "<phrase arch=\"linux-any\">(xem <xref linkend=\"kernel-baking\"/>)</phrase>."
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "Thông báo vấn đề cài đặt"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4543,7 +4549,7 @@ msgstr ""
 "nó. Khi thông báo lỗi, khuyên bạn đính kèm thông tin này."
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4555,13 +4561,13 @@ msgstr ""
 "</filename> sau khi máy tính đã khởi động vào hệ thống mới được cài đặt."
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "Đệ trình báo cáo cài đặt"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4577,7 +4583,7 @@ msgstr ""
 "<email>vi-VN@googlegroups.com</email> nhé. Chúng tôi sẽ dịch cho bạn.]"
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4589,7 +4595,7 @@ msgstr ""
 "đảm bảo bạn sử dụng một địa chỉ thư điện tử cũng công cộng."
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4609,7 +4615,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/vi/install-methods.po b/po/vi/install-methods.po
index 44b575826..c2e093bb3 100644
--- a/po/vi/install-methods.po
+++ b/po/vi/install-methods.po
@@ -7,7 +7,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: install-methods\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-31 22:16+0700\n"
 "Last-Translator: hailang <hailangvn@gmail.com>\n"
 "Language-Team: MOST Project <du-an-most@lists.hanoilug.org>\n"
@@ -82,15 +82,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -131,7 +130,7 @@ msgstr ""
 "tập tin đó trong cùng một thư mục trên đĩa CD."
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -141,7 +140,7 @@ msgstr ""
 "tập tin khác cần thiết."
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -160,13 +159,13 @@ msgstr ""
 "nó để khởi động trình cài đặt."
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "Tải tập tin xuống máy nhân bản &debian;"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -176,7 +175,7 @@ msgstr ""
 "debian-mirrors;\">danh sách máy nhân bản &debian;</ulink>."
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -187,13 +186,13 @@ msgstr ""
 "độ văn bản (text) hay tự động (automatic)."
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "Tìm ảnh cài đặt ở đâu"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -209,13 +208,13 @@ msgstr ""
 "và mục đích tương ứng."
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Tập tin cài đặt N2100 Thecus"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -229,13 +228,13 @@ msgstr ""
 "ảnh &nslu2-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "Tập tin cài đặt GLAN Tank"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -247,13 +246,13 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Tập tin cài đặt Kurobox Pro"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -265,13 +264,13 @@ msgstr ""
 "firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "Tập tin cài đặt HP mv2120"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -287,13 +286,13 @@ msgstr ""
 "&mv2120-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "Tập tin cài đặt QNAP Turbo Station"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -307,13 +306,13 @@ msgstr ""
 "TS-41x từ &qnap-kirkwood-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Tập tin Cài đặt Máy tính Đầu gắn điện (Plug Computer) và OpenRD"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -329,14 +328,14 @@ msgstr ""
 "này từ &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "NSLU2 Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "Tập tin cài đặt NSLU2"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -353,13 +352,13 @@ msgstr ""
 "này từ &kirkwood-marvell-firmware-img;."
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "Tạo băng IPL"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -382,13 +381,13 @@ msgstr ""
 "filename>: xem <xref linkend=\"where-files\"/>."
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "Tạo đĩa mềm từ ảnh đĩa"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -399,7 +398,7 @@ msgstr ""
 "CD hoặc bằng cách nào khác."
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -409,7 +408,7 @@ msgstr ""
 "từ đĩa mềm nằm trong ổ đĩa mềm USB của máy tính Apple Mac."
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -429,7 +428,7 @@ msgstr ""
 "emphasis> các dữ liệu từ tập tin vào đĩa mềm."
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -440,7 +439,7 @@ msgstr ""
 "tả phương pháp tạo đĩa mềm từ ảnh đĩa trên nền tảng khác nhau."
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -455,7 +454,7 @@ msgstr ""
 "cài đặt, những ảnh đĩa mềm có thể nằm trên đĩa đó.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -467,13 +466,13 @@ msgstr ""
 "sẽ không bị hại tình cờ."
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "Ghi ảnh đĩa từ hệ thống Linux/UNIX"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -509,7 +508,7 @@ msgstr ""
 "tìm chi tiết)</phrase>."
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -542,7 +541,7 @@ msgstr ""
 "filename>). Trên hệ thống khác, hãy hỏi quản trị hệ thống. </phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -554,13 +553,13 @@ msgstr ""
 "cài đặt nó trước tiên."
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "Ghi ảnh đĩa từ DOS, Windows, hay OS/2"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -570,7 +569,7 @@ msgstr ""
 "một của những chương trình sau đây để sao chép ảnh vào đĩa mềm."
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -587,7 +586,7 @@ msgstr ""
 "động được."
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -599,7 +598,7 @@ msgstr ""
 "bạn sẽ cần phải giải nén tập tin « diskio.dll » trong cùng thư mục."
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -609,13 +608,13 @@ msgstr ""
 "thư mục <filename>/tools</filename> (công cụ)."
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "Ghi ảnh đĩa từ MacOS"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -638,7 +637,7 @@ msgstr ""
 "bỏ hẳn đĩa mềm đó, sau đó nó sẽ ghi vào đó ảnh tập tin."
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -653,13 +652,13 @@ msgstr ""
 "bằng những tiện ích này."
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "Ghi ảnh đĩa bằng <command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -674,7 +673,7 @@ msgstr ""
 "máy nhân bản &debian;."
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -684,7 +683,7 @@ msgstr ""
 "ulink> và dùng nó để mở tập tin <filename>root.bin</filename>."
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -696,7 +695,7 @@ msgstr ""
 "trường này phân biệt chữ hoa/thường."
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -712,7 +711,7 @@ msgstr ""
 "hành MacOS gỡ bỏ các khối tin khởi động nếu ảnh này được gắn kết tình cờ."
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -724,7 +723,7 @@ msgstr ""
 "url=\"&url-powerpc-diskcopy;\"></ulink>."
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -741,13 +740,13 @@ msgstr ""
 "chương trình nên đẩy ra đĩa."
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "Ghi ảnh đĩa bằng <command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -761,7 +760,7 @@ msgstr ""
 "đơn <userinput>Special</userinput> (đặc biệt)."
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
@@ -769,14 +768,14 @@ msgstr ""
 "Khi được nhắc, nạp đĩa mềm, rồi bấm phím &enterkey; (bất đầu ở rãnh ghi 0)."
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr "Chọn tập tin <filename>root.bin</filename> trong hộp thoại mở tập tin."
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -789,7 +788,7 @@ msgstr ""
 "Nếu gặp lỗi nào trong khi tạo đĩa mềm, đơn giản hãy bỏ đĩa và thử đĩa mới."
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -801,13 +800,13 @@ msgstr ""
 "tình cờ."
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "Chuẩn bị tập tin để khởi động thanh bộ nhớ USB"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -830,7 +829,7 @@ msgstr ""
 "phải tắt cái chuyển bảo vệ chống ghi của nó."
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -844,13 +843,13 @@ msgstr ""
 "là tất cả các thông tin nằm trên (ví dụ) một đĩa cứng bị mất hoàn toàn."
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "Chuẩn bị một thanh USB bằng ảnh CD lai hay DVD"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -864,7 +863,7 @@ msgstr ""
 "lấy về một ảnh CD hay DVD."
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -877,7 +876,7 @@ msgstr ""
 "filename> (tại vị trí được đề cập đến trong <xref linkend=\"where-files\"/>)."
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -896,7 +895,7 @@ msgstr ""
 
 # Literal: don't translate; Nghĩa chữ : dừng dịch
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -912,7 +911,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -926,7 +925,7 @@ msgstr ""
 "khi bạn chắc chắn rằng thanh đó đã được tháo gắn kết:"
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -938,7 +937,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -950,13 +949,13 @@ msgstr ""
 "những người có nhu cầu đặc biệt."
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "Chép thủ công các tập tin vào thanh USB"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -970,7 +969,7 @@ msgstr ""
 "copy-flexible\"/>)."
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -986,7 +985,7 @@ msgstr ""
 "của nó.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -1002,20 +1001,20 @@ msgstr ""
 "khác."
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr "Để sử dụng ảnh này, chỉ cần giải nén nó trực tiếp vào thanh USB:"
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -1028,13 +1027,13 @@ msgstr ""
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -1065,13 +1064,13 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>) và bạn đã làm xong."
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "Chép thủ công các tập tin vào thanh USB &mdash; theo cách uyển chuyển"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1086,13 +1085,13 @@ msgstr ""
 "có tùy chọn sao chép vào nó một ảnh ISO đĩa CD đầy đủ."
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "Phân vùng thanh USB"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1102,7 +1101,7 @@ msgstr ""
 "thứ nhất, thay vì toàn bộ thiết bị."
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1144,7 +1143,7 @@ msgstr ""
 "<classname>dosfstools</classname>."
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1163,7 +1162,7 @@ msgstr ""
 "cấu hình của bộ nạp khởi động."
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1187,13 +1186,13 @@ msgstr ""
 "<filename>ldlinux.sys</filename> mà chứa mã của bộ nạp khởi động."
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "Thêm ảnh cài đặt"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1219,7 +1218,7 @@ msgstr ""
 "lý tên tập tin kiểu DOS (8.3)."
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1253,7 +1252,7 @@ msgstr ""
 "vào dòng thứ hai chuỗi <userinput>vga=788</userinput>."
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1261,7 +1260,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy "
@@ -1290,7 +1289,7 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>)."
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1319,7 +1318,7 @@ msgstr ""
 "<classname>hfsutils</classname>."
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1336,7 +1335,7 @@ msgstr ""
 "động."
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1372,7 +1371,7 @@ msgstr ""
 "ích UNIX thông thường."
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1383,31 +1382,31 @@ msgstr ""
 "Debian:"
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (tập tin nhị phân của hạt nhân)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (ảnh đĩa RAM đầu tiên)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (tập tin cấu hình yaboot)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (thông điệp khởi động tùy chọn)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1443,13 +1442,13 @@ msgstr ""
 "khởi động."
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "Chuẩn bị tập tin để khởi động đĩa cứng"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1461,7 +1460,7 @@ msgstr ""
 "một bộ nạp khởi động trực tiếp từ BIOS."
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1475,7 +1474,7 @@ msgstr ""
 "đáng tin."
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1499,7 +1498,7 @@ msgstr ""
 "hệ điều hành MacOS và Linux, đặc biệt các tập tin cài đặt bạn tải về."
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1510,7 +1509,7 @@ msgstr ""
 "trình khác nhau để khởi động hệ thống cài đặt trên đĩa cứng."
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1520,7 +1519,7 @@ msgstr ""
 "<command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1531,7 +1530,7 @@ msgstr ""
 "command>."
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1543,7 +1542,7 @@ msgstr ""
 "RAM này như là hệ thống tập tin gốc."
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1554,19 +1553,19 @@ msgstr ""
 "trên đĩa cứng, v.d. vào <filename>/boot/newinstall/</filename>."
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename> (tập tin nhị phân của hạt nhân)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (ảnh đĩa RAM)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1576,13 +1575,13 @@ msgstr ""
 "\"boot-initrd\"/>."
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr "Khởi động trình cài đặt trên đĩa cứng bằng <command>loadlin</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1592,7 +1591,7 @@ msgstr ""
 "DOS, dùng <command>loadlin</command>."
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1602,7 +1601,7 @@ msgstr ""
 "mục theo đây."
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
@@ -1611,19 +1610,19 @@ msgstr ""
 "RAM)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (công cụ loadlin)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "Khởi động trình cài đặt trên đĩa cứng của Mac kiểu cũ"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1648,7 +1647,7 @@ msgstr ""
 "ứng dụng <application>BootX</application>."
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1676,13 +1675,13 @@ msgstr ""
 "Kernels</filename> vào System Folder (thư mục hệ thống) đang hoạt động."
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "Khởi động trình cài đặt trên đĩa cứng của Mac kiểu mới"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1703,7 +1702,7 @@ msgstr ""
 "command> nên không dùng nó trên máy PowerMac kiểu mới."
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1718,34 +1717,34 @@ msgstr ""
 
 # Name: don't translate / Tên: đừng dịch
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 # Name: don't translate / Tên: đừng dịch
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 # Literal: don't translate / Nghĩa chữ: đừng dịch
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1761,7 +1760,7 @@ msgstr ""
 "cài đặt."
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
@@ -1769,13 +1768,13 @@ msgstr ""
 ">."
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "Chuẩn bị tập tin để khởi động qua mạng TFTP"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1790,7 +1789,7 @@ msgstr ""
 "đó, cũng cấu hình máy đó để hỗ trợ khả năng khởi động máy tính riêng của bạn."
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1803,7 +1802,7 @@ msgstr ""
 "phrase>."
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1824,7 +1823,7 @@ msgstr ""
 "thống riêng chỉ có thể được cấu hình bằng DHCP.</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1836,7 +1835,7 @@ msgstr ""
 "BOOTP."
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1846,7 +1845,7 @@ msgstr ""
 "một gói <classname>rbootd</classname>."
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1861,7 +1860,7 @@ msgstr ""
 "SunOS 5.x (cũng tên Solaris), và GNU/Linux."
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1875,13 +1874,13 @@ msgstr ""
 "đề. Một sự chọn tốt khác là <classname>atftpd</classname>."
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "Thiết lập trình phục vụ RARP"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1900,7 +1899,7 @@ msgstr ""
 "dụng câu lệnh <userinput>ip addr show dev eth0</userinput>."
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1925,13 +1924,13 @@ msgstr ""
 "rarpd -a</userinput> trên hệ thống SunOS 4 (Solaris 1)."
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Thiết lập trình phục vụ DHCP"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1945,7 +1944,7 @@ msgstr ""
 "filename>):"
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -2005,7 +2004,7 @@ msgstr ""
 "fixed-address\t\tđịa chỉ cố định]"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -2023,7 +2022,7 @@ msgstr ""
 "replaceable> (tên tập tin) nên là tên tập tin sẽ được lấy thông qua TFTP."
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -2034,13 +2033,13 @@ msgstr ""
 "server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "Bật khả năng khởi động PXE trong cấu hình DHCP"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -2111,13 +2110,13 @@ msgstr ""
 "hạt nhân (xem <xref linkend=\"tftp-images\"/> bên dưới)."
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "Thiết lập trình phục vụ BOOTP"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -2133,7 +2132,7 @@ msgstr ""
 "từng cái."
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2199,7 +2198,7 @@ msgstr ""
 "</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2224,13 +2223,13 @@ msgstr ""
 "dhcp3-server restart</userinput>."
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Bật chạy trình phục vụ TFTP"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2240,7 +2239,7 @@ msgstr ""
 "<command>tftpd</command> được hiệu lực."
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2256,7 +2255,7 @@ msgstr ""
 "cài đặt, và lúc nào cũng có thể được thay đổi bằng cách cấu hình lại gói đó."
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2275,7 +2274,7 @@ msgstr ""
 "ứng."
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2292,7 +2291,7 @@ msgstr ""
 "để chẩn đoán nguyên nhân của lỗi."
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2323,13 +2322,13 @@ msgstr ""
 "trình phục vụ TFTP Linux sử dụng."
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "Xác định vị trí của ảnh TFTP"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2346,7 +2345,7 @@ msgstr ""
 "tiêu chuẩn mạnh nào."
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2362,13 +2361,13 @@ msgstr ""
 "tập tin theo đây:"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2385,7 +2384,7 @@ msgstr ""
 "tin cần khởi động."
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2402,13 +2401,13 @@ msgstr ""
 "như là tên tập tin cần khởi động."
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "Khởi động TFTP SPARC"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2438,7 +2437,7 @@ msgstr ""
 "đổi mọi chữ sang chữ hoa, cũng (nếu cần thiết) phụ thêm tên kiến trúc phụ đó."
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2451,7 +2450,7 @@ msgstr ""
 "tra các bản ghi trên trình phục vụ TFTP để xem tên ảnh nào được yêu cầu."
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2465,13 +2464,13 @@ msgstr ""
 "phục vụ TFTP tìm."
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "Khởi động TFTP SGI"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2486,13 +2485,13 @@ msgstr ""
 "tin cấu hình <filename>/etc/dhcpd.conf</filename>."
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Cài đặt tự động"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2508,13 +2507,13 @@ msgstr ""
 "ulink> để tìm thông tin chi tiết."
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "Tự động cài đặt dùng trình cài đặt &debian;"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2527,7 +2526,7 @@ msgstr ""
 "cũng cung cấp trả lời cho câu được hỏi trong khi cài đặt."
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/zh_CN/boot-installer.po b/po/zh_CN/boot-installer.po
index 471d55ae5..c81da4000 100644
--- a/po/zh_CN/boot-installer.po
+++ b/po/zh_CN/boot-installer.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-25 16:38+0800\n"
 "Last-Translator: Ji YongGang <jungleji@gmail.com>\n"
 "Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n"
@@ -56,8 +56,8 @@ msgstr "从 TFTP 引导"
 
 # index.docbook:432, index.docbook:786, index.docbook:1338, index.docbook:1819, index.docbook:2242, index.docbook:2338
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -68,8 +68,8 @@ msgstr ""
 
 # index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -78,8 +78,8 @@ msgstr "较早的系统比如 715 也许需要使用一台 RBOOT 服务器来取
 
 # index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -94,8 +94,8 @@ msgstr "从 CD 光盘上引导"
 
 # index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -111,8 +111,8 @@ msgstr ""
 
 # index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -127,8 +127,8 @@ msgstr ""
 
 # index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -143,8 +143,8 @@ msgstr ""
 
 # index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -370,8 +370,8 @@ msgstr "安装程序将正常启动。"
 
 # index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "从 CD-ROM 启动"
@@ -390,16 +390,22 @@ msgstr "从 Windows 下启动安装程序，您可以"
 
 #. Tag: para
 #: boot-installer.xml:355
-#, no-c-format
+#, fuzzy, no-c-format
+#| msgid ""
+#| "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described "
+#| "in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files"
+#| "\"/>, or"
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "从 <xref linkend=\"official-cdrom\"/> 和 <xref linkend=\"boot-usb-files\"/> "
 "获取 CD-ROM/DVD-ROM 或 U 盘安装映像，或者"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -409,7 +415,7 @@ msgstr ""
 "stable/win32-loader.exe，"
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -423,7 +429,7 @@ msgstr ""
 "<command>setup.exe</command> 程序。"
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -434,13 +440,13 @@ msgstr ""
 "序。"
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, no-c-format
 msgid "Booting from DOS"
 msgstr "从 DOS 引导"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -448,7 +454,7 @@ msgid ""
 msgstr "要启动到 DOS (非 Windows)，您可以从一个用于恢复或诊断的磁盘引导。"
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -465,7 +471,7 @@ msgstr ""
 "\"/> 指引准备好了硬盘, 然后切换到该磁盘。"
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -486,14 +492,14 @@ msgstr ""
 "会加载并运行安装程序。"
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr "引导 Linux 使用 <command>LILO</command> 或 <command>GRUB</command>"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -503,7 +509,7 @@ msgstr ""
 "<xref linkend=\"boot-drive-files\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -519,7 +525,7 @@ msgstr ""
 "您重新分区用于引导的硬盘，需要小心操作。"
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, no-c-format
 msgid ""
 "Alternatively, if you intend to keep an existing partition on the hard drive "
@@ -535,7 +541,7 @@ msgstr ""
 "以从硬盘引导，并从 CD/DVD 映像文件上安装，而不使用网络。"
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -553,7 +559,7 @@ msgstr ""
 "lilo.conf</filename> 的例子："
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -565,7 +571,7 @@ msgstr ""
 "       initrd=/boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -580,7 +586,7 @@ msgstr ""
 "行 <userinput>lilo</userinput> 并且重新启动。"
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -595,7 +601,7 @@ msgstr ""
 "boot</filename> 位于系统中第一个磁盘的第一个分区上面):"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, no-c-format
 msgid ""
 "title  New Install\n"
@@ -609,7 +615,7 @@ msgstr ""
 "initrd /boot/newinstall/initrd.gz"
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -620,7 +626,7 @@ msgstr ""
 "filename> 替代 <filename>menu.lst</filename> 文件。安装程序的入口，例如:"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -640,7 +646,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
 "From here on, there should be no difference between <command>GRUB</command> "
@@ -651,13 +657,13 @@ msgstr ""
 
 # index.docbook:700, index.docbook:2176
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "从 U 盘引导"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -681,14 +687,14 @@ msgstr ""
 
 # index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "从软盘引导"
 
 # index.docbook:724, index.docbook:2286
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -698,7 +704,7 @@ msgstr ""
 "\"create-floppy\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -708,7 +714,7 @@ msgstr ""
 "开。"
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -724,7 +730,7 @@ msgstr ""
 "(master)，那么在提示符下输入 <userinput>install root=/dev/hdc</userinput>。"
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -739,7 +745,7 @@ msgstr ""
 "选择。在其它情况下，请在引导时使用硬重启。"
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -749,7 +755,7 @@ msgstr ""
 "</prompt> 提示符。"
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -765,7 +771,7 @@ msgstr ""
 "下面 <xref linkend=\"kernel-msgs\"/> 可以找到。"
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -778,26 +784,26 @@ msgstr ""
 
 # index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "用 TFTP 引导"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "在 i386 体系上有很多方法用 TFTP 进行引导。"
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "支持 PXE 的网卡或者主板"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -810,13 +816,13 @@ msgstr ""
 "引导。"
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "网络 BootROM 的网卡"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -824,7 +830,7 @@ msgid ""
 msgstr "您的网卡很有可能提供了 TFTP 引导功能。"
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -834,13 +840,13 @@ msgstr ""
 "文档。"
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -851,13 +857,13 @@ msgstr ""
 
 # index.docbook:1943, index.docbook:2477
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, no-c-format
 msgid "The Boot Screen"
 msgstr "引导界面"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, no-c-format
 msgid ""
 "When the installer boots, you should be presented with a friendly graphical "
@@ -892,7 +898,7 @@ msgstr ""
 "项，在其下方，因此会有双倍的选项。"
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -906,7 +912,7 @@ msgstr ""
 "quote> 入口已经选中 &mdash; 然后按下 &enterkey; 引导安装程序。"
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -917,7 +923,7 @@ msgstr ""
 "expert 模式、rescue 模式和自动安装。"
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -933,7 +939,7 @@ msgstr ""
 "您所做的修改。"
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Choosing the <quote>Help</quote> entry will result in the first help "
@@ -979,7 +985,7 @@ msgstr ""
 "(例如：<userinput>install fb=false</userinput>)。"
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -995,7 +1001,7 @@ msgstr ""
 "说明了如何找到要使用正确的键。"
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -1013,7 +1019,7 @@ msgstr ""
 "Assistant</quote> (IRA)。"
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -1031,13 +1037,13 @@ msgstr ""
 "userinput>，这在帮助里面有说明。"
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "CD 的内容"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -1058,7 +1064,7 @@ msgstr ""
 "光盘套件，则可以不使用网络就能安装大量软件包，建立完整的系统。"
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -1081,7 +1087,7 @@ msgstr ""
 "MBR 或者引导块记录。"
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1096,7 +1102,7 @@ msgstr ""
 "说明如下。"
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1115,7 +1121,7 @@ msgstr ""
 "查一个 EFI 分区是否合适。"
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1135,13 +1141,13 @@ msgstr ""
 "用第一个，当然，该选项不可用或者 CD 由于某种原因没法启动，使用第二个。"
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "重要"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1158,13 +1164,13 @@ msgstr ""
 "command>返回 Boot Manager。"
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "选项 1: 从 Boot Option Maintenance Menu 启动"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1175,7 +1181,7 @@ msgstr ""
 "Boot Manager 页面和菜单。"
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1185,7 +1191,7 @@ msgstr ""
 "<command>ENTER</command>。会显示一个新菜单。"
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1201,7 +1207,7 @@ msgstr ""
 "Boot</command>标签。如果您检查菜单行其他部分，会看到对应的设备和控制器信息。"
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1217,7 +1223,7 @@ msgstr ""
 "的 CD 目录列表，要求您进行(额外的)下一步。"
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1231,7 +1237,7 @@ msgstr ""
 "择，并按下 <command>ENTER</command>。这将进入启动步骤。"
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1242,13 +1248,13 @@ msgstr ""
 "进入选择启动内核和选项。"
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "选项 2: 从 EFI Shell 启动"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1261,7 +1267,7 @@ msgstr ""
 "来引导 &debian; 安装程序 CD :"
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1270,7 +1276,7 @@ msgid ""
 msgstr "把 CD 放入 DVD/CD 驱动器。"
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1290,7 +1296,7 @@ msgstr ""
 "用于初始化 CD 驱动器。"
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1303,7 +1309,7 @@ msgstr ""
 "<filename>fs<replaceable>n</replaceable></filename>。"
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1316,7 +1322,7 @@ msgstr ""
 "光盘的分区号。Shell 现在将在提示符下显示分区号。"
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1326,7 +1332,7 @@ msgstr ""
 "骤。"
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1340,13 +1346,13 @@ msgstr ""
 "replaceable>:elilo</command>简短命令。进入选择启动内核和选项。"
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "使用串口控制台安装"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1364,7 +1370,7 @@ msgstr ""
 "置。"
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1376,7 +1382,7 @@ msgstr ""
 "置，可以通过命令 <command>baud</command> 在 EFI shell 获得。"
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1391,7 +1397,7 @@ msgstr ""
 "窗口。"
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1406,7 +1412,7 @@ msgstr ""
 "装。参考 <classname>Params</classname> 帮助菜单，获得启动文本模式安装的指导。"
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1418,13 +1424,13 @@ msgstr ""
 "核启动后死掉，只有重新启动才能开始安装。"
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "选择启动内核与选项"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1441,7 +1447,7 @@ msgstr ""
 "<classname>Params</classname>窗口解释命令行参数。"
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1461,7 +1467,7 @@ msgstr ""
 "始安装："
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1469,7 +1475,7 @@ msgid ""
 msgstr "使用方向键选择您需要的内核版本和适合的安装模式。"
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1480,7 +1486,7 @@ msgstr ""
 "控制台)指定的。"
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1491,7 +1497,7 @@ msgstr ""
 "一个屏幕显示常规的初始化信息。"
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1499,7 +1505,7 @@ msgid ""
 msgstr "进入到下一章继续安装本地语言，网络和磁盘分区。"
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1516,7 +1522,7 @@ msgstr ""
 "器。"
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1529,13 +1535,13 @@ msgstr ""
 "必须在 EFI boot manager 下定义来打开网络的装入。"
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "配置网络服务器"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1559,7 +1565,7 @@ msgstr ""
 "在客户端运行。"
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1574,7 +1580,7 @@ msgstr ""
 "它包括 IA-64 系统需要的启动文件。"
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1592,7 +1598,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1611,13 +1617,13 @@ msgstr ""
 "filename>。请查看 <classname>elilo</classname> 软件包附带的文档以获得细节。"
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "配置客户机"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1644,7 +1650,7 @@ msgstr ""
 "DHCP 查询，然后会从服务器装入 <filename>elilo.efi</filename>。"
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1659,13 +1665,13 @@ msgstr ""
 
 # index.docbook:1899, index.docbook:1946
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI TFTP 引导"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1687,13 +1693,13 @@ msgstr ""
 
 # index.docbook:1943, index.docbook:2477
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "引导参数"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1703,7 +1709,7 @@ msgstr ""
 "参数。"
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1721,20 +1727,20 @@ msgstr ""
 "command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 # index.docbook:1899, index.docbook:1946
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "Cobalt TFTP 引导"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1749,7 +1755,7 @@ msgstr ""
 "键，机器就从 NFS 网络启动。它会在显示器上显示几个选项。有下面两种安装方法："
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1763,7 +1769,7 @@ msgstr ""
 "到机器就可以开始安装。"
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1774,7 +1780,7 @@ msgstr ""
 "115200 bps) 然后进行安装。"
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1785,13 +1791,13 @@ msgstr ""
 "default.colo</filename> 文件，将参数给 <replaceable>args</replaceable> 变量。"
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390 的限制"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1799,7 +1805,7 @@ msgid ""
 msgstr "为了在 S/390 上安装系统，需要一个工作的网络设置和 ssh 会话。"
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1811,13 +1817,13 @@ msgstr ""
 "一个 ssh 会话登录进入系统，并且开始一个标准系统安装。"
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390 引导参数"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1829,7 +1835,7 @@ msgstr ""
 "映像。"
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1845,7 +1851,7 @@ msgstr ""
 "keycap> 和 <keycap>Delete</keycap> 组合键引导出厂默认的 CD/DVD 驱动器。"
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -1862,13 +1868,13 @@ msgstr ""
 "</screen></informalexample> 另一种方法引导出厂默认的 CD/DVD 驱动器，键入"
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -1883,7 +1889,7 @@ msgstr ""
 "安装程序 从 CD 上选择所需要的文件。"
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -1894,20 +1900,20 @@ msgstr ""
 "<keycap>Esc</keycap> 键，出现 SmartFirmware 提示符后，键入"
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr "boot cd install/pegasos"
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "从硬盘引导"
 
 # index.docbook:1591, index.docbook:2097
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -1918,7 +1924,7 @@ msgstr ""
 
 # index.docbook:1597, index.docbook:2103
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you will have already completed "
@@ -1929,13 +1935,13 @@ msgstr ""
 "下载并且安置所需文件。"
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "从 OldWorld PowerMacs 的 MacOS 上引导"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -1956,13 +1962,13 @@ msgstr ""
 "序。"
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "从 NewWorld Macs 的 OpenFirmware 引导"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, no-c-format
 msgid ""
 "You will have already placed the <filename>vmlinux</filename>, "
@@ -2003,19 +2009,19 @@ msgstr ""
 
 # index.docbook:700, index.docbook:2176
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "从 U 盘引导"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr "当前，New World PowerMac 系统支持从 USB 引导。"
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, no-c-format
 msgid ""
 "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
@@ -2028,7 +2034,7 @@ msgstr ""
 "Open Firmware 提示符。参阅 <xref linkend=\"invoking-openfirmware\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -2049,7 +2055,7 @@ msgstr ""
 "disk@1</filename> 。"
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2073,7 +2079,7 @@ msgstr ""
 "command>。"
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2084,7 +2090,7 @@ msgstr ""
 "动参数，或者只按下 &enterkey;。"
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2095,13 +2101,13 @@ msgstr ""
 "下安装报告，参阅 <xref linkend=\"submit-bug\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr "目前来说，PReP 以及 New World PowerMac 系统支持网络引导。"
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2134,7 +2140,7 @@ msgstr ""
 "<userinput>help boot</userinput> 命令可以给出语法和选项的说明。"
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2146,7 +2152,7 @@ msgstr ""
 "没有安装 软盘驱动器，并且附带的 USB 软盘并不支持引导。"
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2157,7 +2163,7 @@ msgstr ""
 "按下电源开关前把它放到软盘驱动器内。"
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2169,7 +2175,7 @@ msgstr ""
 "序。一个 没有有效引导系统的软盘将回被弹出，并且机器将检查硬盘分区。"
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2180,13 +2186,13 @@ msgstr ""
 "&enterkey;。安装程序将在根系统被装入内存后自动启动。"
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC 引导参数"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2201,7 +2207,7 @@ msgstr ""
 "128 来说，请改变其值为 <userinput>video=aty128fb:vmode:6</userinput> 。"
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2220,7 +2226,7 @@ msgstr ""
 "i; 。"
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2232,13 +2238,13 @@ msgstr ""
 "盘)。"
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM 消息"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2252,13 +2258,13 @@ msgstr ""
 "nvram-faq;\">Sun NVRAM FAQ</ulink> 以获得更多信息。"
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr "辅助功能"
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2283,13 +2289,13 @@ msgstr ""
 "要注意在大多数架构下 boot loader 将视您的键盘为 QWERTY 布局。"
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr "USB 盲文点显器"
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2308,13 +2314,13 @@ msgstr ""
 "website</ulink> 可以找到盲文点显器的键绑定文档。"
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr "串口盲文点显器"
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2349,13 +2355,13 @@ msgstr ""
 "\"><classname>brltty</classname> website</ulink> 找到。"
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr "软件语音合成(Software Speech Synthesis)"
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2369,13 +2375,13 @@ msgstr ""
 "<classname>espeak</classname>)。"
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr "硬件语音合成(Hardware Speech Synthesis)"
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2386,7 +2392,7 @@ msgstr ""
 "择 <quote>Graphical install</quote> 项。"
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2406,13 +2412,13 @@ msgstr ""
 "对于语音合成设备的支持也会被自动安装到最终系统里面。"
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr "板卡设备"
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2427,7 +2433,7 @@ msgstr ""
 "数量。"
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2437,13 +2443,13 @@ msgstr ""
 "userinput> &enterkey;。"
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr "高亮主题"
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2454,13 +2460,13 @@ msgstr ""
 "<userinput>theme=dark</userinput> 引导参数即可。"
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr "预置"
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2470,7 +2476,7 @@ msgstr ""
 "\"appendix-preseed\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2483,7 +2489,7 @@ msgstr ""
 "要给内核一点小小的帮助。"
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2496,7 +2502,7 @@ msgstr ""
 "的硬件特定参数。"
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2511,7 +2517,7 @@ msgstr ""
 "linkend=\"boot-troubleshooting\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2549,7 +2555,7 @@ msgstr ""
 "para> </footnote>。"
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2591,7 +2597,7 @@ msgstr ""
 "para> </footnote>。"
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2604,13 +2610,13 @@ msgstr ""
 "<envar>output-device</envar> OpenPROM 变量至 <filename>ttya</filename>。"
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "&debian; 安装程序的参数"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2623,7 +2629,7 @@ msgstr ""
 "para> </footnote>，它们很有用。"
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2637,19 +2643,19 @@ msgstr ""
 "用简写。"
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority (priority)"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "这些参数设置将设置显示的信息为最低的级别。"
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2662,7 +2668,7 @@ msgstr ""
 "将按照要求调整优先级别。"
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2680,13 +2686,13 @@ msgstr ""
 "且尝试正确无误地执行各项事宜。"
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2719,13 +2725,13 @@ msgstr ""
 "所支持的平台上使用 <userinput>gtk</userinput> 前端。"
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2737,49 +2743,49 @@ msgstr ""
 "debug shell。(退出 shell 以后会继续引导过程。)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "此为默认。"
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "更多的信息。"
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "大量的调试信息。"
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2789,13 +2795,13 @@ msgstr ""
 "Shell 将继续引导过程。"
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -2806,7 +2812,7 @@ msgstr ""
 "<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -2815,19 +2821,19 @@ msgstr ""
 "引导软盘通常会扫描所有的软盘来找到根软盘，可以通过此参数设置只查找一个设备。"
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr "log_host"
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr "log_port"
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -2838,13 +2844,13 @@ msgstr ""
 "定，默认端口是 syslog 标准端口 514。"
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr "lowmem"
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -2855,13 +2861,13 @@ msgstr ""
 "和 2。参阅 <xref linkend=\"lowmem\"/>。"
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr "noshell"
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -2871,13 +2877,13 @@ msgstr ""
 "处。"
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer (fb)"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -2893,13 +2899,13 @@ msgstr ""
 "bogl 的相关错误信息、一个空白的屏幕，或者在开始安装几分钟后停止。"
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "在 hppa 上面报告过存在这些问题。"
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -2916,13 +2922,13 @@ msgstr ""
 "<userinput>fb=true</userinput>。"
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/theme (theme)"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -2937,13 +2943,13 @@ msgstr ""
 "<userinput>theme=<replaceable>dark</replaceable></userinput> 设置。"
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -2955,7 +2961,7 @@ msgstr ""
 "视并且改变其获得的设定。您可以在 DHCP 检测失败的情况下手工配置网络。"
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -2968,13 +2974,13 @@ msgstr ""
 "过 DHCP 配置网络，并手工输入信息。"
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -2984,13 +2990,13 @@ msgstr ""
 "携机会有这种现象。"
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr "disk-detect/dmraid/enable (dmraid)"
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -3004,13 +3010,13 @@ msgstr ""
 "ulink> 找到。"
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url (url)"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -3020,13 +3026,13 @@ msgstr ""
 "install\"/>。"
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file (file)"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -3036,13 +3042,13 @@ msgstr ""
 ">。"
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/interactive"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -3056,13 +3062,13 @@ msgstr ""
 "<xref linkend=\"preseed-seenflag\"/> 了解详细信息。"
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "auto-install/enable (auto)"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -3073,13 +3079,13 @@ msgstr ""
 "auto\"/> 了解自动安装的详细信息。"
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr "finish-install/keep-consoles"
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -3090,13 +3096,13 @@ msgstr ""
 "inittab</filename> 里已经关掉。将其改为 <userinput>true</userinput> 打开。"
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -3112,7 +3118,7 @@ msgstr ""
 "新加载介质。"
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -3123,13 +3129,13 @@ msgstr ""
 "后，不会自动从光盘引导。"
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "base-installer/install-recommends (recommends)"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -3142,7 +3148,7 @@ msgstr ""
 "<xref linkend=\"di-install-base\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3156,13 +3162,13 @@ msgstr ""
 "非常有经验的用户来使用。"
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/allow_unauthenticated"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3175,13 +3181,13 @@ msgstr ""
 "emphasis>"
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3192,13 +3198,13 @@ msgstr ""
 "置。该值的单位是 kB。"
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr "rescue/enable"
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3208,13 +3214,13 @@ msgstr ""
 "<xref linkend=\"rescue\"/>。"
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr "使用内核模块参数回答提问"
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3227,25 +3233,25 @@ msgstr ""
 "bootparms\"/> 找到。下面是一些具体的例子。"
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/language (language)"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/country (country)"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/locale (locale)"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3255,7 +3261,7 @@ msgstr ""
 "和地方(locale)。"
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3273,7 +3279,7 @@ msgstr ""
 "式组合。"
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3288,13 +3294,13 @@ msgstr ""
 "locale=en_GB.UTF-8</userinput>。"
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr "anna/choose_modules (modules)"
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3309,7 +3315,7 @@ msgstr ""
 "classname> (参阅 <xref linkend=\"pppoe\"/>)</phrase>。"
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3318,13 +3324,13 @@ msgstr ""
 "如果您想禁止 DHCP 使用静态网络设置，将它设为 <userinput>true</userinput>。"
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr "mirror/protocol (protocol)"
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3339,13 +3345,13 @@ msgstr ""
 "序使用该协议。注意，必须手动输入主机名，而不是从列表中选择 ftp 镜像。"
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr "tasksel:tasksel/first (tasks)"
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3356,13 +3362,13 @@ msgstr ""
 "literal> 任务。参阅 <xref linkend=\"pkgsel\"/> 了解详细信息。"
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr "给内核模块传递参数"
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3382,7 +3388,7 @@ msgstr ""
 "配置中。"
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3394,7 +3400,7 @@ msgstr ""
 "并很好地设置默认参数。然而，某些情况下还是需要手动设置参数。"
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3414,19 +3420,19 @@ msgstr ""
 "用："
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr "3c509.xcvr=3 3c509.irq=10"
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr "内核模块黑名单"
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3441,7 +3447,7 @@ msgstr ""
 "间冲突或者错误的驱动先加载，将造成设备无法正常工作。"
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3455,7 +3461,7 @@ msgstr ""
 "入 <filename>/etc/modprobe.d/blacklist.local</filename> 文件的黑名单中。"
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3467,19 +3473,19 @@ msgstr ""
 "件检查过程中从显示的模块列表中取消该模块。"
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "安装过程中的故障修复"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "CD-ROM 的可靠性"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3491,7 +3497,7 @@ msgstr ""
 "&mdash; 即使是从 CD-ROM 成功引导 &mdash; 无法识别 CD-ROM 或在安装时读取错误。"
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3502,13 +3508,13 @@ msgstr ""
 "下的由您来处理。"
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr "您首先应试试两种最简单的方法。"
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3516,7 +3522,7 @@ msgid ""
 msgstr "如果 CD-ROM 没有引导，检查一下它是否放好，并且没有弄脏。"
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3534,7 +3540,7 @@ msgstr ""
 "的问题可以用这种方法解决。"
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3545,7 +3551,7 @@ msgstr ""
 "CD-ROM 和 DVD，为了方便，只提到 CD-ROM。"
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3553,13 +3559,13 @@ msgid ""
 msgstr "如果您用 CD-ROM 无法安装，试试其他可用的安装方法。"
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr "常见问题"
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3567,7 +3573,7 @@ msgid ""
 msgstr "有些老 CD-ROM 驱动器不能读取新 CD 刻录机的高速模式下刻录的光盘。"
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some older CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3580,19 +3586,19 @@ msgstr ""
 "常工作。"
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr "如何调查研究或许可以解决问题"
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr "如果从 CD-ROM 引导失败，试试下面所列的建议。"
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Check that your BIOS actually supports booting from CD-ROM (older systems "
@@ -3606,7 +3612,7 @@ msgstr ""
 "持您所使用的介质。"
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3630,7 +3636,7 @@ msgstr ""
 "用下面的命令。它使用映像的尺寸从 CD-ROM 读取正确的字节数。"
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3652,7 +3658,7 @@ msgstr ""
 "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3671,7 +3677,7 @@ msgstr ""
 "shell。"
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3683,7 +3689,7 @@ msgstr ""
 "<command>dmesg</command> 的输出。"
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3711,7 +3717,7 @@ msgstr ""
 "<command>modprobe</command> 手动加载。"
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3723,7 +3729,7 @@ msgstr ""
 "cdrom0</filename>。"
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -3738,7 +3744,7 @@ msgstr ""
 "</screen></informalexample> 检查命令后面是否有什么错误信息。"
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -3763,7 +3769,7 @@ msgstr ""
 "</screen></informalexample> 确保您所处的目录对应 CD-ROM 驱动器。"
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -3775,13 +3781,13 @@ msgstr ""
 "性。如果 CD-ROM 可以读，该选项可以对其进行测试。"
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "软盘的可靠性"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -3790,7 +3796,7 @@ msgstr ""
 "对于用软盘安装 &debian; 的人来说，他们遇到的最大的问题很可能是软盘的可靠性。"
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -3806,7 +3812,7 @@ msgstr ""
 "息。"
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -3821,7 +3827,7 @@ msgstr ""
 "化以后看起来没有错误。如果可能，在别的统上重写这些软盘更好一些。"
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -3832,7 +3838,7 @@ msgstr ""
 "软盘才算工作良好。"
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -3843,7 +3849,7 @@ msgstr ""
 "来检验下载的映像是否正确。"
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -3854,13 +3860,13 @@ msgstr ""
 "有缺陷的硬件或固件软盘驱动器驱动程序造成的。"
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "引导配置"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -3873,7 +3879,7 @@ msgstr ""
 "\"/> 讨论。"
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -3882,7 +3888,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -3897,37 +3903,37 @@ msgstr ""
 "台机器上声音可以正常工作的 Linux 系统上(比如，live CD)，运行下面命令的输出。"
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr "dmesg"
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr "lspci"
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr "lsmod"
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr "amixer"
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "&arch-title; 常见安装问题"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -3935,7 +3941,7 @@ msgid ""
 msgstr "有一些常见的安装问题，可以通过给安装程序特定的引导参数解决或避免。"
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -3953,13 +3959,13 @@ msgstr ""
 "\"boot-parms\"/> 来获得细节信息。"
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "在 PCMCIA 配置阶段系统停止"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -3985,7 +3991,7 @@ msgstr ""
 "段。"
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -4005,19 +4011,19 @@ msgstr ""
 "项。注意您在安装程序中，输入这些值的时候必须忽略逗号。"
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "有一些常见的安装问题值得解释一下。"
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr "错误的视频输出"
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -4041,7 +4047,7 @@ msgstr ""
 "<userinput>video=atyfb:off</userinput> 启动安装程序。"
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -4054,13 +4060,13 @@ msgstr ""
 "xorg.conf</filename> 中的视频驱动。"
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "从 CD-ROM 上引导或安装失败"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -4071,19 +4077,19 @@ msgstr ""
 "费解的错误。SunBlade 系统被报告了很多问题。"
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr "我们建议从网络安装这些系统。"
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "内核起始信息注解"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -4117,13 +4123,13 @@ msgstr ""
 "linkend=\"kernel-baking\"/>)</phrase>。"
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "报告安装问题"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -4140,7 +4146,7 @@ msgstr ""
 "索。如果您正在提交一个 bug 报告，可以报告里附上该信息。"
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -4151,13 +4157,13 @@ msgstr ""
 "新安装的系统启动后，放在 <filename>/var/log/debian-installer/</filename> 里。"
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "提交缺陷报告"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -4169,7 +4175,7 @@ msgstr ""
 "这让我们可以尽可能多地了解硬件的配置数量。"
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -4180,7 +4186,7 @@ msgstr ""
 "件列表。确保您使用的邮件地址可以被公开。"
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -4199,7 +4205,7 @@ msgstr ""
 "command> 命令。"
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/zh_CN/install-methods.po b/po/zh_CN/install-methods.po
index 57bb59c30..f1a53eb81 100644
--- a/po/zh_CN/install-methods.po
+++ b/po/zh_CN/install-methods.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2012-07-25 22:21+0800\n"
 "Last-Translator: Ji YongGang <jungleji@gmail.com>\n"
 "Language-Team: debian-chinese-gb <debian-chinese-gb@lists.debian.org>\n"
@@ -72,15 +72,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -118,7 +117,7 @@ msgstr ""
 "件路径时，请在 CD 中同样的文件目录和子目录下查找它们。"
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -126,7 +125,7 @@ msgid ""
 msgstr "一旦安装程序被引导，它将能够获得 CD 中其他所有必需的文件。"
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -143,13 +142,13 @@ msgstr ""
 "\">一台连网的计算机上</phrase>，然后它们可以被用来引导安装程序。"
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "从 &debian; 镜像服务器下载文件"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -159,7 +158,7 @@ msgstr ""
 "debian-mirrors;\">&debian; 镜像列表</ulink>。"
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, no-c-format
 msgid ""
 "When downloading files from a &debian; mirror using FTP, be sure to download "
@@ -169,13 +168,13 @@ msgstr ""
 "<emphasis>二进制</emphasis>模式，而不是文本或者自动模式。"
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "在哪里能找到安装映像"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -190,13 +189,13 @@ msgstr ""
 "\">MANIFEST</ulink> 文件列出了每一个映像及其用途。"
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "Thecus N2100 安装文件"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -209,13 +208,13 @@ msgstr ""
 "firmware-img; 获得。"
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, no-c-format
 msgid "GLAN Tank Installation Files"
 msgstr "GLAN Tank 安装文件"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -226,13 +225,13 @@ msgstr ""
 "些映象可以从 &glantank-firmware-img; 获得。"
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, no-c-format
 msgid "Kurobox Pro Installation Files"
 msgstr "Kurobox Pro 安装文件"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -243,13 +242,13 @@ msgstr ""
 "这些映象可以从 &kuroboxpro-firmware-img; 获得。"
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "HP mv2120 安装文件"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -264,13 +263,13 @@ msgstr ""
 "映象。"
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, no-c-format
 msgid "QNAP Turbo Station Installation Files"
 msgstr "QNAP Turbo Station 安装文件"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -283,13 +282,13 @@ msgstr ""
 "img; 取得。"
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "Plug Computer 和 OpenRD 安装文件"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -304,14 +303,14 @@ msgstr ""
 "Boot 的内核和 initrd。您可以从 &kirkwood-marvell-firmware-img; 取得这些文件。"
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "GLAN Tank Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "GLAN Tank 安装文件"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The installation files for plug computers (SheevaPlug, GuruPlug, etc) and "
@@ -327,13 +326,13 @@ msgstr ""
 "Boot 的内核和 initrd。您可以从 &kirkwood-marvell-firmware-img; 取得这些文件。"
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "创建一个 IPL 磁带"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -354,13 +353,13 @@ msgstr ""
 "linkend=\"where-files\"/>,"
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "从软盘映像创建引导软盘"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -370,7 +369,7 @@ msgstr ""
 "最后一种方法。"
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -378,7 +377,7 @@ msgid ""
 msgstr "有报告说 Mac 上的 USB 软盘驱动器安装程序软盘引导失败。"
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -396,7 +395,7 @@ msgstr ""
 "按扇区复制</emphasis>到软盘中。"
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -407,7 +406,7 @@ msgstr ""
 "像创建引导软盘。"
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -421,7 +420,7 @@ msgstr ""
 "DVD，软盘映像可能已经包含在 CD/DVD 上面。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -432,13 +431,13 @@ msgstr ""
 "保内容不会在无意被抹掉。"
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "从 Linux 或者 Unix 系统写软盘映像"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -470,7 +469,7 @@ msgstr ""
 "(Solaris 系统中使用 <command>eject</command> 命令，请参见其手册)</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -500,7 +499,7 @@ msgstr ""
 "统，请咨询您的系统管理员)。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -511,13 +510,13 @@ msgstr ""
 "command> 命令能够很好地对此进行控制，当然您可能需要先安装它。"
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "在 DOS、Windows 或者 OS/2 下写磁盘映像"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -526,7 +525,7 @@ msgstr ""
 "如果您能操作一台 i386 或 amd64 机器，可以使用如下方法之一往软盘复制映像文件。"
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -540,7 +539,7 @@ msgstr ""
 "或者在文件浏览器中双击使用这些程序是<emphasis>不能</emphasis>运行的。"
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -551,7 +550,7 @@ msgstr ""
 "可能最新的版本上运行。要使用它您需要解压 diskio.dll 至相同目录下。"
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -561,13 +560,13 @@ msgstr ""
 "下。"
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "在 MacOS 上写磁盘映像"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -587,7 +586,7 @@ msgstr ""
 "您确认的确想要清空磁盘并写入磁盘映像。"
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -600,13 +599,13 @@ msgstr ""
 "您可以使用以下方法之一来利用这些工具将磁盘映像写入软盘。"
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "写磁盘映像：使用<command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -619,7 +618,7 @@ msgstr ""
 "下载映像文件的情况。"
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -629,7 +628,7 @@ msgstr ""
 "且用它打开 <filename>root.bin</filename> 文件。"
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -640,7 +639,7 @@ msgstr ""
 "<userinput>DDim</userinput> (binary floppy image)。注意此处大小写敏感。"
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -655,7 +654,7 @@ msgstr ""
 "会删除引导区。"
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -667,7 +666,7 @@ msgstr ""
 "ulink>。"
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -682,13 +681,13 @@ msgstr ""
 "删除它。完成后它应该会弹出软盘。"
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "写磁盘映像：使用<command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -701,21 +700,21 @@ msgstr ""
 "userinput> 菜单中选择<quote>Overwrite Sectors...</quote>。"
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr "按照要求插入软盘，然后点击 &enterkey; (从0扇区开始)。"
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr "在打开文件对话框中选择 <filename>root.bin</filename> 文件。"
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -728,7 +727,7 @@ msgstr ""
 "换别的软盘试试。"
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -739,13 +738,13 @@ msgstr ""
 "然在 MacOS 中挂载了它，MacOS 将会将其毁坏。"
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "为从 U 盘引导准备文件"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -766,7 +765,7 @@ msgstr ""
 "护开关。"
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -778,13 +777,13 @@ msgstr ""
 "搞错，比如写成硬盘，将造成该设备上的所有信息丢失。"
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr "使用混合 CD 或 DVD 映像制作 U 盘"
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -797,7 +796,7 @@ msgstr ""
 "cdrom\"/> 获取 CD 或 DVD 映像。"
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -810,7 +809,7 @@ msgstr ""
 ">)。"
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -826,7 +825,7 @@ msgstr ""
 "在 U 盘上。您应该挂载第二个分区，并将固件解压到里面。"
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -842,7 +841,7 @@ msgstr ""
 "# umount"
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -855,7 +854,7 @@ msgstr ""
 "U 盘已经卸载："
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -867,7 +866,7 @@ msgstr ""
 "<prompt>#</prompt> <userinput>sync</userinput>"
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -878,13 +877,13 @@ msgstr ""
 "项主要提供给有特殊需要的用户。"
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr "手动复制文件到 U 盘。"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -896,7 +895,7 @@ msgstr ""
 "可以使用较少容量，请参考 <xref linkend=\"usb-copy-flexible\"/>)。"
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -911,7 +910,7 @@ msgstr ""
 "classname> 和对应的配置文件</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -925,19 +924,19 @@ msgstr ""
 "量创建一个新的文件系统。"
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr "使用该映象只须将它直接解压到 U 盘："
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -948,13 +947,13 @@ msgstr ""
 "的 <userinput>C</userinput> 命令，并直接解压映象："
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 #| msgid ""
 #| "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -984,13 +983,13 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>) 就完成了。"
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "手动复制文件到 U 盘 &mdash; 灵活的方法"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, no-c-format
 msgid ""
 "If you like more flexibility or just want to know what's going on, you "
@@ -1003,13 +1002,13 @@ msgstr ""
 "文件放到 U 盘。"
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr "给 U 盘分区"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -1017,7 +1016,7 @@ msgid ""
 msgstr "我们将展示如何使用 U 盘的第一个分区，而不是整个设备。"
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Since most USB sticks come pre-configured with a single FAT16 partition, "
@@ -1057,7 +1056,7 @@ msgstr ""
 "classname> 软件包中。"
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1074,7 +1073,7 @@ msgstr ""
 "用来改变 boot loader 的配置文件。"
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, no-c-format
 msgid ""
 "To put <classname>syslinux</classname> on the FAT16 partition on your USB "
@@ -1097,13 +1096,13 @@ msgstr ""
 "filename> 文件。"
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, no-c-format
 msgid "Adding the installer image"
 msgstr "添加安装程序映像"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /"
@@ -1127,7 +1126,7 @@ msgstr ""
 "(8.3) 文件名。"
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1160,7 +1159,7 @@ msgstr ""
 "userinput> 到第二行尾部。"
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1168,7 +1167,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you used an <filename>hd-media</filename> image, you should now copy "
@@ -1194,7 +1193,7 @@ msgstr ""
 "footnote> 到 U 盘。完成后，卸载 U 盘 (<userinput>umount /mnt</userinput>)。"
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, no-c-format
 msgid ""
 "Most USB sticks do not come pre-configured in such a way that Open Firmware "
@@ -1221,7 +1220,7 @@ msgstr ""
 "command> 命令包含在 &debian; 的 <classname>hfsutils</classname> 软件包中。"
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1236,7 +1235,7 @@ msgstr ""
 "变启动引导器的配置文件。"
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, no-c-format
 msgid ""
 "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1270,7 +1269,7 @@ msgstr ""
 "就可以用普通的 Unix 工具来处理了。"
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, no-c-format
 msgid ""
 "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /"
@@ -1280,31 +1279,31 @@ msgstr ""
 "mnt</userinput>)，然后复制下面的安装程序映象文件到 U 盘："
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (内核二进制文件)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (初始化内存映像)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yaboot 配置文件)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (可选的启动信息)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1340,13 +1339,13 @@ msgstr ""
 "的大小。"
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "为从硬盘引导准备文件"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1357,7 +1356,7 @@ msgstr ""
 "者直接使用 BIOS 提供的引导装载程序直接启动。"
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1370,7 +1369,7 @@ msgstr ""
 "缠不清。"
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1390,7 +1389,7 @@ msgstr ""
 "Linux 之间交换文件，特别是那些您下载的安装文件。"
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1401,7 +1400,7 @@ msgstr ""
 "装程序的引导将使用不同的安装文件。"
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1410,7 +1409,7 @@ msgstr ""
 "硬盘安装程序引导使用 <command>LILO</command> 或 <command>GRUB</command>"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1420,7 +1419,7 @@ msgstr ""
 "command> 或 <command>GRUB</command>。"
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1431,7 +1430,7 @@ msgstr ""
 "盘可以被用做内核的根文件系统。"
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, no-c-format
 msgid ""
 "Copy the following files from the &debian; archives to a convenient location "
@@ -1442,19 +1441,19 @@ msgstr ""
 "newinstall/</filename>。"
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename>(内核二进制文件)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (内存虚拟磁盘映像)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1462,13 +1461,13 @@ msgid ""
 msgstr "最后，要配置 bootloader，请进入 <xref linkend=\"boot-initrd\"/>。"
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr "硬盘安装程序引导使用 <command>loadlin</command>"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, no-c-format
 msgid ""
 "This section explains how to prepare your hard drive for booting the "
@@ -1477,7 +1476,7 @@ msgstr ""
 "本节将说明如何用 <command>loadlin</command> 从 DOS 启动安装程序准备您的硬盘。"
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, no-c-format
 msgid ""
 "Copy the following directories from a &debian; CD image to <filename>c:\\</"
@@ -1485,26 +1484,26 @@ msgid ""
 msgstr "从 &debian; CD 映象复制下列目录到 <filename>c:\\</filename>。"
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, no-c-format
 msgid ""
 "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr "<filename>/&x86-install-dir;</filename> (二进制和 ramdisk 映象)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>/tools</filename> (loadlin 工具)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "在 OldWorld Macs 上引导硬盘安装程序"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1526,7 +1525,7 @@ msgstr ""
 "是必须的。"
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1553,13 +1552,13 @@ msgstr ""
 "的系统文件夹中。"
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "在 NewWorld Macs 上启动硬盘安装程序"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1577,7 +1576,7 @@ msgstr ""
 "不能用在 NewWorld PowerMacs 上。"
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1590,31 +1589,31 @@ msgstr ""
 "硬盘图标的方法来完成)。"
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1628,19 +1627,19 @@ msgstr ""
 "的时候，您需要这个分区号码在 Open Firmware 提示符下面输入命令。"
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr "要引导安装程序，请进入 <xref linkend=\"boot-newworld\"/>。"
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "为使用 TFTP 网络引导准备文件"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1654,7 +1653,7 @@ msgstr ""
 "上面的某个特殊地方，并且配置好能够能够支持对您的机器进行引导。"
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1666,7 +1665,7 @@ msgstr ""
 "condition=\"supports-bootp\">，或 BOOTP 服务器</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1685,7 +1684,7 @@ msgstr ""
 "些系统只能通过 DHCP 来配置。"
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1696,7 +1695,7 @@ msgstr ""
 "替 BOOTP 比较好。有些最新的机器不能从 BOOTP 引导。"
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1706,7 +1705,7 @@ msgstr ""
 "个 <classname>rbootd</classname> 软件包。"
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1720,7 +1719,7 @@ msgstr ""
 "Linux 上面的一些操作例子。"
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1733,13 +1732,13 @@ msgstr ""
 "多问题。另一个好的选择是 <classname>atftpd</classname>。"
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "设置 RARP 服务器"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1757,7 +1756,7 @@ msgstr ""
 "addr show dev eth0</userinput> 命令。"
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1780,13 +1779,13 @@ msgstr ""
 "<userinput>/usr/etc/rarpd -a</userinput> 命令。"
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "设置 DHCP 服务器"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1799,7 +1798,7 @@ msgstr ""
 "示例文件(参阅 <filename>/etc/dhcp3/dhcpd.conf</filename>)："
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1843,7 +1842,7 @@ msgstr ""
 "}"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1859,7 +1858,7 @@ msgstr ""
 "TFTP 获取的文件名。"
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1869,13 +1868,13 @@ msgstr ""
 "<userinput>/etc/init.d/dhcp3-server restart</userinput>。"
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "在 DHCP 配置中打开 PXE 引导功能"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -1945,13 +1944,13 @@ msgstr ""
 "的 <xref linkend=\"tftp-images\"/>)。"
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "架设 BOOTP 服务器"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -1966,7 +1965,7 @@ msgstr ""
 "<classname>dhcp3-server</classname> 软件包。"
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2028,7 +2027,7 @@ msgstr ""
 "MAC 地址。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2050,13 +2049,13 @@ msgstr ""
 "<command>dhcpd</command>。"
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "开启 TFTP 服务器"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2065,7 +2064,7 @@ msgstr ""
 "要准备好 TFTP 服务器，您首先需要确定 <command>tftpd</command> 已经启动。"
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2079,7 +2078,7 @@ msgstr ""
 "以在安装软件包的时候选择，也可以用重新配置软件包方式修改。"
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2096,7 +2095,7 @@ msgstr ""
 "置文件示例。"
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2110,7 +2109,7 @@ msgstr ""
 "问题，建议先检查这些日志信息，这对于分析错误是一个好的起始点。"
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2138,13 +2137,13 @@ msgstr ""
 "错误。"
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "将 TFTP 映像放到适当的位置"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2159,7 +2158,7 @@ msgstr ""
 "完全决定于 TFTP 客户程序，而且没有一个强制的标准。"
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, no-c-format
 msgid ""
 "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2174,13 +2173,13 @@ msgstr ""
 "件："
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr "boot.msg"
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2195,7 +2194,7 @@ msgstr ""
 "需的文件名传递给 <command>tftpd</command>。"
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2210,13 +2209,13 @@ msgstr ""
 "efi</filename> 以启动所需的文件名传递至<command>tftpd</command>。"
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "SPARC TFTP 引导"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2244,7 +2243,7 @@ msgstr ""
 "并在必要时加上子体系名。"
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2256,7 +2255,7 @@ msgstr ""
 "映像。假如映像找不到，查看 tftp 服务器的日志所需要的映像文件名。"
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2269,13 +2268,13 @@ msgstr ""
 "仍然必须被请放置在 TFTP 服务器要查找的目录中。"
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI TFTP 引导"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2289,13 +2288,13 @@ msgstr ""
 "现在 <filename>/etc/dhcpd.conf</filename>。"
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "自动化安装"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, no-c-format
 msgid ""
 "For installing on multiple computers it's possible to do fully automatic "
@@ -2310,13 +2309,13 @@ msgstr ""
 "更多细节。"
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "使用 &debian; 安装程序进行自动安装"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2328,7 +2327,7 @@ msgstr ""
 "介质上加载，并自动回答安装过程中的问题。"
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/zh_TW/boot-installer.po b/po/zh_TW/boot-installer.po
index ea0d0e8c5..b28851eea 100644
--- a/po/zh_TW/boot-installer.po
+++ b/po/zh_TW/boot-installer.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2005-07-18 14:56+0800\n"
 "Last-Translator: Jhang, Jia-Wei<dreamcryer@gmail.com>\n"
 "Language-Team: debian-chinese-big5 <debian-chinese-big5@lists.debian.org>\n"
@@ -52,8 +52,8 @@ msgstr "從 TFTP 開機"
 
 # index.docbook:432, index.docbook:786, index.docbook:1338, index.docbook:1819, index.docbook:2242, index.docbook:2338
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125
-#: boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127
+#: boot-installer.xml:1628 boot-installer.xml:1737
 #, no-c-format
 msgid ""
 "Booting from the network requires that you have a network connection and a "
@@ -64,8 +64,8 @@ msgstr ""
 
 # index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1130
-#: boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132
+#: boot-installer.xml:1633 boot-installer.xml:1742
 #, no-c-format
 msgid ""
 "Older systems such as the 715 might require the use of an RBOOT server "
@@ -74,8 +74,8 @@ msgstr "較早的系統如 715 也許需要使用一台 RBOOT 伺服器來取代
 
 # index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1135
-#: boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137
+#: boot-installer.xml:1638 boot-installer.xml:1747
 #, no-c-format
 msgid ""
 "The installation method to support network booting is described in <xref "
@@ -90,8 +90,8 @@ msgstr "從光碟開機"
 
 # index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744
-#: boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746
+#: boot-installer.xml:1404 boot-installer.xml:1776
 #, fuzzy, no-c-format
 msgid ""
 "The easiest route for most people will be to use a set of &debian; CDs. If "
@@ -107,8 +107,8 @@ msgstr ""
 
 # index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:755
-#: boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757
+#: boot-installer.xml:1415 boot-installer.xml:1787
 #, no-c-format
 msgid ""
 "Note that certain CD drives may require special drivers, and thus be "
@@ -123,8 +123,8 @@ msgstr ""
 
 # index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:763
-#: boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765
+#: boot-installer.xml:1423 boot-installer.xml:1795
 #, no-c-format
 msgid ""
 "Even if you cannot boot from CD-ROM, you can probably install the &debian; "
@@ -139,8 +139,8 @@ msgstr ""
 
 # index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:771
-#: boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773
+#: boot-installer.xml:1431 boot-installer.xml:1803
 #, no-c-format
 msgid ""
 "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -320,8 +320,8 @@ msgstr ""
 
 # index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396
-#: boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398
+#: boot-installer.xml:1770
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr "從光碟開機"
@@ -345,14 +345,16 @@ msgstr ""
 #| "To boot the installer from hard disk, you must first download and place "
 #| "the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgid ""
-"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in "
-"<xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or"
+"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
+"stick</phrase> installation media as described in <xref linkend=\"official-"
+"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
+"usb-files\"/></phrase> or"
 msgstr ""
 "為了從硬碟開機安裝程式，您首先必須按照要求下載並且放置所需的文件，請參閱 "
 "<xref linkend=\"boot-drive-files\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:361
+#: boot-installer.xml:363
 #, no-c-format
 msgid ""
 "download a standalone Windows executable, which is available as tools/win32-"
@@ -360,7 +362,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:369
+#: boot-installer.xml:371
 #, no-c-format
 msgid ""
 "If you use an installation CD or DVD, a pre-installation program should be "
@@ -371,7 +373,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:377
+#: boot-installer.xml:379
 #, no-c-format
 msgid ""
 "After the program has been started, a few preliminary questions will be "
@@ -380,14 +382,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:387
+#: boot-installer.xml:389
 #, fuzzy, no-c-format
 #| msgid "Booting from MacOS"
 msgid "Booting from DOS"
 msgstr "從 MacOS 開機"
 
 #. Tag: para
-#: boot-installer.xml:388
+#: boot-installer.xml:390
 #, no-c-format
 msgid ""
 "Boot into DOS (not Windows). To do this, you can for instance boot from a "
@@ -395,7 +397,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:393
+#: boot-installer.xml:395
 #, no-c-format
 msgid ""
 "If you can access the installation CD, change the current drive to the CD-"
@@ -407,7 +409,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:403
+#: boot-installer.xml:405
 #, no-c-format
 msgid ""
 "Enter the subdirectory for the flavor you chose, e.g., "
@@ -421,14 +423,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:421
+#: boot-installer.xml:423
 #, no-c-format
 msgid ""
 "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>"
 msgstr "使用 <command>LILO</command> 或 <command>GRUB</command> 啟動 Linux"
 
 #. Tag: para
-#: boot-installer.xml:424
+#: boot-installer.xml:426
 #, no-c-format
 msgid ""
 "To boot the installer from hard disk, you must first download and place the "
@@ -438,7 +440,7 @@ msgstr ""
 "<xref linkend=\"boot-drive-files\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:429
+#: boot-installer.xml:431
 #, fuzzy, no-c-format
 msgid ""
 "If you intend to use the hard drive only for booting and then download "
@@ -453,7 +455,7 @@ msgstr ""
 "您用於開機的硬碟。這裡需要小心操作。"
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:441
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Alternatively, if you intend to keep an existing partition on the hard "
@@ -476,7 +478,7 @@ msgstr ""
 "像檔上安裝。"
 
 #. Tag: para
-#: boot-installer.xml:448
+#: boot-installer.xml:450
 #, no-c-format
 msgid ""
 "For <command>LILO</command>, you will need to configure two essential things "
@@ -494,7 +496,7 @@ msgstr ""
 "lilo.conf</filename> 的例子："
 
 #. Tag: screen
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, fuzzy, no-c-format
 msgid ""
 "image=/boot/newinstall/vmlinuz\n"
@@ -509,7 +511,7 @@ msgstr ""
 "phrase>ramdisk_size=12000\""
 
 #. Tag: para
-#: boot-installer.xml:469
+#: boot-installer.xml:471
 #, no-c-format
 msgid ""
 "For more details, refer to the <citerefentry><refentrytitle>initrd</"
@@ -524,7 +526,7 @@ msgstr ""
 "行 <userinput>lilo</userinput> 並且重新啟動。"
 
 #. Tag: para
-#: boot-installer.xml:478
+#: boot-installer.xml:480
 #, fuzzy, no-c-format
 msgid ""
 "The procedure for <command>GRUB1</command> is quite similar. Locate your "
@@ -544,7 +546,7 @@ msgstr ""
 "userinput>。</phrase>"
 
 #. Tag: screen
-#: boot-installer.xml:486
+#: boot-installer.xml:488
 #, fuzzy, no-c-format
 msgid ""
 "title  New Install\n"
@@ -560,7 +562,7 @@ msgstr ""
 "phrase>ramdisk_size=12000\""
 
 #. Tag: para
-#: boot-installer.xml:488
+#: boot-installer.xml:490
 #, fuzzy, no-c-format
 msgid ""
 "The procedure for <command>GRUB2</command> is very similar. The file is "
@@ -578,7 +580,7 @@ msgstr ""
 "userinput>。</phrase>"
 
 #. Tag: screen
-#: boot-installer.xml:494
+#: boot-installer.xml:496
 #, fuzzy, no-c-format
 msgid ""
 "menuentry 'New Install' {\n"
@@ -597,7 +599,7 @@ msgstr ""
 "phrase>ramdisk_size=12000\""
 
 #. Tag: para
-#: boot-installer.xml:496
+#: boot-installer.xml:498
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Note that the value of the <userinput>ramdisk_size</userinput> may need "
@@ -614,13 +616,13 @@ msgstr ""
 
 # index.docbook:700, index.docbook:2176
 #. Tag: title
-#: boot-installer.xml:505
+#: boot-installer.xml:507
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr "從 USB 隨身碟開機"
 
 #. Tag: para
-#: boot-installer.xml:506
+#: boot-installer.xml:508
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
@@ -644,14 +646,14 @@ msgstr ""
 
 # index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426
 #. Tag: title
-#: boot-installer.xml:520 boot-installer.xml:1675
+#: boot-installer.xml:522 boot-installer.xml:1677
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr "從軟碟開機"
 
 # index.docbook:724, index.docbook:2286
 #. Tag: para
-#: boot-installer.xml:521 boot-installer.xml:1683
+#: boot-installer.xml:523 boot-installer.xml:1685
 #, no-c-format
 msgid ""
 "You will have already downloaded the floppy images you needed and created "
@@ -661,7 +663,7 @@ msgstr ""
 "\"create-floppy\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:528
+#: boot-installer.xml:530
 #, no-c-format
 msgid ""
 "To boot from the installer boot floppy, place it in the primary floppy "
@@ -671,7 +673,7 @@ msgstr ""
 "啟動。"
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:536
 #, fuzzy, no-c-format
 msgid ""
 "For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
@@ -688,7 +690,7 @@ msgstr ""
 "userinput>。從 LS-120 上安裝只為 2.4 及其以後版本的核心支援。"
 
 #. Tag: para
-#: boot-installer.xml:544
+#: boot-installer.xml:546
 #, no-c-format
 msgid ""
 "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
@@ -703,7 +705,7 @@ msgstr ""
 "否則，請用硬重開機的方法來開機。"
 
 #. Tag: para
-#: boot-installer.xml:553
+#: boot-installer.xml:555
 #, no-c-format
 msgid ""
 "The floppy disk will be accessed, and you should then see a screen that "
@@ -713,7 +715,7 @@ msgstr ""
 "</prompt> 提示符號。"
 
 #. Tag: para
-#: boot-installer.xml:559
+#: boot-installer.xml:561
 #, no-c-format
 msgid ""
 "Once you press &enterkey;, you should see the message "
@@ -729,7 +731,7 @@ msgstr ""
 "資訊，請參考 <xref linkend=\"kernel-msgs\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:568
+#: boot-installer.xml:570
 #, no-c-format
 msgid ""
 "After booting from the boot floppy, the root floppy is requested. Insert the "
@@ -742,26 +744,26 @@ msgstr ""
 
 # index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332
 #. Tag: title
-#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248
-#: boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250
+#: boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr "用 TFTP 開機"
 
 #. Tag: para
-#: boot-installer.xml:602
+#: boot-installer.xml:604
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr "在 i386 架構上有很多方法用 TFTP 進行開機。"
 
 #. Tag: title
-#: boot-installer.xml:608
+#: boot-installer.xml:610
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr "支援 PXE 的網卡或者主機板"
 
 #. Tag: para
-#: boot-installer.xml:609
+#: boot-installer.xml:611
 #, fuzzy, no-c-format
 msgid ""
 "It could be that your Network Interface Card or Motherboard provides PXE "
@@ -774,13 +776,13 @@ msgstr ""
 "BIOS 來用網路進行開機。"
 
 #. Tag: title
-#: boot-installer.xml:620
+#: boot-installer.xml:622
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr "採用 Network BootROM 的網卡"
 
 #. Tag: para
-#: boot-installer.xml:621
+#: boot-installer.xml:623
 #, no-c-format
 msgid ""
 "It could be that your Network Interface Card provides TFTP boot "
@@ -788,7 +790,7 @@ msgid ""
 msgstr "您的網卡很有可能提供了 TFTP 開機功能。"
 
 #. Tag: para
-#: boot-installer.xml:626
+#: boot-installer.xml:628
 #, no-c-format
 msgid ""
 "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
@@ -798,13 +800,13 @@ msgstr ""
 "件。"
 
 #. Tag: title
-#: boot-installer.xml:634
+#: boot-installer.xml:636
 #, no-c-format
 msgid "Etherboot"
 msgstr "Etherboot"
 
 #. Tag: para
-#: boot-installer.xml:635
+#: boot-installer.xml:637
 #, no-c-format
 msgid ""
 "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
@@ -815,14 +817,14 @@ msgstr ""
 
 # index.docbook:1943, index.docbook:2477
 #. Tag: title
-#: boot-installer.xml:645
+#: boot-installer.xml:647
 #, fuzzy, no-c-format
 #| msgid "The Boot Prompt"
 msgid "The Boot Screen"
 msgstr "開機提示"
 
 #. Tag: para
-#: boot-installer.xml:646
+#: boot-installer.xml:648
 #, fuzzy, no-c-format
 #| msgid ""
 #| "When the installer boots, you should be presented with a friendly "
@@ -856,7 +858,7 @@ msgstr ""
 "項啟動安裝程式，或者輸入參數以指定您要使用的啟動方式。"
 
 #. Tag: para
-#: boot-installer.xml:658
+#: boot-installer.xml:660
 #, no-c-format
 msgid ""
 "For a normal installation, select either the <quote>Install</quote> or the "
@@ -867,7 +869,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:666
+#: boot-installer.xml:668
 #, no-c-format
 msgid ""
 "The <quote>Advanced options</quote> entry gives access to a second menu that "
@@ -876,7 +878,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:672
+#: boot-installer.xml:674
 #, no-c-format
 msgid ""
 "If you wish or need to add any boot parameters for either the installer or "
@@ -888,7 +890,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:681
+#: boot-installer.xml:683
 #, no-c-format
 msgid ""
 "Choosing the <quote>Help</quote> entry will result in the first help screen "
@@ -907,7 +909,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:701
 #, no-c-format
 msgid ""
 "The keyboard is assumed to have a default American English layout at this "
@@ -919,7 +921,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:711
 #, no-c-format
 msgid ""
 "If you are using a system that has the BIOS configured to use serial "
@@ -932,7 +934,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:721
 #, no-c-format
 msgid ""
 "To bypass the graphical boot screen you can either blindly press &escapekey; "
@@ -945,13 +947,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:781
 #, no-c-format
 msgid "CD Contents"
 msgstr "光碟的內容"
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:783
 #, no-c-format
 msgid ""
 "There are three basic variations of &debian; Install CDs. The "
@@ -972,7 +974,7 @@ msgstr ""
 "裝一個具有各種範圍軟體套件的完全系統。"
 
 #. Tag: para
-#: boot-installer.xml:797
+#: boot-installer.xml:799
 #, no-c-format
 msgid ""
 "The IA-64 architecture uses the next generation Extensible Firmware "
@@ -995,7 +997,7 @@ msgstr ""
 "者開機塊記錄。"
 
 #. Tag: para
-#: boot-installer.xml:813
+#: boot-installer.xml:815
 #, no-c-format
 msgid ""
 "The &debian; Installer CD contains a small EFI partition where the "
@@ -1010,7 +1012,7 @@ msgstr ""
 "出，描述如下。"
 
 #. Tag: para
-#: boot-installer.xml:822
+#: boot-installer.xml:824
 #, no-c-format
 msgid ""
 "Most of the details of how <command>ELILO</command> actually loads and "
@@ -1029,7 +1031,7 @@ msgstr ""
 "分割步驟也會在繼續安裝步驟前檢查 EFI 分割區是否合適。"
 
 #. Tag: para
-#: boot-installer.xml:834
+#: boot-installer.xml:836
 #, no-c-format
 msgid ""
 "The EFI Boot Manager is presented as the last step of the firmware "
@@ -1049,13 +1051,13 @@ msgstr ""
 "用第一個，當然，若該選項不可用或者 CD 由於某種原因沒法啟動，使用第二個。"
 
 #. Tag: title
-#: boot-installer.xml:853
+#: boot-installer.xml:855
 #, no-c-format
 msgid "IMPORTANT"
 msgstr "重要"
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:856
 #, no-c-format
 msgid ""
 "The EFI Boot Manager will select a default boot action, typically the first "
@@ -1072,13 +1074,13 @@ msgstr ""
 "command> 以返回 Boot Manager。"
 
 #. Tag: title
-#: boot-installer.xml:866
+#: boot-installer.xml:868
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr "選項 1: 從 Boot Option Maintenance Menu 啟動"
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:875
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1089,7 +1091,7 @@ msgstr ""
 "Boot Manager 頁面和選單。"
 
 #. Tag: para
-#: boot-installer.xml:879
+#: boot-installer.xml:881
 #, no-c-format
 msgid ""
 "Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
@@ -1099,7 +1101,7 @@ msgstr ""
 "<command>ENTER</command>。會顯示一個新選單。"
 
 #. Tag: para
-#: boot-installer.xml:885
+#: boot-installer.xml:887
 #, no-c-format
 msgid ""
 "Select <command>Boot From a File</command> from the menu with the arrow keys "
@@ -1115,7 +1117,7 @@ msgstr ""
 "command>標籤。如果您檢查選單行其他部分，會看到對應的設備和控制器資訊。"
 
 #. Tag: para
-#: boot-installer.xml:896
+#: boot-installer.xml:898
 #, no-c-format
 msgid ""
 "You can choose either of the entries that refer to the CD/DVD drive. Select "
@@ -1131,7 +1133,7 @@ msgstr ""
 "光碟目錄列表，要求您進行 (額外的) 下一步。"
 
 #. Tag: para
-#: boot-installer.xml:907
+#: boot-installer.xml:909
 #, no-c-format
 msgid ""
 "You will only need this step if you chose <command>Debian Inst [Acpi ...</"
@@ -1145,7 +1147,7 @@ msgstr ""
 "鍵選擇，並按下 <command>ENTER</command>。這將進入啟動步驟。"
 
 #. Tag: para
-#: boot-installer.xml:919
+#: boot-installer.xml:921
 #, no-c-format
 msgid ""
 "These steps start the &debian; boot loader which will display a menu page "
@@ -1156,13 +1158,13 @@ msgstr ""
 "入選擇啟動核心和選項。"
 
 #. Tag: title
-#: boot-installer.xml:929
+#: boot-installer.xml:931
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr "選項 2: 從 EFI Shell 啟動"
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:932
 #, no-c-format
 msgid ""
 "If, for some reason, option 1 is not successful, reboot the machine and when "
@@ -1175,7 +1177,7 @@ msgstr ""
 "來啟動 &debian; 安裝程式："
 
 #. Tag: para
-#: boot-installer.xml:941
+#: boot-installer.xml:943
 #, no-c-format
 msgid ""
 "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
@@ -1186,7 +1188,7 @@ msgstr ""
 "頁和選單。"
 
 #. Tag: para
-#: boot-installer.xml:947
+#: boot-installer.xml:949
 #, no-c-format
 msgid ""
 "Select <command>EFI Shell</command> from the menu with the arrow keys and "
@@ -1206,7 +1208,7 @@ msgstr ""
 "插入光碟，這將花費一些時間以初始化光碟機。"
 
 #. Tag: para
-#: boot-installer.xml:961
+#: boot-installer.xml:963
 #, no-c-format
 msgid ""
 "Examine the output from the shell looking for the CDROM drive. It is most "
@@ -1219,7 +1221,7 @@ msgstr ""
 "replaceable></filename>。"
 
 #. Tag: para
-#: boot-installer.xml:968
+#: boot-installer.xml:970
 #, no-c-format
 msgid ""
 "Enter <command>fs<replaceable>n</replaceable>:</command> and press "
@@ -1232,7 +1234,7 @@ msgstr ""
 "的分割區號。介殼將在提示符號下顯示分割區號。"
 
 #. Tag: para
-#: boot-installer.xml:975
+#: boot-installer.xml:977
 #, no-c-format
 msgid ""
 "Enter <command>elilo</command> and press <command>ENTER</command>. This will "
@@ -1242,7 +1244,7 @@ msgstr ""
 "驟。"
 
 #. Tag: para
-#: boot-installer.xml:982
+#: boot-installer.xml:984
 #, no-c-format
 msgid ""
 "As with option 1, these steps start the &debian; boot loader which will "
@@ -1256,13 +1258,13 @@ msgstr ""
 "replaceable>:elilo</command>簡短指令。進入選擇啟動核心和選項。"
 
 #. Tag: title
-#: boot-installer.xml:996
+#: boot-installer.xml:998
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr "使用序列埠控制台安裝"
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:1000
 #, no-c-format
 msgid ""
 "You may choose to perform an install using a monitor and keyboard or using a "
@@ -1279,7 +1281,7 @@ msgstr ""
 "replaceable> 是序列連接速度。選單項裡有大多數常見鮑率的 ttyS0 設備都有預設。"
 
 #. Tag: para
-#: boot-installer.xml:1009
+#: boot-installer.xml:1011
 #, no-c-format
 msgid ""
 "In most circumstances, you will want the installer to use the same baud rate "
@@ -1291,7 +1293,7 @@ msgstr ""
 "可以在 EFI shell 透過 <command>baud</command> 指令取得。"
 
 #. Tag: para
-#: boot-installer.xml:1016
+#: boot-installer.xml:1018
 #, no-c-format
 msgid ""
 "If there is not an option available that is configured for the serial device "
@@ -1305,7 +1307,7 @@ msgstr ""
 "command> 到 <classname>Boot:</classname> 文字視窗。"
 
 #. Tag: para
-#: boot-installer.xml:1027
+#: boot-installer.xml:1029
 #, no-c-format
 msgid ""
 "Most IA-64 boxes ship with a default console setting of 9600 baud. This "
@@ -1321,7 +1323,7 @@ msgstr ""
 "導。"
 
 #. Tag: para
-#: boot-installer.xml:1036
+#: boot-installer.xml:1038
 #, no-c-format
 msgid ""
 "If you select the wrong console type, you will be able to select the kernel "
@@ -1333,13 +1335,13 @@ msgstr ""
 "核啟動後死掉，只有重新啟動才能開始安裝。"
 
 #. Tag: title
-#: boot-installer.xml:1045
+#: boot-installer.xml:1047
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr "選擇啟動核心與選項"
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1049
 #, no-c-format
 msgid ""
 "The boot loader will display a form with a menu list and a text window with "
@@ -1356,7 +1358,7 @@ msgstr ""
 "<classname>Params</classname>視窗解釋命令列參數。"
 
 #. Tag: para
-#: boot-installer.xml:1059
+#: boot-installer.xml:1061
 #, no-c-format
 msgid ""
 "Consult the <classname>General</classname> help screen for the description "
@@ -1376,7 +1378,7 @@ msgstr ""
 "始安裝："
 
 #. Tag: para
-#: boot-installer.xml:1077
+#: boot-installer.xml:1079
 #, no-c-format
 msgid ""
 "Select the kernel version and installation mode most appropriate to your "
@@ -1384,7 +1386,7 @@ msgid ""
 msgstr "使用方向鍵選擇您需要的核心版本和適合的安裝模式。"
 
 #. Tag: para
-#: boot-installer.xml:1082
+#: boot-installer.xml:1084
 #, no-c-format
 msgid ""
 "Enter any boot parameters by typing at the keyboard. The text will be "
@@ -1395,7 +1397,7 @@ msgstr ""
 "列控制台) 指定的。"
 
 #. Tag: para
-#: boot-installer.xml:1089
+#: boot-installer.xml:1091
 #, no-c-format
 msgid ""
 "Press <command>ENTER</command>. This will load and start the kernel. The "
@@ -1406,7 +1408,7 @@ msgstr ""
 "一個螢幕顯示常規的初始化資訊。"
 
 #. Tag: para
-#: boot-installer.xml:1098 boot-installer.xml:1234
+#: boot-installer.xml:1100 boot-installer.xml:1236
 #, no-c-format
 msgid ""
 "Proceed to the next chapter to continue the installation where you will set "
@@ -1414,7 +1416,7 @@ msgid ""
 msgstr "進入到下一章繼續安裝本地語言，網路和磁碟分割區。"
 
 #. Tag: para
-#: boot-installer.xml:1109
+#: boot-installer.xml:1111
 #, fuzzy, no-c-format
 msgid ""
 "Booting an IA-64 system from the network is similar to a CD boot. The only "
@@ -1430,7 +1432,7 @@ msgstr ""
 "統的安裝將和光碟安裝步驟相同，只是基本軟體套件將從網路裝入而不是光碟機。"
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1145
 #, fuzzy, no-c-format
 msgid ""
 "Network booting an IA-64 system requires two architecture-specific actions. "
@@ -1443,13 +1445,13 @@ msgstr ""
 "Manager 定義新的開機選項來啟動網路網路以下載核心。"
 
 #. Tag: title
-#: boot-installer.xml:1154
+#: boot-installer.xml:1156
 #, no-c-format
 msgid "Configuring the Server"
 msgstr "配置網路伺服器"
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1157
 #, fuzzy, no-c-format
 msgid ""
 "A suitable TFTP entry for network booting an IA-64 system looks something "
@@ -1473,7 +1475,7 @@ msgstr ""
 "戶端運行。"
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1167
 #, no-c-format
 msgid ""
 "Extract the <filename>netboot.tar.gz</filename> file into the directory used "
@@ -1488,7 +1490,7 @@ msgstr ""
 "它包括 IA-64 系統需要的開機檔案。"
 
 #. Tag: screen
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "# cd /var/lib/tftp\n"
@@ -1506,7 +1508,7 @@ msgstr ""
 "[...]"
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1177
 #, no-c-format
 msgid ""
 "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
@@ -1526,13 +1528,13 @@ msgstr ""
 "細節。"
 
 #. Tag: title
-#: boot-installer.xml:1192
+#: boot-installer.xml:1194
 #, no-c-format
 msgid "Configuring the Client"
 msgstr "配置客戶端"
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1195
 #, no-c-format
 msgid ""
 "To configure the client to support TFTP booting, start by booting to EFI and "
@@ -1560,7 +1562,7 @@ msgstr ""
 "filename>。"
 
 #. Tag: para
-#: boot-installer.xml:1225
+#: boot-installer.xml:1227
 #, no-c-format
 msgid ""
 "The boot loader will display its prompt after it has downloaded and "
@@ -1575,13 +1577,13 @@ msgstr ""
 
 # index.docbook:1899, index.docbook:1946
 #. Tag: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1253 boot-installer.xml:1277
 #, fuzzy, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI Indy 透過 TFTP 開機"
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1254
 #, fuzzy, no-c-format
 msgid ""
 "After entering the command monitor use <informalexample><screen>\n"
@@ -1603,13 +1605,13 @@ msgstr ""
 
 # index.docbook:1943, index.docbook:2477
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975
 #, no-c-format
 msgid "Boot Parameters"
 msgstr "開機參數"
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1278
 #, fuzzy, no-c-format
 msgid ""
 "On SGI machines you can append boot parameters to the <command>bootp():</"
@@ -1619,7 +1621,7 @@ msgstr ""
 "機參數。"
 
 #. Tag: para
-#: boot-installer.xml:1281
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
 "Following the <command>bootp():</command> command you can give the path and "
@@ -1637,20 +1639,20 @@ msgstr ""
 "command>:"
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1293
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr "bootp(): append=\"root=/dev/sda1\""
 
 # index.docbook:1899, index.docbook:1946
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1307 boot-installer.xml:1344
 #, fuzzy, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr "SGI Indy 透過 TFTP 開機"
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1308
 #, no-c-format
 msgid ""
 "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to "
@@ -1662,7 +1664,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1316
+#: boot-installer.xml:1318
 #, no-c-format
 msgid ""
 "Via SSH (default): In this case, the installer will configure the network "
@@ -1673,7 +1675,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1325
+#: boot-installer.xml:1327
 #, no-c-format
 msgid ""
 "Via serial console: Using a null modem cable, you can connect to the serial "
@@ -1682,7 +1684,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1345
 #, fuzzy, no-c-format
 msgid ""
 "You cannot pass any boot parameters directly. Instead, you have to edit the "
@@ -1694,13 +1696,13 @@ msgstr ""
 "replaceable> 變數。"
 
 #. Tag: title
-#: boot-installer.xml:1358
+#: boot-installer.xml:1360
 #, no-c-format
 msgid "s390 Limitations"
 msgstr "s390 的限制"
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1361
 #, no-c-format
 msgid ""
 "In order to run the installation system a working network setup and ssh "
@@ -1708,7 +1710,7 @@ msgid ""
 msgstr "為了在 S/390 上安裝系統，需要網路來和 ssh 連線。"
 
 #. Tag: para
-#: boot-installer.xml:1364
+#: boot-installer.xml:1366
 #, no-c-format
 msgid ""
 "The booting process starts with a network setup that prompts you for several "
@@ -1720,13 +1722,13 @@ msgstr ""
 "線登錄進入系統，並且開始標準系統安裝。"
 
 #. Tag: title
-#: boot-installer.xml:1375
+#: boot-installer.xml:1377
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr "s390 開機參數"
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1378
 #, fuzzy, no-c-format
 msgid ""
 "On S/390 you can append boot parameters in the parm file. This file can "
@@ -1738,7 +1740,7 @@ msgstr ""
 "令</ulink> 來取得更多有關 S/390 特定的開機參數。"
 
 #. Tag: para
-#: boot-installer.xml:1436
+#: boot-installer.xml:1438
 #, fuzzy, no-c-format
 msgid ""
 "Currently, the only &arch-title; subarchitectures that support CD-ROM "
@@ -1754,7 +1756,7 @@ msgstr ""
 "和 <keycap>Delete</keycap> 。"
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1447
 #, no-c-format
 msgid ""
 "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
@@ -1766,13 +1768,13 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1458
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr "0 &gt; boot cd:,\\install\\yaboot"
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1460
 #, no-c-format
 msgid ""
 "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
@@ -1787,7 +1789,7 @@ msgstr ""
 "上選擇所需要的文件。"
 
 #. Tag: para
-#: boot-installer.xml:1467
+#: boot-installer.xml:1469
 #, no-c-format
 msgid ""
 "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
@@ -1796,20 +1798,20 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1475
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1481
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr "從硬碟開機"
 
 # index.docbook:1591, index.docbook:2097
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1487
 #, no-c-format
 msgid ""
 "Booting from an existing operating system is often a convenient option; for "
@@ -1820,7 +1822,7 @@ msgstr ""
 
 # index.docbook:1597, index.docbook:2103
 #. Tag: para
-#: boot-installer.xml:1491
+#: boot-installer.xml:1493
 #, fuzzy, no-c-format
 #| msgid ""
 #| "To boot the installer from hard disk, you will have already completed "
@@ -1835,13 +1837,13 @@ msgstr ""
 "> 處下載並且在 <xref linkend=\"boot-drive-files\"/> 安置了所需檔案。"
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1513
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr "從 OldWorld PowerMacs 的 MacOS 上開機"
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1514
 #, no-c-format
 msgid ""
 "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
@@ -1862,13 +1864,13 @@ msgstr ""
 "序。"
 
 #. Tag: title
-#: boot-installer.xml:1530
+#: boot-installer.xml:1532
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr "從 NewWorld Macs 的 OpenFirmware 開機"
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1533
 #, fuzzy, no-c-format
 #| msgid ""
 #| "You will have already placed the <filename>vmlinux</filename>, "
@@ -1935,19 +1937,19 @@ msgstr ""
 
 # index.docbook:700, index.docbook:2176
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr "從 USB 隨身碟開機"
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1566
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr "目前，New World PowerMac 系統支援從 USB 開機。"
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1572
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Make sure you have prepared everything from <xref linkend=\"boot-usb-files"
@@ -1971,7 +1973,7 @@ msgstr ""
 "openfirmware\"/>)。"
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1581
 #, no-c-format
 msgid ""
 "You will need to work out where the USB storage device appears in the device "
@@ -1992,7 +1994,7 @@ msgstr ""
 "disk@1</filename> 。"
 
 #. Tag: para
-#: boot-installer.xml:1591
+#: boot-installer.xml:1593
 #, no-c-format
 msgid ""
 "Having worked out the device path, use a command like this to boot the "
@@ -2016,7 +2018,7 @@ msgstr ""
 "command>。"
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1607
 #, no-c-format
 msgid ""
 "The system should now boot up, and you should be presented with the "
@@ -2027,7 +2029,7 @@ msgstr ""
 "入啟動參數，或者只按下 &enterkey;。"
 
 #. Tag: para
-#: boot-installer.xml:1611
+#: boot-installer.xml:1613
 #, no-c-format
 msgid ""
 "This boot method is new, and may be difficult to get to work on some "
@@ -2038,13 +2040,13 @@ msgstr ""
 "下安裝報告，請參閱 <xref linkend=\"submit-bug\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1644
+#: boot-installer.xml:1646
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr "目前來說，PReP 以及 New World PowerMac 系統支援網路開機。"
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1650
 #, fuzzy, no-c-format
 msgid ""
 "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
@@ -2071,7 +2073,7 @@ msgstr ""
 "userinput>。"
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1678
 #, no-c-format
 msgid ""
 "Booting from floppies is supported for &arch-title;, although it is "
@@ -2083,7 +2085,7 @@ msgstr ""
 "沒有安裝軟碟機，而且加裝的 USB 軟碟並不支援開機。"
 
 #. Tag: para
-#: boot-installer.xml:1688
+#: boot-installer.xml:1690
 #, no-c-format
 msgid ""
 "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
@@ -2094,7 +2096,7 @@ msgstr ""
 "按下電源開關前把它放到軟碟機內。"
 
 #. Tag: para
-#: boot-installer.xml:1694
+#: boot-installer.xml:1696
 #, no-c-format
 msgid ""
 "For those not familiar with Macintosh floppy operations: a floppy placed in "
@@ -2106,7 +2108,7 @@ msgstr ""
 "順序。一個沒有有效開機系統的軟碟將會被退出，並且機器將檢查硬碟分割區。"
 
 #. Tag: para
-#: boot-installer.xml:1701
+#: boot-installer.xml:1703
 #, no-c-format
 msgid ""
 "After booting, the <filename>root.bin</filename> floppy is requested. Insert "
@@ -2117,13 +2119,13 @@ msgstr ""
 "&enterkey;。安裝程式將在根系統被裝入記憶體後自動啟動。"
 
 #. Tag: title
-#: boot-installer.xml:1712
+#: boot-installer.xml:1714
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr "PowerPC 開機參數"
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1715
 #, no-c-format
 msgid ""
 "Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
@@ -2138,7 +2140,7 @@ msgstr ""
 "128 來說，請改變其值為 <userinput>video=aty128fb:vmode:6</userinput> 。"
 
 #. Tag: para
-#: boot-installer.xml:1753
+#: boot-installer.xml:1755
 #, fuzzy, no-c-format
 msgid ""
 "On machines with OpenBoot, simply enter the boot monitor on the machine "
@@ -2157,7 +2159,7 @@ msgstr ""
 "userinput>﹔這些可能不支援 DHCP。"
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1810
 #, fuzzy, no-c-format
 msgid ""
 "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
@@ -2171,13 +2173,13 @@ msgstr ""
 "有些問題。"
 
 #. Tag: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1819
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr "IDPROM 訊息"
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1820
 #, no-c-format
 msgid ""
 "If you cannot boot because you get messages about a problem with "
@@ -2191,13 +2193,13 @@ msgstr ""
 "nvram-faq;\">Sun NVRAM 常見問答集</ulink> 以取得更多資訊。"
 
 #. Tag: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1840
 #, no-c-format
 msgid ""
 "Some users may need specific support because of e.g. some visual impairment. "
@@ -2214,13 +2216,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1861
 #, no-c-format
 msgid ""
 "USB braille displays should be automatically detected. A textual version of "
@@ -2234,13 +2236,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1877
 #, no-c-format
 msgid ""
 "Serial braille displays cannot safely be automatically detected (since that "
@@ -2263,13 +2265,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2861
+#: boot-installer.xml:1899 boot-installer.xml:2863
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1900
 #, no-c-format
 msgid ""
 "Support for software speech synthesis can be activated by selecting it in "
@@ -2280,13 +2282,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1912
 #, no-c-format
 msgid ""
 "Support for hardware speech synthesis devices is available only alongside "
@@ -2295,7 +2297,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1918
 #, no-c-format
 msgid ""
 "Hardware speech synthesis devices cannot be automatically detected. You thus "
@@ -2309,13 +2311,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1934
 #, no-c-format
 msgid ""
 "Some accessibility devices are actual boards that are plugged inside the "
@@ -2326,7 +2328,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1942
 #, no-c-format
 msgid ""
 "If desired a textual version of the bootloader can be activated before "
@@ -2334,13 +2336,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1951
 #, no-c-format
 msgid ""
 "For users with low vision, the installer can use a high-contrast theme that "
@@ -2349,13 +2351,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1961
 #, no-c-format
 msgid ""
 "Alternatively, &debian; can be installed completely automatically by using "
@@ -2363,7 +2365,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1976
 #, no-c-format
 msgid ""
 "Boot parameters are Linux kernel parameters which are generally used to make "
@@ -2376,7 +2378,7 @@ msgstr ""
 "要給核心一點小小的幫助。"
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1983
 #, no-c-format
 msgid ""
 "If this is the first time you're booting the system, try the default boot "
@@ -2389,7 +2391,7 @@ msgstr ""
 "系統什麼樣的特定參數。"
 
 #. Tag: para
-#: boot-installer.xml:1988
+#: boot-installer.xml:1990
 #, no-c-format
 msgid ""
 "Information on many boot parameters can be found in the <ulink url=\"http://"
@@ -2404,7 +2406,7 @@ msgstr ""
 "linkend=\"boot-troubleshooting\"/>。"
 
 #. Tag: para
-#: boot-installer.xml:1999
+#: boot-installer.xml:2001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2432,7 +2434,7 @@ msgstr ""
 "<filename>ttyS0</filename>。"
 
 #. Tag: para
-#: boot-installer.xml:2011
+#: boot-installer.xml:2013
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you are booting with a serial console, generally the kernel will "
@@ -2464,7 +2466,7 @@ msgstr ""
 "<filename>ttyS0</filename>。"
 
 #. Tag: para
-#: boot-installer.xml:2027
+#: boot-installer.xml:2029
 #, no-c-format
 msgid ""
 "For &arch-title; the serial devices are <filename>ttya</filename> or "
@@ -2477,13 +2479,13 @@ msgstr ""
 "<envar>output-device</envar> OpenPROM 變數至 <filename>ttya</filename>。"
 
 #. Tag: title
-#: boot-installer.xml:2038
+#: boot-installer.xml:2040
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr "&debian; 安裝程式的參數"
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2041
 #, fuzzy, no-c-format
 msgid ""
 "The installation system recognizes a few additional boot "
@@ -2496,7 +2498,7 @@ msgstr ""
 "核會忽略過多的選項，2.6 核心則會當機。</para> </footnote>，也許比較有用。"
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2054
 #, no-c-format
 msgid ""
 "A number of parameters have a <quote>short form</quote> that helps avoid the "
@@ -2507,19 +2509,19 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2064
+#: boot-installer.xml:2066
 #, fuzzy, no-c-format
 msgid "debconf/priority (priority)"
 msgstr "debconf/priority"
 
 #. Tag: para
-#: boot-installer.xml:2065
+#: boot-installer.xml:2067
 #, fuzzy, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr "這些參數將顯示資訊設定為最低的級別。"
 
 #. Tag: para
-#: boot-installer.xml:2069
+#: boot-installer.xml:2071
 #, fuzzy, no-c-format
 msgid ""
 "The default installation uses <userinput>priority=high</userinput>. This "
@@ -2532,7 +2534,7 @@ msgstr ""
 "程式將按照要求調整優先級別。"
 
 #. Tag: para
-#: boot-installer.xml:2076
+#: boot-installer.xml:2078
 #, fuzzy, no-c-format
 msgid ""
 "If you add <userinput>priority=medium</userinput> as boot parameter, you "
@@ -2550,13 +2552,13 @@ msgstr ""
 "安裝系統只會顯示至關重要的資訊，並且嘗試正確無誤地執行各項事宜。"
 
 #. Tag: term
-#: boot-installer.xml:2090
+#: boot-installer.xml:2092
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr "DEBIAN_FRONTEND"
 
 #. Tag: para
-#: boot-installer.xml:2091
+#: boot-installer.xml:2093
 #, fuzzy, no-c-format
 msgid ""
 "This boot parameter controls the type of user interface used for the "
@@ -2593,13 +2595,13 @@ msgstr ""
 "用。"
 
 #. Tag: term
-#: boot-installer.xml:2122
+#: boot-installer.xml:2124
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr "BOOT_DEBUG"
 
 #. Tag: para
-#: boot-installer.xml:2123
+#: boot-installer.xml:2125
 #, no-c-format
 msgid ""
 "Setting this boot parameter to 2 will cause the installer's boot process to "
@@ -2611,49 +2613,49 @@ msgstr ""
 "除錯介殼在決定性的時間點上能被使用。 (離開介殼後將繼續安裝程序。)"
 
 #. Tag: userinput
-#: boot-installer.xml:2132
+#: boot-installer.xml:2134
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr "BOOT_DEBUG=0"
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2135
 #, no-c-format
 msgid "This is the default."
 msgstr "此為預設。"
 
 #. Tag: userinput
-#: boot-installer.xml:2137
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr "BOOT_DEBUG=1"
 
 #. Tag: para
-#: boot-installer.xml:2138
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "More verbose than usual."
 msgstr "更多的資訊。"
 
 #. Tag: userinput
-#: boot-installer.xml:2142
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr "BOOT_DEBUG=2"
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2145
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr "大量的除錯資訊。"
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr "BOOT_DEBUG=3"
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2150
 #, no-c-format
 msgid ""
 "Shells are run at various points in the boot process to allow detailed "
@@ -2663,13 +2665,13 @@ msgstr ""
 "程。"
 
 #. Tag: term
-#: boot-installer.xml:2162
+#: boot-installer.xml:2164
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr "INSTALL_MEDIA_DEV"
 
 #. Tag: para
-#: boot-installer.xml:2163
+#: boot-installer.xml:2165
 #, no-c-format
 msgid ""
 "The value of the parameter is the path to the device to load the &debian; "
@@ -2680,7 +2682,7 @@ msgstr ""
 "<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 
 #. Tag: para
-#: boot-installer.xml:2169
+#: boot-installer.xml:2171
 #, fuzzy, no-c-format
 msgid ""
 "The boot floppy, which normally scans all floppies it can to find the root "
@@ -2690,19 +2692,19 @@ msgstr ""
 "只查找一個設備。"
 
 #. Tag: term
-#: boot-installer.xml:2180
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2181
+#: boot-installer.xml:2183
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2182
+#: boot-installer.xml:2184
 #, no-c-format
 msgid ""
 "Causes the installer to send log messages to a remote syslog on the "
@@ -2711,13 +2713,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2193
+#: boot-installer.xml:2195
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2194
+#: boot-installer.xml:2196
 #, no-c-format
 msgid ""
 "Can be used to force the installer to a lowmem level higher than the one the "
@@ -2726,13 +2728,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2204
+#: boot-installer.xml:2206
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2205
+#: boot-installer.xml:2207
 #, no-c-format
 msgid ""
 "Prevents the installer from offering interactive shells on tty2 and tty3. "
@@ -2740,13 +2742,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2216
 #, fuzzy, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2217
 #, fuzzy, no-c-format
 msgid ""
 "Some architectures use the kernel framebuffer to offer installation in a "
@@ -2762,13 +2764,13 @@ msgstr ""
 "空白的螢幕，或者在開始安裝的時候停止幾分鐘。"
 
 #. Tag: para
-#: boot-installer.xml:2224
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr "在 hppa 上面報告過存在這些問題。"
 
 #. Tag: para
-#: boot-installer.xml:2228
+#: boot-installer.xml:2230
 #, fuzzy, no-c-format
 msgid ""
 "Because of display problems on some systems, framebuffer support is "
@@ -2785,13 +2787,13 @@ msgstr ""
 "installer/framebuffer=true</userinput>。"
 
 #. Tag: term
-#: boot-installer.xml:2242
+#: boot-installer.xml:2244
 #, fuzzy, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2243
+#: boot-installer.xml:2245
 #, no-c-format
 msgid ""
 "A theme determines how the user interface of the installer looks (colors, "
@@ -2802,13 +2804,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2255 boot-installer.xml:2488
+#: boot-installer.xml:2257 boot-installer.xml:2490
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr "netcfg/disable_dhcp"
 
 #. Tag: para
-#: boot-installer.xml:2256
+#: boot-installer.xml:2258
 #, no-c-format
 msgid ""
 "By default, the &d-i; automatically probes for network configuration via "
@@ -2820,7 +2822,7 @@ msgstr ""
 "且改變其取得的設定。您可以在 DHCP 檢測失敗的情況下手動配置網路。"
 
 #. Tag: para
-#: boot-installer.xml:2263
+#: boot-installer.xml:2265
 #, no-c-format
 msgid ""
 "If you have a DHCP server on your local network, but want to avoid it "
@@ -2833,13 +2835,13 @@ msgstr ""
 "DHCP 來設定網路並且手動輸入參數。"
 
 #. Tag: term
-#: boot-installer.xml:2274
+#: boot-installer.xml:2276
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr "hw-detect/start_pcmcia"
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2277
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
@@ -2849,13 +2851,13 @@ msgstr ""
 "題。有些筆記型電腦對此會有錯誤的行為。"
 
 #. Tag: term
-#: boot-installer.xml:2285
+#: boot-installer.xml:2287
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2286
+#: boot-installer.xml:2288
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
@@ -2865,13 +2867,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2297
+#: boot-installer.xml:2299
 #, fuzzy, no-c-format
 msgid "preseed/url (url)"
 msgstr "preseed/url"
 
 #. Tag: para
-#: boot-installer.xml:2298
+#: boot-installer.xml:2300
 #, fuzzy, no-c-format
 msgid ""
 "Specify the url to a preconfiguration file to download and use for "
@@ -2881,13 +2883,13 @@ msgstr ""
 "linkend=\"automatic-install\"/>。"
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2309
 #, fuzzy, no-c-format
 msgid "preseed/file (file)"
 msgstr "preseed/file"
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2310
 #, fuzzy, no-c-format
 msgid ""
 "Specify the path to a preconfiguration file to load for automating the "
@@ -2897,13 +2899,13 @@ msgstr ""
 "\"automatic-install\"/>。"
 
 #. Tag: term
-#: boot-installer.xml:2317
+#: boot-installer.xml:2319
 #, fuzzy, no-c-format
 msgid "preseed/interactive"
 msgstr "preseed/file"
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2320
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to display questions even if they have "
@@ -2914,13 +2916,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2330
+#: boot-installer.xml:2332
 #, fuzzy, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2333
 #, no-c-format
 msgid ""
 "Delay questions that are normally asked before preseeding is possible until "
@@ -2929,13 +2931,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2344
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2345
 #, no-c-format
 msgid ""
 "During installations from serial or management console, the regular virtual "
@@ -2944,13 +2946,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2354
+#: boot-installer.xml:2356
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr "cdrom-detect/eject"
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2357
 #, no-c-format
 msgid ""
 "By default, before rebooting, &d-i; automatically ejects the optical media "
@@ -2966,7 +2968,7 @@ msgstr ""
 "碟機不能自動重新掛載媒介。"
 
 #. Tag: para
-#: boot-installer.xml:2364
+#: boot-installer.xml:2366
 #, no-c-format
 msgid ""
 "Set to <userinput>false</userinput> to disable automatic ejection, and be "
@@ -2977,13 +2979,13 @@ msgstr ""
 "後，不會自動從光碟開機。"
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2377
 #, fuzzy, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2378
 #, no-c-format
 msgid ""
 "By setting this option to <userinput>false</userinput>, the package "
@@ -2993,7 +2995,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2383
+#: boot-installer.xml:2385
 #, no-c-format
 msgid ""
 "Note that this option allows to have a leaner system, but can also result in "
@@ -3004,13 +3006,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2395
+#: boot-installer.xml:2397
 #, fuzzy, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2396
+#: boot-installer.xml:2398
 #, no-c-format
 msgid ""
 "By default the installer requires that repositories be authenticated using a "
@@ -3020,13 +3022,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "ramdisk_size"
 msgstr "ramdisk_size"
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, no-c-format
 msgid ""
 "This parameter should already be set to a correct value where needed; set it "
@@ -3035,13 +3037,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2418
+#: boot-installer.xml:2420
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2419
+#: boot-installer.xml:2421
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> to enter rescue mode rather than "
@@ -3049,13 +3051,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2432
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2433
+#: boot-installer.xml:2435
 #, no-c-format
 msgid ""
 "With some exceptions, a value can be set at the boot prompt for any question "
@@ -3065,25 +3067,25 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2445
+#: boot-installer.xml:2447
 #, fuzzy, no-c-format
 msgid "debian-installer/language (language)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: term
-#: boot-installer.xml:2446
+#: boot-installer.xml:2448
 #, fuzzy, no-c-format
 msgid "debian-installer/country (country)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: term
-#: boot-installer.xml:2447
+#: boot-installer.xml:2449
 #, fuzzy, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr "debian-installer/framebuffer"
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2450
 #, no-c-format
 msgid ""
 "There are two ways to specify the language, country and locale to use for "
@@ -3091,7 +3093,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2453
+#: boot-installer.xml:2455
 #, no-c-format
 msgid ""
 "The first and easiest is to pass only the parameter <literal>locale</"
@@ -3104,7 +3106,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid ""
 "The second, more flexible option is to specify <literal>language</literal> "
@@ -3115,13 +3117,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2474
+#: boot-installer.xml:2476
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2475
+#: boot-installer.xml:2477
 #, no-c-format
 msgid ""
 "Can be used to automatically load installer components that are not loaded "
@@ -3132,7 +3134,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2489
+#: boot-installer.xml:2491
 #, no-c-format
 msgid ""
 "Set to <userinput>true</userinput> if you want to disable DHCP and instead "
@@ -3140,13 +3142,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2498
+#: boot-installer.xml:2500
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid ""
 "By default the installer will use the http protocol to download files from "
@@ -3158,13 +3160,13 @@ msgid ""
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2512
+#: boot-installer.xml:2514
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2513
+#: boot-installer.xml:2515
 #, no-c-format
 msgid ""
 "Can be used to select tasks that are not available from the interactive task "
@@ -3173,13 +3175,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2527
+#: boot-installer.xml:2529
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2528
+#: boot-installer.xml:2530
 #, no-c-format
 msgid ""
 "If drivers are compiled into the kernel, you can pass parameters to them as "
@@ -3194,7 +3196,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2541
+#: boot-installer.xml:2543
 #, no-c-format
 msgid ""
 "Note that it is now quite rare that parameters need to be passed to modules. "
@@ -3204,7 +3206,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2548
+#: boot-installer.xml:2550
 #, no-c-format
 msgid ""
 "The syntax to use to set parameters for modules is: "
@@ -3218,19 +3220,19 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2558
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2564
+#: boot-installer.xml:2566
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2565
+#: boot-installer.xml:2567
 #, no-c-format
 msgid ""
 "Sometimes it may be necessary to blacklist a module to prevent it from being "
@@ -3242,7 +3244,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, no-c-format
 msgid ""
 "You can blacklist a module using the following syntax: "
@@ -3253,7 +3255,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2582
+#: boot-installer.xml:2584
 #, no-c-format
 msgid ""
 "Note that a module may still be loaded by the installation system itself. "
@@ -3263,19 +3265,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2598
+#: boot-installer.xml:2600
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr "安裝過程中的障礙排除"
 
 #. Tag: title
-#: boot-installer.xml:2603
+#: boot-installer.xml:2605
 #, fuzzy, no-c-format
 msgid "CD-ROM Reliability"
 msgstr "軟碟的可靠性"
 
 #. Tag: para
-#: boot-installer.xml:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid ""
 "Sometimes, especially with older CD-ROM drives, the installer may fail to "
@@ -3285,7 +3287,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2613
 #, no-c-format
 msgid ""
 "There are many different possible causes for these problems. We can only "
@@ -3294,13 +3296,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2622
+#: boot-installer.xml:2624
 #, no-c-format
 msgid ""
 "If the CD-ROM does not boot, check that it was inserted correctly and that "
@@ -3308,7 +3310,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2628
+#: boot-installer.xml:2630
 #, no-c-format
 msgid ""
 "If the installer fails to recognize a CD-ROM, try just running the option "
@@ -3318,7 +3320,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2638
+#: boot-installer.xml:2640
 #, no-c-format
 msgid ""
 "If this does not work, then try the suggestions in the subsections below. "
@@ -3327,7 +3329,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2644
+#: boot-installer.xml:2646
 #, no-c-format
 msgid ""
 "If you cannot get the installation working from CD-ROM, try one of the other "
@@ -3335,13 +3337,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2652
+#: boot-installer.xml:2654
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2655
+#: boot-installer.xml:2657
 #, no-c-format
 msgid ""
 "Some older CD-ROM drives do not support reading from discs that were burned "
@@ -3349,7 +3351,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2674
 #, no-c-format
 msgid ""
 "Some very old CD-ROM drives do not work correctly if <quote>direct memory "
@@ -3357,19 +3359,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2683
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2684
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2689
+#: boot-installer.xml:2691
 #, no-c-format
 msgid ""
 "Check that your BIOS actually supports booting from CD-ROM (only an issue "
@@ -3377,7 +3379,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2698
 #, no-c-format
 msgid ""
 "If you downloaded an iso image, check that the md5sum of that image matches "
@@ -3393,7 +3395,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2709
+#: boot-installer.xml:2711
 #, no-c-format
 msgid ""
 "$ dd if=/dev/cdrom | \\\n"
@@ -3407,7 +3409,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2714
+#: boot-installer.xml:2716
 #, no-c-format
 msgid ""
 "If, after the installer has been booted successfully, the CD-ROM is not "
@@ -3421,7 +3423,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2726
+#: boot-installer.xml:2728
 #, no-c-format
 msgid ""
 "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
@@ -3430,7 +3432,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2733
+#: boot-installer.xml:2735
 #, no-c-format
 msgid ""
 "Check in the output of <command>dmesg</command> if your CD-ROM drive was "
@@ -3448,7 +3450,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2747
+#: boot-installer.xml:2749
 #, no-c-format
 msgid ""
 "Check that there is a device node for your CD-ROM drive under <filename>/dev/"
@@ -3457,7 +3459,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2755
+#: boot-installer.xml:2757
 #, no-c-format
 msgid ""
 "Use the <command>mount</command> command to check if the CD-ROM is already "
@@ -3468,7 +3470,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2765
+#: boot-installer.xml:2767
 #, no-c-format
 msgid ""
 "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -3484,7 +3486,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2780
+#: boot-installer.xml:2782
 #, no-c-format
 msgid ""
 "If there are any problems during the installation, try checking the "
@@ -3494,13 +3496,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2797
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr "軟碟的可靠性"
 
 #. Tag: para
-#: boot-installer.xml:2797
+#: boot-installer.xml:2799
 #, no-c-format
 msgid ""
 "The biggest problem for people using floppy disks to install &debian; seems "
@@ -3509,7 +3511,7 @@ msgstr ""
 "對於第一次安裝 &debian; 的人來說，他們遇到的最大的問題很可能是軟碟的可靠性。"
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2804
 #, fuzzy, no-c-format
 msgid ""
 "The boot floppy is the floppy with the worst problems, because it is read by "
@@ -3525,7 +3527,7 @@ msgstr ""
 "有關的 I/O 錯誤。"
 
 #. Tag: para
-#: boot-installer.xml:2811
+#: boot-installer.xml:2813
 #, fuzzy, no-c-format
 msgid ""
 "If you are having the installation stall at a particular floppy, the first "
@@ -3540,7 +3542,7 @@ msgstr ""
 "的話甚至要在別的統上重寫這些軟碟。"
 
 #. Tag: para
-#: boot-installer.xml:2820
+#: boot-installer.xml:2822
 #, no-c-format
 msgid ""
 "One user reports he had to write the images to floppy <emphasis>three</"
@@ -3551,7 +3553,7 @@ msgstr ""
 "軟碟才算工作良好。"
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2828
 #, no-c-format
 msgid ""
 "Normally you should not have to download a floppy image again, but if you "
@@ -3560,7 +3562,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid ""
 "Other users have reported that simply rebooting a few times with the same "
@@ -3571,13 +3573,13 @@ msgstr ""
 "為 硬體或者有缺陷的韌體軟碟驅動程式造成的。"
 
 #. Tag: title
-#: boot-installer.xml:2841
+#: boot-installer.xml:2843
 #, no-c-format
 msgid "Boot Configuration"
 msgstr "開機設定"
 
 #. Tag: para
-#: boot-installer.xml:2843
+#: boot-installer.xml:2845
 #, no-c-format
 msgid ""
 "If you have problems and the kernel hangs during the boot process, doesn't "
@@ -3590,7 +3592,7 @@ msgstr ""
 "內容。"
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2854
 #, no-c-format
 msgid ""
 "In some cases, malfunctions can be caused by missing device firmware (see "
@@ -3599,7 +3601,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid ""
 "If software speech synthesis does not work, there is most probably an issue "
@@ -3611,37 +3613,37 @@ msgid ""
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2874
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2876
+#: boot-installer.xml:2878
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2878
+#: boot-installer.xml:2880
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2880
+#: boot-installer.xml:2882
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2888 boot-installer.xml:2999
+#: boot-installer.xml:2890 boot-installer.xml:3001
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr "常見的 &arch-title; 安裝問題"
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2891
 #, no-c-format
 msgid ""
 "There are some common installation problems that can be solved or avoided by "
@@ -3649,7 +3651,7 @@ msgid ""
 msgstr "傳入某些啟動參數可以解決或避免一些常見的安裝問題。"
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, fuzzy, no-c-format
 msgid ""
 "If your screen begins to show a weird picture while the kernel boots, eg. "
@@ -3668,13 +3670,13 @@ msgstr ""
 "parms\"/> 來取得細節資訊。"
 
 #. Tag: title
-#: boot-installer.xml:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr "在 PCMCIA 段系統當機"
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Some laptop models produced by Dell are known to crash when PCMCIA device "
@@ -3700,7 +3702,7 @@ msgstr ""
 "能引起問題的資源範圍。"
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid ""
 "Alternatively, you can boot the installer in expert mode. You will then be "
@@ -3720,19 +3722,19 @@ msgstr ""
 "些有問題的資源範圍選項。注意在安裝程式中，輸入這些值的時候必須忽略逗號。"
 
 #. Tag: para
-#: boot-installer.xml:3000
+#: boot-installer.xml:3002
 #, fuzzy, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr "傳入某些啟動參數可以解決或避免一些常見的安裝問題。"
 
 #. Tag: title
-#: boot-installer.xml:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, no-c-format
 msgid ""
 "It is fairly common for &arch-title; to have two video cards in one machine, "
@@ -3748,7 +3750,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3021
+#: boot-installer.xml:3023
 #, no-c-format
 msgid ""
 "Note that you may also have to manually add this parameter to the silo "
@@ -3758,13 +3760,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3032
+#: boot-installer.xml:3034
 #, fuzzy, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr "從光碟開機"
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid ""
 "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
@@ -3773,19 +3775,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3041
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3048
+#: boot-installer.xml:3050
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr "解讀核心起始資訊"
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3052
 #, fuzzy, no-c-format
 msgid ""
 "During the boot sequence, you may see many messages in the form "
@@ -3819,13 +3821,13 @@ msgstr ""
 "\"linux-any\">(請參閱 <xref linkend=\"kernel-baking\"/>)</phrase>。"
 
 #. Tag: title
-#: boot-installer.xml:3075
+#: boot-installer.xml:3077
 #, fuzzy, no-c-format
 msgid "Reporting Installation Problems"
 msgstr "常見的 &arch-title; 安裝問題"
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, fuzzy, no-c-format
 msgid ""
 "If you get through the initial boot phase but cannot complete the install, "
@@ -3842,7 +3844,7 @@ msgstr ""
 "資訊。"
 
 #. Tag: para
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, fuzzy, no-c-format
 msgid ""
 "Other pertinent installation messages may be found in <filename>/var/log/</"
@@ -3854,13 +3856,13 @@ msgstr ""
 "中。"
 
 #. Tag: title
-#: boot-installer.xml:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr "回報安裝報告"
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, no-c-format
 msgid ""
 "If you still have problems, please submit an installation report. We also "
@@ -3870,7 +3872,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3106
+#: boot-installer.xml:3108
 #, no-c-format
 msgid ""
 "Note that your installation report will be published in the Debian Bug "
@@ -3879,7 +3881,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3112
+#: boot-installer.xml:3114
 #, no-c-format
 msgid ""
 "If you have a working &debian; system, the easiest way to send an "
@@ -3892,7 +3894,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3122
+#: boot-installer.xml:3124
 #, fuzzy, no-c-format
 msgid ""
 "Alternatively you can use this template when filling out installation "
diff --git a/po/zh_TW/install-methods.po b/po/zh_TW/install-methods.po
index e25248177..ec32ba026 100644
--- a/po/zh_TW/install-methods.po
+++ b/po/zh_TW/install-methods.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: 2012-10-24 19:53+0000\n"
+"POT-Creation-Date: 2012-11-24 22:10+0000\n"
 "PO-Revision-Date: 2005-07-18 12:10+0800\n"
 "Last-Translator: Jhang, Jia-Wei<dreamcryer@gmail.com>\n"
 "Language-Team: debian-chinese-big5 <debian-chinese-big5@lists.debian.org>\n"
@@ -73,15 +73,14 @@ msgstr ""
 #, no-c-format
 msgid ""
 "As CDs have a rather limited capacity by today's standards, not all "
-"graphical desktop environments are installable with only the first CD; only "
-"XFCE (which is the default desktop environment installed by &debian-gnu; "
-"&release;) completely fits on the first CD. For all other desktop "
-"environments a CD installation requires either network connectivity during "
-"the installation to download the remaining files or additional CDs."
+"graphical desktop environments are installable with only the first CD; for "
+"some desktop environments a CD installation requires either network "
+"connectivity during the installation to download the remaining files or "
+"additional CDs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:39
+#: install-methods.xml:38
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If your machine doesn't support CD booting, but you do have a CD set, you "
@@ -119,7 +118,7 @@ msgstr ""
 "時，請在光碟中同樣的目錄和子目錄下查找它們。"
 
 #. Tag: para
-#: install-methods.xml:62
+#: install-methods.xml:61
 #, no-c-format
 msgid ""
 "Once the installer is booted, it will be able to obtain all the other files "
@@ -127,7 +126,7 @@ msgid ""
 msgstr "安裝程式啟動一旦啟動，它將能夠取得光碟中其他所有必需的檔案。"
 
 #. Tag: para
-#: install-methods.xml:67
+#: install-methods.xml:66
 #, no-c-format
 msgid ""
 "If you don't have a CD set, then you will need to download the installer "
@@ -144,13 +143,13 @@ msgstr ""
 "\"supports-tftp\">一台有連接網路的電腦上</phrase>，他們可以用來啟動安裝程式。"
 
 #. Tag: title
-#: install-methods.xml:93
+#: install-methods.xml:92
 #, no-c-format
 msgid "Downloading Files from &debian; Mirrors"
 msgstr "從 &debian; 鏡像伺服器下載檔案"
 
 #. Tag: para
-#: install-methods.xml:95
+#: install-methods.xml:94
 #, no-c-format
 msgid ""
 "To find the nearest (and thus probably the fastest) mirror, see the <ulink "
@@ -160,7 +159,7 @@ msgstr ""
 "debian-mirrors;\">&debian; 鏡像列表</ulink>。"
 
 #. Tag: para
-#: install-methods.xml:100
+#: install-methods.xml:99
 #, fuzzy, no-c-format
 #| msgid ""
 #| "When downloading files from a Debian mirror, be sure to download the "
@@ -173,13 +172,13 @@ msgstr ""
 "式下載，而不是文字或者自動模式。"
 
 #. Tag: title
-#: install-methods.xml:108
+#: install-methods.xml:107
 #, no-c-format
 msgid "Where to Find Installation Images"
 msgstr "哪裡能找到安裝映像檔"
 
 #. Tag: para
-#: install-methods.xml:110
+#: install-methods.xml:109
 #, no-c-format
 msgid ""
 "The installation images are located on each &debian; mirror in the directory "
@@ -194,13 +193,13 @@ msgstr ""
 "\">MANIFEST</ulink> 文件列出每個映像檔及其用途。"
 
 #. Tag: title
-#: install-methods.xml:123
+#: install-methods.xml:122
 #, fuzzy, no-c-format
 msgid "Thecus N2100 Installation Files"
 msgstr "CATS 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:124
+#: install-methods.xml:123
 #, no-c-format
 msgid ""
 "A firmware image is provided for the Thecus N2100 which will automatically "
@@ -210,14 +209,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:135
+#: install-methods.xml:134
 #, fuzzy, no-c-format
 #| msgid "CATS Installation Files"
 msgid "GLAN Tank Installation Files"
 msgstr "CATS 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:136
+#: install-methods.xml:135
 #, no-c-format
 msgid ""
 "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk "
@@ -226,14 +225,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:146
+#: install-methods.xml:145
 #, fuzzy, no-c-format
 #| msgid "RiscPC Installation Files"
 msgid "Kurobox Pro Installation Files"
 msgstr "RiscPC 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:147
+#: install-methods.xml:146
 #, no-c-format
 msgid ""
 "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the "
@@ -242,13 +241,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:157
+#: install-methods.xml:156
 #, fuzzy, no-c-format
 msgid "HP mv2120 Installation Files"
 msgstr "CATS 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:158
+#: install-methods.xml:157
 #, no-c-format
 msgid ""
 "A firmware image is provided for the HP mv2120 which will automatically boot "
@@ -259,14 +258,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:170
+#: install-methods.xml:169
 #, fuzzy, no-c-format
 #| msgid "CATS Installation Files"
 msgid "QNAP Turbo Station Installation Files"
 msgstr "CATS 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:171
+#: install-methods.xml:170
 #, no-c-format
 msgid ""
 "The installation files for the QNAP Turbo Station consist of a kernel and "
@@ -276,13 +275,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:182
+#: install-methods.xml:181
 #, fuzzy, no-c-format
 msgid "Plug Computer and OpenRD Installation Files"
 msgstr "NetWinder 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:183
+#: install-methods.xml:182
 #, no-c-format
 msgid ""
 "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug "
@@ -291,14 +290,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:193
+#: install-methods.xml:192
 #, fuzzy, no-c-format
 #| msgid "CATS Installation Files"
 msgid "LaCie NASes Installation Files"
 msgstr "CATS 的安裝檔案"
 
 #. Tag: para
-#: install-methods.xml:194
+#: install-methods.xml:193
 #, no-c-format
 msgid ""
 "The installation files for LaCie NASes (Network Space v2, Network Space Max "
@@ -308,13 +307,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:245
+#: install-methods.xml:244
 #, no-c-format
 msgid "Creating an IPL tape"
 msgstr "建立 IPL 磁帶"
 
 #. Tag: para
-#: install-methods.xml:247
+#: install-methods.xml:246
 #, fuzzy, no-c-format
 msgid ""
 "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
@@ -335,13 +334,13 @@ msgstr ""
 "閱 <xref linkend=\"where-files\"/>,"
 
 #. Tag: title
-#: install-methods.xml:271
+#: install-methods.xml:270
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr "利用軟碟映像檔建立開機磁片"
 
 #. Tag: para
-#: install-methods.xml:272
+#: install-methods.xml:271
 #, no-c-format
 msgid ""
 "Bootable floppy disks are generally used as a last resort to boot the "
@@ -351,7 +350,7 @@ msgstr ""
 "最後一種方法。"
 
 #. Tag: para
-#: install-methods.xml:277
+#: install-methods.xml:276
 #, fuzzy, no-c-format
 msgid ""
 "Booting the installer from floppy disk reportedly fails on Mac USB floppy "
@@ -359,7 +358,7 @@ msgid ""
 msgstr "有報告說 Mac USB 軟碟機不支援開機磁片。"
 
 #. Tag: para
-#: install-methods.xml:282
+#: install-methods.xml:281
 #, no-c-format
 msgid ""
 "Disk images are files containing the complete contents of a floppy disk in "
@@ -377,7 +376,7 @@ msgstr ""
 "<emphasis>按磁區拷貝</emphasis>到軟碟中。"
 
 #. Tag: para
-#: install-methods.xml:293
+#: install-methods.xml:292
 #, fuzzy, no-c-format
 msgid ""
 "There are different techniques for creating floppies from disk images. This "
@@ -388,7 +387,7 @@ msgstr ""
 "在不同平台上從從軟碟映像檔建立開機磁片。"
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:298
 #, no-c-format
 msgid ""
 "Before you can create the floppies, you will first need to download them "
@@ -399,7 +398,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:307
+#: install-methods.xml:306
 #, no-c-format
 msgid ""
 "No matter which method you use to create your floppies, you should remember "
@@ -410,13 +409,13 @@ msgstr ""
 "內容不會在無意間被清除。"
 
 #. Tag: title
-#: install-methods.xml:315
+#: install-methods.xml:314
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr "從 Linux 或者 Unix 系統寫入軟碟映像檔"
 
 #. Tag: para
-#: install-methods.xml:316
+#: install-methods.xml:315
 #, fuzzy, no-c-format
 msgid ""
 "To write the floppy disk image files to the floppy disks, you will probably "
@@ -450,7 +449,7 @@ msgstr ""
 "手冊)</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:337
+#: install-methods.xml:336
 #, no-c-format
 msgid ""
 "Some systems attempt to automatically mount a floppy disk when you place it "
@@ -480,7 +479,7 @@ msgstr ""
 "統，請咨詢您的系統管理員)。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:358
+#: install-methods.xml:357
 #, no-c-format
 msgid ""
 "If writing a floppy on powerpc Linux, you will need to eject it. The "
@@ -491,13 +490,13 @@ msgstr ""
 "command> 指令能夠對此進行控制，當然您可能需要先安裝它。"
 
 #. Tag: title
-#: install-methods.xml:376
+#: install-methods.xml:375
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr "在 DOS、Windows、或者 OS/2 下寫入磁碟映像檔"
 
 #. Tag: para
-#: install-methods.xml:378
+#: install-methods.xml:377
 #, fuzzy, no-c-format
 msgid ""
 "If you have access to an i386 or amd64 machine, you can use one of the "
@@ -506,7 +505,7 @@ msgstr ""
 "如果您能操作一台 i386 機器，您可以使用如下方法之一把映像檔拷貝到軟碟上。"
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:382
 #, no-c-format
 msgid ""
 "The <command>rawrite1</command> and <command>rawrite2</command> programs can "
@@ -520,7 +519,7 @@ msgstr ""
 "者在檔案瀏覽器中雙擊使用這些程式是<emphasis>不能</emphasis>執行的。"
 
 #. Tag: para
-#: install-methods.xml:391
+#: install-methods.xml:390
 #, no-c-format
 msgid ""
 "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, "
@@ -531,7 +530,7 @@ msgstr ""
 "最新的版本上運行。要使用它您需要解壓 diskio.dll 至相同目錄下。"
 
 #. Tag: para
-#: install-methods.xml:397
+#: install-methods.xml:396
 #, no-c-format
 msgid ""
 "These tools can be found on the Official &debian; CD-ROMs under the "
@@ -541,13 +540,13 @@ msgstr ""
 "目錄下。"
 
 #. Tag: title
-#: install-methods.xml:410
+#: install-methods.xml:409
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr "在 MacOS 上寫入磁碟映像檔"
 
 #. Tag: para
-#: install-methods.xml:411
+#: install-methods.xml:410
 #, no-c-format
 msgid ""
 "An AppleScript, <application>Make &debian; Floppy</application>, is "
@@ -567,7 +566,7 @@ msgstr ""
 "寫入磁碟映像檔。"
 
 #. Tag: para
-#: install-methods.xml:422
+#: install-methods.xml:421
 #, no-c-format
 msgid ""
 "You can also use the MacOS utility <command>Disk Copy</command> directly, or "
@@ -580,13 +579,13 @@ msgstr ""
 "例。您可以使用這些工具和以下方法將磁碟映像寫入軟碟。"
 
 #. Tag: title
-#: install-methods.xml:433
+#: install-methods.xml:432
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr "寫入磁碟映像檔：使用<command>Disk Copy</command>"
 
 #. Tag: para
-#: install-methods.xml:434
+#: install-methods.xml:433
 #, no-c-format
 msgid ""
 "If you are creating the floppy image from files which were originally on the "
@@ -599,7 +598,7 @@ msgstr ""
 "像站下載映像檔的情況。"
 
 #. Tag: para
-#: install-methods.xml:443
+#: install-methods.xml:442
 #, no-c-format
 msgid ""
 "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
@@ -609,7 +608,7 @@ msgstr ""
 "且用它打開 <filename>root.bin</filename> 檔案。"
 
 #. Tag: para
-#: install-methods.xml:450
+#: install-methods.xml:449
 #, no-c-format
 msgid ""
 "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
@@ -620,7 +619,7 @@ msgstr ""
 "<userinput>DDim</userinput> (binary floppy image)。注意此處有大小寫區分。"
 
 #. Tag: para
-#: install-methods.xml:457
+#: install-methods.xml:456
 #, no-c-format
 msgid ""
 "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
@@ -635,7 +634,7 @@ msgstr ""
 "MacOS 才不會刪除開機區。"
 
 #. Tag: para
-#: install-methods.xml:466
+#: install-methods.xml:465
 #, no-c-format
 msgid ""
 "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
@@ -647,7 +646,7 @@ msgstr ""
 "ulink>。"
 
 #. Tag: para
-#: install-methods.xml:473
+#: install-methods.xml:472
 #, no-c-format
 msgid ""
 "Run <command>Disk Copy</command>, and select <menuchoice> "
@@ -662,13 +661,13 @@ msgstr ""
 "是否刪除它。完成後它應該會退出磁片。"
 
 #. Tag: title
-#: install-methods.xml:488
+#: install-methods.xml:487
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr "寫入磁碟映像檔：使用<command>suntar</command>"
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:491
 #, no-c-format
 msgid ""
 "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
@@ -681,21 +680,21 @@ msgstr ""
 "userinput> 選單中選擇 <quote>Overwrite Sectors...</quote>。"
 
 #. Tag: para
-#: install-methods.xml:500
+#: install-methods.xml:499
 #, no-c-format
 msgid ""
 "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr "按照要求插入軟碟，然後按下 &enterkey; (從0磁區開始)。"
 
 #. Tag: para
-#: install-methods.xml:506
+#: install-methods.xml:505
 #, no-c-format
 msgid ""
 "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr "在開啟檔案對話框中選擇 <filename>root.bin</filename> 檔案。"
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:510
 #, no-c-format
 msgid ""
 "After the floppy has been created successfully, select <menuchoice> "
@@ -708,7 +707,7 @@ msgstr ""
 "的軟碟試試。"
 
 #. Tag: para
-#: install-methods.xml:519
+#: install-methods.xml:518
 #, no-c-format
 msgid ""
 "Before using the floppy you created, <emphasis>set the write protect tab</"
@@ -719,13 +718,13 @@ msgstr ""
 "偶然在 MacOS 中掛載了它，MacOS 將會將其毀壞。"
 
 #. Tag: title
-#: install-methods.xml:538
+#: install-methods.xml:537
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr "準備從 USB 隨身碟開機的檔案"
 
 #. Tag: para
-#: install-methods.xml:540
+#: install-methods.xml:539
 #, fuzzy, no-c-format
 msgid ""
 "To prepare the USB stick, you will need a system where GNU/Linux is already "
@@ -745,7 +744,7 @@ msgstr ""
 "保護開關。"
 
 #. Tag: para
-#: install-methods.xml:553
+#: install-methods.xml:552
 #, no-c-format
 msgid ""
 "The procedures described in this section will destroy anything already on "
@@ -755,13 +754,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:563
+#: install-methods.xml:562
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:564
+#: install-methods.xml:563
 #, no-c-format
 msgid ""
 "Debian CD and DVD images can now be written directly a USB stick, which is a "
@@ -771,7 +770,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:571
+#: install-methods.xml:570
 #, no-c-format
 msgid ""
 "Alternatively, for very small USB sticks, only a few megabytes in size, you "
@@ -781,7 +780,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:578
 #, no-c-format
 msgid ""
 "A special method can be used to add firmware to the <filename>mini.iso</"
@@ -793,7 +792,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:589
+#: install-methods.xml:588
 #, no-c-format
 msgid ""
 "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -804,7 +803,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:595
+#: install-methods.xml:594
 #, no-c-format
 msgid ""
 "The CD or DVD image you choose should be written directly to the USB stick, "
@@ -814,7 +813,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:602
+#: install-methods.xml:601
 #, no-c-format
 msgid ""
 "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/"
@@ -823,7 +822,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:604
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
 "Simply writing the CD or DVD image to USB like this should work fine for "
@@ -832,14 +831,14 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:615
+#: install-methods.xml:614
 #, fuzzy, no-c-format
 #| msgid "Booting the USB stick"
 msgid "Manually copying files to the USB stick"
 msgstr "以 USB 隨身碟開機"
 
 #. Tag: para
-#: install-methods.xml:616
+#: install-methods.xml:615
 #, fuzzy, no-c-format
 msgid ""
 "An alternative way to set up your USB stick is to manually copy the "
@@ -851,7 +850,7 @@ msgstr ""
 "<xref linkend=\"usb-copy-flexible\"/>)。"
 
 #. Tag: para
-#: install-methods.xml:623
+#: install-methods.xml:622
 #, fuzzy, no-c-format
 msgid ""
 "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
@@ -868,7 +867,7 @@ msgstr ""
 "查您使用的是正確的 USB 隨身碟設備名稱。"
 
 #. Tag: para
-#: install-methods.xml:632
+#: install-methods.xml:631
 #, no-c-format
 msgid ""
 "Note that, although convenient, this method does have one major "
@@ -879,19 +878,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:639
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:644
+#: install-methods.xml:643
 #, fuzzy, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr "# install-mbr /dev/<replaceable>sda</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:645
 #, fuzzy, no-c-format
 msgid ""
 "Create a partition of type \"Apple_Bootstrap\" on your USB stick using "
@@ -908,13 +907,13 @@ msgstr ""
 "查您使用的是正確的 USB 隨身碟設備名稱。"
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:651
 #, fuzzy, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr "# install-mbr /dev/<replaceable>sda</replaceable>"
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:653
 #, fuzzy, no-c-format
 msgid ""
 "After that, mount the USB memory stick <phrase arch=\"x86\">"
@@ -935,14 +934,14 @@ msgstr ""
 "(<userinput>umount /mnt</userinput>) 後結束。"
 
 #. Tag: title
-#: install-methods.xml:671
+#: install-methods.xml:670
 #, fuzzy, no-c-format
 #| msgid "Copying the files &mdash; the flexible way"
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr "複製檔案 &mdash; 靈活的方法"
 
 #. Tag: para
-#: install-methods.xml:672
+#: install-methods.xml:671
 #, fuzzy, no-c-format
 #| msgid ""
 #| "If you like more flexibility or just want to know what's going on, you "
@@ -958,14 +957,14 @@ msgstr ""
 "檔案放到您的隨身碟上。"
 
 #. Tag: title
-#: install-methods.xml:687 install-methods.xml:809
+#: install-methods.xml:686 install-methods.xml:808
 #, fuzzy, no-c-format
 #| msgid "Booting the USB stick"
 msgid "Partitioning the USB stick"
 msgstr "以 USB 隨身碟開機"
 
 #. Tag: para
-#: install-methods.xml:688
+#: install-methods.xml:687
 #, no-c-format
 msgid ""
 "We will show how to set up the memory stick to use the first partition, "
@@ -973,7 +972,7 @@ msgid ""
 msgstr "我們將展示如何使用隨身碟的第一個分割區，而不是整個設備。"
 
 #. Tag: para
-#: install-methods.xml:693
+#: install-methods.xml:692
 #, fuzzy, no-c-format
 msgid ""
 "Since most USB sticks come pre-configured with a single FAT16 partition, you "
@@ -1000,7 +999,7 @@ msgstr ""
 "&debian; 套件中。"
 
 #. Tag: para
-#: install-methods.xml:717
+#: install-methods.xml:716
 #, fuzzy, no-c-format
 #| msgid ""
 #| "In order to start the kernel after booting from the USB stick, we will "
@@ -1025,7 +1024,7 @@ msgstr ""
 "案系統的操作系統可以用來改變 boot-loader 的設定檔案。"
 
 #. Tag: para
-#: install-methods.xml:727
+#: install-methods.xml:726
 #, fuzzy, no-c-format
 #| msgid ""
 #| "To put <command>SYSLINUX</command> on the FAT16 partition on your USB "
@@ -1058,14 +1057,14 @@ msgstr ""
 "<filename>ldlinux.sys</filename> 檔案。"
 
 #. Tag: title
-#: install-methods.xml:744 install-methods.xml:856
+#: install-methods.xml:743 install-methods.xml:855
 #, fuzzy, no-c-format
 #| msgid "Adding an ISO image"
 msgid "Adding the installer image"
 msgstr "添加 ISO 映像"
 
 #. Tag: para
-#: install-methods.xml:745
+#: install-methods.xml:744
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and "
@@ -1099,7 +1098,7 @@ msgstr ""
 "<command>SYSLINUX</command> 只能處理 DOS (8.3) 格式的檔案名稱。"
 
 #. Tag: para
-#: install-methods.xml:769
+#: install-methods.xml:768
 #, fuzzy, no-c-format
 msgid ""
 "Next you should create a <filename>syslinux.cfg</filename> configuration "
@@ -1123,7 +1122,7 @@ msgstr ""
 "userinput> 到 <quote>append</quote> 那一行。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:781
+#: install-methods.xml:780
 #, no-c-format
 msgid ""
 "To enable the boot prompt to permit further parameter appending, add a "
@@ -1131,7 +1130,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:786 install-methods.xml:896
+#: install-methods.xml:785 install-methods.xml:895
 #, no-c-format
 msgid ""
 "If you used an <filename>hd-media</filename> image, you should now copy the "
@@ -1144,7 +1143,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:810
+#: install-methods.xml:809
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Most USB sticks do not come pre-configured in such a way that Open "
@@ -1183,7 +1182,7 @@ msgstr ""
 "&debian; 套件中。"
 
 #. Tag: para
-#: install-methods.xml:827
+#: install-methods.xml:826
 #, no-c-format
 msgid ""
 "In order to start the kernel after booting from the USB stick, we will put a "
@@ -1198,7 +1197,7 @@ msgstr ""
 "改變 boot-loader 的設定檔。"
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:835
 #, fuzzy, no-c-format
 #| msgid ""
 #| "The normal <command>ybin</command> tool that comes with <command>yaboot</"
@@ -1248,7 +1247,7 @@ msgstr ""
 "其他部分就可以用普通的 Unix 工具來處理了。"
 
 #. Tag: para
-#: install-methods.xml:857
+#: install-methods.xml:856
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and "
@@ -1261,31 +1260,31 @@ msgstr ""
 "檔案從 &debian; 檔案庫拷貝到儲存上："
 
 #. Tag: para
-#: install-methods.xml:864
+#: install-methods.xml:863
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr "<filename>vmlinux</filename> (核心二進位文件)"
 
 #. Tag: para
-#: install-methods.xml:869
+#: install-methods.xml:868
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (初始化記憶體映像檔)"
 
 #. Tag: para
-#: install-methods.xml:874
+#: install-methods.xml:873
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr "<filename>yaboot.conf</filename> (yaboot 設定檔案)"
 
 #. Tag: para
-#: install-methods.xml:879
+#: install-methods.xml:878
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr "<filename>boot.msg</filename> (可選的啟動資訊)"
 
 #. Tag: para
-#: install-methods.xml:886
+#: install-methods.xml:885
 #, fuzzy, no-c-format
 msgid ""
 "The <filename>yaboot.conf</filename> configuration file should contain the "
@@ -1322,13 +1321,13 @@ msgstr ""
 "像的大小。"
 
 #. Tag: title
-#: install-methods.xml:924
+#: install-methods.xml:923
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr "準備從硬碟開機的檔案"
 
 #. Tag: para
-#: install-methods.xml:925
+#: install-methods.xml:924
 #, no-c-format
 msgid ""
 "The installer may be booted using boot files placed on an existing hard "
@@ -1339,7 +1338,7 @@ msgstr ""
 "或者直接使用 BIOS 提供的 boot-loader 直接啟動。"
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:930
 #, no-c-format
 msgid ""
 "A full, <quote>pure network</quote> installation can be achieved using this "
@@ -1352,7 +1351,7 @@ msgstr ""
 "不清。"
 
 #. Tag: para
-#: install-methods.xml:938
+#: install-methods.xml:937
 #, no-c-format
 msgid ""
 "The installer cannot boot from files on an HFS+ file system. MacOS System "
@@ -1372,7 +1371,7 @@ msgstr ""
 "和 Linux 之間交換檔案，特別是那些您下載的安裝檔案。"
 
 #. Tag: para
-#: install-methods.xml:949
+#: install-methods.xml:948
 #, no-c-format
 msgid ""
 "Different programs are used for hard disk installation system booting, "
@@ -1383,7 +1382,7 @@ msgstr ""
 "安裝程式開機時將使用不同的安裝檔案。"
 
 #. Tag: title
-#: install-methods.xml:958
+#: install-methods.xml:957
 #, no-c-format
 msgid ""
 "Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
@@ -1392,7 +1391,7 @@ msgstr ""
 "使用 <command>LILO</command> 或 <command>GRUB</command>啟動硬碟安裝程式"
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:959
 #, no-c-format
 msgid ""
 "This section explains how to add to or even replace an existing linux "
@@ -1402,7 +1401,7 @@ msgstr ""
 "或者甚至替換現有的 linux 安裝。"
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:965
 #, no-c-format
 msgid ""
 "At boot time, both bootloaders support loading in memory not only the "
@@ -1413,7 +1412,7 @@ msgstr ""
 "擬磁碟可以被用做核心的根檔案系統。"
 
 #. Tag: para
-#: install-methods.xml:972
+#: install-methods.xml:971
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Copy the following files from the Debian archives to a convenient "
@@ -1428,19 +1427,19 @@ msgstr ""
 "boot/newinstall/</filename>。"
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:979
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr "<filename>vmlinuz</filename>(核心二進位文件)"
 
 #. Tag: para
-#: install-methods.xml:985
+#: install-methods.xml:984
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr "<filename>initrd.gz</filename> (記憶體虛擬磁碟映像)"
 
 #. Tag: para
-#: install-methods.xml:992
+#: install-methods.xml:991
 #, no-c-format
 msgid ""
 "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
@@ -1448,7 +1447,7 @@ msgid ""
 msgstr "最後，要設定 boot-loader，請進入 <xref linkend=\"boot-initrd\"/>。"
 
 #. Tag: title
-#: install-methods.xml:1002
+#: install-methods.xml:1001
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Hard disk installer booting using <command>LILO</command> or "
@@ -1458,7 +1457,7 @@ msgstr ""
 "使用 <command>LILO</command> 或 <command>GRUB</command>啟動硬碟安裝程式"
 
 #. Tag: para
-#: install-methods.xml:1003
+#: install-methods.xml:1002
 #, fuzzy, no-c-format
 #| msgid ""
 #| "This section explains how to add to or even replace an existing linux "
@@ -1472,7 +1471,7 @@ msgstr ""
 "或者甚至替換現有的 linux 安裝。"
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1007
 #, fuzzy, no-c-format
 #| msgid ""
 #| "Copy the following files from the Debian archives to a convenient "
@@ -1486,7 +1485,7 @@ msgstr ""
 "boot/newinstall/</filename>。"
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1012
 #, fuzzy, no-c-format
 #| msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgid ""
@@ -1494,20 +1493,20 @@ msgid ""
 msgstr "<filename>initrd.gz</filename> (初始化記憶體映像檔)"
 
 #. Tag: para
-#: install-methods.xml:1018
+#: install-methods.xml:1017
 #, fuzzy, no-c-format
 #| msgid "<filename>boot.msg</filename> (optional boot message)"
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr "<filename>boot.msg</filename> (可選的啟動資訊)"
 
 #. Tag: title
-#: install-methods.xml:1031
+#: install-methods.xml:1030
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr "OldWorld Macs 上的硬碟開機安裝程式"
 
 #. Tag: para
-#: install-methods.xml:1032
+#: install-methods.xml:1031
 #, no-c-format
 msgid ""
 "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
@@ -1529,7 +1528,7 @@ msgstr ""
 "是必須的。"
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1044
 #, no-c-format
 msgid ""
 "Download and unstuff the <application>BootX</application> distribution, "
@@ -1555,13 +1554,13 @@ msgstr ""
 "目錄中，然後把 <filename>Linux Kernels</filename> 目錄放到活動的系統目錄中。"
 
 #. Tag: title
-#: install-methods.xml:1065
+#: install-methods.xml:1064
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr "NewWorld Macs 下啟動硬碟安裝程式"
 
 #. Tag: para
-#: install-methods.xml:1066
+#: install-methods.xml:1065
 #, no-c-format
 msgid ""
 "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as "
@@ -1579,7 +1578,7 @@ msgstr ""
 "援，也一定不能用在 NewWorld PowerMacs 上。"
 
 #. Tag: para
-#: install-methods.xml:1077
+#: install-methods.xml:1076
 #, no-c-format
 msgid ""
 "<emphasis>Copy</emphasis> (not move) the following four files which you "
@@ -1592,31 +1591,31 @@ msgstr ""
 "案到硬碟圖示的方法來完成)。"
 
 #. Tag: filename
-#: install-methods.xml:1087 install-methods.xml:1413
+#: install-methods.xml:1086 install-methods.xml:1412
 #, no-c-format
 msgid "vmlinux"
 msgstr "vmlinux"
 
 #. Tag: filename
-#: install-methods.xml:1092 install-methods.xml:1418
+#: install-methods.xml:1091 install-methods.xml:1417
 #, no-c-format
 msgid "initrd.gz"
 msgstr "initrd.gz"
 
 #. Tag: filename
-#: install-methods.xml:1097 install-methods.xml:1423
+#: install-methods.xml:1096 install-methods.xml:1422
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1102 install-methods.xml:1428
+#: install-methods.xml:1101 install-methods.xml:1427
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1107
+#: install-methods.xml:1106
 #, fuzzy, no-c-format
 msgid ""
 "Make a note of the partition number of the MacOS partition where you place "
@@ -1630,19 +1629,19 @@ msgstr ""
 "個分割區號碼用於在 Open Firmware 提示符號下面輸入指令。"
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1114
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr "要啟動安裝程式，請進入 <xref linkend=\"boot-newworld\"/>。"
 
 #. Tag: title
-#: install-methods.xml:1128
+#: install-methods.xml:1127
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr "準備以 TFTP 網路開機用的檔案"
 
 #. Tag: para
-#: install-methods.xml:1129
+#: install-methods.xml:1128
 #, no-c-format
 msgid ""
 "If your machine is connected to a local area network, you may be able to "
@@ -1656,7 +1655,7 @@ msgstr ""
 "上面的某個特殊地方，並且設定您的機器從該機器進行開機。"
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1136
 #, fuzzy, no-c-format
 msgid ""
 "You need to set up a TFTP server, and for many machines a DHCP server<phrase "
@@ -1668,7 +1667,7 @@ msgstr ""
 "condition=\"supports-dhcp\">，又或 DHCP 伺服器</phrase>。"
 
 #. Tag: para
-#: install-methods.xml:1144
+#: install-methods.xml:1143
 #, fuzzy, no-c-format
 msgid ""
 "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
@@ -1688,7 +1687,7 @@ msgstr ""
 "只能透過 DHCP 來配置。</phrase>"
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1157
 #, no-c-format
 msgid ""
 "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good "
@@ -1699,7 +1698,7 @@ msgstr ""
 "替 BOOTP 比較好。有些最新的機器不能從 BOOTP 開機。"
 
 #. Tag: para
-#: install-methods.xml:1164
+#: install-methods.xml:1163
 #, fuzzy, no-c-format
 msgid ""
 "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
@@ -1709,7 +1708,7 @@ msgstr ""
 "網站上能夠找到 RBOOTD 軟體套件。"
 
 #. Tag: para
-#: install-methods.xml:1169
+#: install-methods.xml:1168
 #, no-c-format
 msgid ""
 "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to "
@@ -1723,7 +1722,7 @@ msgstr ""
 "上面的一些操作例子。"
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1176
 #, no-c-format
 msgid ""
 "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. "
@@ -1733,13 +1732,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1193
+#: install-methods.xml:1192
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr "設置 RARP 伺服器"
 
 #. Tag: para
-#: install-methods.xml:1194
+#: install-methods.xml:1193
 #, fuzzy, no-c-format
 msgid ""
 "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC "
@@ -1757,7 +1756,7 @@ msgstr ""
 "<userinput>/sbin/ifconfig eth0</userinput> 指令。"
 
 #. Tag: para
-#: install-methods.xml:1206
+#: install-methods.xml:1205
 #, fuzzy, no-c-format
 msgid ""
 "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, "
@@ -1777,13 +1776,13 @@ msgstr ""
 "使用 <userinput>/usr/sbin/rarpd -a</userinput> 指令。"
 
 #. Tag: title
-#: install-methods.xml:1227
+#: install-methods.xml:1226
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "設置 DHCP 伺服器"
 
 #. Tag: para
-#: install-methods.xml:1228
+#: install-methods.xml:1227
 #, no-c-format
 msgid ""
 "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-"
@@ -1793,7 +1792,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1235
+#: install-methods.xml:1234
 #, fuzzy, no-c-format
 msgid ""
 "option domain-name \"example.com\";\n"
@@ -1843,7 +1842,7 @@ msgstr ""
 "檔。"
 
 #. Tag: para
-#: install-methods.xml:1237
+#: install-methods.xml:1236
 #, no-c-format
 msgid ""
 "In this example, there is one server <replaceable>servername</replaceable> "
@@ -1859,7 +1858,7 @@ msgstr ""
 "TFTP 取得的檔案名稱。"
 
 #. Tag: para
-#: install-methods.xml:1247
+#: install-methods.xml:1246
 #, fuzzy, no-c-format
 msgid ""
 "After you have edited the <command>dhcpd</command> configuration file, "
@@ -1869,13 +1868,13 @@ msgstr ""
 "<userinput>/etc/init.d/dhcpd restart</userinput>。"
 
 #. Tag: title
-#: install-methods.xml:1255
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr "在 DHCP 設定中打開 PXE 開機功能"
 
 #. Tag: para
-#: install-methods.xml:1256
+#: install-methods.xml:1255
 #, fuzzy, no-c-format
 msgid ""
 "Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
@@ -1947,13 +1946,13 @@ msgstr ""
 "面的<xref linkend=\"tftp-images\"/> )。"
 
 #. Tag: title
-#: install-methods.xml:1276
+#: install-methods.xml:1275
 #, fuzzy, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr "設置 BOOTP 伺服器"
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1276
 #, fuzzy, no-c-format
 msgid ""
 "There are two BOOTP servers available for GNU/Linux. The first is CMU "
@@ -1968,7 +1967,7 @@ msgstr ""
 "classname> 軟體套件中。"
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1284
 #, fuzzy, no-c-format
 msgid ""
 "To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
@@ -2024,7 +2023,7 @@ msgstr ""
 "的 MAC 位址。 </phrase>"
 
 #. Tag: para
-#: install-methods.xml:1318
+#: install-methods.xml:1317
 #, fuzzy, no-c-format
 msgid ""
 "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
@@ -2045,13 +2044,13 @@ msgstr ""
 "令是：<userinput>/etc/init.d/dhcpd restart</userinput>。"
 
 #. Tag: title
-#: install-methods.xml:1337
+#: install-methods.xml:1336
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "啟用 TFTP 伺服器"
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1337
 #, no-c-format
 msgid ""
 "To get the TFTP server ready to go, you should first make sure that "
@@ -2059,7 +2058,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1343
+#: install-methods.xml:1342
 #, no-c-format
 msgid ""
 "In the case of <classname>tftpd-hpa</classname> there are two ways the "
@@ -2070,7 +2069,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1352
+#: install-methods.xml:1351
 #, no-c-format
 msgid ""
 "Historically, TFTP servers used <filename>/tftpboot</filename> as directory "
@@ -2082,7 +2081,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1362
+#: install-methods.xml:1361
 #, no-c-format
 msgid ""
 "All <command>in.tftpd</command> alternatives available in &debian; should "
@@ -2093,7 +2092,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1369
 #, fuzzy, no-c-format
 msgid ""
 "If you intend to install &debian; on an SGI machine and your TFTP server is "
@@ -2121,13 +2120,13 @@ msgstr ""
 "這個錯誤。"
 
 #. Tag: title
-#: install-methods.xml:1392
+#: install-methods.xml:1391
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr "將 TFTP 映像放到適當的位置"
 
 #. Tag: para
-#: install-methods.xml:1393
+#: install-methods.xml:1392
 #, fuzzy, no-c-format
 msgid ""
 "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
@@ -2143,7 +2142,7 @@ msgstr ""
 "個強制的標準。"
 
 #. Tag: para
-#: install-methods.xml:1402
+#: install-methods.xml:1401
 #, fuzzy, no-c-format
 #| msgid ""
 #| "On NewWorld Power Macintosh machines, you will need to set up the "
@@ -2166,13 +2165,13 @@ msgstr ""
 "TFTP 目錄。"
 
 #. Tag: filename
-#: install-methods.xml:1433
+#: install-methods.xml:1432
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1438
+#: install-methods.xml:1437
 #, fuzzy, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2187,7 +2186,7 @@ msgstr ""
 "所需的檔案名傳遞至 <command>tftpd</command>。"
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1445
 #, no-c-format
 msgid ""
 "For PXE booting, everything you should need is set up in the "
@@ -2202,13 +2201,13 @@ msgstr ""
 "efi</filename> 以開機所需的檔案名傳遞至<command>tftpd</command>。"
 
 #. Tag: title
-#: install-methods.xml:1458
+#: install-methods.xml:1457
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr "SPARC TFTP 開機"
 
 #. Tag: para
-#: install-methods.xml:1459
+#: install-methods.xml:1458
 #, fuzzy, no-c-format
 msgid ""
 "Some SPARC architectures add the subarchitecture names, such as "
@@ -2236,7 +2235,7 @@ msgstr ""
 "該將所有的字母改成大寫並在必要時加上子架構名。"
 
 #. Tag: para
-#: install-methods.xml:1475
+#: install-methods.xml:1474
 #, no-c-format
 msgid ""
 "If you've done all this correctly, giving the command <userinput>boot net</"
@@ -2246,7 +2245,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1482
+#: install-methods.xml:1481
 #, no-c-format
 msgid ""
 "You can also force some sparc systems to look for a specific file name by "
@@ -2259,13 +2258,13 @@ msgstr ""
 "仍然必須被放置在 TFTP 伺服器要查找的目錄中。"
 
 #. Tag: title
-#: install-methods.xml:1493
+#: install-methods.xml:1492
 #, fuzzy, no-c-format
 msgid "SGI TFTP Booting"
 msgstr "SGI Indys TFTP 開機"
 
 #. Tag: para
-#: install-methods.xml:1494
+#: install-methods.xml:1493
 #, fuzzy, no-c-format
 msgid ""
 "On SGI machines you can rely on the <command>bootpd</command> to supply the "
@@ -2279,13 +2278,13 @@ msgstr ""
 "<userinput>filename=</userinput>選項。"
 
 #. Tag: title
-#: install-methods.xml:1602
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "自動化安裝"
 
 #. Tag: para
-#: install-methods.xml:1603
+#: install-methods.xml:1602
 #, fuzzy, no-c-format
 #| msgid ""
 #| "For installing on multiple computers it's possible to do fully automatic "
@@ -2306,13 +2305,13 @@ msgstr ""
 "<classname>autoinstall</classname>，以及 &debian; 安裝程式本身。"
 
 #. Tag: title
-#: install-methods.xml:1615
+#: install-methods.xml:1614
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr "使用 &debian; 安裝程式進行自動安裝"
 
 #. Tag: para
-#: install-methods.xml:1616
+#: install-methods.xml:1615
 #, fuzzy, no-c-format
 msgid ""
 "The &debian; Installer supports automating installs via preconfiguration "
@@ -2324,7 +2323,7 @@ msgstr ""
 "者可從移動媒介上載入，並且被用來在安裝過程中自動回答問題。"
 
 #. Tag: para
-#: install-methods.xml:1623
+#: install-methods.xml:1622
 #, fuzzy, no-c-format
 msgid ""
 "Full documentation on preseeding including a working example that you can "
diff --git a/po/zh_TW/preseed.po b/po/zh_TW/preseed.po
index 6e75d46fd..62ed7489d 100644
--- a/po/zh_TW/preseed.po
+++ b/po/zh_TW/preseed.po
@@ -9,6 +9,7 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
@@ -22,13 +23,17 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:18
 #, no-c-format
-msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation."
+msgid ""
+"This appendix explains how to preseed answers to questions in &d-i; to "
+"automate your installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:23 preseed.xml:685
 #, no-c-format
-msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
+msgid ""
+"The configuration fragments used in this appendix are also available as an "
+"example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
 
 #. Tag: title
@@ -40,13 +45,22 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:32
 #, no-c-format
-msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid ""
+"Preseeding provides a way to set answers to questions asked during the "
+"installation process, without having to manually enter the answers while the "
+"installation is running. This makes it possible to fully automate most types "
+"of installation and even offers some features not available during normal "
+"installations."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:40
 #, no-c-format
-msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline."
+msgid ""
+"Preseeding is not required. If you use an empty preseed file, the installer "
+"will behave just the same way as in a normal manual installation. Each "
+"question you preseed will (if you got it right!) modify the installation in "
+"some way from that baseline."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +72,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:51
 #, no-c-format
-msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods."
+msgid ""
+"There are three methods that can be used for preseeding: <firstterm>initrd</"
+"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. "
+"Initrd preseeding will work with any installation method and supports "
+"preseeding of more things, but it requires the most preparation. File and "
+"network preseeding each can be used with different installation methods."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:60
 #, no-c-format
-msgid "The following table shows which preseeding methods can be used with which installation methods."
+msgid ""
+"The following table shows which preseeding methods can be used with which "
+"installation methods."
 msgstr ""
 
 #. Tag: entry
@@ -98,7 +119,10 @@ msgid "CD/DVD"
 msgstr ""
 
 #. Tag: entry
-#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111
+#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91
+#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100
+#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109
+#: preseed.xml:111
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
@@ -106,7 +130,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:81
 #, no-c-format
-msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately"
+msgid ""
+"but only if you have network access, and set <literal>preseed/url</literal> "
+"appropriately"
 msgstr ""
 
 #. Tag: entry
@@ -124,7 +150,8 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:93
 #, no-c-format
-msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
+msgid ""
+"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
 #. Tag: entry
@@ -148,19 +175,37 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:117
 #, no-c-format
-msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
+msgid ""
+"An important difference between the preseeding methods is the point at which "
+"the preconfiguration file is loaded and processed. For initrd preseeding "
+"this is right at the start of the installation, before the first question is "
+"even asked. For file preseeding this is after the CD or CD image has been "
+"loaded. For network preseeding it is only after the network has been "
+"configured."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:126
 #, no-c-format
-msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
+msgid ""
+"Obviously, any questions that have been processed before the "
+"preconfiguration file is loaded cannot be preseeded (this will include "
+"questions that are only displayed at medium or low priority, like the first "
+"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way "
+"to avoid these questions being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:134
 #, no-c-format
-msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details."
+msgid ""
+"In order to avoid the questions that would normally appear before the "
+"preseeding occurs, you can start the installer in <quote>auto</quote> mode. "
+"This delays questions that would normally be asked too early for preseeding "
+"(i.e. language, country and keyboard selection) until after the network "
+"comes up, thus allowing them to be preseeded. It also runs the installation "
+"at critical priority, which avoids many unimportant questions. See <xref "
+"linkend=\"preseed-auto\"/> for details."
 msgstr ""
 
 #. Tag: title
@@ -172,7 +217,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:149
 #, no-c-format
-msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions."
+msgid ""
+"Although most questions used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You must (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions."
 msgstr ""
 
 #. Tag: title
@@ -184,13 +233,24 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:224
 #, no-c-format
-msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;."
+msgid ""
+"You will first need to create a preconfiguration file and place it in the "
+"location from where you want to use it. Creating the preconfiguration file "
+"is covered later in this appendix. Putting it in the correct location is "
+"fairly straightforward for network preseeding or if you want to read the "
+"file off a floppy or usb-stick. If you want to include the file on a CD or "
+"DVD, you will have to remaster the ISO image. How to get the "
+"preconfiguration file included in the initrd is outside the scope of this "
+"document; please consult the developers' documentation for &d-i;."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:235
 #, no-c-format
-msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
+msgid ""
+"An example preconfiguration file that you can use as basis for your own "
+"preconfiguration file is available from &urlset-example-preseed;. This file "
+"is based on the configuration fragments included in this appendix."
 msgstr ""
 
 #. Tag: title
@@ -202,50 +262,79 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:245
 #, no-c-format
-msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
+msgid ""
+"If you are using initrd preseeding, you only have to make sure a file named "
+"<filename>preseed.cfg</filename> is included in the root directory of the "
+"initrd. The installer will automatically check if this file is present and "
+"load it."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:252
 #, no-c-format
-msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>"
+msgid ""
+"For the other preseeding methods you need to tell the installer what file to "
+"use when you boot it. This is normally done by passing the kernel a boot "
+"parameter, either manually at boot time or by editing the bootloader "
+"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</"
+"filename>) and adding the parameter to the end of the append line(s) for the "
+"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter as a new <literal>set</literal> line for "
+"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</"
+"filename>) and adding the parameter to the end of the <filename>gnumach.gz</"
+"filename> line.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:265
 #, no-c-format
-msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
+msgid ""
+"If you do specify the preconfiguration file in the bootloader configuration, "
+"you might change the configuration so you don't need to hit enter to boot "
+"the installer. <phrase arch=\"linux-any\">For syslinux this means setting "
+"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</"
+"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the "
+"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:274
 #, no-c-format
-msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it."
+msgid ""
+"To make sure the installer gets the right preconfiguration file, you can "
+"optionally specify a checksum for the file. Currently this needs to be a "
+"md5sum, and if specified it must match the preconfiguration file or the "
+"installer will refuse to use it."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:283
 #, no-c-format
 msgid ""
-      "Boot parameters to specify:\n"
-      "- if you're netbooting:\n"
-      "  preseed/url=http://host/path/to/preseed.cfg\n"
-      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're booting a remastered CD:\n"
-      "  preseed/file=/cdrom/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "- if you're installing from USB media (put the preconfiguration file in the\n"
-      "  toplevel directory of the USB stick):\n"
-      "  preseed/file=/hd-media/preseed.cfg\n"
-      "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
+"Boot parameters to specify:\n"
+"- if you're netbooting:\n"
+"  preseed/url=http://host/path/to/preseed.cfg\n"
+"  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're booting a remastered CD:\n"
+"  preseed/file=/cdrom/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"- if you're installing from USB media (put the preconfiguration file in the\n"
+"  toplevel directory of the USB stick):\n"
+"  preseed/file=/hd-media/preseed.cfg\n"
+"  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:285
 #, no-c-format
-msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename>, <filename>preseed/file</filename> to just <filename>file</filename> and <filename>preseed/file/checksum</filename> to just <filename>preseed-md5</filename> when they are passed as boot parameters."
+msgid ""
+"Note that <filename>preseed/url</filename> can be shortened to just "
+"<filename>url</filename>, <filename>preseed/file</filename> to just "
+"<filename>file</filename> and <filename>preseed/file/checksum</filename> to "
+"just <filename>preseed-md5</filename> when they are passed as boot "
+"parameters."
 msgstr ""
 
 #. Tag: title
@@ -257,55 +346,101 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:297
 #, no-c-format
-msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer."
+msgid ""
+"If a preconfiguration file cannot be used to preseed some steps, the install "
+"can still be fully automated, since you can pass preseed values on the "
+"command line when booting the installer."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:303
 #, no-c-format
-msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual."
+msgid ""
+"Boot parameters can also be used if you do not really want to use "
+"preseeding, but just want to provide an answer for a specific question. Some "
+"examples where this can be useful are documented elsewhere in this manual."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:309
 #, no-c-format
-msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package."
+msgid ""
+"To set a value to be used inside &d-i;, just pass "
+"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</"
+"replaceable></userinput> for any of the preseed variables listed in the "
+"examples in this appendix. If a value is to be used to configure packages "
+"for the target system, you will need to prepend the <firstterm>owner</"
+"firstterm><footnote> <para> The owner of a debconf variable (or template) is "
+"normally the name of the package that contains the corresponding debconf "
+"template. For variables used in the installer itself the owner is <quote>d-"
+"i</quote>. Templates and variables can have more than one owner which helps "
+"to determine whether they can be removed from the debconf database if the "
+"package is purged. </para> </footnote> of the variable as in "
+"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</"
+"replaceable>=<replaceable>value</replaceable></userinput>. If you don't "
+"specify the owner, the value for the variable will not be copied to the "
+"debconf database in the target system and thus remain unused during the "
+"configuration of the relevant package."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:332
 #, no-c-format
-msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>."
+msgid ""
+"Normally, preseeding a question in this way will mean that the question will "
+"not be asked. To set a specific default value for a question, but still have "
+"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as "
+"operator. See also <xref linkend=\"preseed-seenflag\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:339
 #, no-c-format
-msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>."
+msgid ""
+"Note that some variables that are frequently set at the boot prompt have a "
+"shorter alias. If an alias is available, it is used in the examples in this "
+"appendix instead of the full variable. The <literal>preseed/url</literal> "
+"variable for example has been aliased as <literal>url</literal>. Another "
+"example is the <literal>tasks</literal> alias, which translates to "
+"<literal>tasksel:tasksel/first</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:348
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid ""
+"A <quote>--</quote> in the boot options has special meaning. Kernel "
+"parameters that appear after the last <quote>--</quote> may be copied into "
+"the bootloader configuration for the installed system (if supported by the "
+"installer for the bootloader). The installer will automatically filter out "
+"any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:357
 #, no-c-format
-msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
+msgid ""
+"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line "
+"options and 32 environment options, including any options added by default "
+"for the installer. If these numbers are exceeded, the kernel will panic "
+"(crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:365
 #, no-c-format
-msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
+msgid ""
+"For most installations some of the default options in your bootloader "
+"configuration file, like <literal>vga=normal</literal>, may be safely "
+"removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:372
 #, no-c-format
-msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
+msgid ""
+"It may not always be possible to specify values with spaces for boot "
+"parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
@@ -318,24 +453,55 @@ msgstr ""
 #: preseed.xml:382
 #, no-c-format
 msgid ""
-      "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n"
-      "auto url=autoserver\n"
-      "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>."
+"There are several features of &debian; Installer that combine to allow "
+"fairly simple command lines at the boot prompt to result in arbitrarily "
+"complex customized automatic installs. To illustrate this, here are some "
+"examples that can be used at the boot prompt: <informalexample><screen>\n"
+"auto url=autoserver\n"
+"</screen></informalexample> This relies on there being a DHCP server that "
+"will get the machine to the point where <literal>autoserver</literal> can be "
+"resolved by DNS, perhaps after adding the local domain if that was provided "
+"by DHCP. If this was done at a site where the domain is <literal>example."
+"com</literal>, and they have a reasonably sane DHCP setup, it would result "
+"in the preseed file being retrieved from <literal>http://autoserver.example."
+"com/d-i/&releasename;/./preseed.cfg</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:399
 #, no-c-format
-msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>."
+msgid ""
+"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</"
+"literal>) is taken from <literal>auto-install/defaultroot</literal>. By "
+"default this includes the directory <literal>&releasename;</literal> to "
+"allow future versions to specify their own codename and let people migrate "
+"forwards in a controlled manner. The <literal>/./</literal> bit is used to "
+"indicate a root, relative to which subsequent paths can be anchored (for use "
+"in preseed/include and preseed/run). This allows files to be specified "
+"either as full URLs, paths starting with / that are thus anchored, or even "
+"paths relative to the location where the last preseed file was found. This "
+"can be used to construct more portable scripts where an entire hierarchy of "
+"scripts can be moved to a new location without breaking it, for example "
+"copying the files onto a USB stick when they started out on a web server. In "
+"this example, if the preseed file sets <literal>preseed/run</literal> to "
+"<literal>/scripts/late_command.sh</literal> then the file will be fetched "
+"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/"
+"late_command.sh</literal>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:419
 #, no-c-format
 msgid ""
-      "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n"
-      "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n"
-      "</screen></informalexample> The way this works is that:"
+"If there is no local DHCP or DNS infrastructure, or if you do not want to "
+"use the default path to <filename>preseed.cfg</filename>, you can still use "
+"an explicit url, and if you don't use the <literal>/./</literal> element it "
+"will be anchored to the start of the path (i.e. the third <literal>/</"
+"literal> in the URL). Here is an example that requires minimal support from "
+"the local network infrastructure: <informalexample><screen>\n"
+"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</"
+"replaceable>\n"
+"</screen></informalexample> The way this works is that:"
 msgstr ""
 
 #. Tag: para
@@ -347,46 +513,82 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:435
 #, no-c-format
-msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and"
+msgid ""
+"if the hostname section contains no periods, it has the domain derived from "
+"DHCP appended to it, and"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:439
 #, no-c-format
-msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added."
+msgid ""
+"if there's no <literal>/</literal>'s after the hostname, then the default "
+"path is added."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:445
 #, no-c-format
 msgid ""
-      "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n"
-      "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n"
-      "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used."
+"In addition to specifying the url, you can also specify settings that do not "
+"directly affect the behavior of &d-i; itself, but can be passed through to "
+"scripts specified using <literal>preseed/run</literal> in the loaded preseed "
+"file. At present, the only example of this is <literal>auto-install/classes</"
+"literal>, which has an alias <literal>classes</literal>. This can be used "
+"thus: <informalexample><screen>\n"
+"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;"
+"class_B</replaceable>\n"
+"</screen></informalexample> The classes could for example denote the type of "
+"system to be installed, or the localization to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:459
 #, no-c-format
-msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you."
+msgid ""
+"It is of course possible to extend this concept, and if you do, it is "
+"reasonable to use the auto-install namespace for this. So one might have "
+"something like <literal>auto-install/style</literal> which is then used in "
+"your scripts. If you feel the need to do this, please mention it on the "
+"<email>debian-boot@lists.debian.org</email> mailing list so that we can "
+"avoid namespace conflicts, and perhaps add an alias for the parameter for "
+"you."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:469
 #, no-c-format
-msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked."
+msgid ""
+"The <literal>auto</literal> boot label is not yet defined everywhere. The "
+"same effect may be achieved by simply adding the two parameters "
+"<literal>auto=true priority=critical</literal> to the kernel command line. "
+"The <literal>auto</literal> parameter is an alias for <literal>auto-install/"
+"enable</literal> and setting it to <literal>true</literal> delays the locale "
+"and keyboard questions until after there has been a chance to preseed them, "
+"while <literal>priority</literal> is an alias for <literal>debconf/priority</"
+"literal> and setting it to <literal>critical</literal> stops any questions "
+"with a lower priority from being asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:483
 #, no-c-format
-msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query."
+msgid ""
+"Additional options that may be of interest while attempting to automate an "
+"install while using DHCP are: <literal>interface=auto netcfg/"
+"dhcp_timeout=60</literal> which makes the machine choose the first viable "
+"NIC and be more patient about getting a reply to its DHCP query."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:492
 #, no-c-format
-msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration."
+msgid ""
+"An extensive example of how to use this framework, including example scripts "
+"and classes, can be found on the <ulink url=\"http://hands.com/d-i/"
+"\">website of its developer</ulink>. The examples available there also show "
+"many other nice effects that can be achieved by creative use of "
+"preconfiguration."
 msgstr ""
 
 #. Tag: title
@@ -398,7 +600,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:504
 #, no-c-format
-msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>."
+msgid ""
+"The following aliases can be useful when using (auto mode) preseeding. Note "
+"that these are simply short aliases for question names, and you always need "
+"to specify a value as well: for example, <literal>auto=true</literal> or "
+"<literal>interface=eth0</literal>."
 msgstr ""
 
 #. Tag: entry
@@ -668,28 +874,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:546
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid ""
+"It's also possible to use DHCP to specify a preconfiguration file to "
+"download from the network. DHCP allows specifying a filename. Normally this "
+"is a file to netboot, but if it appears to be an URL then installation media "
+"that support network preseeding will download the file from the URL and use "
+"it as a preconfiguration file. Here is an example of how to set it up in the "
+"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; "
+"package)."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:557
 #, no-c-format
 msgid ""
-      "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
-      "    filename \"http://host/preseed.cfg\";\n"
-      "}"
+"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n"
+"    filename \"http://host/preseed.cfg\";\n"
+"}"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:559
 #, no-c-format
-msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network."
+msgid ""
+"Note that the above example limits this filename to DHCP clients that "
+"identify themselves as \"d-i\", so it will not affect regular DHCP clients, "
+"but only the installer. You can also put the text in a stanza for only one "
+"particular host to avoid preseeding all installs on your network."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:566
 #, no-c-format
-msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care."
+msgid ""
+"A good way to use the DHCP preseeding is to only preseed values specific to "
+"your network, such as the &debian; mirror to use. This way installs on your "
+"network will automatically get a good mirror selected, but the rest of the "
+"installation can be performed interactively. Using DHCP preseeding to fully "
+"automate &debian; installs should only be done with care."
 msgstr ""
 
 #. Tag: title
@@ -701,7 +923,10 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:581
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
+msgid ""
+"The preconfiguration file is in the format used by the <command>debconf-set-"
+"selections</command> command. The general format of a line in a "
+"preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
@@ -713,87 +938,131 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:589
 #, no-c-format
-msgid "There are a few rules to keep in mind when writing a preconfiguration file."
+msgid ""
+"There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:596
 #, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
+msgid ""
+"Put only a single space or tab between type and value: any additional "
+"whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:600
 #, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
+msgid ""
+"A line can be split into multiple lines by appending a backslash "
+"(<quote><literal>\\</literal></quote>) as the line continuation character. A "
+"good place to split a line is after the question name; a bad place is "
+"between type and value. Split lines will be joined into a single line with "
+"all leading/trailing whitespace condensed to a single space."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:607
 #, no-c-format
-msgid "For debconf variables (templates) used only in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
+msgid ""
+"For debconf variables (templates) used only in the installer itself, the "
+"owner should be set to <quote>d-i</quote>; to preseed variables used in the "
+"installed system, the name of the package that contains the corresponding "
+"debconf template should be used. Only variables that have their owner set to "
+"something other than <quote>d-i</quote> will be propagated to the debconf "
+"database for the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:615
 #, no-c-format
-msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
+msgid ""
+"Most questions need to be preseeded using the values valid in English and "
+"not the translated values. However, there are some questions (for example in "
+"<classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:621
 #, no-c-format
-msgid "Some questions take a code as value instead of the English text that is shown during installation."
+msgid ""
+"Some questions take a code as value instead of the English text that is "
+"shown during installation."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:627
 #, no-c-format
-msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
+msgid ""
+"The easiest way to create a preconfiguration file is to use the example file "
+"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:632
 #, no-c-format
-msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
+msgid ""
+"An alternative method is to do a manual installation and then, after "
+"rebooting, use the <command>debconf-get-selections</command> from the "
+"<classname>debconf-utils</classname> package to dump both the debconf "
+"database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:639
 #, no-c-format
 msgid ""
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
+"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
+"$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:641
 #, no-c-format
-msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
+msgid ""
+"However, a file generated in this manner will have some items that should "
+"not be preseeded, and the example file is a better starting place for most "
+"users."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:649
 #, no-c-format
-msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
+msgid ""
+"This method relies on the fact that, at the end of the installation, the "
+"installer's cdebconf database is saved to the installed system in <filename>/"
+"var/log/installer/cdebconf</filename>. However, because the database may "
+"contain sensitive information, by default the files are only readable by "
+"root."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:657
 #, no-c-format
-msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
+msgid ""
+"The directory <filename>/var/log/installer</filename> and all files in it "
+"will be deleted from your system if you purge the package "
+"<classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:665
 #, no-c-format
-msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
+msgid ""
+"To check possible values for questions, you can use <command>nano</command> "
+"to examine the files in <filename>/var/lib/cdebconf</filename> while an "
+"installation is in progress. View <filename>templates.dat</filename> for the "
+"raw templates and <filename>questions.dat</filename> for the current values "
+"and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:673
 #, no-c-format
-msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
+msgid ""
+"To check if the format of your preconfiguration file is valid before "
+"performing an install, you can use the command <command>debconf-set-"
+"selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
@@ -805,13 +1074,20 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:690
 #, no-c-format
-msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
+msgid ""
+"Note that this example is based on an installation for the Intel x86 "
+"architecture. If you are installing a different architecture, some of the "
+"examples (like keyboard selection and bootloader installation) may not be "
+"relevant and will need to be replaced by debconf settings appropriate for "
+"your architecture."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:698
 #, no-c-format
-msgid "Details on how the different Debian Installer components actually work can be found in <xref linkend=\"module-details\"/>."
+msgid ""
+"Details on how the different Debian Installer components actually work can "
+"be found in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: title
@@ -823,56 +1099,81 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:707
 #, no-c-format
-msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
+msgid ""
+"Setting localization values will only work if you are using initrd "
+"preseeding. With all other methods the preconfiguration file will only be "
+"loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:713
 #, no-c-format
-msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid ""
+"The locale can be used to specify both language and country and can be any "
+"combination of a language supported by &d-i; and a recognized country. If "
+"the combination does not form a valid locale, the installer will "
+"automatically select a locale that is valid for the selected language. To "
+"specify the locale as a boot parameter, use "
+"<userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:722
 #, no-c-format
-msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters."
+msgid ""
+"Although this method is very easy to use, it does not allow preseeding of "
+"all possible combinations of language, country and locale<footnote> <para> "
+"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would "
+"for example result in <literal>en_US.UTF-8</literal> as default locale for "
+"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred "
+"instead, the values will need to be preseeded individually. </para> </"
+"footnote>. So alternatively the values can be preseeded individually. "
+"Language and country can also be specified as boot parameters."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:737
 #, no-c-format
 msgid ""
-      "# Preseeding only locale sets language, country and locale.\n"
-      "d-i debian-installer/locale string en_US\n"
-      "\n"
-      "# The values can also be preseeded individually for greater flexibility.\n"
-      "#d-i debian-installer/language string en\n"
-      "#d-i debian-installer/country string NL\n"
-      "#d-i debian-installer/locale string en_GB.UTF-8\n"
-      "# Optionally specify additional locales to be generated.\n"
-      "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
+"# Preseeding only locale sets language, country and locale.\n"
+"d-i debian-installer/locale string en_US\n"
+"\n"
+"# The values can also be preseeded individually for greater flexibility.\n"
+"#d-i debian-installer/language string en\n"
+"#d-i debian-installer/country string NL\n"
+"#d-i debian-installer/locale string en_GB.UTF-8\n"
+"# Optionally specify additional locales to be generated.\n"
+"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:739
 #, no-c-format
-msgid "Keyboard configuration consists of selecting a keymap and (for non-latin keymaps) a toggle key to switch between the non-latin keymap and the US keymap. Only basic keymap variants are available during installation. Advanced variants are available only in the installed system, through <command>dpkg-reconfigure keyboard-configuration</command>."
+msgid ""
+"Keyboard configuration consists of selecting a keymap and (for non-latin "
+"keymaps) a toggle key to switch between the non-latin keymap and the US "
+"keymap. Only basic keymap variants are available during installation. "
+"Advanced variants are available only in the installed system, through "
+"<command>dpkg-reconfigure keyboard-configuration</command>."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:747
 #, no-c-format
 msgid ""
-      "# Keyboard selection.\n"
-      "# keymap is an alias for keyboard-configuration/xkb-keymap\n"
-      "d-i keymap select us\n"
-      "# d-i keyboard-configuration/toggle select No toggling"
+"# Keyboard selection.\n"
+"# keymap is an alias for keyboard-configuration/xkb-keymap\n"
+"d-i keymap select us\n"
+"# d-i keyboard-configuration/toggle select No toggling"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:749
 #, no-c-format
-msgid "To skip keyboard configuration, preseed <classname>keymap</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
+msgid ""
+"To skip keyboard configuration, preseed <classname>keymap</classname> with "
+"<userinput>skip-config</userinput>. This will result in the kernel keymap "
+"remaining active."
 msgstr ""
 
 #. Tag: title
@@ -884,19 +1185,34 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:762
 #, no-c-format
-msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
+msgid ""
+"Of course, preseeding the network configuration won't work if you're loading "
+"your preconfiguration file from the network. But it's great when you're "
+"booting from CD or USB stick. If you are loading preconfiguration files from "
+"the network, you can pass network config parameters by using kernel boot "
+"parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:770
 #, no-c-format
-msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
+msgid ""
+"If you need to pick a particular interface when netbooting before loading a "
+"preconfiguration file from the network, use a boot parameter such as "
+"<userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:776
 #, no-c-format
-msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
+msgid ""
+"Although preseeding the network configuration is normally not possible when "
+"using network preseeding (using <quote>preseed/url</quote>), you can use the "
+"following hack to work around that, for example if you'd like to set a "
+"static address for the network interface. The hack is to force the network "
+"configuration to run again after the preconfiguration file has been loaded "
+"by creating a <quote>preseed/run</quote> script containing the following "
+"commands:"
 msgstr ""
 
 #. Tag: screen
@@ -915,69 +1231,76 @@ msgstr ""
 #: preseed.xml:794
 #, no-c-format
 msgid ""
-      "# Disable network configuration entirely. This is useful for cdrom\n"
-      "# installations on non-networked devices where the network questions,\n"
-      "# warning and long timeouts are a nuisance.\n"
-      "#d-i netcfg/enable boolean false\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# To pick a particular interface instead:\n"
-      "#d-i netcfg/choose_interface select eth1\n"
-      "\n"
-      "# To set a different link detection timeout (default is 3 seconds).\n"
-      "# Values are interpreted as seconds.\n"
-      "#d-i netcfg/link_detection_timeout string 10\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, uncomment this line and\n"
-      "# the static network configuration below.\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "\n"
-      "# If you want the preconfiguration file to work on systems both with and\n"
-      "# without a dhcp server, uncomment these lines and the static network\n"
-      "# configuration below.\n"
-      "#d-i netcfg/dhcp_failed note\n"
-      "#d-i netcfg/dhcp_options select Configure network manually\n"
-      "\n"
-      "# Static network configuration.\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Any hostname and domain names assigned from dhcp take precedence over\n"
-      "# values set here. However, setting the values still prevents the questions\n"
-      "# from being shown, even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# If you want to force a hostname, regardless of what either the DHCP\n"
-      "# server returns or what the reverse DNS entry for the IP is, uncomment\n"
-      "# and adjust the following line.\n"
-      "#d-i netcfg/hostname string somehost\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "# If non-free firmware is needed for the network or other hardware, you can\n"
-      "# configure the installer to always try to load it, without prompting. Or\n"
-      "# change to false to disable asking.\n"
-      "#d-i hw-detect/load_firmware boolean true"
+"# Disable network configuration entirely. This is useful for cdrom\n"
+"# installations on non-networked devices where the network questions,\n"
+"# warning and long timeouts are a nuisance.\n"
+"#d-i netcfg/enable boolean false\n"
+"\n"
+"# netcfg will choose an interface that has link if possible. This makes it\n"
+"# skip displaying a list if there is more than one interface.\n"
+"d-i netcfg/choose_interface select auto\n"
+"\n"
+"# To pick a particular interface instead:\n"
+"#d-i netcfg/choose_interface select eth1\n"
+"\n"
+"# To set a different link detection timeout (default is 3 seconds).\n"
+"# Values are interpreted as seconds.\n"
+"#d-i netcfg/link_detection_timeout string 10\n"
+"\n"
+"# If you have a slow dhcp server and the installer times out waiting for\n"
+"# it, this might be useful.\n"
+"#d-i netcfg/dhcp_timeout string 60\n"
+"\n"
+"# If you prefer to configure the network manually, uncomment this line and\n"
+"# the static network configuration below.\n"
+"#d-i netcfg/disable_dhcp boolean true\n"
+"\n"
+"# If you want the preconfiguration file to work on systems both with and\n"
+"# without a dhcp server, uncomment these lines and the static network\n"
+"# configuration below.\n"
+"#d-i netcfg/dhcp_failed note\n"
+"#d-i netcfg/dhcp_options select Configure network manually\n"
+"\n"
+"# Static network configuration.\n"
+"#d-i netcfg/get_nameservers string 192.168.1.1\n"
+"#d-i netcfg/get_ipaddress string 192.168.1.42\n"
+"#d-i netcfg/get_netmask string 255.255.255.0\n"
+"#d-i netcfg/get_gateway string 192.168.1.1\n"
+"#d-i netcfg/confirm_static boolean true\n"
+"\n"
+"# Any hostname and domain names assigned from dhcp take precedence over\n"
+"# values set here. However, setting the values still prevents the questions\n"
+"# from being shown, even if values come from dhcp.\n"
+"d-i netcfg/get_hostname string unassigned-hostname\n"
+"d-i netcfg/get_domain string unassigned-domain\n"
+"\n"
+"# If you want to force a hostname, regardless of what either the DHCP\n"
+"# server returns or what the reverse DNS entry for the IP is, uncomment\n"
+"# and adjust the following line.\n"
+"#d-i netcfg/hostname string somehost\n"
+"\n"
+"# Disable that annoying WEP key dialog.\n"
+"d-i netcfg/wireless_wep string\n"
+"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
+"#d-i netcfg/dhcp_hostname string radish\n"
+"\n"
+"# If non-free firmware is needed for the network or other hardware, you can\n"
+"# configure the installer to always try to load it, without prompting. Or\n"
+"# change to false to disable asking.\n"
+"#d-i hw-detect/load_firmware boolean true"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:796
 #, no-c-format
-msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
+msgid ""
+"Please note that <command>netcfg</command> will automatically determine the "
+"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In "
+"this case, the variable has to be marked as <literal>seen</literal> for "
+"automatic installations. Similarly, <command>netcfg</command> will choose an "
+"appropriate address if <classname>netcfg/get_gateway</classname> is not set. "
+"As a special case, you can set <classname>netcfg/get_gateway</classname> to "
+"<quote>none</quote> to specify that no gateway should be used."
 msgstr ""
 
 #. Tag: title
@@ -990,13 +1313,13 @@ msgstr ""
 #: preseed.xml:814
 #, no-c-format
 msgid ""
-      "# Use the following settings if you wish to make use of the network-console\n"
-      "# component for remote installation over SSH. This only makes sense if you\n"
-      "# intend to perform the remainder of the installation manually.\n"
-      "#d-i anna/choose_modules string network-console\n"
-      "#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
-      "#d-i network-console/password password r00tme\n"
-      "#d-i network-console/password-again password r00tme"
+"# Use the following settings if you wish to make use of the network-console\n"
+"# component for remote installation over SSH. This only makes sense if you\n"
+"# intend to perform the remainder of the installation manually.\n"
+"#d-i anna/choose_modules string network-console\n"
+"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n"
+"#d-i network-console/password password r00tme\n"
+"#d-i network-console/password-again password r00tme"
 msgstr ""
 
 #. Tag: title
@@ -1008,36 +1331,48 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:820
 #, no-c-format
-msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
+msgid ""
+"Depending on the installation method you use, a mirror may be used to "
+"download additional components of the installer, to install the base system, "
+"and to set up the <filename>/etc/apt/sources.list</filename> for the "
+"installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:827
 #, no-c-format
-msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
+msgid ""
+"The parameter <classname>mirror/suite</classname> determines the suite for "
+"the installed system."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:832
 #, no-c-format
-msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this."
+msgid ""
+"The parameter <classname>mirror/udeb/suite</classname> determines the suite "
+"for additional components for the installer. It is only useful to set this "
+"if components are actually downloaded over the network and should match the "
+"suite that was used to build the initrd for the installation method used for "
+"the installation. Normally the installer will automatically use the correct "
+"value and there should be no need to set this."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:843
 #, no-c-format
 msgid ""
-      "# If you select ftp, the mirror/country string does not need to be set.\n"
-      "#d-i mirror/protocol string ftp\n"
-      "d-i mirror/country string manual\n"
-      "d-i mirror/http/hostname string &archive-mirror;\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "# Suite to install.\n"
-      "#d-i mirror/suite string testing\n"
-      "# Suite to use for loading installer components (optional).\n"
-      "#d-i mirror/udeb/suite string testing"
+"# If you select ftp, the mirror/country string does not need to be set.\n"
+"#d-i mirror/protocol string ftp\n"
+"d-i mirror/country string manual\n"
+"d-i mirror/http/hostname string &archive-mirror;\n"
+"d-i mirror/http/directory string /debian\n"
+"d-i mirror/http/proxy string\n"
+"\n"
+"# Suite to install.\n"
+"#d-i mirror/suite string testing\n"
+"# Suite to use for loading installer components (optional).\n"
+"#d-i mirror/udeb/suite string testing"
 msgstr ""
 
 #. Tag: title
@@ -1049,57 +1384,73 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:849
 #, no-c-format
-msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
+msgid ""
+"The password for the root account and name and password for a first regular "
+"user's account can be preseeded. For the passwords you can use either clear "
+"text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:856
 #, no-c-format
-msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
+msgid ""
+"Be aware that preseeding passwords is not completely secure as everyone with "
+"access to the preconfiguration file will have the knowledge of these "
+"passwords. Using MD5 hashes is considered slightly better in terms of "
+"security but it might also give a false sense of security as access to a MD5 "
+"hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:866
 #, no-c-format
 msgid ""
-      "# Skip creation of a root account (normal user account will be able to\n"
-      "# use sudo).\n"
-      "#d-i passwd/root-login boolean false\n"
-      "# Alternatively, to skip creation of a normal user account.\n"
-      "#d-i passwd/make-user boolean false\n"
-      "\n"
-      "# Root password, either in clear text\n"
-      "#d-i passwd/root-password password r00tme\n"
-      "#d-i passwd/root-password-again password r00tme\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/root-password-crypted password [MD5 hash]\n"
-      "\n"
-      "# To create a normal user account.\n"
-      "#d-i passwd/user-fullname string Debian User\n"
-      "#d-i passwd/username string debian\n"
-      "# Normal user's password, either in clear text\n"
-      "#d-i passwd/user-password password insecure\n"
-      "#d-i passwd/user-password-again password insecure\n"
-      "# or encrypted using an MD5 hash.\n"
-      "#d-i passwd/user-password-crypted password [MD5 hash]\n"
-      "# Create the first user with the specified UID instead of the default.\n"
-      "#d-i passwd/user-uid string 1010\n"
-      "\n"
-      "# The user account will be added to some standard initial groups. To\n"
-      "# override that, use this.\n"
-      "#d-i passwd/user-default-groups string audio cdrom video"
+"# Skip creation of a root account (normal user account will be able to\n"
+"# use sudo).\n"
+"#d-i passwd/root-login boolean false\n"
+"# Alternatively, to skip creation of a normal user account.\n"
+"#d-i passwd/make-user boolean false\n"
+"\n"
+"# Root password, either in clear text\n"
+"#d-i passwd/root-password password r00tme\n"
+"#d-i passwd/root-password-again password r00tme\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/root-password-crypted password [MD5 hash]\n"
+"\n"
+"# To create a normal user account.\n"
+"#d-i passwd/user-fullname string Debian User\n"
+"#d-i passwd/username string debian\n"
+"# Normal user's password, either in clear text\n"
+"#d-i passwd/user-password password insecure\n"
+"#d-i passwd/user-password-again password insecure\n"
+"# or encrypted using an MD5 hash.\n"
+"#d-i passwd/user-password-crypted password [MD5 hash]\n"
+"# Create the first user with the specified UID instead of the default.\n"
+"#d-i passwd/user-uid string 1010\n"
+"\n"
+"# The user account will be added to some standard initial groups. To\n"
+"# override that, use this.\n"
+"#d-i passwd/user-default-groups string audio cdrom video"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:868
 #, no-c-format
-msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
+msgid ""
+"The <classname>passwd/root-password-crypted</classname> and "
+"<classname>passwd/user-password-crypted</classname> variables can also be "
+"preseeded with <quote>!</quote> as their value. In that case, the "
+"corresponding account is disabled. This may be convenient for the root "
+"account, provided of course that an alternative method is set up to allow "
+"administrative activities or root login (for instance by using SSH key "
+"authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:878
 #, no-c-format
-msgid "The following command can be used to generate an MD5 hash for a password:"
+msgid ""
+"The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
@@ -1118,17 +1469,17 @@ msgstr ""
 #: preseed.xml:890
 #, no-c-format
 msgid ""
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "d-i clock-setup/utc boolean true\n"
-      "\n"
-      "# You may set this to any valid setting for $TZ; see the contents of\n"
-      "# /usr/share/zoneinfo/ for valid values.\n"
-      "d-i time/zone string US/Eastern\n"
-      "\n"
-      "# Controls whether to use NTP to set the clock during the install\n"
-      "d-i clock-setup/ntp boolean true\n"
-      "# NTP server to use. The default is almost always fine here.\n"
-      "#d-i clock-setup/ntp-server string ntp.example.com"
+"# Controls whether or not the hardware clock is set to UTC.\n"
+"d-i clock-setup/utc boolean true\n"
+"\n"
+"# You may set this to any valid setting for $TZ; see the contents of\n"
+"# /usr/share/zoneinfo/ for valid values.\n"
+"d-i time/zone string US/Eastern\n"
+"\n"
+"# Controls whether to use NTP to set the clock during the install\n"
+"d-i clock-setup/ntp boolean true\n"
+"# NTP server to use. The default is almost always fine here.\n"
+"#d-i clock-setup/ntp-server string ntp.example.com"
 msgstr ""
 
 #. Tag: title
@@ -1140,25 +1491,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:896
 #, no-c-format
-msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file."
+msgid ""
+"Using preseeding to partition the harddisk is limited to what is supported "
+"by <classname>partman-auto</classname>. You can choose to partition either "
+"existing free space on a disk or a whole disk. The layout of the disk can be "
+"determined by using a predefined recipe, a custom recipe from a recipe file "
+"or a recipe included in the preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:904
 #, no-c-format
-msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install."
+msgid ""
+"Preseeding of advanced partition setups using RAID, LVM and encryption is "
+"supported, but not with the full flexibility possible when partitioning "
+"during a non-preseeded install."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:910
 #, no-c-format
-msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases."
+msgid ""
+"The examples below only provide basic information on the use of recipes. For "
+"detailed information see the files <filename>partman-auto-recipe.txt</"
+"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in "
+"the <classname>debian-installer</classname> package. Both files are also "
+"available from the <ulink url=\"&url-d-i-gitweb-doc-devel;\">&d-i; source "
+"repository</ulink>. Note that the supported functionality may change between "
+"releases."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:924
 #, no-c-format
-msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
+msgid ""
+"The identification of disks is dependent on the order in which their drivers "
+"are loaded. If there are multiple disks in the system, make very sure the "
+"correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: title
@@ -1171,76 +1540,79 @@ msgstr ""
 #: preseed.xml:935
 #, no-c-format
 msgid ""
-      "# If the system has free space you can choose to only partition that space.\n"
-      "# This is only honoured if partman-auto/method (below) is not set.\n"
-      "#d-i partman-auto/init_automatically_partition select biggest_free\n"
-      "\n"
-      "# Alternatively, you may specify a disk to partition. If the system has only\n"
-      "# one disk the installer will default to using that, but otherwise the device\n"
-      "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
-      "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
-      "# For example, to use the first SCSI/SATA hard disk:\n"
-      "#d-i partman-auto/disk string /dev/sda\n"
-      "# In addition, you'll need to specify the method to use.\n"
-      "# The presently available methods are:\n"
-      "# - regular: use the usual partition types for your architecture\n"
-      "# - lvm:     use LVM to partition the disk\n"
-      "# - crypto:  use LVM within an encrypted partition\n"
-      "d-i partman-auto/method string lvm\n"
-      "\n"
-      "# If one of the disks that are going to be automatically partitioned\n"
-      "# contains an old LVM configuration, the user will normally receive a\n"
-      "# warning. This can be preseeded away...\n"
-      "d-i partman-lvm/device_remove_lvm boolean true\n"
-      "# The same applies to pre-existing software RAID array:\n"
-      "d-i partman-md/device_remove_md boolean true\n"
-      "# And the same goes for the confirmation to write the lvm partitions.\n"
-      "d-i partman-lvm/confirm boolean true\n"
-      "d-i partman-lvm/confirm_nooverwrite boolean true\n"
-      "\n"
-      "# You can choose one of the three predefined partitioning recipes:\n"
-      "# - atomic: all files in one partition\n"
-      "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
-      "d-i partman-auto/choose_recipe select atomic\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe into the preconfiguration file in one\n"
-      "# (logical) line. This example creates a small /boot partition, suitable\n"
-      "# swap, and uses the rest of the space for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string                         \\\n"
-      "#      boot-root ::                                            \\\n"
-      "#              40 50 100 ext3                                  \\\n"
-      "#                      $primary{ } $bootable{ }                \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ /boot }                     \\\n"
-      "#              .                                               \\\n"
-      "#              500 10000 1000000000 ext3                       \\\n"
-      "#                      method{ format } format{ }              \\\n"
-      "#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
-      "#                      mountpoint{ / }                         \\\n"
-      "#              .                                               \\\n"
-      "#              64 512 300% linux-swap                          \\\n"
-      "#                      method{ swap } format{ }                \\\n"
-      "#              .\n"
-      "\n"
-      "# The full recipe format is documented in the file partman-auto-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository. This also documents how to specify settings such as file\n"
-      "# system labels, volume group names and which physical devices to include\n"
-      "# in a volume group.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation, provided\n"
-      "# that you told it what to do using one of the methods above.\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# If the system has free space you can choose to only partition that space.\n"
+"# This is only honoured if partman-auto/method (below) is not set.\n"
+"#d-i partman-auto/init_automatically_partition select biggest_free\n"
+"\n"
+"# Alternatively, you may specify a disk to partition. If the system has "
+"only\n"
+"# one disk the installer will default to using that, but otherwise the "
+"device\n"
+"# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n"
+"# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n"
+"# For example, to use the first SCSI/SATA hard disk:\n"
+"#d-i partman-auto/disk string /dev/sda\n"
+"# In addition, you'll need to specify the method to use.\n"
+"# The presently available methods are:\n"
+"# - regular: use the usual partition types for your architecture\n"
+"# - lvm:     use LVM to partition the disk\n"
+"# - crypto:  use LVM within an encrypted partition\n"
+"d-i partman-auto/method string lvm\n"
+"\n"
+"# If one of the disks that are going to be automatically partitioned\n"
+"# contains an old LVM configuration, the user will normally receive a\n"
+"# warning. This can be preseeded away...\n"
+"d-i partman-lvm/device_remove_lvm boolean true\n"
+"# The same applies to pre-existing software RAID array:\n"
+"d-i partman-md/device_remove_md boolean true\n"
+"# And the same goes for the confirmation to write the lvm partitions.\n"
+"d-i partman-lvm/confirm boolean true\n"
+"d-i partman-lvm/confirm_nooverwrite boolean true\n"
+"\n"
+"# You can choose one of the three predefined partitioning recipes:\n"
+"# - atomic: all files in one partition\n"
+"# - home:   separate /home partition\n"
+"# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+"d-i partman-auto/choose_recipe select atomic\n"
+"\n"
+"# Or provide a recipe of your own...\n"
+"# If you have a way to get a recipe file into the d-i environment, you can\n"
+"# just point at it.\n"
+"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
+"\n"
+"# If not, you can put an entire recipe into the preconfiguration file in "
+"one\n"
+"# (logical) line. This example creates a small /boot partition, suitable\n"
+"# swap, and uses the rest of the space for the root partition:\n"
+"#d-i partman-auto/expert_recipe string                         \\\n"
+"#      boot-root ::                                            \\\n"
+"#              40 50 100 ext3                                  \\\n"
+"#                      $primary{ } $bootable{ }                \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ /boot }                     \\\n"
+"#              .                                               \\\n"
+"#              500 10000 1000000000 ext3                       \\\n"
+"#                      method{ format } format{ }              \\\n"
+"#                      use_filesystem{ } filesystem{ ext3 }    \\\n"
+"#                      mountpoint{ / }                         \\\n"
+"#              .                                               \\\n"
+"#              64 512 300% linux-swap                          \\\n"
+"#                      method{ swap } format{ }                \\\n"
+"#              .\n"
+"\n"
+"# The full recipe format is documented in the file partman-auto-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository. This also documents how to specify settings such as file\n"
+"# system labels, volume group names and which physical devices to include\n"
+"# in a volume group.\n"
+"\n"
+"# This makes partman automatically partition without confirmation, provided\n"
+"# that you told it what to do using one of the methods above.\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1252,73 +1624,84 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:940
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices."
+msgid ""
+"You can also use preseeding to set up partitions on software RAID arrays. "
+"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and "
+"specifying spare devices."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:946
 #, no-c-format
-msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid ""
+"If you are using RAID 1, you can preseed grub to install to all devices used "
+"in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:953
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
+msgid ""
+"This type of automated partitioning is easy to get wrong. It is also "
+"functionality that receives relatively little testing from the developers of "
+"&d-i;. The responsibility to get the various recipes right (so they make "
+"sense and don't conflict) lies with the user. Check <filename>/var/log/"
+"syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:963
 #, no-c-format
 msgid ""
-      "# The method should be set to \"raid\".\n"
-      "#d-i partman-auto/method string raid\n"
-      "# Specify the disks to be partitioned. They will all get the same layout,\n"
-      "# so this will only work if the disks are the same size.\n"
-      "#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
-      "\n"
-      "# Next you need to specify the physical partitions that will be used. \n"
-      "#d-i partman-auto/expert_recipe string \\\n"
-      "#      multiraid ::                                         \\\n"
-      "#              1000 5000 4000 raid                          \\\n"
-      "#                      $primary{ } method{ raid }           \\\n"
-      "#              .                                            \\\n"
-      "#              64 512 300% raid                             \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .                                            \\\n"
-      "#              500 10000 1000000000 raid                    \\\n"
-      "#                      method{ raid }                       \\\n"
-      "#              .\n"
-      "\n"
-      "# Last you need to specify how the previously defined partitions will be\n"
-      "# used in the RAID setup. Remember to use the correct partition numbers\n"
-      "# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
-      "# devices are separated using \"#\".\n"
-      "# Parameters are:\n"
-      "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
-      "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "\n"
-      "#d-i partman-auto-raid/recipe string \\\n"
-      "#    1 2 0 ext3 /                    \\\n"
-      "#          /dev/sda1#/dev/sdb1       \\\n"
-      "#    .                               \\\n"
-      "#    1 2 0 swap -                    \\\n"
-      "#          /dev/sda5#/dev/sdb5       \\\n"
-      "#    .                               \\\n"
-      "#    0 2 0 ext3 /home                \\\n"
-      "#          /dev/sda6#/dev/sdb6       \\\n"
-      "#    .\n"
-      "\n"
-      "# For additional information see the file partman-auto-raid-recipe.txt\n"
-      "# included in the 'debian-installer' package or available from D-I source\n"
-      "# repository.\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman-md/confirm boolean true\n"
-      "d-i partman-partitioning/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select finish\n"
-      "d-i partman/confirm boolean true\n"
-      "d-i partman/confirm_nooverwrite boolean true"
+"# The method should be set to \"raid\".\n"
+"#d-i partman-auto/method string raid\n"
+"# Specify the disks to be partitioned. They will all get the same layout,\n"
+"# so this will only work if the disks are the same size.\n"
+"#d-i partman-auto/disk string /dev/sda /dev/sdb\n"
+"\n"
+"# Next you need to specify the physical partitions that will be used. \n"
+"#d-i partman-auto/expert_recipe string \\\n"
+"#      multiraid ::                                         \\\n"
+"#              1000 5000 4000 raid                          \\\n"
+"#                      $primary{ } method{ raid }           \\\n"
+"#              .                                            \\\n"
+"#              64 512 300% raid                             \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .                                            \\\n"
+"#              500 10000 1000000000 raid                    \\\n"
+"#                      method{ raid }                       \\\n"
+"#              .\n"
+"\n"
+"# Last you need to specify how the previously defined partitions will be\n"
+"# used in the RAID setup. Remember to use the correct partition numbers\n"
+"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n"
+"# devices are separated using \"#\".\n"
+"# Parameters are:\n"
+"# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;"
+"mountpoint&gt; \\\n"
+"#          &lt;devices&gt; &lt;sparedevices&gt;\n"
+"\n"
+"#d-i partman-auto-raid/recipe string \\\n"
+"#    1 2 0 ext3 /                    \\\n"
+"#          /dev/sda1#/dev/sdb1       \\\n"
+"#    .                               \\\n"
+"#    1 2 0 swap -                    \\\n"
+"#          /dev/sda5#/dev/sdb5       \\\n"
+"#    .                               \\\n"
+"#    0 2 0 ext3 /home                \\\n"
+"#          /dev/sda6#/dev/sdb6       \\\n"
+"#    .\n"
+"\n"
+"# For additional information see the file partman-auto-raid-recipe.txt\n"
+"# included in the 'debian-installer' package or available from D-I source\n"
+"# repository.\n"
+"\n"
+"# This makes partman automatically partition without confirmation.\n"
+"d-i partman-md/confirm boolean true\n"
+"d-i partman-partitioning/confirm_write_new_label boolean true\n"
+"d-i partman/choose_partition select finish\n"
+"d-i partman/confirm boolean true\n"
+"d-i partman/confirm_nooverwrite boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1330,29 +1713,44 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:969
 #, no-c-format
-msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead."
+msgid ""
+"Normally, filesystems are mounted using a universally unique identifier "
+"(UUID) as a key; this allows them to be mounted properly even if their "
+"device name changes. UUIDs are long and difficult to read, so, if you "
+"prefer, the installer can mount filesystems based on the traditional device "
+"names, or based on a label you assign. If you ask the installer to mount by "
+"label, any filesystems without a label will be mounted using a UUID instead."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:978
 #, no-c-format
-msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs."
+msgid ""
+"Devices with stable names, such as LVM logical volumes, will continue to use "
+"their traditional names rather than UUIDs."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:985
 #, no-c-format
-msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random."
+msgid ""
+"Traditional device names may change based on the order in which the kernel "
+"discovers devices at boot, which may cause the wrong filesystem to be "
+"mounted. Similarly, labels are likely to clash if you plug in a new disk or "
+"a USB drive, and if that happens your system's behaviour when started will "
+"be random."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:995
 #, no-c-format
 msgid ""
-      "# The default is to mount by UUID, but you can also choose \"traditional\" to\n"
-      "# use traditional device names, or \"label\" to try filesystem labels before\n"
-      "# falling back to UUIDs.\n"
-      "#d-i partman/mount_style select uuid"
+"# The default is to mount by UUID, but you can also choose \"traditional\" "
+"to\n"
+"# use traditional device names, or \"label\" to try filesystem labels "
+"before\n"
+"# falling back to UUIDs.\n"
+"#d-i partman/mount_style select uuid"
 msgstr ""
 
 #. Tag: title
@@ -1364,21 +1762,25 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1002
 #, no-c-format
-msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
+msgid ""
+"There is actually not very much that can be preseeded for this stage of the "
+"installation. The only questions asked concern the installation of the "
+"kernel."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1009
 #, no-c-format
 msgid ""
-      "# Configure APT to not install recommended packages by default. Use of this\n"
-      "# option can result in an incomplete system and should only be used by very\n"
-      "# experienced users.\n"
-      "#d-i base-installer/install-recommends boolean false\n"
-      "\n"
-      "# The kernel image (meta) package to be installed; \"none\" can be used if no\n"
-      "# kernel is to be installed.\n"
-      "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
+"# Configure APT to not install recommended packages by default. Use of this\n"
+"# option can result in an incomplete system and should only be used by very\n"
+"# experienced users.\n"
+"#d-i base-installer/install-recommends boolean false\n"
+"\n"
+"# The kernel image (meta) package to be installed; \"none\" can be used if "
+"no\n"
+"# kernel is to be installed.\n"
+"#d-i base-installer/kernel/image string &kernelpackage;-2.6-486"
 msgstr ""
 
 #. Tag: title
@@ -1390,39 +1792,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1015
 #, no-c-format
-msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
+msgid ""
+"Setup of the <filename>/etc/apt/sources.list</filename> and basic "
+"configuration options is fully automated based on your installation method "
+"and answers to earlier questions. You can optionally add other (local) "
+"repositories."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1023
 #, no-c-format
 msgid ""
-      "# You can choose to install non-free and contrib software.\n"
-      "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true\n"
-      "# Uncomment this if you don't want to use a network mirror.\n"
-      "#d-i apt-setup/use_mirror boolean false\n"
-      "# Select which update services to use; define the mirrors to be used.\n"
-      "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
-      "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
-      "\n"
-      "# Additional repositories, local[0-9] available\n"
-      "#d-i apt-setup/local0/repository string \\\n"
-      "#       http://local.server/debian stable main\n"
-      "#d-i apt-setup/local0/comment string local server\n"
-      "# Enable deb-src lines\n"
-      "#d-i apt-setup/local0/source boolean true\n"
-      "# URL to the public key of the local repository; you must provide a key or\n"
-      "# apt will complain about the unauthenticated repository and so the\n"
-      "# sources.list line will be left commented out\n"
-      "#d-i apt-setup/local0/key string http://local.server/key\n"
-      "\n"
-      "# By default the installer requires that repositories be authenticated\n"
-      "# using a known gpg key. This setting can be used to disable that\n"
-      "# authentication. Warning: Insecure, not recommended.\n"
-      "#d-i debian-installer/allow_unauthenticated boolean true"
+"# You can choose to install non-free and contrib software.\n"
+"#d-i apt-setup/non-free boolean true\n"
+"#d-i apt-setup/contrib boolean true\n"
+"# Uncomment this if you don't want to use a network mirror.\n"
+"#d-i apt-setup/use_mirror boolean false\n"
+"# Select which update services to use; define the mirrors to be used.\n"
+"# Values shown below are the normal defaults.\n"
+"#d-i apt-setup/services-select multiselect security, volatile\n"
+"#d-i apt-setup/security_host string security.debian.org\n"
+"#d-i apt-setup/volatile_host string volatile.debian.org\n"
+"\n"
+"# Additional repositories, local[0-9] available\n"
+"#d-i apt-setup/local0/repository string \\\n"
+"#       http://local.server/debian stable main\n"
+"#d-i apt-setup/local0/comment string local server\n"
+"# Enable deb-src lines\n"
+"#d-i apt-setup/local0/source boolean true\n"
+"# URL to the public key of the local repository; you must provide a key or\n"
+"# apt will complain about the unauthenticated repository and so the\n"
+"# sources.list line will be left commented out\n"
+"#d-i apt-setup/local0/key string http://local.server/key\n"
+"\n"
+"# By default the installer requires that repositories be authenticated\n"
+"# using a known gpg key. This setting can be used to disable that\n"
+"# authentication. Warning: Insecure, not recommended.\n"
+"#d-i debian-installer/allow_unauthenticated boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1434,7 +1840,9 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1029
 #, no-c-format
-msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
+msgid ""
+"You can choose to install any combination of tasks that are available. "
+"Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
@@ -1506,35 +1914,43 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1072
 #, no-c-format
-msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
+msgid ""
+"You can also choose to install no tasks, and force the installation of a set "
+"of packages in some other way. We recommend always including the "
+"<userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1078
 #, no-c-format
-msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
+msgid ""
+"If you want to install some individual packages in addition to packages "
+"installed by tasks, you can use the parameter <classname>pkgsel/include</"
+"classname>. The value of this parameter can be a list of packages separated "
+"by either commas or spaces, which allows it to be used easily on the kernel "
+"command line as well."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1088
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
-      "\n"
-      "# Individual additional packages to install\n"
-      "#d-i pkgsel/include string openssh-server build-essential\n"
-      "# Whether to upgrade packages after debootstrap.\n"
-      "# Allowed values: none, safe-upgrade, full-upgrade\n"
-      "#d-i pkgsel/upgrade select none\n"
-      "\n"
-      "# Some versions of the installer can report back on what software you have\n"
-      "# installed, and what software you use. The default is not to report back,\n"
-      "# but sending reports helps the project determine what software is most\n"
-      "# popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
+"#tasksel tasksel/first multiselect standard, web-server\n"
+"# If the desktop task is selected, install the kde and xfce desktops\n"
+"# instead of the default gnome desktop.\n"
+"#tasksel tasksel/desktop multiselect kde, xfce\n"
+"\n"
+"# Individual additional packages to install\n"
+"#d-i pkgsel/include string openssh-server build-essential\n"
+"# Whether to upgrade packages after debootstrap.\n"
+"# Allowed values: none, safe-upgrade, full-upgrade\n"
+"#d-i pkgsel/upgrade select none\n"
+"\n"
+"# Some versions of the installer can report back on what software you have\n"
+"# installed, and what software you use. The default is not to report back,\n"
+"# but sending reports helps the project determine what software is most\n"
+"# popular and include it on CDs.\n"
+"#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
 #. Tag: title
@@ -1547,49 +1963,56 @@ msgstr ""
 #: preseed.xml:1095
 #, no-c-format
 msgid ""
-      "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "# To also skip installing lilo, and install no bootloader, uncomment this\n"
-      "# too:\n"
-      "#d-i lilo-installer/skip boolean true</phrase>\n"
-      "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n"
-      "#d-i grub-installer/skip boolean true</phrase>\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if it also finds some other\n"
-      "# OS, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "# To install grub to multiple disks:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
-      "# To install to a particular device:\n"
-      "#d-i grub-installer/bootdev  string /dev/sda\n"
-      "\n"
-      "# Optional password for grub, either in clear text\n"
-      "#d-i grub-installer/password password r00tme\n"
-      "#d-i grub-installer/password-again password r00tme\n"
-      "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
-      "#d-i grub-installer/password-crypted password [MD5 hash]\n"
-      "\n"
-      "# Use the following option to add additional boot parameters for the\n"
-      "# installed system (if supported by the bootloader installer).\n"
-      "# Note: options passed to the installer will be added automatically.\n"
-      "#d-i debian-installer/add-kernel-opts string nousb"
+"<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If "
+"you want lilo installed\n"
+"# instead, uncomment this:\n"
+"#d-i grub-installer/skip boolean true\n"
+"# To also skip installing lilo, and install no bootloader, uncomment this\n"
+"# too:\n"
+"#d-i lilo-installer/skip boolean true</phrase>\n"
+"<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment "
+"this\n"
+"#d-i grub-installer/skip boolean true</phrase>\n"
+"\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
+"# if no other operating system is detected on the machine.\n"
+"d-i grub-installer/only_debian boolean true\n"
+"\n"
+"# This one makes grub-installer install to the MBR if it also finds some "
+"other\n"
+"# OS, which is less safe as it might not be able to boot that other OS.\n"
+"d-i grub-installer/with_other_os boolean true\n"
+"\n"
+"# Alternatively, if you want to install to a location other than the mbr,\n"
+"# uncomment and edit these lines:\n"
+"#d-i grub-installer/only_debian boolean false\n"
+"#d-i grub-installer/with_other_os boolean false\n"
+"#d-i grub-installer/bootdev  string (hd0,0)\n"
+"# To install grub to multiple disks:\n"
+"#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
+"# To install to a particular device:\n"
+"#d-i grub-installer/bootdev  string /dev/sda\n"
+"\n"
+"# Optional password for grub, either in clear text\n"
+"#d-i grub-installer/password password r00tme\n"
+"#d-i grub-installer/password-again password r00tme\n"
+"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n"
+"#d-i grub-installer/password-crypted password [MD5 hash]\n"
+"\n"
+"# Use the following option to add additional boot parameters for the\n"
+"# installed system (if supported by the bootloader installer).\n"
+"# Note: options passed to the installer will be added automatically.\n"
+"#d-i debian-installer/add-kernel-opts string nousb"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1097
 #, no-c-format
-msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
+msgid ""
+"An MD5 hash for a password for <classname>grub</classname> can be generated "
+"using <command>grub-md5-crypt</command>, or using the command from the "
+"example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
@@ -1602,23 +2025,23 @@ msgstr ""
 #: preseed.xml:1109
 #, no-c-format
 msgid ""
-      "# During installations from serial console, the regular virtual consoles\n"
-      "# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
-      "# line to prevent this.\n"
-      "#d-i finish-install/keep-consoles boolean true\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i finish-install/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false\n"
-      "\n"
-      "# This is how to make the installer shutdown when finished, but not\n"
-      "# reboot into the installed system.\n"
-      "#d-i debian-installer/exit/halt boolean true\n"
-      "# This will power off the machine instead of just halting it.\n"
-      "#d-i debian-installer/exit/poweroff boolean true"
+"# During installations from serial console, the regular virtual consoles\n"
+"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n"
+"# line to prevent this.\n"
+"#d-i finish-install/keep-consoles boolean true\n"
+"\n"
+"# Avoid that last message about the install being complete.\n"
+"d-i finish-install/reboot_in_progress note\n"
+"\n"
+"# This will prevent the installer from ejecting the CD during the reboot,\n"
+"# which is useful in some situations.\n"
+"#d-i cdrom-detect/eject boolean false\n"
+"\n"
+"# This is how to make the installer shutdown when finished, but not\n"
+"# reboot into the installed system.\n"
+"#d-i debian-installer/exit/halt boolean true\n"
+"# This will power off the machine instead of just halting it.\n"
+"#d-i debian-installer/exit/poweroff boolean true"
 msgstr ""
 
 #. Tag: title
@@ -1631,13 +2054,13 @@ msgstr ""
 #: preseed.xml:1116
 #, no-c-format
 msgid ""
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file"
+"# Depending on what software you choose to install, or if things go wrong\n"
+"# during the installation process, it's possible that other questions may\n"
+"# be asked. You can preseed those too, of course. To get a list of every\n"
+"# possible question that could be asked during an install, do an\n"
+"# installation, and then run these commands:\n"
+"#   debconf-get-selections --installer > file\n"
+"#   debconf-get-selections >> file"
 msgstr ""
 
 #. Tag: title
@@ -1655,33 +2078,36 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1127
 #, no-c-format
-msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
+msgid ""
+"A very powerful and flexible option offered by the preconfiguration tools is "
+"the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1135
 #, no-c-format
 msgid ""
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preconfiguration file like this one. Only use preconfiguration files from\n"
-      "# trusted locations! To drive that home, and because it's generally useful,\n"
-      "# here's a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "# This command is run immediately before the partitioner starts. It may be\n"
-      "# useful to apply dynamic partitioner preseeding that depends on the state\n"
-      "# of the disks (which may not be visible when preseed/early_command runs).\n"
-      "#d-i partman/early_command \\\n"
-      "#       string debconf-set partman-auto/disk \"$(list-devices disk | head -n1)\"\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory. You can chroot to /target and use it\n"
-      "# directly, or use the apt-install and in-target commands to easily install\n"
-      "# packages and run commands in the target system.\n"
-      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
+"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
+"# for attempts at buffer overflows or other exploits of the values of a\n"
+"# preconfiguration file like this one. Only use preconfiguration files from\n"
+"# trusted locations! To drive that home, and because it's generally useful,\n"
+"# here's a way to run any shell command you'd like inside the installer,\n"
+"# automatically.\n"
+"\n"
+"# This first command is run as early as possible, just after\n"
+"# preseeding is read.\n"
+"#d-i preseed/early_command string anna-install some-udeb\n"
+"# This command is run immediately before the partitioner starts. It may be\n"
+"# useful to apply dynamic partitioner preseeding that depends on the state\n"
+"# of the disks (which may not be visible when preseed/early_command runs).\n"
+"#d-i partman/early_command \\\n"
+"#       string debconf-set partman-auto/disk \"$(list-devices disk | head -"
+"n1)\"\n"
+"# This command is run just before the install finishes, but when there is\n"
+"# still a usable /target directory. You can chroot to /target and use it\n"
+"# directly, or use the apt-install and in-target commands to easily install\n"
+"# packages and run commands in the target system.\n"
+"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
 #. Tag: title
@@ -1694,28 +2120,51 @@ msgstr ""
 #: preseed.xml:1141
 #, no-c-format
 msgid ""
-      "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
-      "d-i foo/bar string value\n"
-      "d-i foo/bar seen false\n"
-      "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file."
+"It is possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a question. <informalexample><screen>\n"
+"d-i foo/bar string value\n"
+"d-i foo/bar seen false\n"
+"</screen></informalexample> The same effect can be achieved for "
+"<emphasis>all</emphasis> questions by setting the parameter "
+"<classname>preseed/interactive=true</classname> at the boot prompt. This can "
+"also be useful for testing or debugging your preconfiguration file."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1155
 #, no-c-format
-msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>."
+msgid ""
+"Note that the <quote>d-i</quote> owner should only be used for variables "
+"used in the installer itself. For variables belonging to packages installed "
+"on the target system, you should use the name of that package instead. See "
+"the footnote to <xref linkend=\"preseed-bootparms\"/>."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1162
 #, no-c-format
-msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
+msgid ""
+"If you are preseeding using boot parameters, you can make the installer ask "
+"the corresponding question by using the <quote>?=</quote> operator, i.e. "
+"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?"
+"=<replaceable>value</replaceable></userinput> (or "
+"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</"
+"replaceable>?=<replaceable>value</replaceable></userinput>). This will of "
+"course only have effect for parameters that correspond to questions that are "
+"actually displayed during an installation and not for <quote>internal</"
+"quote> parameters."
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1172
 #, no-c-format
-msgid "For more debugging information, use the boot parameter <classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</classname> to print much more detail about the current settings of each variable and about its progress through each package's installation scripts."
+msgid ""
+"For more debugging information, use the boot parameter "
+"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</"
+"classname> to print much more detail about the current settings of each "
+"variable and about its progress through each package's installation scripts."
 msgstr ""
 
 #. Tag: title
@@ -1727,40 +2176,50 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:1185
 #, no-c-format
-msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
+msgid ""
+"It is possible to include other preconfiguration files from a "
+"preconfiguration file. Any settings in those files will override pre-"
+"existing settings from files loaded earlier. This makes it possible to put, "
+"for example, general networking settings for your location in one file and "
+"more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
 #: preseed.xml:1195
 #, no-c-format
 msgid ""
-      "# More than one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preconfiguration file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# The installer can optionally verify checksums of preconfiguration files\n"
-      "# before using them. Currently only md5sums are supported, list the md5sums\n"
-      "# in the same order as the list of files to include.\n"
-      "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preconfiguration files, includes those files. \n"
-      "#d-i preseed/include_command \\\n"
-      "#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
-      "\n"
-      "# Most flexibly of all, this downloads a program and runs it. The program\n"
-      "# can use commands such as debconf-set to manipulate the debconf database.\n"
-      "# More than one script can be listed, separated by spaces.\n"
-      "# Note that if the filenames are relative, they are taken from the same\n"
-      "# directory as the preconfiguration file that runs them.\n"
-      "#d-i preseed/run string foo.sh"
+"# More than one file can be listed, separated by spaces; all will be\n"
+"# loaded. The included files can have preseed/include directives of their\n"
+"# own as well. Note that if the filenames are relative, they are taken from\n"
+"# the same directory as the preconfiguration file that includes them.\n"
+"#d-i preseed/include string x.cfg\n"
+"\n"
+"# The installer can optionally verify checksums of preconfiguration files\n"
+"# before using them. Currently only md5sums are supported, list the md5sums\n"
+"# in the same order as the list of files to include.\n"
+"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n"
+"\n"
+"# More flexibly, this runs a shell command and if it outputs the names of\n"
+"# preconfiguration files, includes those files. \n"
+"#d-i preseed/include_command \\\n"
+"#      string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n"
+"\n"
+"# Most flexibly of all, this downloads a program and runs it. The program\n"
+"# can use commands such as debconf-set to manipulate the debconf database.\n"
+"# More than one script can be listed, separated by spaces.\n"
+"# Note that if the filenames are relative, they are taken from the same\n"
+"# directory as the preconfiguration file that runs them.\n"
+"#d-i preseed/run string foo.sh"
 msgstr ""
 
 #. Tag: para
 #: preseed.xml:1197
 #, no-c-format
-msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
+msgid ""
+"It is also possible to chainload from the initrd or file preseeding phase, "
+"into network preseeding by setting preseed/url in the earlier files. This "
+"will cause network preseeding to be performed when the network comes up. You "
+"need to be careful when doing this, since there will be two distinct runs at "
+"preseeding, meaning for example that you get another chance to run the "
+"preseed/early command, the second one happening after the network comes up."
 msgstr ""
-