linux-kernel - Re: [RFD] 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 10 Jun 2007 14:29:45 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Jesper Juhl <jesper.juhl@...il.com>
cc:	Tsugikazu Shibata <tshibata@...jp.nec.com>,
	linux-kernel@...r.kernel.org, gregkh@...e.de, m-ikeda@...jp.nec.com
Subject: Re: [RFD] Documentation/HOWTO translated into Japanese


On Jun 10 2007 14:24, Jesper Juhl wrote:
>
> If we start adding translated versions of documentation to the kernel
> source how should we organize the documents? Should each language get
> a sepperate directory in Documentation/ - like Documentation/JP/,
> Documentation/EN/, Documentation/DA/ etc?

I'd prefer the 'standardized' "ja_JP", "en_US", "de_DE", "nb_NO", etc.
as names.

> With multiple translated versions of the documentation in the tree,
> don't we run the risk that the translations will quickly become
> outdated since most people updating the documentation won't be able to
> update the translations?

What's more, the kernel tarball grows and grows :(



	Jan
-- 
-
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/