Skip to content
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.

Non ASCII characters in search get mangled #103

Open
ssteiner opened this issue Feb 9, 2022 · 0 comments
Open

Non ASCII characters in search get mangled #103

ssteiner opened this issue Feb 9, 2022 · 0 comments

Comments

@ssteiner
Copy link

ssteiner commented Feb 9, 2022

I've been playing around with your lib and fired off a few queries. e.g. (l=Münster*).
Looking at the SubStringFilter, the Initial value is 'M??nster', not 'Münster'.

I don't think this is what's supposed to happen.

Had a look at the SearchRequestDecoder and sure enough, everything was decoded using the ASCII decoder. Switching that to UTF8 took care of it.

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

No branches or pull requests

1 participant