# HG changeset patch
# User Yoshiki Yazawa <yaz@honeyplanet.jp>
# Date 1235231297 -32400
# Node ID 1604f2b2054b1fb6b23ef472a984794f54df7661
# Parent  63060ad65ab849b9a147031a4ef8fe41e12c6643
more intro.tex

diff -r 63060ad65ab8 -r 1604f2b2054b ja/intro.tex
--- a/ja/intro.tex	Sat Feb 21 23:56:55 2009 +0900
+++ b/ja/intro.tex	Sun Feb 22 00:48:17 2009 +0900
@@ -291,35 +291,60 @@
 %\section{Trends in revision control}
 \section{リビジョンコントロールのトレンド}
 
-There has been an unmistakable trend in the development and use of
-revision control tools over the past four decades, as people have
-become familiar with the capabilities of their tools and constrained
-by their limitations.
+%There has been an unmistakable trend in the development and use of
+%revision control tools over the past four decades, as people have
+%become familiar with the capabilities of their tools and constrained
+%by their limitations.
+
+リビジョンコントロールツールの開発と使用において，過去20年間ツールに親し
+み，ツールの制限を知るに従って，紛れもないトレンドが存在している．
 
-The first generation began by managing single files on individual
-computers.  Although these tools represented a huge advance over
-ad-hoc manual revision control, their locking model and reliance on a
-single computer limited them to small, tightly-knit teams.
+%The first generation began by managing single files on individual
+%computers.  Although these tools represented a huge advance over
+%ad-hoc manual revision control, their locking model and reliance on a
+%single computer limited them to small, tightly-knit teams.
+
+第一世代のツールは単一のファイルを個別のコンピュータの上で管理した．アド
+ホックな手動によるリビジョンコントロールと比べて大幅な進歩があったが，ロッ
+クモデルと単一コンピュータへの依存のため，利用は小規模で緊密なチームに限
+られた．
 
-The second generation loosened these constraints by moving to
-network-centered architectures, and managing entire projects at a
-time.  As projects grew larger, they ran into new problems.  With
-clients needing to talk to servers very frequently, server scaling
-became an issue for large projects.  An unreliable network connection
-could prevent remote users from being able to talk to the server at
-all.  As open source projects started making read-only access
-available anonymously to anyone, people without commit privileges
-found that they could not use the tools to interact with a project in
-a natural way, as they could not record their changes.
+%The second generation loosened these constraints by moving to
+%network-centered architectures, and managing entire projects at a
+%time.  As projects grew larger, they ran into new problems.  With
+%clients needing to talk to servers very frequently, server scaling
+%became an issue for large projects.  An unreliable network connection
+%could prevent remote users from being able to talk to the server at
+%all.  As open source projects started making read-only access
+%available anonymously to anyone, people without commit privileges
+%found that they could not use the tools to interact with a project in
+%a natural way, as they could not record their changes.
 
-The current generation of revision control tools is peer-to-peer in
-nature.  All of these systems have dropped the dependency on a single
-central server, and allow people to distribute their revision control
-data to where it's actually needed.  Collaboration over the Internet
-has moved from constrained by technology to a matter of choice and
-consensus.  Modern tools can operate offline indefinitely and
-autonomously, with a network connection only needed when syncing
-changes with another repository.
+第二世代のツールは，ネットワーク中心のアーキテクチャに移行することで，そ
+れまでの制限を緩和し，プロジェクト全体を同時に管理した．プロジェクトが大
+きく成長すると，新たな問題に直面した．クライアントがサーバに頻繁に通信す
+るため，大規模プロジェクトではサーバの規模が問題になった．信頼性のないネッ
+トワーク接続はリモートユーザがサーバと通信するのを妨げた．オープンソース
+プロジェクトがコミット権のないユーザにも匿名の読み出し専用アクセスを提供
+するようになると，ツールは彼らの行った変更を記録できないため，プロジェク
+トとやりとりを行う自然な手段とは言えないことがわかった．
+
+%The current generation of revision control tools is peer-to-peer in
+%nature.  All of these systems have dropped the dependency on a single
+%central server, and allow people to distribute their revision control
+%data to where it's actually needed.  Collaboration over the Internet
+%has moved from constrained by technology to a matter of choice and
+%consensus.  Modern tools can operate offline indefinitely and
+%autonomously, with a network connection only needed when syncing
+%changes with another repository.
+
+現行世代のリビジョンコントロールツールは，ピアツーピアである．これらのシ
+ステムの全てが単一の中央サーバへ依存しなくなっており，リビジョンコントロー
+ルデータを必要なところへ分散させることができるようになっている．インター
+ネットを通じた共同作業は技術的制約から離れて，選択と合意によって行われる
+ようになった．現代のツールはオフラインのままでも，自律的にも動作するよう
+になっている．ネットワーク接続は変更を別のリポジトリと同期させる時にのみ
+必要である．
 
 %\section{A few of the advantages of distributed revision control}
 \section{分散リビジョンコントロールの利点}
diff -r 63060ad65ab8 -r 1604f2b2054b ja/todo.txt
--- a/ja/todo.txt	Sat Feb 21 23:56:55 2009 +0900
+++ b/ja/todo.txt	Sun Feb 22 00:48:17 2009 +0900
@@ -8,7 +8,7 @@
 hg_id.tex	noneed
 hgext.tex	100%
 hook.tex	50%
-intro.tex
+intro.tex	40%
 license.tex
 mq-collab.tex   100%
 mq-ref.tex	100%