Commits

Tohru Ike  committed 9be49f5 Merge

merge origin default into pypyja

  • Participants
  • Parent commits 6d3ff11, 11d352c

Comments (0)

Files changed (9)

 .project
 .pydevproject
 
+pypy/doc/.omakedb
+pypy/doc/.omakedb.lock
+pypy/doc/OMakefile
+pypy/doc/OMakefile.omc
+pypy/doc/OMakeroot
+pypy/doc/OMakeroot.omc
+
 syntax: regexp
 ^testresult$
 ^site-packages$

File pypy/doc/cpython_differences.rst

+..
+  ====================================
+  Differences between PyPy and CPython
+  ====================================
+
 ====================================
-Differences between PyPy and CPython
+PyPyとCPythonの違い
 ====================================
 
-This page documents the few differences and incompatibilities between
-the PyPy Python interpreter and CPython.  Some of these differences
-are "by design", since we think that there are cases in which the
-behaviour of CPython is buggy, and we do not want to copy bugs.
+..
+  This page documents the few differences and incompatibilities between
+  the PyPy Python interpreter and CPython.  Some of these differences
+  are "by design", since we think that there are cases in which the
+  behaviour of CPython is buggy, and we do not want to copy bugs.
 
-Differences that are not listed here should be considered bugs of
-PyPy.
+このページはPyPy PythonインタープリターとCPythonとのわずかな違いと非互換性について説明します。
+これらの違いのいくつかは「デザイン」であり、CPythonでのバグっぽい挙動に対して、
+バグをコピーしたくないと思うからです。
 
+..
+  Differences that are not listed here should be considered bugs of
+  PyPy.
 
-Extension modules
+ここに記載されていない違いは、PyPyのバグだと考えられます。
+
+..
+  Extension modules
+  -----------------
+
+拡張モジュール
 -----------------
 
-List of extension modules that we support:
+..
+  List of extension modules that we support:
 
-* Supported as built-in modules (in `pypy/module/`_):
+サポートしている拡張モジュールのリスト:
+
+..
+  * Supported as built-in modules (in `pypy/module/`_):
+
+* 組み込みモジュールとしてサポート ( `pypy/module/`_):
 
     __builtin__
     `__pypy__`_
     zipimport
     zlib
 
-  When translated to Java or .NET, the list is smaller; see
-  `pypy/config/pypyoption.py`_ for details.
+..
+    When translated to Java or .NET, the list is smaller; see
+    `pypy/config/pypyoption.py`_ for details.
 
-  When translated on Windows, a few Unix-only modules are skipped,
-  and the following module is built instead:
+  Javaか.NETへ変換する際には、より少なくなります。
+  詳細は `pypy/config/pypyoption.py`_ を参照して下さい。
+
+..
+    When translated on Windows, a few Unix-only modules are skipped,
+    and the following module is built instead:
+
+  Windowsで解釈される際には、Unixのみのモジュールがいくつかスキップされ、以下のモジュールが代わりにビルドされます:
 
     _winreg
 
-* Supported by being rewritten in pure Python (possibly using ``ctypes``):
-  see the `lib_pypy/`_ directory.  Examples of modules that we
-  support this way: ``ctypes``, ``cPickle``, ``cmath``, ``dbm``, ``datetime``...
-  Note that some modules are both in there and in the list above;
-  by default, the built-in module is used (but can be disabled
-  at translation time).
+..
+  * Supported by being rewritten in pure Python (possibly using ``ctypes``):
+    see the `lib_pypy/`_ directory.  Examples of modules that we
+    support this way: ``ctypes``, ``cPickle``, ``cmath``, ``dbm``, ``datetime``...
+    Note that some modules are both in there and in the list above;
+    by default, the built-in module is used (but can be disabled
+    at translation time).
 
-The extension modules (i.e. modules written in C, in the standard CPython)
-that are neither mentioned above nor in `lib_pypy/`_ are not available in PyPy.
-(You may have a chance to use them anyway with `cpyext`_.)
+* (できる限り ``ctypes`` を使って)ピュアPythonで書き直してサポート: `lib_pypy/`_ ディレクトリを参照。
+  この方法を使ってサポートしたモジュールの例: ``ctypes``, ``cPickle``, ``cmath``, ``dbm``, ``datetime``
+  いくつかのモジュールではそのモジュール内と上記のリストの両方で、標準により、
+  組み込みモジュールが使われる(、しかし解釈時には無効になる)ことに注意しなければなりません。
+
+..
+  The extension modules (i.e. modules written in C, in the standard CPython)
+  that are neither mentioned above nor in `lib_pypy/`_ are not available in PyPy.
+  (You may have a chance to use them anyway with `cpyext`_.)
+
+上で言及されていない、 `lib_pypy/`_ にもない拡張モジュール( 標準CPythonでのCで書かれたモジュール)はPyPyでは利用できません。
+(`cpyext`_ を用いることで利用できるかもしれません。)
 
 .. the nonstandard modules are listed below...
 .. _`__pypy__`: __pypy__-module.html
 .. _`_minimal_curses`: config/objspace.usemodules._minimal_curses.html
 .. _`cpyext`: http://morepypy.blogspot.com/2010/04/using-cpython-extension-modules-with.html
 
+..
+  Differences related to garbage collection strategies
+  ----------------------------------------------------
 
-Differences related to garbage collection strategies
+GC(ガベージコレクション)戦略に関連する違い
 ----------------------------------------------------
 
-Most of the garbage collectors used or implemented by PyPy are not based on
-reference counting, so the objects are not freed instantly when they are no
-longer reachable.  The most obvious effect of this is that files are not
-promptly closed when they go out of scope.  For files that are opened for
-writing, data can be left sitting in their output buffers for a while, making
-the on-disk file appear empty or truncated.
+..
+  Most of the garbage collectors used or implemented by PyPy are not based on
+  reference counting, so the objects are not freed instantly when they are no
+  longer reachable.  The most obvious effect of this is that files are not
+  promptly closed when they go out of scope.  For files that are opened for
+  writing, data can be left sitting in their output buffers for a while, making
+  the on-disk file appear empty or truncated.
 
-Fixing this is essentially not possible without forcing a
-reference-counting approach to garbage collection.  The effect that you
-get in CPython has clearly been described as a side-effect of the
-implementation and not a language design decision: programs relying on
-this are basically bogus.  It would anyway be insane to try to enforce
-CPython's behavior in a language spec, given that it has no chance to be
-adopted by Jython or IronPython (or any other port of Python to Java or
-.NET, like PyPy itself).
+PyPyで使われ、実行されているGCの多くは参照カウントに基づいていませんので、到達不可能になってもオブジェクトは即座に解放されません。
+この影響により、スコープから出ても、ファイルが即座に閉じられません。
+書き出し用に開いたファイルに対して、データをしばらく出力バッファに置いたままにすることができ、ディスク上のファイルを空、または、不完全に見えさせます。
 
-This affects the precise time at which ``__del__`` methods are called, which
-is not reliable in PyPy (nor Jython nor IronPython).  It also means that
-weak references may stay alive for a bit longer than expected.  This
-makes "weak proxies" (as returned by ``weakref.proxy()``) somewhat less
-useful: they will appear to stay alive for a bit longer in PyPy, and
-suddenly they will really be dead, raising a ``ReferenceError`` on the
-next access.  Any code that uses weak proxies must carefully catch such
-``ReferenceError`` at any place that uses them.  (Or, better yet, don't use
-``weakref.proxy()`` at all; use ``weakref.ref()``.)
+..
+  This affects the precise time at which ``__del__`` methods are called, which
+  is not reliable in PyPy (nor Jython nor IronPython).  It also means that
+  weak references may stay alive for a bit longer than expected.  This
+  makes "weak proxies" (as returned by ``weakref.proxy()``) somewhat less
+  useful: they will appear to stay alive for a bit longer in PyPy, and
+  suddenly they will really be dead, raising a ``ReferenceError`` on the
+  next access.  Any code that uses weak proxies must carefully catch such
+  ``ReferenceError`` at any place that uses them.  (Or, better yet, don't use
+  ``weakref.proxy()`` at all; use ``weakref.ref()``.)
 
-There are a few extra implications for the difference in the GC.  Most
-notably, if an object has a ``__del__``, the ``__del__`` is never called more
-than once in PyPy; but CPython will call the same ``__del__`` several times
-if the object is resurrected and dies again.  The ``__del__`` methods are
-called in "the right" order if they are on objects pointing to each
-other, as in CPython, but unlike CPython, if there is a dead cycle of
-objects referencing each other, their ``__del__`` methods are called anyway;
-CPython would instead put them into the list ``garbage`` of the ``gc``
-module.  More information is available on the blog `[1]`__ `[2]`__.
+これは ``__del__`` メソッドが呼ばれる正確な時間に影響し、PyPy(Jython, IronPythonでも)では信頼できません。
+また、弱参照が予想より少し長く生き残るかもしれないことを意味します。
+これは(weakref.proxy()が返すような)「弱いプロキシ」となり、あまり役にたちません。
+PyPy上でほんの少しだけ長く生き残り、突然本当に死亡し、次のアクセスで ``ReferenceError`` を挙げます。
+弱プロキシを使うすべてのコードのあらゆる場所で ``ReferenceError`` を注意深くキャッチしなけばなりません。
+
+..
+  As a side effect, the ``finally`` clause inside a generator will be executed
+  only when the generator object is garbage collected (see `issue 736`__).
+
+副作用として、ジェネレーター内の ``finally`` 節はジェネレーターオブジェクトがGCされたときのみ実行されます。( `issue 736`__ 参照)
+
+.. __: http://bugs.pypy.org/issue736
+
+..
+  There are a few extra implications for the difference in the GC.  Most
+  notably, if an object has a ``__del__``, the ``__del__`` is never called more
+  than once in PyPy; but CPython will call the same ``__del__`` several times
+  if the object is resurrected and dies again.  The ``__del__`` methods are
+  called in "the right" order if they are on objects pointing to each
+  other, as in CPython, but unlike CPython, if there is a dead cycle of
+  objects referencing each other, their ``__del__`` methods are called anyway;
+  CPython would instead put them into the list ``garbage`` of the ``gc``
+  module.  More information is available on the blog `[1]`__ `[2]`__.
+
+GCの違いによっていくつかの特別な影響があります。
+一番顕著なのは、もしオブジェクトが ``__del__`` を持つ場合、PyPyでは ``__del__`` が一度以上呼ばれることはありません。: しかし、CPythonではオブジェクトを復活させ、再度死ぬならば、何回か同じ ``__del__`` を呼びます。
+CPythonではお互いを射すオブジェクトでは ``__del__`` メソッドは「正しい」順番で呼ばれますが、CPythonとは異なり、お互いにオブジェクト参照する死のサイクルがあれば、それらの ``__del__`` メソッドはどこでも呼ばれます。
+CPythonは代わりにgcモジュールの ``garbage`` リストにそれらを入れるでしょう。 
+詳しい情報はブログを参照して下さい。 `[1]`__ `[2]`__
 
 .. __: http://morepypy.blogspot.com/2008/02/python-finalizers-semantics-part-1.html
 .. __: http://morepypy.blogspot.com/2008/02/python-finalizers-semantics-part-2.html
 
 .. __: http://bugs.pypy.org/issue736
 
-Using the default GC called ``minimark``, the built-in function ``id()``
-works like it does in CPython.  With other GCs it returns numbers that
-are not real addresses (because an object can move around several times)
-and calling it a lot can lead to performance problem.
+..
+  Using the default GC called ``minimark``, the built-in function ``id()``
+  works like it does in CPython.  With other GCs it returns numbers that
+  are not real addresses (because an object can move around several times)
+  and calling it a lot can lead to performance problem.
 
-Note that if you have a long chain of objects, each with a reference to
-the next one, and each with a ``__del__``, PyPy's GC will perform badly.  On
-the bright side, in most other cases, benchmarks have shown that PyPy's
-GCs perform much better than CPython's.
+``minimark`` と呼ばれる標準GCを使うことで、ビルトイン関数 ``id()`` はCPythonと同様に動作します。
+他のGCでは(オブジェクトが何度か移動できるので)実際のアドレスと異なる数字を返し、何度も呼ばれることでパフォーマンス問題を引き起こします。
 
-Another difference is that if you add a ``__del__`` to an existing class it will
-not be called::
+..
+  Note that if you have a long chain of objects, each with a reference to
+  the next one, and each with a ``__del__``, PyPy's GC will perform badly.  On
+  the bright side, in most other cases, benchmarks have shown that PyPy's
+  GCs perform much better than CPython's.
+
+オブジェクトの長いチェインがあり、それぞれ次のオブジェクトの参照をもち、それぞれ ``__del__`` を持つ場合、
+PyPy GCのパフォーマンスがひどく悪くなることに注意してください。
+明るい言い方をすると、他のほとんどの場合では、ベンチマークがPyPy GCのパフォーマンスがCPythonよりはるかによくなります。
+
+..
+  Another difference is that if you add a ``__del__`` to an existing class it will
+  not be called::
+
+別の違いは、 ``__del__`` メソッドを既存のクラスに追加すると呼ばれないということです。 ::
 
     >>>> class A(object):
     ....     pass
     >>>> A.__del__ = lambda self: None
     __main__:1: RuntimeWarning: a __del__ method added to an existing type will not be called
 
-Even more obscure: the same is true, for old-style classes, if you attach
-the ``__del__`` to an instance (even in CPython this does not work with
-new-style classes).  You get a RuntimeWarning in PyPy.  To fix these cases
-just make sure there is a ``__del__`` method in the class to start with
-(even containing only ``pass``; replacing or overriding it later works fine).
+..
+  Even more obscure: the same is true, for old-style classes, if you attach
+  the ``__del__`` to an instance (even in CPython this does not work with
+  new-style classes).  You get a RuntimeWarning in PyPy.  To fix these cases
+  just make sure there is a ``__del__`` method in the class to start with
+  (even containing only ``pass``; replacing or overriding it later works fine).
 
+さらによりわかりづらいこと : インスタンスに ``__del__`` メソッドをつける場合、
+旧スタイルクラスでは同じことをしてもエラーになりません。(CPythonでは新スタイルクラスの場合でさえも動作しません)
+PyPyでは実行時に警告が出ます。
+この場合、初めからクラスに ``__del__`` メソッドを持つように修正してください。
+( ``pass`` も含んで渡します; オーバライドすると、正常に動作します。)
 
-Subclasses of built-in types
+..
+  Subclasses of built-in types
+  ----------------------------
+
+組み込み型のサブクラス
 ----------------------------
 
-Officially, CPython has no rule at all for when exactly
-overridden method of subclasses of built-in types get
-implicitly called or not.  As an approximation, these methods
-are never called by other built-in methods of the same object.
-For example, an overridden ``__getitem__()`` in a subclass of
-``dict`` will not be called by e.g. the built-in ``get()``
-method.
+..
+  Officially, CPython has no rule at all for when exactly
+  overridden method of subclasses of built-in types get
+  implicitly called or not.  As an approximation, these methods
+  are never called by other built-in methods of the same object.
+  For example, an overridden ``__getitem__()`` in a subclass of
+  ``dict`` will not be called by e.g. the built-in ``get()``
+  method.
 
-The above is true both in CPython and in PyPy.  Differences
-can occur about whether a built-in function or method will
-call an overridden method of *another* object than ``self``.
-In PyPy, they are generally always called, whereas not in
-CPython.  For example, in PyPy, ``dict1.update(dict2)``
-considers that ``dict2`` is just a general mapping object, and
-will thus call overridden ``keys()``  and ``__getitem__()``
-methods on it.  So the following code prints ``42`` on PyPy
-but ``foo`` on CPython::
+「組み込み型のサブクラスの適切なオーバーライドメソッドがさりげなく呼ばれたり、
+呼ばれなかったりする」場合の公式なCPythonの仕様はありません。
+大体、これらのメソッドは同じオブジェクトの他の組み込みメソッドから決して呼ばれません。
+例えば、 ``dict`` のサブクラスで ``__getitem__()`` をオーバーライドしても、組み込みの ``get()`` などから呼ばれません。
+
+..
+  The above is true both in CPython and in PyPy.  Differences
+  can occur about whether a built-in function or method will
+  call an overridden method of *another* object than ``self``.
+  In PyPy, they are generally always called, whereas not in
+  CPython.  For example, in PyPy, ``dict1.update(dict2)``
+  considers that ``dict2`` is just a general mapping object, and
+  will thus call overridden ``keys()``  and ``__getitem__()``
+  methods on it.  So the following code prints ``42`` on PyPy
+  but ``foo`` on CPython::
+
+前述の内容はCPythonでもPyPyでも正しいです。
+違いは、組込み関数、または、メソッドが ``self`` ではない *別* のオブジェクトのオーバーライドされたメソッドを呼ぶ場合に起こります。
+PyPyでは一般的にいつでも呼ばれますが、CPythonではそうではありません。
+例えば、PyPyでは ``dict1.update(dict2)`` は ``dict2`` が一般的にオブジェクトにマッピングされ、
+``keys()`` と ``__getitem__()`` メソッドがオーバーライドされて呼ばれるとみなされます。
+そのため、下のコードは PyPy では ``42`` を出力しますが、 CPython では ``foo`` を出力します。::
 
     >>>> class D(dict):
     ....     def __getitem__(self, key):
 ``__eq__`` in ``y``) the behavior is exactly the same as CPython.
 
 
-Ignored exceptions
+..
+  Ignored exceptions
+  -----------------------
+
+警告の無視
 -----------------------
 
-In many corner cases, CPython can silently swallow exceptions.
-The precise list of when this occurs is rather long, even
-though most cases are very uncommon.  The most well-known
-places are custom rich comparison methods (like \_\_eq\_\_);
-dictionary lookup; calls to some built-in functions like
-isinstance().
+..
+  In many corner cases, CPython can silently swallow exceptions.
+  The precise list of when this occurs is rather long, even
+  though most cases are very uncommon.  The most well-known
+  places are custom rich comparison methods (like \_\_eq\_\_);
+  dictionary lookup; calls to some built-in functions like
+  isinstance().
 
-Unless this behavior is clearly present by design and
-documented as such (as e.g. for hasattr()), in most cases PyPy
-lets the exception propagate instead.
+めったに発生しない厄介なケースの多くで、CPythonは静かに例外を飲み込み、見えなくすることができます。
+こうなるケースはたくさんありますが、ほとんどのケースはめったに起こりません。
+もっとも有名なのは、カスタム比較メソッド(例 ``__eq__``)、辞書の検索、 ``isinstance()`` などの組み込み関数の呼び出しです。
 
 Object Identity of Primitive Values, ``is`` and ``id``
 -------------------------------------------------------
 above types will return a value that is computed from the argument, and can
 thus be larger than ``sys.maxint`` (i.e. it can be an arbitrary long).
 
+..
+  Miscellaneous
+  -------------
 
-Miscellaneous
+寄せ集め
 -------------
 
-* ``sys.setrecursionlimit()`` is ignored (and not needed) on
-  PyPy.  On CPython it would set the maximum number of nested
-  calls that can occur before a RuntimeError is raised; on PyPy
-  overflowing the stack also causes RuntimeErrors, but the limit
-  is checked at a lower level.  (The limit is currently hard-coded
-  at 768 KB, corresponding to roughly 1480 Python calls on
-  Linux.)
+..
+  * ``sys.setrecursionlimit()`` is ignored (and not needed) on
+    PyPy.  On CPython it would set the maximum number of nested
+    calls that can occur before a RuntimeError is raised; on PyPy
+    overflowing the stack also causes RuntimeErrors, but the limit
+    is checked at a lower level.  (The limit is currently hard-coded
+    at 768 KB, corresponding to roughly 1480 Python calls on
+    Linux.)
 
-* assignment to ``__class__`` is limited to the cases where it
-  works on CPython 2.5.  On CPython 2.6 and 2.7 it works in a bit
-  more cases, which are not supported by PyPy so far.  (If needed,
-  it could be supported, but then it will likely work in many
-  *more* case on PyPy than on CPython 2.6/2.7.)
+* ``sys.setrecursionlimit()`` はPyPyでは(不要であり、)無視されます。
+  CPythonでは、コールのネスト数の最大値を設定します。
+  これを超えると実行エラーが起こります。
+  PyPyで他の実行エラーが原因でスタックがオーバーフローし、制限はより低レベルで
+  チェックされます。
+  (制限は現在768KBでハードコードされ、Linux上では大体1480 Python callに相当します。)
 
-* the ``__builtins__`` name is always referencing the ``__builtin__`` module,
-  never a dictionary as it sometimes is in CPython. Assigning to
-  ``__builtins__`` has no effect.
+..  
+  * assignment to ``__class__`` is limited to the cases where it
+    works on CPython 2.5.  On CPython 2.6 and 2.7 it works in a bit
+    more cases, which are not supported by PyPy so far.  (If needed,
+    it could be supported, but then it will likely work in many
+    *more* case on PyPy than on CPython 2.6/2.7.)
+
+* ``__class__`` への割り当てはCPython 2.5で動作する場合に制限されます。
+  CPython 2.6、2.7ではほんの少し多くの場合でも動作しますが、PyPyではいまのところサポートしていません。
+  (必要ならばサポート可能でしたが、PyPyではCPython 2.6/2.7よりも *たくさんの* 場合に動作します。)
+
+..
+  * the ``__builtins__`` name is always referencing the ``__builtin__`` module,
+    never a dictionary as it sometimes is in CPython. Assigning to
+    ``__builtins__`` has no effect.
+
+* ``__builtins__`` はいつも ``__builtin__`` モジュールを参照しますので、
+  その辞書はCPythonにはありません。
+  ``__builtins__`` への割り当ては影響がありません。
 
 * directly calling the internal magic methods of a few built-in types
   with invalid arguments may have a slightly different result.  For

File pypy/doc/ctypes-implementation.rst

 PyPy's ctypes implementation 
 =============================
 
-Summary
+.. Summary
+.. ========
+
+
+サマリー
 ========
 
-Terminology:
 
-* application level code - code written in full Python
+.. Terminology:
 
-* interpreter level code - code written in RPython, compiled
-  to something else, say C, part of the interpreter.
+.. * application level code - code written in full Python
 
-PyPy's ctypes implementation in its current state proves the
-feasibility of implementing a module with the same interface and
-behavior for PyPy as ctypes for CPython.
+.. * interpreter level code - code written in RPython, compiled
+..   to something else, say C, part of the interpreter.
 
-PyPy's implementation internally uses `libffi`_ like CPython's ctypes.
-In our implementation as much as possible of the code is written in
-full Python, not RPython. In CPython's situation, the equivalent would
-be to write as little as possible code in C.  We essentially favored
-rapid experimentation over worrying about speed for this first trial
-implementation. This allowed to provide a working implementation with
-a large part of ctypes features in 2 months real time.
+専門用語の定義:
 
-We reused the ``ctypes`` package version 1.0.2 as-is from CPython. We
-implemented ``_ctypes`` which is a C module in CPython mostly in pure
-Python based on a lower-level layer extension module ``_rawffi``.
+
+* アプリケーションレベルコード - すべて Python で書かれたコード
+* インタプリタレベルコード - RPython で書かれ、インタプリタを C 等に変換したもの
+
+.. PyPy's ctypes implementation in its current state proves the
+.. feasibility of implementing a module with the same interface and
+.. behavior for PyPy as ctypes for CPython.
+
+現状、PyPy における ctypes によるモジュールの実装は CPython における ctypes と同様のインターフェスとふるまいを保証しています。
+
+.. PyPy's implementation internally uses `libffi`_ like CPython's ctypes.
+.. In our implementation as much as possible of the code is written in
+.. full Python, not RPython. In CPython's situation, the equivalent would
+.. be to write as little as possible code in C.  We essentially favored
+.. rapid experimentation over worrying about speed for this first trial
+.. implementation. This allowed to provide a working implementation with
+.. a large part of ctypes features in 2 months real time.
+
+PyPy の実装では、 CPython における ctypes の `libffi`_ のようなものを内部的に利用します。
+実装は RPython ではなく、すべて Python で書かれています。
+CPython では、同様のものが C で書かれています。
+私たちは基本的に実装の早さよりも、動作の速さを重視しています。
+実際 ctypes のほとんどの機能の実装に 2 ヶ月間をかけています。
+
+.. We reused the ``ctypes`` package version 1.0.2 as-is from CPython. We
+.. implemented ``_ctypes`` which is a C module in CPython mostly in pure
+.. Python based on a lower-level layer extension module ``_rawffi``.
+
+CPython 同様に ``ctypes`` のバージョン 1.0.2 を再利用しています。
+CPython の C モジュールではなく、
+ピュア Python ベースの低レベルのレイヤの拡張モジュール ``_rawffi`` で ``_ctypes`` を実装しています。
 
 .. _`libffi`: http://sources.redhat.com/libffi/
 
-Low-level part: ``_rawffi``
-============================
+.. Low-level part: ``_rawffi``
+.. ============================
 
-This PyPy extension module (``pypy/module/_rawffi``) exposes a simple interface
-to create C objects (arrays and structures) and calling functions
-in dynamic libraries through libffi. Freeing objects in most cases and making
-sure that objects referring to each other are kept alive is responsibility of the higher levels.
+低レベル部品: ``_rawffi``
+=========================
 
-This module uses bindings to libffi which are defined in ``pypy/rlib/libffi.py``.
+.. This PyPy extension module (``pypy/module/_rawffi``) exposes a simple interface
+.. to create C objects (arrays and structures) and calling functions
+.. in dynamic libraries through libffi. Freeing objects in most cases and making
+.. sure that objects referring to each other are kept alive is responsibility of the higher levels.
 
-We tried to keep this module as small as possible. It is conceivable
-that other implementations (e.g. Jython) could use our ctypes
-implementation by writing their version of ``_rawffi``.
+この PyPy 拡張モジュール (``pypy/module/_rawffi``) は C オブジェクト (配列や構造体) の作成や、
+libffi 経由で動的ライブラリの関数を呼び出すためのシンプルなインターフェースを提供します。
+大抵のオブジェクトの開放の場合、
+互いを参照しているオブジェクトの生存確認はより高レベルで解決します。
 
-High-level parts
-=================
+.. This module uses bindings to libffi which are defined in ``pypy/rlib/libffi.py``.
 
-The reused ``ctypes`` package lives in ``lib_pypy/ctypes``. ``_ctypes``
-implementing the same interface as ``_ctypes`` in CPython is in
-``lib_pypy/_ctypes``.
+このモジュールは ``pypy/rlib/libffi.py`` に定義されている libffi バインディングを利用します。
 
-Discussion and limitations
-=============================
+.. We tried to keep this module as small as possible. It is conceivable
+.. that other implementations (e.g. Jython) could use our ctypes
+.. implementation by writing their version of ``_rawffi``.
 
-Reimplementing ctypes features was in general possible. PyPy supports
-pluggable garbage collectors, some of them are moving collectors, this
-means that the strategy of passing direct references inside Python
-objects to an external library is not feasible (unless the GCs
-support pinning, which is not the case right now).  The consequence of
-this is that sometimes copying instead of sharing is required, this
-may result in some semantics differences. C objects created with
-_rawffi itself are allocated outside of the GC heap, such that they can be
-passed to external functions without worries.
+このモジュールはできるだけコンパクトなままにしておくつもりです。
+他の実装の場合 (例えば Jython) でも、それぞれのバージョンの ``_rawffi`` を書くことにより、
+ctypes 実装を利用できると考えています。
 
-Porting the implementation to interpreter-level should likely improve
-its speed.  Furthermore the current layering and the current _rawffi
-interface require more object allocations and copying than strictly
-necessary; this too could be improved.
+.. High-level parts
+.. =================
 
-Here is a list of the limitations and missing features of the
-current implementation:
+高レベル部品
+============
 
-* No support for ``PyXxx`` functions from ``libpython``, for obvious reasons.
+.. The reused ``ctypes`` package lives in ``lib_pypy/ctypes``. ``_ctypes``
+.. implementing the same interface as ``_ctypes`` in CPython is in
+.. ``lib_pypy/_ctypes``.
 
-* We copy Python strings instead of having pointers to raw buffers
+再利用している ``ctypes`` は ``lib_pypy/ctypes`` にあります。
+CPython の ``_ctypes`` 同じインターフェースの実装の ``_ctypes`` は ``lib_pypy/_ctypes`` にあります。
 
-* Features we did not get to implement:
+.. Discussion and limitations
+.. =============================
 
-  - custom alignment and bit-fields
+考察と制限
+==========
 
-  - resizing (``resize()`` function)
+.. Reimplementing ctypes features was in general possible. PyPy supports
+.. pluggable garbage collectors, some of them are moving collectors, this
+.. means that the strategy of passing direct references inside Python
+.. objects to an external library is not feasible (unless the GCs
+.. support pinning, which is not the case right now).  The consequence of
+.. this is that sometimes copying instead of sharing is required, this
+.. may result in some semantics differences. C objects created with
+.. _rawffi itself are allocated outside of the GC heap, such that they can be
+.. passed to external functions without worries.
 
-  - non-native byte-order objects
+ctypes の機能のほとんどは再実装可能でした。
+PyPy は拡張可能なガーベージコレクタをサポートしており、
+そのいくつかのコレクタは動いており、
+これは Python オブジェクトの内部で直接参照している外部のライブラリの状態の解析ができないことを意味しています
+(GC のサポートを限定していない場合は、このケースは当てはまりません)。
+その結果、いくつかのケースではいくつかの動作の違いがあるため、共有せずに複製する必要がでてきます。
+_rawffi によて作成された C オブジェクトは GC のヒープ外に割り当てられ、
+とくになにも気にすることなく外部関数に引き継ぐことができます。
 
-  - callbacks accepting by-value structures
+.. Porting the implementation to interpreter-level should likely improve
+.. its speed.  Furthermore the current layering and the current _rawffi
+.. interface require more object allocations and copying than strictly
+.. necessary; this too could be improved.
 
-  - slight semantic differences that ctypes makes
-    between its primitive types and user subclasses
-    of its primitive types
+実装のインタプリタレベルのポーティングによりその速度は改善されます。
+また、現状のレイヤリングと現状の _rawffi インターフェースは、
+さらに厳格なオブジェクトの配置と複製を必要とします;
+これは改善することができました。
 
-Running application examples
-==============================
+.. Here is a list of the limitations and missing features of the
+.. current implementation:
 
-`pyglet`_ is known to run. We also had some success with pygame-ctypes (which is no longer maintained) and with a snapshot of the experimental pysqlite-ctypes. We will only describe how to run the pyglet examples.
+現状の実装における制限と実装されてない機能は以下のようなものがあります。
+
+.. * No support for ``PyXxx`` functions from ``libpython``, for obvious reasons.
+
+.. * We copy Python strings instead of having pointers to raw buffers
+
+.. * Features we did not get to implement:
+
+..   - custom alignment and bit-fields
+
+..   - resizing (``resize()`` function)
+
+..   - non-native byte-order objects
+
+..   - callbacks accepting by-value structures
+
+..   - slight semantic differences that ctypes makes
+..     between its primitive types and user subclasses
+..     of its primitive types
+
+* ``libpython`` の ``PyXxx`` 関数は明確な理由からサポートされていません。
+
+* 生バッファへのポインタの保持ではなく Python の文字列を複製しています
+
+* 実装していない機能
+
+  - カスタムアラインメントとビットフィールド
+
+  - リサイズ (``resize()`` 関数)
+
+  - 非ネィティブバイトオーダオブジェクト
+
+  - By-value オブジェクトへのコールバックの許可
+
+  - ctypes のプリミティブ型とユーザサブクラスのプリミティブ型にはいくつかの動作の違いがあります
+
+.. Running application examples
+.. ==============================
+
+アプリケーションの実装例
+========================
+
+.. `pyglet`_ is known to run. We also had some success with pygame-ctypes (which is no longer maintained) and with a snapshot of the experimental pysqlite-ctypes. We will only describe how to run the pyglet examples.
+
+`pyglet`_ の実装が知られています。
+pygame-ctypes (しばらくメンテナンスされていません) や pysqlite-ctypes のスナップショット等の成功例があります。
+pyglet の実装方法を例示します。
 
 pyglet
--------
+------
 
-We tried pyglet checking it out from its repository at revision 1984.
+.. We tried pyglet checking it out from its repository at revision 1984.
 
-From pyglet, the following examples are known to work:
-  
+pyglet のリポジトリからリビジョン 1984 をチェックアウトします。
+
+.. From pyglet, the following examples are known to work:
+
+pyglet では以下の動作例が知られています:
+
   - opengl.py
   - multiple_windows.py
   - events.py
   - window_platform_event.py
   - fixed_resolution.py
 
-The pypy-c translated to run the ctypes tests can be used to run the pyglet examples as well. They can be run like e.g.::
+.. The pypy-c translated to run the ctypes tests can be used to run the pyglet examples as well. They can be run like e.g.::
+
+ctypes のテストを実行する pypy-c は、同様に pyglet の例の実行に用いることができます。
 
     $ cd pyglet/
     $ PYTHONPATH=. ../ctypes-stable/pypy/translator/goal/pypy-c examples/opengl.py
 
+.. they usually should be terminated with ctrl-c. Refer to the their doc strings for details about how they should behave.
 
-they usually should be terminated with ctrl-c. Refer to the their doc strings for details about how they should behave.
+通常 ctrl-c で終了することができます。
 
-The following examples don't work for reasons independent from ctypes:
+.. The following examples don't work for reasons independent from ctypes:
+
+..   - image_convert.py needs PIL
+..   - image_display.py needs PIL
+..   - astraea/astraea.py needs PIL
+
+以下の例は ctypes から独立しているため動作しません。
 
   - image_convert.py needs PIL
   - image_display.py needs PIL
   - astraea/astraea.py needs PIL
 
-We did not try the following examples:
+.. We did not try the following examples:
 
-  - media_player.py needs avbin or at least a proper sound card setup for
-    .wav files
-  - video.py needs avbin
-  - soundscape needs avbin
+..   - media_player.py needs avbin or at least a proper sound card setup for
+..     .wav files
+..   - video.py needs avbin
+..   - soundscape needs avbin
+
+以下の例は試していません:
+
+  - media_player.py は avbin または、少なくとも .wav ファイルを再生するために適切なサウンドカードのセットアップが必要です
+  - video.py は avbin が必要です
+  - soundscape は avbin が必要です
 
 .. _`pyglet`: http://pyglet.org/
 
 
-ctypes configure
-=================
+.. ctypes configure
+.. ================
 
-We also released ``ctypes-configure``, which is an experimental package
-trying to approach the portability issues of ctypes-based code.
+ctypes のコンフィグレーション
+=============================
 
-idea
-----
+.. We also released ``ctypes-configure``, which is an experimental package
+.. trying to approach the portability issues of ctypes-based code.
 
-One of ctypes problems is that ctypes programs are usually not very
-platform-independent. We created ctypes_configure, which invokes c
-compiler (via distutils) for various platform-dependent details like
-exact sizes of types (for example size_t), ``#defines``, exact outline of
-structures etc. It replaces in this regard code generator (h2py).
+ctypes ベースのコードの移植性の課題を解決するための実験的なパッケージとして ``ctypes-configure`` もリリースしています。
 
-installation
+.. idea
+.. ----
+
+アイデア
+--------
+
+.. One of ctypes problems is that ctypes programs are usually not very
+.. platform-independent. We created ctypes_configure, which invokes c
+.. compiler (via distutils) for various platform-dependent details like
+.. exact sizes of types (for example size_t), ``#defines``, exact outline of
+.. structures etc. It replaces in this regard code generator (h2py).
+
+ctypes の問題点のひとつは、通常 ctypes プログラムにプラットフォーム依存があることです。
+各プラットフォームに依存する型のサイズ (例えば size_t)、
+``#defines`` や構造体のアウトライン等の細部のために C コンパイラを呼び出す (distutils 経由) 
+ctypes_configure を作成し、
+
+.. installation
+.. ------------
+
+インストール
 ------------
 
 ``easy_install ctypes_configure``
 
-usage
------
+.. usage
+.. -----
 
-`ctypes_configure/doc/sample.py`_ explains in details how to use it.
+利用方法
+--------
+
+.. `ctypes_configure/doc/sample.py`_ explains in details how to use it.
+
+`ctypes_configure/doc/sample.py`_ で詳細な利用方法について解説しています。
 
 
 .. include:: _ref.txt

File pypy/doc/getting-started-python.rst

+''  ==============================================
+''  Getting Started with PyPy's Python Interpreter
+''  ==============================================
+
 ==============================================
-Getting Started with PyPy's Python Interpreter
+PyPyPythonインタプリタ
 ==============================================
 
 .. contents::
 
 
-PyPy's Python interpreter is a very compliant Python
-interpreter implemented in Python.  When translated to C, it passes most of 
-`CPythons core language regression tests`_ and comes with many of the extension
-modules included in the standard library including ``ctypes``. It can run large
-libraries such as Django_ and Twisted_. There are some small behavioral
-differences with CPython and some missing extensions, for details see `CPython
-differences`_.
+''  PyPy's Python interpreter is a very compliant Python
+''  interpreter implemented in Python.  When translated to C, it passes most of 
+''  `CPythons core language regression tests`_ and comes with many of the extension
+''  modules included in the standard library including ``ctypes``. It can run large
+''  libraries such as Django_ and Twisted_. There are some small behavioral
+''  differences with CPython and some missing extensions, for details see `CPython
+''  differences`_.
+
+PyPyのPythonインタプリタは、通常のPythonと高い互換性を持った,Python自身で書かれたPythonの処理系です。
+これをC言語に変換した場合、殆どのCPython用のリグレッションテストをパスできます。
+また、多くの追加モジュールも動作しますし、標準ライブラリで提供されている``ctypes``も動作します。
+更に、 `Django`_ や `Twisted`_ 等の大規模なライブラリにも対応しています。
+ただし、CPythonと比べて少なからず挙動が異なる部分や、一部対応していない追加モジュールも存在しています。
+詳しくは、`CPython differences`_ をご覧下さい。
 
 .. _Django: http://djangoproject.com
 .. _Twisted: http://twistedmatrix.com
 
 .. _`CPython differences`: cpython_differences.html
 
-To actually use PyPy's Python interpreter, the first thing to do is to 
-`download a pre-built PyPy`_ for your architecture.  
+
+''  To actually use PyPy's Python interpreter, the first thing to do is to 
+''  `download a pre-built PyPy`_ for your architecture.  
+
+実際にPyPyのPythonインタプリタを使い始めるために、
+まず `download a pre-build PyPy`_ をご覧下さい。
 
 .. _`download a pre-built PyPy`:  http://pypy.org/download.html
 
-Translating the PyPy Python interpreter
+''  Translating the PyPy Python interpreter
+''  ---------------------------------------
+
+PyPy Pythonインタプリタの変換
 ---------------------------------------
 
-(**Note**: for some hints on how to translate the Python interpreter under
-Windows, see the `windows document`_)
+''  (**Note**: for some hints on how to translate the Python interpreter under
+''  Windows, see the `windows document`_)
+
+(**注釈**: PythonインタプリタをWindows環境下で変換する為のヒントは
+`windows document`_ にあります)
 
 .. _`windows document`: windows.html
 
-You can translate the whole of PyPy's Python interpreter to low level C code,
-or `CLI code`_.  If you intend to build using gcc, check to make sure that
-the version you have is not 4.2 or you will run into `this bug`_.
+''  You can translate the whole of PyPy's Python interpreter to low level C code,
+''  or `CLI code`_. If you intend to build using gcc, check to make sure that
+..  the version you have is not 4.2 or you will run into `this bug`_.
 
 .. _`this bug`: https://bugs.launchpad.net/ubuntu/+source/gcc-4.2/+bug/187391
 
-1. First `download a pre-built PyPy`_ for your architecture which you will
-   use to translate your Python interpreter.  It is, of course, possible to
-   translate with a CPython 2.6 or later, but this is not the preferred way,
-   because it will take a lot longer to run -- depending on your architecture,
-   between two and three times as long.
+PyPyのPythonインタプリタは、C言語にも、`CLI code`_にも変換が可能です。
+gccを使用して構築する予定の場合は、お持ちのバージョンが4.2でないことを確認してください。さもなければ、`this bug`_  が実行されます。
 
-2. Install build-time dependencies.  On a Debian box these are::
+''  1. First `download a pre-built PyPy`_ for your architecture which you will
+''     use to translate your Python interpreter.  It is, of course, possible to
+''     translate with a CPython 2.6 or later, but this is not the preferred way,
+''     because it will take a lot longer to run -- depending on your architecture,
+''     between two and three times as long.
 
-     [user@debian-box ~]$ sudo apt-get install \
-     gcc make python-dev libffi-dev pkg-config \
-     libz-dev libbz2-dev libncurses-dev libexpat1-dev \
-     libssl-dev libgc-dev python-sphinx python-greenlet
+1. 始めに、 `download a pre-built PyPy`_ から、Pythonインタプリタを変換する為に
+お使いのコンピュータに合ったコンパイル済みのPyPyをダウンロードしてください。
+この変換作業はCPython 2.6以降を使用しても行えますが、
+お使いの環境により2-3倍程度の時間がかかる事があるため、推奨されません。 
 
    On a Fedora-16 box these are::
 
      zlib-devel bzip2-devel ncurses-devel expat-devel \
      openssl-devel gc-devel python-sphinx python-greenlet
 
-   The above command lines are split with continuation characters, giving the necessary dependencies first, then the optional ones.
+2. ビルド時に必要となる依存ファイル群をインストールしてください。Debianの場合は次のようにします。
+    [user@debian-box ~]$ sudo apt-get install \
+    gcc make python-dev libffi-dev pkg-config \
+    libz-dev libbz2-dev libncurses-dev libexpat1-dev \
+    libssl-dev libgc-dev python-sphinx python-greenlet
 
-   * ``pkg-config`` (to help us locate libffi files)
-   * ``libz-dev`` (for the optional ``zlib`` module)
-   * ``libbz2-dev`` (for the optional ``bz2`` module)
-   * ``libncurses-dev`` (for the optional ``_minimal_curses`` module)
-   * ``libexpat1-dev`` (for the optional ``pyexpat`` module)
-   * ``libssl-dev`` (for the optional ``_ssl`` module)
-   * ``libgc-dev`` (for the Boehm garbage collector: only needed when translating with `--opt=0, 1` or `size`)
-   * ``python-sphinx`` (for the optional documentation build.  You need version 1.0.7 or later)
+''     On a Fedora box these are::
+''  
+''       [user@fedora-or-rh-box ~]$ sudo yum install \
+''       gcc make python-devel libffi-devel pkg-config \
+''       zlib-devel bzip2-devel ncurses-devel expat-devel \
+''       openssl-devel gc-devel python-sphinx python-greenlet
 
+   Fedoraの場合は次のようにします。
+      [user@fedora-or-rh-box ~]$ sudo yum install \
+      gcc make python-devel libffi-devel pkg-config \
+      zlib-devel bzip2-devel ncurses-devel expat-devel \
+      openssl-devel gc-devel python-sphinx python-greenlet
+
+''     The above command lines are split with continuation characters, giving the necessary dependencies first, then the optional ones.
+''  
+''     * ``pkg-config`` (to help us locate libffi files)
+''     * ``libz-dev`` (for the optional ``zlib`` module)
+''     * ``libbz2-dev`` (for the optional ``bz2`` module)
+''     * ``libncurses-dev`` (for the optional ``_minimal_curses`` module)
+''     * ``libexpat1-dev`` (for the optional ``pyexpat`` module)
+''     * ``libssl-dev`` (for the optional ``_ssl`` module)
+''     * ``libgc-dev`` (for the Boehm garbage collector: only needed when translating with `--opt=0, 1` or `size`)
+''     * ``python-sphinx`` (for the optional documentation build.  You need version 1.0.7 or later)
+''     * ``python-greenlet`` (for the optional stackless support in interpreted mode/testing)
+
+  上記のコマンドでは、改行の直前に\記号を挿入しています。(改行をせず一行で書く場合には\記号は必要ありません)。
+  下記のファイル群は必須ではありませんが、インストールしておくことを推奨します。
+
+      * ``pkg-config`` (libffiのファイル郡を管理するツール)
+      * ``libz-dev`` (オプションの``zlib``用モジュール) 
+      * ``libbz2-dev`` (オプションの``bz2``用モジュール) 
+      * ``libncurses-dev`` (オプションの``_minimal_curses``用モジュール) 
+      * ``libexpat1-dev`` (オプションの``pyexpat``用モジュール)
+      * ``libssl-dev`` (オプションの``_ssl``用モジュール)
+      * ``libgc-dev`` (`--opt=0,1`もしくは`size`オプションを指定して変換を行う際に必要となるBoehm GC用モジュール)
+      * ``python-sphinx`` (ドキュメント作成用モジュール。動作には1.0.7以上のバージョンが必要です)
+      * ``python-greenlet`` (Stacklessを利用する場合に必要。interpreted mode/testingのみサポートしています)
 
 3. Translation is time-consuming -- 45 minutes on a very fast machine --
    and RAM-hungry.  As of March 2011, you will need **at least** 2 GB of 

File pypy/doc/getting-started.rst

+..
+    ==================================
+    Getting Started 
+    ==================================
+
 ==================================
-Getting Started 
+はじめに
 ==================================
 
 .. contents::
 
 .. _howtopypy: 
 
-What is PyPy ?
+..
+    What is PyPy ?
+    ==============
+
+PyPyとは?
 ==============
 
-In common parlance, PyPy has been used to mean two things.  The first is the
-`RPython translation toolchain`_, which is a framework for generating
-dynamic programming language implementations.  And the second is one
-particular implementation that is so generated --
-an implementation of the Python_ programming language written in
-Python itself.  It is designed to be flexible and easy to experiment with.
+..
+    In common parlance, PyPy has been used to mean two things.  The first is the
+    `RPython translation toolchain`_, which is a framework for generating
+    dynamic programming language implementations.  And the second is one
+    particular implementation that is so generated --
+    an implementation of the Python_ programming language written in
+    Python itself.  It is designed to be flexible and easy to experiment with.
 
-This double usage has proven to be confusing, and we are trying to move
-away from using the word PyPy to mean both things.  From now on we will
-try to use PyPy to only mean the Python implementation, and say the
-`RPython translation toolchain`_ when we mean the framework.  Some older
-documents, presentations, papers and videos will still have the old
-usage.  You are hereby warned.
+通俗的にPyPyは2つの意味を持っています。
+1つめは、動的言語実装を生み出すフレームワークである `RPython translation toolchain`_ です。
+そして2つめは、これによって生成された特定の実装( Python_ 自身で書かれたプログラミング言語Python)です。
+それは柔軟で簡単に実験しやすいように設計されています。
 
-We target a large variety of platforms, small and large, by providing a
-compiler toolsuite that can produce custom Python versions.  Platform, memory
-and threading models, as well as the JIT compiler itself, are aspects of the
-translation process - as opposed to encoding low level details into the
-language implementation itself. `more...`_
+..
+    This double usage has proven to be confusing, and we are trying to move
+    away from using the word PyPy to mean both things.  From now on we will
+    try to use PyPy to only mean the Python implementation, and say the
+    `RPython translation toolchain`_ when we mean the framework.  Some older
+    documents, presentations, papers and videos will still have the old
+    usage.  You are hereby warned.
+
+この2つの用法は、混乱をもたらすのは知られています。
+私たちはPyPyという名称をこの2つの意味で使うことからやめる試みをしています。
+これからは、私たちはPyPyという名称をPythonの実装だけに限定して使い、
+フレームワークを `RPython translation toolchain`_ と呼びます。
+いくつかの古い文書、プレゼンテーション、論文、動画はまだ古い用法のままです。
+注意してください。
+
+..
+  We target a large variety of platforms, small and large, by providing a
+  compiler toolsuite that can produce custom Python versions.  Platform, memory
+  and threading models, as well as the JIT compiler itself, are aspects of the
+  translation process - as opposed to encoding low level details into the
+  language implementation itself. `more...`_
+
+私たちはカスタムなPythonバージョンを生成するコンパイラのツール一式を提供することにより、
+小規模および大規模、様々なプラットフォームをターゲットにしています。
+プラットフォーム、メモリとスレッドモデルのみならず、JITコンパイラ自体も翻訳工程の側面です。
+- ということで、言語実装に対する低レベルな詳細情報の変換を認めていません。 `more...`_
 
 .. _Python: http://docs.python.org/reference/
 .. _`RPython translation toolchain`: translation.html
 .. _`more...`: architecture.html
 
-Just the facts 
-============== 
+..
+  Just the facts 
+  ============== 
 
-Download a pre-built PyPy
--------------------------
+もっともな事実
+===============
 
-The quickest way to start using PyPy is to download a prebuilt binary for your
-OS and architecture.  You can either use the `most recent release`_ or one of
-our `development nightly build`_.  Please note that the nightly builds are not
-guaranteed to be as stable as official releases, use them at your own risk.
+..
+  Download a pre-built PyPy
+  -------------------------
+
+プレビルドPyPyのダウンロード
+-----------------------------
+
+..
+  The quickest way to start using PyPy is to download a prebuilt binary for your
+  OS and architecture.  You can either use the `most recent release`_ or one of
+  our `development nightly build`_.  Please note that the nightly builds are not
+  guaranteed to be as stable as official releases, use them at your own risk.
+
+PyPyを使い始める最速な方法は、プレビルドバイナリをあなたのOSとアーキテクチャにダウンロードすることです。
+あなたは `most recent release`_ または、ある特定の `development nightly build`_ のいずれかを使うことができます。
+ナイトリービルドは安定したオフィシャルなリリースとしての保証をしていませんので、あなたの責任でそれらを使用して下さい。
 
 .. _`most recent release`: http://pypy.org/download.html
 .. _`development nightly build`: http://buildbot.pypy.org/nightly/trunk/
 
-Installing PyPy
----------------
+..
+  Installing PyPy
+  ---------------
 
-PyPy is ready to be executed as soon as you unpack the tarball or the zip
-file, with no need to install it in any specific location::
+PyPyインストール
+----------------
 
     $ tar xf pypy-1.9-linux.tar.bz2
     $ ./pypy-1.9/bin/pypy
     Python 2.7.2 (341e1e3821ff, Jun 07 2012, 15:40:31)
     [PyPy 1.9.0 with GCC 4.4.3] on linux2
+
     Type "help", "copyright", "credits" or "license" for more information.
     And now for something completely different: ``it seems to me that once you
     settle on an execution / object model and / or bytecode format, you've already
     first class for''
     >>>>
 
-If you want to make PyPy available system-wide, you can put a symlink to the
-``pypy`` executable in ``/usr/local/bin``.  It is important to put a symlink
-and not move the binary there, else PyPy would not be able to find its
-library.
+..
+  If you want to make PyPy available system-wide, you can put a symlink to the
+  ``pypy`` executable in ``/usr/local/bin``.  It is important to put a symlink
+  and not move the binary there, else PyPy would not be able to find its
+  library.
 
-If you want to install 3rd party libraries, the most convenient way is to
-install distribute_ and pip_:
+もしあなたがシステム全体でPyPyを使いたいのであれば、
+あなたは ``pypy`` のシンボリックリンクを ``/usr/local/bin`` に置くことができる。
+重要なこととして、シンボリックリンクを置くとバイナリを移動しないという他に、
+PyPyはPyPyのライブラリを見つけることができません。
+
+..
+  If you want to install 3rd party libraries, the most convenient way is to
+  install distribute_ and pip_:
+
+あなたがサードパーティのライブラリをインストールしたいのであれば、最も便利な方法は、
+distribute_ と pip_ をインストールすることです:
 
     $ curl -O http://python-distribute.org/distribute_setup.py
 
 
     $ ./pypy-1.9/bin/pip install pygments  # for example
 
-3rd party libraries will be installed in ``pypy-1.9/site-packages``, and
-the scripts in ``pypy-1.9/bin``.
 
-Installing using virtualenv
----------------------------
+..
+  3rd party libraries will be installed in ``pypy-1.9/site-packages``, and
+  the scripts in ``pypy-1.9/bin``.
 
-It is often convenient to run pypy inside a virtualenv.  To do this
-you need a recent version of virtualenv -- 1.6.1 or greater.  You can
-then install PyPy both from a precompiled tarball or from a mercurial
-checkout::
+サードパーティのライブラリは ``pypy-1.9/site-packages`` にインストールされ
+スクリプトは ``pypy-1.9/bin`` にあります。
+
+..
+  Installing using virtualenv
+  ---------------------------
+
+virtualenvを使ったインストール
+------------------------------
+
+..
+  It is often convenient to run pypy inside a virtualenv.  To do this
+  you need a recent version of virtualenv -- 1.6.1 or greater.  You can
+  then install PyPy both from a precompiled tarball or from a mercurial
+  checkout::
+
+多くの場合、virtualenvでPyPyを実行すると便利です。
+これを行うには、virtualenvの最新のバージョンが必要です。 - 1.6.1か、それ以上の。
+あなたはプレコンパイルされたtarball、またはMercurialのチェックアウトからPyPyをインストールできます::
 
 	# from a tarball
 	$ virtualenv -p /opt/pypy-c-jit-41718-3fb486695f20-linux/bin/pypy my-pypy-env
 	# from the mercurial checkout
 	$ virtualenv -p /path/to/pypy/pypy/translator/goal/pypy-c my-pypy-env
 
-Note that bin/python is now a symlink to bin/pypy.
+..
+  Note that bin/python is now a symlink to bin/pypy.
+
+bin/pythonは/bin/pypyへの新たなシンボリックリンクであることに注意してください。
 
 .. _`distribute`: http://www.python-distribute.org/
 .. _`pip`: http://pypi.python.org/pypi/pip
 
 
-Clone the repository
---------------------
+..
+  Clone the repository
+  --------------------
 
-If you prefer to `compile PyPy by yourself`_, or if you want to modify it, you
-will need to obtain a copy of the sources.  This can be done either by
-`downloading them from the download page`_ or by checking them out from the
-repository using mercurial.  We suggest using mercurial if one wants to access
-the current development.
+リポジトリのクーロン
+---------------------
+
+..
+  If you prefer to `compile PyPy by yourself`_, or if you want to modify it, you
+  will need to obtain a copy of the sources.  This can be done either by
+  `downloading them from the download page`_ or by checking them out from the
+  repository using mercurial.  We suggest using mercurial if one wants to access
+  the current development.
+
+あなたが `compile PyPy by yourself`_ 場合、または自ら修正したい場合は、
+ソースをコピーして手に入れる必要があります。
+これは、 `downloading them from the download page`_ または、Mercurialを使ってリポジトリから
+ソースコードをチェックアウトすることによって行うことができます。
+
+現在の開発コードを利用したい場合は、Mercurialを使うことをお勧めします。
 
 .. _`downloading them from the download page`: http://pypy.org/download.html
 
-You must issue the following command on your
-command line, DOS box, or terminal::
+..
+  You must issue the following command on your
+  command line, DOS box, or terminal::
+
+コマンドライン、DOSボックス、ターミナルで次のコマンドを実行する必要があります::
 
     hg clone http://bitbucket.org/pypy/pypy pypy
 
-This will clone the repository and place it into a directory
-named ``pypy``, and will get you the PyPy source in
-``pypy/pypy`` and documentation files in ``pypy/pypy/doc``.
-We try to ensure that the tip is always stable, but it might
-occasionally be broken.  You may want to check out `our nightly tests:`_
-find a revision (12-chars alphanumeric string, e.g. "963e808156b3") 
-that passed at least the
-``{linux32}`` tests (corresponding to a ``+`` sign on the
-line ``success``) and then, in your cloned repository, switch to this revision
-using::
+..
+  This will clone the repository and place it into a directory
+  named ``pypy``, and will get you the PyPy source in
+  ``pypy/pypy`` and documentation files in ``pypy/pypy/doc``.
+  We try to ensure that the tip is always stable, but it might
+  occasionally be broken.  You may want to check out `our nightly tests:`_
+  find a revision (12-chars alphanumeric string, e.g. "963e808156b3") 
+  that passed at least the
+  ``{linux32}`` tests (corresponding to a ``+`` sign on the
+  line ``success``) and then, in your cloned repository, switch to this revision
+  using::
+
+これは、リポジトリをクローンし、 ``pypy`` という名前でディレクトリを配置します。
+またそれと、PyPyソースを ``pypy/pypy`` 、ドキュメントファイルを ``pypy/pypy/doc`` に取得します。
+私たちは、最新のコードが常に安定していることを保証しようとしていますが、
+時々壊れている可能性があります。
+`our nightly tests:`_ はリビジョンを入手しチェックアウトすることができます
+あなたは最新の ``{linux32}`` テストを通った( ``+`` 符号は ``success`` に相当する)
+`our nightly tests:`_ のリビジョン(英数字の12文字、例: "963e808156b3")を見つけ、
+チェックアウトし入手することができます。
+あとで、複製されたリポジトリで使用してこのリビジョンに切り替えます::
 
     hg up -r XXXXX
 
-where XXXXX is the revision id.
-
+XXXXX はリビジョンIDです。
 
 .. _`compile PyPy by yourself`: getting-started-python.html
 .. _`our nightly tests:`: http://buildbot.pypy.org/summary?branch=<trunk>
 
-Where to go from here
+..
+  Where to go from here
+  ======================
+
+ここから先の話
 ======================
 
-After you successfully manage to get PyPy's source you can read more about:
+..
+  After you successfully manage to get PyPy's source you can read more about:
+
+首尾よくPyPyのソースを取得した後に、詳細を読むことができます。
 
  - `Building and using PyPy's Python interpreter`_
  - `Learning more about the RPython toolchain and how to develop (with) PyPy`_
 
 .. _setuptools: http://pypi.python.org/pypi/setuptools
 
-Understanding PyPy's architecture
+..
+  Understanding PyPy's architecture
+  ---------------------------------
+
+PyPyのアーキテクチャを理解する
 ---------------------------------
 
-For in-depth information about architecture and coding documentation 
-head over to the `documentation section`_ where you'll find lots of 
-interesting information.  Additionally, in true hacker spirit, you 
-may just `start reading sources`_ . 
+..
+  For in-depth information about architecture and coding documentation 
+  head over to the `documentation section`_ where you'll find lots of 
+  interesting information.  Additionally, in true hacker spirit, you 
+  may just `start reading sources`_ . 
+
+上記のアーキテクチャおよび、コーディングマニュアルに関する詳細な情報については、
+`documentation section`_ へ進み興味深い情報を見つけることができます。
+さらに、真のハッカーの精神により、あなたは `start reading sources`_ ことができます。
 
 .. _`documentation section`: index.html#project-documentation
 .. _`start reading sources`: getting-started-dev.html#start-reading-sources
 
-Filing bugs or feature requests 
+..
+  Filing bugs or feature requests 
+  -------------------------------
+
+バグのファイルイングや機能要求
 -------------------------------
 
-You may file `bug reports`_ on our issue tracker which is
-also accessible through the 'issues' top menu of 
-the PyPy website.  `Using the development tracker`_ has 
-more detailed information on specific features of the tracker. 
+..
+  You may file `bug reports`_ on our issue tracker which is
+  also accessible through the 'issues' top menu of 
+  the PyPy website.  `Using the development tracker`_ has 
+  more detailed information on specific features of the tracker. 
+
+PyPyウェブサイトのトップメニューの 'issues' から
+私たちの課題トラッカーにアクセスでき、 `bug reports`_ を提出することができます。
 
 .. _`Using the development tracker`: coding-guide.html#using-development-tracker
 .. _bug reports:            https://codespeak.net/issue/pypy-dev/

File pypy/doc/index.rst

+..
+    Welcome to PyPy Development
+    =============================================
 
-Welcome to PyPy Development
+PyPy開発へようこそ
 =============================================
 
-The PyPy project aims at producing a flexible and fast Python_
-implementation.  The guiding idea is to translate a Python-level
-description of the Python language itself to lower level languages.
-Rumors have it that the secret goal is being faster-than-C which is
-nonsense, isn't it?  `more...`_
+..
+    The PyPy project aims at producing a flexible and fast Python_
+    implementation.  The guiding idea is to translate a Python-level
+    description of the Python language itself to lower level languages.
+    Rumors have it that the secret goal is being faster-than-C which is
+    nonsense, isn't it?  `more...`_
 
-Getting into PyPy ... 
+PyPyプロジェクトは、柔軟で高速なPython実装を生み出すことをを目指しています。
+指針の考えは、PythonによるPython自身の記述を低レベルの言語へ翻訳することです。
+噂ではCより高速になるのを秘密の目標としているらしい。この噂はくだらん。だろう? `more...`_
+
+..
+    Getting into PyPy ... 
+    =============================================
+
+PyPyの世界へ...
 =============================================
 
-* `Getting started`_: how to install and run the PyPy Python interpreter
+..
+  * `Getting started`_: how to install and run the PyPy Python interpreter
 
-* `FAQ`_: some frequently asked questions.
+* `Getting started`_ : インストールとPyPy Pythonインタプリタの実行方法
 
+<<<<<<< local
 * `Release 1.9`_: the latest official release
+=======
+..
+  * `FAQ`_: some frequently asked questions.
+>>>>>>> other
 
-* `PyPy Blog`_: news and status info about PyPy 
+* `FAQ`_ : 頻繁に聞かれる質問。
 
-* `Papers`_: Academic papers, talks, and related projects
+..
+  * `Release 1.6`_: the latest official release
 
-* `speed.pypy.org`_: Daily benchmarks of how fast PyPy is
+* `Release 1.6`_: 最新の公式リリース
 
-* `potential project ideas`_: In case you want to get your feet wet...
+..
+  * `PyPy Blog`_: news and status info about PyPy 
 
-Documentation for the PyPy Python Interpreter
+* `PyPy Blog`_: PyPyについてのニュースと状況
+
+..
+  * `Papers`_: Academic papers, talks, and related projects
+
+* `Papers`_: 学術論文、話題、関連するプロジェクト
+
+.. 
+  * `speed.pypy.org`_: Daily benchmarks of how fast PyPy is
+
+* `speed.pypy.org`_: PyPyがどのくらいの速度なのか、毎日のベンチマークです。
+
+..
+  * `potential project ideas`_: In case you want to get your feet wet...
+
+* `potential project ideas`_: あなたがその世界に飛び込んでみたいなら...
+
+
+..
+    Documentation for the PyPy Python Interpreter
+    ===============================================
+
+PyPy Python インタプリタのドキュメント
 ===============================================
 
-New features of PyPy's Python Interpreter and 
-Translation Framework: 
+..
+    `getting started`_ provides hands-on instructions 
+    including a two-liner to run the PyPy Python interpreter 
+    on your system, examples on advanced features and 
+    entry points for using the `RPython toolchain`_.
+
+`getting started`_ はシステム上でPyPy Python インタプリタを実行するには2つのライナーを含む実践的な手順を説明します。例えば、 `RPython toolchain`_ を使った次世代の機能とエントリポイントがあります。
+
+..
+   `FAQ`_ contains some frequently asked questions.
+
+`FAQ`_ は頻繁に述べられるいくつかの質疑応答があります。
+
+..
+    New features of PyPy's Python Interpreter and 
+    Translation Framework: 
+
+      * `Differences between PyPy and CPython`_
+      * `What PyPy can do for your objects`_
+      * `Stackless and coroutines`_
+      * `JIT Generation in PyPy`_ 
+      * `Sandboxing Python code`_
+
+PyPyのPythonインタプリタの新機能と翻訳フレームワーク:
 
   * `Differences between PyPy and CPython`_
   * `What PyPy can do for your objects`_
   * `JIT Generation in PyPy`_ 
   * `Sandboxing Python code`_
 
-Status_ of the project.
+..
+    Status_ of the project.
 
+プロジェクトの 対応状況_
 
-Mailing lists, bug tracker, IRC channel
+..
+    Mailing lists, bug tracker, IRC channel
+    =============================================
+
+メーリングリスト、バグトラッカ、IRCチャンネル
 =============================================
 
-* `Development mailing list`_: development and conceptual
-  discussions. 
+..
+    * `Development mailing list`_: development and conceptual
+      discussions. 
 
-* `Mercurial commit mailing list`_: updates to code and
-  documentation. 
+* `Development mailing list`_: 開発とコンセプトの議論 
 
-* `Development bug/feature tracker`_: filing bugs and feature requests. 
+..
+    * `Mercurial commit mailing list`_: updates to code and
+      documentation. 
 
-* **IRC channel #pypy on freenode**: Many of the core developers are hanging out 
-  at #pypy on irc.freenode.net.  You are welcome to join and ask questions
-  (if they are not already developed in the FAQ_).
-  You can find logs of the channel here_.
+* `Mercurial commit mailing list`_: コードの更新とドキュメント 
 
-Meeting PyPy developers
-=======================
+..
+    * `Development bug/feature tracker`_: filing bugs and feature requests. 
 
-The PyPy developers are organizing sprints and presenting results at
-conferences all year round. They will be happy to meet in person with
-anyone interested in the project.  Watch out for sprint announcements
-on the `development mailing list`_.
+* `Development bug/feature tracker`_: バグの書き起こしと将来の要望
+
+..
+    * **IRC channel #pypy on freenode**: Many of the core developers are hanging out 
+      at #pypy on irc.freenode.net.  You are welcome to join and ask questions
+      (if they are not already developed in the FAQ_).
+      You can find logs of the channel here_.
+
+* **IRC channel #pypy on freenode**: コア開発者の多くは、irc.freenode.netの#pypyにぶら下がっています。
+  参加を歓迎し、質問を歓迎します。
+  (もし質問が FAQ_ に存在しなかった場合)
+  あなたはチャンネルのログをここで見つけることが出来ます。 here_.
+
+..
+    Meeting PyPy developers
+    =======================
+
+PyPy開発者のミーティング
+=========================
+
+..
+    The PyPy developers are organizing sprints and presenting results at
+    conferences all year round. They will be happy to meet in person with
+    anyone interested in the project.  Watch out for sprint announcements
+    on the `development mailing list`_.
+
+PyPy開発者はスプリントを整備し一年中、カンファレンスで結果を披露します。
+それらはプロジェクトに興味をもった人に素晴らしい出会いをもたらします。
+スプリントのアナウンスに目を配ってください `development mailing list`_ 。
 
 .. _Python: http://docs.python.org/index.html
 .. _`more...`: architecture.html#mission-statement 
 .. _`RPython toolchain`: translation.html
 .. _`potential project ideas`: project-ideas.html
 
-Project Documentation
+..
+    Project Documentation
+    =====================================
+
+プロジェクトドキュメント
 =====================================
 
-PyPy was funded by the EU for several years. See the `web site of the EU
-project`_ for more details.
+..
+    PyPy was funded by the EU for several years. See the `web site of the EU
+    project`_ for more details.
+    
+PyPyは数年間、EUから資金供給を受けました。詳細はこちらです。 `web site of the EU project`_
 
 .. _`web site of the EU project`: http://pypy.org
 
-architecture_ gives a complete view of PyPy's basic design. 
+..
+    architecture_ gives a complete view of PyPy's basic design. 
 
-`coding guide`_ helps you to write code for PyPy (especially also describes
-coding in RPython a bit). 
+architecture_ は完全なPyPyの基本設計の考えを提供します。
 
-`sprint reports`_ lists reports written at most of our sprints, from
-2003 to the present.
+..
+    `coding guide`_ helps you to write code for PyPy (especially also describes coding in RPython a bit). 
 
-`papers, talks and related projects`_ lists presentations 
-and related projects as well as our published papers.
+`coding guide`_ はPyPyのコードを書くのを手助けします。(とりわけRPythonの部分を記述する際に)
 
-`PyPy video documentation`_ is a page linking to the videos (e.g. of talks and
-introductions) that are available.
+..
+    `sprint reports`_ lists reports written at most of our sprints, from
+    2003 to the present.
 
-`Technical reports`_ is a page that contains links to the
-reports that we submitted to the European Union.
+`sprint reports`_ 2003年から現在まで、リポートのリストの多くはわれわれのスプリントで書きました。
 
-`development methodology`_ describes our sprint-driven approach.
+..
+    `papers, talks and related projects`_ lists presentations 
+    and related projects as well as our published papers.
 
-`LICENSE`_ contains licensing details (basically a straight MIT-license). 
+`papers, talks and related projects`_ プレゼンテーションのリストと関連したプロジェクトのみならず我々が発行した論文です。
 
-`Glossary`_ of PyPy words to help you align your inner self with
-the PyPy universe.
+..
+    `PyPy video documentation`_ is a page linking to the videos (e.g. of talks and
+    introductions) that are available.
 
+`PyPy video documentation`_ は動画(例えば発表や会議)を観ることができるリンクです。
 
-Status
+..
+    `Technical reports`_ is a page that contains links to the
+    reports that we submitted to the European Union.
+
+`Technical reports`_ 我々がEUに提出したレポートのリンクを含んだページです。
+
+..
+    `development methodology`_ describes our sprint-driven approach.
+
+`development methodology`_ 我々のスプリント指向によるアプローチを説明します。
+
+..
+    `LICENSE`_ contains licensing details (basically a straight MIT-license). 
+
+`LICENSE`_ は詳細なライセンス(標準的で変更のないMITライセンス)を含んでいます。
+
+..
+    `Glossary`_ of PyPy words to help you align your inner self with
+    the PyPy universe.
+
+`Glossary`_ のPyPy単語集はあなた自身をPyPyの分野と引き合わせる手助けをします。
+
+
+..
+    Status
+    ===================================
+
+対応状況
 ===================================
 
+<<<<<<< local
 PyPy can be used to run Python programs on Linux, OS/X,
 Windows, on top of .NET, and on top of Java.
 To dig into PyPy it is recommended to try out the current
 Mercurial default branch, which is always working or mostly working,
 instead of the latest release, which is `1.9`__.
+=======
+..
+    PyPy can be used to run Python programs on Linux, OS/X,
+    Windows, on top of .NET, and on top of Java.
+    To dig into PyPy it is recommended to try out the current
+    Mercurial default branch, which is always working or mostly working,
+    instead of the latest release, which is `1.6`__.
+
+PyPyはLinux、OS/X、Windows、.NET環境、Java環境でPythonプログラムを実行するために使用することができます。
+PyPyについて掘り下げるために、最新のリリース `1.6`__ の代わりにつねに取り組んでいるまたは、主に取り組んでいる現在のMercurialのデフォルトブランチを試みることを推奨します。
+>>>>>>> other
 
 .. __: release-1.9.0.html
 
-PyPy is mainly developed on Linux and Mac OS X.  Windows is supported,
-but platform-specific bugs tend to take longer before we notice and fix
-them.  Linux 64-bit machines are supported (though it may also take some
-time before we notice and fix bugs).
+..
+    PyPy is mainly developed on Linux and Mac OS X.  Windows is supported,
+    but platform-specific bugs tend to take longer before we notice and fix
+    them.  Linux 64-bit machines are supported (though it may also take some
+    time before we notice and fix bugs).
 
-PyPy's own tests `summary`_, daily updated, run through BuildBot infrastructure.
-You can also find CPython's compliance tests run with compiled ``pypy-c``
-executables there.
+PyPyは主にLinuxとMac OS X上で開発されています。
+Windowsはサポートされた。しかし、プラットフォーム特有のバグは我々が気づき直すのに時間がかかる傾向がある。
+Linux 64-bitマシンはサポートされた。(だけれどもそれもまた我々が気づき直すのに、時間がかかるかもしれない)
 
+..
+    PyPy's own tests `summary`_, daily updated, run through BuildBot infrastructure.
+    You can also find CPython's compliance tests run with compiled ``pypy-c``
+    executables there.
 
-Source Code Documentation
+PyPyは 毎日更新されるBuildBotインフラストラクチャを介して実行する独自のテストをもつ。 `summary`_
+あなたはまたCPythonに含まれるテストをみつけ、コンパイルして、 ``pypy-c`` の実行とともに走らせることができます。
+
+..
+    Source Code Documentation
+    ===============================================
+
+ソースコードドキュメント
 ===============================================
 
-`object spaces`_ discusses the object space interface 
-and several implementations. 
+..
+    `object spaces`_ discusses the object space interface 
+    and several implementations. 
 
-`bytecode interpreter`_ explains the basic mechanisms 
-of the bytecode interpreter and virtual machine. 
+`object spaces`_ 議論するオブジェクトスペースインタフェースといくつかの実現について議論します。
 
-`interpreter optimizations`_ describes our various strategies for
-improving the performance of our interpreter, including alternative
-object implementations (for strings, dictionaries and lists) in the
-standard object space.
+..
+    `bytecode interpreter`_ explains the basic mechanisms 
+    of the bytecode interpreter and virtual machine. 
 
-`translation`_ is a detailed overview of our translation process.  The
-rtyper_ is the largest component of our translation process.
+`bytecode interpreter`_ 標準的なバイトコードインタプリタの構造と仮想マシンの構造を説明します。
 
-`dynamic-language translation`_ is a paper that describes
-the translation process, especially the flow object space
-and the annotator in detail. (This document is one
-of the `EU reports`_.)
+..
+    `interpreter optimizations`_ describes our various strategies for
+    improving the performance of our interpreter, including alternative
+    object implementations (for strings, dictionaries and lists) in the
+    standard object space.
 
-`low-level encapsulation`_ describes how our approach hides
-away a lot of low level details. This document is also part
-of the `EU reports`_.
+`interpreter optimizations`_ 様々な我々のインタプリタにおける性能改善のための戦略を説明します。
 
-`translation aspects`_ describes how we weave different
-properties into our interpreter during the translation
-process. This document is also part of the `EU reports`_.
+..
+    `translation`_ is a detailed overview of our translation process.  The
+    rtyper_ is the largest component of our translation process.
 
-`garbage collector`_ strategies that can be used by the virtual
-machines produced by the translation process.
+`translation`_ は我々の変換工程の詳細な概略です。 rtyper_ は最新の変換工程の構成要素です。
 
-`parser`_ contains (outdated, unfinished) documentation about
-the parser.
+..
+    `dynamic-language translation`_ is a paper that describes
+    the translation process, especially the flow object space
+    and the annotator in detail. (This document is one
+    of the `EU reports`_.)
 
-`rlib`_ describes some modules that can be used when implementing programs in
-RPython.
+`dynamic-language translation`_ は変換工程を説明する資料です。とりわけオブジェクト空間の流れとアノテーションの詳細です。
+(このドキュメントは `EU reports`_ の一つです。)
 
-`configuration documentation`_ describes the various configuration options that
-allow you to customize PyPy.
+..
+    `low-level encapsulation`_ describes how our approach hides
+    away a lot of low level details. This document is also part
+    of the `EU reports`_.
 
-`CLI backend`_ describes the details of the .NET backend.
+`low-level encapsulation`_ はどのように多くの低レベルな詳細を隠し離すのか説明します。このドキュメントも `EU reports`_ の一つです。
 
-`JIT Generation in PyPy`_ describes how we produce the Python Just-in-time Compiler
-from our Python interpreter.
+..
+    `translation aspects`_ describes how we weave different
+    properties into our interpreter during the translation
+    process. This document is also part of the `EU reports`_.
 
+`translation aspects`_ はどのように我々のインタプリタが変換工程の間に異なった特性を織りまぜているのか説明します。このドキュメントも `EU reports`_ の一つです。
+
+..
+    `garbage collector`_ strategies that can be used by the virtual
+    machines produced by the translation process.
+
+`garbage collector`_ は変換工程に生み出した仮想マシンを使われることができる戦略です。
+
+..
+    `parser`_ contains (outdated, unfinished) documentation about
+    the parser.
+
+`parser`_ は構文解析器に関するドキュメント(最新ではなく未完成)を含んでいます。
+
+..
+    `rlib`_ describes some modules that can be used when implementing programs in
+    RPython.
+
+`rlib`_ はRPythonのプログラム実装時に使うことが出来る、いくつかのモジュールについて説明します。
+
+..
+    `configuration documentation`_ describes the various configuration options that
+    allow you to customize PyPy.
+
+`configuration documentation`_ あなたに様々な許可されたPyPyのカスタマイズ設定オプションを説明します。
+
+..
+    `CLI backend`_ describes the details of the .NET backend.
+
+`CLI backend`_ は.NETの裏側を説明します。
+
+..
+    `JIT Generation in PyPy`_ describes how we produce the Python Just-in-time Compiler
+    from our Python interpreter.
+
+`JIT Generation in PyPy`_ はどのようにPythonのジャストインタイムコンパイラをPythonインタプリタから提供するのか説明します。
 
 
 .. _`FAQ`: faq.html
 .. _`Sandboxing Python code`: sandbox.html
 .. _`LICENSE`: https://bitbucket.org/pypy/pypy/src/default/LICENSE
 
-PyPy directory cross-reference 
-------------------------------
+..
+    PyPy directory cross-reference 
+    ------------------------------
 
-Here is a fully referenced alphabetical two-level deep 
-directory overview of PyPy: 
+Pythonディレクトリ構成リファレンス
+-----------------------------------
+
+..
+    Here is a fully referenced alphabetical two-level deep 
+    directory overview of PyPy: 
+
+これはPyPyの全網羅された2階層の深さでアルファベット順によるディレクトリ構成の参考文書です。
+
+..
+  ================================   =========================================== 
+  Directory                          explanation/links
+  ================================   =========================================== 
+  `pypy/annotation/`_                `type inferencing code`_ for `RPython`_ programs 
+
+  `pypy/bin/`_                       command-line scripts, mainly `py.py`_ and `translatorshell.py`_
+
+  `pypy/config/`_                    handles the numerous options for building and running PyPy
+
+  `pypy/doc/`_                       text versions of PyPy developer documentation
+
+  `pypy/doc/config/`_                documentation for the numerous translation options
+
+  `pypy/doc/discussion/`_            drafts of ideas and documentation
+
+  ``doc/*/``                         other specific documentation topics or tools
+
+  `pypy/interpreter/`_               `bytecode interpreter`_ and related objects
+                                     (frames, functions, modules,...) 
+
+  `pypy/interpreter/pyparser/`_      interpreter-level Python source parser
+
+  `pypy/interpreter/astcompiler/`_   interpreter-level bytecode compiler, via an AST
+                                     representation
+
+  `pypy/module/`_                    contains `mixed modules`_ implementing core modules with 
+                                     both application and interpreter level code.
+                                     Not all are finished and working.  Use the ``--withmod-xxx``
+                                     or ``--allworkingmodules`` translation options.
+
+  `pypy/objspace/`_                  `object space`_ implementations
+
+  `pypy/objspace/trace.py`_          the `trace object space`_ monitoring bytecode and space operations
+
+  `pypy/objspace/dump.py`_           the dump object space saves a large, searchable log file
+                                     with all operations
+
+  `pypy/objspace/thunk.py`_          the `thunk object space`_, providing unique object features 
+
+  `pypy/objspace/flow/`_             the FlowObjSpace_ implementing `abstract interpretation`_
+
+  `pypy/objspace/std/`_              the StdObjSpace_ implementing CPython's objects and types
+
+  `pypy/rlib/`_                      a `"standard library"`_ for RPython_ programs
+
+  `pypy/rpython/`_                   the `RPython Typer`_ 
+
+  `pypy/rpython/lltypesystem/`_      the `low-level type system`_ for C-like backends
+
+  `pypy/rpython/ootypesystem/`_      the `object-oriented type system`_ for OO backends
+
+  `pypy/rpython/memory/`_            the `garbage collector`_ construction framework
+
+  `pypy/tool/`_                      various utilities and hacks used from various places 
+
+  `pypy/tool/algo/`_                 general-purpose algorithmic and mathematic
+                                     tools
+
+  `pypy/tool/pytest/`_               support code for our `testing methods`_
+
+  `pypy/translator/`_                translation_ backends and support code
+
+  `pypy/translator/backendopt/`_     general optimizations that run before a backend generates code
+
+  `pypy/translator/c/`_              the `GenC backend`_, producing C code from an
+                                     RPython program (generally via the rtyper_)
+
+  `pypy/translator/cli/`_            the `CLI backend`_ for `.NET`_ (Microsoft CLR or Mono_)
+
+  `pypy/translator/goal/`_           our `main PyPy-translation scripts`_ live here
+
+  `pypy/translator/jvm/`_            the Java backend
+
+  `pypy/translator/tool/`_           helper tools for translation, including the Pygame
+                                     `graph viewer`_
+
+  ``*/test/``                        many directories have a test subdirectory containing test 
+                                     modules (see `Testing in PyPy`_) 
+
+  ``_cache/``                        holds cache files from internally `translating application 
+                                     level to interpreterlevel`_ code.   
+  ================================   =========================================== 
+
 
 ================================   =========================================== 
-Directory                          explanation/links
+ディレクトリ                       説明/リンク
 ================================   =========================================== 
-`pypy/annotation/`_                `type inferencing code`_ for `RPython`_ programs 
+`pypy/annotation/`_                `RPython`_ プログラム用の `type inferencing code`_
 
-`pypy/bin/`_                       command-line scripts, mainly `py.py`_ and `translatorshell.py`_
+`pypy/bin/`_                       コマンドラインスクリプトです。ほとんどは `py.py`_  `translatorshell.py`_ です。
 
-`pypy/config/`_                    handles the numerous options for building and running PyPy
+`pypy/config/`_                    非常にたくさんあるビルド時、PyPy実行時のオプションを扱います。
 
-`pypy/doc/`_                       text versions of PyPy developer documentation
+`pypy/doc/`_                       PyPy開発者ドキュメントの試作版。
 
-`pypy/doc/config/`_                documentation for the numerous translation options
+`pypy/doc/config/`_                非常にたくさんある変換オプション。
 
-`pypy/doc/discussion/`_            drafts of ideas and documentation
+`pypy/doc/discussion/`_            アイデア、ドキュメントの草案。
 
-``doc/*/``                         other specific documentation topics or tools
+``doc/*/``                         他に特化したドキュメント題目、ツール。
 
-`pypy/interpreter/`_               `bytecode interpreter`_ and related objects
+`pypy/interpreter/`_               `bytecode interpreter`_ と関連したオブジェクト。
                                    (frames, functions, modules,...) 
 
-`pypy/interpreter/pyparser/`_      interpreter-level Python source parser
+`pypy/interpreter/pyparser/`_      インタプリタレベルのPythonコード構文解析器。
 
-`pypy/interpreter/astcompiler/`_   interpreter-level bytecode compiler, via an AST
-                                   representation
+`pypy/interpreter/astcompiler/`_   インタプリタレベルのASTを通すバイトコードコンパイラ。
 
-`pypy/module/`_                    contains `mixed modules`_ implementing core modules with 
-                                   both application and interpreter level code.
-                                   Not all are finished and working.  Use the ``--withmod-xxx``
-                                   or ``--allworkingmodules`` translation options.
+`pypy/module/`_                    アプリケーションとインタプリタレベルの`mixed modules`_ とコアモジュールの実装を含んでいます。
+                                   全ての仕事が完了している訳ではない。
+                                   ``--withmod-xxx`` か ``--allworkingmodules`` 変換オプションを使って下さい。
 
-`pypy/objspace/`_                  `object space`_ implementations
+`pypy/objspace/`_                  `object space`_ の実装です。
 
-`pypy/objspace/trace.py`_          the `trace object space`_ monitoring bytecode and space operations
+`pypy/objspace/trace.py`_          `trace object space`_ はバイトコードと空間の活用します。
 
-`pypy/objspace/dump.py`_           the dump object space saves a large, searchable log file
-                                   with all operations
+`pypy/objspace/dump.py`_           ダンプオブジェクトのスペースはすべての操作で検索可能な大規模なログファイルを節約をします。
 
-`pypy/objspace/thunk.py`_          the `thunk object space`_, providing unique object features 
+`pypy/objspace/thunk.py`_          `thunk object space`_ は単一なオブジェクト機能を提供します。
 
-`pypy/objspace/flow/`_             the FlowObjSpace_ implementing `abstract interpretation`_
+`pypy/objspace/flow/`_             FlowObjSpace_  `abstract interpretation`_ を実装します。
 
-`pypy/objspace/std/`_              the StdObjSpace_ implementing CPython's objects and types
+`pypy/objspace/std/`_              StdObjSpace_ はCpythonのオブジェクトと型を実装します。
 
-`pypy/rlib/`_                      a `"standard library"`_ for RPython_ programs
+`pypy/rlib/`_                      RPython_ プログラムによる `"standard library"`_ です。
 
-`pypy/rpython/`_                   the `RPython Typer`_ 
+`pypy/rpython/`_                   `RPython Typer`_ です。
 
-`pypy/rpython/lltypesystem/`_      the `low-level type system`_ for C-like backends
+`pypy/rpython/lltypesystem/`_      Cに似たバックエンドによる `low-level type system`_ です。
 
-`pypy/rpython/ootypesystem/`_      the `object-oriented type system`_ for OO backends
+`pypy/rpython/ootypesystem/`_      OOバックエンドによる `object-oriented type system`_ です。
 
-`pypy/rpython/memory/`_            the `garbage collector`_ construction framework
+`pypy/rpython/memory/`_            `garbage collector`_ 構造です。
 
-`pypy/tool/`_                      various utilities and hacks used from various places 
+`pypy/tool/`_                      様々な箇所で使われるユーティリティ、ハックです。
 
-`pypy/tool/algo/`_                 general-purpose algorithmic and mathematic
-                                   tools
+`pypy/tool/algo/`_                 多目的なアルゴリズムと数理的なツールです。
 
-`pypy/tool/pytest/`_               support code for our `testing methods`_
+`pypy/tool/pytest/`_               私たちの `testing methods`_ の補助ツールです。