The LEB site does not have a contact address, so I'll mention it here, hoping that someone appropriate reads this.
Luke 2:44 has acquantances instead of acquaintances
Luke 12:1 has Pharisess instead of Pharisees
John 6:12 has satisified instead of satisfied
Acts 17:23 has observeing instead of observing
James 15:10 has perseverence instead of perseverance (it seems that perseverence is possibly an alternative spelling, but the other two times the word appears in the LEB it is written perseverance)
1P 1:19 has umblemished instead of unblemished
Rev 17:4 has destestable instead of detestable
Rev 18:22 has muscians instead of musicians
Mat 3:8; Mat 3:11; Lu 3:8; Lu 5:32; Ro 2:4; 2Co 7:9; 2Co 7:10; 2Ti 2:25; Heb 6:6; Heb 12:17; 2P 3:9 all have repentence instead of repentance (which appears 11 times in the LEB).
Richard Wilson
http://www.laparola.net/program/
Thanks, Richard.
I assume James 15.10 above is a typo for James 5.10.
We appreciate it!
Rick BrannanData Wrangler, FaithlifeMy books in print
Yes, it was James 5:10.
I missed some more however:
Acts 19:13 iterant instead of itinerant
1Cor 1:16 maybe Stephanus; in 1Cor 16:15,17 it is Stephanas
Eph 6:11 strategems instead of stratagems
Rev 9:11 maybe Abbadon; almost all other English versions have Abaddon, and the critical text that LEB says it follows has Ἀβαδδὼν (although the Byzantine text is Ἀββαδών)
I have gone through the notes to the text now, and have found some more errors:
Mt 23:13 (first note) { should be (Lu 2:36 Liteally should be LiterallyLu 17:20 obeservation should be observationActs 24:6 addtional should be additionalRom 16:1 Phobe should be Phoebe (at least, that is how it is in the text of that verse)1Thess 5:8 (twice),11; 2Thess 2:5,11 have a formatting error, that shows up in different ways. In Logos, the superscript letter that indicates the note is not in superscript, but is part of the text. In the downloadable versions (XML file, text file, etc), the letter is part of the text of the note, eg the note on 1Thess 5:11 starts "dLiterally..." instead of "Literally...", where 'd' would be the letter that indicates that the note exists (which should be in the XML file)
Hope to see a corrected version of the text soon...
Remember that the best way to report typos is through the right click menu. That gets them to the right department.
Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."
MJ. Smith: Remember that the best way to report typos is through the right click menu. That gets them to the right department.
Richard might not be using Logos. I suspect he's downloaded the RTF format and run it through a spell-checker.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Mark Barnes: MJ. Smith: Remember that the best way to report typos is through the right click menu. That gets them to the right department. Richard might not be using Logos. I suspect he's downloaded the RTF format and run it through a spell-checker.
Yeah, either that or he's a really fast reader!
I'm pretty surprised that Logos didn't run the text through a spell-checker before releasing it. The number of glaring typos in it is unexpectedly large. This is Bible text we're talking about here. It deserves to be treated with great care.
How to Ask for Help | Logos Wiki | My Machine Specs | My Blog
Almost... I ran the downloadable text and XML files through the LaParola program (see my signature), and with that I can pick up words that aren't used in any other English translation in the program. This is better than using a spell checker, because it doesn't flag all the names (like a spell checker does), but it does show the names that are wrong. There were less than a hundred such words, so it wasn't hard to pick out the misspellings from amongst the words that were actually correct.
I did report the first typo that I found with Logos. But it takes a while to find each of the more than 30 words in Logos, select it, send the report, etc. Life is short and I preferred to send a list. At least I know that someone from Logos (Rick) read the first list of corrections.
If you want to see some poor editing, check out this second paragraph in Nicene and Post-Nicene Fathers, First Series, Vol. XiII (I sent typo reports on many of the words, but there are so many I stopped.)
“The history and remains of St. Chrysostom are in one respect more interesting perhaps to the modern reader, than most of the monuments of those whoare technically called the Fahters. At the time when he was raised up, and in those parts of the Chrisitain world to which he was sent, the Patriarchates, namely, of Antioch and Constaninople, the Church was niehter agitated by persecution from without, nor by any particular doctrinal controversy within, sufficient to attract his main attention, and connect his name with its history, as the name of St. Athanaius, e.g., is connected with the Arian, or that of St. Augustine with the Pelagian, controversy. The labours of St. Athanasius and St. Basil, and their friends and disciples, had come to a happy issue at the second Oecumenical Council; the civil power favoured orthodox doctrine, and upheld Episcopal authority. The Church seemed for the time free to try the force of her morals and discipline against the ordinary vices and errors of all ages and all nations. This is one reason why the Homilies of St. Chrysostom have always been considered as eminently likely among the relics of Antiquity, to be useful as models fro preaching, and as containg hints for the application of Scripture to common life, and the consciences of persons around us.
Philip Schaff, The Nicene and Post-Nicene Fathers Vol. XII (Oak Harbor: Logos Research Systems, 1997).
Elder/Pastor, Hope Now Bible Church, Fresno CA
Thanks again for the reports, Richard.
Updates to the XML, EPUB and TXT formats should be up soon. Same for the *.lbxlls to be used with LDLS3. We have an update to the *.logos4 edition, but will need to wait until we can get the reverse interlinear alignments corrected before we let those updates out. I'll post a follow-up to this thread when I know things have been updated (and what has been updated).
Richard Wilson:Almost... I ran the downloadable text and XML files through the LaParola program (see my signature), and with that I can pick up words that aren't used in any other English translation in the program.
Hi Richard,
If you read this, would you mind providing instructions for how you did this with the program?
Thanks!
Ron Keyston Jr:If you read this, would you mind providing instructions for how you did this with the program?
It was not as simple as I made out. First of all, the program can't import this type of OSIS file (that uses paragraph markers as the structure with the verses indicated as milestones, rather than using the verses as the structure with the paragraphs indicated as milestones). So I had to write a small program to transform the plain text version of the text into a format that could be imported. The method for importing a text is described in the program help file, in the section How Do I... Add the Text of the Bible. There is a reference there to the page "Files to Import a Text", and to a file needed to add the roots to all the word. Having import lots of English Bibles and other texts, I already have a file with lots of English words with the corresponding roots (base words). If you want to use it, it is at http://www.laparola.net/en.zip After having imported the text, I go to Tools | Search in the main menu of the program, the the Choose Word button, then in the second column I choose '*'. In the third column there is then the list of all the words without a known root. Some of them are words that have never been used in any English text so far, so I add them to my list. Others are misprints, so I get them corrected. Of course, this method does not pick up words that are misprints, but the error is to make it a word the same as an existing word. But a spell checker doesn't pick these up either.
Richard Wilson:It was not as simple as I made out. First of all, the program can't import this type of OSIS file (that uses paragraph markers as the structure with the verses indicated as milestones, rather than using the verses as the structure with the paragraphs indicated as milestones). So I had to write a small program to transform the plain text version of the text into a format that could be imported. The method for importing a text is described in the program help file, in the section How Do I... Add the Text of the Bible. There is a reference there to the page "Files to Import a Text", and to a file needed to add the roots to all the word. Having import lots of English Bibles and other texts, I already have a file with lots of English words with the corresponding roots (base words). If you want to use it, it is at http://www.laparola.net/en.zip After having imported the text, I go to Tools | Search in the main menu of the program, the the Choose Word button, then in the second column I choose '*'. In the third column there is then the list of all the words without a known root. Some of them are words that have never been used in any English text so far, so I add them to my list. Others are misprints, so I get them corrected. Of course, this method does not pick up words that are misprints, but the error is to make it a word the same as an existing word. But a spell checker doesn't pick these up either.
Yeah, I ran into some major snags trying to import the ISV into the program, so I gave up and came up with another method to do what I was trying to accomplish. Thanks anyway!
Rick Brannan:Updates to the XML, EPUB and TXT formats should be up soon.
I received confirmation this morning that the XML, EPUB and TXT have been updated. I'll notify here as others are available.
Rick Brannan: Thanks again for the reports, Richard. Updates to the XML, EPUB and TXT formats should be up soon. Same for the *.lbxlls to be used with LDLS3. We have an update to the *.logos4 edition, but will need to wait until we can get the reverse interlinear alignments corrected before we let those updates out. I'll post a follow-up to this thread when I know things have been updated (and what has been updated).
The updated LEB resources have now been published.
Bradley Grainger:The updated LEB resources have now been published.
I just ran your script to update my *.lbxlls file and it said there are no updates available...
TomReynolds:I just ran your script to update my *.lbxlls file and it said there are no updates available...
Tom,
Sometimes you need to close L4 and restart it before L4 will see new resources. When I closed and restarted, L4 automatically downloaded the new update without me even having to use the command.
Keith Larson:Sometimes you need to close L4 and restart it before L4 will see new resources. When I closed and restarted, L4 automatically downloaded the new update without me even having to use the command.
Keith,
I'm referring to L3. I am not using L4 at this time. I'm using the update script they have here http://www.logos.com/support/download/30update.
Thanks,Tom
It's been a few weeks since I ran the updater. Im a 3.0 user too. I just ran it and it updated the LEB and St. Paul and Justification.
I just checked the ftp site and the LEB.lbxlls file is dated March 25 so I don't think you downloaded the freshly updated version. Presumably they are still working on it.
Tom
Chris: It's been a few weeks since I ran the updater. Im a 3.0 user too. I just ran it and it updated the LEB and St. Paul and Justification.