Community
Participate
Working Groups
Build Identifier: I20100313 Complex expressions are not displayed correctly in Bookmarks view Reproducible: Always Steps to Reproduce: 1.Open eclipse in english version by passing the argument -nl en. 2.Create a file in a path like ABC2/EFG1/XYZ english LMN/HLK where capital letters are Arabic characters and HLK is the file's Arabic name. 3.Create a bookmark in the file, Open the Bookmarks vew. Expected Resuts: The path of the file is correctly displayed. Actual Results. The path of the file is not correctly displayed.
Created attachment 163172 [details] Snapshot of the defect
>1.Open eclipse in english version by passing the argument -nl en. Tomer, I think at this point this is not supported since with this command line the TextProcessor isn't enabled. Bug 307307 discusses how to enable that scenario in the future, correct?
That is correct. If we are seeking the resolution of this issue using TextProcessor we should use something like this: -nl ar -dir ltr (or -nl he -dir ltr). Under those conditions (assuming TextProcessor is called in the code) we should see proper display of the text. However, I would strongly suggest to use new generation of TextProcessor for handling this issue. Please see bug 183164 for more details.
Basically it means to call: ComplExpProcessor.process(<string>, ComplExpProcessor.PATH); instead of calling: TextProcessor.process(<string>);
(In reply to comment #2) > >1.Open eclipse in english version by passing the argument -nl en. > Tomer, I think at this point this is not supported since with this command line > the TextProcessor isn't enabled. I too think that this is not a supported scenario. Having the new TextProcessor won't change that (or we'll have to suffer performance consequences across IDE). Unless the problem manifests in the BiDi locale, this looks like an invalid bug.
(In reply to comment #5) Thanks Oleg for the headsup.
I disagree with comment #5. Proper processing of Bidi data ONLY in Bidi locale is not a correct perception of actual user environment. Bidi data can be processed in any locale. Specifically, Israeli customers usually use English version of Eclipse running with default English locale. However, at the same time they expect to properly see Bidi data. I agree that processing of Bidi data with TextProcessor (and its successor) should be limited (in order not to affect users not interested in Bidi support). However, I disagree that the condition for this invocation should be locale. I proposed to have a new command line option to be used as a trigger to invoking Bidi support focused at end user originated data. For more details please see bug 307307
Just a couple of words to clarify the situation. The problem reported in this bug will occur in both English version of Eclipse (aka in non Bidi locale) and in Bidi version of Eclipse (aka in Bidi locale). To reproduce it we will have to use different data patterns in those two environment. However, it will occur in both. So, the main point is not under which condition TextProcessor (or its successor) should be called (which is still important subject but it is discussed in different bugs). Instead the point is that TextProcessor (or its successor) are NOT called in the discussed context.
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.
