-
Bug
-
Resolution: Fixed
-
P4
-
1.1.3, 1.1.5
-
1.2beta4
-
generic, x86
-
generic, windows_95, windows_nt
-
Not verified
i
Name: joT67522 Date: 11/11/97
When using java.util.Locale.toString() method
on Korean Windows95, "KO" is returned as a country
ID for Korean.
I understand the right country ID for Korean is "KR".
I am now using JDK1.1.3.
Source***************
java.util.Locale locale=java.uti.Locale.getDefault();
System.out.println("The locale is" + locale.toString();
Output***************
>The locale is ko_KO
Is this a known bug with
JDK1.1.3. If so, please tell me when the fix is
available.
(Review ID: 19915)
======================================================================
A licensee has a similar problem :
"We are experiencing difficulties with JDK1.1.3 on a Korean WinNT4.0 machine.
The problem is with the locale.
For example: System.out.println(Locale.getDefault()); returns ko_KO.
All the documentation we have from Sun specifies ko_KR as being
the correct locale for Korean / Korea. This problem is affecting the naming
of our resource bundles.
If the same sample code is run on my English NT machine, I get the same
exact errors. If I change the locale (.setDefault(Locale.JAPANESE) and run this
on my English machine (or Korean machine), everything works fine."
-mick
==============================================================================
Name: joT67522 Date: 11/11/97
When using java.util.Locale.toString() method
on Korean Windows95, "KO" is returned as a country
ID for Korean.
I understand the right country ID for Korean is "KR".
I am now using JDK1.1.3.
Source***************
java.util.Locale locale=java.uti.Locale.getDefault();
System.out.println("The locale is" + locale.toString();
Output***************
>The locale is ko_KO
Is this a known bug with
JDK1.1.3. If so, please tell me when the fix is
available.
(Review ID: 19915)
======================================================================
A licensee has a similar problem :
"We are experiencing difficulties with JDK1.1.3 on a Korean WinNT4.0 machine.
The problem is with the locale.
For example: System.out.println(Locale.getDefault()); returns ko_KO.
All the documentation we have from Sun specifies ko_KR as being
the correct locale for Korean / Korea. This problem is affecting the naming
of our resource bundles.
If the same sample code is run on my English NT machine, I get the same
exact errors. If I change the locale (.setDefault(Locale.JAPANESE) and run this
on my English machine (or Korean machine), everything works fine."
-mick
==============================================================================
- duplicates
-
JDK-4209823 Locale.getDefault() returns with invalid country code "KO" in windows(korean)
- Closed