Bug 273832 - Bidi3.5: Arabic Data is not correctly manipulated when exporting an Arabic named UML model
Summary: Bidi3.5: Arabic Data is not correctly manipulated when exporting an Arabic na...
Status: NEW
Alias: None
Product: MDT.UML2
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: UML2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 160682
Blocks:
  Show dependency tree
 
Reported: 2009-04-27 09:22 EDT by Mai El-Sayad CLA
Modified: 2012-06-19 15:32 EDT (History)
8 users (show)

See Also:


Attachments
Project generated after exporting the model (12.41 KB, application/octet-stream)
2009-04-27 09:24 EDT, Mai El-Sayad CLA
no flags Details
Model used in this scenario (521 bytes, text/xml)
2009-04-27 09:25 EDT, Mai El-Sayad CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mai El-Sayad CLA 2009-04-27 09:22:21 EDT
Build ID: I20090424-1604

Steps To Reproduce:
1. Create a general Arabic named Project and create UML model with an Arabic name inside it.
Scenario:
2. Create an Arabic named EMF project and select the UML model file name in the .genmodel file and choose Generate All from the Generator menu 
3. Select the UML model file name in the .genmodel file and choose Export Model from the Generator menu
4. Select the modelName package and press process all and finish.

Expected Result:
A new UML Model is successfully exported

Actual Result:
The model is exported, but the files created all include errors. The Arabic names are displayed as question marks.



More information:
Find attached the model used in this scenario and the output project. Please check the Java files in this project.
Comment 1 Mai El-Sayad CLA 2009-04-27 09:24:40 EDT
Created attachment 133355 [details]
Project generated after exporting the model
Comment 2 Mai El-Sayad CLA 2009-04-27 09:25:48 EDT
Created attachment 133356 [details]
Model used in this scenario
Comment 3 Anthony Hunter CLA 2009-04-27 13:43:02 EDT
Resolution of BIDI defects are not in plan for Galileo. BIDI in text fields in
SWT applications are limited by issues in the base platform and there is no
plan to address these issues in Galileo.

Leaving open in case BIDI defects are looked at in a future release.
Comment 4 Mai El-Sayad CLA 2009-05-03 06:24:49 EDT
It is acceptable to defer fixing the defect as it is not in Galileo plans, however, we believe the severity should be left as "Major" (even if not resolved) as it reflects the degree of criticality from Bidi perspective, regardless of the resolution plan.