Viewing .lbxoeb files in Logos 4?

Is there a way to view the old PBB files (with the .lbxoeb) extension in Logos 4? I've downloaded a few from websites but can't figure out how to view them. Do I need Logos 3 or an old version of PBB that's probably no longer distributed?

Thanks,
Josh

Find more posts tagged with

Comments

DMB

Josh ... Logos4 doesn't read the older Libronix3 files Thus on the forum, there's a considerable amount of anguish.

The logic for why is inherent in making the Logos4 files virtually the same as other Logos4 resources, including indexing, tagging and so forth, all drawn from the Word markup language.

Why they didn't at least create a tool to move the older files into a Word environment for final editing is curious. That would have seemed to have been fairly easy (headings/text) but then maybe they tried it, and it didn't move the ball very far.

Brother Mark

https://community.logos.com/discussion/comment/280756#Comment_280756

Why they didn't at least create a tool to move the older files into a Word environment for final editing is curious. That would have seemed to have been fairly easy (headings/text) but then maybe they tried it, and it didn't move the ball very far.

Abandoning user's legacy data is harsh. We all know the pressure to bring PBB to market was intense, but its stupefying ( <-- intended to convey that "curious" just doesn't quantify it adequately for me) that the response is along the lines of.... IF you have the original Word file, you can always apply the new markups to it and compile under L4 PBB.

If Logos won't or can't do the data conversion, how about releasing the code so that a cottage industry user can reverse engineer it. In their spare time. Over the weekend. [;)]

MJ. Smith

https://community.logos.com/discussion/comment/280785#Comment_280785

There is another way of looking at this - which may or may not be right. Logos has stated that the new "store" is intended for user created resources not user formatted resources such as public domain items. Much of the L3 material is PD materiel. What would be the reaction to providing a conversion path only to close off the sharing path?

It seems to me that this may be a case where Logos' view of our use of PB's may not match our view of our use of PB's. I would also note that there was an implication that PB's might quiet some of the demand for changes in the Notes function. For myself that has not happened..

Bob Pritchett

https://community.logos.com/discussion/comment/280785#Comment_280785

The LDLS 3.x PBB was built around hosting Internet Explorer. It uses HTML, not the Logos XML format and display engine. Users told us enthusiastically and unequivocally that they didn't want us depending on IE anymore inside the app. Unfortunately, writing our own IE-compatible HTML parser/renderer is simply too big a job just to read existing LBXOEB. In theory we could write something that does a "pretty good job," abandoning complex HTML, etc. but since most PBB users seem to have started in Word, it seemed easier to have people re-build.

We do hate "orphaning" any data files, and this is one reason we made sure Logos 3.x still runs side-by-side with Logos 4. We haven't removed access to your data -- we just aren't bringing this one format forward.

MJ. Smith

https://community.logos.com/discussion/comment/280839#Comment_280839

We do hate "orphaning" any data files, and this is one reason we made sure Logos 3.x still runs side-by-side with Logos 4. We haven't removed access to your data -- we just aren't bringing this one format forward.

Just to be clear, I do agree with this decision. In terms of the complexity of the task, I'd rather have you use your resources on other projects. However, the timelines, parallel passages and lectionaries we made in L3 are also orphans which I certainly hope are coming in L4.

Brother Mark

https://community.logos.com/discussion/comment/280839#Comment_280839

The LDLS 3.x PBB was built around hosting Internet Explorer. It uses HTML, not the Logos XML format and display engine. Users told us enthusiastically and unequivocally that they didn't want us depending on IE anymore inside the app. Unfortunately, writing our own IE-compatible HTML parser/renderer is simply too big a job just to read existing LBXOEB. In theory we could write something that does a "pretty good job," abandoning complex HTML, etc. but since most PBB users seem to have started in Word, it seemed easier to have people re-build.

We do hate "orphaning" any data files, and this is one reason we made sure Logos 3.x still runs side-by-side with Logos 4. We haven't removed access to your data -- we just aren't bringing this one format forward.

Thanks for the reply Bob. We ALL appreciate that L3 continues to work alongside L4, and that L4 has a PB feature now. Really awesome, as far as it goes.... but in the spirit of having my cake and eating it too: And in a perfect world, L4 PBB would work just as it does and would also read LBX PBs (code re-use from L3?), OR the parser/renderer module for conversion from HTML to XML would eliminate the possibility of orphaning your user's data (if they no longer have the original .doc file) or having to maintain a legacy application to access legacy data. And, yessir, browser independence is a major issue so thank you for addressing that issue.

tom

https://community.logos.com/discussion/comment/280806#Comment_280806

there was an implication that PB's might quiet some of the demand for changes in the Notes function. For myself that has not happened..

same here

Josh Pritchard

https://community.logos.com/discussion/comment/280806#Comment_280806

can you give me a link that talks about this "store" you speak of?

Kevin Becker

https://community.logos.com/discussion/comment/281520#Comment_281520

can you give me a link that talks about this "store" you speak of?

It hasn't been opened yet. Presumably Logos has internal builds that they are working on.