From: Li Yang <leoli@freescale.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: torvalds@linux-foundation.org, gregkh@suse.de,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-kernel@zh-kernel.org
Subject: Re: [GIT PATCH] Update to Chinese documents
Date: Wed, 09 Jan 2008 18:41:06 +0800 [thread overview]
Message-ID: <1199875266.21597.16.camel@Gundam> (raw)
In-Reply-To: <20080108131823.GB23947@uranus.ravnborg.org>
On Tue, 2008-01-08 at 21:18 +0800, Sam Ravnborg wrote:
> On Tue, Jan 08, 2008 at 08:50:37PM +0800, Li Yang wrote:
> > Please pull from the doc branch at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/leo/chinese.git doc
> >
> > to receive the following updates to in-tree Chinese documents
> > and to add newly translated guideline documents.
>
> Hi Li Yang.
>
> In another thread we have discussed localized versions of Kconfig
> files facilitating po files.
> Will the community you represent here see any advantage in that and
> would be interested to contribute?
AFAIK, a guy here had started to translate the Kconfig directly.
Changing to use po file should be a better approach.
>
> What is generally seen as a showstopper is the amount of work needed
> to do the translation - and keeping it up-to-date.
Sure. The key is to have more participants to involve. The work can't
be done without a large contributor base.
>
> If lkml actually accept .po files in the kernel is not yet setteled
> but no matter I would like kconfig to be extended to support it.
More people will be interested to participate by accepting .po files in
the kernel.
- Leo
> For this work help is needed too.
> It is a pick-up of the Linux Kernel Translation project
> (http://tlktp.sourceforge.net/) where several kconfig patches exists.
>
> Sam
>
next prev parent reply other threads:[~2008-01-09 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 12:50 [GIT PATCH] Update to Chinese documents Li Yang
2008-01-08 13:18 ` Sam Ravnborg
2008-01-09 10:41 ` Li Yang [this message]
2008-01-09 11:54 ` Sam Ravnborg
2008-01-09 16:48 ` Bryan Wu
2008-01-14 6:39 ` WANG Cong
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=1199875266.21597.16.camel@Gundam \
--to=leoli@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
/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