Re: [RFD] Documentation/HOWTO translated into Japanese

[IKEDA Munehiro <m-ikeda@ds.jp.nec.com>]

Jesper Juhl wrote:
>> - Character encoding is ISO-2022-JP, which is normally used for email
>>   using Japanese.
> 
> 
> I think there's consensus that documents in the kernel source should
> be either plain ASCII or UTF-8 (doesn't UTF-8 work for japanese?).

Oh really?
UTF-8 works even for Japanese.  Thank you and Jan for the suggestion.

> 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?
> 
> 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?
> 
> 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.

Yes, that's the point.

At least for Japanese, there is a great activity "JF" as Tsugikazu 
Shibata mentioned.  It is a separate project from the tree, and it often 
happens that some documentations are outdated.  If we could merge them, 
they could be kept up-to-date IMHO.
But, on the other hand, it is fact that kernel tar ball would bloat.

Your opinion above as "creating official space in kernel.org and putting 
pointer in Documentation" seems good for me.

Hmm...

--
IKEDA, Munehiro