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

enable decomposition in search for ligatures and diacritics #204

Open
6 of 7 tasks
robinschwab opened this issue Jan 14, 2025 · 0 comments
Open
6 of 7 tasks

enable decomposition in search for ligatures and diacritics #204

robinschwab opened this issue Jan 14, 2025 · 0 comments
Labels
feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up

Comments

@robinschwab
Copy link

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
  • I optionally donated to support the Fossify mission.

Feature description

When you search for names there should be decomposition for ligatures and special glyphs. This should work on both sides

I.e. when you search for an entry with the name Lætitia, the search term "Laetitia" should return a hit. It doesn't currently.

On the other hand when you have a name that is entered with ANSI characters someone using a local keyboard should get a hit too. I.e. in Switzerland you would enter the name Jule Aßmann as Jule Assmann. But someone with a German (Germany) keyboard layout might search for Aßmann and will currently not get a hit.

Why do you want this feature?

Depending on your language it will happen regularly that you search for a name that contains special characters. You may not be sure wether this name is stored in Unicode or in ANSI in the contacts. Or you type on a keyboard that does not contain the special character.

This feature is expected by users since it is widely implemented in Google, MS Word, Acrobat. Spotify finds the right song when you enter "laetitia" even when it is stored as "Elaeudanla téitéia" (spelled) in their database.

Additional information

The feature is not presend in AOSP either. But we want Fossify to be better, don't we?

@robinschwab robinschwab added feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up
Projects
None yet
Development

No branches or pull requests

1 participant