SUMMARY When a face region is being tagged, and the user is the process of looking for a name the suggested search returns name values explicitly. STEPS TO REPRODUCE 1. Have a people tag already defined with the name "José" 2. Tag a new face region 2. Click on the face region to add a name 3. Type "Jose" without the accented e OBSERVED RESULT "José" is not returned as a suggested value. EXPECTED RESULT Digikam should ignore common diacritical marks (Example: á, é, ñ, ü, â, ect) when suggesting names to assign to the face region. So a search for "Jose" should return "José" SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The process of adding diacritical marks using a keyboard may involve multiple keystrokes and combinations for example adding an é may involve <Alt>+<1>, <Alt>+<3>, <Alt>+<0> in a standard keyboard. Users with names containing diacritical marks on occasion have to sacrifice the proper spelling of their names in software applications in order to accommodate convenience and avoiding potential problems. In the early days of computing, this was understandable. However as applications and operating systems more generally accept international characters, the applications which run on them should also.
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