Bug 18341

Summary: NO-BREAK SPACE is not counted as white space in search queries.
Product: Koha Reporter: Barton Chittenden <barton>
Component: SearchingAssignee: Galen Charlton <gmcharlt>
Status: CLOSED WORKSFORME QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: jpalmer
Version: Main   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Crowdfunding committed: 0
Crowdfunding contact: Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: CSV file containing titles separated by NO-BREAK SPACE

Description Barton Chittenden 2017-03-27 20:27:06 UTC
Created attachment 61648 [details]
CSV file containing titles separated by NO-BREAK SPACE

I've transcribed this from a ticket that one of our partners submitted. 

A librarian noted that she had an Excel spreadsheet of titles she was copying and pasting into Koha to search, and occasionally one of the titles wouldn't come up even though they have the book. ( CSV file containing titles is attached.)  She noted if she just typed the title into Koha, it came up w/o a problem.
Here's a screenshot of one of the failed searches.

Notice the %C2%A0  between the words. That's the UTF-8 code for non-breaking space (see http://www.fileformat.info/info/unicode/char/00a0/index.htm).

--

The underlying issue here is that when we paste in a search term containing the unicode NO-BREAK SPACE glyph, this arguably should be treated as white space, and the search should succeed if it matches strings with words separated by other whitespace characters.
Comment 1 Katrin Fischer 2023-09-10 21:04:16 UTC
I cannot replicate this with the CSV file provided.