LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Li Yang <leoli@freescale.com>
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: Tue, 8 Jan 2008 14:18:23 +0100	[thread overview]
Message-ID: <20080108131823.GB23947@uranus.ravnborg.org> (raw)
In-Reply-To: <1199796637.6835.7.camel@Gundam>

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?

What is generally seen as a showstopper is the amount of work needed
to do the translation - and keeping it up-to-date.

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.
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

  reply	other threads:[~2008-01-08 13:18 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 [this message]
2008-01-09 10:41   ` Li Yang
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=20080108131823.GB23947@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kernel@zh-kernel.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;
as well as URLs for NNTP newsgroup(s).