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:	Mon, 16 Jul 2007 01:46:42 +0900 (JST)
From:	Tsugikazu Shibata <tshibata@...jp.nec.com>
To:	rob@...dley.net
Cc:	LeoLi@...escale.com, gh@...ibm.com, hpa@...or.com,
	kunai@...ux-foundation.jp, holzheu@...ux.vnet.ibm.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	lf_kernel_messages@...ux-foundation.org, tshibata@...jp.nec.com
Subject: Re: Documentation of kernel messages (Summary)

On Sat, 14 Jul 2007 22:12:35 -0400, rob wrote:
> On Friday 13 July 2007 9:46:59 pm Tsugikazu Shibata wrote:
> > > > How about adding;
> > > > kernel-doc-nano-HOWTO.txt
> > >
> > > The problem is, the generated htmdocs are in english.  This file is about
> > > how to generate (and author) English documentation that won't be
> > > translated. What's the point of translating the instructions if the
> > > result won't be translated?
> >
> > People (who even in non-native) would better to know and read it such
> > htmldocs because there are good and important documents even in English.
> > I thought that translation of this file may help.
> 
> The english version of htmldocs is generated from the source code.    If 
> translating remotely current versions of htmldocs into other languages was 
> feasible, then the english version wouldn't need to be in the source code in 
> the first place.
> 
> Translating a document _about_ htmldocs boils down to "Dear non-english 
> speaker: here's something you can't read, nor can you update it either except 
> though your language maintainer."

No, kernel-doc-nano-HOWTO includes explanation of tools to extract the
document, format of extractable document in source files and so on.
I thought this file would help non-native people, how to extract or add
in-kernel extractable documents.
I understand that these tools will generate English documents but
that's OK. Such large volume of documents are not easy to translate
into other languages.

> 
> Rob
> -- 
> "One of my most productive days was throwing away 1000 lines of code."
>   - Ken Thompson.
> 
-
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