Bug 184722 - [Implementation for] Display of File Path Complex Expression Containing BiDi Text
Summary: [Implementation for] Display of File Path Complex Expression Containing BiDi ...
Status: NEW
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: UI Guidelines (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ui.guidelines-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-30 11:57 EDT by Tomer Mahlin CLA
Modified: 2022-11-25 01:28 EST (History)
14 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomer Mahlin CLA 2007-04-30 11:57:18 EDT
This defect is a placeholder for discussion related to implementation of API resolving issue with display of File Type complex expression.

Problem overview
-----------------
  
 File path string should be rendered left-to-right and also has the Unicode Bidirectional algorithm applied to it in order to render the mixed text of the segment in the proper orientation. 
  As an example, a file path such as 

  d:\myFolder\FOLDER\MYFILE.java
(where capital letters indicate RTL-oriented text) should render as 

  d:\myFolder\REDLOF\ELIFYM.java

when using the Unicode Bidi algorithm and segmenting the string according to a specified delimiter set. 
  
  However, since the OS does not understand that the string should be segmented according to each segment of the file path, it renders the string as 

  java.ELIFYM\REDLOF\d:\myFolder


Approach overview
-----------------
 The design for File Path complex expression is available in bug 179191 dedicated to general complex expressions design discussion.

 Following the terminology defined in bug 183164 File Path type of complex expression belong to group 1 languages. This group includes languages which can be adequately parsed into tokens using oversimplified technique of parsing - tokenization based on list of separators. For File Path this list should include: colon (:), backslash (\) and full stop (.) for Windows, slash (/) and full stop (.) for Linux.


History of handling and related instances addressed in various components
-------------------------------------------------------------------------
  The cycle of handling File Path complex expression in Eclipse started from TVT defects back in December 2005. See bug 119517 for more details. 
 This defect was resolved via another bug 126402 in February 2006.
 The source code of TextProcessor which fixes this defect can be found 
here: https://bugs.eclipse.org/bugs/attachment.cgi?id=34133&action=view . 
 In May 2006 the implementation was improved via bug 139806. 
 Owner of implementation is Karice McIntyre.
 According to Karice McIntyre in bug 148966, comment 15 the originator of the code is Lina Kemmel.

History outlines
-----------------

   * bug 119517 - general description
   * bug 126402 - implementation
   * bug 139806 - improvement of implementation
   * bug 146220 - suggestion for gneralization of solution
   * bug 181961 - issue instance handled in BIRT
   * bug 181965 - issue instance handled in DTP
   * bug 179328 - issue instance handled in TPTP

Documentation
--------------

  The implementation (aka API) is described at this site:     
    http://wiki.eclipse.org/index.php/New_Bidi_APIs
Comment 1 Eclipse Genie CLA 2015-01-02 20:32:53 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.
Comment 2 Eclipse Genie CLA 2016-12-23 15:19:07 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.
Comment 3 Eclipse Genie CLA 2018-12-14 15:09:51 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.
Comment 4 Eclipse Genie CLA 2020-12-04 20:26:35 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.
Comment 5 Eclipse Genie CLA 2022-11-25 01:28:55 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.