PUBLIC COMMENTS
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.
|
EVALUATION
To be fixed.
xueming.shen@Eng 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?
minchi.tien@eng 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.
minchi.tien@eng 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.
###@###.### 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.
###@###.### 2001-08-13
Reopen the bug for real fix ...
###@###.### 2002-10-29
================================================
Verified with Mantis b08, fixed!
###@###.### 2002-11-21
|
Java