From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: greg@kroah.com, kongjianjun@gmail.com,
linux-kernel@vger.kernel.org, joe@perches.com,
rdunlap@xenotime.net, harryxiyou@gmail.com
Subject: Re: [Patch Resend]Fix the messy code file Documentation/zh_CN/SubmitChecklist
Date: Sat, 16 Jul 2011 17:56:57 +0800 [thread overview]
Message-ID: <20110716095655.GA5073@gmail.com> (raw)
In-Reply-To: <4E21595D.2040309@cn.fujitsu.com>
On Sat, Jul 16, 2011 at 05:26:53PM +0800, Li Zefan wrote:
> 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..
This translation is a little worse, but we can proofread it again and again til well.
You can not expect anything to be perfect in the first time.
>
> 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.
I will try my best.
>
> >
> >
> > -??????????
> > +???????????????
> > ---------------------------------------------------------------------
> > -Linux????????????
> > +Linux??????????????????
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > -??????????????????????????????????????????????????????????????????????
> > -??????????????
> > +?????????????????????????????????????????????????????????????????????????????????????????????????????????
> > +?????????????????????
>
> You're a bit rigid in translation. I believe this should be better:
True, i will change my translation to yours.
>
> ?????????????????????????????????????????????????????????????????????
>
> [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.
Okay, i will proofread it with others who are all kernel lovers by
linux-kernel@zh-kernel.org. The translation of this document is only
translated and proofread by me so there are some improper portions.
Now i prepare to proofread it again til okay.
Thanks for your correction, i will try my best to translate
documentations correctly.
Comments?
>
> "?????????lockdep????????????????????????????????????????????????????????????"
>
> >
> [snip]
next prev parent reply other threads:[~2011-07-16 9:57 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
2011-07-16 9:56 ` Harry Wei [this message]
-- 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=20110716095655.GA5073@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=greg@kroah.com \
--cc=harryxiyou@gmail.com \
--cc=joe@perches.com \
--cc=kongjianjun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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