Bug 6135 - NLS WSDD problems in IDE and VM - Japanese project
Summary: NLS WSDD problems in IDE and VM - Japanese project
Status: CLOSED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 9330
Blocks:
  Show dependency tree
 
Reported: 2001-11-20 17:49 EST by OTI Support CLA
Modified: 2005-05-10 14:56 EDT (History)
1 user (show)

See Also:


Attachments
WSDD workspace containing testcase classes (251.42 KB, application/x-gzip)
2001-11-20 18:05 EST, OTI Support CLA
no flags Details
WSDD debugger screen capture of problem (380.48 KB, image/gif)
2001-11-20 18:06 EST, OTI Support CLA
no flags Details
WSDD IDE screen capture of problem (390.19 KB, image/gif)
2001-11-20 18:07 EST, OTI Support CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description OTI Support CLA 2001-11-20 17:49:55 EST
Eclipse cannot display Japanese letters in the Java Editor pane and console pane 
even if I change the font.  All Japanese letters are displayed as '?' letters. 
In other panes, like packages, outline, tasks, etc. looks OK.

Tested on Japanese Windows 2000.  The same test should be done on Windows XP, 
NT, ME, 98, and 95, but I didn't due to other tasks.

For the detail of each test case, see the comments in the source file.

-----------------------------------------------------------------
Test Case under Japanese project      IDE       J9 (command line)
-----------------------------------------------------------------
AsciiOnlyHelloWolrd                Exception     Exception
JapaneseStringHelloWorld           Exception     Exception
JapaneseMethodName                 Exception     Exception
ClassUser                          Exception     Exception
ยท   (A single Japanese character)  Exception     Exception
-----------------------------------------------------------------

Unhandled exception
Type=GPF vmState=0xffffffff
ExceptionCode=0xc0000005 ExceptionAddress=0x10019c78
ContextFlags=0x0001003f
Handler1=0x110014b0 Handler2=0x100254f0
Module=C:\Projects\VAME\FromOTI\WSDDTest\wsdd\ive\bin\J9VM15.dll
Module_base_address=0x10000000
Offset_in_DLL=0x00019c78
EDI=0x00000004 ESI=0x00000016 EAX=0x53ec8b41
EBX=0x10014300 ECX=0x90000000 EDX=0x0040dcd0
EBP=0x53ec8b41 ESP=0x0012f7a0 EIP=0x10019c78

Thread: main (priority 5) (LOCATION OF ERROR)

Thread: Gc Thread (priority 5) (daemon)
Comment 1 OTI Support CLA 2001-11-20 18:05:32 EST
Created attachment 130 [details]
WSDD workspace containing testcase classes
Comment 2 OTI Support CLA 2001-11-20 18:06:16 EST
Created attachment 131 [details]
WSDD debugger screen capture of problem
Comment 3 OTI Support CLA 2001-11-20 18:07:02 EST
Created attachment 132 [details]
WSDD IDE screen capture of problem
Comment 4 Kevin Haaland CLA 2001-11-20 22:40:53 EST
Pls double check the font used by the editor. It has it's own font setting 
dialog. 
Comment 5 OTI Support CLA 2002-01-17 11:18:20 EST
Received the following report from a customer:

As I installed the nls fragments, the menus are displayed In Japanese.
However, the Japanese strings in the Java Editor still are displayed as "?"
(question marks), though I specified Japanese Font.

My environnemt is

Japanese Windows 2000
WSDD 4.0 Beta Build 3.99.3 (Built on 2001-12-21)
Comment 6 Kevin Haaland CLA 2002-02-07 20:53:04 EST
Pls confirm that this defect has been resolved to everyones satisfaction. 
Comment 7 Tod Creasey CLA 2002-02-08 16:12:25 EST
The font problem is fixed after SWT switched to using the proper system fonts 
in 200201xx. However there is still a problem running Japanese packages - see 
Bug 9330
Comment 8 Nick Edgar CLA 2002-05-14 18:23:04 EDT
Tod, please verify the above bug 9330 and close PR if no longer an issue.
Comment 9 Tod Creasey CLA 2002-05-15 12:31:31 EDT
See Bug 9330. This is a VM issue.
Comment 10 Tod Creasey CLA 2002-08-06 14:06:57 EDT
Marking as fixed as we have done all that we can - the packages problem is a VM 
problem.
Comment 11 Tod Creasey CLA 2005-05-10 14:56:02 EDT
Marking closed