LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org> To: WANG Cong <xiyou.wangcong@gmail.com> Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kbuild <linux-kbuild@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: Kbuild update Date: Sun, 6 Jan 2008 17:07:44 +0200 [thread overview] Message-ID: <20080106150744.GJ2082@does.not.exist> (raw) In-Reply-To: <20080106142606.GB2528@hacking> On Sun, Jan 06, 2008 at 10:26:06PM +0800, WANG Cong wrote: > > >> It sort of stopped at one point due to missing integration in mainline. > >> What I refer to is mostly the mconf.c bits, but I would also like to > >> see what lkml says to a sample of .po files included in the kernel > >> for a number of languages. > >> > >> One criteria to get a .po file integrated could be at least 10% of the > >> strings translated or similar. > > Well, I think it's worthy. The translation effort will be valuable > and much helpful for non-English-speaking peoples. > > >Besides the initial translation efforts a big problem would be to > >also find people who will regularly update the translations for > >many years. > > Yes, that's really a problem. But I think the updates won't be > too frequent, only update for stable release is enough. "only" is the wrong word in this context. If someone would update the translations for one language every 3 months for the next years that would be great and disprove my concerns. After all, updates every 3 months would beat the maintainance level of at least three of our architectures... And don't underestimate the amount of work required - even when talking about requiring "only" 10% of the help texts translated that's a four digit number of lines to translate. > If we can make this to be an offical project for Linux kernel, I > think it won't be a big problem. We don't even manage to maintain the English language texts properly, and I am therefore not overly optimistic that we'll have the translations maintained properly for many years. OTOH, if someone wouldn't just blindly translate the outdated English texts but also review the English texts when translating this alone might be worth it... > Regards. > > Cong cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-06 15:08 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-03 21:32 Kbuild update Sam Ravnborg 2008-01-03 21:46 ` Josh Boyer 2008-01-03 22:33 ` Jan Engelhardt 2008-01-04 19:43 ` Sam Ravnborg 2008-01-04 20:09 ` Jan Engelhardt 2008-01-04 13:23 ` WANG Cong 2008-01-04 14:39 ` Sam Ravnborg 2008-01-05 5:48 ` Adrian Bunk 2008-01-06 14:26 ` WANG Cong 2008-01-06 15:07 ` Adrian Bunk [this message] 2008-01-06 15:45 ` Sam Ravnborg 2008-01-09 2:32 ` WANG Cong 2008-01-09 5:18 ` Sam Ravnborg 2008-01-09 2:28 ` WANG Cong 2008-01-06 21:41 ` translations (Re: Kbuild update) Oleg Verych 2008-01-06 22:03 ` Sam Ravnborg 2008-01-09 2:22 ` WANG Cong 2008-01-09 13:50 ` Oleg Verych 2008-01-15 1:33 ` WANG Cong -- strict thread matches above, loose matches on Subject: below -- 2007-09-16 9:47 kbuild update Sam Ravnborg 2007-09-16 12:58 ` Robert P. J. Day 2007-09-16 15:13 ` Sam Ravnborg 2007-09-16 15:21 ` Robert P. J. Day 2007-09-16 19:23 ` Andrew Morton 2007-09-16 20:38 ` Sam Ravnborg 2007-06-03 20:36 Sam Ravnborg 2007-06-03 20:51 ` Sam Ravnborg
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=20080106150744.GJ2082@does.not.exist \ --to=bunk@kernel.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=sam@ravnborg.org \ --cc=xiyou.wangcong@gmail.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: linkBe 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).