Better [Warning] messages by Import of PB Bibles

Hello
Such Warnings by import of a PB Bible is not very useful.
[Warning] Text in 'bible' field but not in a Bible verse milestone.
It should say where this bug is. In which verse +-1.
Thanks
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
Comments
-
For starters cut your docx file into one book per file. Then one chapter per file of the bad book. Then double check that file. Could be as simple as a missing or extra punctuation mark. What I did was to deliberately double up the last verse in a chapter. Then I could count chapters [that had a known error - the extra verse] to where the misstook was. [[Next time build the next bible one chapter at a time.]]
0 -
David Ames said:
Could be as simple as a missing or extra punctuation mark.
Thanks.
Do you mean between the {{field-on:bible}} {{field-off:bible}}? Or where?
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Fabian said:
Do you mean between the {{field-on:bible}} {{field-off:bible}}? Or where?
That I do not [currently] know. First we need to figure out if Gen 1:1 works ok. Then we go from there.
If Gen 1:1 works than you have the general format correct. My Gen 1:1 line below. The '1' just before the {{field-on is to Print the verse number
[[@Bible:Genesis 1:1]]1{{field-on:Bible}} IN the beginning God created heaven and earth.{{field-off:Bible}}
(And it shows as) 1 IN the beginning God created heaven and earth.
If Gen 1:1 works then add the rest of Gen 1 If that works add the rest of Gen and build your confidence that your doing it right.
Then add each book til you find the book that has the error.
Then back that book out and start adding chapters of that book.
When you get it down to one chapter that fails check the formatting of each verse.
If you see nothing wrong back that chapter out and add one verse at a time until you find the verse that fails.
If you see nothing wrong in that verse line retype the verse line and delete the line that was there (that you have now re typed) there may have been an invisible character in the line (maybe a control character?)
Don't give up. Prove that Gen 1:1 works and, step by step, go from there.
0 -
Fabian said:
[Warning] Text in 'bible' field but not in a Bible verse milestone.
Maybe one of your [[@Bible:Genesis 1:2]] has a problem as the {{field-on:Bible}} TEXT HERE {{field-off:Bible}} part seems to have been recognized.
See if one of the double [[ or ]] is only a single or is a triple?
Maybe copy the docx file to a new file name. Change, in the copy file only, all of the [[ to XX and all of the ]] to ZZ then search for a XX[ or a ZZ] or a [ or ] by itself Maybe - that is one of the things I would look for. Then look for missing @ as in Bible rather than @ Bible.
0 -
I am working on adding a Bible to my personal books.
At the end of the book of Ezekiel I added the 35th verse twice [I also did this to all other books
[[@Bible:Ezekiel 48:35]]35{{field-on:Bible}} NotYetEntered {{field-off:Bible}}
[[@Bible:Ezekiel 48:35]]35{{field-on:Bible}} NotYetEntered {{field-off:Bible}} Have not yet done a study in Ezekiel so have not added that text.
The when I get the errors
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.26.48.35
Book 26 is Ezekiel Chapter 48 Verse 35 followed by
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
I know that I goofed up in the book of Daniel.
So I copied the last verse in each chapter and pasted it right after the ‘real’ copy to give me two of the last verse now in each chapter [expect Consecutive duplicate Milestone error now for each chapter of Daniel]
And that is what I got
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.27.2.49
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
My first error was in Daniel Chapter 3 In this Bible I am using the KJV versification but was trying to add the additional, compared to the KJV, verses that are found in the Bible that I am importing. Goofed some of them up. [[Yes, I know that I could have used a DR versication but chose not to as when I use this bible I want the 'no corresponding' verses to show up]] [Could have used the word 'extra' but that would have made a judgement on which Bible is correct. Calling a verse 'extra' or 'missing' judges this version to be 'wrong']
But that is how I debug a Bible PBB. Fabian , How are you coming along?
0 -
Hello David
Many thank.
First I have to say it was not an error only a warning. I was able to import but not without the warning.
I have copied the Bible in a TextEditor with Regex so I have deleted nearly all except the needed one. I was then able to search for any difference from the "normal". But I found nothing.
After my post and as a result of your answer I changed my workflow as follow. I have used a technic I used in A too. Mostly the import in A says where the bug is. But not in any case. I have taken the whole bible and have then deleted Revelation until Job. Because I thought the bug can be in Psalms. And I was right. It imported it well. So I have done than simply Command-Z (I guess for the English keyboard it it Command-Y) and then I selected from Revelation until Proverbs. So I found the bug was in Psalms.
I thought the bug can be in Psalms 3 as I used a Bible with Psalms 3:1, but the versification with a Psalm 3:0 or title.
I deleted then part for part in Psalms until the warning doesn't came. And as I found the Psalm I was going back and deleted verse for verse.
The bug was that Logos have made from Psalm 15:1 ==> Psalm 151. I reported the bug.
https://community.logos.com/forums/p/198021/1148204.aspx#1148204
Thanks.
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
David Ames said:Fabian said:
[Warning] Text in 'bible' field but not in a Bible verse milestone.
Maybe one of your [[@Bible:Genesis 1:2]] has a problem as the {{field-on:Bible}} TEXT HERE {{field-off:Bible}} part seems to have been recognized.
See if one of the double [[ or ]] is only a single or is a triple?
Maybe copy the docx file to a new file name. Change, in the copy file only, all of the [[ to XX and all of the ]] to ZZ then search for a XX[ or a ZZ] or a [ or ] by itself Maybe - that is one of the things I would look for. Then look for missing @ as in Bible rather than @ Bible.
Thanks the Bible was made as a conversation from another format. I used the tool from Michael Schierl. For me it was clear the tags was correct set. But as I wrote before I checked it with Regex.
Thanks
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
David Ames said:
I am working on adding a Bible to my personal books.
At the end of the book of Ezekiel I added the 35th verse twice [I also did this to all other books
[[@Bible:Ezekiel 48:35]]35{{field-on:Bible}} NotYetEntered {{field-off:Bible}}
[[@Bible:Ezekiel 48:35]]35{{field-on:Bible}} NotYetEntered {{field-off:Bible}} Have not yet done a study in Ezekiel so have not added that text.
The when I get the errors
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.26.48.35
Book 26 is Ezekiel Chapter 48 Verse 35 followed by
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
I know that I goofed up in the book of Daniel.
So I copied the last verse in each chapter and pasted it right after the ‘real’ copy to give me two of the last verse now in each chapter [expect Consecutive duplicate Milestone error now for each chapter of Daniel]
And that is what I got
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.27.2.49
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
My first error was in Daniel Chapter 3 In this Bible I am using the KJV versification but was trying to add the additional, compared to the KJV, verses that are found in the Bible that I am importing. Goofed some of them up. [[Yes, I know that I could have used a DR versication but chose not to as when I use this bible I want the 'no corresponding' verses to show up]] [Could have used the word 'extra' but that would have made a judgement on which Bible is correct. Calling a verse 'extra' or 'missing' judges this version to be 'wrong']
But that is how I debug a Bible PBB. Fabian , How are you coming along?
Hello David
Many Thanks. Thanks for explaining the "Warning code 23.3.34" or so. It seems there is a verse ref, but not always for every bug. Similar to A.
O.K do you say if there is a bug at the end of Ezek then Daniel has a bug too?
Yes, I read No more books than the scheme and No more chapters than the scheme. Similar to A. Joel and Mal are the ones which are difficile. If you have Joel 4 than you have Mal 3. Or Joel 3 than Mal 4.
You have then to use the scheme of the Bible you use, for example with Mal 3 and put {{field-on:Bible}} (Mal 4:1) bla bla bla.{{field-off:Bible}}.
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Conclusion:
For David. The bug is found.
For the Logos devs: It seems not all Errors and Warnings has a location like 23.12.36. In the case of my bug / warnings there was no location. There is a bug in Logos that make Ps 15:1 to Ps 151 if the PBB has Ps 15:1 but the scheme Ps 15:0 or title.
It would be great if the bug can be fixed. And probably include a location reference for obscure bug warnings.
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Old thread => 4.5 Beta 10 Text Comparison Puzzle for 1 Verse includes Faithlife development insight about Bible Verse mapping so changed @Bible to @BibleKJV for older Text Comparison.
Fabian said:It would be great if the bug can be fixed. And probably include a location reference for obscure bug warnings.
Considering CEO reply => https://community.logos.com/forums/p/126859/848584.aspx#848584 am not anticipating development effort of PB message improvements as Faithlife has lots more stuff to do (more ideas, improvements & bugs to fix) than available resources: e.g. Feedback has 79 votes for Paper Builder so suggest creating a PB message improvement post => https://feedback.faithlife.com/ for Logos Desktop App.
Keep Smiling [:)]
0 -
Fabian said:
Many Thanks. Thanks for explaining the "Warning code 23.3.34" or so. It seems there is a verse ref, but not always for every bug. Similar to A.
O.K do you say if there is a bug at the end of Ezek then Daniel has a bug too?
There is no error at the end of Ezek EXCEPT one that I put there deliberately. I have doubled the last verse of every book of the Bible so that there will be a warning when the compiler gets to the end of each book. Then when something goes wrong I have [hopefully] a hint where the problem is. If and when I ever finish inputting all the text into this Bible I will remove the doubled verses. I currently only add sections of this Bible to cover what I need to add when I want to use this Bible in my study of that section of scripture.
[some of my studies are on how different versions translate the underlying text when they do it differently. But it is one that I often fat finger a {{ or some other format and I would like some idea where. This study is low on my priority list but when you posted your problem with an error I opened it up to try to help by letting you know how others have addressed Bible formatting errors] Glad you found your error. [If they ever release the Knox translation I will not have to finish entering this one]
0 -
Hello David
Thanks. I was not quite sure about the intention of the "double" milestones, if I had understand it correct. Thanks for your second explanation. Thanks also for the tip. This is a good idea.
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Old thread => 4.5 Beta 10 Text Comparison Puzzle for 1 Verse includes Faithlife development insight about Bible Verse mapping so changed @Bible to @BibleKJV for older Text Comparison.
Fabian said:It would be great if the bug can be fixed. And probably include a location reference for obscure bug warnings.
Considering CEO reply => https://community.logos.com/forums/p/126859/848584.aspx#848584 am not anticipating development effort of PB message improvements as Faithlife has lots more stuff to do (more ideas, improvements & bugs to fix) than available resources: e.g. Feedback has 79 votes for Paper Builder so suggest creating a PB message improvement post => https://feedback.faithlife.com/ for Logos Desktop App.
Keep Smiling
Thanks
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Hello
For Warnings like: "[Warning] Artikel ist zu lang, was zu einem Artikelbruch führt" it would be great if the first 5 words of the article is mentioned after the warning. Otherwise thanks for the warning but it doesn't help.
Thanks
Fabian
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
German => English Thanks to Googol TranslateFabian said:For Warnings like: "[Warning] Artikel ist zu lang, was zu einem Artikelbruch führt"
Artikel ist zu lang, => Article is too long [Was] zu einem Artikelbruch führt => leads to an article break
Just guessing but it looks like some "article" got loaded as two "articles". I assume that it if had not been loaded it would have been flagged as an error.
Also I do not know what the system is seeing as an "article". Once that is defined find the longest one and see if it got cut into two in the output resource.
And [maybe] what we need is the last 5 words before the 'cut' and the first 5 words after that.
0 -
David Ames said:
Also I do not know what the system is seeing as an "article". Once that is defined find the longest one and see if it got cut into two in the output resource.
The system may use the word "article" to mean "Paragraph"
Used a Dummy file 33 pages long with no breaks [one long paragraph] and the output file has three paragraphs
I was shown some text in the "article" See below:
[Info] Starting build for PBB:7e276e5bc6e94a539dc4e52f64cd96ac
[Info] Converting
[Info] Converting\Users\User1\Documents\bible study\ZZ PBB\dummy.docx
[Warning] Article too long, forcing article break
[Warning] Article too long, forcing article break
[Info] Compiling
[Warning] Article 'A_OHCHOCOLATE.NOTONLYAREYOUONEOFTH_RONEOFYOURAMAZINGHEALTHBENEFITS.' has 50111 characters. Consider shortening this article.
[Warning] Article 'A_OHCHOCOLATE.NOTONLYAREYOUONEOFTH_RONEOFYOURAMAZINGHEALTHBENEFITS._A' has 50112 characters. Consider shortening this article.
[Error] Font 'Tahoma' is not a valid font for use in resources.
[Info] Discovering
[Info] Completeanother one of your amazing health benefits. Oh, chocolate. Not only are you one of the most universally savored treats on the planet, but every day it seems a study is released revealing yet another one of your amazing health benefits. [[There was a break inserted here]]
Oh, chocolate. Not only are you one of the most universally savored treats on the planet, but every day it seems a study is released revealing yet another one of your amazing health benefits
Dummy 000. (n.d.).
0 -
Hello I'm coming back to this issue.
Thats fine Logos tell there are problems. Warnings and Errors. But WHERE???
[Warning] opening field bible that is already open.
[Warning] opening field bible that is already open.
[Warning] opening field bible that is already open.
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed.
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed.
[Warning] closing field bible that is already closed.
[Warning] closing field bible that is already closed.
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed.
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed.
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] closing field bible that is already closed.
[Warning] closing field bible that is already closed.
[Warning] Failed to interpret width value: 0ptIn Bible like the one above I would love to see a Bible reference.
In other books I would love to see a short "bla bla bla bla" or in which chapter. So we can search for it and fix it.
For example:
[Warning Gen 3:3] opening field bible that is already open.
[Warning Chapter "God is Love"] Failed to interpret width value: 0pt
[Warning Place "God created the man on his image..."] Failed to interpret width value: 0pt
Thanks.
BTW I have wrote also other issues for PB import which are still unsolved.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Most likely one of the {{ or }} is missing a { or }
My best hint is to double up the last verse of each book as:
[[@Bible:Revelation 22:21]]21{{field-on:bible}} {{field-off:bible}}
[[@Bible:Revelation 22:21]]21{{field-on:bible}} {{field-off:bible}}
Then there will be a warning that that verse is entered twice
Now I added an error: I dropped a "}" to a bible that I am currently working :
[[@Bible:1 Samuel 18:1]]1{{field-on:bible} After Saul talked with David, Jonathan’s heart went out to him, and he loved David as much as he loved himself because they were so much alike. {{field-off:bible}}
Note missing } in field-on for 1 Samuel 18:1
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.9.31.13 Shows that I doubled up the last verse of book 9
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.10.24.25 Shows that I doubled up the last verse of book 10
[Warning] opening field bible that is already open.
[Warning] closing field bible that is already closed. [did not print all of the warnings]
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.11.22.53 Shows that I doubled up the last verse of book 11[Warning] closing field bible that is already closed.
"everything" though book 10 is "OK" but something in book 11 is "goofed up" Now we just need to figure out what is the tenth book of the bible and start looking there. [Hint: Double up the last verse of every chapter in the book with error to find what chapter. Then each verse to find the verse with the error.] Looking at all of the {{ and }} to find one that is { or } is an eye test. - Good hunting!
Yes, FL does not help find where the error is but we KNOW that we will make "mistooks" so we plan ahead - I double up the last verse of each book!
Helps me find where I goofed up. Then I keep them until I finish the entire Bible. Never know when the edit program will randomly drop a character.
0 -
Some hints that might help but first save the file to some temp name because you are going to forget to replace the XX before going to the next step!
search or find: XX or some other text not in your bible - ensure that there are ZERO of that two character set: // \\ also work
replace [[ to XX then search for a single [ fix the error then replace all XX back to [[ before going to next step]]
repeat for ]] {{ and }} Hope that helps
Edit: Also please note that biblE is not the same as bible [Had to use my own troubleshooting methods as I some how changed an 'e' to 'E' while getting a print out for this thread.
0 -
Thanks David
I check this.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0