Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4459099
Votes 1
Synopsis J2RE can't run on Windows 2000 Hindi locale
Category java:classes_util
Reported Against 1.3 , merlin-beta , merlin-beta2
Release Fixed 1.4.2(mantis)
State 10-Fix Delivered, Verified, bug
Priority: 2-High
Related Bugs 4308929 , 4371865 , 4430838 , 4486077 , 4492682 , 4667175
Submit Date 15-MAY-2001
Description
Fixed GetStringPlarform in jni_util.c.
Fixed NewPlatformString in java.c

Notes:

1) We have fixed jre-intrinsic problems with Hindi.
   A remaining issue is, that some applications and
   demos use default-encoding versions of Readers/Writers
   when reading ASCI Files. For Hindi, the default encoding
   is utf-16le, which is not an 8-bit superset of ASCI. Therefore,
   if an applications read an ASCI text file using default-encoding
   version of FileReader, this application will fail on Hindi-locale.
   To remedy this, one needs to explicitely specify encoding (i.e. Cp1252)
   in all reader/writer constructors dealing with ASCI files.

2) javac works fine with hindi encoding, to compile asci files use
   javac -encoding Cp1252 some_asci_file.java

3) appletviewer fails, when reading ASCI html files on Hindi, EVEN IF
   -encoding is Cp1252. This is a bug which will be filed against 
   appletviewer. For now, use 
   appletviewer -J-Dfile.encoding=Cp1252 example.html to use appletviewer
   with ASCI html files.

4) Some java demo applications (SwingSet2) fail. There will be bug filed
   for this. For now use
   java -Dfile.encoding=Cp1252 to use failing demo applications (and any other           failing applications) on Hindi locale.
On a Win 2000, with Hindi enabled as default locale, installed Merlin b64, run Font2DTest, the following exception is thrown (this is mark copy/paste from dos promp window), same with other demo programs.

J:\\jdk1.4\\demo\\jfc\\Font2DTest>java -jar Font2DTest.jar\par
Exception in thread "main" j a v a . l a n g . E x c e p t i o n I n I n i t i a\par
 l i z e r E r r o r\par
 C a u s e d   b y :   j a v a . l a n g . N u l l P o i n t e r E x c e p t i o\par
 n\par
         a t   j a v a . i o . W i n 3 2 F i l e S y s t e m . n o r m a l i z e\par
 ( U n k n o w n   S o u r c e )\par
         a t   j a v a . i o . W i n 3 2 F i l e S y s t e m . g e t U s e r P a\par
 t h ( U n k n o w n   S o u r c e )\par
         a t   j a v a . i o . W i n 3 2 F i l e S y s t e m . r e s o l v e ( U\par
 n k n o w n   S o u r c e )\par
         a t   j a v a . i o . F i l e . g e t C a n o n i c a l P a t h ( U n k\par
 n o w n   S o u r c e )\par
         a t   j a v a . l a n g . C l a s s L o a d e r . l o a d L i b r a r y\par
 0 ( U n k n o w n   S o u r c e )\par
         a t   j a v a . l a n g . C l a s s L o a d e r . l o a d L i b r a r y\par
 ( U n k n o w n   S o u r c e )\par
         a t   j a v a . l a n g . R u n t i m e . l o a d L i b r a r y 0 ( U n\par
 k n o w n   S o u r c e )\par
         a t   j a v a . l a n g . S y s t e m . l o a d L i b r a r y ( U n k n\par
 o w n   S o u r c e )\par
         a t   s u n . s e c u r i t y . a c t i o n . L o a d L i b r a r y A c\par
 t i o n . r u n ( U n k n o w n   S o u r c e )\par
         a t   j a v a . s e c u r i t y . A c c e s s C o n t r o l l e r . d o\par
 P r i v i l e g e d ( N a t i v e   M e t h o d )\par
         a t   j a v a . u t i l . z i p . Z i p F i l e . < c l i n i t > ( U n\par
 k n o w n   S o u r c e )\par
\par

When doing "java -version", this is what displayed:

J:\\jdk1.4\\demo\\jfc\\Font2DTest>java -version\par
  a v a   v e r s i o n   " 1 . 4 . 0 - b e t a "\par
 J a v a ( T M )   2   R u n t i m e   E n v i r o n m e n t ,   S t a n d a r d\par
   E d i t i o n   ( b u i l d   1 . 4 . 0 - b e t a - b 6 4 )\par
 n u l l   ( b u i l d   n u l l ,   m i x e d   m o d e )\par
\par
Work Around
N/A
Evaluation
To be fixed.


 xxxxx@xxxxx  2001-07-27
Looks like the  FIX does not work, now the error messages is

java -jar Java2Demo.jar

Error occurred during initialization of VM
java.lang.Error: Can't fond java.home ??

The above message shows when doing java -version, for build 73 on Win2000 Hindi locale. Is the fixed integrated in build 73?
 xxxxx@xxxxx  2001-07-30

the fix is not in build 73, it will appear in  b74.  -- Konstantin

With b74, here is what I had, on a Hinde enabled Win2000:
J:\>which java
j:\jdk1.4\bin/java.exe

J:\>java -version
  a v a   v e r s i o n   " 1 . 4 . 0 - b e t a _ r e f r e s h "
 J a v a ( T M )   2   R u n t i m e   E n v i r o n m e n t ,   S t a n d a r d   E d i t i o n   (
 b u i l d   1 . 4 . 0 - b e t a _ r e f r e s h - b 7 4 )
 J a v a   H o t S p o t ( T M )   C l i e n t   V M   ( b u i l d   1 . 4 . 0 - b e t a _ r e f r e
 s h - b 7 4 ,   m i x e d   m o d e )

J:\jdk1.4\demo\jfc>cd Font2DTest

J:\jdk1.4\demo\jfc\Font2DTest>java -jar Font2DTest.jar
Exception in thread "main" j a v a . u t i l . z i p . Z i p E x c e p t i o n :   T h e   f i l e n
 a m e ,   d i r e c t o r y   n a m e ,   o r   v o l u m e   l a b e l   s y n t a x   i s   i n c
 o r r e c t
         a t   j a v a . u t i l . z i p . Z i p F i l e . o p e n ( N a t i v e   M e t h o d )
         a t   j a v a . u t i l . z i p . Z i p F i l e . < i n i t > ( Z i p F i l e . j a v a : 1
 1 5 )
         a t   j a v a . u t i l . j a r . J a r F i l e . < i n i t > ( J a r F i l e . j a v a : 1
 2 5 )
         a t   j a v a . u t i l . j a r . J a r F i l e . < i n i t > ( J a r F i l e . j a v a : 5
 9 )

The behavior is different, not fixed.
 xxxxx@xxxxx  2001-08-02

Verified in Merlin b75, Win2000, with workaround suggested 
	- appletviewer -J-Dfile.encoding=Cp1252 example.html
	- java -Dfile.encoding=Cp1252 -jar xxxx.jar
it worked.
 xxxxx@xxxxx  2001-08-13

I should add here, for Merlin release it should work without the above workaround, after all, Hindi support is one of Merlin Group driver feature.
Without fixing the above, nearly nothing works without workaround, which is very inconvenient for users.
 xxxxx@xxxxx  2001-08-13

Reopen the bug for real fix ...
 xxxxx@xxxxx  2002-10-29

================================================

Verified with Mantis b08, fixed!

 xxxxx@xxxxx  2002-11-21
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang