-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Searches with non-ASCII characters like umlauts or accented characters are always case-sensitive #386
Comments
I looked into it and one suggested solution on stackoverflow is to normalize the input and data through the Transliterator extension. I am leaving the pointers here for reference: Normalizing the input may be a solution but would need some big changes to how we store and retrieve data on all views, so I don't think I can provide a patch in the short term. |
To fix issue mozfr#386
To fix issue mozfr#386
I'm trying to wrap my head around this. It definitely works by adding Working on this for a bit. |
…tions to highlight Fix issue mozfr#386
…tions to highlight Also added tests for markString and highlightString. Fixes issue mozfr#386
…acters, use multibyte functions to highlight Also added tests for markString and highlightString. Fixes issue mozfr#386
Searches with non-ASCII characters like umlauts or accented characters are always case-sensitive, e.g.
http://transvision.mozfr.org/?recherche=%C3%BCberdeckende&repo=gaia&sourcelocale=en-US&locale=de&search_type=strings_entities returns nothing
http://transvision.mozfr.org/?recherche=%C3%9Cberdeckende&repo=gaia&sourcelocale=en-US&locale=de&search_type=strings_entities finds the strings.
The text was updated successfully, but these errors were encountered: