Chosen: Bug when searching non-ASCII languages
hi
I am using chosen 1.7.0 JQuery in my asp.net MVC project. It works perfect in English, but in my case when I use chosen in multi-select mode for Persian language the search text shows just last charterer instead of whole word. i have work around it and found the problem happens in line 394 , 395 of "chosen.jquery.js" when creating tag.
no difference whether using rtl option or not the result is the same.
thanks in advance.
ali1360
All 5 comments
Thank you, this helped me a lot
I had to remove ( .substr(startpos); ) from line 395 to fix the issue. i'm using Arabic.
aaltheiab2012
on 1 Jul 2017
Based on #2819, it sounds like there might be a similar issue with Chinese (a regression in search between 1.6.2 and 1.7), so this might not be limited to RTL languages.
Based on the .substr(startpos) highlighted above, it might be a multi-byte char issue? That would affect a number of non-ASCII languages, not just RTL ones.
tjschuck
on 18 Jul 2017
Hi, I've got the same problem with cyrilic languages. Signed up on the topic and waiting for solution)
As temp solution, commented this string:
option.search_text = text.substr(0, startpos) + '<em>' + text.substr(startpos);
evanre
on 19 Jul 2017
Today I learned that \w and \b are ASCII-specific in JavaScript — they do not work for characters outside the ASCII character range.
I’m working on an alternative solution to #1483, but just wanted to post here because it was surprising news to me and thought you might be interested in learning, too!
adunkman
on 29 Aug 2017
This was fixed in #2877 and has been released as part of version 1.8.1.
tjschuck
on 5 Sep 2017
Related issues
asvetlenko
·
3Comments
jbrooksuk
·
6Comments
vpode
·
5Comments
alexfrancavilla
·
9Comments
eduardokranz
·
6Comments
Most helpful comment
Thank you, this helped me a lot
I had to remove ( .substr(startpos); ) from line 395 to fix the issue. i'm using Arabic.