[sword-devel] Strong's Greek & Hebrew, and indexed word search

[Justin Long]

-----Original Message-----
From: sword-devel-admin@crosswire.org
[mailto:sword-devel-admin@crosswire.org]On Behalf Of Chris Little
Sent: Saturday, August 23, 2003 9:24 PM
To: sword-devel@crosswire.org
Subject: RE: [sword-devel] Strong's Greek & Hebrew, and indexed word
search


On Sat, 23 Aug 2003, Justin Long wrote:

> On Saturday 23 August 2003 01:33 pm, Justin Long wrote:
> > 1) There is a STrong's built into a KJV version with the Sword Engine.
> > HOwever there doesn't seem to be Strong's the other way - e.g. for a
> > specific word, listing all the Scriptures where the word occurs. Has
this
> > been built? Will it be built?
> __________________________________________________________
>
> I don't mean all the KJV, I just mean a reverse of what is presently
> available in the KJV. Like what Crosswalk.com does with the Strong's
> concordance there. Instead of showing, in a particular verse, the Strong's
> #s for each of the individual words, the ability to look at a Strong's
entry
> and find all the verses where it occurs. It should be a simple matter of
> doing the reverse task on the index.

Just do a search on the basis of a Strong's number.  I think concordances
in software are just silly.  That's what search is for.

Do others feel like this is an important feature?  We could possibly add
a new module for this, but I'm not sure which GNT we would use as a basis
in the Greek portion.  And the Hebrew might have to be based on the KJV
itself rather than a Hebrew text.

___________________________________
Justin writes:
I never thought to search for a Strong's number, and I am technically
literate
(a programmer for over 15 years). I doubt must non-technically-literate
people
will. They expect a Hebrew/Greek concordance based either on KJV or ASV. So
if
that's the way you're going to implement it, then you should make it plain
in the
search box that you can search for a Strong's number. I wouldn't put it in
the
manual because many people don't read it.


> > 2) I did a word search on the whole Bible and it took a while for the
> > search to be finished. Has someone indexed the words... because it
didn't
> > seem to be an indexed search, but more like a full text search.

The modules are not indexed.  There's an indexing implementation, but it
doesn't improve the speed all that much.  Our full text search beats a
number of indexed implementations in other software.  Of course, it will
be more sensitive to your hard drive performance (speed & caching), as
well as your OS's caching performance, than indexed searches.

I think we've had some volunteers to work on indexed searching.  But we
tend to get a lot more people who volunteer to do work than who actually
do any.

______________________
Justin writes:
If indexing doesn't improve the speed that much then it isn't good indexing!
Seriously, an index search *should* beat a forced search hands down. That's
why
Godspeed could do a full text search of the Bible in less than a second, at
least in its original incarnation, even on a 80286 (which is where I ran
it).
I have indexed databases at work that can scan over 2 million records in
seconds;
the same thing in full-text search would take over an hour.

Another thing that would be nice is the ability to search all versions at
once for a
particular word. When I'm doing Bible studies, I look at multiple versions.
Right
now what I have to do is go to each version and do a lookup...

Cordially,
Justin Long