-
Notifications
You must be signed in to change notification settings - Fork 46
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
Google like search #3
Comments
I suggest we do the search in three mode:
You need to detect which language the search is in. I have seen that Arabic characters have a fixed range in Unicode character set. If the search criteria contains words in that character range, then it is Arabic. Same approach for Bangla. For the other semantic match, we will have to use the Ontology mapping that is being developed separately. Then we will be able to show matches of words that have ontological relationship. |
Hi, just checking, how are you doing with the search implementation? |
I have added a search feature. Please take a look. It does a straightforward Arabic, English, Bangla search now in a regular search page. If you want to extend this, please make a Google like auto complete search feature. You can use the code in Search.aspx to do the search and expose that over an API. |
Hi, After submission of my another two issues, I have start working on this issue. To detect language in the search box, I am using Unicode character hexadecimal range. |
salaam Ismail, there's a Google i18n script/code snippet you can find online to check language of input, and automatically set LTR or RTL. Let me know if you can't find it. ps: you can also see it in action here: http://qurandev.appspot.com/ (type arabic/english in search box) salam |
Google like search feature that matches verses as user types some partial word and shows the matched verses in an auto complete dropdown.
And build a very powerful search feature so that if someone searches using "Hajj", it will show matches containing "Arafah", "Mecca" etc relevant verses as well.
The text was updated successfully, but these errors were encountered: