Bug #242
Umlaute and special characters not handled properly in search and filters
| Status: | Assigned | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: | Andrew Dolgov | % Done: | 0% |
|
| Category: | backend | |||
| Target version: | - | |||
| Resolution: |
Description
When using a word containing an Umlaut in a search or a filter it won't match items using the html version of the umlaut.
e.g.
'Köln' will not match 'Köln' or 'Köln'
History
Updated by Andrew Dolgov 421 days ago
- Status changed from New to Assigned
I'm not sure of a generic way to convert this sort of thing, e.g. PHP has htmlentities() but I'm not certain that it would convert to ö.
Unless there will be a patch, can't promise a fix soon.