Update of POT and PO files for the manual

1 files changed, 1013 insertions, 191 deletions

diff --git a/po/fi/hardware.po b/po/fi/hardware.po
index b9600305a..674d8f74b 100644
--- a/po/fi/hardware.po
+++ b/po/fi/hardware.po
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Debian Installation Guide hardware\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-08-18 17:32+0000\n"
+"POT-Creation-Date: 2006-09-08 22:58+0000\n"
 "PO-Revision-Date: 2006-09-08 10:41+0300\n"
 "Last-Translator: Tapio Lehtonen <tale@debian.org>\n"
 "Language-Team: Finnish <debian-l10n-finnish@lists.debian.org>\n"
@@ -22,8 +22,13 @@ msgstr "Laitteistovaatimukset"
 #. 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 Linux."
-msgstr "Tässä luvussa on tietoa laitteista joilla pääsee alkuun Debianin kanssa. Mukana on myös viitteitä lisätietoon GNU:n ja Linuxin tukemista laitteista."
+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 Linux."
+msgstr ""
+"Tässä luvussa on tietoa laitteista joilla pääsee alkuun Debianin kanssa. "
+"Mukana on myös viitteitä lisätietoon GNU:n ja Linuxin tukemista laitteista."
 
 #. Tag: title
 #: hardware.xml:20
@@ -34,14 +39,32 @@ msgstr "Tuetut laitteet"
 #. Tag: para
 #: hardware.xml:21
 #, no-c-format
-msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux 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."
-msgstr "Debianin laitevaatimukset eivät ole ankarampia kuin Linuxin ytimen ja GNU-työkalusarjan vaatimukset. Niimpä kaikki laitealustat joille on siirretty Linux-ydin, libc, <command>gcc</command>, jne, ja joille on olemassa Debianin siirros, kelpaavat Debianille. Debianin Siirrokset-sivulta osoitteessa <ulink url=\"&url-ports;\"></ulink> löytyy yksityiskohtaisempaa tietoa laitealustan &arch-title; järjestelmistä joissa Debiania on kokeiltu."
+msgid ""
+"Debian does not impose hardware requirements beyond the requirements of the "
+"Linux kernel and the GNU tool-sets. Therefore, any architecture or platform "
+"to which the Linux 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."
+msgstr ""
+"Debianin laitevaatimukset eivät ole ankarampia kuin Linuxin ytimen ja GNU-"
+"työkalusarjan vaatimukset. Niimpä kaikki laitealustat joille on siirretty "
+"Linux-ydin, libc, <command>gcc</command>, jne, ja joille on olemassa "
+"Debianin siirros, kelpaavat Debianille. Debianin Siirrokset-sivulta "
+"osoitteessa <ulink url=\"&url-ports;\"></ulink> löytyy yksityiskohtaisempaa "
+"tietoa laitealustan &arch-title; järjestelmistä joissa Debiania on kokeiltu."
 
 #. 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."
-msgstr "Tässä luvussa ei kerrota kaikkia laitealustan &arch-title; tuettuja laitteistokokoonpanoja, vaan kerrotaan yleisempää tietoa ja annetaan viitteet joista lisätietoa löytyy."
+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 ""
+"Tässä luvussa ei kerrota kaikkia laitealustan &arch-title; tuettuja "
+"laitteistokokoonpanoja, vaan kerrotaan yleisempää tietoa ja annetaan "
+"viitteet joista lisätietoa löytyy."
 
 #. Tag: title
 #: hardware.xml:41
@@ -51,9 +74,13 @@ msgstr "Tuetut laitealustat"
 
 #. Tag: para
 #: hardware.xml:42
-#, no-c-format
-msgid "Debian &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
-msgstr "Debianin versio &release; tukee yhtätoista laitealustaa ja kunkin laitealustan useaa <quote>versiota</quote>. "
+#, fuzzy, no-c-format
+msgid ""
+"Debian &release; supports twelve major architectures and several variations "
+"of each architecture known as <quote>flavors</quote>."
+msgstr ""
+"Debianin versio &release; tukee yhtätoista laitealustaa ja kunkin "
+"laitealustan useaa <quote>versiota</quote>. "
 
 #. Tag: entry
 #: hardware.xml:53
@@ -308,7 +335,8 @@ msgid "r4k-kn04"
 msgstr "r4k-kn04"
 
 #. Tag: entry
-#: hardware.xml:135 hardware.xml:1082 hardware.xml:1092 hardware.xml:1097 hardware.xml:1107
+#: hardware.xml:135 hardware.xml:1082 hardware.xml:1092 hardware.xml:1097
+#: hardware.xml:1107
 #, no-c-format
 msgid "r3k-kn02"
 msgstr "r3k-kn02"
@@ -508,17 +536,44 @@ msgstr "tape"
 #. Tag: para
 #: hardware.xml:201
 #, no-c-format
-msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. 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 "Tässä ohjeessa käsitellään asennusta <emphasis>&arch-title;</emphasis>-laitealustalle. Muiden Debianin tukemien laitealustojen tietoja kannattaa etsiä Debianin <ulink url=\"http://www.debian.org/ports/\">Siirrokset</ulink>-sivuilta."
+msgid ""
+"This document covers installation for the <emphasis>&arch-title;</emphasis> "
+"architecture. 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 ""
+"Tässä ohjeessa käsitellään asennusta <emphasis>&arch-title;</emphasis>-"
+"laitealustalle. Muiden Debianin tukemien laitealustojen tietoja kannattaa "
+"etsiä Debianin <ulink url=\"http://www.debian.org/ports/\">Siirrokset</"
+"ulink>-sivuilta."
 
 #. Tag: para
 #: hardware.xml:209
 #, no-c-format
-msgid "This is the first official release of &debian; 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. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
-msgstr "Tämä on &debian;in ensimmäinen virallinen julkistus laitealustalle &arch-title;. Mielestämme se on koitoksissa osoittautunut riittävän hyväksi julkaistavaksi. Koska sitä ei kuitenkaan ole käytetty yhtä laajalti (eikä käyttäjiä ole ollut yhtä paljon) kuin Debiania eräillä muilla laitealustoilla, saattaa löytyä muutamia vikoja. Ilmoita vioista Debianin <ulink url=\"&url-bts;\">Vianseurantajärjestelmällä</ulink>; muista mainita vian ilmenevän laitealustalla &arch-title;. Saattaa olla tarpeen käyttää myös postituslistaa <ulink url=\"&url-list-subscribe;\">debian-&arch-listname;</ulink>."
+msgid ""
+"This is the first official release of &debian; 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. It can be necessary to use the <ulink url=\"&url-list-subscribe;"
+"\">debian-&arch-listname; mailing list</ulink> as well."
+msgstr ""
+"Tämä on &debian;in ensimmäinen virallinen julkistus laitealustalle &arch-"
+"title;. Mielestämme se on koitoksissa osoittautunut riittävän hyväksi "
+"julkaistavaksi. Koska sitä ei kuitenkaan ole käytetty yhtä laajalti (eikä "
+"käyttäjiä ole ollut yhtä paljon) kuin Debiania eräillä muilla "
+"laitealustoilla, saattaa löytyä muutamia vikoja. Ilmoita vioista Debianin "
+"<ulink url=\"&url-bts;\">Vianseurantajärjestelmällä</ulink>; muista mainita "
+"vian ilmenevän laitealustalla &arch-title;. Saattaa olla tarpeen käyttää "
+"myös postituslistaa <ulink url=\"&url-list-subscribe;\">debian-&arch-"
+"listname;</ulink>."
 
 #. Tag: title
-#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 hardware.xml:821 hardware.xml:907 hardware.xml:949 hardware.xml:1017 hardware.xml:1176 hardware.xml:1622
+#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802
+#: hardware.xml:821 hardware.xml:907 hardware.xml:949 hardware.xml:1017
+#: hardware.xml:1176 hardware.xml:1622
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr "Tuetut prosessorit, emolevyt ja näytönohjaimet"
@@ -526,20 +581,44 @@ msgstr "Tuetut prosessorit, emolevyt ja näytönohjaimet"
 #. Tag: para
 #: hardware.xml:232
 #, no-c-format
-msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks."
-msgstr "Kaikki tiedot tuetuista DEC Alpha -koneista löytyy ohjeesta <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. Tämän luvun on tarkoitus kertoa käynnistystaltioiden tukemista järjestelmistä."
+msgid ""
+"Complete information regarding supported DEC Alphas can be found at <ulink "
+"url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this "
+"section is to describe the systems supported by the boot disks."
+msgstr ""
+"Kaikki tiedot tuetuista DEC Alpha -koneista löytyy ohjeesta <ulink url="
+"\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. Tämän luvun on tarkoitus "
+"kertoa käynnistystaltioiden tukemista järjestelmistä."
 
 #. Tag: para
 #: hardware.xml:239
 #, no-c-format
-msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system."
-msgstr "Alpha-koneet jaetaan erilaisiin järjestelmätyyppeihin koska emolevyjä ja piirisarjoja on useita sukupolvia. Erilaiset järjestelmät (<quote>laitemallit</quote>) on usein rakennettu tyystin eri tavoilla ja ominaisuudetkin vaihtelevat. Näin ollen asennus ja erityisesti tietokoneen käynnistäminen vaihtelee järjestelmittäin."
+msgid ""
+"Alpha machines are subdivided into different system types because there are "
+"a number of generations of motherboard and supporting chipsets. Different "
+"systems (<quote>sub-architectures</quote>) often have radically different "
+"engineering and capabilities. Therefore, the process of installing and, more "
+"to the point, booting, can vary from system to system."
+msgstr ""
+"Alpha-koneet jaetaan erilaisiin järjestelmätyyppeihin koska emolevyjä ja "
+"piirisarjoja on useita sukupolvia. Erilaiset järjestelmät "
+"(<quote>laitemallit</quote>) on usein rakennettu tyystin eri tavoilla ja "
+"ominaisuudetkin vaihtelevat. Näin ollen asennus ja erityisesti tietokoneen "
+"käynnistäminen vaihtelee järjestelmittäin."
 
 #. Tag: para
 #: hardware.xml:247
 #, no-c-format
-msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:"
-msgstr "Seuraavassa taulukossa luetellaan Debianin asennusjärjestelmän tukemat laitemallit. Taulukosta ilmenee myös näiden laitemallien <emphasis>koodinimi</emphasis>. Tämä koodinimi on tiedettävä kun varsinaista asennusta aloitetaan:"
+msgid ""
+"The following table lists the system types supported by the Debian "
+"installation system. The table also indicates the <emphasis>code name</"
+"emphasis> for these system types. You'll need to know this code name when "
+"you actually begin the installation process:"
+msgstr ""
+"Seuraavassa taulukossa luetellaan Debianin asennusjärjestelmän tukemat "
+"laitemallit. Taulukosta ilmenee myös näiden laitemallien "
+"<emphasis>koodinimi</emphasis>. Tämä koodinimi on tiedettävä kun varsinaista "
+"asennusta aloitetaan:"
 
 #. Tag: entry
 #: hardware.xml:264
@@ -668,7 +747,8 @@ msgid "Mustang"
 msgstr "Mustang"
 
 #. Tag: entry
-#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328
+#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312
+#: hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328
 #, no-c-format
 msgid "avanti"
 msgstr "avanti"
@@ -902,7 +982,16 @@ msgid "Jensen"
 msgstr "Jensen"
 
 #. Tag: entry
-#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449 hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479 hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521 hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567 hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593 hardware.xml:597 hardware.xml:604 hardware.xml:608 hardware.xml:612 hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 hardware.xml:648 hardware.xml:652 hardware.xml:659 hardware.xml:663
+#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449
+#: hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479
+#: hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495
+#: hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521
+#: hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567
+#: hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593
+#: hardware.xml:597 hardware.xml:604 hardware.xml:608 hardware.xml:612
+#: hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628
+#: hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644
+#: hardware.xml:648 hardware.xml:652 hardware.xml:659 hardware.xml:663
 #, no-c-format
 msgid "<entry>N/A</entry>"
 msgstr "<entry>&mdash;</entry>"
@@ -938,13 +1027,15 @@ msgid "Personal WorkStation 433a"
 msgstr "Personal WorkStation 433a"
 
 #. Tag: entry
-#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422
+#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406
+#: hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422
 #, no-c-format
 msgid "Miata"
 msgstr "Miata"
 
 #. Tag: entry
-#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423
+#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407
+#: hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423
 #, no-c-format
 msgid "miata"
 msgstr "miata"
@@ -1274,13 +1365,15 @@ msgid "DeskStation AlphaPC164-UX"
 msgstr "DeskStation AlphaPC164-UX"
 
 #. Tag: entry
-#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551
+#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543
+#: hardware.xml:547 hardware.xml:551
 #, no-c-format
 msgid "Ruffian"
 msgstr "Ruffian"
 
 #. Tag: entry
-#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552
+#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544
+#: hardware.xml:548 hardware.xml:552
 #, no-c-format
 msgid "ruffian"
 msgstr "ruffian"
@@ -1630,14 +1723,27 @@ msgstr "<entry>xl</entry>"
 #. Tag: para
 #: hardware.xml:675
 #, no-c-format
-msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options."
-msgstr "Tiettävästi Debian &releasename; tukee asennusta kaikille alphan laitemalleille lukuunottamatta vain ARC:lle olevia Ruffian- ja XL-malleja sekä Titan-mallia, joka vaatii muutoksen ytimen käännösvalitsimiin."
+msgid ""
+"It is believed that Debian &releasename; supports installing on all alpha "
+"sub-architectures with the exception of the ARC-only Ruffian and XL sub-"
+"architectures and the Titan subarchitecture, which requires a change to the "
+"kernel compile options."
+msgstr ""
+"Tiettävästi Debian &releasename; tukee asennusta kaikille alphan "
+"laitemalleille lukuunottamatta vain ARC:lle olevia Ruffian- ja XL-malleja "
+"sekä Titan-mallia, joka vaatii muutoksen ytimen käännösvalitsimiin."
 
 #. Tag: para
 #: hardware.xml:691 hardware.xml:822
 #, 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."
-msgstr "Kaikki tiedot tuetuista oheislaitteista löytyvät ohjeesta <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. Tässä luvussa kerrotaan vain perusteet."
+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 ""
+"Kaikki tiedot tuetuista oheislaitteista löytyvät ohjeesta <ulink url=\"&url-"
+"hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. Tässä luvussa "
+"kerrotaan vain perusteet."
 
 #. Tag: title
 #: hardware.xml:699 hardware.xml:830 hardware.xml:990
@@ -1654,14 +1760,29 @@ msgstr "Sekä AMD64- että Intel Em64T-prosessorit ovat tuettuja."
 #. Tag: para
 #: hardware.xml:728
 #, 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 systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale."
-msgstr "Jokainen erilainen ARM-laitealusta vaatii oman ytimensä. Tästä syystä Debianin vakiojakelu tukee asennusta vain muutamalle yleisimmälle järjestelmälle. Debianin sovelluksia sitävastoin voi käyttää <emphasis>kaikilla</emphasis> ARM-prosessoreilla, mukaanlukien xscale."
+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 systems. The Debian userland however may be used by "
+"<emphasis>any</emphasis> ARM CPU including xscale."
+msgstr ""
+"Jokainen erilainen ARM-laitealusta vaatii oman ytimensä. Tästä syystä "
+"Debianin vakiojakelu tukee asennusta vain muutamalle yleisimmälle "
+"järjestelmälle. Debianin sovelluksia sitävastoin voi käyttää "
+"<emphasis>kaikilla</emphasis> ARM-prosessoreilla, mukaanlukien xscale."
 
 #. Tag: para
 #: hardware.xml:736
 #, 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."
-msgstr "Useimpia ARM-prosessoreita voi käyttää joko big endian tai little endian -toimintatiloissa. Nykyisistä järjestelmätoteutuksista enemmistö käyttää kuitenkin little endian -toimintatilaa. Debian tukee tällä hetkellä vain little endian ARM-järjestelmiä."
+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 ""
+"Useimpia ARM-prosessoreita voi käyttää joko big endian tai little endian -"
+"toimintatiloissa. Nykyisistä järjestelmätoteutuksista enemmistö käyttää "
+"kuitenkin little endian -toimintatilaa. Debian tukee tällä hetkellä vain "
+"little endian ARM-järjestelmiä."
 
 #. Tag: para
 #: hardware.xml:744
@@ -1678,8 +1799,18 @@ msgstr "Netwinder"
 #. Tag: para
 #: hardware.xml:752
 #, no-c-format
-msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)."
-msgstr "Tämä on itse asiassa nimi StronARM 110 -prosessoriin ja Intel 21285 Northbridge (tunnetaan myös nimellä Footbridge) -piirisarjaan perustuvalle ryhmälle koneita. Siihen kuuluvat koneet kuten: Netwinder (luultavasti eräs yleisimpiä ARM-koneita), CATS (tunnetaan myös nimellä EB110ATX), EBSA 285 ja Compaq personal server (cps eli skiff)."
+msgid ""
+"This is actually the name for the group of machines based upon the StrongARM "
+"110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises "
+"of machines like: Netwinder (possibly one of the most common ARM boxes), "
+"CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, "
+"aka skiff)."
+msgstr ""
+"Tämä on itse asiassa nimi StronARM 110 -prosessoriin ja Intel 21285 "
+"Northbridge (tunnetaan myös nimellä Footbridge) -piirisarjaan perustuvalle "
+"ryhmälle koneita. Siihen kuuluvat koneet kuten: Netwinder (luultavasti eräs "
+"yleisimpiä ARM-koneita), CATS (tunnetaan myös nimellä EB110ATX), EBSA 285 ja "
+"Compaq personal server (cps eli skiff)."
 
 #. Tag: term
 #: hardware.xml:765
@@ -1690,8 +1821,15 @@ msgstr "NSLU2"
 #. Tag: para
 #: hardware.xml:766
 #, no-c-format
-msgid "The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected."
-msgstr "Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) on pieni laite joka on tarkoitettu tallennustilan tarjoamiseen verkon kautta. Siinä on Ethernet-liitäntä ja kaksi USB-porttia joihin voi liittää kiintolevyjä."
+msgid ""
+"The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small "
+"device which allows you to easily provide storage via the network. It comes "
+"with an Ethernet connection and two USB ports to which hard drives can be "
+"connected."
+msgstr ""
+"Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) on pieni laite "
+"joka on tarkoitettu tallennustilan tarjoamiseen verkon kautta. Siinä on "
+"Ethernet-liitäntä ja kaksi USB-porttia joihin voi liittää kiintolevyjä."
 
 #. Tag: term
 #: hardware.xml:777
@@ -1702,31 +1840,92 @@ msgstr "<term>RiscPC</term>"
 #. Tag: para
 #: hardware.xml:778
 #, no-c-format
-msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers."
-msgstr "Tämä kone on vanhin tuettu laitteisto: se julkistettiin 1994. Siinä on RISC OS ROM:illa, ja Linux voidaan käynnistää tuosta käyttöjärjestelmästä linloaderin avulla. RiscPC:ssä on prosessorikortti moduulina, jossa tyypillisesti on 30 MHz 610, 40 MHz 710 tai 233 MHz Strongarm 110 -prosessori asennettuna. Emolevyllä on yhdysrakenteisena IDE, SVGA-näytönohjain, rinnakkaisportti, yksi sarjaportti, PS/2 näppäimistöportti ja epästandardi hiiriportti. Epästandardi moduulien laajennusväylä sallii kokoonpanosta riippuen enintään kahdeksan lisälaitekortin asennuksen, useille näistä moduuleista on ajurit Linuxissa."
+msgid ""
+"This machine is the oldest supported hardware: it was released in 1994. It "
+"has RISC OS in ROM, Linux can be booted from that OS using linloader. The "
+"RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or "
+"233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA "
+"video, parallel port, single serial port, PS/2 keyboard and proprietary "
+"mouse port. The proprietary module expansion bus allows for up to eight "
+"expansion cards to be fitted depending on configuration, several of these "
+"modules have Linux drivers."
+msgstr ""
+"Tämä kone on vanhin tuettu laitteisto: se julkistettiin 1994. Siinä on RISC "
+"OS ROM:illa, ja Linux voidaan käynnistää tuosta käyttöjärjestelmästä "
+"linloaderin avulla. RiscPC:ssä on prosessorikortti moduulina, jossa "
+"tyypillisesti on 30 MHz 610, 40 MHz 710 tai 233 MHz Strongarm 110 -"
+"prosessori asennettuna. Emolevyllä on yhdysrakenteisena IDE, SVGA-"
+"näytönohjain, rinnakkaisportti, yksi sarjaportti, PS/2 näppäimistöportti ja "
+"epästandardi hiiriportti. Epästandardi moduulien laajennusväylä sallii "
+"kokoonpanosta riippuen enintään kahdeksan lisälaitekortin asennuksen, "
+"useille näistä moduuleista on ajurit Linuxissa."
 
 #. Tag: para
 #: hardware.xml:803
-#, no-c-format, fuzzy
-msgid "The 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 "Tuettujen laitealustojen vivahteit??? on kaksi päälinjaa: PA-RISC 1.1 ja PA-RISC 2.0. PA-RISC 1.1 -laitealusta on suunnattu 32-bittisille prosessoreille kun taas 2.0 on suunnattu 64-bittisille. Joissain järjestelmissä on mahdollista suorittaa kumpaa ydintä vaan. Molemmissa tapauksissa käyttäjän sovellukset toimivat 32-bittisinä. 64-bittiset käyttäjän sovellukset ovat mahdollisia tulevaisuudessa."
+#, fuzzy, no-c-format
+msgid ""
+"The 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 ""
+"Tuettujen laitealustojen vivahteit??? on kaksi päälinjaa: PA-RISC 1.1 ja PA-"
+"RISC 2.0. PA-RISC 1.1 -laitealusta on suunnattu 32-bittisille prosessoreille "
+"kun taas 2.0 on suunnattu 64-bittisille. Joissain järjestelmissä on "
+"mahdollista suorittaa kumpaa ydintä vaan. Molemmissa tapauksissa käyttäjän "
+"sovellukset toimivat 32-bittisinä. 64-bittiset käyttäjän sovellukset ovat "
+"mahdollisia tulevaisuudessa."
 
 #. Tag: para
 #: hardware.xml:831
 #, 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-bits AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon."
-msgstr "Melkein kaikki x86-arkkitehtuurin (IA-32) prosessorit joita yhä käytetään henkilökohtaisissa tietokoneissa ovat tuettuja, mukaan lukien kaikki mallit Intelin \"Pentium\"-sarjassa. Tähän joukkoon kuuluvat myös 32-bittiset AMD:n ja VIA:n (entinen Cyrix) prosessorit, ja uudet prosessorit kuten Athlon XP ja 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-bits AMD and VIA (former Cyrix) processors, and new "
+"processors like the Athlon XP and Intel P4 Xeon."
+msgstr ""
+"Melkein kaikki x86-arkkitehtuurin (IA-32) prosessorit joita yhä käytetään "
+"henkilökohtaisissa tietokoneissa ovat tuettuja, mukaan lukien kaikki mallit "
+"Intelin \"Pentium\"-sarjassa. Tähän joukkoon kuuluvat myös 32-bittiset AMD:n "
+"ja VIA:n (entinen Cyrix) prosessorit, ja uudet prosessorit kuten Athlon XP "
+"ja Intel P4 Xeon."
 
 #. Tag: para
 #: hardware.xml:839
 #, no-c-format
-msgid "If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bits) i386 architecture."
-msgstr "Jos koneessa on 64-bittinen AMD64, Intel EM64t tai Intel Core 2 Duo prosessori,  haluttaneen käyttää amd64-arkkitehtuurille tarkoitettua asenninta eikä (32-bittisen) i386-arkkitehtuurin asenninta. "
+msgid ""
+"If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo "
+"processor, you will probably want to use the installer for the amd64 "
+"architecture instead of the installer for the (32-bits) i386 architecture."
+msgstr ""
+"Jos koneessa on 64-bittinen AMD64, Intel EM64t tai Intel Core 2 Duo "
+"prosessori,  haluttaneen käyttää amd64-arkkitehtuurille tarkoitettua "
+"asenninta eikä (32-bittisen) i386-arkkitehtuurin asenninta. "
 
 #. Tag: para
 #: hardware.xml:846
 #, no-c-format
-msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<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\", Debian "
+"Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors "
+"(and their clones), which were supported by earlier releases<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 ""
 "On huomattava <emphasis>ettei</emphasis> Debian GNU/Linux\n"
 "&releasename; toimi 386-prosessorilla tai sitä vanhemmilla\n"
@@ -1746,7 +1945,11 @@ msgstr ""
 "<footnote>\n"
 "<para> Mukavana sivuvaikutuksena tälle poistetulle vanhojen\n"
 "prosessorien tuelle useat Debianin paketit toimivat itse asiassa\n"
-"nopeammin uusissa tietokoneissa. Vuonna 1989 julkistetussa i486-prosessorissa on kolme käskyä (bswap, cmpxchg, ja xadd) jotka puuttuvat vuonna 1986 julkistetusta i386-prosessorista. Aikaisemmin näitä käskyjä ei helposti voinut käyttää useimmissa Debianin paketeissa, mutta nyt voi.</para></footnote>."
+"nopeammin uusissa tietokoneissa. Vuonna 1989 julkistetussa i486-"
+"prosessorissa on kolme käskyä (bswap, cmpxchg, ja xadd) jotka puuttuvat "
+"vuonna 1986 julkistetusta i386-prosessorista. Aikaisemmin näitä käskyjä ei "
+"helposti voinut käyttää useimmissa Debianin paketeissa, mutta nyt voi.</"
+"para></footnote>."
 
 #. Tag: title
 #: hardware.xml:883
@@ -1757,80 +1960,192 @@ msgstr "I/O Väylä"
 #. Tag: para
 #: hardware.xml:884
 #, 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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
-msgstr "Väylä on emolevyn osa jonka kautta prosessori kommunikoi oheislaitteiden kuten massamuistien kanssa. Tietokoneessa on oltava ISA, EISA, PCI, Mikrokanava (MCA, käytettiin IBM:n PS/2-malleissa), tai VESA Local Bus (VLB, joskus käytetään nimeä VL-väylä). Käytännöllisesti katsoen kaikissa viime vuosina myydyissä henkilökohtaisissa tietokoneissa on joku näistä."
+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, the Microchannel Architecture (MCA, used in IBM's PS/2 "
+"line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all "
+"personal computers sold in recent years use one of these."
+msgstr ""
+"Väylä on emolevyn osa jonka kautta prosessori kommunikoi oheislaitteiden "
+"kuten massamuistien kanssa. Tietokoneessa on oltava ISA, EISA, PCI, "
+"Mikrokanava (MCA, käytettiin IBM:n PS/2-malleissa), tai VESA Local Bus (VLB, "
+"joskus käytetään nimeä VL-väylä). Käytännöllisesti katsoen kaikissa viime "
+"vuosina myydyissä henkilökohtaisissa tietokoneissa on joku näistä."
 
 #. Tag: para
 #: hardware.xml:908
-#, no-c-format, fuzzy
-msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics."
-msgstr "Kaikki tiedot tuetuista M68000-prosessoria (<emphasis>&architecture;</emphasis>) käyttävistä järjestelmistä löytyy usein kysyttyjen kysymysten luettelosta <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Tässä luvussa kerrotaan vain perusteet."
+#, fuzzy, no-c-format
+msgid ""
+"Complete information concerning supported M68000 based "
+"(<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url="
+"\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the "
+"basics."
+msgstr ""
+"Kaikki tiedot tuetuista M68000-prosessoria (<emphasis>&architecture;</"
+"emphasis>) käyttävistä järjestelmistä löytyy usein kysyttyjen kysymysten "
+"luettelosta <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Tässä "
+"luvussa kerrotaan vain perusteet."
 
 #. Tag: para
 #: hardware.xml:915
 #, no-c-format
-msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details."
-msgstr "Linuxin &architecture;-siirros toimii kaikilla 680x0-prosessoreilla joissa on PMMU (Paged Memory Management Unit) ja FPU (liukulukuyksikkö). Tämä sisältää 68020 jossa on ulkoinen 68851 PMMU, 68030 ja paremmat. <quote>EC</quote>-mallin 680x0-prosessorit eivät kuulu joukkoon. Katso lisätietoja ohjeesta <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>."
+msgid ""
+"The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory "
+"Management Unit) and a FPU (floating-point unit). This includes the 68020 "
+"with an external 68851 PMMU, the 68030, and better, and excludes the "
+"<quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-"
+"faq;\">Linux/m68k FAQ</ulink> for complete details."
+msgstr ""
+"Linuxin &architecture;-siirros toimii kaikilla 680x0-prosessoreilla joissa "
+"on PMMU (Paged Memory Management Unit) ja FPU (liukulukuyksikkö). Tämä "
+"sisältää 68020 jossa on ulkoinen 68851 PMMU, 68030 ja paremmat. <quote>EC</"
+"quote>-mallin 680x0-prosessorit eivät kuulu joukkoon. Katso lisätietoja "
+"ohjeesta <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>."
 
 #. Tag: para
 #: hardware.xml:923
 #, no-c-format
-msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian."
-msgstr "Arkkitehtuurille <emphasis>&architecture;</emphasis> on neljä tuettua päälinjaa: Amiga, Atari, Macintosh ja VME. Amiga ja Atari olivat ensimmäiset kaksi järjestelmää joille Linux siirrettiin; ne ovat myös kaksi parhaiten tuettua Debianin siirrosta. Macintosh-tuotelinjan tuki on epätäydellinen sekä Debianissa että Linux-ytimessä; osoitteesta <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> löytyy projektin tilanne ja tuetut laitteistot. BVM:n ja Motorolan yhden kortin VME-väyläiset tietokoneet ovat viimeisin lisäys Debianin tukemien koneiden luetteloon. Siirrokset muihin &architecture;-laitealustoihin, kuten Sun3-koneille ja NeXTin mustaan laatikkoon ovat tekeillä, mutta Debian ei vielä tue niitä."
+msgid ""
+"There are four major supported <emphasis>&architecture;</emphasis> flavors: "
+"Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two "
+"systems to which Linux was ported; in keeping, they are also the two most "
+"well-supported Debian ports. The Macintosh line is supported incompletely, "
+"both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;"
+"\">Linux m68k for Macintosh</ulink> for project status and supported "
+"hardware. The BVM and Motorola single board VMEbus computers are the most "
+"recent addition to the list of machines supported by Debian. Ports to other "
+"&architecture; architectures, such as the Sun3 architecture and NeXT black "
+"box, are underway but not yet supported by Debian."
+msgstr ""
+"Arkkitehtuurille <emphasis>&architecture;</emphasis> on neljä tuettua "
+"päälinjaa: Amiga, Atari, Macintosh ja VME. Amiga ja Atari olivat ensimmäiset "
+"kaksi järjestelmää joille Linux siirrettiin; ne ovat myös kaksi parhaiten "
+"tuettua Debianin siirrosta. Macintosh-tuotelinjan tuki on epätäydellinen "
+"sekä Debianissa että Linux-ytimessä; osoitteesta <ulink url=\"&url-m68k-mac;"
+"\">Linux m68k for Macintosh</ulink> löytyy projektin tilanne ja tuetut "
+"laitteistot. BVM:n ja Motorolan yhden kortin VME-väyläiset tietokoneet ovat "
+"viimeisin lisäys Debianin tukemien koneiden luetteloon. Siirrokset muihin "
+"&architecture;-laitealustoihin, kuten Sun3-koneille ja NeXTin mustaan "
+"laatikkoon ovat tekeillä, mutta Debian ei vielä tue niitä."
 
 #. Tag: para
 #: hardware.xml:950
 #, 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> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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> Broadcom "
+"BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom "
+"based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> "
+"Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board "
+"from Broadcom based on the quad-core SB1A 1480 CPU. </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 ""
 "Debianin &arch-title;-siirros tukee seuraavia laitealustoja: <itemizedlist>\n"
 "<listitem>\n"
 "<para> SGI IP22: tähän laitealustaan kuuluvat SGI:n mallit Indy, Indigo 2\n"
-"ja Challenge S. Koska nämä mallit ovat hyvin samanlaisia, koskee kaikki mitä tässä ohjeessa sanotaan SGI Indy:stä myös Indigo 2:sta ja Challenge S:ää.</para></listitem>\n"
+"ja Challenge S. Koska nämä mallit ovat hyvin samanlaisia, koskee kaikki mitä "
+"tässä ohjeessa sanotaan SGI Indy:stä myös Indigo 2:sta ja Challenge S:ää.</"
+"para></listitem>\n"
 "<listitem>p\n"
 "<para> SGI IP32: tämä laitealusta tunnetaan yleensä nimellä SGI O2.\n"
 "</para></listitem>\n"
 "<listitem>\n"
-"<para> Broadcom BCM91250A (SWARM): tämä on kehityskäyttöön ATX-kokoinen emolevy, jossa on kaksiytiminen SB1 1250 -prosessori.\n"
+"<para> Broadcom BCM91250A (SWARM): tämä on kehityskäyttöön ATX-kokoinen "
+"emolevy, jossa on kaksiytiminen SB1 1250 -prosessori.\n"
 "</para></listitem>\n"
 "<listitem>\n"
-"<para> Broadcom BCM91480B (BigSur): tämä on kehityskäyttöön ATX-kokoinen emolevy, jossa on neliytiminen SB1A 1480 -prosessori.\n"
+"<para> Broadcom BCM91480B (BigSur): tämä on kehityskäyttöön ATX-kokoinen "
+"emolevy, jossa on neliytiminen SB1A 1480 -prosessori.\n"
 "</para></listitem> </itemizedlist> \n"
-"Kaikki tiedot tuetuista mips/mipsel-koneista löytyvät osoitteesta <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. Seuraavassa kerrotaan vain Debianin asentimen tukemista järjestelmistä. Etsittäessä tukea muille laitemalleille kannattaa käyttää <ulink url=\"&url-list-subscribe;\">sähköpostituslistaa debian-&arch-listname;</ulink>."
+"Kaikki tiedot tuetuista mips/mipsel-koneista löytyvät osoitteesta <ulink url="
+"\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. Seuraavassa kerrotaan vain "
+"Debianin asentimen tukemista järjestelmistä. Etsittäessä tukea muille "
+"laitemalleille kannattaa käyttää <ulink url=\"&url-list-subscribe;"
+"\">sähköpostituslistaa debian-&arch-listname;</ulink>."
 
 #. Tag: para
 #: hardware.xml:991
 #, 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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode."
-msgstr "Mallit SGI IP22, SGI Indy, Indigo 2 ja Challenge S joissa on prosessorina R4000, R4400, R4600 and R5000 ovat Debianin asennusjärjestelmän tukemia big endian MIPS-koneilla. Kehityskäyttöön tarkoitettu Broadcom BCM91250A -emolevy toimitetaan SB1 1250 -piirillä jossa on kaksi prosessoriydintä ja tämä asennin tukee niitä SMP-tilassa. Samoin BCM91480B-kehityslaitteistossa on SB1A 1480 -piiri jonka neljää ydintä tuetaan SMP-tilassa."
+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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 "
+"chip with two cores which are supported in SMP mode by this installer. "
+"Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with "
+"four cores which are supported in SMP mode."
+msgstr ""
+"Mallit SGI IP22, SGI Indy, Indigo 2 ja Challenge S joissa on prosessorina "
+"R4000, R4400, R4600 and R5000 ovat Debianin asennusjärjestelmän tukemia big "
+"endian MIPS-koneilla. Kehityskäyttöön tarkoitettu Broadcom BCM91250A -"
+"emolevy toimitetaan SB1 1250 -piirillä jossa on kaksi prosessoriydintä ja "
+"tämä asennin tukee niitä SMP-tilassa. Samoin BCM91480B-kehityslaitteistossa "
+"on SB1A 1480 -piiri jonka neljää ydintä tuetaan SMP-tilassa."
 
 #. Tag: para
 #: hardware.xml:1001
 #, 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."
-msgstr "Joitakin MIPS-koneita voidaan käyttää sekä big endian että little endian -toimintatiloissa. Tiedot little endian MIPS:stä löytyvät mipsel-laitealustan ohjeista."
+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 ""
+"Joitakin MIPS-koneita voidaan käyttää sekä big endian että little endian -"
+"toimintatiloissa. Tiedot little endian MIPS:stä löytyvät mipsel-laitealustan "
+"ohjeista."
 
 #. Tag: para
 #: hardware.xml:1018
 #, no-c-format
-msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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> DECstation: various models of the DECstation are supported. "
+"</para></listitem> <listitem><para> Cobalt Microserver: only MIPS based "
+"Cobalt machines are covered here. This includes the Cobalt Qube 2700 "
+"(Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></"
+"listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form "
+"factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </"
+"para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an "
+"ATX form factor evaluation board from Broadcom based on the quad-core SB1A "
+"1480 CPU. </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 ""
 "Debianin &arch-title;-siirros tukee seuraavia laitealustoja: <itemizedlist>\n"
 "<listitem>\n"
 "<para> DECstation: DECstation useat mallit ovat tuettuja.\n"
 "</para></listitem>\n"
 "<listitem>\n"
-"<para> Cobalt Microserver: vain MIPS-prosessorilla toimivia Cobalt-koneita käsitellään tässä. Tähän kuuluvat Cobalt Qube 2700 (Qube1), RaQ, Qube2 ja RaQ2,\n"
+"<para> Cobalt Microserver: vain MIPS-prosessorilla toimivia Cobalt-koneita "
+"käsitellään tässä. Tähän kuuluvat Cobalt Qube 2700 (Qube1), RaQ, Qube2 ja "
+"RaQ2,\n"
 "ja Gateway Microserver. </para></listitem>\n"
 "<listitem>\n"
-"<para> Broadcom BCM91250A (SWARM): tämä on kehityskäyttöön ATX-kokoinen emolevy, jossa on kaksiytiminen SB1 1250 -prosessori.\n"
+"<para> Broadcom BCM91250A (SWARM): tämä on kehityskäyttöön ATX-kokoinen "
+"emolevy, jossa on kaksiytiminen SB1 1250 -prosessori.\n"
 "</para></listitem>\n"
 "<listitem>\n"
-"<para> Broadcom BCM91480B (BigSur): tämä on kehityskäyttöön ATX-kokoinen emolevy, jossa on neliytiminen SB1A 1480 -prosessori.\n"
+"<para> Broadcom BCM91480B (BigSur): tämä on kehityskäyttöön ATX-kokoinen "
+"emolevy, jossa on neliytiminen SB1A 1480 -prosessori.\n"
 "</para></listitem> </itemizedlist> \n"
 "Kaikki tiedot tuetuista mips/mipsel-koneista löytyvät osoitteesta \n"
-"<ulink url=\\\"&url-linux-mips;\\\">Linux-MIPS homepage</ulink>. Seuraavassa kerrotaan vain Debianin asentimen tukemista järjestelmistä. Etsittäessä\n"
-"tukea muille laitemalleille kannattaa käyttää <ulink url=\"&url-list-subscribe;\">sähköpostituslistaa debian-&arch-listname;</ulink>."
+"<ulink url=\\\"&url-linux-mips;\\\">Linux-MIPS homepage</ulink>. Seuraavassa "
+"kerrotaan vain Debianin asentimen tukemista järjestelmistä. Etsittäessä\n"
+"tukea muille laitemalleille kannattaa käyttää <ulink url=\"&url-list-"
+"subscribe;\">sähköpostituslistaa debian-&arch-listname;</ulink>."
 
 #. Tag: title
 #: hardware.xml:1058
@@ -1841,8 +2156,14 @@ msgstr "Prosessori/laitemalleja"
 #. Tag: para
 #: hardware.xml:1060
 #, no-c-format
-msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:"
-msgstr "Tällä hetkellä vain DECstationit joissa on prosessorina R3000 tai R4000/R4400 ovat Debianin asennusjärjestelmän tukemia little endian MIPS-koneilla. Debianin asennusjärjestelmä toimii seuraavilla koneilla:"
+msgid ""
+"Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by "
+"the Debian installation system on little endian MIPS. The Debian "
+"installation system works on the following machines:"
+msgstr ""
+"Tällä hetkellä vain DECstationit joissa on prosessorina R3000 tai R4000/"
+"R4400 ovat Debianin asennusjärjestelmän tukemia little endian MIPS-koneilla. "
+"Debianin asennusjärjestelmä toimii seuraavilla koneilla:"
 
 #. Tag: entry
 #: hardware.xml:1072
@@ -1955,13 +2276,23 @@ msgstr "Personal DECstation 5000/50"
 #. Tag: para
 #: hardware.xml:1116
 #, no-c-format
-msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH."
-msgstr "Kaikki Cobalt-koneet ovat tuettuja. Aikaisemmin olivat tuettuja vain koneet joissa oli sarjapääte konsolina (eli kaikki koneet paitsi Qube 2700, eli Qube1). Nyt ovat asennukset kuitenkin mahdollisia myös SSH:n kautta."
+msgid ""
+"All Cobalt machines are supported. In the past, only machines with a serial "
+"console were supported (that is, all machines except for the Qube 2700, aka "
+"Qube1). However, installations are now also possible through SSH."
+msgstr ""
+"Kaikki Cobalt-koneet ovat tuettuja. Aikaisemmin olivat tuettuja vain koneet "
+"joissa oli sarjapääte konsolina (eli kaikki koneet paitsi Qube 2700, eli "
+"Qube1). Nyt ovat asennukset kuitenkin mahdollisia myös SSH:n kautta."
 
 #. Tag: para
 #: hardware.xml:1123
 #, no-c-format
-msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode."
+msgid ""
+"The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two "
+"cores which are supported in SMP mode by this installer. Similarly, the "
+"BCM91480B evaluation board contains an SB1A 1480 chip with four cores which "
+"are supported in SMP mode."
 msgstr ""
 
 #. Tag: title
@@ -1973,16 +2304,30 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1134
 #, no-c-format
-msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to &mdash; usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options."
+msgid ""
+"A serial console is available on all supported DECstations (9600 bps, 8N1). "
+"To use the serial console, you have to boot the installer image with the "
+"<literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter "
+"(with <replaceable>x</replaceable> being the number of the serial port you "
+"have your terminal connected to &mdash; usually <literal>2</literal>, but "
+"<literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ "
+"(DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available "
+"with the PMAG-BA and the PMAGB-B graphics options."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1145
 #, no-c-format
 msgid ""
-      "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n"
-      "$ cu -l /dev/ttyS1 -s 9600\n"
-      "</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)."
+"If you have a Linux system to use as serial terminal, an easy way is to run "
+"<command>cu</command><footnote> <para> In Woody this command was part of the "
+"<classname>uucp</classname> package, but in later releases it is available "
+"as a separate package. </para> </footnote> on it. Example: "
+"<informalexample><screen>\n"
+"$ cu -l /dev/ttyS1 -s 9600\n"
+"</screen></informalexample> where the option <literal>-l</literal> (line) "
+"sets the serial port to use and <literal>-s</literal> (speed) sets the speed "
+"for the connection (9600 bits per second)."
 msgstr ""
 
 #. Tag: para
@@ -1994,13 +2339,21 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1177
 #, no-c-format
-msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants."
+msgid ""
+"There are four major supported <emphasis>&architecture;</emphasis> "
+"subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga "
+"Power-UP System), and CHRP machines. Each subarchitecture has its own boot "
+"methods. In addition, there are four different kernel flavours, supporting "
+"different CPU variants."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1185
 #, no-c-format
-msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future."
+msgid ""
+"Ports to other <emphasis>&architecture;</emphasis> architectures, such as "
+"the Be-Box and MBX architecture, are underway but not yet supported by "
+"Debian. We may have a 64-bit port in the future."
 msgstr ""
 
 #. Tag: title
@@ -2012,7 +2365,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1195
 #, no-c-format
-msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:"
+msgid ""
+"There are four flavours of the powerpc kernel in Debian, based on the CPU "
+"type:"
 msgstr ""
 
 #. Tag: term
@@ -2024,7 +2379,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1203
 #, 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
@@ -2042,19 +2400,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1218
 #, 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:1224
 #, 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:1229
 #, 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: term
@@ -2078,7 +2443,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1248
 #, no-c-format
-msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled."
+msgid ""
+"This kernel flavour supports the Amiga Power-UP System, though it is "
+"currently disabled."
 msgstr ""
 
 #. Tag: title
@@ -2090,25 +2457,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1263
 #, 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:1270
 #, 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:1278
 #, 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:1286
 #, 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
@@ -2136,7 +2520,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356
+#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320
+#: hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332
+#: hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344
+#: hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
@@ -2238,7 +2625,11 @@ msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368 hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380 hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392 hardware.xml:1398 hardware.xml:1401 hardware.xml:1407 hardware.xml:1413 hardware.xml:1419
+#: hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368
+#: hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380
+#: hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392
+#: hardware.xml:1398 hardware.xml:1401 hardware.xml:1407 hardware.xml:1413
+#: hardware.xml:1419
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
@@ -2480,7 +2871,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1527
 #, 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
@@ -2492,19 +2893,33 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1566
 #, 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:1575
 #, 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:1583
 #, 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
@@ -2516,13 +2931,34 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1600
 #, no-c-format
-msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance."
+msgid ""
+"Complete information regarding supported S/390 and zSeries machines can be "
+"found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/"
+"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: "
+"Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128."
+"ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the "
+"developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries "
+"are fully supported; Multiprise 2000, G3 and G4 machines are supported with "
+"IEEE floating point emulation and thus degraded performance."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1623
 #, no-c-format
-msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information."
+msgid ""
+"Currently the <emphasis>&architecture;</emphasis> port supports several "
+"types of Sparc systems. The most common identifiers for Sparc systems are "
+"sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old "
+"sun4 hardware. However, the other systems are supported. Sun4d has been "
+"tested the least of these, so expect possible problems with regard to the "
+"kernel stability. Sun4c and Sun4m, the most common of the older Sparc "
+"hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the "
+"SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems "
+"fall under the sun4u identifier, and are supported using the sun4u set of "
+"install images. Some systems that fall under these supported identifiers are "
+"known to not be supported. Known unsupported systems are the AP1000 "
+"multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-"
+"linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information."
 msgstr ""
 
 #. Tag: title
@@ -2534,19 +2970,34 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1644
 #, no-c-format
-msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result."
+msgid ""
+"Some older Sun workstations, notably the Sun IPX and Sun IPC have memory "
+"banks located at fixed locations in physical memory. Thus if the banks are "
+"not filled gaps will exist in the physical memory space. The Linux "
+"installation requires a contiguous memory block into which to load the "
+"kernel and the initial RAMdisk. If this is not available a <quote>Data "
+"Access Exception</quote> will result."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1653
 #, no-c-format
-msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient."
+msgid ""
+"Thus you must configure the memory so that the lowest memory block is "
+"contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks "
+"are mapped in at 16Mb boundaries. In effect this means that you must have a "
+"sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this "
+"case 4Mb is <emphasis>not</emphasis> sufficient."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1661
 #, no-c-format
-msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2."
+msgid ""
+"Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four "
+"SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS "
+"connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then "
+"recommended to install the 4Mb SIMM in bank 2."
 msgstr ""
 
 #. Tag: title
@@ -2558,19 +3009,32 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1673
 #, no-c-format
-msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized."
+msgid ""
+"Especially in the case of older Sun workstations, it is very common for "
+"there to be an onboard framebuffer which has been superseded (for example "
+"the bwtwo on a sun IPC), and an SBUS card containing a later probably "
+"accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS "
+"this causes no problems because both cards are initialized."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1682
 #, no-c-format
-msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk."
+msgid ""
+"However with Linux this can cause a problem, in that the boot PROM monitor "
+"may display its output on this additional card; however the linux kernel "
+"boot messages may then be directed to the original on board framebuffer, "
+"leaving <emphasis>no</emphasis> error messages on the screen, with the "
+"machine apparently stuck loading the RAMdisk."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1690
 #, no-c-format
-msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console."
+msgid ""
+"To avoid this problem, connect the monitor (if required) to the video card "
+"in the lowest numbered SBUS slot (on motherboard card counts as below "
+"external slots). Alternatively it is possible to use a serial console."
 msgstr ""
 
 #. Tag: title
@@ -2582,25 +3046,45 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1703
 #, no-c-format
-msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document."
+msgid ""
+"You should be using a VGA-compatible display interface for the console "
+"terminal. Nearly every modern display card is compatible with VGA. Ancient "
+"standards such CGA, MDA, or HGA should also work, assuming you do not "
+"require X11 support. Note that X11 is not used during the installation "
+"process described in this document."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1711
 #, no-c-format
-msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;."
+msgid ""
+"Debian's support for graphical interfaces is determined by the underlying "
+"support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work "
+"under X.Org. Details on supported graphics buses, cards, monitors, and "
+"pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian "
+"&release; ships with X.Org version &x11ver;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1720
 #, no-c-format
-msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
+msgid ""
+"The X.Org X11 window system is only supported on the SGI Indy and the O2. "
+"The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v "
+"PCI slots and support VGA emulation or Linux framebuffer on a selected range "
+"of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility "
+"listing</ulink> for Broadcom evaluation boards is available."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1729
 #, no-c-format
-msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
+msgid ""
+"The X.Org X11 window system is supported on some DECstation models. The "
+"Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI "
+"slots and support VGA emulation or Linux framebuffer on a selected range of "
+"graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility "
+"listing</ulink> for Broadcom evaluation boards is available."
 msgstr ""
 
 #. Tag: title
@@ -2612,7 +3096,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1741
 #, no-c-format
-msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>"
+msgid ""
+"Laptops are also supported. Laptops are often specialized or contain "
+"proprietary hardware. To see if your particular laptop works well with GNU/"
+"Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>"
 msgstr ""
 
 #. Tag: title
@@ -2624,49 +3111,92 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1753
 #, no-c-format
-msgid "Multi-processor support &mdash; also called <quote>symmetric multi-processing</quote> or SMP &mdash; is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead."
+msgid ""
+"Multi-processor support &mdash; also called <quote>symmetric multi-"
+"processing</quote> or SMP &mdash; is available for this architecture. The "
+"standard Debian &release; kernel image was compiled with SMP support. This "
+"should not prevent installation, since the SMP kernel should boot on non-SMP "
+"systems; the kernel will simply cause a bit more overhead."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1761
 #, no-c-format
-msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config."
+msgid ""
+"In order to optimize the kernel for single CPU systems, you'll have to "
+"replace the standard Debian kernel. You can find a discussion of how to do "
+"this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version "
+"&kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-"
+"option;</quote> in the <quote>&smp-config-section;</quote> section of the "
+"kernel config."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1776
 #, no-c-format
-msgid "Multi-processor support &mdash; also called <quote>symmetric multi-processing</quote> or SMP &mdash; is available for this architecture. The standard Debian &release; kernel image was 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 ""
+"Multi-processor support &mdash; also called <quote>symmetric multi-"
+"processing</quote> or SMP &mdash; is available for this architecture. The "
+"standard Debian &release; kernel image was 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:1785
 #, 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:1795
 #, no-c-format
-msgid "Multi-processor support &mdash; also called <quote>symmetric multi-processing</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 the first CPU."
+msgid ""
+"Multi-processor support &mdash; also called <quote>symmetric multi-"
+"processing</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 the first CPU."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1804
 #, no-c-format
-msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. 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."
+msgid ""
+"In order to take advantage of multiple processors, you'll have to replace "
+"the standard Debian kernel. 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."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1818
 #, no-c-format
-msgid "Multi-processor support &mdash; also called <quote>symmetric multi-processing</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 ""
+"Multi-processor support &mdash; also called <quote>symmetric multi-"
+"processing</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:1828
 #, 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. You can also build your own customized kernel to support SMP. 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."
+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. You can also build your own customized kernel to "
+"support SMP. 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."
 msgstr ""
 
 #. Tag: title
@@ -2678,7 +3208,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1851
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted 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. For example, if you have a floppy disk drive on your "
+"machine, it can be used to install Debian. There is a whole chapter devoted "
+"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
@@ -2690,7 +3226,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1863
 #, 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
@@ -2708,67 +3247,125 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1878
 #, 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, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI."
+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, except for some very old nonstandard CD-"
+"ROM drives which are neither SCSI nor IDE/ATAPI."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1885
 #, no-c-format
-msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>."
+msgid ""
+"CD-ROM based installation is supported for some architectures. On machines "
+"which support bootable CD-ROMs, you should be able to do a completely "
+"<phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-"
+"less</phrase> installation. Even if your system doesn't support booting from "
+"a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to "
+"install your system, once you've booted up by other means; see <xref linkend="
+"\"boot-installer\"/>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1897
 #, no-c-format
-msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux."
+msgid ""
+"Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard "
+"CD interfaces supported by Linux are supported by the boot disks (such as "
+"Mitsumi and Matsushita drives). However, these models might require special "
+"boot parameters or other massaging to get them to work, and booting off "
+"these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;"
+"\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs "
+"with Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1907
 #, 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
 #: hardware.xml:1912
 #, no-c-format
-msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>."
+msgid ""
+"Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as "
+"the controller is supported by the SRM console. This rules out many add-on "
+"controller cards, but most integrated IDE and SCSI chips and controller "
+"cards that were provided by the manufacturer can be expected to work. To "
+"find out whether your device is supported from the SRM console, see the "
+"<ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1921
 #, no-c-format
-msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported."
+msgid ""
+"IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-"
+"ROMs are also supported."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1926
 #, 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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card."
+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. The Broadcom BCM91250A supports standard IDE devices, "
+"including CD-ROM drives, but CD images for this platform are currently not "
+"provided because the firmware doesn't recognize CD drives. In order to "
+"install Debian on an Broadcom BCM91480B evaluation board, you need an PCI "
+"IDE, SATA or SCSI card."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1941
 #, no-c-format
-msgid "On DECstations, 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."
+msgid ""
+"On DECstations, 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."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1950
 #, no-c-format
-msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)."
+msgid ""
+"CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-"
+"based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal "
+"DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the "
+"R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal "
+"DECstation 5000/50)."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1959
 #, no-c-format
-msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:"
+msgid ""
+"To boot from CD, issue the command <userinput>boot <replaceable>#</"
+"replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware "
+"prompt, where <replaceable>#</replaceable> is the number of the TurboChannel "
+"device from which to boot (3 on most DECstations) and <replaceable>id</"
+"replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass "
+"additional parameters, they can optionally be appended with the following "
+"syntax:"
 msgstr ""
 
 #. Tag: userinput
 #: hardware.xml:1971
 #, no-c-format
-msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..."
+msgid ""
+"boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> "
+"param1=value1 param2=value2 ..."
 msgstr ""
 
 #. Tag: title
@@ -2780,19 +3377,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1980
 #, 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."
+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."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1986
 #, no-c-format
-msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines."
+msgid ""
+"In fact, installation from your local disk is the preferred installation "
+"technique for most &architecture; machines."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:1991
 #, 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
@@ -2804,7 +3408,13 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2001
 #, no-c-format
-msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives."
+msgid ""
+"Many Debian boxes need their floppy and/or CD-ROM drives only for setting up "
+"the system and for rescue purposes. If you operate some servers, you will "
+"probably already have thought about omitting those drives and using an USB "
+"memory stick for installing and (when necessary) for recovering the system. "
+"This is also useful for small systems which have no room for unnecessary "
+"drives."
 msgstr ""
 
 #. Tag: title
@@ -2816,19 +3426,26 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2015
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>"
+msgid ""
+"You can also <emphasis>boot</emphasis> your system over the network. <phrase "
+"arch=\"mips\">This is the preferred installation technique for Mips.</phrase>"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2021
 #, 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: para
 #: hardware.xml:2026
 #, no-c-format
-msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP."
+msgid ""
+"After the operating system kernel is installed, you can install the rest of "
+"your system via any sort of network connection (including PPP after "
+"installation of the base system), via FTP or HTTP."
 msgstr ""
 
 #. Tag: title
@@ -2840,7 +3457,12 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2037
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the 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\"/>."
+msgid ""
+"If you are running another Unix-like system, you could use it to install "
+"&debian; without using the &d-i; described in the rest of the 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\"/>."
 msgstr ""
 
 #. Tag: title
@@ -2852,61 +3474,108 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2051
 #, no-c-format
-msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware."
+msgid ""
+"The Debian boot disks contain a kernel which is built to maximize the number "
+"of systems it runs on. Unfortunately, this makes for a larger kernel, which "
+"includes many drivers that won't be used for your machine (see <xref linkend="
+"\"kernel-baking\"/> to learn how to build your own kernel). Support for the "
+"widest possible range of devices is desirable in general, to ensure that "
+"Debian can be installed on the widest array of hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2061
 #, no-c-format
-msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, 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 floppies, IDE "
+"drives, IDE floppies, parallel port IDE devices, 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:2068
 #, no-c-format
-msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface &mdash; often called MFM, RLL, IDE, or ATA &mdash; are supported. Very old 8&ndash;bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details."
+msgid ""
+"Disk interfaces that emulate the <quote>AT</quote> hard disk interface "
+"&mdash; often called MFM, RLL, IDE, or ATA &mdash; are supported. Very old "
+"8&ndash;bit hard disk controllers used in the IBM XT computer are supported "
+"only as a module. SCSI disk controllers from many different manufacturers "
+"are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware "
+"Compatibility HOWTO</ulink> for more details."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2078
 #, no-c-format
-msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module."
+msgid ""
+"Pretty much all storage systems supported by the Linux kernel are supported "
+"by the Debian installation system. Note that the current Linux kernel does "
+"not support floppies on the Macintosh at all, and the Debian installation "
+"system doesn't support floppies for Amigas. Also supported on the Atari is "
+"the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) "
+"file system. Amigas support the FAT file system, and HFS as a module."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2088
 #, 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:2121
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)"
+msgid ""
+"Any storage system supported by the Linux kernel is also supported by the "
+"boot system. This includes both SCSI and IDE disks. Note, however, that on "
+"many systems, the SRM console is unable to boot from IDE drives, and the "
+"Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;"
+"\"></ulink> for more information on booting the Jensen)"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2130
 #, 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:2136
 #, 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:2142
 #, 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:2147
 #, 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
@@ -2918,37 +3587,55 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2165
 #, no-c-format
-msgid "Linux 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 ""
+"Linux 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:2171
 #, no-c-format
-msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)."
+msgid ""
+"USB hardware generally works fine, only some USB keyboards may require "
+"additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2177
 #, no-c-format
-msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux."
+msgid ""
+"Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware "
+"Compatibility HOWTO</ulink> to determine whether your specific hardware is "
+"supported by Linux."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2183
 #, 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:2189
 #, no-c-format
-msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots."
+msgid ""
+"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 "
+"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation "
+"board features four 64 bit PCI slots."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2195
 #, no-c-format
-msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid ""
+"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 "
+"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation "
+"board features four 64 bit PCI slots. The Cobalt RaQ has no support for "
+"additional devices but the Qube has one PCI slot."
 msgstr ""
 
 #. Tag: title
@@ -2960,25 +3647,42 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2207
 #, 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:2215
 #, no-c-format
-msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all."
+msgid ""
+"Unfortunately, it's quite rare to find any vendor shipping new &arch-title; "
+"machines at all."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2220
 #, 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:2228
 #, no-c-format
-msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors."
+msgid ""
+"Whether or not you are purchasing a system with Linux bundled, or even a "
+"used system, it is still important to check that your hardware is supported "
+"by the Linux kernel. Check if your hardware is listed in the references "
+"found above. Let your salesperson (if any) know that you're shopping for a "
+"Linux system. Support Linux-friendly hardware vendors."
 msgstr ""
 
 #. Tag: title
@@ -2990,19 +3694,34 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2240
 #, 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 Linux source code."
+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 Linux "
+"source code."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2247
 #, no-c-format
-msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports."
+msgid ""
+"Another example is the proprietary hardware in the older Macintosh line. In "
+"fact, no specifications or documentation have ever been released for any "
+"Macintosh hardware, most notably the ADB controller (used by the mouse and "
+"keyboard), the floppy controller, and all acceleration and CLUT manipulation "
+"of the video hardware (though we do now support CLUT manipulation on nearly "
+"all internal video chips). In a nutshell, this explains why the Macintosh "
+"Linux port lags behind other Linux ports."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2258
 #, no-c-format
-msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market."
+msgid ""
+"Since we haven't been granted access to the documentation on these devices, "
+"they simply won't work under Linux. You can help by asking the manufacturers "
+"of such hardware to release the documentation. If enough people ask, they "
+"will realize that the free software community is an important market."
 msgstr ""
 
 #. Tag: title
@@ -3014,19 +3733,50 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2271
 #, no-c-format
-msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence."
+msgid ""
+"A disturbing trend is the proliferation of Windows-specific modems and "
+"printers. In some cases these are specially designed to be operated by the "
+"Microsoft Windows operating system and bear the legend <quote>WinModem</"
+"quote> or <quote>Made especially for Windows-based computers</quote>. This "
+"is generally done by removing the embedded processors of the hardware and "
+"shifting the work they do over to a Windows driver that is run by your "
+"computer's main CPU. This strategy makes the hardware less expensive, but "
+"the savings are often <emphasis>not</emphasis> passed on to the user and "
+"this hardware may even be more expensive than equivalent devices that retain "
+"their embedded intelligence."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2284
 #, no-c-format
-msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware."
+msgid ""
+"You should avoid Windows-specific hardware for two reasons. The first is "
+"that the manufacturers do not generally make the resources available to "
+"write a Linux driver. Generally, the hardware and software interface to the "
+"device is proprietary, and documentation is not available without a non-"
+"disclosure agreement, if it is available at all. This precludes its being "
+"used for free software, since free software writers disclose the source code "
+"of their programs. The second reason is that when devices like these have "
+"had their embedded processors removed, the operating system must perform the "
+"work of the embedded processors, often at <emphasis>real-time</emphasis> "
+"priority, and thus the CPU is not available to run your programs while it is "
+"driving these devices. Since the typical Windows user does not multi-process "
+"as intensively as a Linux user, the manufacturers hope that the Windows user "
+"simply won't notice the burden this hardware places on their CPU. However, "
+"any multi-processing operating system, even Windows 2000 or XP, suffers from "
+"degraded performance when peripheral manufacturers skimp on the embedded "
+"processing power of their hardware."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2305
 #, no-c-format
-msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>."
+msgid ""
+"You can help improve this situation by encouraging these manufacturers to "
+"release the documentation and other resources necessary for us to program "
+"their hardware, but the best strategy is simply to avoid this sort of "
+"hardware until it is listed as working in the <ulink url=\"&url-hardware-"
+"howto;\">Linux Hardware Compatibility HOWTO</ulink>."
 msgstr ""
 
 #. Tag: title
@@ -3038,13 +3788,27 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2319
 #, no-c-format
-msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits."
+msgid ""
+"If you ask for Parity RAM in a computer store, you'll probably get "
+"<emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true "
+"parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be "
+"distinguished because they only have one more chip than an equivalent non-"
+"parity SIMM, and that one extra chip is smaller than all the others. Virtual-"
+"parity SIMMs work exactly like non-parity memory. They can't tell you when "
+"you have a single-bit RAM error the way true-parity SIMMs do in a "
+"motherboard that implements parity. Don't ever pay more for a virtual-parity "
+"SIMM than a non-parity one. Do expect to pay a little more for true-parity "
+"SIMMs, because you are actually buying one extra bit of memory for every 8 "
+"bits."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2334
 #, no-c-format
-msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>."
+msgid ""
+"If you want complete information on &arch-title; RAM issues, and what is the "
+"best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</"
+"ulink>."
 msgstr ""
 
 #. Tag: para
@@ -3062,25 +3826,44 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2357
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes."
+msgid ""
+"You must have at least &minimum-memory; of memory and &minimum-fs-size; of "
+"hard disk space. For a minimal console-based system (all standard packages), "
+"250MB is required. If you want to install a reasonable amount of software, "
+"including the X Window System, and some development programs and libraries, "
+"you'll need at least 400MB. For a more or less complete desktop system, "
+"you'll need a few gigabytes."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2366
 #, no-c-format
-msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically."
+msgid ""
+"On the Amiga the size of FastRAM is relevant towards the total memory "
+"requirements. Also, using Zorro cards with 16-bit RAM is not supported; "
+"you'll need 32-bit RAM. The <command>amiboot</command> program can be used "
+"to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>. Recent kernels should disable 16-bit RAM automatically."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2375
 #, no-c-format
-msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM."
+msgid ""
+"On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many "
+"users have reported problems running the kernel itself in Fast RAM, so the "
+"Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for "
+"ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2383
 #, no-c-format
-msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB."
+msgid ""
+"On the Macintosh, care should be taken on machines with RAM-based video "
+"(RBV). The RAM segment at physical address 0 is used as screen memory, "
+"making the default load position for the kernel unavailable. The alternate "
+"RAM segment used for kernel and RAMdisk must be at least 4 MB."
 msgstr ""
 
 #. Tag: emphasis
@@ -3098,25 +3881,41 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2406
 #, no-c-format
-msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider &amp; Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols."
+msgid ""
+"Most PCI and many older ISA network cards are supported. Some network "
+"interface cards are not supported by most Debian installation disks, such as "
+"AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider &amp; Koch "
+"G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) "
+"network cards are not supported by the standard installation system, but see "
+"<ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) "
+"instructions. FDDI networks are also not supported by the installation "
+"disks, both cards and protocols."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2425
 #, no-c-format
-msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;."
+msgid ""
+"As for ISDN, the D-channel protocol for the (old) German 1TR6 is not "
+"supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2433
 #, no-c-format
-msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details."
+msgid ""
+"Any network interface card (NIC) supported by the Linux kernel should also "
+"be supported by the boot disks. You may need to load your network driver as "
+"a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete "
+"details."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2442
 #, no-c-format
-msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:"
+msgid ""
+"The following network interface cards (NICs) are supported from the bootable "
+"kernel directly:"
 msgstr ""
 
 #. Tag: para
@@ -3134,7 +3933,10 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2462
 #, no-c-format
-msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:"
+msgid ""
+"The following network interface cards are supported as modules. They can be "
+"enabled once the drivers are installed during the setup. However, due to the "
+"magic of OpenPROM, you still should be able to boot from these devices:"
 msgstr ""
 
 #. Tag: para
@@ -3156,21 +3958,31 @@ msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2488 hardware.xml:2494 hardware.xml:2500 hardware.xml:2506 hardware.xml:2512
+#: hardware.xml:2488 hardware.xml:2494 hardware.xml:2500 hardware.xml:2506
+#: hardware.xml:2512
 #, no-c-format
-msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module."
+msgid ""
+"Any network interface card (NIC) supported by the Linux kernel should also "
+"be supported by the boot disks. You may need to load your network driver as "
+"a module."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2518
 #, no-c-format
-msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work."
+msgid ""
+"Due to kernel limitations only the onboard network interfaces on DECstations "
+"are supported, TurboChannel option network cards currently do not work."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2524
 #, no-c-format
-msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:"
+msgid ""
+"Any network interface card (NIC) supported by the Linux kernel is also be "
+"supported by the boot disks. All network drivers are compiled as modules so "
+"you need to load one first during the initial network setup. The list of "
+"supported network devices is:"
 msgstr ""
 
 #. Tag: para
@@ -3188,7 +4000,8 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2542
 #, no-c-format
-msgid "Inter-User Communication Vehicle (IUCV) &mdash; available for VM guests only"
+msgid ""
+"Inter-User Communication Vehicle (IUCV) &mdash; available for VM guests only"
 msgstr ""
 
 #. Tag: para
@@ -3200,7 +4013,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2556
 #, no-c-format
-msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:"
+msgid ""
+"The following network interface cards are supported directly by the boot "
+"disks on Netwinder and CATS machines:"
 msgstr ""
 
 #. Tag: para
@@ -3218,7 +4033,9 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2575
 #, no-c-format
-msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:"
+msgid ""
+"The following network interface cards are supported directly by the boot "
+"disks on RiscPCs:"
 msgstr ""
 
 #. Tag: para
@@ -3242,12 +4059,17 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2598
 #, no-c-format
-msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks."
+msgid ""
+"If your card is mentioned in the lists above, the complete installation can "
+"be carried out from the network with no need for CD-ROMs or floppy disks."
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:2604
 #, no-c-format
-msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media."
+msgid ""
+"Any other network interface card (NIC) supported by the Linux kernel should "
+"also be supported by the boot disks. You may need to load your network "
+"driver as a module; this means that you will have to install the operating "
+"system kernel and modules using some other media."
 msgstr ""
-