Pdf to logos supported format to be read in the software

I was wondering if there is any way to convert the pdf resources that we own into logos software readable format.

Welcome [:D]

Currently, Logos 4 does not offer a way to convert pdf resources into Logos format. Personal Book Builder (PBB) is being developed for Logos 4, hopefully included in next Beta development cycle.

Libronix 3 had PBB; a blog describes "PBB or not PBB" => http://blog.logos.com/archives/2008/08/pbb_or_not_pbb_that_is_the_question_1.html

Also found a Libronix 3 PBB tutorial => http://www.logos.com/media/pbb/tutorial.html - appears converting a pdf to PBB will take some effort.

Learned Libronix 3 PBB has an annual maintenance fee => http://www.logos.com/pbb (not know about Logos 4 pricing)

Keep Smiling [:)]

https://community.logos.com/discussion/comment/233412#Comment_233412

Currently, Logos 4 does not offer a way to convert pdf resources into Logos format. Personal Book Builder (PBB) is being developed for Logos 4, hopefully included in next Beta development cycle.

Bob Pritchett (Logos CEO) has indicated that the PBB feature will allow you to compile from Word (and hopefully other word processors). If you then have a pdf to doc converter, you could get them into L4 that way. OmniPagePro is supposed to be able to do this.

Details on PBB are still somewhat hazy. Along with KS4J, hoping to see PBB in the next Beta.

PS: This feature is still promised for 2nd Quarter 2011. Thus, it must appear in Beta very soon.

David Mitchell

https://community.logos.com/discussion/comment/233443#Comment_233443

Bob Pritchett (Logos CEO) has indicated that the PBB feature will allow you to compile from Word (and hopefully other word processors).

Specifically, we intend to support docx, which started as the Microsoft Word format and is now registered with the ECMA standards body as ECMA-376 (http://www.ecma-international.org/publications/standards/Ecma-376.htm) as well as with ISO as ISO/IEC 29500. PBB should be able to accept documents from any word processor that supports this format.

https://community.logos.com/discussion/comment/233545#Comment_233545

Specifically, we intend to support docx, which started as the Microsoft Word format and is now registered with the ECMA standards body as ECMA-376 (http://www.ecma-international.org/publications/standards/Ecma-376.htm) as well as with ISO as ISO/IEC 29500. PBB should be able to accept documents from any word processor that supports this format.

EDITED:

The problem here is that Microsoft isn't even supporting the strict standard. It can be argued that they are using a flawed implementation under the guise of a"transitional" format created only because Microsoft told the multi national panel that it would eventually support a strict standard which years later they still do not.

PBB should be able to accept documents from any word processor that supports this format.

Again, this is a problem and it concerns me about the future because there is no office suite out there that writes docx as a 29500 strict implementation, nothing. Not Word 2010, not anything.

I'm worried that by choosing this as yet not fully supported format that you're setting yourself up for future incompatibility despite the goals of the stated standards for long term archival etc.

Office 2010 provides read support for
ECMA-376, read/write support for ISO/IEC 29500 Transitional, and
read support for ISO/IEC 29500 Strict.
http://technet.microsoft.com/en-us/library/cc179190.aspx
Office 2010 Not Fully Supporting
ISO/IEC 29500 Strict -- Redmondmag.com
http://redmondmag.com/articles/2010/04/07/office-2010-breaks-iso-iec-standard.aspx
ISO - News - ISO/IEC DIS 29500
receives necessary votes for approval as an International Standard
http://www.iso.org/iso/pressrelease.htm?refid=Ref1123
Office Open XML - Wikipedia, the free
encyclopedia
http://en.wikipedia.org/wiki/Office_Open_XML#Compatibility_between_versions

I would strongly urge Logos to reconsider or to at least adopt additional options beyond that of docx which even in it's transitional form has a limited number of office suites that write to it.

DominicM

https://community.logos.com/discussion/comment/233570#Comment_233570

ISO/IEC 29500 “Strict” version.
This is the version that ISO said should be used for new documents. But neither Office 2007 nor Office 2010 are capable of writing OOXML “Strict.” Microsoft has made no public commitment on when they will fully implement OOXML “Strict.”

ISO/IEC 29500 “Transitional"
the version that ISO stated should not be used for new documents. Neither Microsoft Office 2007 nor Office 2010 implement this version precisely. Further, Office 2010 writes out a non-standard form of OOXML “Transitional” which includes many proprietary extensions. These extensions have not been contributed back to ISO for standardization.

As long as we can import HTML/marked up TXT files I will be happy...

would prefer not to be tied to standard which seems flawed either..

https://community.logos.com/discussion/comment/233545#Comment_233545

Specifically, we intend to support docx, which started as the Microsoft Word format

Is there any word processor available for the Mac OS that uses this format—even in a flawed version—other than Microsoft Word? MS Word for Mac is seriously flawed for serious Bible Study. It does not—and never will—support right-to-left text. With this decision, Logos has started down a dead-end street for the Mac OS.

https://community.logos.com/discussion/comment/233837#Comment_233837

Is there any word processor available for the Mac OS that uses this format—even in a flawed version—other than Microsoft Word?

There is a non-exaustive and not entirely accurate list here as a starting place Jack: http://en.wikipedia.org/wiki/Office_Open_XML_software#Word_processors

Note that it claims a few can write the format but further investigation will reveal they can't or that there are incompatibilities.

https://community.logos.com/discussion/comment/233960#Comment_233960

There is a non-exaustive and not entirely accurate list here as a starting place Jack

When that list is cross-referenced with Mac word processors that can handle Hebrew text, it is not very promising.

I posted a question in the Mellel support page. I'll let Mac users know the answer (PC users can read the answer also, but we will then have to kill them [:D]).

Stephen

https://community.logos.com/discussion/comment/233960#Comment_233960

I would prefer that Logos go with something not based off of Microsoft Word. I use a Mac and am not a fan of Microsoft (hence using a Mac). I have Pages and can save a document as .doc but not docx. So if PBB imports only .docx from Microsoft it will be useless for me. I might as well make them pdf or epub format. Epub is an electronic publication format so to me it would make more sense for PBB to be able to import epub, which I believe is an open format.

In short if PBB only imports .docx then I won't be using it and again it will seem like Logos is treat the mac users (which are growing) like step children. I don't like and won't purchase Microsoft products so please don't go the route of focusing on Microsoft products.

Stephen

https://community.logos.com/discussion/comment/233970#Comment_233970

When that list is cross-referenced with Mac word processors that can handle Hebrew text, it is not very promising.

And yet HTML4 is incredibly cross platform, as is HTML5.

tom

https://community.logos.com/discussion/comment/233973#Comment_233973

HTML4 is incredibly cross platform, as is HTML5

I agree with all that has been said above. It looks like to me [again, this is just my humble opinion] that Logos is making another design error with L4.

https://community.logos.com/discussion/comment/233545#Comment_233545

Bob Pritchett (Logos CEO) has indicated that the PBB feature will allow you to compile from Word (and hopefully other word processors).

Specifically, we intend to support docx, which started as the Microsoft Word format and is now registered with the ECMA standards body as ECMA-376 (http://www.ecma-international.org/publications/standards/Ecma-376.htm) as well as with ISO as ISO/IEC 29500. PBB should be able to accept documents from any word processor that supports this format.

Wonder which Microsoft transitional docx format(s) will be supported ? (e.g. Office 2007 XML, ...)

Libre Office 3.3.2 Final (2011-03-22) is available for download (free) => http://www.libreoffice.org/download/ includes document save as Microsoft Word 2007 XML (docx)

Edit: add Libre Office 3.3.2 Save as with File type: Microsoft Word 2007 XML.

Keep Smiling [:)]

mab

https://community.logos.com/discussion/comment/235082#Comment_235082

I recently put Libre Office on my PC instead of reinstalling Office. I've yet to check how well it does Hebrew. It might replace Office on my Mac if it proves completely viable although I think I will stay with Mellel

Paul Gisbourne

https://community.logos.com/discussion/comment/235082#Comment_235082

Libre Office 3.3.2 Final (2011-03-22) is available for download (free) => http://www.libreoffice.org/download/ includes document save as Microsoft Word 2007 XML (docx)

Edit: add Libre Office 3.3.2 Save as with File type: Microsoft Word 2007 XML.

Keep Smiling

My query as a mac user would be, why should I have to obtain another word processor, albeit free, to use PBB. Surely it would be better that PBB is capable of importing from many file formats?

https://community.logos.com/discussion/comment/235313#Comment_235313

I recently put Libre Office on my PC instead of reinstalling Office. I've yet to check how well it does Hebrew. It might replace Office on my Mac if it proves completely viable although I think I will stay with Mellel

Copying and pasting Hebrew from Logos 4.2a SR-5 to LibreOffice 3.3.2.2 works; albeit with a glitch for Lexham Hebrew-English Interlinear (LHI), see fragments in Untitled 1 screen shot. Can save to docx, but table formatting changes; screen shot shows saved docx (after reopening) and newly pasted Interlinear (that reverses Hebrew word order):

Without inline display, can copy and paste LHI text: removed fragment comments, showing document after save and open

Dreaming about LibreOffice Open Document format support for Logos 4 Personal Book Builder (PBB).

Keep Smiling [:)]

Mike Tourangeau

https://community.logos.com/discussion/comment/233412#Comment_233412

Currently, Logos 4 does not offer a way to convert pdf resources into Logos format. Personal Book Builder (PBB) is being developed for Logos 4, hopefully included in next Beta development cycle.

Do I understand PBB right? It allows you to include pdf resources I already have in a searchable format in L4? That WOULD BE great!

https://community.logos.com/discussion/comment/243785#Comment_243785

Do I understand PBB right? It allows you to include pdf resources I already have in a searchable format in L4? That WOULD BE great!

In the prior (L3) incarnation that was not the case. Whether or not that will be a function of the vastly improved L4 version of PBB is not yet public knowledge.

https://community.logos.com/discussion/comment/243799#Comment_243799

Do I understand PBB right? It allows you to include pdf resources I already have in a searchable format in L4? That WOULD BE great!

In the prior (L3) incarnation that was not the case. Whether or not that will be a function of the vastly improved L4 version of PBB is not yet public knowledge.

Looking at prior incarnation Personal Book Builder Tutorial, noticed document needed appropriate formatting and tags for PBB compilation. Have doubts about PDF resource(s) being tagged for Logos library integration (may be able to convert PDF to DOCX, then add Logos formatting and tags).

Keep Smiling [:)]

Bob

https://community.logos.com/discussion/comment/233545#Comment_233545

What you are describing is of no use or value to me. Even if PBB in such an implementation were free it would be far to expensive. Frankly the topic files feature from e-sword would be far more valuable than the PBB you are describing. And probably a lot easier to implement. How do you plan to deal with the incompatibilities that MS always puts in to ensure that apple and windows versions of office cannot interoperate? How do you intend to deal with incompatibilities between releases of Windows Office? If you don't want to have PBB then just don't do it. Don't put in a crippled useless implementation that no one can use.

Rev Chris

https://community.logos.com/discussion/comment/243949#Comment_243949

What you are describing is of no use or value to me. Even if PBB in such an implementation were free it would be far to expensive. Frankly the topic files feature from e-sword would be far more valuable than the PBB you are describing. And probably a lot easier to implement. How do you plan to deal with the incompatibilities that MS always puts in to ensure that apple and windows versions of office cannot interoperate? How do you intend to deal with incompatibilities between releases of Windows Office? If you don't want to have PBB then just don't do it. Don't put in a crippled useless implementation that no one can use.

Well I for one am looking forward to PBB. I have been waiting a long time for this. And while yes, I'd like to see more flexibility than docx, I'll still welcome the addition as the pain of compatability is worth the benefits of PBB to me. And that also means, for me, I'd like to see PBB released earlier than later, and more compatability added later on if deemed appropriate.

https://community.logos.com/discussion/comment/233970#Comment_233970

There is a non-exaustive and not entirely accurate list here as a starting place Jack

When that list is cross-referenced with Mac word processors that can handle Hebrew text, it is not very promising.

I posted a question in the Mellel support page. I'll let Mac users know the answer (PC users can read the answer also, but we will then have to kill them ).

After copying from Logos 4.2a SR-5 and pasting into LibreOffice 3.3.2.2, noticed vowel point misalignment using SBL Hebrew font, pasted again, then changed font to Silom along with saving and opening document in Microsoft Word 2007 XML format (docx), deleted a blank line, clicked save with pop-up verification of format:

Keep Smiling [:)]