APAR status
Closed as Permanent restriction.
Error description
Hebrew characters contained in a Microsoft Visio Diagram appear distorted (gibberish) when inserted as an OLE in DOORS. However, when the OLE is activated, which opens Microsoft Visio the Hebrew characters are displayed correctly. Steps to reproduce: ------------------------ 1.? Have a Microsoft Visio diagram file (.vsd) that contains Hebrew characters in it. 2.? Edit Object Text of a DOORS Module Object and insert the above mentioned (.vsd) file as an OLE. You would observe that the Hebrew characters appear distorted in DOORS. When the OLE is activated to be opened in Microsoft Visio application, the characters appear fine.
Local fix
Problem summary
Hebrew characters contained in a Microsoft Visio Diagram appear distorted (gibberish) when inserted as an OLE in DOORS. However, when the OLE is activated, which opens Microsoft Visio the Hebrew characters are displayed correctly. Steps to reproduce: ------------------------ 1.> Have a Microsoft Visio diagram file (.vsd) that contains Hebrew characters in it. 2.> Edit Object Text of a DOORS Module Object and insert the above mentioned (.vsd) file as an OLE. You would observe that the Hebrew characters appear distorted in DOORS. When the OLE is activated to be opened in Microsoft Visio application, the characters appear fine.
Problem conclusion
This APAR has been rejected. It is a limitation of the third party control used for this functionality. From the third party: The behavior you are seeing appears by design - the conversion from Unicode is not directly possible with the English default system locale. It?s been the case for many releases of Windows that in order for non-Unicode applications to display certain text correctly they would need the default locale changed: http://windows.microsoft.com/en-US/windows7/Change-the-system-lo cale I confirmed this by entering Russian text into PowerPoint then inserting the object into WordPad. With English as the default locale we see ??? with Russian selected we see the correct text. Unless we look to make an architectural change to Windows (not going to happen) I don?t see what more we can offer. I was hoping that there would be some developer guidelines in place with regards to the controls that you are trying to use and any alternatives you should be looking at. Unfortunately I was not able to find more on this.
Temporary fix
This APAR has been rejected
Comments
APAR Information
APAR number
PM71436
Reported component name
TLOGIC DOORS
Reported component ID
5724V61DR
Reported release
930
Status
CLOSED PRS
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-23
Closed date
2013-11-01
Last modified date
2013-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
01 May 2020