Sertillanges (3) Abby (3) Abortion (29) Absurdity (1) Academia (4) Accordance (1) Adoration (1) Advent (18) Aesthetics (1) Affluence (1) Agenda (1) Aging (1) AIDS (1) AKG (1) Alan Keyes (3) Alasdair MacIntyre (2) Alexander Solzhenitsyn (1) Algebra (1) Al Gore (1) Alienation (2) Alvin Plantinga (1) America (3) American Culture (3) American Enterprise Institute (1) Americanism (1) Amnesty International (1) Anand Giridharadas (1) Andrew Hacker (1) Andrew R. Lack of Hebrew analytical search capability lack of phrase support in multi-term text expression searches lack of ability to search only Biblical text overall searching performance.#MeToo (1) 1st Corinthians (1) 1st Peter (2) 1st Timothy (1) 2nd Corinthians (1) 2nd Peter (1) 60 Minutes (1) 1970s (1) 1980 (1) A. Word lists fuzzy search features (thesaurus and word forms) XOR and NOT Boolean operators. In spite of these criticisms of search performance, it’s important to keep in mind that the majority of users will make the majority of their searches against one or perhaps a few Bibles, using simple search parameters – and QuickVerse will handle that fine.
Again for comparison, the same search against the exact same set of books in WORDsearch took less than 1 second. manually enter against a collection of 15 books. Creating a search range for non-contiguous books is no problem (e.g. The only default range options are All, Old Testament, and New Testament, but you can type your own search ranges into the box, and recently defined custom ranges are added to the selectable options in the drop-down. Setting a filter for Bible ranges is done via a drop-down text box. Multiple books – including multiple Bibles – can be searched simultaneously. Selecting the target books to search is done via an expandable tree control which shows the entire library – including User Books. Terms can be grouped in parentheses for greater control, and both * and ? wildcards are accepted. This is a poor substitute for a NEAR operator, and I can’t imagine wanting to search for two words, but only if they exist in the same book! There is no NEAR operator, but the Search dialog includes a drop-down box where the user selects whether the Boolean logic is applied against terms within the same verse, the same chapter, or the same book. There’s a pick button for those who want to stop typing and use the mouse to input the operators between words. Operators must be entered in ALL CAPS, or by using logical symbols (&, |, X, !). An implicit OR is supplied if there is no operator between two terms (personally, I think programs should instead AND terms by default, so that using more search terms narrows results rather than expanding them, but that is just a preference). Text searches allow for combining words using the Boolean operators AND, OR, XOR, and NOT. There is no facility to search for Strong’s codes as such, but you can search Strong’s-tagged books with a text search for a code, such as for G2588.
Recent search terms can be recalled in the search box, but associated parameters (even including search mode) are not likewise recalled, limiting the usefulness of this time-saving feature. The dialog box includes a pop-up keyboard for “typing” with mouse clicks in various languages. Newer versions of QuickVerse have a fourth mode, Text in Titles, which was an optional parameter to Text mode searches in version 11, and which I never found any use for.
The general search tool has three modes (selectable from a drop-down): Text, Phrase, and Verse Reference. The most recent versions of QV introduce a couple other specialized searching tools I’ll discuss below. QuickVerse has two tools for searching Biblical text: an Analytical Greek search tool designed to work with a morphologically tagged Greek NT module, and a general search tool used for searching English language Bible, as well as all other books – including user-created books.
QUICKVERSE BIBLE STUDY SOFTWARE SERIES
This is the first installment in a series I plan to write, performing a side-by-side assessment of WORDsearch, Logos, QuickVerse, and Pradis.