There is a KJV-only church in the area that is going to be REALLY UPSET that Logos updated the KJV!!
The changes that Logos has introduced in this update are all as inspired as all the other changes that have been done to the KJV since 1611...
I can't tell if you are joking or not. The emoticon leads me to believe not... In any case, it isnt the KJV TEXT which has been updated, but the KJV FILE.
While it is unlikely the text is changed other than spelling mistakes and unintentional errors there is underneath the text links to the hebrew and greek original and again may have unintentional errors linking to the wrong thing. It could even be as simple as a paragraph maker was not in place so two paragraphs were running together. But rest assured if you had worry nothing has been changed indeed were any changes there you can be sure you'd have to be paying for the new and improved version... ie: https://www.logos.com/product/24557/the-new-cambridge-paragraph-bible-with-the-apocrypha-rev-ed
-dan
It is probably due to the inline interlinear problem reported on another thread: https://community.logos.com/forums/t/152619.aspx
This is the reason for today's update (Tuesday, October 17, 2017).
For future reference, I have not known Logos to update the text (by change) of any Bible. When they speak of updates, it is generally links, typographical errors introduced by Logos, display issues, etc.
I have not known Logos to update the text (by change) of any Bible.
I do know that they have updated the text of a Bible! See ESV.
I have not known Logos to update the text (by change) of any Bible. I do know that they have updated the text of a Bible! See ESV.
Wow. That's interesting. I won't contaminate this thread with the discussion, but I am interested and will be looking into how a textual change could occur (and what changed) without the publisher releasing a new version such as was done with HCSB. Thanks
To my knowledge, we have only changed/edited text of a Bible with publisher's approval. Is there something specific you're thinking of here, alabama24?
How about the LEB then? [:#]
I am surprised that you don't know what I am talking about! [:)] For the record, I am not upset about this policy or the change... rather, to the contrary I am thankful for it.
The ESV has undergone a number of changes. The TEXT of the ESV license which we have has undergone those same changes. "Faithlife" didn't make the changes to the text... the publisher did. Faithlife did, however, change the copy of the text we have to correspond to those changes. This has happened at least twice. The current license for the ESV is the 2016 edition. If someone was particular about wanting the previous translation of the ESV (i.e. 2011), they would be out of luck. See this for more info: https://www.blueletterbible.org/help/esv2016.cfm
Wow. That's interesting. I won't contaminate this thread with the discussion, but I am interested and will be looking into how a textual change could occur (and what changed) without the publisher releasing a new version
Did my previous post answer your question? The change wasn't done without the publisher's permission, to the contrary, I presume it was done upon the publisher's request!
Sometimes when a publisher makes changes to a resource, it becomes a new "resource" or "edition." Other times, it is considered the same one. When the ESV made changes (on at least two occasions), those changes populated to the "ESV" in Logos. Logos doesn't have multiple versions of the ESV in their system... they have one. When changes were made, everyone received those changes.
Wow. That's interesting. I won't contaminate this thread with the discussion, but I am interested and will be looking into how a textual change could occur (and what changed) without the publisher releasing a new version Did my previous post answer your question? The change wasn't done without the publisher's permission, to the contrary, I presume it was done upon the publisher's request! Sometimes when a publisher makes changes to a resource, it becomes a new "resource" or "edition." Other times, it is considered the same one. When the ESV made changes (on at least two occasions), those changes populated to the "ESV" in Logos. Logos doesn't have multiple versions of the ESV in their system... they have one. When changes were made, everyone received those changes.
Yes it did. Thank you very much.
Actually, I had read that before, and had forgotten. [:)] I went to create a file of the changes, and found that I had done that before also. I'm really slipping these days. Lol
Here is the docx file in case anyone else is interested. If it doesn't post, it is easy to recreate. Just go to Blueletter link.
6036.ESV 2011-2016 Textual Changes.docx
LOL!
Hasn't changed since Paul wrote most of the NT.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
