Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 163676 - BiDi1.0: Arabic characters are not well shaped
Summary: BiDi1.0: Arabic characters are not well shaped
Status: RESOLVED DUPLICATE of bug 163677
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Karice McIntyre CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-07 11:11 EST by Janis Steinfeld CLA
Modified: 2006-11-08 11:08 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janis Steinfeld CLA 2006-11-07 11:11:04 EST
When Writing Arabic characters in  button labels, it was found that these characters are not well shaped.

Build date: 03/10/2006
OS: RHEL 4.0

Steps to recreate the problem

Step 1: Create a simple project.
Step 2: Go to “Import” -> “General” -> “File System”

Step 3: Import these files:  "image1.jpg", "image2.gif", and "test.xml"    
Step 4: Select “test.xml” file in Navigator view. 
Step 5: Open context menu and select “Open with”->”Welcomepage Editor”
Step 6: Go to “Window”->”Show View”->”Others…”
Step 7: Open “Basic” category and select “Properties”. Then press OK button
Step 8: Select a button in the test file.
Step 9: Insert any Arabic text into the Label field of Properties view.

Expected Output: 

The Arabic labels should be displayed correctly, it should be well shaped, well ordered

Actual Output:

The Arabic labels aren't well shaped. The Arabic label in the "Green circle" represents the well shaped data that should be displayed.

N.B
When verifying this defect on English (USA) locale, it was found that all button labels are correctly displayed 

when switching back to Arabic (Egypt) locale, all button labels are again correctly displayed
Comment 1 Karice McIntyre CLA 2006-11-08 11:08:44 EST

*** This bug has been marked as a duplicate of 163677 ***