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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070610221330.GG11166@waste.org>
Date:	Sun, 10 Jun 2007 17:13:30 -0500
From:	Matt Mackall <mpm@...enic.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Sam Ravnborg <sam@...nborg.org>, Greg KH <gregkh@...e.de>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Tsugikazu Shibata <tshibata@...jp.nec.com>,
	linux-kernel@...r.kernel.org, m-ikeda@...jp.nec.com
Subject: Re: kconfig .po files in kernel tree? [Was: Documentation/HOWTO translated into Japanese]

On Sun, Jun 10, 2007 at 08:35:03PM +0200, Jan Engelhardt wrote:
> 
> On Jun 10 2007 19:52, Sam Ravnborg wrote:
> >> >  Since the common language of most kernel contributors is english I
> >> >  personally feel that we should stick to just that one language in the
> >> >  tree and then perhaps keep translations on a website somewhere. So the
> >> >  authoritative docs stay in the tree, in english, so that as many
> >> >  contributors as possible can read and update them. It would then be a
> >> >  seperate project to generate translations and keep them updated
> >> >  according to what's in the tree.  Perhaps we could get the kernel.org
> >> >  people to create an official space for that and then place a pointer
> >> >  to that site in Documentation/ somewhere.
> >> 
> >> No, I think the translated files should be in the tree proper, we have
> >> the space :)
> >
> >We once discussed about .po files for kconfig and back then
> >the conclusion was not to keep them in the kernel tree.
> >
> >I advocated that they should stay out back then.
> >But on the other hand I do not see it causing much troubles
> >having scripts/kconfig/po/da.po etc araound.
> >
> >Any opinion about the .po files?
> 
> Like with translated doc, they might get out of date easily.

Well, if for each document you translate, you record what revision you
translated (git hash or kernel release), it's fairly easy to generate
diffs and know what changes need to be translated.

I don't think keeping the translations of Documentation/ in the kernel
tree eases this significantly though.

-- 
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/