27 replies to this topic

[WesleyanPreacher]

This morning at my office I just learned of the 2016 ESV Permanent Text Edition which the committee apparently will "freeze" for a while.  Can we get the e-Sword ESV module updated to this latest revision?

 

[Tj Higgins]

This morning at my office I just learned of the 2016 ESV Permanent Text Edition which the committee apparently will "freeze" for a while.  Can we get the e-Sword ESV module updated to this latest revision?

 

It would require permission from Crossway Bibles the company that publishes the ESV

[APsit190]

This morning at my office I just learned of the 2016 ESV Permanent Text Edition which the committee apparently will "freeze" for a while.  Can we get the e-Sword ESV module updated to this latest revision?

It would require permission from Crossway Bibles the company that publishes the ESV

 

Considering that the ESV is an official e-Sword resource, whatever new versions/editions of this translation is released (as with any other) will eventually be updated for e-Sword by Rick Meyers and his team. Just keep an eye on your e-Sword Download Manager of whatever new editions are released.

 

Blessings,

[Eliran Wong]

This morning at my office I just learned of the 2016 ESV Permanent Text Edition which the committee apparently will "freeze" for a while.  Can we get the e-Sword ESV module updated to this latest revision?

 

if for personal use, just need a SQLite editor and half an hour (you may do it faster) to edit all 52 changes listed at: http://www.esv.org/about/pt-changes/

 

if for distribution, as Higgins said, "require permission from Crossway"

[Eliran Wong]

if for personal use, just need a SQLite editor and half an hour (you may do it faster) to edit all 52 changes listed at: http://www.esv.org/about/pt-changes/

 

if for distribution, as Higgins said, "require permission from Crossway"

remarks:

 

1) notes of the following verses also changed:

 

Gen 3:16; 4:7; Hos 13:14; Luk 24:47

 

2) a note deleted in Jdg 6:13

 

3) the punctuation a the end of Col 1:10 changed in 2016 version, i.e.:

... in the knowledge of God;

 

4) to accordance bible software user, the text in 1Kings 8:48 had not been updated in the module.  In additional, footnotes markers in many notes are wrongly numbered.  I had reported these errors to Helen Brown.

[Eliran Wong]

remarks:

 

...

 

4) to accordance bible software user, the text in 1Kings 8:48 had not been updated in the module.  In additional, footnotes markers in many notes are wrongly numbered.  I had reported these errors to Helen Brown.

 

... an update of ESV2016 is now available in Accordance, which had corrected the problems I mentioned in my last post.

[Katoog]

https://www.crossway...esv-bible-text/

http://www.christian...n-permanent.htm

http://www.thetextof...47-and-esv.html

Crossway has deleted the change-log page:

https://web.archive....out/pt-changes/

[APsit190]

I like the way some people name their Bible translations to make it "sound better" or "more improved", or something else. And in doing that, it leaves the field wide open for jokes and fun poked at them; even to the extend where there is heaps of room for puns to come streaming out. And this one has to be one of the best that has been made:

 

ESV - Permanent Text Edition

 

OK, so when I first seen that title, my imagination ran wild. I mean it really went crazy, and I kind of went like this:

 

No, no! Not like that... like this:

 

Fair Dinkum, it's true, and no joking. I'm being really (cough) serious.

 

So, here are some of the thoughts I had:

• OK, if this is the permanent text edition, what happened to the previous editions?
  • Did the text run away?
  • Did the text fall off the page(s)?
  • Did the Text curl up their toes and kark it (that is, did it die)?
  • Did someone keep on erasing the text?
  • Did all the previous editions have temporary text?
• There's a thief running around stealing the text

And so the list can go on, and on, and on, and on, and on, and on... You get the picture.

 

This sort of reminded me when the people of the NIV fame put out the NIrV. You know, the New International readers Version.  An insinuation can be derived from that, the other one (the NIV) can't be read, or that others are just too dumb to read it.

 

So, as you can see, there are plenty of ways that one can be totally entertained by some of the titles people give to Bible translations.

 

I hope you've had fun reading this, and got a good laugh out of it.

 

Blessings,

 

Edited by APsit190, 30 September 2016 - 03:00 PM.

[Katoog]

This morning at my office I just learned of the 2016 ESV Permanent Text Edition which the committee apparently will "freeze" for a while.  Can we get the e-Sword ESV module updated to this latest revision?

The text of ESV module is now updated to the 2016 ESV Permanent Text by the e-Sword downloads. Make a backup if you don't want to lose the 2011 version.

[GWSwordUser]

I want to be sure I do this correctly. My the file name of my current ESV version (2001) is esv.bblx I renamed it as esv 2001.bblx and saw that e-Sword still recognized the file and loaded it in to the Bible tabs. Now I'll download the 2016 version and install it. But before I do, what I'd like to end up with is both versions available in my Bible tabs.

 

Can this be done? How do I rename the tabs so that I can easily tell which tab shows which version?