Using the Tense Voice Mood resource in libronix 3.x, I can use the following query to get 43 occurances in21 articles:
imperative and (aorist or "no tense stated" or perfect or present)
I get 0 results in Logos 4... Am I missing something?
Using the Tense Voice Mood resource in libronix 3.x, I can use the following query to get 43 occurances in21 articles: imperative and (aorist or "no tense stated" or perfect or present) I get 0 results in Logos 4... Am I missing something?
Others can speak more intelligibly but I do know that AND and OR must be in upper case in 4.0.
I do know that AND and OR must be in upper case in 4.0.
I agree!
I had to learn about the UPPER CASE in v4. I can say that for me, the search operator WITHINWORD does not work in v4B3 but does in v3.x. For example I searched: Moses WITHIN 4 WORDS Miriam and the operator worked but did not in v4.
Beta 3 contains a bug that requires "words" to be in lowercase (but all other operators in uppercase).
Ahhhh, knew it was something obvious... Thanks for the info...
Just found out TVM is no longer a searchable field in KJV...
Bradley,
This doesn't work as well in v.4: moses WITHIN 4 WORDS miriam
it should be moses WITHIN 4 words miriam
Have you tried searching the actual morph in a reverse interlinear'ed Bible, like the ESV? (KJV is coming.)
Our hope is to get away from TVM, which just uses numbers to represent combinations of tense, voice and mood, and let you search on actual tense, voice, and mood, even if you're using the English text.
Sorry, missed the quotes. Works fine. Thanks!
Our hope is to get away from TVM,
Please drop TVM, Bob. And also (my hope) is to confine Strong's numbers to the KJV only; replace them with Louw-Nida in the Greek NT's and drop them from NASB95 (where they are not the same system).
Our hope is to get away from TVM, Please drop TVM, Bob. And also (my hope) is to confine Strong's numbers to the KJV only; replace them with Louw-Nida in the Greek NT's and drop them from NASB95 (where they are not the same system).
My guess is that if he did that he would go from having 30 users with pitchforks at the doors of Logos headquarters to a different group of 1000 users.
OK, you read me! But I didn't think there would be that many ...
I have just tried the searches described but I used WORDS and words in two searches and I got different results. See screen shots:
1047 results in this lower case search ^
24,365 results in upper case search \/
Jason,
this is why you got different results; the "words" being in uppercase were not treated like a search operator but as a search item.
Thanks Robert
I'm still unsure about all these commands and just decided to try it out to see what results I got. I looked at the results but must be tired as I didn't see what you pointed out!
It just points out that you need to be VERY specific in searches like these!
Jason
I don't mind things being replaced with proven better systems, but just want to make sure they are in place before the old systems leave... I am especially concerned if the new system really needs additional paid resources to be useful I may not have... In general, it would be good to see a guide with details for what is needed and recommended for moving from any systems being replaced, and if they are available now or when they are expected to be...
I am really impressed with what can be done with the ESV, I just need to get over the learning curve... Thanks so much...
Quick! Where's my pitchfork and torch...gather the angry mob....[:D].
Quick! Where's my pitchfork and torch...gather the angry mob..
Was that for the TVM?[:)]
I don't mind things being replaced with proven better systems, but just want to make sure they are in place before the old systems leave...
In case of TVM Bob has said what would be put in place, and that would be an existing morphological scheme. Getting rid of Strong's from NASB95 would make one resource redundant (NAS Hebrew - Aramaic and Greek Dictionaries). As it is populated with Greek and Hebrew words the loss of Strong's is not an issue.
Replacing Strong's in Greek Bibles is not an issue either because of the excellent Greek-English lexicons available. If it is replaced with Louw-Nida domains this improves the searching possibilities for those not familiar with Greek e.g. search for "LN in 20.1-11" (v3) which is Greek words meaning "Violent"!
I, for one, look forward to replacing strongs.
