Bug 77429 - Symptoms: DBCS: runOnServer.properties DBCS show error on Navigator
Summary: Symptoms: DBCS: runOnServer.properties DBCS show error on Navigator
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-11-01 17:04 EST by Terri Lafoon CLA
Modified: 2007-06-22 10:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Terri Lafoon CLA 2004-11-01 17:04:13 EST
Environment:
       CHT/JPN/ENG(Fail),CHS/KOR(NA)

Defect Description:
1. Open HATS studio.
2. Create one project and configure one 5250 display session(tai405.tw.ibm.com) 
with codepage is 1371.
3. Start Run On Server.(by HATS => Run On Server)
4. Pop-up Show Display termina and select "Yes".
5. Start Navigator verify the runOnServer.properties file.
   (by window -> show view -> Navigator)

<<ERROR>> 
The runOnServer.properties DBCS show error.
The DBCS show garbage characters.


<<Expected Result>>
The runOnServer.properties should show correct DBCS data.

    <Note by davelin (DAVE LIN), 2004/10/14 06:03:08, seq: 5 rel: 0  action: 
note>
The DBCS characters in .properties file should be local MS Windows encoding 
(SHIFT-JIS, BIG5, etc.), and the file is indeed local
encoding, the problem is RAD6 properties editor can't display local encoding 
files except ASCII encoding.


Defect Description:
1. Open RAD and new a Java Project.
3. New a file with extension .properties (test.properties)
4. Insert string which is non-ASCII, like Japanese or Chinese characters with 
native encoding.
5. Save the file, close it and reopen, the non-ASCII characters become question-
mark (?)
6. Edit the file with editor outside RAD, and insert non-ASCII characters with 
native encoding.
7. Go back to RAD, reolad the properties file, the non-ASCII characters become 
different and error characters.

<<ERROR>> 
The properties file can't insert/display non-ASCII(DBCS) native encoding 
characters correctly.
<<Expected Result>>
The properties should display/insert correct non-ASCII(DBCS) characters with 
native encoding.

From RAD development: 
what editor are you using to open the .properties file?  It looks like by 
default, the properties file editor is used.  If that is the editor you are 
using, this editor is contributed by Eclipse, so this defect should be opened 
on http://bugs.eclipse.org/bugs instead.
Comment 1 Dani Megert CLA 2004-11-02 03:34:14 EST
What encoding does the file have (select file in Navigator, File > Properties)?
You might have run into bug 57556.

We need more data. See also:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-text-home/development/bug-incomplete.htm
Comment 2 Anny Yu CLA 2004-11-16 05:03:57 EST
We create a project to run runOnServer function, open the 
runonserver.properties file, but show garbage code.
(By Window>Preference>Workbence>Editor, the Encoding is "Defect:MS950")

If change the Encoding to "Other:UTF-8" setting, it show still garbage code.

Code Version: RWD: 20041031_2232 / HATS V6.0: 20041110

Environment:  Windows2000/CHT
Comment 3 Dani Megert CLA 2004-11-16 05:22:00 EST
Sorry, I guess your case is bug 65571 and not bug 57556. Please also answer the
question from comment 2: "What encoding does the file have (select file in
Navigator, File > Properties)?".

Bug 65571 causes the file to be opened using "ISO-8859-1".
Comment 4 Anny Yu CLA 2004-12-05 22:46:17 EST
I check your method(select file in Navigator, File > Properties),
the file to be opened using "ISO-8859-1".
Comment 5 Dani Megert CLA 2007-06-22 09:59:15 EDT
Get rid of deprecated state.
Comment 6 Dani Megert CLA 2007-06-22 10:04:31 EDT
.