> OK. The reason I ask is to try to rule things out. The environment has
> changed, the JDK hasn't, so maybe the environment needs more attention.
> I suspect your answer lies in the C library and its I18N support, not in
> the JDK. Have you tried other applications than the JDK, to see if their
> What has changed and what hasn't changed? Are you trying to use the same
> Java distribution in two different Linux environments, or different JDK
> distributions?
It's the same JDK on two different Linux distribution. CLE is based on
RedHat 6.0 and we are moving over to RedHat 6.1. CLE has so
Runtime in RedHat always have default local to be en_US.
We have tried setting LANG, LC_ALL, LC_CTYPE and etc. It doesn't seem
to affect the default locale. We try adding -Dfile.encoding. Doesn't
work either. Can any one with source access to JDK take a peek at how
default locale is dec
ct the the default converter. I wonder how the getDefault() method
is controled.
David Li
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e how hard would it be to port it to Linux?
David Li
Topware Technology
---
Subject: [ANNOUNCE] LaTTe Java Virtual Machine
Date: 18 Oct 1999 23:41:30 -0400
From: [EMAIL PROTECTED] (Prof. Soo-Mook Moon)
Organization: Seoul National University
Newsgroups: comp.compilers, comp.lang.java.machine
The LaT
