Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 205215

Summary:

BIDI: Bad encoding of imported symptom contains Hebrew characters

Product:

z_Archived

Reporter:

jkubasta

Component:

TPTP.monitoring

Assignee:

Alex Nan <apnan>

Status:

CLOSED INVALID

QA Contact:

Severity:

normal

Priority:

Keywords:

plan

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Symptom definition before catalog export	none
Symptom definition after catalog export and import	none

Description jkubasta

2007-10-02 13:38:12 EDT

1. Create a symptom database by selecting File > New > Other > Profiling and Logging > Symptom Database 
2. Enter a string that contains Hebrew characters for Name field, and click Finish
3. In the opened editor select Details tab
4. Select Catalog Symptom name and click Add to create a new definition.
5. Enter a string that contains Hebrew characters for each field and press Ctrl-s to save it
6. Select the symptom database created and click File > Export > Profiling and Logging > Symptom database file to open the export wizard.
7. Click Next to open the Export Symptom Database File page and click finish
8. Now, Click File > Import > Profiling and Logging > Symptom Database File and click Next to open the import wizard. 
9. Select Local host, browse to the symptom database exported in step 7, enter strings for Folder and File fields, and click Finish.
10. Open the imported symptom in the details tab

Result: The Hebrew strings were entered before for the symptom catalog and definition are being corrupted.

Comment 1 Alex Nan

2007-10-03 17:00:21 EDT

Created attachment 79680 [details]
Symptom definition before catalog export

.

Comment 2 Alex Nan

2007-10-03 17:00:52 EDT

Created attachment 79681 [details]
Symptom definition after catalog export and import

Comment 3 Alex Nan

2007-10-03 17:02:28 EDT

As it can be observed in the attached screen captures, the problem is not reproducible with TPTP-4.4.0.3-200709191245. This problem was fixed in 4.2.1, returning...

Comment 4 Paul Slauenwhite

2007-12-19 07:59:28 EST

Please change the target to the 4.5 iteration when this Bugzilla was resolved.

Comment 5 jkubasta

2009-02-24 16:26:15 EST

closing