How do I get rid of mounce?

[William B]

When using a strongs tagged bible (esvs) when I click a word I want the strongs dictionary not this mounce summary of the word which i find to be the least useful of all the Greek resources. I have tried reordering the order of the modules in the Greek section, but it makes no difference this mounce thing appears unmovable! Am I doing something wrong? I remember before i could control it then this mounce stuff came on the scene, I have tolerated it up to now but I am sick of having to amplify twice to get relevant information or using the search thing to jump to another module.

 

Any help much appreciated.

Edited January 16, 2014 by William B

[Rick Bennett]

Each of our Key Number (Strong's or GK) tagged texts is designed to work with specific dictionaries. Only the KJVS is designed to automatically amplify to the older Greek/Hebrew Strong's Dictionary. We made this decision a couple years ago, and to my knowledge have not had anyone object to it.

 

We previously used the so-called Greek/Hebrew Keys dictionaries, but these were basically the old Strong's dictionaries with some edits to the numbering system to help them accord to modern choices in lexicography. The definitions however, were still based on translation choices in the KJV, and so in many cases were entirely inconsistent with how the words were translated in the ESV and other modern translations. The Mounce Greek (and Kohlenberger/Mounce Hebrew) are much more modern, and accommodate both the Strong's and GK numbering system.

 

I hope this helps explain our rationale. On iOS the only option is the two-step method you alluded to, to still amplify to the Strong's dictionaries. On Mac (or Win) you can amplify by lemma, then select the dictionary of your choice.

 

Additionally, I am really curious why you feel the Mounce dictionary is inferior to Strong's. Can you provide some specific feedback on why? This may help us improve the product. Further updates are planned for it, but not in the immediate future.

 

Thanks for the feedback.

[Julia Falling]

Rick – I really like the KM Hebrew, and it's my first choice when I want to learn more about the word behind my English text. Maybe when I get a bit of an handle on Hebrew that will no longer be the case. But for now, it's great.

 

I'm most often in the NAS95, however, and would love my triple click to open the KM. Is there any way for me to override the NAS95 —> NAS Hebrew Dictionary? I find the Strong's, Key, and NAS dictionaries to be too bare-bones to be of any use except to learn what root word(s) is behind the one I'm studying. For that the NAS Hebrew Dictionary is helpful.

[Rick Bennett]

Rick – I really like the KM Hebrew, and it's my first choice when I want to learn more about the word behind my English text. Maybe when I get a bit of an handle on Hebrew that will no longer be the case. But for now, it's great.

 

I'm most often in the NAS95, however, and would love my triple click to open the KM. Is there any way for me to override the NAS95 —> NAS Hebrew Dictionary? I find the Strong's, Key, and NAS dictionaries to be too bare-bones to be of any use except to learn what root word(s) is behind the one I'm studying. For that the NAS Hebrew Dictionary is helpful.

 

You could amplify by lemma and select the dictionary of your choice. But, at present you cannot edit the triple-click association.

[Julia Falling]

Thanks, Rick!

[willrid]

Yes, I also find the Mounce dictionary to be the least useful. Is there any way to set in preferences which source is used? I would like to return to the Greek Keys as my default which often shows more useful information about the word and its components. I particually find the little Mounce pointing "hand" annoying and useless.

 

WR

[Tony Lawrence]

I use the NKJV as my default translation and since it is based on the same textual base as the KJV, when triple clicking the result is often "off." I have reported numerous instances of this via the report correction. However, after a while I just gave up. Now I parallel with the KJV and a more modern text (usually Mounce or NAS95) and triple click off them if there the NKJV connection is "off."

 

There are things I really like about KM, namely the ability to click on a translation at the bottom and get all the instances in that translation. However, there were features about the older Greek/Hebrew Strong's that were simply more helpful. If one were amplifying to a compound word the Strong's dictionaries would identify those root words. If KM had the root words and their corresponding Strong's numbers it would be my dictionary of choice. I think the better solution as other have proposed is the ability to choose in the preference. I realize Accordance invested a lot of time and effort in getting KM up, but I think the comments above indicate that it has some deficiencies.

[Rick Bennett]

I use the NKJV as my default translation and since it is based on the same textual base as the KJV, when triple clicking the result is often "off." I have reported numerous instances of this via the report correction. However, after a while I just gave up. Now I parallel with the KJV and a more modern text (usually Mounce or NAS95) and triple click off them if there the NKJV connection is "off."

 

There are things I really like about KM, namely the ability to click on a translation at the bottom and get all the instances in that translation. However, there were features about the older Greek/Hebrew Strong's that were simply more helpful. If one were amplifying to a compound word the Strong's dictionaries would identify those root words. If KM had the root words and their corresponding Strong's numbers it would be my dictionary of choice. I think the better solution as other have proposed is the ability to choose in the preference. I realize Accordance invested a lot of time and effort in getting KM up, but I think the comments above indicate that it has some deficiencies.

 

I will look into the error reports; there should not be instances where the amplifying is off. The Strong's number in Mounce should be the same as in any other resource. We'll definitely look into that.

 

And, thanks for the comment on the compound words. We can look into possibly incorporating something like that in Mounce. As mentioned there are planned updates on this.

 

The 'hand' was used simply to try to help the user understand the purpose of the following hyperlinks. We used a symbol in one of our fonts so that you can hover over it and get an explanation of the hyperlinks. I'm open to changing it, but still think it is helpful.

Edited February 17, 2014 by Rick Bennett

[Michael Eppley]

Really for people on a Bible forum its not appropriate to talk about getting rid of someone else, it seems to me that belongs to another forum, that I am sure the NSA monitors closely. I like mounce, mostly but not greatly.