possible to edit LBSPBB file type directly?

Because of MS Word's limit of it's Table of Contents, I'm wondering if it might be possible to manually edit a LBSPBB (the file type Logos/Verbum uses for storing Personal Books).

As you can see in the attached example, my table of contents, which follows the outline of St. Thomas's commentary on the Gospel of St. John, exceeds the 9-level limit in Word, and that gets carried over to Word when it's imported into Logos/Verbum.

Any ideas?

Find more posts tagged with

Comments

Dave Hooton

The format, as with other resource formats like *.logos4, is not designed for editing.

I'd be tempted to modify the unwieldy looking source formatting in Word...

NB.Mick

Because of MS Word's limit of it's Table of Contents, I'm wondering if it might be possible to manually edit a LBSPBB (the file type Logos/Verbum uses for storing Personal Books).

no, not that I know of. But you wouldn't want to do this anyway - way too deep into the structure. If I was in your place I'd edit the docx file Word produces, assuming that the Logos PB compiler (and Logos 6 itself and the other ways Faithlife presents the files to us') doesn't have the same limitations. Note that Docx files are nothing else than zipped XML files. They could be written by any text processor writing docx format not having the same limitations (Open Office?), any other XML editor or even an ASCII editor such as Notepad.

So you could write them as Heading level 9 in Word, find the respective entry in the XML and change that to the appropriate Heading Level (which drives the ToC level) before building the PB.

James Smith

https://community.logos.com/discussion/comment/818084#Comment_818084

Dear NB.Mick,

Thank you for the great suggestion. There might be a good solution here.

Actually, I produce the document in OmniOutliner and then export the file as a .docx file. I hadn't realized that docx files were merely zipped XML files, but knowing that, I just need to a compatible XML file out of OmniOutliner, and then somehow zip it correctly or convert it into docx file. Do you you happen to know if it is as simple as changing the file extension? So far that hasn't worked for me (after doing so, I've tried to open the file in Word, but it gives a file corruption error), but there are a couple of spots where I could be doing things incorrectly.

As you indicate, as long as there is no inherent obstacle in Logos, I should be able to move this from OmniOutliner to Logos/Verbum with very little difficulty as long as I can figure out the format and file extension issues.

Any further suggestions would be very welcome.

Best,

James