From: Yanteng Si <si.yanteng@linux.dev>
To: alexs@kernel.org
Cc: Yanteng Si <siyanteng@loongson.cn>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] docs/zh_CN: add few request for Chinese translation
Date: Thu, 13 Feb 2025 18:18:40 +0800 [thread overview]
Message-ID: <5d35c3f6-a52f-4e63-a972-50ee2898947e@linux.dev> (raw)
In-Reply-To: <20250213054222.21776-2-alexs@kernel.org>
在 2/13/25 1:42 PM, alexs@kernel.org 写道:
> From: Alex Shi <alexs@kernel.org>
>
> A good checked summit could save much time for linux-doc maintainer.
>
> Signed-off-by: Alex Shi <alexs@kernel.org>
> Cc: Yanteng Si <siyanteng@loongson.cn>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
Reviewed-by: Yanteng Si <si.yanteng@linux.dev>
> ---
> Documentation/translations/zh_CN/index.rst | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/index.rst b/Documentation/translations/zh_CN/index.rst
> index 7574e1673180..cc512ca54172 100644
> --- a/Documentation/translations/zh_CN/index.rst
> +++ b/Documentation/translations/zh_CN/index.rst
> @@ -26,7 +26,13 @@
> 顺便说下,中文文档也需要遵守内核编码风格,风格中中文和英文的主要不同就是中文
> 的字符标点占用两个英文字符宽度,所以,当英文要求不要超过每行100个字符时,
> 中文就不要超过50个字符。另外,也要注意'-','='等符号与相关标题的对齐。在将
> -补丁提交到社区之前,一定要进行必要的 ``checkpatch.pl`` 检查和编译测试。
> +补丁提交到社区之前,一定要进行必要的 ``checkpatch.pl`` 检查和编译测试,确保
> +在 ``make htmldocs/pdfdocs`` 中不增加新的告警,最后,安装检查你生成的
> +html/pdf 文件,确认它们看起来是正常的。
> +
> +提交之前请确认你的补丁可以正常提交到中文文档维护库:
> +https://git.kernel.org/pub/scm/linux/kernel/git/alexs/linux.git/
> +如果你的补丁依赖于其他人的补丁, 可以与其他人商量后由某一个人合并提交。
I think this requires a detailed tutorial. Otherwise, it
will increase the difficulty for beginners to get started.
How about removing it for now? I have a plan to write
a translation guidebook. What's your opinion?
Thanks,
Yanteng
>
> 与Linux 内核社区一起工作
> ------------------------
next prev parent reply other threads:[~2025-02-13 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 5:42 [PATCH 1/2] docs/zh_CN: add maintainer tree for Chinese doc pickup alexs
2025-02-13 5:42 ` [PATCH 2/2] docs/zh_CN: add few request for Chinese translation alexs
2025-02-13 10:18 ` Yanteng Si [this message]
2025-02-14 1:59 ` Alex Shi
2025-02-14 3:24 ` Dongliang Mu
2025-02-14 4:33 ` Alex Shi
2025-02-14 10:18 ` Dongliang Mu
2025-02-14 15:50 ` Jonathan Corbet
2025-02-15 3:00 ` Dongliang Mu
2025-02-17 2:02 ` Yanteng Si
2025-02-17 3:24 ` Dongliang Mu
2025-02-13 10:12 ` [PATCH 1/2] docs/zh_CN: add maintainer tree for Chinese doc pickup Yanteng Si
2025-02-14 2:04 ` Alex Shi
2025-02-18 20:38 ` Jonathan Corbet
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=5d35c3f6-a52f-4e63-a972-50ee2898947e@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.