lledu · lledu · Mar 5, 2013 · Mar 5, 2013 · Mar 5, 2013 · Mar 5, 2013
diff --git a/README.md b/README.md
@@ -1,3 +1,15 @@
 If you have any problem, do not hesitate to tell me 
+
 via email:dpzhang314@163.com
+
+
+To make html file, just type in "make",
+
+
+Use web browser to preview it;
+
+
+To clean html file, just type in "make clean";
+
+
 Thanks.
diff --git a/appendices/contributing/text.xml b/appendices/contributing/text.xml
@@ -1,13 +1,11 @@
 <?xml version="1.0"?>
 <guide self="appendices/contributing/">
 <chapter>
-<title>Contributing to This Document</title>
+<title>为本文档贡献自己的力量</title>
 
 <body>
 <p>
-Contributions for this document are very welcome. Whether you've found a typo
-or have written an entire new section, the best way to get in touch is via Bugzilla
-at <uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>.
+非常欢迎为本文档添砖加瓦，哪怕是印刷错误或一段新的内容，您都可以通过登录Bugzilla<uri link="http://bugs.gentoo.org">bugs.gentoo.org</uri>来提交.
 </p>
 
 <p>

diff --git a/appendices/contributors/text.xml b/appendices/contributors/text.xml
@@ -1,11 +1,11 @@
 <?xml version="1.0"?>
 <guide self="appendices/contributors/">
 <chapter>
-<title>Contributions</title>
+<title>编者目录</title>
 <body>
 
 <p>
-This page lists the contributions to the Gentoo Development Guide:
+在此列出本册各章节编者，再次感谢他们为Gentoo开发文档做出的贡献:
 </p>
 
 <authors>

diff --git a/appendices/editor-configuration/text.xml b/appendices/editor-configuration/text.xml
@@ -1,30 +1,30 @@
-<?xml version="1.0"?>
-<guide self="appendices/editor-configuration/">
-<chapter>
-<title>Editor Configuration</title>
-<body>
-
-<p>
-This section provides hints as to how to configue your text editor for working with ebuilds.
-</p>
-
-<todo>
-from vapier:  add a section for nano ... users just have to copy
-/etc/nanorc to ~/.nanorc and uncomment the sections for ebuilds
-</todo>
-
-</body>
-
-<section>
-<title>Contents</title>
-<body>
-<contentsTree/>
-</body>
-</section>
-</chapter>
-
-<include href="vim/"/>
-<include href="emacs/"/>
-<include href="xemacs/"/>
-
-</guide>
+<?xml version="1.0"?>
+<guide self="appendices/editor-configuration/">
+<chapter>
+<title>工欲善其功，必先利其器</title>
+<body>
+
+<p>
+给你一点提示，有关编辑ebuilds文档所用的text editor的提示.
+</p>
+
+<todo>
+据vapier所言:你用nano么?...哥们你只用复制
+/etc/nanorc到~/.nanorc并去除ebuilds段的相关注释就行.
+</todo>
+
+</body>
+
+<section>
+<title>看看有没有你想要的</title>
+<body>
+<contentsTree/>
+</body>
+</section>
+</chapter>
+
+<include href="vim/"/>
+<include href="emacs/"/>
+<include href="xemacs/"/>
+
+</guide>
diff --git a/appendices/editor-configuration/vim/text.xml b/appendices/editor-configuration/vim/text.xml
@@ -1,25 +1,24 @@
-<?xml version="1.0"?>
-<guide self="appendices/editor-configuration/vim/">
-<chapter>
-<title>Configuring <c>vim</c> and <c>gvim</c></title>
-<body>
-
-<p>
-For full whitespace, character set, syntax highlighting and indent settings for
-all of Gentoo's file-types in <c>vim</c> and <c>gvim</c>, emerge the
-<c>app-vim/gentoo-syntax</c> package.
-</p>
-
-<p>
-Full documentation is provided with the package, and can be viewed
-by using <c>vim</c>'s internal help browser (<c>:help gentoo-syntax</c>).
-</p>
-
-<p>
-When fixing ebuilds with broken whitespace, the <c>:retab!</c> command may be
-of interest. The ! is required to replace spaces with tabs.
-</p>
-
-</body>
-</chapter>
-</guide>
+<?xml version="1.0"?>
+<guide self="appendices/editor-configuration/vim/">
+<chapter>
+<title>神级编辑器<c>vim</c>和<c>gvim</c></title>
+<body>
+
+<p>
+所有gentoo文档中的whitespace, character set, syntax高亮和缩进设置
+<c>vim</c>与<c>gvim</c>类似, emerge这个<c>app-vim/gentoo-syntax</c>软件包.
+</p>
+
+<p>
+Full documentation is provided with the package, and can be viewed
+by using <c>vim</c>'s internal help browser (<c>:help gentoo-syntax</c>).
+</p>
+
+<p>
+When fixing ebuilds with broken whitespace, the <c>:retab!</c> command may be
+of interest. The ! is required to replace spaces with tabs.
+</p>
+
+</body>
+</chapter>
+</guide>
diff --git a/appendices/further-reading/text.xml b/appendices/further-reading/text.xml
@@ -1,66 +1,62 @@
-<?xml version="1.0"?>
-<guide self="appendices/further-reading/">
-<chapter>
-<title>Further Reading</title>
-<body>
-
-<p>
-This section lists some recommended further reading. These are real
-recommendations, not padding designed to make this document look important.
-</p>
-
-<section>
-<title>Books</title>
-<body>
-
-<dl>
-  <dt>
-    Mastering Regular Expressions
-  </dt>
-  <dd>
-    <p>
-    "Mastering Regular Expressions" by Jeffrey E. F. Friedl (O'Reilly,
-    ISBN 0-596-00289-0) is <b>the</b> book on regular expressions. Very readable and
-    devoid of the usual mathematical jargon that tends to fill up these kinds of
-    books. <uri link="http://www.oreilly.com/catalog/regex2/">Publisher's page</uri>
-    </p>
-  </dd>
-</dl>
-
-</body>
-</section>
-
-<section>
-<title>Articles</title>
-<body>
-
-<dl>
-  <dt>
-    Making Packager-Friendly Software
-  </dt>
-  <dd>
-    <p>
-    <uri link="http://www.onlamp.com/pub/a/onlamp/2005/03/31/packaging.html">Making
-    Packager-Friendly Software</uri> by Julio M. Merino Vidal describes various things
-    that can be done by upstream software providers to make life easy for the
-    distribution people (that means you).
-    </p>
-  </dd>
-  <dt>
-    How to Report Bugs Effectively
-  </dt>
-  <dd>
-    <p>
-    <uri link="http://freshmeat.net/articles/view/149">How to Report Bugs
-    Effectively</uri> by Simon Tatham is a good overview of effective bug reporting.
-    </p>
-  </dd>
-</dl>
-
-</body>
-</section>
-
-</body>
-</chapter>
-</guide>
-
+<?xml version="1.0"?>
+<guide self="appendices/further-reading/">
+<chapter>
+<title>延伸阅读</title>
+<body>
+
+<p>
+强烈推荐阅读本章列出的文章、书籍. 次均肺腑之言,非锦上添花凑数之物.
+</p>
+
+<section>
+<title>书籍是人类向上的阶梯</title>
+<body>
+
+<dl>
+  <dt>
+    Mastering Regular Expressions(掌握正则表达式)
+  </dt>
+  <dd>
+    <p>
+    "Mastering Regular Expressions" Jeffrey E. F. Friedl (O'Reilly,
+    ISBN 0-596-00289-0)著，是<b>专门</b>介绍Regular Expressions. 可读性强、深入浅出
+    规避以往此类书籍中常用的繁杂冗长之数学术语. <uri link="http://www.oreilly.com/catalog/regex2/">扉页</uri>
+    </p>
+  </dd>
+</dl>
+
+</body>
+</section>
+
+<section>
+<title>文章</title>
+<body>
+
+<dl>
+  <dt>
+    Making Packager-Friendly Software
+  </dt>
+  <dd>
+    <p>
+    <uri link="http://www.onlamp.com/pub/a/onlamp/2005/03/31/packaging.html">Making
+    Packager-Friendly Software</uri> 由Julio M. Merino Vidal编著，指出了很多upstream software providers可做的事情，它会更加方便于使用它的人.
+    </p>
+  </dd>
+  <dt>
+    How to Report Bugs Effectively
+  </dt>
+  <dd>
+    <p>
+    <uri link="http://freshmeat.net/articles/view/149">How to Report Bugs
+    Effectively</uri>由Simon Tatham撰写，想更加有效的提交Bugs么，闲暇时先读一下它吧.
+    </p>
+  </dd>
+</dl>
+
+</body>
+</section>
+
+</body>
+</chapter>
+</guide>
+
diff --git a/appendices/text.xml b/appendices/text.xml
@@ -5,7 +5,7 @@
 
 <body>
 <p>
-本章包含一些可能有用的附加文档方便参考。
+本章包含一些可能有用的附加文档,方便参考。
 </p>
 </body>
 

diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
@@ -16,42 +16,36 @@
 <subsection>
 <title>无效的 <c>static</c> use 标记</title>
 <body>
-The <c>static</c> use-flag should only be used to make a binary use static
-linking instead of dynamic linking. It should not be used to make a library
-install static libraries. Instead, the <c>static-libs</c> use-flag is used for this.
+<c>static</c> use 标记在生成二进制文件的时候只能使用静态链接而不能使用动态链接。
+它不能使一个库安装成为一个静态库，如果想这样做，请使用<c>static-libs</c> use 标记。
 </body>
 </subsection>
 
 <subsection>
-<title>Invalid use of <c>ROOT</c></title>
+<title><c>ROOT</c>的无效使用</title> 
 <body>
 <p>
-The usage of <c>ROOT</c> is only designed to influence the way the package is
-installed (ie. into <c>ROOT</c>) - building and compiling should not depend on
-<c>ROOT</c>. As a consequence of this the usage of <c>ROOT</c> in <c>src_*</c>
-functions is not allowed.
+<c>ROOT</c> 仅仅只是用来影响包的安装路径的（例如 into <c>ROOT</c>），构建和编译却不应该依靠 <c>ROOT</c>。
+所以 <c>ROOT</c> 不能够在 <c>src_*</c> 函数中使用。
 </p>
 
 <p>
-See also <uri link="::ebuild-writing/variables#ROOT"/>.
+参见 <uri link="::ebuild-writing/variables#ROOT"/>.
 </p>
 </body>
 </subsection>
 
 <subsection>
-<title>Referencing the full path to documentation files that could be
-compressed</title>
-<body>
-When printing out to the users where to find files like INSTALL, do not specify
-the full path since <c>PORTAGE_COMPRESS</c> comes into play.  The file could be
-compressed with gzip, bzip2, or some other random compression tool.  So,
-instead of doing this:
+<title>引用可能被压缩的文件全路径</title>
+<body>当给用户指出在哪找文件（例如INSTALL文件）时不要用确定的全路径名，因为 <c>PORTAGE_COMPRESS</c> 在起作用。
+文件可能被gzip，bzip2或者其他的压缩工具压缩。所以，不要像这样做：
+
 
 <codesample lang="ebuild">
 elog "They are listed in /usr/share/doc/${PF}/INSTALL.gz"
 </codesample>
 
-Do something like:
+要这样做:
 
 <codesample lang="ebuild">
 elog "They are listed in the INSTALL file in /usr/share/doc/${PF}"
@@ -60,30 +54,24 @@ elog "They are listed in the INSTALL file in /usr/share/doc/${PF}"
 </subsection>
 
 <subsection>
-<title>Build log not verbose</title>
+<title>编译日志不详细</title>
 <body>
-When writing ebuilds, you should always check the build log, because the build
-system might ignore CC/CXX/LD/CFLAGS/LDFLAGS and such or add undesired flags
-by default. In order to analyze this and have complete information, in case
-someone reports a bug for your package, the <b>build log must always be verbose.</b>
+写ebuild文件时，你应该时常检查编译日志，因为编译系统有可能会忽略CC/CXX/LD/CFLAGS/LDFLAGS，
+或者会默认增加不需要的标志。为了有完整的信息分析这种情况，以便别人为你的包报告漏洞，<b>编译日志必须详细</b>
 <p>
-There are several ways to fix non-verbose build logs depending on the build system:
+有许多方法修改不详细的编译日志，这要看用的什么编译系统：
 </p>
 <p>
-For <c>cmake</c> based build systems it should be sufficient that the ebuild calls
-cmake-utils_src_compile which picks up the cmake-utils.eclass variable 'CMAKE_VERBOSE=1'
-by default. If you call emake directly for whatever reason, you can do 'emake VERBOSE=1'
-(note that cmake-utils_src_compile takes arguments as well which are passed to make).
+对于基于 <c>cmake</c> 的编译系统，这样做就行了：ebuild会调用cmake-utils_src_compile，
+它默认设置变量'CMAKE_VERBOSE=1'。如果你由于某些原因直接调用了emake，你可以设置'emake VERBOSE=1'
+（注意cmake-utils_src_compile在make中也是可以带参数的）
 </p>
-
 <p>
-For <c>autotools</c> based build systems you can pass '--disable-silent-rules' to econf,
-or use EAPI 5 where that argument is passed automatically. 'emake V=1' should also work.
+对于基于 <c>autotools</c> 的编译系统，你可以给econf传递选项'--disable-silent-rules'。
+或者用EAPI 5让参数自动传递，设置'emake V=1'也是可以的。
 </p>
-
 <p>
-For custom Makefiles you often have to write a patch. Try to get upstream to include an
-option like 'V=1' to enable full verbosity.
+对于自定义的Makefiles，你必须经常写补丁。回溯上游的时候尝试使用例如'V=1'这样的可以记录详细情况的选项。
 </p>
 <note>In case you encounter an affected package which uses a build system not
 controllable by portage or eclasses you should file a bug (preferably with a patch)
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,7 +5,7 @@ @@
     <body>
     <p>
-    本章包含一些可能有用的附加文档方便参考。
+    本章包含一些可能有用的附加文档,方便参考。
     </p>
     </body>
@@ Expand Down @@