public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Deng <theandy.deng@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Deng <theandy.deng@gmail.com>
Subject: [PATCH v2 3/3] docs/zh_CN: Add coding-style into docs build system
Date: Wed, 25 Jan 2017 12:14:33 +0800	[thread overview]
Message-ID: <20170125041433.9713-3-theandy.deng@gmail.com> (raw)
In-Reply-To: <20170125041433.9713-1-theandy.deng@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 2068 bytes --]

Tested by the command:

    make htmldocs

During the compiling process, zh_CN/coding-style.rst has no errors and
warnings generated, the generated html document has been checked.

Signed-off-by: Andy Deng <theandy.deng@gmail.com>
---
 Documentation/index.rst                                      | 10 +++++++++-
 .../translations/zh_CN/{CodingStyle => coding-style.rst}     |  0
 Documentation/translations/zh_CN/index.rst                   | 12 ++++++++++++
 3 files changed, 21 insertions(+), 1 deletion(-)
 rename Documentation/translations/zh_CN/{CodingStyle => coding-style.rst} (100%)
 create mode 100644 Documentation/translations/zh_CN/index.rst

diff --git a/Documentation/index.rst b/Documentation/index.rst
index cb5d776..f6e641a 100644
--- a/Documentation/index.rst
+++ b/Documentation/index.rst
@@ -47,7 +47,7 @@ These books get into the details of how specific kernel subsystems work
 from the point of view of a kernel developer.  Much of the information here
 is taken directly from the kernel source, with supplemental material added
 as needed (or at least as we managed to add it — probably *not* all that is
-needed). 
+needed).
 
 .. toctree::
    :maxdepth: 2
@@ -68,6 +68,14 @@ Korean translations
 
    translations/ko_KR/index
 
+Chinese translations
+--------------------
+
+.. toctree::
+   :maxdepth: 1
+
+   translations/zh_CN/index
+
 Indices and tables
 ==================
 
diff --git a/Documentation/translations/zh_CN/CodingStyle b/Documentation/translations/zh_CN/coding-style.rst
similarity index 100%
rename from Documentation/translations/zh_CN/CodingStyle
rename to Documentation/translations/zh_CN/coding-style.rst
diff --git a/Documentation/translations/zh_CN/index.rst b/Documentation/translations/zh_CN/index.rst
new file mode 100644
index 0000000..75956d6
--- /dev/null
+++ b/Documentation/translations/zh_CN/index.rst
@@ -0,0 +1,12 @@
+.. raw:: latex
+
+	\renewcommand\thesection*
+	\renewcommand\thesubsection*
+
+Chinese translations
+====================
+
+.. toctree::
+   :maxdepth: 1
+
+   coding-style
-- 
2.9.3

  parent reply	other threads:[~2017-01-25  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  4:14 [PATCH v2 1/3] zh_CN/CodingStyle: improve translation Andy Deng
2017-01-25  4:14 ` [PATCH v2 2/3] zh_CN/CodingStyle: Convert to ReST markup Andy Deng
2017-01-25  4:14 ` Andy Deng [this message]
2017-01-26 22:40 ` [PATCH v2 1/3] zh_CN/CodingStyle: improve translation Jonathan Corbet
2017-01-27  2:28   ` Andy Deng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170125041433.9713-3-theandy.deng@gmail.com \
    --to=theandy.deng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox