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

replace lucene with soundex (patented) #836

Closed
jmichae3 opened this issue Nov 3, 2017 · 4 comments
Closed

replace lucene with soundex (patented) #836

jmichae3 opened this issue Nov 3, 2017 · 4 comments

Comments

@jmichae3
Copy link

jmichae3 commented Nov 3, 2017

instead of using lucene to do a job and making Christians and pastors wonder about who is really behind it, why not use

  • pcre
  • partial word searches, such as using std::string.find()!=std::string::npos in a word. break a word down.
  • soundex http://www.highprogrammer.com/alan/numbers/soundex.html
    patent is listed. a fuzzy search is not what you want, since it learns from previous efforts. try a modification of soundex based on the language instead. soundex is an old but familiar replacement for like-word search and it's fairly good.

and did you know you can access a list of strings faster using a reference than passing by value to a function? saves an full temporary copy of the whole thing. and if it's big, that can eliminate 5 minutes.

@refdoc
Copy link
Contributor

refdoc commented Nov 4, 2017

It is the devil what is behind CLucene. We know.

@refdoc refdoc closed this as completed Nov 4, 2017
@karlkleinpaste
Copy link
Contributor

it is the underlying sword library that defines what optimized search facility is provided. as matters stand, sword itself can be built --with-cxx11regex and --with-xapian but neither is used in practice in packages as distributed. routinely, --with-icuregex is used, however. in any event, this isn't an issue controlled by xiphos, but by the packagers of the sword lib.

@jmichae3
Copy link
Author

jmichae3 commented Nov 7, 2017

how about a aounds-like algorithm of your own making?

@karlkleinpaste
Copy link
Contributor

how about we're not researchers in textual extraction.
how about we're not able to alter unilaterally how the sword lib does search.
what part of "this isn't an issue controlled by xiphos" did you fail to understand?

@crosswire crosswire locked and limited conversation to collaborators Nov 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants