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]
Message-ID: <12c511ca0706111038j37e188b6n2677b1789d14de23@mail.gmail.com>
Date:	Mon, 11 Jun 2007 10:38:10 -0700
From:	"Tony Luck" <tony.luck@...il.com>
To:	"Matt Mackall" <mpm@...enic.com>
Cc:	"Greg KH" <gregkh@...e.de>, "Matthias Schniedermeyer" <ms@...d.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: [RFD] Documentation/HOWTO translated into Japanese

> I'd rather have a single file, marked "Japanese" (in Japanese), that
> had pointers to current translations. These will always be at least as
> current as whatever we have in the tree, if not more so. Especially
> when someone is trying to figure out how to work based on the year-old
> kernel their embedded vendor gave them.

Knowing whether a translation is current or not would be useful ... perhaps
the translated files could include the GIT blob SHA1 of the version they
were translated from (and some human readable version string too :-)
This would allow someone reading the documentation to know whether
is really was current.  If it isn't, it provides an easy path to see what
changed in the source document since the translation was made. This
same diff should lighten the load for people maintaining the translation.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ