Re: kconfig .po files in kernel tree? [Was: Documentation/HOWTO translated into Japanese]

From: Denis Vlasenko
Date: Mon Jun 11 2007 - 03:46:31 EST

On Monday 11 June 2007 02:56, Paul Mundt wrote:
> On Mon, Jun 11, 2007 at 01:59:00AM +0200, Denis Vlasenko wrote:
> > On Sunday 10 June 2007 20:58, Rene Herman wrote:
> > > All that stuff only serves to multiply the speed at which a fixed
> > > percentage of content obsoletes itself. When it's still new and
> > > shiny, sure, stuff will get translated but in no time at all it'll
> > > become a fragmented mess which nobody ever feels right about removing
> > > because that would be anti-social to all those poor non-english
> > > speaking kernel hackers out there.
> >
> > I agree. i18n efforts won't help one iota because people just have
> > to know English in order to participate in l-k development.
> That's a ridiculous statement. Non-native language abilities and
> technical competence have very little to do with each other. People have
> to understand the code and figure out what it is that they want to
> change. As long as this is done cleanly and the intent is obvious,
> language doesn't even factor in beyond the Signed-off-by tag. Explanation
> is necessary from time to time, but it really depends on the area in
> which someone is working. If it's a complicated and involved change, then
> of course it takes a bit more effort on both sides, but that doesn't
> invalidate the importance or necessity of the work.

Point me to one person who doesn't know English at all
and who has successfully participated in l-k devel.

I'm not saying that non-English should banned or something.
In Kconfig it can even make sense. A section on
where people can put translations is also a good idea.
I can still think that it is almost useless activity,
but who knows, maybe I'm wrong.

Just not Documentation/<lang>/* thing and no i18n of printks.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at