[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[d-i doc] 翻訳更新

鍋太郎です。

インストールマニュアルの訳を追随しました。

本文と差分を添付しますので査読をお願いいたします。
＃先ほど、リポジトリへのコミット権をいただきましたのでコミットしておきます。

アーカイブの内容は以下になります。
$ tar ztf d-i-update0518.tar.gz
ja/bookinfo.xml
ja/install-methods/install-tftp.xml
ja/install-methods/usb-setup/i386.xml
ja/install-methods/boot-drive-files.xml
ja/install-methods/boot-usb-files.xml
ja/install-methods/create-floppy.xml
ja/install-methods/ipl-tape.xml
ja/install-methods/tftp/bootp.xml

-- 
+--------------------------------------------------------+
 倉澤 望(鍋太郎) 
 KURASAWA Nozomu (nabetaro)  <nabetaro @ caldron.jp>
 GnuPG FingerPrint:
    C4E5 7063 FD75 02EB E71D  559B ECF6 B9D2 8147 ADFB
+--------------------------------------------------------+

Attachment: d-i-update0518.tar.gz
Description: Binary data

Index: ja/bookinfo.xml
===================================================================
--- ja/bookinfo.xml	(ӥ 37399)
+++ ja/bookinfo.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 34719 -->
+<!-- original version: 36879 -->
 
 <bookinfo id="debian_installation_guide">
 <title>&debian; 󥹥ȡ륬</title>
@@ -18,7 +18,7 @@
 &debian; &release; ƥ (ɥ͡ <quote>&releasename;</quote>)
 Υ󥹥ȡǤ
 ޤ˾ܤؤΥݥ󥿤䡢
-ۤȤɤο Debian ƥбˡ˴ؤޤǤޤ
+ Debian ƥۤˡˤڤƤޤ
 </para>
 
 <para>
@@ -46,7 +46,7 @@
 Υޥ˥奢ο (ΥƥФơ
 Ǥ¤褯񤫤Ƥޤ) ϡ󥿡ͥå 
 (<ulink url="&url-d-i;">&d-i; home page</ulink>) ǸĤޤ
-ޤɲä⸫ĤǤ礦
+ޤǡɲ⸫ĤǤ礦
 </para></warning>
 
 <note condition="checked"><para>
@@ -61,10 +61,34 @@
 &releasename; θ꡼ˡ
 Ĥѹäκƹײ褷Ƥޤ
 Υޥ˥奢οǤϡ󥿡ͥå 
-(<ulink url="&url-d-i;">&d-i; home page</ulink>) ǸĤ뤫Τޤ
-ޤɲ⸫ĤǤ礦
+(<ulink url="&url-d-i;">&d-i; home page</ulink>) ǸĤޤ
+ޤǡɲ⸫ĤǤ礦
 </para></note>
 </para>
+
+<para condition="bookinfo-langteam">
+<!--
+Translators can use this paragraph to provide some information about
+the status of the translation, the people behind it, how to contact
+the team, etc.
+
+See build/lang-options/README on how to enable this paragraph.
+Its condition is "bookinfo_langteam".
+-->
+ܸϡ
+  (1997 ǯ)
+  (1998-1999 ǯ)
+ƣ  (1998-2000 ǯ)
+ ˡë ŸȬ ԡGuangcheng Wen (1999 ǯ)
+  졢  ҹƣ ء ͺ (2002 ǯ)
+ ͧϡ ߷ ˾ (2002-2006 ǯ)
+ޤ
+</para>
+
+<para condition="bookinfo-langteam">
+ܸˤĤƤΤ䤤碌ϡ
+debian-doc@debian.or.jp ؤꤤޤ( subscribe)
+</para>
 </abstract>
 
 <copyright>
@@ -74,18 +98,6 @@
  <holder>the Debian Installer team</holder>
 </copyright>
 
-<!--
-ܸˤĤƤϡ
-  (1997 ǯ)
-  (19981999 ǯ)
- ˡë ŸȬ ԡGuangcheng Wen (1999 ǯ)
-ƣ  (1998-2000 ǯ)
-  졢  ҹƣ ء
- ͧϡ  ͺ (2002 ǯ)
-߷ ˾ ͧϡ  (2002-2005 ǯ)
-ޤ
-
-:嵭ʸɽǤ?
 -->
 
 <legalnotice>
Index: ja/install-methods/install-tftp.xml
===================================================================
--- ja/install-methods/install-tftp.xml	(ӥ 37399)
+++ ja/install-methods/install-tftp.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35613 -->
+<!-- original version: 36841 -->
 
  <sect1 condition="supports-tftp" id="install-tftp">
  <title>TFTP ͥåȥ֡ѥեν</title>
@@ -341,14 +341,15 @@
 <!--
 For DECstations, there are tftpimage files for each subarchitecture,
 which contain both kernel and installer in one file. The naming
-convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img.
+convention is
+<filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>.
 Copy the tftpimage file you would like to use to
 <userinput>/tftpboot/tftpboot.img</userinput> if you work with the
 example BOOTP/DHCP setups described above.
 -->
 DECstation ˤϡƥ֥ƥ㤴Ȥ tftp ᡼ꡢ
 ͥȥ󥹥ȡ餬ҤȤĤΥ᡼˼Ƥޤ
-̿̾§ <replaceable>subarchitecture</replaceable>/netboot-boot.img Ǥ
+̿̾§ <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename> Ǥ
 ҤΤ褦 BOOTP/DHCP ꤷΤǤ顢
 Ȥ tftp ᡼ <userinput>/tftpboot/tftpboot.img</userinput>
 ˥ԡޤ
@@ -476,45 +477,39 @@
 <para>
 
 <!--
-SPARC architectures for instance use the subarchitecture names, such
-as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the
-architecture is left blank, so the file the client looks for is just
-<filename>client-ip-in-hex</filename>.  Thus, if your system
-subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename
-would be <filename>C0A80103.SUN4C</filename>. An easy way to determine
-this is to pull up a shell on another Unix machine and:
-
-this is to enter the following command in a shell (assuming the
-machine's intended IP is 10.0.0.4).
+Some SPARC architectures add the subarchitecture names, such as
+<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus,
+if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3,
+the filename would be <filename>C0A80103.SUN4C</filename>. However,
+there are also subarchitectures where the file the client looks for is
+just <filename>client-ip-in-hex</filename>. An easy way to determine the
+hexadecimal code for the IP address is to enter the following command
+in a shell (assuming the machine's intended IP is 10.0.0.4).
 -->
 <!--nabetaro Ĥޤ -->
-SPARC ƥ (: <replaceable>client-architecture</replaceable> )
+SPARC ƥǤϡ
 <quote>SUN4M</quote>  <quote>SUN4C</quote> Τ褦
-֥ƥ̾Ȥޤ
-ˤäƤϥƥ㤬ΤȤ⤢ꡢ
-ξ祯饤Ȥõե
-<filename>client-ip-in-hex</filename> ˤʤޤ
+֥ƥ̾ե̾ɲäޤ
 㤨СƥΥ֥ƥ㤬 SUN4C 
-IP  192.168.1.3 ξϡե̾
-<filename>C0A80103.SUN4C</filename> Ȥʤޤ
-ꤹñˡϡʲΥޥɤ򥷥Ϥޤ
-(ͽꤷƤ IP ɥ쥹 10.0.0.4 Ȥ)
+IP ɥ쥹 192.168.1.3 ξ硢
+ե̾ <filename>C0A80103.SUN4C</filename> Ȥʤޤ
+饤Ȥõե뤬
+<filename>client-ip-in-hex</filename> Ȥʤ륵֥ƥ⤢ޤ
+IP ɥ쥹 16 ɽñˤϡ
+ʲΥޥɤ򥷥ϤƤ
+(ꤷƤ IP ɥ쥹 10.0.0.4 Ǥ)
 
 <informalexample><screen>
 $ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4
 </screen></informalexample>
  
 <!--
-This will spit out the IP in hexadecimal; to get to the correct
-filename, you will need to change all letters to uppercase and
-if necessary append the subarchitecture name.
+To get to the correct filename, you will need to change all letters to
+uppercase and if necessary append the subarchitecture name.
 -->
-ͽꤷƤޥ IP ɥ쥹 10.0.0.4 ξ硢
- IP ɥ쥹 16 ʿǽϤޤ
 ե̾ˤϡʸ򤹤٤ʸѹ
 (ɬפʤ) ֥ƥ̾ɲäʤФʤޤ
 
-
 </para><para>
 
 <!--
@@ -597,7 +592,7 @@
 
 <!--
 You don't have to configure DHCP in a special way because you'll pass the
-full path of the file to the loaded to CFE.
+full path of the file to be loaded to CFE.
 -->
 CFE ˥ɤեΥեѥϤƤ뤿ᡢ
 ü DHCP 򤹤ɬפϤޤ
Index: ja/install-methods/usb-setup/i386.xml
===================================================================
--- ja/install-methods/usb-setup/i386.xml	(ӥ 37399)
+++ ja/install-methods/usb-setup/i386.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33725-->
+<!-- original version: 36841-->
 
    <sect3 arch="i386">
    <title>&arch-title; Ǥ USB ƥåΥѡƥʬ</title>
@@ -19,16 +19,16 @@
 Since most USB sticks come pre-configured with a single FAT16
 partition, you probably won't have to repartition or reformat the
 stick.  If you have to do that anyway, use <command>cfdisk</command>
-or any other partitioning tool for creating a FAT16 partition and then
+or any other partitioning tool to create a FAT16 partition, and then
 create the filesystem using:
 -->
 ۤȤɤ USB ƥåϡ
 FAT16 ѡƥ 1 ĤǤ餫ꤵƤΤǡ
 餯 USB ƥåΥѡƥʬΤľ䡢
-ƥեޥåȤɬפʤǤ礦
+ƥեޥåȤɬפޤ
 ɤƤ⤷ʤФʤʤϡ
 <command>cfdisk</command> ¾ΥѡƥʬġȤäơ
-FAT16 ѡƥưʲϤƤ
+FAT16 ѡƥʲΤ褦˥ե륷ƥƤ
 
 <informalexample><screen>
 # mkdosfs /dev/<replaceable>sda1</replaceable>
Index: ja/install-methods/boot-drive-files.xml
===================================================================
--- ja/install-methods/boot-drive-files.xml	(ӥ 37399)
+++ ja/install-methods/boot-drive-files.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28997 -->
+<!-- original version: 36841 -->
 
  <sect1 condition="bootable-disk" id="boot-drive-files">
  <title>ϡɥǥưեν</title>
@@ -262,14 +262,14 @@
 <!--
 Make a note of the partition number of the MacOS partition where you
 place these files. If you have the MacOS <command>pdisk</command>
-program, you can use the L command to check for the partition
-number. You will need this partition number for the command you type
-at the Open Firmware prompt when you boot the installer.
+program, you can use the <command>L</command> command to check for the
+partition number. You will need this partition number for the command
+you type at the Open Firmware prompt when you boot the installer.
 -->
 Υե֤ MacOS ѡƥ
 ѡƥֹϿƤޤ礦
 MacOS  <command>pdisk</command> ץबС
-L ޥɤǥѡƥֹǧǤޤ
+<command>L</command> ޥɤǥѡƥֹǧǤޤ
 Υѡƥֹϡ󥹥ȡưȤ
 Open Firmware ץץȤϤ륳ޥɤɬפȤʤޤ
 
Index: ja/install-methods/boot-usb-files.xml
===================================================================
--- ja/install-methods/boot-usb-files.xml	(ӥ 37399)
+++ ja/install-methods/boot-usb-files.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 32124 -->
+<!-- original version: 37295 -->
 
  <sect1 condition="bootable-usb" id="boot-usb-files">
  <title>USB ꥹƥåǤεưѥեν</title>
@@ -8,22 +8,22 @@
 <para>
 
 <!--
-For preparing the USB stick you will need a system where GNU/Linux is
+To prepare the USB stick, you will need a system where GNU/Linux is
 already running and where USB is supported. You should ensure that the
 usb-storage kernel module is loaded (<userinput>modprobe
 usb-storage</userinput>) and try to find out which SCSI device the USB
 stick has been mapped to (in this example
 <filename>/dev/sda</filename> is used). To write to your stick, you
-will probably have to turn off its write protection switch.
+may have to turn off its write protection switch.
 -->
-USB ƥåνΤᡢ
+USB ƥåν򤹤ˤϡ
 GNU/Linux ưƤơUSB 򥵥ݡȤƤ륷ƥबɬפˤʤޤ
 usb-storage ͥ⥸塼򤭤ȥɤ 
 (<userinput>modprobe usb-storage</userinput>)
 USB ƥåޥåԥ󥰤ƤΤɤ SCSI ǥХ򸡽ФƤߤ٤Ǥ
 (Ǥ <filename>/dev/sda</filename> Ѥޤ) 
-餯 USB ƥå˽񤭹िˡ
-饤ȥץƥȥåڤʤФʤޤ
+USB ƥå˽񤭹िˡ
+饤ȥץƥȥåڤɬפޤ
 
 </para><para>
 
@@ -134,17 +134,26 @@
 &usb-setup-i386.xml;
 &usb-setup-powerpc.xml;
 
-   <sect3>
+   </sect2>
+   <sect2>
+<!--
+   <title>Adding an ISO image</title>
+-->
    <title>ISO ᡼ɲ</title>
 <para>
 
 <!--
-Now you should put any Debian ISO image (businesscard, netinst or even
-a full one) onto your stick (if it fits). The file name of such an
+The installer will look for a Debian ISO image on the stick as its source
+for additional data needed for the installation. So your next step is to
+copy a Debian ISO image (businesscard, netinst or even a full CD image)
+onto your stick (be sure to select one that fits). The file name of the
 image must end in <filename>.iso</filename>.
 -->
-٤ϡDebian ISO ᡼ (̾ɡnetinstǤΤ줫) 
-USB ƥå (ʤ) ޤ礦
+󥹥ȡϡUSB ƥå Debian ISO ᡼õ
+󥹥ȡɬפɲåǡμȤޤ
+Ǥ鼡Υƥåפϡ
+Debian ISO ᡼ (̾ɡnetinstǤΤ줫) 
+USB ƥå (Τ) 뤳ȤǤ
 ISO ᡼Υե̾ <filename>.iso</filename> 
 ǽäƤʤФʤޤ
 
@@ -177,11 +186,14 @@
 饤ȥץƥȥåͭˤƤ
 
 </para>
-   </sect3>
+  </sect2>
 
-   <!-- TODO: doesn't this section belong later? -->
-   <sect3 arch="i386">
-   <title>USB ƥåεư</title>
+  <!-- TODO: doesn't this section belong later? -->
+  <sect2 arch="i386">
+<!--
+  <title>Booting the USB stick</title>
+-->
+  <title>USB ƥåεư</title>
 <warning><para>
 
 <!--
@@ -200,6 +212,5 @@
 </screen></informalexample>
 
 </para></warning>
-   </sect3>
   </sect2>
  </sect1>
Index: ja/install-methods/create-floppy.xml
===================================================================
--- ja/install-methods/create-floppy.xml	(ӥ 37399)
+++ ja/install-methods/create-floppy.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 -->
+<!-- original version: 36841 -->
 
  <sect1 condition="supports-floppy-boot" id="create-floppy">
  <title>ǥ᡼Υեåԡκ</title>
@@ -17,19 +17,20 @@
 </para><para arch="powerpc">
 
 <!--
-Floppy disk booting reportedly fails on Mac USB floppy drives.
+Booting the installer from floppy disk reportedly fails on Mac USB
+floppy drives.
 -->
-Mac USB եåԡɥ饤֤Ǥ
-եåԡǥεưϤǤʤǤ
+Mac USB եåԡɥ饤֤Ǥϡ
+եåԡǥ饤󥹥ȡưǤʤǤ
 
 </para><para arch="m68k">
 
 <!--
-Floppy disk booting is not supported on Amigas or
+Booting the installer from floppy disk is not supported on Amigas or
 68k Macs.
 -->
 Amiga  68k Mac Ǥϡ
-եåԡεưϥݡȤƤޤ
+եåԡ饤󥹥ȡεư򥵥ݡȤƤޤ
 
 </para><para>
 
@@ -57,12 +58,11 @@
 </para><para>
 
 <!--
-There are different techniques for creating floppies from disk images,
-which depend on your platform.  This section describes how to create
-floppies from disk images on different platforms.
+There are different techniques for creating floppies from disk images.
+This section describes how to create floppies from disk images on
+different platforms.
 -->
-ץåȥեˤäơ
-ǥ᡼եåԡˡϰۤʤޤ
+ǥ᡼եåԡˡˤϰ㤤ޤ
 Ǥϡ줾Υץåȥեˤơ
 ǥ᡼եåԡˡޤ
 
Index: ja/install-methods/ipl-tape.xml
===================================================================
--- ja/install-methods/ipl-tape.xml	(ӥ 37399)
+++ ja/install-methods/ipl-tape.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 -->
+<!-- original version: 36841 -->
 
  <sect1 arch="s390" id="ipl-tape">
  <title>IPL ơפκ</title>
@@ -32,7 +32,7 @@
 <filename>parmfile.debian</filename>, 
 <filename>initrd.debian</filename> Ǥ
 Υե <filename>tape</filename> ֥ǥ쥯ȥˤޤ
-<xref linkend="where-files"/> 򻲾ȤƤ
+<xref linkend="where-files"/> 
 
 </para>
  </sect1>
Index: ja/install-methods/tftp/bootp.xml
===================================================================
--- ja/install-methods/tftp/bootp.xml	(ӥ 37399)
+++ ja/install-methods/tftp/bootp.xml	(ȥԡ)
@@ -1,24 +1,28 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 35613 -->
+<!-- original version: 36841 -->
 
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
+<!--
+  <title>Setting up BOOTP server</title>
+-->
   <title>BOOTP Ф</title>
 <para>
 
 <!--
-There are two BOOTP servers available for GNU/Linux, the CMU
-<command>bootpd</command> and the other is actually a DHCP server, ISC
-<command>dhcpd</command>, which are contained in the
+There are two BOOTP servers available for GNU/Linux. The first is CMU
+<command>bootpd</command>. The other is actually a DHCP server: ISC
+<command>dhcpd</command>. In &debian; these are contained in the
 <classname>bootp</classname> and <classname>dhcp</classname> packages
-in &debian;.
+respectively.
 -->
-GNU/Linux ǻȤ BOOTP ФĤޤ
-CMU  <command>bootpd</command> ȡ⤦Ĥϼºݤˤ DHCP ФʤΤǤ
-ISC  <command>dhcpd</command> Ǥ줾 &debian; Ǥ
+GNU/Linux ǻȤ BOOTP Ф 2 Ĥޤ
+ҤȤĤ CMU  <command>bootpd</command> Ǥ
+⤦ 1 Ĥϼºݤ DHCP ФǤISC  <command>dhcpd</command> Ǥ
+&debian; Ǥϡ
 <classname>bootp</classname> ѥå <classname>dhcp</classname> 
-ѥåäƤޤ
+ѥåˤ줾äƤޤ
 
 </para><para>
 
@@ -27,14 +31,14 @@
 add) the relevant line in <filename>/etc/inetd.conf</filename>.  On
 &debian;, you can run <userinput>update-inetd -\-enable
 bootps</userinput>, then <userinput>/etc/init.d/inetd
-reload</userinput> to do so. Elsewhere, the line in question should
-look like:
+reload</userinput> to do so. Just in case your BOOTP server does not
+run Debian, the line in question should look like:
 -->
 CMU <command>bootpd</command> Ȥϡޤ <filename>/etc/inetd.conf</filename> ե
 Ԥ򥢥󥳥 (ޤɲ) ɬפޤ
 &debian; Ǥ <userinput>update-inetd --enable bootps</userinput> ¹Ԥ
 ³ <userinput>/etc/init.d/inetd reload</userinput> Ȥ OK Ǥ
-ιԤϼΤ褦ʤΤǤ
+ǰΤᡢBOOTP Ф Debian ưޤ󡣰ʲΤ褦ˤޤ
 
 <informalexample><screen>
 bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120