Problem with Creating a PBB

Page 1 of 1 (7 items)
This post has 6 Replies | 0 Followers

Posts 188
Gerald Rodgers | Forum Activity | Posted: Mon, Jan 8 2018 5:43 AM

Hi folks

Any help would be much appreciated. I'm trying to compile a PBB book (Preachers Homilitic Commentary on the book of Romans). Have enclosed the log file. Can anyone please interpret it and tell me what the problem is and how I might resolve it. Thanks so much.

Posts 151
Dave L | Forum Activity | Replied: Tue, Jan 9 2018 4:56 AM

I'm not sure how to interpret the log file but I've found that by stripping the format of the text sometimes helps. I normally copy the entire text from MS Word and paste it into Notepad. Then copy that and paste the NotePad version back into Word. Then hit auto format in Word (2013). It then opens without errors in Logos when saved as a .docx file. If you do not have Auto Format it should still work. But check this out:

If it is the same as what you are trying to develop, the Logos versions have always been better than my PBs.

Posts 505
Robert Neely | Forum Activity | Replied: Sat, Jan 20 2018 3:49 PM

Check your document map in Word for any blank spaces.  It appears you have a paragraph mark with a heading style that does not have any text.

Posts 505
Robert Neely | Forum Activity | Replied: Sun, Jan 21 2018 1:06 PM

Here is an example.  

The space in the document map below is caused by the lone paragraph mark that has no text. This will cause the zero length article compile error.

The style of the paragraph mark has been set to 'Normal' and now there are no blank spaces in the document map.  The file will compile without errors now.

Posts 11832
Forum MVP
NB.Mick | Forum Activity | Replied: Sun, Jan 21 2018 1:51 PM

Since Logos changed the way the PB compiler treats those "empty" paragraphs (i.e. breaking the PB build), it is necessary to treat them.

Either like shown above - reformatting them, or creating the space not with paragraphs, but linefeeds - or by using a workaround like replacing all "^p" (ie. paragraph mark in Word) with " ^p" (i.e. space plus paragraph mark, leave out the quote markers in Word). This way, there are no more "empty" paragraphs and the PB build will work. The additional spaces normally should not be a concern.

I use the workaround if it is a lengthy PB document, since it works quickly and doesn't break the existing Heading style formats or other formatting as tinkering manually with the paragraphs may.

Running Logos 9 latest (beta) version on Win 10

Posts 505
Robert Neely | Forum Activity | Replied: Sun, Jan 21 2018 5:13 PM

That is a nice, quick way to resolve the issue.

I use the Document Map to build the Table of Contents that will appear in Logos using my Quick Styles for Heading 1, Heading 2, and Heading 3. It is therefore easy for me to fix any errant paragraph marks as I go through the document to get the TOC the way I want it.

Posts 232
Genghis | Forum Activity | Replied: Thu, Feb 22 2018 1:22 AM

Public Book  compiler (PBC) does seem to play nicely with the paragraph formatting in MS Word 2016.  If you need space between paragraphs, I suggest you use this feature rather than inserting blank paragraphs.

PBC gives the "empty article" error if you have blank paragraphs.  

Removing all styles except normal also seems to work well too.  It just means there is more work manually adding back in your formatting, such as bold, caps, indenting and of course paragraph spacing.  


Page 1 of 1 (7 items) | RSS