cvs: peardoc /ja/chapters intro.xml

hirokawa Mon Feb 11 18:14:28 2002 EDT Modified files: /peardoc/ja/chapters intro.xml Log: translation updated.

Index: peardoc/ja/chapters/intro.xml diff -u peardoc/ja/chapters/intro.xml:1.2 peardoc/ja/chapters/intro.xml:1.3 --- peardoc/ja/chapters/intro.xml:1.2 Fri Feb 1 09:55:16 2002 +++ peardoc/ja/chapters/intro.xml Mon Feb 11 18:14:28 2002 @@ -1,46 +1,218 @@ <?xml encoding="utf-8"?> -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <chapter id="introduction"> + <docinfo> + <author> + <firstname>Stig</firstname> + <surname>Bakken</surname> + </author> + <date>2002-02-10</date> + </docinfo> <title>はじめに</title> <simpara> - PEAR は、1999/11/21 に生まれたMalin Bakkenに捧げられています。(最初 - のPEARのコードは、彼女が生まれたちょうど二時間後に書かれました。) + PEAR は、1999/11/21 に生まれたMalin Bakkenに捧げられています。 </simpara> - <sect1 id="pear-whatis"> + <sect1 id="about.pear"> <title>PEARとは?</title> - <simpara> - PEAR は、TeXの CTAN および Perlの CPANにヒントを得たPHP拡張および - PHPライブラリのコード用のコードレポジトリです。 - </simpara> <para> - PEARの目的は次のようなものです。 + PEAR は、"PHP Extension and Application Repository"を省略したもの + で、果物(梨)と同じように発音します。PEARの目的は次のようなものです。 <itemizedlist> <listitem> <simpara> - ライブラリコードの作者に他の開発者とコードを共有するための確実 - な手段を提供する + PHPユーザのためのオープンソースコードの構造化されたライブラリ </simpara> </listitem> <listitem> <simpara> - PHPコミュニティにコードを共有するためのインフラを提供する + コード配布及びパッケージ管理のためのシステム </simpara> </listitem> <listitem> <simpara> - 開発者が移植性の高い再使用可能なコードを書きやすくするために標 - 準を定義する + <link linkend="standards">ここで指定されている</link>PHPのコー + ド作成に関する標準スタイル </simpara> </listitem> <listitem> <simpara> - コードの維持管理と配布のためのツールを提供する + The PHP Foundation Classes (PFC)。<link linkend="about-pfc">詳 + 細は以下を参照</link> + </simpara> + </listitem> + <listitem> + <simpara> + The PHP Extension Code Library (PECL), + <link linkend="about-pecl">詳細は以下を参照</link> + </simpara> + </listitem> + <listitem> + <simpara> + PHP/PEARコミュニティをサポートするためのWebサイト、メーリングリ + スト、ダウンロードミラー </simpara> </listitem> </itemizedlist> </para> + + <sect2 id="about-pear-stlib"> + <title>PHPコードの構造化されたライブラリ</title> + <para> + The code in PEAR is partitioned in "packages". Each package + is a separate project with its own development team, version + number, release cycle, documentation and a defined relation to + other packages (including dependencies). Packages are + distributed as gzipped tar files with a description file inside, + and installed on your local system using the PEAR installer. + </para> + <para> + There are two types of packages: source packages (containing + source files only), and binary packages (containing + platform-specific binary files, and possible source files). + Installing source packages with C code obviously requires a C + build environment. + </para> + <para> + PEAR defines a package tree, where each "node" in the tree is + represented by a part of the package name. The nodes are + organized by simple descriptive topics, and each part is + separated by an underscore. Examples of package names are + "MP3_Id", "Archive_Tar" and "HTTP_Post". + </para> + <para> + Packages may relate to eachother through explicit dependencies, + but there is no automatic relation between for example a package + and its "parent" in the package tree (for example, "HTTP_Post" is + by default independent of "HTTP"). + </para> + <para> + A few top-level nodes in the package tree called + "sub-repositories" have special functions, currently these are + <link linkend="about-pecl">PECL</link>, <link + linkend="about-gtk">Gtk</link> and <link + linkend="about-app">App</link>. For each of these, different + rules apply, see more in the description of each sub-repository + below. + </para> + <para> + A style guide, the <link linkend="standards">PEAR Coding + Standards</link> (short PCS), exists to ease collaboration + between PEAR developers, to help quality and portability, and to + help PEAR contributors to provide consistent-looking-and-feeling + APIs. For packages in the <link linkend="about-pfc">PFC</link>, + this standard applies strictly, for non-PFC packages it applies + more relaxed. + </para> + </sect2> + + <sect2 id="about-pear-distpkg"> + <title>コード配布及びパッケージ管理</title> + <para> + All PEAR packages are registered in and uploaded to a central + database available at pear.php.net. Open-sourced + third-party packages may also be registered and uploaded. + Closed-source packages may be installed by the PEAR installer, + but the PEAR database is for open-source code only. + </para> + <para> + Pear.php.net will provide both a human-friendly (HTML) and + machine-friendly (currently XML-RPC) interface to the PEAR + database. Package downloads are done with plain HTTP. + Other functions the pear.php.net site will provide are: + <itemizedlist> + <listitem> + <simpara>user account management (integrated with the CVS server)</simpara> + </listitem> + <listitem> + <simpara>package management</simpara> + </listitem> + <listitem> + <simpara>release management</simpara> + </listitem> + </itemizedlist> + </para> + <para> + Packages are distributed as a gzipped tar file with an XML description + file inside. The description file contains some information + about the package, a list of files and their roles, and dependencies. + </para> + </sect2> + + <sect2 id="about-pfc"> + <title>The PHP Foundation Classes</title> + <titleabbrev>PFC</titleabbrev> + <para> + The PHP Foundation Classes is a subset of PEAR that focuses on + quality, generality, interoperability and compatibility. If + PHP is going to continue bundling PEAR packages beyond the + installer, it will bundle the PFC. + </para> + <para> + Focus on quality means that no packages or releases or less than "stable" + quality are accepted in the PFC. + </para> + <para> + Generality means that packages should not be more than reasonably + specific to any type of environment (such as an output format + like HTML, an operating system, a web server or SAPI backend + etc). + </para> + <para> + Interoperable packages work well with other packages, have + stable, standardized APIs, prefer other well-established (and + also interoperable) components and also work well in different + environments (PHP version, SAPI backend, operating system etc.) + </para> + <para> + Compatibility is not just about supporting the same syntax and + semantics as earlier versions, it is also about planning ahead + when writing the code. Designing code so it would be easy, or at + least possible, to add features that are likely to appear later, + gives code that is also "forward-compatible". + </para> + </sect2> + + <sect2 id="about-pecl"> + <title>The PHP Extension Code Library (PECL)</title> + <subtitle>PECL</subtitle> + <para> + PECL (pronounced "pickle") is a sub-repository of PEAR for C + extensions ala those distributed with PHP 4, in fact, having + somewhere to move extensions to from PHP was one of the + motivations when creating PECL. Extensions in PECL follow PHP's + coding standards rather than PEAR's, but they are distributed and + installed as PEAR packages. + </para> + <para> + The process of moving an extension from PHP to PECL is referred + to as "pickling". + </para> + </sect2> + + <sect2 id="about-gtk"> + <title>Gtkパッケージ</title> + <subtitle>Gtk</subtitle> + <para> + TBD + </para> + </sect2> + + <sect2 id="about-app"> + <title>Applicationパッケージ</title> + <subtitle>App</subtitle> + <para> + TBD + <!-- + Ideas: + * files may also be installed in the web server's document root + * installer knows how to configure one or more web servers to + set up a virtual host or subdirectory for the application + --> + </para> + </sect2> + </sect1> </chapter>