Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 328866

Summary: Certain characters are not being parsed properly when performing a remote search.
Product: [Tools] Target Management Reporter: Ryan Weiss <ryanweis>
Component: RSEAssignee: David McKnight <dmcknigh>
Status: NEW --- QA Contact: Martin Oberhuber <mober.at+eclipse>
Severity: normal    
Priority: P3 CC: dmcknigh, ryanweis, samuelwu
Version: unspecified   
Target Milestone: 3.3.1   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Ryan Weiss CLA 2010-10-27 13:36:31 EDT
Build Identifier: RSE 3.2.2

The remote search is not displaying proper line result text when the line containing a search result contains certain characters.

Reproducible: Always

Steps to Reproduce:
1.Create a dstore connection to a linux server.
2.Create a folder and create a text file within the folder.
3.Open the text file in the editor and input the following three lines:
a
a¨ aaa
a¨

NOTE: The ¨ character is equivalent to unicode character 168 (0x00A8).
4. Save the text file.
5. Right-click on the folder in the RSE view and select "Search..." from the menu.
6. Select the Remote Search tab, and input "a" (no quotes) as the search term.
7. A result should be displayed in the Remote Search result view, expand it by clicking the plus icon.
8. The following three line results are displayed:
a
aaaa
a value=


No exceptions are thrown, however the results in the remote search view should correspond to the text input in step 3.  These characters are displayed correctly when the file is opened in an editor.  

Unicode character 168 is not the only character that causes this issue, it has also been observed using unicode character 196 and 191.
Comment 1 Martin Oberhuber CLA 2011-05-31 17:48:25 EDT
Bulk moving 3.3 deferred items to 3.3.1
Comment 2 Samuel Wu CLA 2012-05-30 11:47:02 EDT
Hi Dave,
Have you got a chance to look into this problem? Thanks.
Comment 3 David McKnight CLA 2012-05-31 11:43:03 EDT
Samuel, could you add the following option to the server script you use?
-DSTORE_SERVER_ENCODING=UTF-8