Date: Thu, 14 Jan 1999 20:27:53 +0900 From: SHUDO Kazuyuki <shudoh@muraoka.info.waseda.ac.jp> To: freebsd-java@FreeBSD.ORG Subject: Re: About Japanese problem with Swing. Message-ID: <199901141127.UAA03328@cafe.muraoka.info.waseda.ac.jp> In-Reply-To: Your message of "Thu, 31 Dec 1998 23:39:44 JST." <19981231233944V.daichi@ongs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > the environment values: > > LANG=ja_JP.EUC > > The information "file.encoding=8859_1" is bad. > > That should be "file.encoding=EUC_JP". > I think so. A default value of property `file.encoding' > should follow locale of the system. > > Who should deal with this problem? > > Maybe the best is working of Sun. Now I don't think so. Porting team should make JDK recognize locale name which is depend on each platform. On SunOS 5, `ja' and `japanese' are only locale names for Japanese. JDK for SunOS 5 supports these two locale names, but JDK for FreeBSD should recognize locale names on FreeBSD such as `ja_JP.EUC'. A file.encoding property have to be `EUC_JP' if locale name (LANG) represents Japanese(ja) as language and EUC as encoding. I've not get souce code of JDK 1.2, but guess that JDK 1.2 for SunOS 5 recognize only `ja' and `japanese' as locale name. I'll wait issue of new and more liberal source code license. Note that encoding name `EUC' (extended unix code) don't specify language. There are several EUCes, for Japanese, Chinese, Korean and Taiwanese. Kazuyuki SHUDO Happy Hacking! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901141127.UAA03328>