svn commit: r43360 - head/ja_JP.eucJP/books/handbook/basics

[Ryusuke SUZUKI]

Author: ryusuke
Date: Fri Dec 20 22:32:58 2013
New Revision: 43360
URL: http://svnweb.freebsd.org/changeset/doc/43360

Log:
  - Merge the following from the English version:
  
  	r17931 -> r17937	head/ja_JP.eucJP/books/handbook/basics/chapter.xml

Modified:
  head/ja_JP.eucJP/books/handbook/basics/chapter.xml

Modified: head/ja_JP.eucJP/books/handbook/basics/chapter.xml
==============================================================================
--- head/ja_JP.eucJP/books/handbook/basics/chapter.xml	Fri Dec 20 20:14:37 2013	(r43359)
+++ head/ja_JP.eucJP/books/handbook/basics/chapter.xml	Fri Dec 20 22:32:58 2013	(r43360)
@@ -3,7 +3,7 @@
      The FreeBSD Documentation Project
      The FreeBSD Japanese Documentation Project
 
-     Original revision: r17931
+     Original revision: r17937
      $FreeBSD$
 -->
 <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="basics">
@@ -1825,10 +1825,10 @@ console none                            
     <para>So, why are there so many different formats?</para>
 
     <para>Back in the dim, dark past, there was simple hardware.  This
-      simple hardware supported a simple, small system. a.out was
+      simple hardware supported a simple, small system. <filename>a.out</filename> was
       completely adequate for the job of representing binaries on this
       simple system (a PDP-11). As people ported Unix from this simple
-      system, they retained the a.out format because it was sufficient
+      system, they retained the <filename>a.out</filename> format because it was sufficient
       for the early ports of Unix to architectures like the Motorola
       68k, VAXen, etc.</para>
 
@@ -1874,18 +1874,18 @@ console none                            
       support for building cross compilers, plugging in different
       formats at will, etc. Since many people wanted to build cross
       compilers targeting FreeBSD, they were out of luck since the
-      older sources that FreeBSD had for as and ld were not up to the
-      task. The new gnu tools chain (binutils) does support cross
+      older sources that FreeBSD had for <application>as</application> and <application>ld</application> were not up to the
+      task. The new GNU tools chain (<application>binutils</application>) does support cross
       compiling, <acronym>ELF</acronym>, shared libraries, C++
       extensions, etc. In addition, many vendors are releasing
       <acronym>ELF</acronym> binaries, and it is a good thing for
       FreeBSD to run them.</para>
 
-    <para><acronym>ELF</acronym> is more expressive than a.out and
+    <para><acronym>ELF</acronym> is more expressive than <filename>a.out</filename> and
       allows more extensibility in the base system. The
       <acronym>ELF</acronym> tools are better maintained, and offer
       cross compilation support, which is important to many people.
-      <acronym>ELF</acronym> may be a little slower than a.out, but
+      <acronym>ELF</acronym> may be a little slower than <filename>a.out</filename>, but
       trying to measure it can be difficult. There are also numerous
       details that are different between the two in how they map
       pages, handle init code, etc. None of these are very important,