Identifying causes for "warnings" when compiling personal books

I have been slowly but surely reducing the number of errors in my compilation log for a personal Bible (most due to universal wildcard changes), but I'm coming down to the point of being unable to recognize what is generating an error.

1. I assume "[Warning] closing field bible that is already closed." indicates I have two consecutive "field-off:bible" markers without on intervening "field-on:bible" marker.

2. And I assume that "[Warning] opening field bible that is already open." indicates I have two consecutive "field-on:bible" markers without on intervening "field-off:bible" marker.

3. However, I do not know that generates "[Warning] Text in 'bible' field but not in a Bible verse milestone."

I have been hunting down #1&2, and have reduced warnings from over 2000 to 233, but I'm running out of ways to search for the errors. Can anyone please tell me what to look for to correct #3? Or of a way of finding #1 & 2?

Thanks,

Mark A. Ellis

Find more posts tagged with

Comments

Dave Hooton

I have been hunting down #1&2, and have reduced warnings from over 2000 to 233, but I'm running out of ways to search for the errors.

I have a simple resource with two adjacent WOC (words-of-christ) fields and two Warnings about opening and closing. I've given up on hunting those down! Likewise with "closing field heading that is already closed." You may still have issues with 233 warnings but if you have balanced field-on + field-off tags there is nothing else to do.

3. However, I do not know that generates "[Warning] Text in 'bible' field but not in a Bible verse milestone."

In a Bible PB, this may indicate you have missed a milestone marker @ e.g. [[Bible:Matt 10:12]] {{field-on:bible}} instead of [[@Bible:Matt 10:12]] {{field-on:bible}}, or simply missing a milestone before {{field-on:bible}}.

Mark Barnes

3. However, I do not know that generates "[Warning] Text in 'bible' field but not in a Bible verse milestone."

It means that you have a {{field-on:bible}}, and the preceding milestone is NOT [[@Bible...]. As Dave said, it could be an error (you've missed the @, or mistyped 'Bible'). But equally it could be that you've got another milestone such as [[@Headword]].

As for finding them, the only way I'm aware of would be to copy and paste your Word document into a text editor that supports RegEx (such as Notepad++). Of course, you'd then have to learn RegEx, which might take more time than finding the problems manually!

David Ames

https://community.logos.com/discussion/comment/505845#Comment_505845

At the end of Genesis I force an error by adding two Gen 50 verse 26 lines
[[@Bible:Genesis 50:26]]26{{field-on:Bible}} Not Yet Entered {{field-off:Bible}}
[[@Bible:Genesis 50:26]]26{{field-on:Bible}} Not Yet Entered {{field-off:Bible}}

Then I also do that at the end of every book

This KNOWN error creates an error message:
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.1.50.26
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.2.40.38
[Warning] Consecutive duplicate Milestone Start for data-type bible: bible.3.27.34

Where the 1 is the Book of the Bible with the 'error'
Helps find where the errors are [sometimes]

Also sometimes a warning will leave parts of the missing milestone in your book

[May find "{{" or "[[" or "]]" in the text of the book when read in Logos]

Mark A. Ellis

https://community.logos.com/discussion/comment/505845#Comment_505845

Thank you both for your leads.

After looking at RegEx a little more, I was able to construct a search string which found several more miscodings. We will keep working!

All the best,

Mark