OK, the issue is coming from the staff client. Sometimes (especially when there is a second space) a nonbreaking space chr(160) is getting encoded which is kind of rude of it.
New patch, again lightly tested but worked with a combination of regular and non-breaking spaces:
OK, the issue is coming from the staff client. Sometimes (especially when there is a second space) a nonbreaking space chr(160) is getting encoded which is kind of rude of it.
New patch, again lightly tested but worked with a combination of regular and non-breaking spaces:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=commit; h=fc598078a3dbf d981cd4fee29310 9408ce5b0653