-
Notifications
You must be signed in to change notification settings - Fork 89
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
Latin script: segmenter should support word segmentation #175
Comments
This issue came from a discord chat I was having about how search works vs what I thought would happen. So this all comes from the belief that a user should be able to search for key segments within the system. So, if we use the example above
However, this goes deeper for my use hope, I would want someone to be able to search for redneckbo and get the results accordingly. So, instant-segment does make a lot of sense, but we are also at that point having to consider how many languages and other factors that come into play. Would it maybe make sense to create a solution that would take words that are not dictionary and maybe store them in segments, so RedneckBossRyan could be stored as word segments sure, but could also be stored in 3-4 character chunks |
Sorry if my question sounds a bit simple, but, why don't you add spaces when searching in Meilisearch? 🤔 |
It's a valid question. The issue is usernames. People type these long winded usernames so searching becomes very "challenging" |
Mmmmh, I see, unless having the possibility to upload a custom dictionary, your use case can't be solved completely. If a contributor solves it, you could expect a better Meilisearch behavior in a future version. 😃 |
I'm investigating meilisearch for my employer, whose main customers will be Dutch. For our use case word segmentation is very important. Dutch (and German too) uses a lot of compound words, so searching for a part of a word should work correctly. In my testing, meilisearch (and typesense for that matter), was unable to find documents containing "lichtgeel" and "zachtgeel" when searching for "geel". Even though specific types of yellow should come up when searching for yellow in general. Instant-segment may not work in our case as it is meant for English text, for which corpuses exist which have the bigrams separated. In Dutch the correct word is a combination of two words. |
An other german here with the same problem. |
In the source of that repo, another repo is linked which seems to have a quite good database af all german compound words: http://repo.or.cz/w/wortliste.git / https://repo.or.cz/wortliste.git/blob/HEAD:/wortliste In general I think a database of words would be the way to go (at least for my use cases) |
We should be able to support splitting words by methods other than the text casing. Libraries like instant-segment exist to do that.
redneckbossryan
->redneck
,boss
andryan
can be extractedmassachusetsinstutitute
->massachusetts
,institute
The text was updated successfully, but these errors were encountered: