Community
Participate
Working Groups
Build ID: version 3.2.0 Steps To Reproduce: Note: Treat Caps Lock latin letters as BiDi (Hebrew/Arabic) letters. 1. Access the source code for the Eclipse Web Tools Platform from the Concurrent Versions System (CVS) repository. To access the CVS repository select Window -> Open Perspective -> Other and select CVS Repository Exploring. 2. The CVS Repositories view is now on the left side of your screen. Select the Add CVS Repository icon and in the Add CVS repository dialog enter the following values: Host: dev.eclipse.org Repository Path: abcABC\DEF Expected Res : abcABC\DEF Actual Ressult : abcDEF\ABC 3. Click the Finish button. we can see the complex expression is not presented as the Exp, in the "Unable To Validate" Msg Box. More information:
Created attachment 60984 [details] The attachment describe the defect by encircling the problem with Red rectangles. Here, i attach the screen shot which describe the defect.
Hello, sorry for the changes.
Changing the severity to match to BiDi criteria
Add Tod to the bug.
Here's a FAQ by Tod on Bidi support n Eclipse: http://todcreaseyeclipse.blogspot.com/2007/03/bidirectional-support-faq.html It's not clear from the information you provided whether you used -rtl or -nl. Please retest using the setup described in the link above and reopen if the problem persists.
(In reply to comment #0) > Build ID: version 3.2.0 > > Steps To Reproduce: > Note: Treat Caps Lock latin letters as BiDi (Hebrew/Arabic) letters. > > 1. Access the source code for the Eclipse Web Tools Platform from the > Concurrent Versions System (CVS) repository. To access the CVS repository > select Window -> Open Perspective -> Other and select CVS Repository Exploring. > > 2. The CVS Repositories view is now on the left side of your screen. Select the > Add CVS Repository icon and in the Add CVS repository dialog enter the > following values: > Host: dev.eclipse.org > Repository Path: abcABC\DEF > > 3. Click the Finish button. we can see the complex expression is not presented > as the Exp, in the "Unable To Validate" Msg Box. > Expected Res : abcABC\DEF > Actual Ressult : abcDEF\ABC > > > > > More information: >
Created attachment 62060 [details] Adding an Image which describe the problem.
(In reply to comment #5) > Here's a FAQ by Tod on Bidi support n Eclipse: > > http://todcreaseyeclipse.blogspot.com/2007/03/bidirectional-support-faq.html > > It's not clear from the information you provided whether you used -rtl or -nl. > Please retest using the setup described in the link above and reopen if the > problem persists. > Hello Tod. In this bug description you should run eclipse as usuall with no Flag. I've added an attachment which you can see the problem. In bug #177316 you should run with -dir rtl. Thanks.
If you run without any flags set you get no BIDI support - you must run with the -nl flag.
(In reply to comment #9) > If you run without any flags set you get no BIDI support - you must run with > the -nl flag. This test case is not run when using mirrored gui. I'm using neither -dir rtl, neither -nl iw flags.
Tod, What you say in general is not entirely correct: >If you run without any flags set you get no BIDI support - you must run >with the -nl flag. TextProcessor is invoked when default locale is set to Arabic / Hebrew. If you set your default locale on OS level to Arabic / Hebrew and run Eclipse without any command line arguments (e.g. -dir rtl or -nl iw etc.) you will have IDE in LTR mode but TextProcessor will be still invoked. Look for example at dialog for creating a new General project (New->General->Project), the location field (assuming workspace includes BiDi subfolders) shows correct path.
Ok so you are running with the Hebrew locale. In the Hebrew locale with no command lines you will get textprocessing but not rtl switching. Are there any plans for this in 3.3?
This is really the same issue as bug 182713. I think the error is clear enough for the user to understand (especially considering that the paths appear the same in both places) so I do not think we need to address this in 3.3.
THis is far from being the same issue as in bug 182713. bug 182713 is about general G11N issue, while this defect is about BiDI specific issue. To resolve this defect you should use BiDi API. To resolve bug 182713 using BiDi API will not help.
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.
