[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ae9f3fe4-65e3-4e37-a480-70d7ceea2ec5@linux.dev>
Date: Mon, 17 Feb 2025 10:02:30 +0800
From: Yanteng Si <si.yanteng@...ux.dev>
To: Dongliang Mu <mudongliangabcd@...il.com>
Cc: alexs@...nel.org, Yanteng Si <siyanteng@...ngson.cn>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] docs/zh_CN: add few request for Chinese translation
在 2/14/25 11:24 AM, Dongliang Mu 写道:
> On Thu, Feb 13, 2025 at 6:24 PM Yanteng Si <si.yanteng@...ux.dev> wrote:
>>
>> 在 2/13/25 1:42 PM, alexs@...nel.org 写道:
>>> From: Alex Shi <alexs@...nel.org>
>>>
>>> A good checked summit could save much time for linux-doc maintainer.
>>>
>>> Signed-off-by: Alex Shi <alexs@...nel.org>
>>> Cc: Yanteng Si <siyanteng@...ngson.cn>
>>> Cc: Jonathan Corbet <corbet@....net>
>>> Cc: linux-doc@...r.kernel.org
>>> Cc: linux-kernel@...r.kernel.org
>> Reviewed-by: Yanteng Si <si.yanteng@...ux.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?
> Good idea. I can help contribute. Our Translation Team has a simple
> one to guide team members in kernel document translation.
Good jobs, This is very helpful to me.
In fact, I already had a draft before New Year's Day.
The reason I didn't submit it was because, in practice,
I found many deficiencies. I'll try to submit it later this week.
Thanks,
Yanteng
Powered by blists - more mailing lists