Skip to content
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

content chooser search has issues with extended chars #276

Closed
hvelarde opened this issue Sep 4, 2013 · 1 comment · Fixed by #291
Closed

content chooser search has issues with extended chars #276

hvelarde opened this issue Sep 4, 2013 · 1 comment · Fixed by #291
Assignees
Labels
Milestone

Comments

@hvelarde
Copy link
Member

hvelarde commented Sep 4, 2013

content chooser search does not behaves the same when using extended or standard chars; on the images attached you can see different search results when using "apagão" and "apagao":

apagão

apagao

results must be always the same; please use integration tests here.

@ghost ghost assigned marcosfromero Sep 4, 2013
@hvelarde
Copy link
Member Author

according to @jpgimenez this is a known issue of the ZCTextIndex lexicon in versions of Plone below 4.3; the proposed solution is to install Products.UnicodeLexicon in that case:

The standard ZCTextIndex lexicon only deals with 8-bit strings (and only
if you get the zope.conf locale setting right). It does not handle Unicode
or UTF-8. UnicodeLexicon fills this gap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants