linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongliang Mu <dzm91@hust.edu.cn>
To: Yan Zhu <zhuyan2015@qq.com>, Fan Wu <wufan@kernel.org>
Cc: alexs@kernel.org, si.yanteng@linux.dev, corbet@lwn.net,
	mic@digikod.net, skhan@linuxfoundation.org, gnoack@google.com,
	linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 09/10] docs/zh_CN: add LSM/ipe Chinese translation
Date: Mon, 26 Oct 2026 17:26:23 +0800	[thread overview]
Message-ID: <440378d6-d72c-4edd-9159-582df02b49e6@hust.edu.cn> (raw)
In-Reply-To: <tencent_EF8D392378BF3BBAB8583E67EDDDE51E950A@qq.com>


On 6/13/26 11:08 PM, Yan Zhu wrote:
> On 6/13/2026 10:54 AM, Fan Wu wrote:
>> On Fri, Jun 12, 2026 at 8:59 AM Yan Zhu <zhuyan2015@qq.com> wrote:
>>>
>>> Translate Documentation/admin-guide/LSM/ipe.rst into Chinese.
>>>
>>> Update the translation through commit d7ba853c0e47
>>> ("ipe: Update documentation for script enforcement")
>>>
>>> Assisted-by: Claude:deepseek-4-pro
>>> Signed-off-by: Yan Zhu <zhuyan2015@qq.com>
>>> ---
>>
>> Have you tried to refine the AI translation? IMO some are really bad 
>> translated.
>
> I have double-checked it several times and manually corrected the 
> formatting and the accuracy of the translation.


IMO, some translation seems like a draft version generated by AI and 
without any further refinement.

Dongliang Mu


>
>>
>> Also how does the doc translation project work? I do notice there is
>> another IPE design doc translation,
>> https://docs.kernel.org/next/translations/zh_CN/security/ipe.html
>> which has a wrong "original link".>
>> -Fan
>
> The documents in the "admin-guide" directory are intended for both 
> administrators and users, focusing on usage; the documents in the 
> "security" directory are targeted at developers, emphasizing design 
> and development.
>


  reply	other threads:[~2026-10-26  9:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1781105672.git.zhuyan2015@qq.com>
2026-06-12 15:58 ` [PATCH 01/10] docs/zh_CN: add LSM/index Chinese translation Yan Zhu
2026-06-12 15:58 ` [PATCH 02/10] docs/zh_CN: add LSM/apparmor " Yan Zhu
2026-06-12 15:58 ` [PATCH 03/10] docs/zh_CN: add LSM/LoadPin " Yan Zhu
2026-10-26  9:21   ` Dongliang Mu
2026-06-12 15:58 ` [PATCH 04/10] docs/zh_CN: add LSM/SELinux " Yan Zhu
2026-06-12 15:58 ` [PATCH 05/10] docs/zh_CN: add LSM/Smack " Yan Zhu
2026-06-12 15:58 ` [PATCH 06/10] docs/zh_CN: add LSM/tomoyo " Yan Zhu
2026-06-12 15:58 ` [PATCH 07/10] docs/zh_CN: add LSM/Yama " Yan Zhu
2026-06-12 15:58 ` [PATCH 08/10] docs/zh_CN: add LSM/SafeSetID " Yan Zhu
2026-06-12 15:58 ` [PATCH 09/10] docs/zh_CN: add LSM/ipe " Yan Zhu
2026-06-13  2:54   ` Fan Wu
2026-06-13 15:08     ` Yan Zhu
2026-10-26  9:26       ` Dongliang Mu [this message]
2026-07-06  4:41     ` Alex Shi
2026-10-23 15:38     ` Weijie Yuan
2026-06-12 15:58 ` [PATCH 10/10] docs/zh_CN: add LSM/landlock " Yan Zhu
2026-10-26 10:12   ` Dongliang Mu
2026-11-15 14:12     ` Yan Zhu
2026-06-12 16:03 ` [PATCH 03/10] docs/zh_CN: add LSM/LoadPin " Yan Zhu
2026-07-04 15:20 ` [PATCH 01/10] docs/zh_CN: add LSM/index " Weijie Yuan
2026-11-15 15:19 ` Yan Zhu
2026-11-15 15:19 ` [PATCH 02/10] docs/zh_CN: add LSM/apparmor " Yan Zhu
2026-11-15 15:19 ` [PATCH 03/10] docs/zh_CN: add LSM/LoadPin " Yan Zhu
2026-11-15 15:20 ` [PATCH 04/10] docs/zh_CN: add LSM/SELinux " Yan Zhu
2026-11-15 15:20 ` [PATCH 05/10] docs/zh_CN: add LSM/Smack " Yan Zhu
2026-11-15 15:20 ` [PATCH 06/10] docs/zh_CN: add LSM/tomoyo " Yan Zhu
2026-11-15 15:20 ` [PATCH 07/10] docs/zh_CN: add LSM/Yama " Yan Zhu
2026-11-15 15:20 ` [PATCH 08/10] docs/zh_CN: add LSM/SafeSetID " Yan Zhu
2026-11-15 15:20 ` [PATCH 09/10] docs/zh_CN: add LSM/ipe " Yan Zhu

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=440378d6-d72c-4edd-9159-582df02b49e6@hust.edu.cn \
    --to=dzm91@hust.edu.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gnoack@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=wufan@kernel.org \
    --cc=zhuyan2015@qq.com \
    /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;
as well as URLs for NNTP newsgroup(s).