| Summary: | [Usability] Ignore common diacritical marks when searching names for tagging face regions | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | José Oliver-Didier <jose_oliver> |
| Component: | Faces-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | hanser, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
José Oliver-Didier
2020-11-21 14:14:32 UTC
Unfortunately, it is still not so easy with the accents today. For example, it is not possible to have Jose and José at the same time in a MySQL table. Both are identical for MySQL. I haven't tested a binary table now. Then comes our QCompleter, who fills the popup with the results. Unfortunately, this currently only knows 3 comparison options. And none would allow us to filter this. It would be conceivable to convert all accented characters. But then we collide with this Bug 406583, for example, where the user wishes that the accent input in the AppImage does not cause any problems. So that accented characters can be searched for. Maik I was thinking just for Face Tag search were name search can get complicated. When the word lists for QCompleter is generated could another entry be added to the list without the accents, still showing "José" as a suggestion when a user types "Jose"? Here is a post with a similar issue: https://stackoverflow.com/questions/31465850/a-qlineedit-qcombobox-search-that-ignores-diacritics *** Bug 506864 has been marked as a duplicate of this bug. *** |