Community
Participate
Working Groups
Build ID: I20071213-1700 Steps To Reproduce: A globalization tester for my product discovered this issue when using part of my UI that uses the WorkspaceResourceDialog from EMF. Here are the steps provided by the tester. I've removed the parts that are specific to my product. At step #2, the WorkspaceResourceDialog is open. This is Bidi specific defect, in the test case upper English letters represent Hebrew letters. 1. Create directory with Hebrew name AB and subdirectory with Hebrew Name TTT under directory AB (AB and TTT are Hebrew characters) 2. Select "New folder" 3. Expand "Advanced" 4. Select "Variable" and then "New" 5. Define a new path variable, select a path to Hebrew subdirectory AB/TTT. OK. OK 6. Inspect "Resolved location" path in "New Folder" dialog Expected result: home/AB/TTT Actual result: home/TTT/AB Comment: Eclipse provides support for "static" complex expressions via new BiDI API in TextProcessor class (http://wiki.eclipse.org/index.php/New_Bidi_APIs) More information:
The issue is in org.eclipse.ui.dialog.NewFolderDialog.
You should test the NewFolderDialog in 3.4 ... there was a lot of work to support BiDi on linux. PW
as per 2009 triage guidelines
This behavior still happens, I am using TPTP all in one download (4.7.0M6)
Created attachment 163519 [details] Screenshot highlighting the path wrong display on Windows7
(In reply to comment #4) > This behavior still happens, I am using TPTP all in one download (4.7.0M6) I forgot to say that this was reported on both Windows7 and Redhat Enterprise Linux (5.3)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
