[jsword-devel] regex searching

[trent.jsword at trentonadams.ca]

Yeah, I think it is needed, sometimes certain things are very difficult to find.  For example, if you know part of a word, but not the complete word, you might try something like this.

wash.*word

This would find all words that start with wash, and have any text between that and "word".

As an example, try "wash.*word" in here...
http://www.trentonadams.ca/biblesearch/

I was able to get the results I wanted in jsword, by either giving exactly what I wanted "+washing +word", or by putting "word" and "wash" in the fields "includes these words" and the "include words starting with" respectively, and using the prioritized searching.  It would have been much easier, if there was a checkbox beside the search box that said "regex", and I just typed what I wanted.

So yeah, a simple searcher that just read all biblical raw text, and applied regular expressions to it would be awesome.

----- "Trenton D. Adams" <trent.jsword at trentonadams.ca> wrote:

> From: "Trenton D. Adams" <trent.jsword at trentonadams.ca>
> To: "J-Sword Developers Mailing List" <jsword-devel at crosswire.org>
> Sent: Tuesday, February 23, 2010 7:33:49 PM GMT -06:00 US/Canada Central
> Subject: Re: [jsword-devel] regex searching
>
> But then again, I wonder if it's even needed, who knows.
> 
> ----- "Trenton D. Adams" <trent.jsword at trentonadams.ca> wrote:
> 
> > From: "Trenton D. Adams" <trent.jsword at trentonadams.ca>
> > To: "J-Sword Developers Mailing" <jsword-devel at crosswire.org>
> > Sent: Tuesday, February 23, 2010 7:29:08 PM GMT -06:00 US/Canada
> Central
> > Subject: [jsword-devel] regex searching
> >
> > Hello,
> > 
> > I'm getting the impression that regular expression searching is not
> at
> > all possible without implementing something that loads the books
> > itself, and goes through each verse of the bible.  Is this true?
> > 
> > It seems like the Lucene Index just doesn't support regular
> expression
> > searches, eh?  And it also seems like SearcherFactory is currently
> not
> > finished being implemented as a SearcherFactory, correct?  Or,
> perhaps
> > other methods need to be added, like createSearcher(Book, Class
> > searcherClass)???  Then you could provide another searcher type.
> > 
> > What would be appropriate for this? adding the new
> > SearcherFactory.createSearcher(), adding another "find" method to
> > AbstractBook/Book that is something like "find(SearchRequest,
> > Searcher)"???
> > 
> > Are the books and everything abstract enough that I can search them
> by
> > loading the text?  Or would I have to restrict it to the book types
> I
> > know how to parse?
> > 
> > Anything else?
> > 
> > Thanks.
> > 
> > _______________________________________________
> > jsword-devel mailing list
> > jsword-devel at crosswire.org
> > http://www.crosswire.org/mailman/listinfo/jsword-devel
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel