Bug 307161 - [search][BiDi] BIDI3.6_BDL: ComplexExpression-Bidi data displayed unreadable in Search view
Summary: [search][BiDi] BIDI3.6_BDL: ComplexExpression-Bidi data displayed unreadable ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 306751
Blocks:
  Show dependency tree
 
Reported: 2010-03-26 04:30 EDT by Dani Megert CLA
Modified: 2023-03-08 18:11 EST (History)
9 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2010-03-26 04:30:38 EDT
+++ This bug was initially created as a clone of Bug #306751 +++

Build Identifier: 3.6.0 - I20100313-1044

BIDI3.6_BDL: ComplexExpression-Bidi data displayed unreadable in Search view
1. Open Eclipse, create Java project and java class inside the project
2. Create Hebrew-named method which recieves two parameters of Hebrew-named type
3. Perform Search and make sure the method declaration line will be found
4. Examine the results
Result : Hebrew text became mixed with English (see screenshot)

Reproducible: Always
Comment 1 Eclipse Genie CLA 2019-03-26 14:36:10 EDT
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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2021-03-17 16:39:38 EDT
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.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-03-08 18:11:43 EST
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.

--
The automated Eclipse Genie.