Initial commit preparing to add variant for AMD64.

This commit basically creates the AMD64 variant as a copy of the i386 manual.
Further commits will be needed to differentiate the AMD64 variant from i386 where needed.
Commit includes changes for all translations.

6 files changed, 21 insertions, 21 deletions

diff --git a/en/preparing/bios-setup/i386.xml b/en/preparing/bios-setup/i386.xml
index e5e884612..7d19431f2 100644
--- a/en/preparing/bios-setup/i386.xml
+++ b/en/preparing/bios-setup/i386.xml
@@ -2,7 +2,7 @@
 <!-- $Id$ -->
 
 
-  <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title>
+  <sect2 arch="x86" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title>
 
 <para>
 
@@ -102,7 +102,7 @@ try using a shareware/freeware program.  Try looking in
 </para>
   </sect2>
 
-  <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title>
+  <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title>
 
 <para>
 
@@ -230,7 +230,7 @@ save the changes on your computer. Often, you must press
    </sect3>
   </sect2>
 
-  <sect2 arch="i386">
+  <sect2 arch="x86">
   <title>Miscellaneous BIOS Settings</title>
 
    <sect3 id="cd-settings"><title>CD-ROM Settings</title>
diff --git a/en/preparing/minimum-hardware-reqts.xml b/en/preparing/minimum-hardware-reqts.xml
index 3dffd6e91..0def42ddb 100644
--- a/en/preparing/minimum-hardware-reqts.xml
+++ b/en/preparing/minimum-hardware-reqts.xml
@@ -15,7 +15,7 @@ Depending on your needs, you might manage with less than some of the
 recommended hardware listed in the table below. However, most users
 risk being frustrated if they ignore these suggestions.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 A Pentium 100 is the minimum recommended for desktop
 systems, and a Pentium II-300 for a Server.
diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml
index 53f7ea264..8f68abd37 100644
--- a/en/preparing/needed-info.xml
+++ b/en/preparing/needed-info.xml
@@ -52,8 +52,8 @@ Often contains useful information on configuring or using your hardware.
 
  <!-- We need the arch dependence for the whole list to ensure proper xml
       as long as not architectures have a paragraph -->
- <itemizedlist arch="i386;m68k;alpha;sparc;mips;mipsel">
-<listitem arch="i386"><para>
+ <itemizedlist arch="x86;m68k;alpha;sparc;mips;mipsel">
+<listitem arch="x86"><para>
 
 <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>
 
@@ -175,7 +175,7 @@ The cases and boxes for each piece of hardware.
 
 </para></listitem>
 
-<listitem arch="i386"><para>
+<listitem arch="x86"><para>
 
 The System window in the Windows Control Panel.
 
@@ -215,7 +215,7 @@ networking and e-mail.
 </row>
 <row arch="not-s390"><entry>Their order on the system.</entry></row>
 <!-- "not-m68k;not-s390" would really turn out to be everything... -->
-<row arch="alpha;arm;hppa;i386;ia64;mips;mipsel;powerpc;sparc">
+<row arch="alpha;arm;hppa;x86;ia64;mips;mipsel;powerpc;sparc">
   <entry>Whether IDE or SCSI (most computers are IDE).</entry>
 </row>
 <row arch="m68k">
@@ -296,19 +296,19 @@ Many brand name products work without trouble on Linux. Moreover,
 hardware for Linux is improving daily. However, Linux still does not
 run as many different types of hardware as some operating systems.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 In particular, Linux usually cannot run hardware that requires a
 running version of Windows to work.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 Although some Windows-specific hardware can be made to run on Linux,
 doing so usually requires extra effort. In addition, Linux drivers
 for Windows-specific hardware are usually specific to one Linux
 kernel. Therefore, they can quickly become obsolete.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 So called win-modems are the most common type of this hardware.
 However, printers and other equipment may also be Windows-specific.
diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml
index 6e444855a..0f95aefe4 100644
--- a/en/preparing/non-debian-partitioning.xml
+++ b/en/preparing/non-debian-partitioning.xml
@@ -20,7 +20,7 @@ means an LPAR or VM guest in this case.
 
 If you already have an operating system on your system
 
-<phrase arch="i386">
+<phrase arch="x86">
 (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, &hellip;)
 </phrase>
 
@@ -47,7 +47,7 @@ root.
 
 You can find information about your current partition setup by using
 a partitioning tool for your current operating system<phrase
-arch="i386">, such as fdisk or PartitionMagic</phrase><phrase
+arch="x86">, such as fdisk or PartitionMagic</phrase><phrase
 arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase
 arch="m68k">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase
 arch="s390">, such as the VM diskmap</phrase>. Partitioning tools always
@@ -97,7 +97,7 @@ special circumstances like the order of the existing partitions within
 the partition map, that force you to partition before installing
 anyway.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 If your machine has a FAT or NTFS filesystem, as used by DOS and Windows,
 you can wait and use Debian installer's partitioning program to
diff --git a/en/preparing/nondeb-part/i386.xml b/en/preparing/nondeb-part/i386.xml
index 3846cec48..4346fe83f 100644
--- a/en/preparing/nondeb-part/i386.xml
+++ b/en/preparing/nondeb-part/i386.xml
@@ -2,7 +2,7 @@
 <!-- $Id$ -->
 
 
-  <sect2 arch="i386"><title>Partitioning From DOS or Windows</title>
+  <sect2 arch="x86"><title>Partitioning From DOS or Windows</title>
 <para>
 
 If you are manipulating existing FAT or NTFS partitions, it is
diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 369fb6922..03be8cd7b 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -54,7 +54,7 @@ FIXME: more description of this needed.
 
 </emphasis></phrase>
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 The very best motherboards support parity RAM and will actually tell
 you if your system has a single-bit error in RAM. Unfortunately, they
@@ -65,7 +65,7 @@ in your data. Thus, the best systems have motherboards that support
 parity and true-parity memory modules; see
 <xref linkend="Parity-RAM"/>.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 If you do have true-parity RAM and your motherboard can handle it, be
 sure to enable any BIOS settings that cause the motherboard to
@@ -73,7 +73,7 @@ interrupt on memory parity errors.
 
 </para>
 
-   <sect3 arch="i386"><title>The Turbo Switch</title>
+   <sect3 arch="x86"><title>The Turbo Switch</title>
 <para>
 
 Many systems have a <emphasis>turbo</emphasis> switch that controls
@@ -87,7 +87,7 @@ accidentally touch the software control for the turbo switch.
 </para>
    </sect3>
 
-   <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title>
+   <sect3 arch="x86"><title>Cyrix CPUs and Floppy Disk Errors</title>
 <para>
 
 Many users of Cyrix CPUs have had to disable the cache in their
@@ -106,7 +106,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code.
 </para>
    </sect3>
 
-   <sect3 arch="i386"><title>Peripheral Hardware Settings</title>
+   <sect3 arch="x86"><title>Peripheral Hardware Settings</title>
 <para>
 
 You may have to change some settings or jumpers on your computer's
@@ -124,7 +124,7 @@ amount of RAM in your system.
 </para>
    </sect3>
 
-   <sect3 arch="i386" id="usb-keyboard-config">
+   <sect3 arch="x86" id="usb-keyboard-config">
    <title>USB BIOS support and keyboards</title>
 <para>