According to Eep Talstra’s ETCBC database In the BHS (Biblia Hebraica Stuttgartensia) there are a total of 62 occurrences where:
x-Qatal clauses
in which Conjunctive phrases
with Et asher are followed by a phrase, labelled verbal Predicate
Genesis 9:24
Genesis 18:19
Genesis 27:45
Genesis 28:15
Exodus 10:2
Leviticus 9:5
Numbers 32:31
Numbers 33:4
Deuteronomy 4:3
Deuteronomy 7:18
Deuteronomy 9:7
Deuteronomy 24:9
Deuteronomy 25:17
Deuteronomy 29:15
Joshua 2:10
Joshua 5:1
Joshua 9:3
Joshua 9:24
Joshua 24:7
Judges 14:6
Judges 18:27
1 Samuel 12:24
1 Samuel 15:2
1 Samuel 15:16
1 Samuel 16:4
1 Samuel 25:35
1 Samuel 28:9
1 Samuel 30:23
1 Samuel 31:11
2 Samuel 19:20
2 Samuel 19:38
2 Samuel 21:11
1 Kings 2:5
1 Kings 5:22
1 Kings 8:24
1 Kings 8:25
1 Kings 11:10
1 Kings 18:13
2 Kings 5:20
2 Kings 7:12
2 Kings 8:5
2 Kings 10:10
2 Kings 19:11
2 Kings 20:3
Isaiah 38:3
Isaiah 55:11
Jeremiah 7:12
Jeremiah 23:25
Jeremiah 38:9
Jeremiah 45:4
Jeremiah 51:12
Ezekiel 23:22
Zechariah 12:10
Ruth 2:17
Ruth 2:18
Ruth 2:19
Esther 9:23
1 Chronicles 4:10
2 Chronicles 6:15
2 Chronicles 6:16
Software
Accordance 12
If, a picture is worth a thousand words how much more is a video worth? Check out the latest edition/version of the acclaimed scholarly grade (yet, incredibly intuitive and easy to use) Bible Studies research software. If, you like what you see in the video you can download the lite version to try it out.
Introducing Software For running Torah Trope clause/phrase searches
There are times when one might want to find Trope/accent patterns (or clause / phrases ) in the Hebrew Bible. To do so sometimes printed works such as James D. Price’s multivolume Concordance of the Hebrew Accents in the Hebrew Bible are use. Such tools tend to be expensive and hard to find unless you happen to live near a very good library. fortunately, there are few software programs that allow one to run precisely those type of searches.
(1) Quantified Cantillation (It’s free!):
Is a free, to use online cantillation/Torah accent database with an intuitive graphic user interface. All, searches are executed both visually and via a click of your computer’s mouse. Currently, the database only covers the Pentateuch / Torah. https://quantifiedcantillation.nl/
(2) Accordance Bible Software (It’s intuitive, easy to use, and powerful!):
If you own a license for Accordance and one of the Hebrew Bible modules sold on their website you can search for individual accents, accent patterns (Trope patterns), words with a particular accent, morphology, root,wildcards + accents, and so much more. Accordance allows one to do so either by typing in a search window or visually through the construct search window selecting accents via the character palette via a click of the mouse. https://www.accordancebible.com/
(3) BibleWords (It is powerful!)
When you purchases a license for BibleWorks you get 90% of all the modules they offer. So, the base product already comes with enough for you to start searching on accents and accent patterns. In Bible works you search either by typing codes/tags on the command line or through the use of the powerful graphic search engine. However, you will still need to type in the codes to run your searches. http://www.bibleworks.com/
If, by any chance, you are aware of software for search on the Torah trope that I have overlooked or missed please leave a comment here or on the contact page.
The Masora Thesaurus (part two)
I originally posted the following as a series of replies on the Accordance forums in December of 2015.
The printed BHS only contains the Masora Parva, Masora finalis (and a highly edited form of that). Also. The editors of the BHS put theMasora Magna in a separate volume that is now out of print (although a digital edition of that does exist).
The Masorah Thesaurus has so much more. It has the unedited Masorah Parva, the Masorah Magna of the Leningrad Codex(and other sources, too), as well cross references to other Masoretic list, notations, and texts (as well as more). The Masorah Thesaurus is of course searchable in ways that neither the print edition of the BHS nor the digital edition of Gerard E. Weil’s Massorah Gedolah: Manuscrit B. 19a de Léningrad are.
In a printed edition of the BHS we turn to page one or to Genesis 1:1. Now, we notice the raised circle above בְּרֵאשִׁית . That circle in our printed BHS alerts us to the marginal notes called Masora Parva. To better illustrate what has just been said take a look at the following:
In the photo (or in the BHS) we notice that the fist letter of the note is the fifth letter of the Hebrew Alphabet ה̇. We, also notice that the ה̇is has a small dot over it. When we see a dot over a letter that often tells us that the letter is meant to be read as a number. In this case, we read is as telling us that there are five occurrences of the word בְּרֵאשִׁית in the text of the Tanach/Hebrew Bible.
We, also notice that there are two other Hebrew letters in the note with dots; both ג̇ and ב̇ followed by abbreviations or shorthand notes. ג̇ being the third letter of the alphabet represent 3, and ב̇ being the second letter represents two (2 plus 3 is, of course, five). So, the Masora tells us that בְּרֵאשִׁיתstarts a stanza(ר״פ) three times (ג̇) , and is embedded in a stanza ( מ״פ) two times(ב̇).
This may help us understand the above abbreviations:
(Within, inside) מ = מצעא
(Head, start) רֹ =ראש
(verse/Stanza) פ = פסוקֹ, פסֹ, פסוֹ
Sometimes (or at least I have seen some use) קֹ in place of פסוקֹ
However, since the Masora Parva is brief it does not list those occurrences mentioned above. Before the advent of the Masorah Thesaurus that we would need to run a quick Accordance search, check out a paper concordance, or wade through Masoretic lists to find all of the occurrences mention in the BHS’ Masora Parva.
The Masora Magna Register at the bottom of the printed BHS, however, does indicate where we can (or could in past time) quickly locate the list in Weil’s Massorah Gedolah.
Unfortunately, the Massorah Gedolah is out of print, but as mention, before there is a digital version of it in another software platform. Before I got access to the Masorah Thesaurus module I, will admit, I used to use the digital version of Weil’s Massorah Gedolah a fair bit and it still has its place. However, the Masorah Thesaurus module offers much more than what Weil’s Massorah Gedolah does.
Now, turn to Genesis 43:8 in a printed edition of the BHS (page 71). Let’s look at a rather famous example:
וַיֹּ֨אמֶר יְהוּדָ֜ה אֶל־יִשְׂרָאֵ֣ל אָבִ֗יו שִׁלְחָ֥ה הַנַּ֛עַר אִתִּ֖י וְנָק֣וּמָה וְנֵלֵ֑כָה וְנִֽחְיֶה֙ וְלֹ֣א נָמ֔וּת גַּם־אֲנַ֥חְנוּ גַם־אַתָּ֖הגַּם־טַפֵּֽנוּ׃
Take a look at the Masora Parva note for Genesis 43:8 : י̇ב̇ פסוק̇ גם גם גם
י̇ב̇ = 12
Verses =פסוק̇
גם גם גם = a construction/string גם
The meaning = There are 12 verses in the Tanach where גם occurs three times.
The Mm register for Genesis 43:8 only has Mm index numbers for the following words:
שִׁלְחָה= Mm index number 2915
וְנָקוּמָה = Mm Index number 3078
In other words neither the BHS nor it’s companion volume Weil’s Masorah Gedolah can help you in finding the list or references for the 12 occurrences of the גם גם גם construction.
Also, in this case, a paper concordance will be of little help since
גם appears something like 769 times in the Tanach/Hebrew Bible.
Click Searching on גם will similarly not help you much.
(However, Accordance’s construction search can find examples of the structure and depending on how many intervening word you selected between each of the גם your results will vary).
However, Since we have the Masorah Thesaurus we can easily find everything the Masora Parva note of the BHS was alluding to:
(1) Open the Masorah Thesaurus
(2) Open the Table contents
(3) Type in גם and search
(4) Now, we will find the information we wanted to know at:
Paragraph 43839 of 188291
Paragraph 43844 of 188291
Paragraph 43850 of 188291
As we can see there simply isn’t enough space in the printed/paper BHS to provide that type of detailed information for every MasorParvava note. This one reason (there are many more) why the Masorah Thesaurus is indispensable for Masoretic studies.
Differences underlying Morphologically Tagged Texts
The following is dated, but information on issues that still apply to morphological tagging:
(Warring: the Bible Software programs mentioned below have evolved, and have a lot more morphological tagged texts than they did back in the 90’s when this was written. Bible Works version 3 and Logos version 2 are discussed below, but both been replaced and updated by newer and more advance versions of their respective programs, several times, throughout the last decade and half. Now, BibleWorks is in it’s 9th version and Logos is in it’s 6th version)
Researchers who use these tools should be aware of how these potential pitfalls can affect the accuracy of their analysis.
The following discussion focuses on the Greek New Testament, but the principles are applicable to searching the Hebrew Bible and Septuagint.
Differences in the Underlying Biblical Texts
- Different Morphologically Tagged TextsAs has been shown, there is a considerable variation in the tagging schemes used in Greek New Testament texts. The Friberg texts use a more functional classification method than other texts. Even the Friberg 2 text still has many functional and unusual classifications. The Gramcord and CCAT texts use largely formal classifications.Unfortunately, except for Gramcord, the manuals for popular Bible-search programs rarely discuss the assumptions used in the classification of words. Yet it is essential that researchers understand the nature of the underlying machine-readable biblical text if their analysis of the text is to be meaningful.The print edition of the Friberg 1 text has an appendix outlining the criteria used for the tags (Barbara and Timothy Friberg, eds., Analytical Greek New Testament, Grand Rapids: Baker, 1981). Unfortunately there is no similar book explaining the classification philosophy of the revised Friberg text. In many instances TheWord deviates from the Friberg 1 tags, without documenting the differences. No program makes use of more than one of the Friberg multiple classifications of ambiguous words and no program documents the selection criteria…
- Many tagged texts have some functional or unusual classifications of words which can produce unexpected search results.In Gramcord, many foreign words such a hosanna are classified as interjections. However, foreign proper nouns are classified as nouns and parsed by function in context. By contrast, Bible Windows and Bible Works classify hosanna as a particle.Conjunctions and particles are particularly difficult words to classify. A beginning user might miss many occurrences of kai if he only searches for the word as a conjunction. Since kai also functions as an adverb in some cases, most programs will sometimes classify it as an adverb. However, as the following chart shows, the classification choices in individual instances vary considerably:
- Bible Windows was unable to report the total number of occurrences of kai, because it only allows 750 matches in a search. Since it is hard to predict how a program will classify the word in any given passage, the safest approach is to search for all possible classifications and manually eliminate invalid matches. The Gramcord manual documents how many times each word is classified as a conjunction, particle or adverb, which makes it easier to define searches that will find all occurrences of such words.Since the Friberg text (Bible Works and TheWord) attempts to classify many words by function based on discourse analysis, some classifications may be surprising to users. Friberg 1 uses the category of “substantive adjective” to refer to adjectives which are used as nouns in context. For example, agathos (“good”) is classified as a substantive adjective in Mt 5:45 (“he makes the sun shine on the evil and the good). This type of classification affects 4131 occurrences of 1068 words in 3009 verses! While adjectives can certainly function as substantives, the term “substantive adjective” is not a part of speech used by most Greek grammars. It would be easy for a user to accidentally miss many important occurrences of adjectives unless he searches both for “adjectives” and “substantive adjectives”. The Friberg 2 text eliminates the substantive adjective classification, but it introduces other surprising functional classifications. For example, in most cases Friberg 2 classifies relative pronouns as adjectives, with an adjective subtype of “relative.” It introduces a category of participial imperative (168 occurrences of 120 words in 135 verses) and (7813 occurrences of 1726 words in 4792 verses).Functional classifications such as those frequently used in Friberg’s text are more subjective than formal classifications. Their value depends largely on the accuracy of the classifier’s interpretation of the text. While they appear to be objective raw data, in fact they contain the prior conclusions of another researcher, which tends to skew the search results to fit the classifier’s own viewpoint.
- Treatment of Classification AmbiguitiesEven the strictest formal classification method must classify certain words by function in context, since the morphology of these words is inconclusive. While in most cases the meaning is clear in the context, in some instances the grammatical classification is subject to scholarly debate. For example, the gender of potamou could be either neuter or masculine. In Mt 6:13 the meaning is debated: Does the Lord’s Prayer ask for deliverance from “evil” (neuter) or “the evil one” (masculine)? Since Bible Windows 2, Gramcord and Accordance classify potamou in Mt 6:13 as neuter, a search for masculine adjectives will not find the verse. By contrast, TheWord and Bible Works classify the word as masculine and do not allow the word to be found in a search for masculine adjectives! Only Bible Windows 3 acknowledges both possible parsings and allows the word to be found with either search.Bible-search programs would be more useful if they marked such words as ambiguous and allowed searching on the multiple classifications. The print version of the Friberg text includes multiple classifications in many instances. However, at this time only Bible Windows 3 allows searching on Friberg’s multiple classifications. Although Bible Works and TheWord both remove the multiple parsings in Friberg 1, the documentation does not explain the criteria used to make these choices.Gramcord makes a good attempt at handling ambiguous classifications. In many cases, it tags words in multiple ways and flags the ambiguous classification in the resulting concordance. The documentation lists all ambiguous classifications which are used. However, even Gramcord could be improved in this area. For example, it does not include the ambiguous classification ofpotamou in Mt 6:13.