-
Notifications
You must be signed in to change notification settings - Fork 27
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
Allow transcripts of umlauts #16
Comments
This feature is now implemented and seems to work. However, I found one strange result today:
|
Great! |
@janschreiber Thanks for the report. Unfortunately it's not easy to fix, as we apply some tricks to make it fast: the substring search needed here (as the item is |
@danielnaber Thanks for your explanation. I'm not sure if the following suggestion makes any sense whatsoever, but wouldn't it be possible to apply the normalization to the search terms rather than to the searched data? I mean, isn't it possible to transform a search for words that contain "umlaut-ish" character combinations such as 'ae' to a search for (Cäsar|Caesar) before it is even sent to the search algorithm? |
The normalization needs to be applied to both, but our in-memory database currently isn't a mapping, but just a list of words. We'd need to extend that to contain a mapping from normalized to original term. (Plus, we actually have two different ways of normalization.) |
For all users of openthesaurus not using a german keyboard layout and not knowing how to use compose keys, it would be very nice to have an automatic conversion for umlauts:
dict.cc is doing the same
The text was updated successfully, but these errors were encountered: