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]

Message-Id: <20070611.013451.74739872.tshibata@ab.jp.nec.com>
Date:	Mon, 11 Jun 2007 01:34:51 +0900 (JST)
From:	Tsugikazu Shibata <tshibata@...jp.nec.com>
To:	gregkh@...e.de
Cc:	jesper.juhl@...il.com, linux-kernel@...r.kernel.org,
	m-ikeda@...jp.nec.com, tshibata@...jp.nec.com
Subject: Re: [RFD] Documentation/HOWTO translated into Japanese

On Sun, 10 Jun 2007 09:22:21 -0700, gregkh wrote:
> On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
> >  On 10/06/07, Tsugikazu Shibata <tshibata@...jp.nec.com> wrote:

> > > Actually, this is my first trial to post Japanese translated document
> > > and here are some points I decided ;
> > >
> > > - 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?).
> 
> Is it hard to convert it to UTF-8?

NO, it's easy.

iconv -f ISO-2022-JP -t UTF-8 <infile >outfile

We are usually using ISO-2022-JP for email exchange and if anyone
would comment on my document, this is better I believe.
For documentation purpose, I agree with UTF-8.

Thanks,
Tsugikazu Shibata
-
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/