Bug 877242 - Some characters can't be searched for in "project-wide search and replace"
Summary: Some characters can't be searched for in "project-wide search and replace"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: 2.0
Hardware: Unspecified
OS: Linux
high
medium
Target Milestone: ---
: 2.0
Assignee: David Mason
QA Contact: Patrick Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-16 02:34 UTC by Sam Friedmann
Modified: 2013-02-26 03:46 UTC (History)
3 users (show)

Fixed In Version: 2.0.3-SNAPSHOT (20121127-0017)
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-26 03:46:20 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 879099 0 high CLOSED Project-wide search does not show results for matching substring 2021-02-22 00:41:40 UTC

Internal Links: 879099

Description Sam Friedmann 2012-11-16 02:34:33 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121025 Firefox/10.0.10
Build Identifier: 

Certain characters in "project-wide search and replace" are not found whereas they are found with a normal search (within a file).
Eg: On a document update, I was trying to replace normal spaces preceding colons by nonbreaking spaces, as some of the colons would end up on they next line when the document was built.
I first searched within a document and I was able to replace the spaces as I wanted.
When trying this on project-wide search and replace, it did not detect them, so I searched for colons only, but it didn't detect any as well.

Reproducible: Always

Steps to Reproduce:
1. Search for a space followed by a colon (or just a colon) in project-wide search and replace.
2. Search for a space followed by a colon (or just a colon) in a file's search box.
3.
Actual Results:  
In project-wide search and replace, there are no results found.
In a file's search box, there are some results.

Comment 1 Sean Flanigan 2012-11-19 01:28:16 UTC
Switching to the HQL implementation (rather than Hibernate Search) should fix this.

Comment 2 David Mason 2012-11-23 08:39:56 UTC
Changed to HQL use in 2.0.3-SNAPSHOT and 2.1-SNAPSHOT

See: https://github.com/zanata/zanata/commit/1a6d8aae03c2e8856d3864e628320caba1aab64b

Comment 4 Patrick Huang 2012-11-27 03:29:58 UTC
verified in Zanata version 2.1-SNAPSHOT (20121127-1134) and Zanata version 2.0.3-SNAPSHOT (20121127-0017).


Note You need to log in before you can comment on or make changes to this bug.