From: Li Zefan <lizf@cn.fujitsu.com>
To: jiaweiwei.xiyou@gmail.com
Cc: greg@kroah.com, linux-kernel@vger.kernel.org,
kongjianjun@gmail.com, joe@perches.com, rdunlap@xenotime.net,
harryxiyou@gamil.com
Subject: Re: [Patch Resend]Fix the messy code file Documentation/zh_CN/SubmitChecklist
Date: Sat, 16 Jul 2011 17:26:53 +0800 [thread overview]
Message-ID: <4E21595D.2040309@cn.fujitsu.com> (raw)
In-Reply-To: <20110716083618.GA4941@gmail.com>
16:36, Harry Wei wrote:
> From: Harry Wei <harryxiyou@gmail.com>
>
> So sorry with a mistake, which i did not check my patch with
> ./checkpatch.pl. This one is all well for checkpatch.pl. It
> can fix the messy code file Documentation/zh_CN/SubmitChecklist correctly.
>
I'm not fond of kernel documentation translation.. but after a quick
look, I don't think the quality of this translation is satisfying..
I'm not going to review the whole doc, just a few comments below.
> Signed-off-by: Harry Wei <harryxiyou@gmail.com>
> ---
> Documentation/zh_CN/SubmitChecklist | 118 +++++++++++++++++-----------------
> 1 files changed, 59 insertions(+), 59 deletions(-)
>
> diff --git a/Documentation/zh_CN/SubmitChecklist b/Documentation/zh_CN/SubmitChecklist
> index 951415b..7f41713 100644
> --- a/Documentation/zh_CN/SubmitChecklist
> +++ b/Documentation/zh_CN/SubmitChecklist
> @@ -8,102 +8,102 @@ or if there is a problem with the translation.
>
> Chinese maintainer: Harry Wei <harryxiyou@gmail.com>
> ---------------------------------------------------------------------
> -Documentation/SubmitChecklist ?????ķ???
> +Documentation/SubmitChecklist 的中文翻译
>
> -?????????ۻ????±??ĵ????ݣ???ֱ??�ϵԭ?ĵ???ά???ߡ???????ʹ??Ӣ??
> -??????�?ѵĻ???Ҳ?????????İ?ά?????????????�?????²???ʱ???߷?
> -?????????⣬??�ϵ???İ?ά???ߡ?
> +如果想评论或更新本文的内容,请直接联系原文档的维护者。如果你使用英文
> +交流有困难的话,也可以向中文版维护者求助。如果本翻译更新不及时或者翻
> +译存在问题,请联系中文版维护者。
>
> -???İ?ά???ߣ? ?????? Harry Wei <harryxiyou@gmail.com>
> -???İ淭???ߣ? ?????? Harry Wei <harryxiyou@gmail.com>
> -???İ?У???ߣ? ?????? Harry Wei <harryxiyou@gmail.com>
> +中文版维护者: 贾威威 Harry Wei <harryxiyou@gmail.com>
> +中文版翻译者: 贾威威 Harry Wei <harryxiyou@gmail.com>
> +中文版校译者: 贾威威 Harry Wei <harryxiyou@gmail.com>
I don't think you can be the reviewer as well as the translator.
>
>
> -????Ϊ????
> +以下为正文
> ---------------------------------------------------------------------
> -Linux?ں??ύ?嵥
> +Linux内核提交清单
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> -??????һЩ?ں˿?????Ӧ?????Ļ??????飬?????????뿴???Լ????ں˲????ύ
> -?????ܵĸ??졣
> +这里有一些内核开发者应该做的基本事情,如果他们想看到自己的内核补丁提交
> +被接受的更快。
You're a bit rigid in translation. I believe this should be better:
如果他们想看到自己提交的内核补丁被接受的更快。
[snip]
>
> -15?????е?codepaths?Ѿ???ʹ????lockdep???ù??ܡ?
> +15:所有的codepaths已经行使所有lockdep启用功能。
I suspect you don't really understand the original sentence, because
the translated text isn't understandable at all.
"在打开lockdep功能的情况下,所有的代码路径都被运行过。"
>
[snip]
next prev parent reply other threads:[~2011-07-16 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 7:43 [Patch Resend]Fix the messy code file Documentation/zh_CN/SubmitChecklist Harry Wei
2011-07-16 8:36 ` Harry Wei
2011-07-16 9:26 ` Li Zefan [this message]
2011-07-16 9:56 ` Harry Wei
-- strict thread matches above, loose matches on Subject: below --
2011-07-10 2:00 Harry Wei
2011-07-11 1:59 ` Amos Kong
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=4E21595D.2040309@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=greg@kroah.com \
--cc=harryxiyou@gamil.com \
--cc=jiaweiwei.xiyou@gmail.com \
--cc=joe@perches.com \
--cc=kongjianjun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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