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.

4 files changed, 13 insertions, 13 deletions

diff --git a/eu/boot-installer/i386.xml b/eu/boot-installer/i386.xml
index 0867c918a..6a2727f83 100644
--- a/eu/boot-installer/i386.xml
+++ b/eu/boot-installer/i386.xml
@@ -1,7 +1,7 @@
 <!-- retain these comments for translator revision tracking -->
 <!-- original version: 16879 untranslated -->
 
-  <sect2 arch="i386"><title>Booting from a CD-ROM</title>
+  <sect2 arch="x86"><title>Booting from a CD-ROM</title>
 
 &boot-installer-intro-cd.xml;
 
@@ -98,7 +98,7 @@ installing via this method.
 
 
 
-  <sect2 arch="i386" id="install-from-dos">
+  <sect2 arch="x86" id="install-from-dos">
   <title>Booting from a DOS partition</title>
 
 &boot-installer-intro-hd.xml;
@@ -130,7 +130,7 @@ bf2.4 flavor. The symptom of the problem is an
   </sect2>
 
 
-  <sect2 arch="i386" id="boot-initrd">
+  <sect2 arch="x86" id="boot-initrd">
   <title>Booting from linux using <command>LILO</command> or
   <command>GRUB</command></title>
 <para>
@@ -273,7 +273,7 @@ your hard drive will be un-bootable for a short period of time.
 </para>
   </sect2>
 
-  <sect2 arch="i386" id="usb-boot">
+  <sect2 arch="x86" id="usb-boot">
   <title>Booting from USB memory stick</title>
 <para>
 
@@ -296,7 +296,7 @@ it asks for the root floppy, simply press &enterkey;. You should see
 </para>
   </sect2>
 
-  <sect2 arch="i386" id="floppy-boot">
+  <sect2 arch="x86" id="floppy-boot">
   <title>Booting from Floppies</title>
 <para>
 
@@ -374,7 +374,7 @@ contents are loaded into memory. The installer program
 </para>
   </sect2>
   
-  <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title>
+  <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title>
  
 &boot-installer-intro-net.xml;
  
@@ -449,7 +449,7 @@ debian/dists/sarge/main/installer-i386/current/doc/INSTALLATION-HOWTO
    </sect3>
   </sect2>
 
-  <sect2 arch="i386"><title>i386 Boot Parameters</title>
+  <sect2 arch="x86"><title>i386 Boot Parameters</title>
 <para>
 
 If you are booting from the boot floppy or from CD-ROM you will be
@@ -498,7 +498,7 @@ console features. See <xref linkend="boot-parms"/> for details.
   </sect2>
 
 
-  <sect2 arch="i386">
+  <sect2 arch="x86">
   <title>System freeze during the PCMCIA configuration phase</title>
 
 <para>
@@ -527,7 +527,7 @@ installer.
 </para>
   </sect2>
 
-  <sect2 arch="i386">
+  <sect2 arch="x86">
   <title>System freeze while loading the USB modules</title>
 <para>
 
diff --git a/eu/boot-installer/intro-cd.xml b/eu/boot-installer/intro-cd.xml
index 4959075fa..fd4655de0 100644
--- a/eu/boot-installer/intro-cd.xml
+++ b/eu/boot-installer/intro-cd.xml
@@ -7,7 +7,7 @@ The easiest route for most people will be to use a
 <ulink url="http://www.debian.org/CD/vendors/">set of Debian CDs</ulink>. 
 If you have a CD set, and if your machine supports booting directly off
 the CD, great!  Simply 
-<phrase arch="i386">
+<phrase arch="x86">
 configure your system for booting off a CD as described in 
 <xref linkend="boot-dev-select"/>,
 </phrase> 
diff --git a/eu/boot-installer/parameters.xml b/eu/boot-installer/parameters.xml
index b8a9c9784..5367d8c43 100644
--- a/eu/boot-installer/parameters.xml
+++ b/eu/boot-installer/parameters.xml
@@ -214,7 +214,7 @@ you can disable the feature by the parameter
 symptoms are error messages about bterm or bogl, a blank screen, or
 a freeze within a few minutes after starting the install.
 
-</para><para arch="i386">
+</para><para arch="x86">
 
 The <userinput>video=vga16:off</userinput> argument may also be used
 to disable the framebuffer. Such problems have been reported on a Dell
diff --git a/eu/boot-installer/trouble.xml b/eu/boot-installer/trouble.xml
index 2db641c44..b393ca3d9 100644
--- a/eu/boot-installer/trouble.xml
+++ b/eu/boot-installer/trouble.xml
@@ -67,7 +67,7 @@ your kernel.  The installer requires
 </para><para>
 
 Often, problems can be solved by removing add-ons and peripherals, and
-then trying booting again.  <phrase arch="i386">Internal modems, sound
+then trying booting again.  <phrase arch="x86">Internal modems, sound
 cards, and Plug-n-Play devices can be especially problematic.</phrase>
 
 </para><para>
@@ -168,7 +168,7 @@ report, this information will be included automatically.
 
 <informalexample><screen>
 
-<phrase arch="i386">
+<phrase arch="x86">
 flavor:        <replaceable>flavor of image you are using</replaceable>
 </phrase>
 architecture:  &architecture;